Date: Monday, April 19, 2021 at 1:26 PM
To: "archivesspace_users_group@lyralists.lyrasis.org"
Subject: Re: [Archivesspace_Users_Group] Should digital object file_uri field
allow non URI data?
Option A, because anything but a URI would create invalid EAD if exported or
requested v
Hi,
We have been trying to understand what to do about cases like the following:
http://sandbox.archivesspace.org/digital_objects/2/edit#tree::digital_object_2
[cid:image001.png@01D73512.22D7F220]
As things are now, ArchivesSpace will allow a value like this, but various
renderings and
Option A, because anything but a URI would create invalid EAD if
exported or requested via OAI-PMH.
Andrew.
On 19/04/2021 17:41, Majewski, Steven Dennis (sdm7g) wrote:
I would think ‘A’, but that’s based on that the field is labeled “File
URI” so I expect something that looks like a URI,
I would think ‘A’, but that’s based on that the field is labeled “File URI” so
I expect something that looks like a URI, and the fact that some notes in
ArchivesSpace are explicitly labeled as allowing mixed content, and that has
made me assume that allowing mixed content is not the default.
