1 / 18

Jane Greenberg, Professor and

The Dryad Repository: A Metadata Best Practice for a Scientific Data Repository ASIST RESEARCH DATA ACCESS & PRESERVATION SUMMIT April 9-10, 2010, Phoenix, Arizona. Jane Greenberg, Professor and Director, Metadata Research Center <MRC> School of Information And Library Science

bona
Download Presentation

Jane Greenberg, Professor and

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Dryad Repository: A Metadata Best Practice for a Scientific Data RepositoryASIST RESEARCH DATA ACCESS & PRESERVATION SUMMITApril 9-10, 2010, Phoenix, Arizona Jane Greenberg, Professor and Director, Metadata Research Center <MRC>School of Information And Library Science University of North Carolina at Chapel Hill

  2. Ecology • Paleontology • Population genetics • Physiology • Systematics • Genomics • Dryad Goals • One-stop deposition/access for data objects supporting published research… • Acquisition, preservation, discovery, and reuse of heterogeneous digital datasets 2

  3. l

  4. Partner Journals • American Society of Naturalists • American Naturalist • Ecological Society of America • Ecology, Ecological Letters, Ecological Monographs, etc. • European Society for Evolutionary Biology • Journal of Evolutionary Biology • Society for Integrative and Comparative Biology • Integrative and Comparative Biology • Society for Molecular Biology and Evolution • Molecular Biology and Evolution • Society for the Study of Evolution • Evolution • Society for Systematic Biology • Systematic Biology • Commercial journals • Molecular Ecology • Molecular Phylogenetics and Evolution

  5. Developing a Metadata Best PracticeMETADATA, from the onset, and important part of DryadNot let legacy practice hold us back • Dyrad’s functional requirements: • Support resource discovery and use; data interoperability; computer-aided metadata generation, augmentation, and quality control; linking publications and underlying datasets; and data security (Dube et al, 2006, White et al 2008) • Dryad’s high-level metadata requirements • Simple:depositor created metadata; automation of metadata gen; discovery of heterogeneous datasets • Interoperable: harvesting, cross-system searching • Semantic Web Compatible: sustainable and adaptable metadata architecture, supporting machine processing

  6. Dryad’s Metadata Best Practice • Digital data repositories ought to support immediate operational needs and long term goals to be sustainable. ~ a two-pronged approach • Sustainable in the evolving information environment (DCAM application profile) • Immediate need to make content available in Dspace (XML schema)

  7. A hierarchy of goals Synthesis Sharing Discovery Preservation

  8. Dryad metadata application profile

  9. Singapore Framework (machine processing, long term quality control Semantic web/linked data) • A loose standard for DC endorsed application profiles

  10. Singapore Framework http://dublincore.org/documents/singapore-framework/ Stuff we do any how…just better! ( JLM paper) • A “loose” standard for Dublin Core “endorsed” application profiles • Singapore framework provides guidelines for creating a DCAM-conformant Application Profile (“DC Application Profile”) • A packet of documentation which consists of: • Functional requirements (desirable) • Domain model (mandatory) • Description Set Profile (DSP) (mandatory) • Usage guidelines (optional) • Encoding syntax guidelines (optional)

  11. Potential for metadata and …data reuse in different contexts Description Set Profile Toward the Semantic Web… linked data…. • DSP is “an information model and XML expression” (http://www.unc.edu/~scarrier/dryad/DSPLevelOneAppProfDraft.xml) • Obligation (optional, mandatory) • Non-literal (thing – philosophically – things in the real world, known in different ways) • http://purl.org/dc/elements/1.1/rights (mandatory), there are different rights • Subject, creator, description… • Literals (strings): • http://purl.org/dc/elements/1.1/identifier = http://purl.org/dc/terms/URI, • http://purl.org/dc/terms/available = http://purl.org/dc/terms/W3CDTF 12

  12. Helping Interdisciplinary Vocabulary Engineering (HIVE) • <AMG> approach for integrating discipline CVs • Model addressing C V cost, interoperability, and usability • constraints (interdisciplinary environment) • Building, Sharing, Evaluation the HIVE…. 26/07/2014 Titel (edit in slide master) 13

  13. Reality… • Dryad development—reversed engineered long-term goals first did not have to hit the ground running • Commencement of data exchange plans DCAP work refocus  XML schema • Harvesting EML records from LTER Network’s Metacat • Data exchange plans Dryad  TreeBASE • Discouraged …approaches not at odds • App. profile work instrumental in creating a sufficient XML schema • Renderings of the same intellectual work on a continuum • GRDDL (Gleaning Resource Descriptions from Dialects of Languages) – enabling technology to create RDF

  14. Application profile work, thoughts…to date… • Positive aspects • Intellectually engaging • Think we are making a contribution, have to start somewhere… • Machine capabilities • eScience/data synthesis • Challenges • Infrastructure not all there… (a lot is not in RDF) • Registered Dryad “purl” • Proof of concept difficult • Time consuming • Documentation lacking

  15. DCAP Semantic Web ~ linked data… XML Scheme Conclusions: • Dryad development team has discovered that a two prong hybrid philosophy works well in this environment, keeps legacy practices from impeding development • A bridge… • Development has been consensus driven • biologists, computer scientists, librarians • New models need to be explored • No exploration, no discovery… unsuccessful results are Not always BAD

  16. Dryad Team • NESCEnt • Hilmar LappAssistant Director for Informatics • Ryan ScherleData Repository Architect • Todd Vision, Associate Director of Informatics • UNC/SILS/MRC • Jane Greenberg, Professor • Lina Huang, MSIS Student, Research Assistant • Robert M. Losee, Professor • Jose R. Pérez-Agüera, Clinical Assistant Professor • Hollie White, Metadata Research Center Doctoral Fellow • Collaborators • North Carolina State University • University of New Mexico/LTER • Yale University • Partner journals and societies HIVE Advisory Board • Jim Balhoff, NESCent • Libby Dechman, LCSH • Mike Frame, USGS • Alistair Miles, CCLRC Rutherford Appleton Laboratory • William Moen, University of North Texas • Eva Méndez Rodríguez, University Carlos III of Madrid • Joseph Shubitowski, Getty Research Institute • Ed Summers, LCSH • Barbara Tillett, Library of Congress • Kathy Wisser, UNC Chapel Hill • Lisa Zolly, USGS Vocabulary Partners • Library of Congress: LCSH • the Getty Research Institute (GRI): TGN (Thesaurus of Geographic Names ) • United States Geological Survey (USGS): NBII Thesaurus

  17. For Information • Dryad • http://datadryad.org/ • Dryad Wiki • https://www.nescent.org/wg_digitaldata/Main_Page • Includes links to publications, the application profile, and lists Dryad team members • Metadata Research Center <MRC> • http://www.ils.unc.edu/mrc/ • National Evolutionary Synthesis Center (NESCent) • http://www.nescent.org/index.php The Dryad Data Repository 26/07/2014 18

More Related