Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update RoleNORManager.md #2631

Merged
merged 5 commits into from
Aug 20, 2024
Merged

Update RoleNORManager.md #2631

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a6d2f79
Update RoleNORManager.md
matentzn Aug 10, 2024
8f904fd
Apply suggestions from code review
matentzn Aug 11, 2024
9715771
Update docs/roles/RoleNORManager.md
matentzn Aug 12, 2024
0c83ba1
Update docs/roles/RoleNORManager.md
matentzn Aug 19, 2024
961bcec
Merge branch 'master' into matentzn-patch-18
nlharris Aug 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion docs/roles/RoleNORManager.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ The New Ontology Request (NOR) Manager has these basic duties:
3. Supporting the New Ontology requestor to pass the OBO Dashboard
4. Assigning a provisional reviewer from the OBO Operations Committee
5. Removing the accepted ontology from the NOR Dashboard upon acceptance
6. Maintaining the OBO Duty Rotation Table

### Receiving `new ontology` requests on OBO and acknowledging the receipt

Expand Down Expand Up @@ -78,7 +79,6 @@ In addition, some checks need to be carried out manually by the NOR manager unti

- URIs: check if it includes "https" and if it [conforms with the overall format](http://obofoundry.org/id-policy) "http://purl.obolibrary.org/obo/ONTOLOGY_"


- Release artefact: check if release artefacts are identified as such and ensure that, alongside a "main release", a base release is provided which **does not include imported terms**.

- Imports: Ensure that there is a mechanism in place to update imported terms (classes and properties).
Expand All @@ -98,3 +98,10 @@ If and only if the requested ontology passes the dashboard, i.e. no more "red" e
When the ontology is accepted, the OBO NOR reviewer needs to make sure that the accepted ontology is removed from the OBO NOR Dashboard.

Note 29.11.2022: There is a [work in progress](https://github.com/OBOFoundry/obo-nor.github.io/pull/23) which can deal with this step automatically, but the responsibility still stays with the OBO NOR Manager.

### Maintaining the OBO Duty Rotation Table

The OBO Duty Rotation Table is a Google spreadsheet available [here](https://docs.google.com/spreadsheets/d/19GrEWVnpxjnrig0iYUOiUvsZ0JDbprMh1USnRb-SXtg/edit).
When a new member is added to OBO Foundry, the OBO NOR reviewer should add their name to this table. Likewise, former members should be removed from the table. The list of current OBO Foundry members is maintained in the file [operations.yml](https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/_data/operations.yml).
matentzn marked this conversation as resolved.
Show resolved Hide resolved

In addition, when a new ontology has been submitted, it should be added to the ['Ontology Reviewers' tab](https://docs.google.com/spreadsheets/d/19GrEWVnpxjnrig0iYUOiUvsZ0JDbprMh1USnRb-SXtg/edit?gid=1683009411#gid=1683009411) in the OBO Duty Rotation spreadsheet.
Loading