Update RoleNORManager.md (#2248)

* Update RoleNORManager.md

* Update docs/roles/RoleNORManager.md

* Update RoleNORManager.md

Added the requestors need to join obo-discuss and Slack.

* Update RoleNORManager.md

Valid link for new ontology submission template

Co-authored-by: Nico Matentzoglu <nicolas.matentzoglu@gmail.com>

Author: pfabry

docs/roles/RoleNORManager.md

@@ -6,17 +6,24 @@ title: New Ontology Request (NOR) Manager
 
 The New Ontology Request (NOR) Manager has these basic duties:
 
-1. Receiving `new ontology` requests on OBO and acknowledging the receipt
-2. Including the ontology in the OBO New Ontology Request (NOR) Dashboard
+1. Receiving `new ontology` requests on the OBO Foundry GitHub issues tracker and acknowledging the receipt
+2. Including the ontology in the OBO New Ontology Request (NOR) Dashboard and updating the dashboard
 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
 
 
 ### Receiving `new ontology` requests on OBO and acknowledging the receipt
 
-- The NOR Manager MUST actively listen to issues on the [OBO Issue Tracker](https://github.com/OBOFoundry/OBOFoundry.github.io/issues).
-- When a new ontology request is received, and the wrong issue template was used, the New Ontology Request (NOR) Manager must inform the NOR requestor to use the correct issue template and close the wrongly submitted issue.
+- The NOR Manager MUST actively listen to issues on the [OBOFoundry GitHub issues tracker](https://github.com/OBOFoundry/OBOFoundry.github.io/issues).
+- When a new ontology request is received, and the wrong issue template was used, the NOR Manager must inform the NOR requestor to use the correct issue template and close the wrongly submitted issue with the following message:
+    ```markdown
+    Dear @GITHUBNAME,
+    
+    Thank you for your submission. 
+    However, the wrong issue template has been used. Please make sure to follow the [New Ontology Submission Instructions](https://obofoundry.org/docs/NewOntologyRegistrationInstructions.html) and use the [New Ontology Request issue template](https://github.com/OBOFoundry/OBOFoundry.github.io/issues/new?assignees=&labels=new+ontology&template=new-ontology.yml&title=Request+for+new+ontology+%5BNAME%5D).
+    Thank you.
+    ```
 - When a valid NOR request is received the NOR Manager acknowledges the receipt with the following message:
     ```markdown
     Dear @GITHUBNAME,
@@ -38,14 +45,27 @@ The New Ontology Request (NOR) Manager has these basic duties:
 
     Good luck.
     ```
+- The NOR Manager must ensure that the requestors use the proper communication channels with the OBO community:
+    - Make sure that the requestors have joined and send an appropriate email to the obo-discuss mailing list (see the [FAQ](https://obofoundry.org/faq/how-do-i-register-my-ontology.html)). If they have not, point them to the instructions and ask them to do so.
+    - Invite the requestors (using the email listed in the metadata) to the OBO Foundry Slack space (using the `Slack->Invite people to obo-community` menu, adding the email provided.
 
-### Including the ontology into the OBO New Ontology Request (NOR) Dashboard
+### Including the ontology into the OBO New Ontology Request (NOR) Dashboard and updating the dashboard
 
 The OBO NOR Dashboard is managed here: https://github.com/OBOFoundry/obo-nor.github.io.
 
 Integrating the submitted ontology into OBO dashboard means simply adding a new record into the `ontologies->custom` subsection
-of the [dashboard config file](https://github.com/OBOFoundry/obo-nor.github.io/blob/master/dashboard-config.yml). Only information explicitly mentioned in the New Ontology Request should be used.
-- When dashboard config is updated, and every Monday morning, the OBO NOR Dashboard is regenerated using [this](https://github.com/OBOFoundry/obo-nor.github.io/blob/master/.github/workflows/dashboard.yml) GitHub action. The OBO NOR Manager should sanity check the diff for any oddities, in particular, changes to the file `dashboard/dashboard-results.yml`.  This PR should always be reviewed by the NOR Manager and not be automatically merged into the main branch as part of the GitHub action.
+of the [dashboard config file](https://github.com/OBOFoundry/obo-nor.github.io/blob/master/dashboard-config.yml). Only information explicitly mentioned in the New Ontology Request should be used.  
+NOTE: 
+> **All modifications on obo-nor.github.io repository MUST be done via pull requests and NOT via direct commits on the master branch.  
+> The /workflow/dahsboard.yml file must indicate the GitHubID of the actual NOR manager as assignee.**  
+
+Every update (adding or removing an ontology) should proceed as follows:  
+1. Creation of a Pull Request (PR) for modification of the [dashboard config file](https://github.com/OBOFoundry/obo-nor.github.io/blob/master/dashboard-config.yml) for adding or deleting record in the `ontologies->custom` section of the file.
+2. Once the previous PR is merged, it triggers the *Update dashboard run* [GitHub action](https://github.com/OBOFoundry/obo-nor.github.io/blob/master/.github/workflows/dashboard.yml). This action can also be triggered manually [here](https://github.com/OBOFoundry/obo-nor.github.io/actions/workflows/dashboard.yml) with the `run workflow` button.
+3. Once the run is complete, a new PR named `Update dashboard run` is created. Manually check the diff, especially the /dashboard/dahsboard-result.yml file for inconsistencies.
+4. Finally, merge the `Update dashboard run` PR. This PR should always be reviewed by the NOR Manager and not be automatically merged into the main branch as part of the GitHub action.
+
+In addition, the *Update dashboard run* action is automatically triggered on Monday mornings and steps 3 and 4 must be performed afterward.
 
 ### Supporting the New Ontology requestor to pass the OBO Dashboard