CDLUC3 / dash

General repository for documents and communication for UC Dash project.
http://cdluc3.github.io/dash
MIT License
11 stars 4 forks source link

Oct 2013 Dataset deposit from Data Management Consultant in UCSF OB/Gyn Dept. #8

Open MeganLaurance opened 10 years ago

MeganLaurance commented 10 years ago

Here is detailed description of the user experience and use case from a dataset submission in UCSF DataShare from October 2013.

This use case (Data Management Consultant, Ob/Gyn & Reproductive Sciences) resulted in a dataset deposit. http://datashare.ucsf.edu/xtf/view?docId=erc/ark%2B%3Db7272%3Dq6pn93h6/mrt-datacite.xml;query=;brand=default o The data from this use case came from a multi-center clinical study. The data was already de-identified (no PHI). The study was NIH funded, had concluded, findings published, and ready to be archived. In the words of this user “We’re done with this data. We’ve picked all the fruit. It should be put out there in a repository like DataShare.” o This Data Management Consultant for the project had also been fielding requests from other investigators to share their data. This had been a cumbersome process involving repackaging the data and sending it via e-mail. Now that the data is available on DataShare she can point other researchers toward the link on DataShare. (We think this is a great use case, and probably pretty common among Data Analysts and Lab Managers here at UCSF who deal with NIH policy compliance, and other open access compliance issues.) o She appreciated that the metadata fields and accepted file formats in DataShare were open-ended enough that the barrier to data deposit in DataShare was fairly low. She felt it would encourage more people to share their data. o Her user experience depositing the data in DataShare was very positive. She had very few questions, and generally found the interface intuitive and easy to use. (We sat behind her to watch the first-time user experience, but didn’t provide a lot of instruction on how to go about depositing the data). o With that said – there were a few enhancement requests we noted during the data sharing session:

  1. Make it really obvious what file formats are accepted. Will it take SAAS data? She wasn’t sure.
  2. Add a printable checklist somewhere so the user can print out the Steps to Deposit. “That way I can prepare ahead of time before I sit down to deposit the data”.
  3. Eliminate the Publication Date field. What DataShare really needs is the date of deposit in DataShare, which can be automatically detected and added to the record. No need for the user to enter this.
  4. Add the ability to add multiple keywords in a tab-delimited or comma-separated list (rather than one at a time). She was copying and pasting keywords from the associated publication, and the MeSH terms in the PubMed record.
  5. “Click here to review metadata” before submitting the record should be more obvious. She didn’t see it.
  6. Would be great to autofill metadata from a PMID associated with the dataset. (eScholarship has this feature…. Perhaps we could repurpose it for DataShare.)
  7. Add a place for the data depositor’s contact information. It wasn’t clear to this user how she would be contacted if someone downloading her dataset had questions.
strasser commented 10 years ago

Some of these enhancement requests here are already represented in other tickets:

(2) Printable checklist = #6

(6) PMID auto fill = #5

(7) Contact information = #3

Also, (3) Publication date field has been eliminated (auto-filled by Dash)

strasser commented 10 years ago

Added separate issue for (4) - multiple keywords. #28