When a class (value) is created in CEDAR, it produces a provisional class in BioPortal (in the CEDARPC ontology). But nothing happens after that to encourage turning the provisional class into an ontology.
Enable functionality that will let users find, view, and edit existing provisional classes, including the ability to manage their disposition (either by accepting the proposed class in the proposed ontology (and therefore deprecating the provision class in deference to the actual class), suggesting it for another ontology, or refusing to accept it and therefore deprecating it. A standard pattern should be followed for deprecating and forward-linking provisional classes.
In time this may provide the option to notify (directly or through BioPortal, Ontolobridge, or other system) the owner of the ontology that the provisional class has been recommended, and even to track the status of the request.
When a class (value) is created in CEDAR, it produces a provisional class in BioPortal (in the CEDARPC ontology). But nothing happens after that to encourage turning the provisional class into an ontology.
Enable functionality that will let users find, view, and edit existing provisional classes, including the ability to manage their disposition (either by accepting the proposed class in the proposed ontology (and therefore deprecating the provision class in deference to the actual class), suggesting it for another ontology, or refusing to accept it and therefore deprecating it. A standard pattern should be followed for deprecating and forward-linking provisional classes.
In time this may provide the option to notify (directly or through BioPortal, Ontolobridge, or other system) the owner of the ontology that the provisional class has been recommended, and even to track the status of the request.
Some existing tickets that are related: https://github.com/issues/metadatacenter/cedar-terminology-server/24 https://github.com/issues/metadatacenter/cedar-terminology-server/14