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. This was passed in 2022 but tabled because it conflicted with a related ticket (
ANW-1209
-
Getting issue details...STATUS
). That ticket has now been implemented and now the Make Representative button can be used designate only one thumbnail per digital object. I’m not clear on the use case for this – presumably a thumbnail for a master and access copy of a digital image would look the same? Different file versions are already linked via the Additional File Versions section of the Digital Object Record in the PUI. I’m curious to hear input from the team on this one, but I’m leaning towards closing.
Confirmed this bug report. As a side note, the user documentation of the Xlink fields in the digital object record could be expanded upon.