Re: [Archivesspace_Users_Group] Importing EAD components with multiple sibling top containers
Mark, thanks. That worked. I was wondering if @parent was somehow necessary, but simple @ids sufficed. John From: Custer, Mark Sent: Wednesday, May 13, 2020 11:53 AM To: archivesspace_users_group@lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Importing EAD components with multiple sibling top containers Hi, John! Short answer: yes. But you have to use @id attributes on the containers, otherwise I think that the ASpace importer will assume that the containers are nested (details are defined here for the importer logic, https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb). Also, if you use @parent attributes that link to the @id values, then you can create multiple container groups (e.g. Box 1, Folders 1-5; Box 2, Folders 1-8; etc.). However, even though you can use container/@parent in EAD to reference a parent container anywhere else in the EAD file, with the ASpace importer, you can only do that within the same component (so, you need to explicitly repeat data in the EAD). So in your example, this should do the trick, if I recall correctly: 1 2 1862 -- 1875 Sept. And, if you needed something with subcontainers, that would look like this: 1 2 1 2 1862 -- 1875 Sept. I've got a number of different updates I run on EAD files prior to ingesting them to ASpace, and here's an example of one that can be used to add those id and parent attributes for some use cases: https://github.com/YaleArchivesSpace/xslt-files/blob/master/EAD_add_IDs_to_containers.xsl Mark From: archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> on behalf of Rees, John (NIH/NLM) [E] mailto:re...@mail.nlm.nih.gov>> Sent: Wednesday, May 13, 2020 11:30 AM To: archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org> mailto:archivesspace_users_group@lyralists.lyrasis.org>> Subject: [Archivesspace_Users_Group] Importing EAD components with multiple sibling top containers Is it possible to import an EAD component that is comprised of multiple parent-level top containers and have ASpace create two sibling top container instances? Currently it seems ASpace will create a single instance with one top container for the positioned first, then create children/grandchildren for each subsequently positioned in that single instance. Is there a container attribute/semantics I could add to define this parallel logical relationship that would force ASpace to create two instances each with a top container? Or does the EAD importer as a general use tool assume most content is of a type parent/child? Example: 1 2 1862 -- 1875 Sept. To get: [cid:image002.jpg@01D6292C.142865E0] Thanks, John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 Teleworking M-F 8:00AM - 4:30PM until 5/31/2020 ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Importing EAD components with multiple sibling top containers
Is it possible to import an EAD component that is comprised of multiple parent-level top containers and have ASpace create two sibling top container instances? Currently it seems ASpace will create a single instance with one top container for the positioned first, then create children/grandchildren for each subsequently positioned in that single instance. Is there a container attribute/semantics I could add to define this parallel logical relationship that would force ASpace to create two instances each with a top container? Or does the EAD importer as a general use tool assume most content is of a type parent/child? Example: 1 2 1862 -- 1875 Sept. To get: [cid:image002.jpg@01D62919.F3141870] Thanks, John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 Teleworking M-F 8:00AM - 4:30PM until 5/31/2020 ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
Re: [Archivesspace_Users_Group] Importing EAD components with multiple sibling top containers
Hi, John! Short answer: yes. But you have to use @id attributes on the containers, otherwise I think that the ASpace importer will assume that the containers are nested (details are defined here for the importer logic, https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb). Also, if you use @parent attributes that link to the @id values, then you can create multiple container groups (e.g. Box 1, Folders 1-5; Box 2, Folders 1-8; etc.). However, even though you can use container/@parent in EAD to reference a parent container anywhere else in the EAD file, with the ASpace importer, you can only do that within the same component (so, you need to explicitly repeat data in the EAD). So in your example, this should do the trick, if I recall correctly: 1 2 1862 -- 1875 Sept. And, if you needed something with subcontainers, that would look like this: 1 2 1 2 1862 -- 1875 Sept. I've got a number of different updates I run on EAD files prior to ingesting them to ASpace, and here's an example of one that can be used to add those id and parent attributes for some use cases: https://github.com/YaleArchivesSpace/xslt-files/blob/master/EAD_add_IDs_to_containers.xsl Mark From: archivesspace_users_group-boun...@lyralists.lyrasis.org on behalf of Rees, John (NIH/NLM) [E] Sent: Wednesday, May 13, 2020 11:30 AM To: archivesspace_users_group@lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Importing EAD components with multiple sibling top containers Is it possible to import an EAD component that is comprised of multiple parent-level top containers and have ASpace create two sibling top container instances? Currently it seems ASpace will create a single instance with one top container for the positioned first, then create children/grandchildren for each subsequently positioned in that single instance. Is there a container attribute/semantics I could add to define this parallel logical relationship that would force ASpace to create two instances each with a top container? Or does the EAD importer as a general use tool assume most content is of a type parent/child? Example: 1 2 1862 -- 1875 Sept. To get: [cid:image002.jpg@01D62919.F3141870] Thanks, John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 Teleworking M-F 8:00AM – 4:30PM until 5/31/2020 ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
