...
Page Properties | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
Resources & Remarks Nils' original description: A multipart request body is posted. It always contains a "data" part, that contains an object list with the metadata of the affected objects. On an import or content update it can contains further parts as with renditions. The majority of the metadata in the "data" part is still raw. That means it is not yet normalized, validated and system properties are not yet set. Only content properties are available in case of import or content update. For more details take a look at the examples below. If the regular import route should be continued, pass the multipart to http://registry/api/dms/objects.
Modification History
|
...
As of Version | 2020 Winter |
---|---|
HTTP Method | POST |
Response Format | JSON |
Predicate | The predicate is applied on all objects of the |
Description | It can be triggered by
The take-off point of the interceptor is after the REPOSITORY service. The initial request body is already normalized, validated and enriched with content stream properties as can be seen in the examples provided below. The enriched multipart request body is taken by the interceptor. It always contains a Within the interceptor, any user-defined operation can be executed on the corresponding metadata by calling the external endpoint specified as If the interceptor should continue the regular process exactly at the take-off point, pass the multipart to |
Requirements for external endpoint | The target URL must be a POST endpoint accepting a multipart request body and returning a list of objects as JSON. |
Affected API Requests | POST /api/dms/objects/{objectId} |
Restart Service | Repository service |
Header | Authorization-Header |
...