Issues
- role attribute value stripped out upon importANW-814Resolved issue: ANW-814Lora Woodford
- Tree node request error and mismatches resource and AO IDANW-782
- Event Outcome ProblemsANW-778Resolved issue: ANW-778Lora Woodford
- There is some strange, non-Unicode behavior with the EAD3 exports now (I'm guessing due to gem issues since nothing else has changed). See the two examples belowANW-745Resolved issue: ANW-745Mark Custer
- PUI container inventory search page: pagination links don't work with facetsANW-733Resolved issue: ANW-733Manny Rodriguez
- As a repository manager, I would like staff and patrons to be able to use the keyword string of our institution's name to help limit searches.ANW-715Resolved issue: ANW-715
- Using Browser Back Button On Collections Gives "unexpected error"ANW-709Resolved issue: ANW-709Laney McGlohon
- As a collection manager, I would like the option to export a list of top containers associated with collectionANW-695Resolved issue: ANW-695Mark Cooper
- I would like classifications and associated records to load faster.ANW-652
role attribute value stripped out upon import
Description
Environment
Attachments
Details
Assignee
Lora WoodfordLora WoodfordReporter
Ryan EdwardsRyan EdwardsSprint
NoneFix versions
Affects versions
Priority
MinorHarvest Time Tracking
Open Harvest Time Tracking
Details
Details
Assignee
Reporter
Sprint
Fix versions
Affects versions
Priority
Harvest Time Tracking
Activity
Joshua ShawApril 29, 2021 at 1:02 PM
Importing EAD with origination role attributes appears to be fixed.
Christine Di BellaApril 26, 2021 at 2:48 PM
@Andrew Morrison Got it. I’ve created a Jira for this at https://archivesspace.atlassian.net/browse/ANW-1276 . Please check to see if it describes the situation accurately and add to it if more clarification is needed.
@Lora Woodford These comments about issues with the EAD export depending on role do not relate to https://archivesspace.atlassian.net/browse/ANW-814.
Andrew MorrisonApril 26, 2021 at 2:26 PM
Yes. But an additional complications is only unpublished agents linked to archival objects with role of “Subject”. Ones that are unpublished and linked to resources with a role of “Subject” are exported. Publishing the agents means they do export, no matter what the level of the record is.
Christine Di BellaApril 26, 2021 at 2:03 PM
@Andrew Morrison Just want to check since this is confusing and fiddly thanks to the combination of EAD and ArchivesSpace settings, and likely unrelated to the relator import issue on this ticket. Is the issue you’re pointing out that unpublished agents with a role of “Creator” are always included in the EAD export when “include unpublished” is selected, but that unpublished agents with a role of “Subject” are not?
Andrew MorrisonApril 26, 2021 at 1:11 PM
Apologies, I misread what the EAD exporter was doing. You are correct, it is mapping Relator fields to role attributes.
But there is another problem. I created a test EAD file (the attached role_test_ead2002_in.xml) and imported that into test.archivesspace.org. The role attribute values populated the Relator fields in the linked agents correctly. Then I exported it as EAD 2002 (role_test_ead2002_out.xml) and EAD3 (role_test_ead3_out.txt) with the option to include anything unpublished (which the agents created upon import all are.)
As you can see if you diff them, the agents which are linked to the archival objects with “Subject” as their Role have been lost. The only controlaccess exported is the first one, for the agents linked to the collection-level resource. After that, in the <c>
, only the agents which are linked with the Role of “Creator” are exported, as children of origination.
When linking an agent to a resource we have the option to declare a relator term, in this example, former owner (see attached agent-links.jpg screenshot)
The record exports as the following in EAD:
<c04 id="aspace_600045f6612fc94f6e7b67ce9ef71219" level="file">
<did>
<unittitle><title render="italic">Luise Stauffer, born Schärer</title> [<title
render="italic">Luise Stauffer, geb. Schärer</title>],</unittitle>
<unitid>28.IV new impression b (Lehrs)</unitid>
<origination label="creator"><persname role="fmo"
source="library of congress name authority file">Simms, Richard A.,
Dr.</persname></origination>
<physdesc altrender="whole"><extent altrender="materialtype spaceoccupied">1
print</extent></physdesc>
<unitdate normal="1887/1887">[1887]</unitdate>
<container id="aspace_711b121874b7a8ca44f79430373c6c0a" label="Graphic Materials"
type="box">31</container>
</did>
The relator term is tagged as the role attribute:
<origination label="creator"><persname role="fmo"
source="library of congress name authority file">Simms, Richard A.,
Dr.</persname></origination>
When, however, we try to import a resource that has a role attribute value, that value does not appear in the relator field and upon re-export it is clear in the ead that the role/relator has been stripped out. We would like the role attribute to populate the relator field upon import.
Thanks,
Ryan
Ryan Edwards
Digital Access and Systems Librarian
Getty Digital – Collection Management Systems
Getty Research Institute
1200 Getty Center Drive, Suite 1100
Los Angeles, CA 90049-1688
reedwards@getty.edu
310.440.7398