[Archivesspace_Users_Group] EAD Import trouble with audience/publish
Chris.Fitzpatrick at lyrasis.org
Tue Apr 5 02:45:00 EDT 2016
Yes, it looks like the EAD converter<https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L108> only looks at @audience for archdesc and c tags.
Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat | Phone: 918.236.6048
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jane LaBarbara <jane.labarbara at mail.wvu.edu>
Sent: Monday, April 04, 2016 8:34 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] EAD Import trouble with audience/publish
I'm using legacy EAD XML to test ArchivesSpace's EAD Import in preparation for a mass migration to ArchivesSpace. I've noticed that I can add the attribute audience="external" to <archdesc> and all of my "notes" (e.g. <relatedmaterial>, <bioghist>, and many more), but the resulting Resource Record is only published at the highest level-the notes themselves are not published. Once we migrate, I'm guessing this will mean that staff will have to go into each Resource Record and click the "publish" checkboxes for everything we need to show up in the public view, and we have over 4000 collections.
Has anyone else noticed that the EAD Import does not respect audience="external", or found a solution or workaround for this?
Jane Metters LaBarbara
West Virginia & Regional History Center<https://wvrhc.lib.wvu.edu/>
West Virginia University Libraries
Reference desk: 304-293-3536
Office phone: 304-293-0352
Email: jane.labarbara at mail.wvu.edu<mailto:jane.labarbara at mail.wvu.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group