...
| 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 | 2.42020 Winter |
|---|---|
| HTTP Method | POST |
Response FormatFormat  | JSON |
| Description | This Interceptor can be trigger by The Interceptor allows for manipulation of the metadata before storing in the database.
The take-off point of the interceptor is after the REPOSITORY service. The initial request body is already normalized, validated and enriched with system 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, e.g. by calling an external endpoint. Afterwards, the modified multipart has to be routed back to continue the regular process at the suitable point. If the interceptor should continue the regular process exactly at the take-off point, pass the multipart to |
| Affected API Requests | POST /api/dms/objects/{objectId} |
| Restart Service | Repository service |
| Header | Authorization-Header |
| PredicatePredicate | The predicate is applied on all objects of the object list in the "data" part. If at least one object matches, the interceptor is called. |
...