[Archivesspace_Users_Group] Should digital object file_uri field allow non URI data?

[Brian Hoffman]

Hmm. I am attaching the image again, please let me know if you still can’t see it:



From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Busch, Ed" <buschedw at msu.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Monday, April 19, 2021 at 11:53 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Should digital object file_uri field allow non URI data?

I get an unable to access page. Maybe a screen shot.



Ed Busch, MLIS
Interim Head of University Archives and Historical Collections
Electronic Records Archivist
Conrad Hall, 943 Conrad Road, Room 101
East Lansing, MI 48824
517-884-6438
buschedw at msu.edu<mailto:buschedw at msu.edu>
he/him/his


From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Brian Hoffman <brian.hoffman at lyrasis.org>
Reply-To: "archivesspace_users_group at lyralists.lyrasis.org" <archivesspace_users_group at lyralists.lyrasis.org>
Date: Monday, April 19, 2021 at 11:50 AM
To: "archivesspace_users_group at lyralists.lyrasis.org" <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Should digital object file_uri field allow non URI data?

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<https://urldefense.com/v3/__http:/sandbox.archivesspace.org/digital_objects/2/edit*tree::digital_object_2__;Iw!!HXCxUKc!m5EZAjZpgnW9XFWWxV7oF0TcX5E5N_BW_qyN_ynsYM9hxEPWDlknlgebRkMhKZ8$>

[cid:image001.png at 01D73513.22FFD000]

As things are now, ArchivesSpace will allow a value like this, but various renderings and transformations will not work as expected. I am wondering if:


  1.  This is a legacy bug; the field should have originally validated values to ensure they were URIs
  2.  This is a presentation layer bug: non URIs should be allowed in the file_uri field, but HTML and PDF presentations need to accommodate that.
  3.  Everything is fine. Users should be able to put whatever they want in file_uri, but if they want it to present right they need to write a plugin.

This isn’t an academic question, as this is currently happening with records created automatically by Preservica software.

Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20210419/58e04a3f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 95640 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20210419/58e04a3f/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: file_uri_img.png
Type: image/png
Size: 90523 bytes
Desc: file_uri_img.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20210419/58e04a3f/attachment-0003.png>