Read only taxonomy field
We need to, via API, create a bespoke unique identifier for each newly created asset and store that in the taxonomy. Once entered in the taxonomy the value should not be editable. This ensures that published assets, especially printed ones, can always be identified by this field.
-
Richard Jones
commented
We have other fields which were migrated as part of our on boarding - which we want to keep as a record but do not want people to be able to edit. In out case these fields are links to assets contained in RICH_TEXT fields, we will be using Related Assets going forward, so don not want people maintaining or changing these fields.
-
Ian Saltwell
commented
All types to fields need to be configurable as read only, and sometimes rich_text fields are used for URLs dropdowns and labels for filterability and text fields for simple references.
-
Brian Macdonell
commented
The default asset GUID is not user friendly, that's why we need to do the workaround using an API in the first place.
It needs to be treated the same way as the GUID would be - i.e. non editable and persisting through all versions of the same asset.