Library Main Navigation:     Ecosystem Use Case Library Home   |  User Stories   |   Use Cases   |   Efforts   |   Library Help

E1: Data Repository Finder

The Data Repository Finder is an open-access, web-based tool that helps NICHD researchers find data repositories where they can share data as they develop and implement their NIH Data Management and Sharing Plans. Repositories are added on an ongoing basis.

> Live in Beta. Visit the website at https://data-repository-finder.ll.mit.edu*

*External link, NIH is not responsible for content of external sites

Table of Contents

• Effort Overview: high-level details and contact information
• Effort Documentation: details the scope of the effort, including:
  • Use Cases Diagram - use cases for the E1-Data Repository Finder effort and their relationships
  • Use Cases and Origin User Stories - overview of each use case, related actors, and their goals
  • Documentation Files - files that can be downloaded for this project.

Effort Overview

Recognizing the need for researchers to find and use data repositories that address their specific data needs, NICHD developed a tool to display information researchers need to complete their Data Management and Sharing Plans when applying for NICHD funding. Information is manually extracted from the websites of repositories identified by NICHD's Office of Data Science and Sharing (ODSS) and includes details such as what data access tiers the repository supports and data submission requirements.

Primary contact: Data-Repository-Finder-Support@ll.mit.edu

Details:

• Built by: MIT Lincoln Laboratory in REACT
  
• Hosted by: MIT Lincoln Laboratory in their public AWS cloud environment
  
• Sponsor contact: Dr. Rebecca Rosen, Director of NICHD ODSS

Effort Documentation

Use Cases Diagram

Use cases diagrams are a standard Unified Modeling Language (UML)* structure which summarizes the details of a system's users (called Actors) and their interactions with the system (called Use Cases). Multiple use cases detailed together in a use cases diagram are used to define the scope of an effort. Our use cases reference UML best practices informed by User-Centered Design*.

*External link, NIH is not responsible for content of external sites

Actors can map to multiple users from User Stories, as they represent users who may have different titles within an organization but have similar goals or requirements within an Effort.

Text description of the Use Cases Diagram

The Data Repository Finder has three primary actors: A repository Subject Matter Expert (SME), a Repository Publisher, and a Repository Searcher. For a Repository Searcher, the main use case is to identify a repository, which includes selecting a repository. For a Repository SME, the main use case is to add a repository, which includes editing a repository, and selecting a repository. For a Repository Publisher, the main use case is to publish a repository, which includes editing a repository, and selecting a repository. Viewing provenance extends editing and publishing a repository, and includes selecting a repository.

Use Cases and Origin User Stories

UC#	Use Case	Actors	User Story
UC1.1	Add repository	Repository SME	(enabling functionality)
UC1.2	Publish repository	Repository Publisher	(enabling functionality)
UC1.3	Edit Repository	Repository SME, Repository Publisher	S3: As NICHD staff, I want to be able to update a given field in the Data Repository Finder and track the date and reason for the change, so that I can go back later and review why that decisions was made
UC1.4	View Provenance	Repository Publisher	S3: As NICHD staff, I want to be able to update a given field in the Data Repository Finder and track the date and reason for the change, so that I can go back later and review why that decisions was made
UC1.5	Identify Repository	Repository Searcher	S30: As an NICHD researcher, I want to find the best data repositories for the sharing scientific data that I am generating in my project and understand the repository 's submission and sharing practices so I can complete my Data Management and Sharing Plan S31: As an NICHD program officer, I want to verify that researchers are using data repositories appropriate for the scientific data they plan to share and that their DMS Plan is consistent with the repository's expectations and requirements.

Use Case Actors, Goals, and Related Users from User Stories

Actors	Actor Goal	Related Users
Repository SME	Subject Matter Expert (SME) goal is to ensure their repository is listed, findable, and represented accurately	NICHD Staff, Other
Repository Publisher	Publisher goal is to ensure the information entered for a given repository matches display intent and meets/exceeds quality checks before the public can see the information	NICHD Staff, Other
Repository Searcher	Searcher goal is to find a data repository that matches their internal search criteria (e.g., I need a repository that handles genomic data)	NICHD Researchers, NICHD Staff, Participant Community, Other

Documentation Files

• 1_Use-Cases: Formalized documentation describing interaction requirements and Effort scope.

• 2_Supplemental: Other documentation describing Effort design and build decisions (coming soon)

• 3_Code: Effort code files (coming soon)