Coordinate the creation of backlog items for each deliverable (need not be "ready" yet)

[mreekie]

Work with the devs who were part of the problem statement creation to get the corresponding backlog issues into the backlog. Use label: bk2211

Context:

---

• 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
• NetCDF

---

Defintion of done:

• Problem statement is defined in it's description
  • e.g. of problem statement 4 | 1.4.1 | Resolve OAI-PMH harvesting issues | 5#9036
• Problem statement issue is in the "No Backlog Status Column"
  • e.g. see: https://github.com/orgs/IQSS/projects/32/views/7
• Initial issues are associated with the deliverable
• Initial issues are in the global backlog

---

Each issue has:
Title
Objective
Context or background section
Definition of done.

• How do you know when this issue is ready for review?
  Acceptance criteria
• Notes on testing and expected outcomes for review and QA

[mreekie]

Using this the backlog is another new thing so I don't expect today to go smooth.
What could help us bootstrap for this sprint is if the caretakers could propose 1 issues each in the "Proposed Next" column.
You don't need to. Nothing bad happens if you dont, but it would be helpful.

Today's prio meeting is not going to be "clean".
This will be the first time that Stefano will see it during a prio meeting.
I know that he wants to get the NIH deliverables going.

Here is what we have going in:
2 white paper issues, one of which has a placeholder issue. I'll add the other
The existing issue Phil added,
Phil Don't forget to add the new issue you raised today.
The harvesting backlog that was created. (I'll move these over under NIH)
We also have what's not finished yet on the board.
For today I won't reflect that on the backlog but maybe there is automation we can take advantage of here?

[mreekie]

I'm taking this off the board.
It's too broad.
Instead specific sidecar issues will be put on the board and worked as part of the sprint.