2024-09-12

[kltm]

• Send reminder email to go-consortium mailing list
• Run noctua-models-migration pipeline for (@vanaukenk) (automated to day before) to get report
  http://skyhook.berkeleybop.org/noctua-models-migrations/reports/
• Refresh minerva code with latest from minerva master
• Run replaced_by term update on blazegraph (@vanaukenk)
• Cycle minerva to get latest ontology
• Follow instructions below to update noctua SAF
• Update NEO
• Prep ticket for next outage

[kltm]

@balhoff to add instructions for migration discussed on slack.

[dustine32]

@kltm Forgot to ask this yesterday. Can we schedule the pull of the Alliance pathway preview workbench changes (basically the changes in geneontology/noctua-alliance-pathway-preview#15; a PR into master will be made by @tmushayahama) into Noctua prod?

[kltm]

@dustine32 @tmushayahama It should all be fine as we can always roll back. Just add necessary instructions to the list above and merge any PRs that are necessary.

[kltm]

@vanaukenk migrations run, diff available.

[kltm]

Note to @vanaukenk : in preparation, I'm running the commands up through the failure from last time around to see if it happens again. I'll report here if it does.

[vanaukenk]

Extra large diff file this time, but all changes are consistent with recent ontology updates wrt enzymatic activities, transporter activities, and GPI-related BP terms.

Also noting that in one case, a term merge will result in two identical annotations. I'm not sure we've encountered this before, so I'll put a ticket in the noctua tracker as a placeholder to discuss and investigate what we want to do about those annotations.
#917

[tmushayahama]

register noctua-standard-annotations inside noctua startup yaml

git pull origin noctua-landing-page master branch

cd noctua-standard-annotations
git pull origin noctua-standard-annotations
git checkout main

[kltm]

As a note from @tmushayahama during the meeting, the workbench addition can be added anywhere, so I will add it to the bottom of the list.