Digital Objects in the PUI only display *one* file version even if more than one published file version exists
Description
Complexity
Activity
Matt StraussDecember 7, 2023 at 4:46 PM
At the December Development/Prioritization meeting, we discussed the issue raised by this ticket. In testing the use case (a sound recording digital object that has both a WAV and MP3 file version) I confirmed that only one version of the file is accessible in the PUI. There are several different ways multiple file versions can be made accessible in the PUI (via multiple thumbnails/icons, links in the Additional File Versions section of the Digital Object record, potentially something similar in the archival object record, etc.). For this reason, we are going to seek input from the wider ArchivesSpace community before moving forward.
Christine Di BellaOctober 10, 2022 at 2:20 PMEdited
As written, this conflicts with https://archivesspace.atlassian.net/browse/ANW-1209, for which a community specification was circulated and for which work is well underway. My suggestion would be to hold off on this one and consider it again once https://archivesspace.atlassian.net/browse/ANW-1209 is fully implemented.
Angela WhiteFebruary 7, 2022 at 7:10 PM
Dev-Pri looked at this ticket during our February meeting and decided to pass it on for development. It is unlikely that a digital object would have so many file versions as to be problematic.
Details
Assignee
UnassignedUnassignedReporter
Joshua ShawJoshua ShawPriority
MinorHarvest Time Tracking
Open Harvest Time Tracking
Details
Details
Assignee
Reporter
Joshua ShawPriority
Minor
I think changing this behavior would require additional work around digital object file versions and how those are implemented, as well as how those are displayed in the PUI. There would also need to be migrations for existing data.
Use Case
We have a digital object with a derivative - ie a wav and mp3. One could list this as two digital objects, but in reality they are both different file versions of the same object. The expected data entry would be to enter the two formats as different file versions. If both were to be made available to the public, you would tick off publish for both. However, even though you can enter the data this way, the display in the PUI does not support this.
Ideally, I think that each file version should be available for display with each object able to record a display thumbnail, rather than the 'is representative' + xlink attribute method used now.
This is the culprit as far as explicitly limiting to one DO:
This bit of code: https://github.com/archivesspace/archivesspace/blob/971cff22493981d0c1db95358b0fc5710b70f73c/public/app/controllers/concerns/result_info.rb#L107
calls this bit https://github.com/archivesspace/archivesspace/blob/971cff22493981d0c1db95358b0fc5710b70f73c/public/app/controllers/concerns/result_info.rb#L164 which explicitly limits the number of file versions that can be displayed as it accumulates all of the data from the file versions into one object.