Dryad Management Board Meeting Friday, May 22 1:30 p.m. Session 3: Software development timeline and priorities Slides pprepared by the Dryad development group

Overview  Current timeline [see handout]  Activities [??/tasks?] impacting Dryad’s functionality –Curation and quality control  Submission system  Search interface  Discussion

Activities Impacting Dryad’s Functionality: Curation and Quality Control 3 May 21-22, 2009, Dryad Management Board Meeting

Curation: Collecting, preserving, archiving, and providing access to digital data stored in Dryad  Curator: Generally an information professional who has knowledge of and experience working with information standards  Dryad depositors perform some curation tasks  Software aids curation  Data curation tasks  Name authority control for authors [subjects, and institutions?]  Quality control  Maintain documentation of cataloging/curation policies 4 May 21-22, 2009, Dryad Management Board Meeting

Name authority control example  Choice of name –John Doe, John Doe-Ramsey  Fullness of name –Todd Vision; Todd J. Vision; Todd Jeremy Vision –Todd Vision, Ph.d.  Entry element –Todd Vision; Vision, Todd  Benefits: Provides consistency, interoperability, and collocation (more thorough retrieval of related data sets)

Name authority control example  See CCQ article on name authority control… perhaps provide screen capture example, per Ryan’s suggestion

May 21-22, 2009, Dryad Management Board Meeting Quality Control  Developing a curation / metadata generation workflow that meets (or exceeds) Dryad’s functional requirements  Completeness  Accuracy  Provenance  Conformance to user expectations  Logical consistency & coherence  Timeliness  accessibility (Bruce and Hillmann, 2004) 7

May 21-22, 2009, Dryad Management Board Meeting Completeness (example)  A complete metadata record, or some key fields  An incomplete metadata record, basically showing a metadata record/citation, with missing data 8

May 21-22, 2009, Dryad Management Board Meeting Accuracy (example)  An accurate metadata record, or some fields  Metadata record with errors (e.g., date in the author field) 9

Dryad’s Submission System: Curation and Quality Control 10 May 21-22, 2009, Dryad Management Board Meeting

Submission system: Curation [and QC?]  Current depositor curatorial tasks include –XXXX or show example/screen capture –E.g., writing out name; filling in X metadata fields  Planned professional curatorial tasks include –XXXX or show example, or screen capture –E.g., authority control for personal names and subject authority data (ontologies and other standard vocabularies)  Planned machine-driven curatorial tasks, planned –Assisting w/both name and subject authority control 11 May 21-22, 2009, Dryad Management Board Meeting

Submission system: Quality control  Not sure if we need another slide..maybe previous slide is really about both?  Ideas?? 12 May 21-22, 2009, Dryad Management Board Meeting

Dryad’s Search Interface 13 May 21-22, 2009, Dryad Management Board Meeting

Search Interface  Example/screen capture here [and next slide], but what are we wanting to demonstrate?  E.g., how quality control, curation allows for interoperability, collocation? This would be better demonstrated live.  Would we want to show NSDL, and icons? 14 May 21-22, 2009, Dryad Management Board Meeting

Summary Points, Questions and Discussion 15 May 21-22, 2009, Dryad Management Board Meeting

Summary points  Curation and quality control have a cost  The Dryad development team is aiming to automate as much of the curation and quality control activities as possible, but this takes time –E.g., Helping Interdisciplinary Vocabulary Engineering (HIVE) project  Machines are more consistent and expedient, but humans are superior in conducting certain curatorial tasks  An overriding goal is to reduce depositor curatorial responsibility 16 May 21-22, 2009, Dryad Management Board Meeting

Questions and discussion  What to you see as the biggest curatorial and data quality challenges?  How can we effectively engage depositors in curatorial tasks? (How can we keep depositors from thinking curation it is a burden?)  Should depositors engage in quality control; and, if so, at what level –E.g., If the curator updates a metadata record, should the depositor be notified  Other?? 17 May 21-22, 2009, Dryad Management Board Meeting

Extra slides follow here.. Not sure if we will use. 18 May 21-22, 2009, Dryad Management Board Meeting

29/05/2016Titel (edit in slide master) 19 HIVE model

May 21-22, 2009, Dryad Management Board Meeting Activities impacting Dryad’s functionality Curation Collecting, preserving, archiving, and providing access to digital data  Curator—a person  Creating metadata that sufficiently describes data objects, facilitates retrieval  Creating metadata in a cost- effective manner  Working with trustworthy information standards (metadata standards, vocabularies) Quality Control  Developing a curation / metadata generation workflow that meets (or exceeds) Dryad’s functional requirements  completeness  accuracy  provenance  conformance to user expectations  logical consistency & coherence  timeliness  Accessibility (Bruce and Hillmann, 2004) 20