use tagged version of nmdc-ontology

[aclum]

Placeholder for updating to a tagged release version of nmdc-ontology. Changes in main in nmdc-ontology recently broke data portal ingest (b/c of Cyclic graph) so this is a good time to update it.

Realvant code

nmdc-server/nmdc_server/ingest/envo.py

Line 16 in f6bfe8f

envo_url = "https://raw.githubusercontent.com/microbiomedata/nmdc-ontology/main/nmdco-classes.json"

[aclum]

cc @turbomam let us know when you have a tagged nmdc-ontology release that resolves the cyclical graph issue.

[turbomam]

https://raw.githubusercontent.com/microbiomedata/nmdc-ontology/2024-02-16/nmdco-classes.json

[ssarrafan]

@aclum should this be in the current sprint? Who owns this issue?

[ssarrafan]

@mbthornton-lbl @naglepuff is this something you are currently working on?

[aclum]

This should be a ticket for Mike or Mary

…

On Wednesday, April 3, 2024, ssarrafan ***@***.***> wrote: @mbthornton-lbl <https://github.com/mbthornton-lbl> @naglepuff <https://github.com/naglepuff> is this something you are currently working on? — Reply to this email directly, view it on GitHub <#1183 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB6RD36RZNQGH7HX2NYTNIDY3RZSZAVCNFSM6AAAAABEW6I4O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVGY2TAMJXGQ> . You are receiving this because you were assigned.Message ID: ***@***.***>

[aclum]

It should be a straightforward swap so seemed okay to have in this sprint. If not, next sprint is fine too.

…

On Wednesday, April 3, 2024, ssarrafan ***@***.***> wrote: @mbthornton-lbl <https://github.com/mbthornton-lbl> @naglepuff <https://github.com/naglepuff> is this something you are currently working on? — Reply to this email directly, view it on GitHub <#1183 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB6RD36RZNQGH7HX2NYTNIDY3RZSZAVCNFSM6AAAAABEW6I4O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVGY2TAMJXGQ> . You are receiving this because you were assigned.Message ID: ***@***.***>

[ssarrafan]

@naglepuff @marySalvi I'm assigning this to you in case one of you has time to do this week.

[ssarrafan]

@marySalvi said she is looking into this one. I'll remove Mike from this ticket.

[marySalvi]

@turbomam @aclum Do we want to always use the latest release or do we want to 'pin' to a specific release? Pinning would require manual updating but potentially less friction for testing different releases

[turbomam]

I defer to @aclum

I am doing active development in the main branch. I'm pretty careful about what I merge, but I haven't been doing an ingest each time. So a pinned release would be safer.

[aclum]

The request is for a pinned release. We haven't been doing this and it broke ingest a few weeks ago. The nmdc-server code and therefore ingest will be more stable. I'd like updating the pinned version to be part of the monthly release cycle. That is, if Mark has a new version there would be a nmdc-server ticket to update the nmdc-ontology version, ideally at least a week before the monthly production release so we could test ingest and the data portal interface on dev. cc @shreddd @pkalita-lbl