Feature calls for a loosening of controls on embedding EAD XML in note fields. Doing so could speed data entry for advanced users, but the application might be unable to validate the XML due to the differences in in-line encoding practice between EAD 2002 and EAD3. This may also present challenges for users unfamiliar with EAD tagging. Recommend gathering more information about alternative approaches, such as importing XML snippets or CSV files into the various list subrecords in Resource record notes.
Confirmed this bug report. I also noticed that the user documentation surrounding
Ticket is asking for thumbnails to display for different file versions of a digital object. The use case involves providing thumbnails (or icons) to an MP3 and WAV versions of a sound recording. This ticket was passed in 2022 but tabled because it conflicted with a related ticket (
ANW-1209
-
Getting issue details...STATUS
), which limits thumbnails/icons to one version. That feature request has now been implemented and may conflict with what is being specifically asked for here, but I do think there is utility in the ability to provide access to different file versions (either via thumbnails/icons, the Additional File Versions section, or some other manner) and to have the user documentation clearly spell out how to do that.
Confirmed this bug report. As a side note, the user documentation of the Xlink fields in the digital object record could be expanded upon.