Groom NIH OTA related back log Problem Statements

[mreekie]

Review problem definitions videos and firm up the problem statements in their description.

Context:

• In the last 2 weeks we met and discussed each of the 1st year nih deliverables.
• For most of the conversations, the outcomes were not recorded as the statments or in some cases recorded as new issues.

Definition of done:

• [ ] Each problem statement (e.g. 1.2.1. ) has a written problem statement based on the outcome of its problem statement meeting.
• [ ] Minimum Viable Product (MVP) for registering metadata in the repository and connecting the metadata to the data in the research computing remote storage (NESE), including Globus endpoints 15 1.1.1
• [ ] Design and implement integration with controlled vocabularies 5 1.2.1
• [ ] Define use cases for DDI-CDI support 5 1.2.2
• [ ] Support software metadata 5 1.3.1
• [ ] Resolve OAI-PMH harvesting issues 5 1.4.1
• [ ] Standardize download metrics for the Harvard Dataverse repository following Make Data Count 1.5.1
• [ ] Integrate with OpenDP tools to support differentially private statistical releases of de-identified data deposited in the repository (in collaboration with the OpenDP.org project, currently partially funded with the Sloan Foundation) 10 1.6.1
• [ ] Discovery phase to support DataTags 10 1.6.2
• [ ] Research & architecture for separating backend and frontend to enable a flexible, scalable design & development of UI modules 5 1.7.1
• [ ] Implementation of UI modules to improve the dataset landing page and access to remote data 5 1.7.2
• [x] NetCDF

[mreekie]

The pattern for these issues is:

The Description:

• I'll be maintaining the description on this.
• It will always contain a problem statement that is understandable by all on the team.
• Then It contains (ideally) measurable plans/results.
• It's less detailed than other entries.
• This summary gets updated automatically upward to a reporting tool.

The 1st Comment

• Contains the overview of the project including the broad aims.

[mreekie]

11/10

• 1.2.2 DDI-CDI - Create the problem statement is drafted from the meeting notes.
• There is follow-up required but we are not going to be moving on this immediately so those can wait until the next grooming.

[mreekie]

This issue is too big. I'm not going to update it further for this sprint. For the next sprint I will proposed individual issues.

[mreekie]

Individual issues are the way to go. I need to meet with specific people on each deliverable so this issue was the wrong way to go about it. Also this sprint, we've been focused on the process as opposed to the content. Closing this.