[ALF-22097] T Engine - add source nodeId parameter Created: 10-Aug-19 Updated: 16-Oct-19 Resolved: 13-Aug-19
|Affects Version/s:||Community Edition Next, Community Edition 201901 GA|
|Fix Version/s:||ACS 201910-EA|
|Security Level:||external (External user)|
|Reporter:||Daniel Gradecak||Assignee:||Closed Issues|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Date of First Response:|
|Resolution Time Custom Field:||2 days, 20 hours, 33 minutes, 55 seconds|
It would help to have the source nodeId in the "always supplied" parameters for a T Engine transform call. While basing transformations only on content is logical but some transformations might need extra metadata of the source, imagine building a templating engine where some metadata would end up in the specific "template document" transformation.
I cna think of two possibilities, either provide the nodeId to T-Engines, so the custom engine could use it and call back the REPO for extra information, either allow some kind of dynamic transformation options that a RenditionDefinition2 might invoke before checking the transformation option but that is not a good option. I would go with the first approach.
So what is needed, to have a way to get source node informations (not just mimetype) on the T Engine side.
args[i++] = "sourceNodeId";
|Comment by Alan Davis [ 12-Aug-19 ]|
Thank you for your suggestion. As part of
|Comment by Daniel Gradecak [ 12-Aug-19 ]|
If I may suggest to have the source ID instead of the source nodeRef, just to stay in the "REST API" fashion. In my opinion it makes sense so it is node needed to do extra processing on the T engine side in order to use the rest API callback for instance.
Not sure if it would make sense for you, but in the same way where through the rendition definition you would define the "sourceId" for instance, it could be a greater value even to have the possibility to include property metadata names that we want transfered. But there you might have more issues with converrters for instance. Just give it a thought and if it makes no sense than the sourceId is completely fine.