Skip to content.

Find topic

Web tools

Help

Tools

       Analysis Tool Bar  +

DEEP Stories

These are user stories to help determine priorities and study specifications for RDI efforts relating to Dr. Susan Brown's work.

DEEP Users
Supervising
Editor
Cheryl
Grad
Researcher
Ian
Senior
Editor
Amanda
Researcher
Ziggy
Collab
Author
Sandra

User Story 1: Supervising Editor

rdi-cheryl.jpg

Cheryl is a contributing editor for the Orlando Project.

She needs to work with a number of entries and needs to accomplish encoding quickly and effectively.

As a senior editor she also helps to shepherd less experienced contributors through the process and is able to check associates' progress and offer assistance based on status reports and requests for assistance surfaced through the dashboard.

The Full Story ...

Here you will find complete user story, along with persona information and a number of scenarios relating to this story.

User Story 2: Graduate Student Researcher Contributor

not John Lutz

Ian has recently become a contributing editor with the Orlando Project.

He needs to build entries and collect reference and primary materials to begin creating entries but is not familiar with the technical underpinnings of SGML or XML encoding. He is generally familiar with editing tools and has an extensive background in the subject matter of the project.

The DEEP dashboard allows him to monitor his progress on the entries that have been sent to him for initial research and to request assistance with contextual or technical problems that he encounters.

He uses the DEEP integrated text and document management to consult online sources, to encode entries and submit them to the DEEP work flow.

The Full Story ...

Here you will find complete user story, along with persona information and a number of scenarios relating to this story.

User Story 3: Senior Editor

rdi-amanda.jpg

Amanda is a professor of early modern English literature at Brock University. She is a senior editor for the Orlando Project.

She needs to be able to effectively scan and verify entries submitted by contributors and process them for inclusion in the Project. This requires her to be able to work with a large number of entries efficiently, and to be able to read them closely for editorial accuracy, emphasis, feel, pace, sequence, as well as for encoding errors or omissions.

She uses the DEEP Dashboard Management system to get an overall picture of editorial performance and be able to quickly prioritize her workflow. Using the dashboard she is able to identify her priorities, view entries submitted for review, make editorial changes and accept entries for publication or send them to other editors for further processing.

User Story 4: End-User/Researcher

not Kevin James

Ziggy is a graduate student at Columbia University.

He is researching the evolution of the treatment of temperance in the writing of Victorian women. He wants to begin his research by compiling a list of names of authors who have dealt with this topic in their writing and to begin to build a bibliography of works to consult. The Orlando project's repository interests him because he is trying to connect upbringing and social circumstances with participation in and attitude towards the Temperance movement.

Ziggy consults the textbase-in-progress to locate authors that meet his criteria and to compile bibliographic and biographic information with his personal texts.




User Story 5: Collaborative Book Author

not Kevin James

Sandra Blenkinsop, a professor at OISE, is editing a book of essays on the use of Powerpoint in the Classroom with two colleagues as co-editors and other colleagues as contributors. She is collaborating with her two co-editor colleagues on a direct peer basis. In the past they have simply emailed revisions and comments in word files. In addition to their email communications they have also had face to face meetings and telephone calls, the results of which has not been particularly documented. She uses the DEEP Editorial Collaboratory to edit, comment on, and mark up the manuscript as it evolves and to be able to collect links to references, some of which contain the print material being referenced and some of which refer to online media. Revisions to the manuscript are tracked and retained by the system so they can be reviewed by her other two collaborating editors. Each of the three editors can use the collaboratory in this way, commenting on each other's changes and implementing her own, as well as adding further references.

Contributors to the in-progress collection can also access it through DEEP. They can read the whole collection, but can only edit their own essays at specific points in the process (in accordance with how the access levels have been set by Sandra and her colleagues, who could have left each individual essay open to editing by the author at any point), when alerted that it is time to do so after the co-editors have read and commented on the draft submission, and again when the essay has been copy-edited and is ready for final proofing.

When the collection is ready, DEEP will allow Sandra to export it as a marked-up file in LaTeX? or several other standard formats ready to transmit to a publisher.




-- SusanBrown - 21 Feb 2008


Use this box to quickly add a comment to the page.

more options...