[Archivesspace_Users_Group] Editing Location of Digital Objects

[Brian Hoffman]

Hi Phil,

ArchivesSpace doesn’t really know very much about digital objects. In addition to the metadata on the digital object record itself, there can be one or more ‘file version’ subrecords, each of which can a ‘file_uri’:
https://github.com/archivesspace/archivesspace/blob/master/common/schemas/file_version.rb <https://github.com/archivesspace/archivesspace/blob/master/common/schemas/file_version.rb>

For the most part, ASpace doesn’t offer much more than display and editing of that URI. However, the public UI does make a *weak* attempt to guess whether it’s an image that can be displayed in the browser, based on the other fields on the file version subrecord. You can see some of that logic here:

https://github.com/archivesspace/archivesspace/blob/master/public/app/models/file_version_view.rb <https://github.com/archivesspace/archivesspace/blob/master/public/app/models/file_version_view.rb>

Note that the accuracy of the file format and size are entry dependent on user entry (or another system's in the case of API integrations).

Brian

> On Jan 21, 2016, at 3:51 PM, Suda, Phillip J <psuda1 at tulane.edu> wrote:
> 
> Greetings all, 
> 
> Let's say I put the objects at http://localhost/files <http://localhost/files>
> 
> What would I need to alter in database so that the digital objects are visible from Public UI from that location? 
> 
> Thanks, 
> 
> Phil 
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160121/cc31988a/attachment.html>