...
| Page Properties | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||
Resources & Remarks Modification History
|
| Excerpt |
|---|
Binary content files can be imported and assigned to document objects in yuuvis® Momentum. Archiving can be managed and renditions can be retrieved. |
...
Detailed guidelines and code examples for the individual scenarios are provided in our Example Tutorials.
Importing and Updating
The content stream properties that are available for import/update requests are described here.
>> Content Stream Properties
Binary content files can be assigned to objects in one call together with the object creation. The request has to be send with a multipart body specifying the assignments the of the binary content files to the corresponding document objects. Especially if you do not want to use the default repository, it is required to specify the target repository by its repositoryId.
>> POST /api/dms/objects
Alternatively, they can be assigned to already existing objects without a binary content file.
The same endpoint can be used to replace an existing content file. Again, if you do not want to use the default repository, it is required to specify the target repository. This is possible via X-OS-REPOSITORY-ID request header.
A new version of the entire object will be saved. The previous version of the object will be moved to the version history part of the database whereas the binary content file remains in the repository. Both metadata and binary content file will be available for version-specific operations as described below. Previous versions of objects and the text renditions of their binary content files are not included in search processes.
>> POST /api/dms/objects/{objectId}/contents/file
...