R utgers C ommunity R epository RU CORE 1 Research Data and Context Presentation Goals The challenge of context Metadata design to support context Rutgers University Libraries’ Rucore strategy
R utgers C ommunity R epository RU CORE 2 The Challenge of Context Information is Changing Fundamentally
R utgers C ommunity R epository RU CORE 3 The Challenge of Context The New Paradigm
R utgers C ommunity R epository RU CORE 4 RUcore Overview 19,000+ objects Popular collections ETDs – Theses and Dissertations (over 1700) Historic Maps (from Special Collections) Grant supported projects: New Jersey Digital Highway (IMLS) Videeo Mosaic Collaborative (NSF) Videos – NJVid Statewide Video Network; (IMLS) Special services Faculty deposit Custom portals Online submission of ETDs
R utgers C ommunity R epository RU CORE 5 RUcore Overview Robust Infrastructure Fedora Commons repository architecture Workflow Management System, for object handling and metadata supports: Full METS profile Event-based metadata for capturing data lifecycle customizable vocabularies by collection User applications Customizable portal archiecture Flexible metadata search and display by portal ETD and Faculty deposit interfaces Access control with XACML.
R utgers C ommunity R epository RU CORE 6 RUResearch – Research Data Portal Support research, collaboration, and related grants Archive and preserve/curate data Facilitate sharing and reuse of data Link all associated resources to data, from the grant documentation to rights licenses and releases to experimental documentation to publication and reuse. All with “who, what, where, when, why” context. Assist in improving data methods Promote innovation and new uses of data Context-based research space in development
R utgers C ommunity R epository RU CORE 7 Evolving Data Management Strategy Heterogeneous data characteristics and methods Shared understanding of data and workflow through data and context model Tools/services for analysis, mining, & visualization Team based approach for Rutgers Data Management Leverage strengths of the Library New roles for liaisons Intensive in-house training to create holistic knowledge base for all
R utgers C ommunity R epository RU CORE 8 PROJECT Experiment Trial DataAnalysis Data Collection Hierarchy Associated objects: Design documents; Grant proposal; Hypothesis; Methodology; Grant award; IRB protocol; Research Data Lifecycle Publication Associated objects: Field notes Lab notes Data corrections Instrument calibrations Associated objects: Code book Software Article, dissertation, etc.
R utgers C ommunity R epository RU CORE 9 Context Starts with Relationship Project Data hasMember/ isMemberOf Documents Software Numeric Data Survey Interview Numeric Data Supp. Materials hasMember/ isMemberOf hasPart/ isPartOf hasPart/ isPartOf Relationships External to Object Dissertation in Ruetd; Article in RUcore (or elsewhere) Fedora “rels ext” RDF statements linked to MODS related item elements
R utgers C ommunity R epository RU CORE 10 Metadata Capturing Data Characteristics Physical Format (audio, video, excel, SPSS, etc.) Date Location Sample type (specimen, sensor data, survey data, etc.) Data collection method (observation, culturing, survey, etc.) Sampling methodology Survey methodology Status (raw, normalized, corrected) Edition RU Data Survey and research profiles Research Metadata Copyright, ownership, and policies A Research Repository (to complement the Archive)
R utgers C ommunity R epository RU CORE 11 Context of Data Creation Project Name Project structure (Experiments, trials, etc.) Provenance of research Grant award Hypotheses, etc. IRB protocol Provenance and relationship of resources
R utgers C ommunity R epository RU CORE 12 Context of Data Use Copyright and ownership / restrictions on reuse License, publicity releases, etc. Publications resulting from research Articles, dissertations, in other collections or external Data Analysis / analytics (GIS maps, Ruanalytic, etc.) New data editions Context is captured through RDF relationship statements (linking) and event metadata in each METS document (descriptive, source, rights, etc.) to add circumstances of relationship.
R utgers C ommunity R epository RU CORE 13 Data Data-centric View Is analyzed in Analysis event Publication event Is published in Is created in Project Creation event e.g., Experiment e.g., Trial Events: Situate each lifecycle event in place and time, with associated objects and agents. Events can be displayed or not in different portals Data is disambiguated from its context for more efficient reuse. But the context is always there to be retrieved, No limit to the number and type of events that can be added.
R utgers C ommunity R epository RU CORE 14 RUResearch Today Metadata specific to the research process Relationships and events to capture research context Customized portals for research projects as well as central portal Preservation, curation, digitization and storage facilities
R utgers C ommunity R epository RU CORE 15 RUResearch Today Project Portals Faculty member selects metadata elements for search and browse Faculty member selects metadata elements (including events) for display Working documents (e.g., IRB protocol, participant releases, etc.) can remain private All relevant ancillary documents are available with the resource. All necessary software applications are maintained up to date and launched as needed. Publications resulting from research are linked and displayed in metadata
R utgers C ommunity R epository RU CORE 16 RUResearch Portal
R utgers C ommunity R epository RU CORE 17 Events showing Lifecycle / Context
R utgers C ommunity R epository RU CORE 18 Custom Portals
R utgers C ommunity R epository RU CORE 19 Equine Science Center Videos
R utgers C ommunity R epository RU CORE 20
R utgers C ommunity R epository RU CORE 21
R utgers C ommunity R epository RU CORE 22
R utgers C ommunity R epository RU CORE 23 OpenWMS
R utgers C ommunity R epository RU CORE 24 OpenWMS
R utgers C ommunity R epository RU CORE 25 OpenWMS
R utgers C ommunity R epository RU CORE 26 OpenWMS
R utgers C ommunity R epository RU CORE 27 Conference Proceedings
EXHIBITIONS SERVICE / PORTAL
R utgers C ommunity R epository RU CORE 29 EXHIBITIONS SERVICE / PORTAL
R utgers C ommunity R epository RU CORE 30 Event metadata triggers Functionality (display order, etc.) Remains with object as lifecycle use event
R utgers C ommunity R epository RU CORE 31
R utgers C ommunity R epository RU CORE 32 RUResearch Tomorrow User friendly submission portal in development Set up of project / data collection hierarchy Manual and automatic upload of data to appropriate place in hierarchy (“folder”) Create project records and events and upload relevant documents (grant award, grant report, IRB protocol, etc.) Ability to review all data and documents according to project structure set up by faculty member / RUcore data administrator. ETA – Winter 2012
R utgers C ommunity R epository RU CORE 33 Context Resource Map: Relationship plus Event-based context
R utgers C ommunity R epository RU CORE 34 RUCore Future – Context-based workspace and public space Researcher files data sets, documents, etc. under relevant event folders. Researcher decides if file is private, shared with specific users or public Users see resources that are made open by researcher ResearcherUser Shared understanding Dynamic Context driven