Propose edits to ontology - What pattern to use?

Ask the Community
,
1

I would like my users to be able to propose edits to the ontology.
I don’t want them to edit the ontology right away. I kind of want to stage the changes and then someone to approve those edits.

I could double up the number of object types I have, but that’s a bit tedious.
Also, it means that if 2 concurrents edits happen at the same time, I would most likely loose one of the edits (how would I know which properties to pull from which edit ?).

Any idea/way to do this in a better way ?

2

Hi @VincentF ,

There are two ways you can do this. The first one is available today but will be outdated once the second option becomes available.

(1) Using ontology roles and ontology proposals. You can make all of your users “Viewers” on the ontology resources. This will mean that they will have to go through an ontology proposal to make modifications to the ontology. In terms of approvals, a change to an ontology resource can be approved by anyone with editor permissions.

(2) Using Foundry branching and project-level resource protection. We will be introducing project-level approval policies, and resource-level protection statuses. This means that if you mark a resource as “protected”, any changes to this resource will have to go through a branch, and will have to be approved according to the approval policy that is set at the project level. An example of an approval policy can be “require at least 2 approvals from {multipass group} AND do not allow self-approval”.

The second option is currently under development.

3

Thanks for the precise answer about Object type !

Sorry, I was unclear: I meant proposals on objects instances.

Aka, for example, I have a “Cars” Object Type, and a “car 1” object instance belonging to this object type. A user needs to propose we make a change to “car 1” (e.g. change the color).
This kind of change cannot be “staged”, so I would need to create a second “Cars (proposal)” Object Type, and let the user fill properties, and then write a function which I’ll need to maintain to “map” the proposal’s properties to the real ones.