Pilot should have a "no ontology modifications" mode

[pmills]

I’ve been testing Pilot recently.

Rather than use the existing properties on the ontology objects provided as inputs, it will often make up new properties that it thinks better suit the app you’re trying to build.

This is quite an insideous problem as unless you know the ontology intimately, these can look like valid properties and so get merged in as changes along with other valid modifications.

This creates duplicated and “dead” properties.

Can there be an option to limit Pilot to building using only existing object properties, links and action types? This would make it much safer to iterate on modules when an incumbent ontology already exists.

[bwisnicki]

Hi there,

Pilot now supports Ontology modification permissions where you can limit Pilot’s ability to create and/or edit ontology entities.

You can enable it for new Pilot projects in the bootstrap form under ‘Ontology permissions’.

For existing apps, navigate to the Ontology page, and you can select the ‘Ontology permissions’ in the top right.

You can also add granular permissions to certain object and action types to prevent Pilot from making proposals on specific existing entities.

Thanks!