This page is for developing a plan for Winter-Summer 2009 project development, based on the deliverable needed by Susan Brown and Stan Ruecker for DHSI.
Minimal Stuff
- Gathering things. The ability to grab one or more URLs. Hoping to get some scraping tools working.
- Adding things. The ability to create new items with cut and paste from other sources (word processors, pages in subscription-based sources).
- Flagging the state of things. We won't be trying to do workflow control, but a set of tags or something that could be set and then made available to flag various doc states would be good. Can use tags for this.
- Getting the editing of item content working right and hooking in the XML editor. Kamal has written James to start this. May or may not have authority list built in. May or may not have some roles.
- Ability to create subset as a URL for analysis.
- The Tagging is good enough for now
- Public Private for any item (later we get groups) - how do we handle roles?
- JiTR this--bookmarklet to have in your browser that would add things to your JiTR collection
- HTML cleaner - can we create a collection of basic tools
- Can we mark the original location -
- Export - tagged collection - ability to wrap with tags; users could export their work as a single large CSS file that would be readable in a browser
- Some documentation
Possible Things
- Set it up so there are three specialized collections everyone gets:
- Reports
- Notes
- Sample with documents that explain how to use this
- A sharing system based on the UNIX groups model
- Tagging that is hierarchical and from authority lists - is that in or out of the xml
- Inbox collection and idea that you can "send" items and that you can "move" items
- Roles and sending docs to other people
- I would like to set up a linking mechanism so that any one item can
Things they can do:
- Create a sources collection and an collaboratively authored collection
- Run TAPoR tools on sources collection.
- How to rip a PDF - use Tapor tool
JITR/DEEP DHSI Recipe: draft
Ingredients
- A set of research interests
- A set of texts (web pages, OCR scan output, pdfs, text files)
Steps:
- Assign/sign up for user account in JITR
- Set up an identifiable project or collection within JITR
- Assign rudimentary roles (manager, editor, researcher) to people within that project
- Add material to collection by identifying web pages and/or importing or copying text from files (OCR, pdf, word processing)
- Annotate materials in collection with notes, tags
- Import a particular XML schema (failing this, have TEI lite, TEI and Orlando schemas (doesn’t exist yet!) available and already set up)
- Edit some materials in collection using xml editor (some materials will be used for reference and do not need to be xml docs; others will need to migrate from something else to xml, some will be created afresh in xml
- Import authority list files; refer to authority lists from within xml editor
- Edit authority lists to add or modify entries
- Import bibliographical materials
- Link to bibliographical entries
- Modify bibliographical materials, link to docs as whole
- Version control, compare versions feature
- Differential access according to roles (e.g. doc creation for managers; doc editing only for research assistants)
- Communications (either within JITR or an email system)
- Tracking of activities/doc status
- Move between multiple collections, share collections, link material across collections
- Some kind of export function for collections
- reports for managers on docflow/doc status