Update labels and help for vocabulary policies

Rename

• Creation Policy => Table Creation Policy
• Don't override existing values => If not existing

• Data loading policy => Duplicate entries policy
  • Studio wins
  • Instance wins
  • Throw an error

Update contextual help for table creation policy

Defines when the underlying database table is created.

• "never": table is never created. Useful when a third party tool will populate it.
• "always": table is dropped and recreated each time the Nuxeo Server instance restarts. Modifications made directly in the instance are lost in the process. Useful during development phase.
• "If not existing": table is created if not existing, then only updated if additional fields need to be added in the database. Recommended for production.

[Learn more](https://doc.nuxeo.com/studio/vocabularies/?utm_source=studio&utm_medium=vocabularies-contextual-help in a new tab)

Add contextual help for duplicate entries policy

Defines which entry will take priority when a conflict happens.

• "Studio wins": Studio configuration overrides any change made in the instance
• "Instance wins": Changes made in the instance are chosen over Studio configuration values
• "Thrown an error": A log entry is created so you can resolve the conflict manually

[Learn more](https://doc.nuxeo.com/studio/vocabularies/?utm_source=studio&utm_medium=vocabularies-contextual-help in a new tab)

Also, when migrating from a previous target platform with a table creation policy set to "If not existing", the default value for the "Duplicate entries policy" must be "Instance wins".