Our REST API today allows enriching documents by contributing new enrichers who will write new properties in contextParameters. However when we need to include extra blob information (ie WOPI links NXP-25300, Liveconnect app links NXP-21249, etc) using document enrichers we will need to use the blob's xpath as key which makes the response structure weird and impossible to validate, ex:
wopi: {
"file:content": {...}
"files:files/0/file": {...}
"files:files/1/file": {...}
}
This extra data should be written along with the blob and not out of band, ie:
file:content: {
data: ".."
name: "..",
wopi: { ...}
}
We will however still need a way to control whether or not these blob enrichers should be active as they may incur a cost. For consistency reasons it would make sense to have enrichers.blob:wopi
- depends on
-
NXP-26038 Make ConfigurationService.getPropertiesAsJson() support nested properties
-
- Resolved
-
- is related to
-
NXP-25300 Add an enricher for WOPI URLs
-
- Resolved
-
- is required by
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
