Create an SOP for Reactome model updates at every Reactome Release

[ukemi]

1. For updates that occur to GO-CAM models based on standard GOC maintenance practices, those updates will be done on an ongoing basis with each GO-CAM maintenance windows. For example, automatic replacement of ontology classes that have been obsoleted and contain a replaced-by tag will be changed as part of the regular updates.
2. If GOC generated changes to models impinge upon the import algorithm, a ticket will be made immediately to make the algorithm consistent with the change, for example changes to relationships.
3. Requests for import changes will be made as soon as possible after a GO-CAM release so that changes and testing can take place. These request should be opened as separate tickets and included in a task list for the next release.
4. A straw-man schedule for standard release is as follows:

• X days before Reactome data freeze- BioPax available for test load into Noctua-dev
• X days before Reactome data freeze- Load Biopax into noctua-dev
• X days before Reactome data freeze- Run Shex QC and Logical error QC on GO-CAMS in noctua-dev.
• X days before Reactome data freeze- Fix logical and QC errors at Reactome.
• X days before Reactome release- QC changes that have been added to the GOC conversion/import code. Can occur after data freeze, but must be complete before GO-CAM release.
• X days before Reactome data freeze- Regenerate BioPax
• X days before Reactome data freeze- Rerun BioPax load into Noctua dev
• X days before Reactome data freeze- Rerun Shex and logical checks- should be clean. If not, return to 4.
• X days before Reactome release- Fix any issues with the GOC conversion code and rerun load and checks. Must be done before GO-CAM release.
• Reactome Data freeze
• Reactome Release
• First GOC maintenance outage after Reactome release- Load Reactome Release BioPax into Noctua prod
• GO-CAM model release