Aim 2.3.3 Term Maturity levels, public opinion period, and conflict resolution

monarch-initiative / phenomics_first_resource

Project Management repository for anything in and around the Phenomics First Resource (PFR)

0 stars 0 forks source link

Aim 2.3.3 Term Maturity levels, public opinion period, and conflict resolution #29

Open sagehrke opened 1 year ago

sagehrke commented 1 year ago

Term Maturity levels, public opinion period, and conflict resolution: We will define the process for community vetting of proposed terms. For example, proposed new terms will be shared with the community for their comments before promoting the terms to the next maturity level (e.g. “proposed”, “provisional”, “mature” or “obsolete.”). The goal is to garner community agreement on what will best balance currency of information delivered to clinical settings with robustness of knowledge and ease of evidence interpretation.

nicolevasilevsky commented 1 year ago

[x] formally document our current worklows to be more explicit and something we can point to on the RPPR, include examples, such as obsoletion process (give example of removing term from obsoletion candidate because someone needed it)

sabrinatoro commented 1 year ago

process for term obsoletion is in place and communicated to users:
- documentation to term obsoletion process (add link), includes
  - list of terms that are candidates to be obsoleted
  - date at which the obsoletion would be effective
  - GitHub issue where users can submit their feedback and request to not obsolete the term
release notes includes
- list of all new terms
- list of terms with updated label
- list of terms with changed definitions
- list of obsoleted terms
- list of new obsoletion candidates
vetting process by members of the community is done on GitHub issues that are visible to (and can be commented by) the community

sabrinatoro commented 1 year ago

To do (proposal):

[ ] workshops involving the community (especially experts) to discuss terms and branch review; Moni has been talking about having a Mondo, NORD, CZI workshop to teach people about Mondo and use of HPO and Mondo. The point person is @monicacecilia.

Proposed idea:

add "reviewed date" (or something similar) on terms when they are reviewed by the community (e.g. during workshops) and are vetting to remain.

Low priority

ontology branch review (priorities to be determined) (We will not prioritize branch reviews at the moment.)

nicolevasilevsky commented 1 year ago

this documentation here: https://mondo.readthedocs.io/en/latest/editors-guide/curation-workflow-overview/