Curator Notes

From Dryad wiki
Jump to: navigation, search

Private curator notes on submissions. See Trello Card #33 on the Dryad Development Board.

Curators require the capability of adding notes to submissions within the Dryad system. These notes are only accessible to curators. Currently, e-mail and a submission tracking spreadsheet are used to communicate these notes externally.


Requirements

The following requirements were gathered through interviews and contextual inquiry (observing someone interacting with a product) with the curators.

  • General information
    • Current handling of curator notes: Using e-mail and a google spreadsheet.
    • First thing curators do before starting a new submission is check to see if there is a note
    • Notes are usually short and standardized unless there is something wrong. In the google spreadsheet, problem submissions are red to draw attention to them.
    • 2 - 3 submissions per week require notes
    • Names are not included in notes. It's unnecessary.
    • If a note is resolved, it may be deleted.
      • An advantage of the google spreadsheet: You can get an overview of ALL notes (and problem submissions.)
  • Possible places in the Dryad system to access notes
    • A new tab or metadata field in the main package page (not for the public).
    • Item Metadata page is used the most. May need a note for individual fields on the file pages
    • Date issued and abstract (dc.description) are usually changed, so having notes there saying “update this when published” or similar could be helpful.

Dryad Project Retreat 2013

The following items are the result of the breakout sessions during the Dryad retreat 2013. The information underneath each item are from individual interviews with the curation staff in order to determine the usefulness of the ideas from the Dryad retreat.

  • Identify differences between comments and discrete queues
    • Discrete queues: Packages w/distinct problems that require correspondence w/author, help from head curator, etc.
    • Could be confusing unless there is just one extra queue, the “problem queue”
      • Lots of common problems, page might get too long w/more queues. Some common problems come and go, like payment issues. If those common problems are fixed, then there is no need for the queue anymore. Fine w/ 1 problem queue
    • Possible development issues?
    • Idea: Queues for assignments
  • Increase number of items per page on my tasks (infinite scroll?)
    • Currently, only 10 submissions per queue are displayed
    • Really want infinite scroll. The curator spreadsheet’s advantage is that all data is displayed and can be easily searched through
      • Won’t need Dryad specific search, could just use browser search (ctrl+f)
    • When clicking on display all link, actually display everything in the queue.
    • Having infinite scroll would be a lot to see, especially for Publication Blackout queue.
    • Probably have about 200 total submissions on My Tasks page. I search instead of scrolling. Just too much to scroll through. A compromise would be to fix display all link
  • Improve facets for searching blackout queue (e.g. by journal)
    • In add refinement section of search add these facets:
      • journal name
      • data/file type
      • if something has a note or not
  • Date should be a column on the queue page
    • Date submitted is most helpful
    • If a submission is pulled and worked on, then put back in the Unclaimed queue, it goes to the bottom of the queue, instead of to its original position (the top of the queue). Fix this.
  • Notes require provenance (timestamp, note author)
    • Will dryadqueue be used as the author of the note? If so, will want to change it when creating the note.
  • Notes should be archiveable if they are issues that are resolved
    • Yes, notes should remain with submission
  • Ability to make notes public (double confirm)
    • Public for anyone who comes to Dryad? Why?
    • Idea: In review, want authors to mark a file for deletion, instead of e-mailing Sara. These notes can be public to the people involved in the review process.
      • Otherwise, cannot think why public notes would be useful. If there is a note about the data, it will be in the readme.