User Story #10926 (closed)
Handling of companion files in clients and server
|Reported by:||bpindelski||Owned by:|
|Cc:||fs@…, web-team@…||Story Points:||n.a.|
|Total Remaining Time:||n.a.||Estimated Remaining Time:||n.a.|
On dev_4_4 companion files (which are a file annotation) are linked to the image (PixelsOriginalFileMap?). This doesn't happen anymore on develop. The companion file now is linked to the same fileset id as the image being imported. According to Jean-Marie, this will increase the number of calls that the client will need to do to retrieve the companion file (don't confuse with original metadata) - first to get the fileset id from the images, then use that to get the companion file. This problem might also impact analysis or tables files attached to images.
This has to be fixed in 3 places: server, Web and Insight. A decision has to be made how the companion files are retrieved so that the clients aren't blocked with an unnecessary high amount of method calls.