[Archivesspace_Users_Group] inconsistency in ead import dao/@rold vs daoloc/@role

Majewski, Steven Dennis (sdm7g) sdm7g at eservices.virginia.edu
Mon Sep 12 09:32:32 EDT 2016


Is there a reason for this inconsistency of the import of @role attribute for dao / doloc ? 


On <dao>, @role is assigned to use_statement 

https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L754

While on <doaloc>, @role is assigned to file_format_name:

https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L795


The first case it a lot more useful for us, while file_format_name is usually identifiable from the filename in href and is redundant. ( We would like @role to indicate if the URI is a pointer to IIIF image service or manifest, or a link to digital object in another system, rather than merely a link to an image. The 2nd case might be better represented internally as external_ids, but there doesn’t seem to be a way to get them in and out with an EAD mapping, or a way to enter and edit them in the frontend. ) 



— Steve. 




More information about the Archivesspace_Users_Group mailing list