1. Redesigning the DOE Data Explorer to embed dataset relationships at the point of search and to reflect landing page organization
Sara Studwell
Department of Energy, office of scientific and technical information

2. DOE’s Office of Scientific and Technical Information (OSTI)
DOE Data Explorer
DOE Data ID Service
The DOE Data Explorer (DDE) launched in June as a tool to help users discover the many collections of publicly available, DOE-sponsored data and other non-text information.
DDE is an information tool to help you locate DOE's collections of scientific research data and also retrieve individual datasets submitted by data centers, repositories, and other organizations within the Department.
OSTI became DataCite member in 2011 – Allows OSTI to assign digital object identifiers (DOIs) to datasets.
DataCite – An international organization supports data visibility, ease of data citation in scholarly publications, data preservation and future re-use, and data access and retrievability by assigning DOIs to datasets.
DOE Data ID Service – OSTI provides service of assigning DOIs to datasets free for DOE-funded research. Will provide the service to other federal agencies through cost recovery model.

3. Technical infrastructure

4. Background
DDE began with records created by OSTI of data collections found on the Web.
Implementation of DOE Data ID Service allowed “data clients” to submit metadata for individual datasets and receive DOIs to promote data citation.
Two product types: 1) Data Collections (no DOI), 2) and Datasets (assigned DOI), became available in DDE.
Some dataset records stemmed from data collections, but were not cross-referenced. Opportunity for linkages!
Materials Project at Berkeley volunteered to pilot, desiring to create collections of DOIs to facilitate Materials Project data citation.
Realized a third product type would be needed—a specialized collection record with an associated DOI.

5. Opportunity
Huge quantities of scientific data
Lack of meaningful organization
How can we create linkages among data to make it contextual and useful?

6. Phase I
The Re-envisioning and implementation of the new DDE organizational Structure

7. DDE Gains a Product Type
Two product types did not sufficiently characterize the hierarchical relationships, so a third was added:
Project: A data Project is the top tier, representing a collection of data from a specific research group, data center, user facility, or other DOE-funded endeavor. (Note: ongoing discussions with our various communities may change the name to better represent this data product type.)
Collection: A data Collection is now a package of related Datasets as described by the data client and assigned a DOI.
Dataset: a Dataset is a single instance of data whose boundaries have been defined by the data client and assigned a DOI.
With the addition of the Project record type, data clients, creators, owners, and curators can more logically organize their data within DDE, allowing them to present their data in a contextually relevant manner.

8. Visually representing the new organizational structure
Toggle between Projects, Collections, and Datasets using tabs at the top of the results list.
Under each Project result is the number of associated Collections and Datasets.
Refine results by specific organization or group producing data or by data creator.

9. Search and navigation using the new relations
Can toggle among the Project and associated Collections and Datasets by tabs or hyperlinks.
Includes:
List of related Projects, Collections, or Datasets
List of scholarly works that cite the Collection or Dataset
Chart and image gallery

10. Technical infrastructure

11. Phase II
Collaborating with clients to create more robust associations

12. Using landing pages as guides for organizing data in DDE
Materials Project: Forming parent/child relationships through bundling DOIs—these can be used to create a relational framework between individual Datasets and overarching Collections in DDE.
Atmospheric Radiation Measurement Archive (ARM): Created relationships between the DOI of the instrument’s datastream and the unique citations generated each time slices of the data are obtained. Collection records for each instrument could be created, and the datastreams for each instrument could become dataset records with individual DOIs.
DOE Geothermal Data Repository (GDR): Provides links to related datasets on its dataset landing pages—these existing associations could be leveraged to group related datasets into DDE Collection records

13. Additional areas for exploration
Other clients are focusing on tying a digital knot between datasets, publications, and related research objects such as software. How can we start to better interlink data, software, and publications to provide a more comprehensive research environment?
OSTI is moving towards this ‘unified user environment’ in SciTech Connect.
How do we create additional hierarchical associations such as “lab rollups,” associating user facilities (like Argonne National Lab-Advanced Photon Source) to the overarching lab (Argonne National Lab) so that a user can find data related to an instrument instead of an individual project?
Some data can logically be related to more than one Project. How can we address these linkages and expose them in DDE?

14. Thank you. Questions?