;)
The ‘protection’ metadata field in IATE is used to mark which entries can be edited based on their protection status and the user’s permissions, ensuring greater control over the integrity of certain entries and the data they contain.
By default, all entries are marked as ‘not protected’, meaning that users from any institution with specific editing rights can modify them. However, Administrators can protect a language-independent level (LIL), language level (LL) or term level (TL), or apply protection via collections, and restrict who can modify the data.
Internal logged-in users can see protection labels on all protected levels in full entry view. On the results page, they can also see protection labels when protection has been applied directly to the entry (and not via a collection).
Protection strategies:
- Loose protection: only data owned by your institution is protected, but other institutions can still add additional languages or terms.
- Strict protection: all data is protected and other institutions cannot add additional languages or terms.
 Applying protection to entries owned by multiples institutions may lead to conflicts. In such cases, a warning will be displayed and you should contact the IATE Support & Development Team. |
To protect a new entry (or parts of the entry) when creating it, select ‘Protected’ in the ‘Protection’ field at the relevant level of the entry, adjusting the protection options as you see fit. Existing entries can be protected through the same field at the relevant level(s) in full entry view.
| By default, all entries are marked as ‘not protected’, meaning that users from any institution with specific editing rights can modify them. |
(*) USER GROUPS AND ACCESS RIGHTS
In the table below you can see the different IATE user groups and the corresponding protection options available to them:
| User group | Read protected metadata | Restrict protection of new entries | Restrict protection of new entries |
|---|---|---|---|
| NON-LOGGED-IN USER | No | No | No |
| EXTERNAL LOGGED-IN USER | No | No | No |
| INTERNAL LOGGED-IN USER | Yes | No | No |
| ADMINISTRATOR | Yes | Yes | Yes |