Old:Interface Mockups

''STATUS: This page is outdated and of historical use only. Please refer to the Curation page.'' Created June 2009 by Sarah Carrier. Updated summer 2009 by Sarah Carrier. Declared outdated December 2009 by Ryan Scherle.

This outdated page contains mockups of the curator interface created in summer 2009.

= First page - shown upon login =
 * The IN TRAY will show the number of submissions needing curation - therefore all of the new submissions. Also, TASKS will include lists of high profile and high use datasets. NOTIFICATIONS will list errors and places where the curator should put their attention. FOR EXAMPLE: a dataset has been submitted that is over the storage limit.
 * The REPORTS section will list reports that are the result of batch operations and queries that are run regularly and automatically. Some of them will be basic statistics reports, and some of them will be error reports, and reports that show submissions that are missing metadata, etc.
 * TOOLS - this is where the tools will be listed in order to be run from the interface.
 * BATCH EDIT is where the curator can go in and search for issues or choose to do unique batch edits - i.e., unique from the batch processes that produce the reports.

= In Tray =
 * This is probably the most important feature of the curator interface - as stated above, the newest submissions will be put into a "curation inbox" where they will be reviewed before finalizing. I am also envisioning that questions, etc. from depositors will also be displayed in the "notifications" section. "Notifications" would also ideally list errors that were noted during submission, for example, "Publications without DOIs." The listing of high profile and high use datasets will be generated through a query based on use statistics.

= Tools page =
 * Essentially, the various tools that we choose to incorporate will be listed, and ideally they will be run directly from the interface.
 * ISSUE: available tools come in a wide variety of different languages, platforms, etc. - this has to be taken into account when integrating with DSpace, etc.
 * DSpace wiki entry for JHOVE integration - important, TechMDExtractor
 * BATCH LEVEL scenarios/use cases:
 * scenario 1: curator needs to migrate/convert ALL items in a certain (proprietary) format to a non-proprietary one.
 * Example: there are 20 Microsoft Word documents in Dryad -> convert all at once to TXT.
 * There are 50 Excel files, they need to be converted all at once to tab delimited.
 * scenario 2: there are a number of file types - those with a certain file extension - that need to be verified/detected, with possible further action taken, depending on the results
 * Example: are all the .nex files the same as the .nexus files? do they need to be converted?
 * scenario 3: the curator needs to convert metadata about all dryad contents/some dryad contents into XML, and store the XML - for preservation purposes, and this should be done regularly
 * scenario 4: legacy data - are these in outdated formats, can they be converted/migrated? again, look for certain file types/extension - use an external file format registry to look for outdated formats
 * then can we/should we offer emulation services? what do we do with those that can't be migrated?

individual item record mockup with ability to launch tool here
 * INDIVIDUAL LEVEL scenarios/use cases:
 * scenario 1: a person submits something in Excel or some proprietary format -> the curator can convert it individually
 * scenario 2: a person submits a file with an unknown file extension -> detect and verify this particular file
 * this should also be a NOTIFICATION for the curator in the "In Tray" - message should be something like "File type not recognized"
 * THEN: can it be converted/migrated? do we need an emulator?

= Batch Edit page =
 * More will be added to this page as batch processes become clearer - and with the next version of DSpace, which will make batch processing easier.

= Reports page =
 * This is going to function almost like reports function in Access, but not as clunky. Therefore, there will be "stock" queries that are run regularly, or can be run by the curator, and viewed within the interface.
 * QUESTION: can we automatically detect metadata that is in the WRONG field?

= General Interface/Functionality Issues Noted and Suggestions, General Questions =


 * 1) When uploading data objects, there is the possibility that:
 * 2) Duplicates are inadvertently added, particularly when uploading many at once.
 * 3) Errors are made with the metadata, or the wrong file is uploaded, and the depositor wants to correct them before finalizing the submission.
 * 4) * Before submission, the author/depositor should have the option to change and fix this information - just as there is an option to edit publication metadata.
 * 5) ISSUE: when you try to upload a READ ME for a data object, the title is reverted back to the default (the name of the file). If you have entered a unique title, this is then lost.
 * 6) If the submission is finalized and the author/depositor wants to add more datasets to the publication, they should be able to go back in and do this -> an authorization issue.
 * 7) ISSUE: when adding keywords, etc. to the publication metadata page, the corresponding author keeps reverting back to the first author listed.
 * 8) QUESTION: what is expected when the depositor is asked for a further description of the publication?
 * 9) ISSUE: with copying and pasting, there are a lot of issues with special characters. This needs to be dealt with. (It can be the curator's task to fix these).
 * 10) Suggestion: The second link under "This item appears in the following..." to "Show full item record" seems either unnecessary or it's not in the right place.
 * 11) ISSUE: there is a problem with the display of search results - for example, when searching full text for "Gibson," the same record is repeated in the results list over and over.
 * 12) QUESTION: don't we need a field for page numbers for the article??