Update the Runtime to work with the Berkeley schema (meta issue) 📚

[eecavanna]

note: planned "full freeze" of main branch on 2024-09-18, after which the goal is to merge berkeley into main.

---

This is a "meta issue" that represents the overall task of updating the Runtime to work with the Berkeley schema.

Terminology

• The Runtime:
  • Everything in the nmdc-runtime repository
• The Berkeley schema:
  • Version 11 of the nmdc-schema PyPI package (which is built from the berkeley-schema-fy24 repo)
• The legacy schema:
  • Versions <= 10 of the nmdc-schema PyPI package (which is built from the nmdc-schema repo)

Branches

I created a branch named berkeley that can act as our "main" branch for Berkeley-specific code.

If it turns out we can add Berkeley schema support directly to the main branch without breaking support for the legacy schema, we can delete the berkeley branch.

Constituent Tasks

When creating a GitHub Issue for a constituent task, please add a link to it to this list.

Blockers

• [x] #586 (@sujaypatil96)
• [x] #646 (@eecavanna)
• [x] #690 (@dwinston, @PeopleMakeCulture)
• [x] #689
• [x] #678 (@sujaypatil96)
• [x] #691 (@eecavanna)

Non-blockers

• [ ] #587 (@sujaypatil96)
• [ ] #588 (@sujaypatil96)
• [ ] #647 (@sujaypatil96)

Uncategorized

• [x] #519 (@eecavanna)
• [x] #582 (@eecavanna)
• [x] #578 (@eecavanna)
• [x] #580 (@aclum)
• [x] #582 (@eecavanna)
• [ ] #589 (@sujaypatil96)
• [x] #590 (@aclum)
• [x] #592 (@eecavanna)
• [x] #593 (@PeopleMakeCulture)
• [x] #594 (@eecavanna)
• [x] #595 (@dwinston & @PeopleMakeCulture @eecavanna)
• [x] #600 (@PeopleMakeCulture)
• [x] #622 (@sujaypatil96)
• [x] #626 (@eecavanna)
• [x] #628 (@PeopleMakeCulture & @dwinston)
• [x] #629 (@PeopleMakeCulture & @dwinston)
• [ ] #630 (@sujaypatil96)
• [x] #632 (@PeopleMakeCulture & @dwinston)
• [x] #636 (@eecavanna)
• [x] #638 (@eecavanna)
• [x] #649 (@eecavanna)
• [x] #653 (@dwinston)
• [x] #655 (@pkalita)
• [x] #658 (@dwinston)
• [x] #685
• [x] #683 (@aclum)
• [x] #685 (@eecavanna)
• [x] #687 (@eecavanna)

[eecavanna]

CC'ing @dwinston and @PeopleMakeCulture on this "meta issue" about updating the Runtime to work with the Berkeley Schema.

Moving to next sprint.

[eecavanna]

I expect this "meta issue" ticket to remain open for multiple sprints. I have already added it to the next sprint board, but did not remove it from the current sprint board yet.

[dwinston]

619 introduces a new test which will need to have type added to tests/files/test_changesheet_insert_study_doi.tsv in order to pass.

h/t @aclum

[eecavanna]

Someone asked me how often I expected the main branch to be merged into the berkeley branch and I realized I never announced or documented my expectation about that. My expectation was that main be merged into berkeley whenever there was something in main that people wanted to exist in berkeley, even if that happened multiple times a day. I want to keep those main-to-berkeley merges small.