Page Properties | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
Resources & Remarks https://wiki.optimal-systems.de/pages/viewpage.action?pageId=57442949
Modification History
|
Excerpt |
---|
The basic idea for the usage of tags is to describe the state of an object within a process chain. They consist basically of a name and a state value and can be assigned to any object. |
Section | ||||||
---|---|---|---|---|---|---|
| ||||||
|
...
- Tags do NOT belong to the metadata and thus do not need to be defined in the schema.
- Tags are stored together with the object as value for the property 'system:tags' similar to metadata.
- Pure tag operations do NOT lead to the creation of a new object version.
- Tags can only be attached to the current version of an object, whereas previous versions cannot have tags.
- For version-specific information, metadata provide the suitable options. They have to be defined in the schema.
...
- Retrieve object tags by ID – GET GET /api/dms/objects/{objectId}/tags
- Add object tag by ID – POST POST /api/dms/objects/{objectId}/tags/{name}/state/{state}
- Update object tag by ID – POST POST /api/dms/objects/{objectId}/tags/{name}/state/{state}?overwrite=true
- Delete object tag by ID – DELETE DELETE /api/dms/objects/{objectId}/tags/{name}
- Add/update object tag by search query – POST POST /api/dms/objects/tags/{name}/state/{state}?query=<SQL>
Anchor ResistantTags ResistantTags
...