...
| Page Properties | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
RessourcesRemarks
|
| Excerpt |
|---|
| This tutorial shows how we can use a Java application to make a request to the Core API of the yuuvis® API system to retrieve the history entries of a DMS document. In addition, it briefly describes which history entries are generated for a document. |
...
For the various actions, such as import, retrieve, update, and deletion of a DMS document, there are the following history entries:
Import:
- CREATEOBJECT_METADATACREATED
- CREATEOBJECT_METADATACREATED_WITH_CONTENT
The difference between these two types of import is that the first type imports only metadata and the second type imports metadata and content simultaneously.
Retrieve:
- GETDOCUMENT_CONTENTACCESSEDGET
- METADATA_METADATAACCESSED
- GETRENDITION_PDF_RENDITIONACCESSED
Each of these types distinguishes between retrieving only metadata, content, or the PDF rendition of the content of a document.
Update:
- UPDATEOBJECT_METADATA_CHANGEDUPDATE
- OBJECT_DOCUMENT_CONTENTCHANGED
Here, a distinction is made between updating the metadata and the content of a document.
Delete:
- DELETE
- MARKEDOBJECT_DELETED
- OBJECT_FLAGGED_FOR_DELETIONDELETE
If a deletion action is triggered, the document to be deleted is first marked as deleted in Elasticsearch so that it can no longer be found. Only then are metadata and content actually deleted, and a corresponding entry is made in the history of the document.
...