From snewhouse at sciencehistory.org Tue Oct 4 12:28:04 2022 From: snewhouse at sciencehistory.org (Newhouse, Sarah) Date: Tue, 4 Oct 2022 16:28:04 +0000 Subject: [Archivesspace_Users_Group] MARC XML -->resource record batch import References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.cb1a7348-2014-44c5-b107-425ed2b9242d@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.5b4804ac-1246-4b08-b712-ea1ebb0f7d14@emailsignatures365.codetwo.com> Message-ID: Hi all, We're trying to figure out the fastest way to generate stub resource records in ASpace from MARC XML for about 300 collections. The MARC XML we get from our Sierra OPAC creates really messy resource records using the MARC import function baked into ASpace, so while we could do that and spend our time on clean-up after ingest, I feel like there must be a way to convert the MARC XML into clean JSON in bulk (maybe with a CSV intermediary step?) and then import via the API. Before I go too far down the "I'll just do it all myself" route, has anyone done this before and could share workflows or scripts? Or gently tell me why this won't work? I'm aware of this from Smith: https://github.com/smith-special-collections/a2c-tools/tree/master/mrbc_resources and the API Playbook from Atlas, the official API wiki and its sample scripts, and various blog posts/guides for ArchivesSnake and PyMARC. Other suggestions? Thank you! __________________________________ Sarah Newhouse (she, her, hers) Digital Preservation Archivist Othmer Library of Chemical History t. +1.215.873.8249 Science History Institute Chemistry * Engineering * Life Sciences 315 Chestnut Street * Philadelphia, PA 19106 * U.S.A. Learn about the scientific discoveries that changed our world at sciencehistory.org/learn -------------- next part -------------- An HTML attachment was scrubbed... URL: From reesj at mail.nlm.nih.gov Tue Oct 4 16:33:37 2022 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Tue, 4 Oct 2022 20:33:37 +0000 Subject: [Archivesspace_Users_Group] MARC XML -->resource record batch import In-Reply-To: References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.cb1a7348-2014-44c5-b107-425ed2b9242d@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.5b4804ac-1246-4b08-b712-ea1ebb0f7d14@emailsignatures365.codetwo.com> Message-ID: Hi Sarah, My path (pre-covid) used MarcEdit 1. grab MARCXML via z39.50 2. use marcedit's MARC-EAD transform xsl (w/ local edits) 3. import EAD into aspace 4. massage/publish agents, subjects, etc. We do this annually for adding accession records as resources (we don't use the aspace accession module). I had done this same routine for our pre-aspace EAD-centric discovery software. John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Newhouse, Sarah Sent: Tuesday, October 4, 2022 12:28 PM To: Archivesspace Users Group Subject: [EXTERNAL] [Archivesspace_Users_Group] MARC XML -->resource record batch import Hi all, We're trying to figure out the fastest way to generate stub resource records in ASpace from MARC XML for about 300 collections. The MARC XML we get from our Sierra OPAC creates really messy resource records using the MARC import function baked into ASpace, so while we could do that and spend our time on clean-up after ingest, I feel like there must be a way to convert the MARC XML into clean JSON in bulk (maybe with a CSV intermediary step?) and then import via the API. Before I go too far down the "I'll just do it all myself" route, has anyone done this before and could share workflows or scripts? Or gently tell me why this won't work? I'm aware of this from Smith: https://github.com/smith-special-collections/a2c-tools/tree/master/mrbc_resources and the API Playbook from Atlas, the official API wiki and its sample scripts, and various blog posts/guides for ArchivesSnake and PyMARC. Other suggestions? Thank you! __________________________________ Sarah Newhouse (she, her, hers) Digital Preservation Archivist Othmer Library of Chemical History t. +1.215.873.8249 Science History Institute Chemistry * Engineering * Life Sciences 315 Chestnut Street * Philadelphia, PA 19106 * U.S.A. Learn about the scientific discoveries that changed our world at sciencehistory.org/learn CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe. -------------- next part -------------- An HTML attachment was scrubbed... URL: From snewhouse at sciencehistory.org Tue Oct 4 17:20:03 2022 From: snewhouse at sciencehistory.org (Newhouse, Sarah) Date: Tue, 4 Oct 2022 21:20:03 +0000 Subject: [Archivesspace_Users_Group] MARC XML -->resource record batch import In-Reply-To: References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.cb1a7348-2014-44c5-b107-425ed2b9242d@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.5b4804ac-1246-4b08-b712-ea1ebb0f7d14@emailsignatures365.codetwo.com> Message-ID: Thanks, John! That's really useful. (And honestly, shame on me for forgetting that MarcEdit exists.) Are you importing those EAD XML files one at a time? Science History Institute Chemistry ? Engineering ? Life Sciences 315 Chestnut Street ? Philadelphia, PA 19106 ? U.S.A. Learn about the scientific discoveries that changed our world at sciencehistory.org/learn __________________________________ Sarah Newhouse (she, her, hers) Digital Preservation Archivist Othmer Library of Chemical History t. +1.215.873.8249 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Rees, John (NIH/NLM) [E] Sent: Tuesday, October 4, 2022 4:33 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] MARC XML -->resource record batch import Hi Sarah, My path (pre-covid) used MarcEdit 1. grab MARCXML via z39.50 2. use marcedit?s MARC-EAD transform xsl (w/ local edits) 3. import EAD into aspace 4. massage/publish agents, subjects, etc. We do this annually for adding accession records as resources (we don?t use the aspace accession module). I had done this same routine for our pre-aspace EAD-centric discovery software. John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Newhouse, Sarah Sent: Tuesday, October 4, 2022 12:28 PM To: Archivesspace Users Group Subject: [EXTERNAL] [Archivesspace_Users_Group] MARC XML -->resource record batch import Hi all, We?re trying to figure out the fastest way to generate stub resource records in ASpace from MARC XML for about 300 collections. The MARC XML we get from our Sierra OPAC creates really messy resource records using the MARC import function baked into ASpace, so while we could do that and spend our time on clean-up after ingest, I feel like there must be a way to convert the MARC XML into clean JSON in bulk (maybe with a CSV intermediary step?) and then import via the API. Before I go too far down the ?I?ll just do it all myself? route, has anyone done this before and could share workflows or scripts? Or gently tell me why this won?t work? I?m aware of this from Smith: https://github.com/smith-special-collections/a2c-tools/tree/master/mrbc_resources and the API Playbook from Atlas, the official API wiki and its sample scripts, and various blog posts/guides for ArchivesSnake and PyMARC. Other suggestions? Thank you! __________________________________ Sarah Newhouse (she, her, hers) Digital Preservation Archivist Othmer Library of Chemical History t. +1.215.873.8249 Science History Institute Chemistry ? Engineering ? Life Sciences 315 Chestnut Street ? Philadelphia, PA 19106 ? U.S.A. Learn about the scientific discoveries that changed our world at sciencehistory.org/learn CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe. -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Oct 5 09:19:25 2022 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 5 Oct 2022 13:19:25 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 3.3.1 now available In-Reply-To: References: Message-ID: Hello ArchivesSpace members, ArchivesSpace 3.3.1 is now available. This patch release fixes a bug when using default values that was introduced by 3.3.0 and adds some missing labels. People who haven't already upgraded to 3.3.0 should go directly to this release when they do upgrade, and we recommend upgrading to 3.3.1 if you have already upgraded to 3.3.0 and use or plan to use default values for record creation. More information about what's in the release and the link to download it are at https://github.com/archivesspace/archivesspace/releases/tag/v3.3.1. Information on upgrading to a new version of ArchivesSpace is available at https://archivesspace.github.io/tech-docs/administration/upgrading.html. If you have questions or need any assistance, please let us know. A special thanks to our Registered Service Providers Atlas Systems for identifying the default values issue and LYRASIS Digital Technology Services for the quick submission of a fix to it. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: From Ron.VandenBranden at antwerpen.be Wed Oct 5 09:55:40 2022 From: Ron.VandenBranden at antwerpen.be (Ron Van den Branden) Date: Wed, 5 Oct 2022 13:55:40 +0000 Subject: [Archivesspace_Users_Group] different date models for Agents vs Accessions, Resources, Archival Objects? Message-ID: Hi, I'm wondering why different date models exist for different record types in ArchivesSpace: * Accessions + Resources/Archival Objects: * Date Certainty: general certainty qualifier: "Approximate", "Inferred", "Questionable" * Agents: * Date Certainty: general certainty qualifier: "Approximate", "Inferred", "Questionable" * Standardized Date Type: specific qualifier for both Begin and End date: "Standard", "Not Before", "Not After" The extra field Standardized Date Type is occurring consistently for all date fields in the Agents module. This raises some questions: * What's the motivation for this difference? Is it standards-based, and does EAC-CPF allow for more detail than EAD? Or is is because the Agents module has been reworked more recently? * In the latter case, is any harmonization foreseen for the date fields in Accessions and Resources/Archival Objects? If so, is there a time frame? Many thanks for your thoughts! Best, Ron Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en Erfgoed Minderbroedersstraat 22, 2000 Antwerpen ? Grote Markt 1, 2000 Antwerpen gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 letterenhuis.be | instagram | facebook Proclaimer Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren. -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Oct 5 12:29:38 2022 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 5 Oct 2022 16:29:38 +0000 Subject: [Archivesspace_Users_Group] different date models for Agents vs Accessions, Resources, Archival Objects? In-Reply-To: References: Message-ID: Hello Ron, The divergence of the two date models within ArchivesSpace did come about with the work on the Agents module. While the plan is to eventually move other record types for which it makes sense to the same model (there are some related requests at https://archivesspace.atlassian.net/browse/ANW-1475 and https://archivesspace.atlassian.net/browse/ANW-380), because dates are so complex and because the agents work was underway already, we treated the work on dates associated with agents as a first step. The motivation for the change was specific to the EAC-CPF standard, though it has broader applicability with EAD as well. I don?t have a specific timeframe for moving other dates in the application to this model right now. One of our thoughts in staging this date transition was that we wanted to get feedback on the agents dates piece before taking the even larger step of moving the other record types (and migrating the associated data) to that model. We haven?t received much feedback on the agents yet, possibly because a lot of people haven?t upgraded to a 3.x version yet or possibly because the new date model meets their needs just fine. We are currently reviewing prioritized projects against capacity in light of staffing changes and I intend to share more information and an updated roadmap soon. I hope that helps. If you have other questions, or if anyone here has background or feedback specific to the agents date model, we?d be glad to have them. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Ron Van den Branden Sent: Wednesday, October 5, 2022 9:56 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] different date models for Agents vs Accessions, Resources, Archival Objects? Hi, I'm wondering why different date models exist for different record types in ArchivesSpace: * Accessions + Resources/Archival Objects: * Date Certainty: general certainty qualifier: "Approximate", "Inferred", "Questionable" * Agents: * Date Certainty: general certainty qualifier: "Approximate", "Inferred", "Questionable" * Standardized Date Type: specific qualifier for both Begin and End date: "Standard", "Not Before", "Not After" The extra field Standardized Date Type is occurring consistently for all date fields in the Agents module. This raises some questions: * What's the motivation for this difference? Is it standards-based, and does EAC-CPF allow for more detail than EAD? Or is is because the Agents module has been reworked more recently? * In the latter case, is any harmonization foreseen for the date fields in Accessions and Resources/Archival Objects? If so, is there a time frame? Many thanks for your thoughts! Best, Ron Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en Erfgoed Minderbroedersstraat 22, 2000 Antwerpen ? Grote Markt 1, 2000 Antwerpen gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 letterenhuis.be | instagram | facebook Proclaimer Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: From reesj at mail.nlm.nih.gov Wed Oct 5 13:48:25 2022 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Wed, 5 Oct 2022 17:48:25 +0000 Subject: [Archivesspace_Users_Group] [EXTERNAL] Re: MARC XML -->resource record batch import In-Reply-To: References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.cb1a7348-2014-44c5-b107-425ed2b9242d@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.5b4804ac-1246-4b08-b712-ea1ebb0f7d14@emailsignatures365.codetwo.com> Message-ID: Nope, all at once, though we're only doing a few dozen at most (acquisitions are slow these days). You could probably send bigger batches over as these would be small file sizes. John From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Newhouse, Sarah Sent: Tuesday, October 4, 2022 5:20 PM To: Archivesspace Users Group Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] MARC XML -->resource record batch import Thanks, John! That's really useful. (And honestly, shame on me for forgetting that MarcEdit exists.) Are you importing those EAD XML files one at a time? Science History Institute Chemistry * Engineering * Life Sciences 315 Chestnut Street * Philadelphia, PA 19106 * U.S.A. Learn about the scientific discoveries that changed our world at sciencehistory.org/learn __________________________________ Sarah Newhouse (she, her, hers) Digital Preservation Archivist Othmer Library of Chemical History t. +1.215.873.8249 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Rees, John (NIH/NLM) [E] > Sent: Tuesday, October 4, 2022 4:33 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] MARC XML -->resource record batch import Hi Sarah, My path (pre-covid) used MarcEdit 1. grab MARCXML via z39.50 2. use marcedit's MARC-EAD transform xsl (w/ local edits) 3. import EAD into aspace 4. massage/publish agents, subjects, etc. We do this annually for adding accession records as resources (we don't use the aspace accession module). I had done this same routine for our pre-aspace EAD-centric discovery software. John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Newhouse, Sarah Sent: Tuesday, October 4, 2022 12:28 PM To: Archivesspace Users Group > Subject: [EXTERNAL] [Archivesspace_Users_Group] MARC XML -->resource record batch import Hi all, We're trying to figure out the fastest way to generate stub resource records in ASpace from MARC XML for about 300 collections. The MARC XML we get from our Sierra OPAC creates really messy resource records using the MARC import function baked into ASpace, so while we could do that and spend our time on clean-up after ingest, I feel like there must be a way to convert the MARC XML into clean JSON in bulk (maybe with a CSV intermediary step?) and then import via the API. Before I go too far down the "I'll just do it all myself" route, has anyone done this before and could share workflows or scripts? Or gently tell me why this won't work? I'm aware of this from Smith: https://github.com/smith-special-collections/a2c-tools/tree/master/mrbc_resources and the API Playbook from Atlas, the official API wiki and its sample scripts, and various blog posts/guides for ArchivesSnake and PyMARC. Other suggestions? Thank you! __________________________________ Sarah Newhouse (she, her, hers) Digital Preservation Archivist Othmer Library of Chemical History t. +1.215.873.8249 Science History Institute Chemistry * Engineering * Life Sciences 315 Chestnut Street * Philadelphia, PA 19106 * U.S.A. Learn about the scientific discoveries that changed our world at sciencehistory.org/learn CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe. CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tlaver at nelson-atkins.org Mon Oct 3 12:01:29 2022 From: tlaver at nelson-atkins.org (Tara Laver) Date: Mon, 3 Oct 2022 16:01:29 +0000 Subject: [Archivesspace_Users_Group] training a new staff member Message-ID: Hello, I'm curious to learn how you have gone about introducing a new staff member to ArchivesSpace and training them. I have somebody starting who had a brief intro to it in school but has no real experience with it. Most of what they will be doing at first is resource record creation (multi-level) and loading via spreadsheet. I don't want to overwhelm but also think that because so much is interconnected that having a good sense of the bigger picture of how it all works would also be helpful. I'm trying to choose among the many training video options available on YouTube and from the help and tutorial pages. If you have suggestions on those for what has worked for you in the past or more generally how you have approached this, I would be grateful to hear. Many thanks, Tara Laver Tara Z. Laver (she/her/hers) Senior Archivist The Nelson-Atkins Museum of Art 4525 Oak Street Kansas City, MO 64111 Office: 816.751.1354 tlaver at nelson-atkins.org www.nelson-atkins.org [cid:image001.png at 01D8D717.4E39A550] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5175 bytes Desc: image001.png URL: From herzogn at uncw.edu Thu Oct 6 09:01:46 2022 From: herzogn at uncw.edu (Herzog, Nina A.) Date: Thu, 6 Oct 2022 13:01:46 +0000 Subject: [Archivesspace_Users_Group] training a new staff member In-Reply-To: References: Message-ID: Hello Tara, My first experience with ArchivesSpace was in graduate school. After reading the manual, then working along with the staff, they showed me how to directly input data without using the spreadsheet. I have never used the spreadsheet and upload, I find it much easier to do direct input instead of the spreadsheet, it eliminates any issues with the spreadsheet not uploading correctly. Regards, Nina Herzog University Archives Library Specialist William Madison Randall Library University of North Carolina at Wilmington 601 South College Road Wilmington, NC 28403 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tara Laver Sent: Monday, October 3, 2022 12:01 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] training a new staff member Some people who received this message don't often get email from tlaver at nelson-atkins.org. Learn why this is important [This email originated from outside of UNCW] Hello, I'm curious to learn how you have gone about introducing a new staff member to ArchivesSpace and training them. I have somebody starting who had a brief intro to it in school but has no real experience with it. Most of what they will be doing at first is resource record creation (multi-level) and loading via spreadsheet. I don't want to overwhelm but also think that because so much is interconnected that having a good sense of the bigger picture of how it all works would also be helpful. I'm trying to choose among the many training video options available on YouTube and from the help and tutorial pages. If you have suggestions on those for what has worked for you in the past or more generally how you have approached this, I would be grateful to hear. Many thanks, Tara Laver Tara Z. Laver (she/her/hers) Senior Archivist The Nelson-Atkins Museum of Art 4525 Oak Street Kansas City, MO 64111 Office: 816.751.1354 tlaver at nelson-atkins.org www.nelson-atkins.org [cid:image001.png at 01D8D962.3287C290] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5175 bytes Desc: image001.png URL: From brijmcla at iu.edu Thu Oct 6 10:21:23 2022 From: brijmcla at iu.edu (McLaughlin, Brianna Jean) Date: Thu, 6 Oct 2022 14:21:23 +0000 Subject: [Archivesspace_Users_Group] training a new staff member In-Reply-To: References: Message-ID: Hi, We have created a number of resources to train folks at Indiana University. We have basic documentation, which is creating collection level information in ArchivesSpace as well as a general introduction to ArchivesSpace. We also have documentation for both the spreadsheet importer and Rapid Data Entry, as well as managing existing component lists in ArchivesSpace. Lastly, I've created complementary videos for the spreadsheet importer and Rapid Data Entry. Everything in our resource suite is a huge information dump, so many of our repositories (we have 26+) take the documentation we've created and pare it down for their purposes. We also have an unpublished training repository set up in ArchivesSpace that is specifically for practice. I like to point new users to the ArchivesSpace YouTube channel. There are a lot of useful basic ArchivesSpace tutorials. I hope that helps! Bri McLaughlin, she/her/hers Visiting Metadata Services Librarian Indiana University 812-856-3321 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Herzog, Nina A. Sent: Thursday, October 6, 2022 9:02 AM To: Archivesspace Users Group Subject: [External] Re: [Archivesspace_Users_Group] training a new staff member You don't often get email from herzogn at uncw.edu. Learn why this is important This message was sent from a non-IU address. Please exercise caution when clicking links or opening attachments from external sources. Hello Tara, My first experience with ArchivesSpace was in graduate school. After reading the manual, then working along with the staff, they showed me how to directly input data without using the spreadsheet. I have never used the spreadsheet and upload, I find it much easier to do direct input instead of the spreadsheet, it eliminates any issues with the spreadsheet not uploading correctly. Regards, Nina Herzog University Archives Library Specialist William Madison Randall Library University of North Carolina at Wilmington 601 South College Road Wilmington, NC 28403 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Tara Laver Sent: Monday, October 3, 2022 12:01 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] training a new staff member Some people who received this message don't often get email from tlaver at nelson-atkins.org. Learn why this is important [This email originated from outside of UNCW] Hello, I'm curious to learn how you have gone about introducing a new staff member to ArchivesSpace and training them. I have somebody starting who had a brief intro to it in school but has no real experience with it. Most of what they will be doing at first is resource record creation (multi-level) and loading via spreadsheet. I don't want to overwhelm but also think that because so much is interconnected that having a good sense of the bigger picture of how it all works would also be helpful. I'm trying to choose among the many training video options available on YouTube and from the help and tutorial pages. If you have suggestions on those for what has worked for you in the past or more generally how you have approached this, I would be grateful to hear. Many thanks, Tara Laver Tara Z. Laver (she/her/hers) Senior Archivist The Nelson-Atkins Museum of Art 4525 Oak Street Kansas City, MO 64111 Office: 816.751.1354 tlaver at nelson-atkins.org www.nelson-atkins.org [cid:image001.png at 01D8D96C.EFEF4380] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5175 bytes Desc: image001.png URL: From Ron.VandenBranden at antwerpen.be Thu Oct 6 12:24:47 2022 From: Ron.VandenBranden at antwerpen.be (Ron Van den Branden) Date: Thu, 6 Oct 2022 16:24:47 +0000 Subject: [Archivesspace_Users_Group] different date models for Agents vs Accessions, Resources, Archival Objects? In-Reply-To: References: Message-ID: Hi Christine, Many thanks for your helpful response, and pointers to those interesting issues! Best, Ron Van: archivesspace_users_group-bounces at lyralists.lyrasis.org Namens Christine Di Bella Verzonden: woensdag 5 oktober 2022 18:30 Aan: Archivesspace Users Group Onderwerp: Re: [Archivesspace_Users_Group] different date models for Agents vs Accessions, Resources, Archival Objects? Hello Ron, The divergence of the two date models within ArchivesSpace did come about with the work on the Agents module. While the plan is to eventually move other record types for which it makes sense to the same model (there are some related requests at https://archivesspace.atlassian.net/browse/ANW-1475 and https://archivesspace.atlassian.net/browse/ANW-380), because dates are so complex and because the agents work was underway already, we treated the work on dates associated with agents as a first step. The motivation for the change was specific to the EAC-CPF standard, though it has broader applicability with EAD as well. I don?t have a specific timeframe for moving other dates in the application to this model right now. One of our thoughts in staging this date transition was that we wanted to get feedback on the agents dates piece before taking the even larger step of moving the other record types (and migrating the associated data) to that model. We haven?t received much feedback on the agents yet, possibly because a lot of people haven?t upgraded to a 3.x version yet or possibly because the new date model meets their needs just fine. We are currently reviewing prioritized projects against capacity in light of staffing changes and I intend to share more information and an updated roadmap soon. I hope that helps. If you have other questions, or if anyone here has background or feedback specific to the agents date model, we?d be glad to have them. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Ron Van den Branden Sent: Wednesday, October 5, 2022 9:56 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] different date models for Agents vs Accessions, Resources, Archival Objects? Hi, I'm wondering why different date models exist for different record types in ArchivesSpace: * Accessions + Resources/Archival Objects: * Date Certainty: general certainty qualifier: "Approximate", "Inferred", "Questionable" * Agents: * Date Certainty: general certainty qualifier: "Approximate", "Inferred", "Questionable" * Standardized Date Type: specific qualifier for both Begin and End date: "Standard", "Not Before", "Not After" The extra field Standardized Date Type is occurring consistently for all date fields in the Agents module. This raises some questions: * What's the motivation for this difference? Is it standards-based, and does EAC-CPF allow for more detail than EAD? Or is is because the Agents module has been reworked more recently? * In the latter case, is any harmonization foreseen for the date fields in Accessions and Resources/Archival Objects? If so, is there a time frame? Many thanks for your thoughts! Best, Ron Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en Erfgoed Minderbroedersstraat 22, 2000 Antwerpen ? Grote Markt 1, 2000 Antwerpen gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 letterenhuis.be | instagram | facebook Proclaimer Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: From ndroark at anderson.edu Thu Oct 6 12:27:09 2022 From: ndroark at anderson.edu (Nic Stanton-Roark) Date: Thu, 6 Oct 2022 12:27:09 -0400 Subject: [Archivesspace_Users_Group] different date models for Agents vs Accessions, Resources, Archival Objects? In-Reply-To: References: Message-ID: Hi all, I will just chime in to say that we have found the new date functions in agents hugely helpful with describing local sources, and are very much looking forward to being able to use those functions in describing works, especially series and file components. NIC DON STANTON-ROARK Archivist Nicholson Library o: 765.641.4285 He/Him This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. On Wed, Oct 5, 2022 at 12:29 PM Christine Di Bella < christine.dibella at lyrasis.org> wrote: > Hello Ron, > > > > The divergence of the two date models within ArchivesSpace did come about > with the work on the Agents module. While the plan is to eventually move > other record types for which it makes sense to the same model (there are > some related requests at > https://archivesspace.atlassian.net/browse/ANW-1475 and > https://archivesspace.atlassian.net/browse/ANW-380), because dates are so > complex and because the agents work was underway already, we treated the > work on dates associated with agents as a first step. The motivation for > the change was specific to the EAC-CPF standard, though it has broader > applicability with EAD as well. > > > > I don?t have a specific timeframe for moving other dates in the > application to this model right now. One of our thoughts in staging this > date transition was that we wanted to get feedback on the agents dates > piece before taking the even larger step of moving the other record types > (and migrating the associated data) to that model. We haven?t received much > feedback on the agents yet, possibly because a lot of people haven?t > upgraded to a 3.x version yet or possibly because the new date model meets > their needs just fine. We are currently reviewing prioritized projects > against capacity in light of staffing changes and I intend to share more > information and an updated roadmap soon. > > > > I hope that helps. If you have other questions, or if anyone here has > background or feedback specific to the agents date model, we?d be glad to > have them. > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 > > 678-235-2905 > > > > [image: ASpaceOrgHomeMedium] > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Ron > Van den Branden > *Sent:* Wednesday, October 5, 2022 9:56 AM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] different date models for Agents > vs Accessions, Resources, Archival Objects? > > > > Hi, > > > > I'm wondering why different date models exist for different record types > in ArchivesSpace: > > > > - Accessions + Resources/Archival Objects: > - Date Certainty: general certainty qualifier: "Approximate", > "Inferred", "Questionable" > - Agents: > - Date Certainty: general certainty qualifier: "Approximate", > "Inferred", "Questionable" > - Standardized Date Type: specific qualifier for both Begin and End > date: "Standard", "Not Before", "Not After" > > > > The extra field Standardized Date Type is occurring consistently for all > date fields in the Agents module. > > > > This raises some questions: > > > > - What's the motivation for this difference? Is it standards-based, > and does EAC-CPF allow for more detail than EAD? Or is is because the > Agents module has been reworked more recently? > - In the latter case, is any harmonization foreseen for the date > fields in Accessions and Resources/Archival Objects? If so, is there a time > frame? > > > > Many thanks for your thoughts! > > > > Best, > > > > Ron > > > > *Ron Van den Branden | functioneel analist - applicatiebeheerder > Letterenhuis* > > Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en > Erfgoed > > Minderbroedersstraat 22, 2000 Antwerpen > > ? Grote Markt 1, 2000 Antwerpen > > gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 > > letterenhuis.be | instagram > | facebook > > > > > *Proclaimer* > > Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, > niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de > afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van > de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie > bevatten. Als stad nemen we privacy heel serieus en willen we als een goede > huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht > per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk > om het meteen te verwijderen en het niet verder te verspreiden of te > kopi?ren. > > > > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: not available URL: From mcallahan at smith.edu Thu Oct 6 12:49:35 2022 From: mcallahan at smith.edu (Maureen Cresci Callahan) Date: Thu, 6 Oct 2022 12:49:35 -0400 Subject: [Archivesspace_Users_Group] training a new staff member In-Reply-To: References: Message-ID: Just a plug that if your staff member would also like a refresher on how to think about the elements inside of ArchivesSpace once they learn how to use the application (how to write good description!), the technical subcommittee on DACS put together some very useful primer videos. It starts here, talking about what a content standard does and why it is useful, and goes from there! https://www.youtube.com/watch?v=X5toytzP8HM Enjoy, Maureen On Thu, Oct 6, 2022 at 10:21 AM McLaughlin, Brianna Jean wrote: > Hi, > > > > We have created a number of resources to train folks at Indiana > University. We have basic documentation, which is creating collection level > information in ArchivesSpace as well as a general introduction to > ArchivesSpace. We also have documentation for both the spreadsheet importer > and Rapid Data Entry, as well as managing existing component lists in > ArchivesSpace. Lastly, I?ve created complementary videos for the > spreadsheet importer and Rapid Data Entry. Everything in our resource suite > is a huge information dump, so many of our repositories (we have 26+) take > the documentation we?ve created and pare it down for their purposes. We > also have an unpublished training repository set up in ArchivesSpace that > is specifically for practice. > > > > I like to point new users to the ArchivesSpace YouTube channel. There are > a lot of useful basic ArchivesSpace tutorials. > > > > I hope that helps! > > > > Bri McLaughlin, she/her/hers > > Visiting Metadata Services Librarian > > Indiana University > > 812-856-3321 > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Herzog, > Nina A. > *Sent:* Thursday, October 6, 2022 9:02 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [External] Re: [Archivesspace_Users_Group] training a new > staff member > > > > You don't often get email from herzogn at uncw.edu. Learn why this is > important > > This message was sent from a non-IU address. Please exercise caution when > clicking links or opening attachments from external sources. > > > > Hello Tara, > > > > My first experience with ArchivesSpace was in graduate school. After > reading the manual, then working along with the staff, they showed me how > to directly input data without using the spreadsheet. I have never used the > spreadsheet and upload, I find it much easier to do direct input instead > of the spreadsheet, it eliminates any issues with the spreadsheet not > uploading correctly. > > > > Regards, > > > > Nina Herzog > > University Archives Library Specialist > > William Madison Randall Library > > University of North Carolina at Wilmington > > 601 South College Road > > Wilmington, NC 28403 > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Tara > Laver > *Sent:* Monday, October 3, 2022 12:01 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] training a new staff member > > > > Some people who received this message don't often get email from > tlaver at nelson-atkins.org. Learn why this is important > > > *[This email originated from outside of UNCW]* > > Hello, > > > > I?m curious to learn how you have gone about introducing a new staff > member to ArchivesSpace and training them. I have somebody starting who had > a brief intro to it in school but has no real experience with it. Most of > what they will be doing at first is resource record creation (multi-level) > and loading via spreadsheet. I don?t want to overwhelm but also think that > because so much is interconnected that having a good sense of the bigger > picture of how it all works would also be helpful. I?m trying to choose > among the many training video options available on YouTube and from the > help and tutorial pages. If you have suggestions on those for what has > worked for you in the past or more generally how you have approached this, > I would be grateful to hear. > > > > Many thanks, > > Tara Laver > > > > *Tara Z. Laver* > > (she/her/hers) > > > Senior Archivist > > The Nelson-Atkins Museum of Art > > 4525 Oak Street > > Kansas City, MO 64111 > > Office: 816.751.1354 > > tlaver at nelson-atkins.org > > www.nelson-atkins.org > > > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Maureen Cresci Callahan* Sophia Smith Collection Archivist Smith College Special Collections Northampton, Massachusetts 01063 voicemail: 413 585 2981 email: mcallahan at smith.edu videoconference: https://smith.zoom.us/my/maureen.callahan pronouns : she/her/hers Information about the Sophia Smith Collection of Women's history For current library access and services details, see Library Services During COVID-19 . -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5175 bytes Desc: not available URL: From Sarah.Tester at ccc.govt.nz Thu Oct 6 18:38:14 2022 From: Sarah.Tester at ccc.govt.nz (Tester, Sarah) Date: Thu, 6 Oct 2022 22:38:14 +0000 Subject: [Archivesspace_Users_Group] Event Type controlled value list error Message-ID: Kia ora all We're currently in the process of upgrading from v2.8.0 to v.3.2.0 and have come across the following issue: When logged in as Admin and trying to create, merge and delete values in the Event Type controlled value list, we have discovered that if the Request value is not attached to any records and is supressed no new values for this list can be created or existing values deleted. A red box appears with 'Failed to create Value'. Once the Request value is unsuppressed we are able to create and delete values as expected. We also cannot delete or merge the Request value, so we unsure as to whether this is somehow connected to another area of the system we don't currently have access to or use. The same issue occurs with the Event Outcome list when supressing the Cancelled value. Is this an issue that anyone else has come across or is known as part of this version upgrade? Many thanks Sarah Sarah Tester (she/her) Community Stories Liaison Digital Content [cid:image003.png at 01D8DA34.D046E010] 03 367 9963 [cid:image004.png at 01D8DA34.D046E010] Sarah.Tester at ccc.govt.nz [cid:image005.png at 01D8DA34.D046E010] Library 180 Smith Street, 180 Smith Street, Christchurch [cid:image006.png at 01D8DA34.D046E010] PO Box 73045, Christchurch 8154 [cid:image007.png at 01D8DA34.D046E010] ccc.govt.nz ________________________________ [cid:image008.png at 01D8DA34.D046E010] ********************************************************************** This electronic email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. The views expressed in this message are those of the individual sender and may not necessarily reflect the views of the Christchurch City Council. If you are not the correct recipient of this email please advise the sender and delete. Christchurch City Council http://www.ccc.govt.nz ********************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 651 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 668 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 685 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 729 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 713 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 3673 bytes Desc: image008.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 647 bytes Desc: image002.jpg URL: From andrew.morrison at bodleian.ox.ac.uk Mon Oct 10 12:43:56 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Mon, 10 Oct 2022 17:43:56 +0100 Subject: [Archivesspace_Users_Group] Event Type controlled value list error In-Reply-To: References: Message-ID: <9e4ce8ef-8d09-01f4-3be8-c96c39df3a14@bodleian.ox.ac.uk> It looks like this may have been fixed in the latest release: https://archivesspace.atlassian.net/browse/ANW-807 Andrew. On 06/10/2022 23:38, Tester, Sarah wrote: > > Kia ora all > > We?re currently in the process of upgrading from v2.8.0 to v.3.2.0 and > have come across the following issue: > > When logged in as Admin and trying to create, merge and delete values > in the Event Type controlled value list, we have discovered that if > the Request value is *not* attached to any records *and* is supressed > no new values for this list can be created or existing values deleted. > A red box appears with ?Failed to create Value?. Once the Request > value is unsuppressed we are able to create and delete values as > expected. We also cannot delete or merge the Request value, so we > unsure as to whether this is somehow connected to another area of the > system we don?t currently have access to or use. > > The same issue occurs with the Event Outcome list when supressing the > Cancelled value. > > Is this an issue that anyone else has come across or is known as part > of this version upgrade? > > Many thanks > > Sarah > > *Sarah Tester *(she/her)* > Community Stories Liaison > *Digital Content > > > > > > 03 367 9963 > > > > Sarah.Tester at ccc.govt.nz > > > > Library 180 Smith Street, 180 Smith Street, Christchurch > > > > PO Box 73045, Christchurch 8154 > > > > ccc.govt.nz > > ------------------------------------------------------------------------ > > ********************************************************************** > This electronic email and any files transmitted with it are intended > solely for the use of the individual or entity to whom they are addressed. > > The views expressed in this message are those of the individual sender > and may not necessarily reflect the views of the Christchurch City > Council. > If you are not the correct recipient of this email please advise the > sender and delete. > Christchurch City Council > http://www.ccc.govt.nz > ********************************************************************** > > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 647 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 651 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 668 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 685 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 729 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 713 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 3673 bytes Desc: not available URL: From scheirw at newschool.edu Mon Oct 10 17:00:13 2022 From: scheirw at newschool.edu (Wendy Scheir) Date: Mon, 10 Oct 2022 17:00:13 -0400 Subject: [Archivesspace_Users_Group] question about LCNAF import settings Message-ID: Hi, Can anyone point us in the direction of information about how to change the default settings for the LCNAF import? Currently it imports Publish? = False and we would like it to import Publish? = True. Many thanks, Wendy ____________________________________ WENDY SCHEIR director THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212-229-5942 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives [image: THE NEW SCHOOL] -------------- next part -------------- An HTML attachment was scrubbed... URL: From vaddonizio at atlas-sys.com Mon Oct 10 17:07:54 2022 From: vaddonizio at atlas-sys.com (Valerie Addonizio) Date: Mon, 10 Oct 2022 21:07:54 +0000 Subject: [Archivesspace_Users_Group] question about LCNAF import settings In-Reply-To: References: Message-ID: Wendy, There are no default settings for the importer in the interface, however, you can set the default publish status for all new records in the Preferences menu under the drop-down arrow next to your name in the upper-right. Try checking Publish? there and your next LCNAF import should be a published record. From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Wendy Scheir Sent: Monday, October 10, 2022 5:00 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] question about LCNAF import settings Hi, Can anyone point us in the direction of information about how to change the default settings for the LCNAF import? Currently it imports Publish? = False and we would like it to import Publish? = True. Many thanks, Wendy ____________________________________ WENDY SCHEIR director THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS 66 FIFTH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212-229-5942 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives [THE NEW SCHOOL] -------------- next part -------------- An HTML attachment was scrubbed... URL: From scheirw at newschool.edu Mon Oct 10 17:58:02 2022 From: scheirw at newschool.edu (Wendy Scheir) Date: Mon, 10 Oct 2022 17:58:02 -0400 Subject: [Archivesspace_Users_Group] question about LCNAF import settings In-Reply-To: References: Message-ID: Thank you, Valerie--I hadn't tried that so just did. I tried changing both Repository and Global Preferences, but it did not make the desired change in our instance. Any other ideas would be most welcome! Best, Wendy On Mon, Oct 10, 2022 at 5:08 PM Valerie Addonizio wrote: > Wendy, > > > > There are no default settings for the importer in the interface, however, > you can set the default publish status for all new records in the > Preferences menu under the drop-down arrow next to your name in the > upper-right. Try checking Publish? there and your next LCNAF import > *should* be a published record. > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Wendy > Scheir > *Sent:* Monday, October 10, 2022 5:00 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] question about LCNAF import > settings > > > > Hi, > > > > Can anyone point us in the direction of information about how to change > the default settings for the LCNAF import? Currently it imports Publish? = > False and we would like it to import Publish? = True. > > > > Many thanks, > > Wendy > > > > ____________________________________ > > *WENDY SCHEIR* > > director > THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS > > 66 FIFTH AVENUE, NEW YORK, NY 10011 > > scheirw at newschool.edu > > > *T* 212-229-5942 > > Explore the Archives | Digital > Collections from the Archives > | New School Histories > | @tnsarchives > > > [image: THE NEW SCHOOL] > _______________________________________________ > 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: From Sarah.Tester at ccc.govt.nz Wed Oct 12 16:49:06 2022 From: Sarah.Tester at ccc.govt.nz (Tester, Sarah) Date: Wed, 12 Oct 2022 20:49:06 +0000 Subject: [Archivesspace_Users_Group] Validation error: missing dates of existence label field Message-ID: Kia ora all As part of our upgrade from v2.8.0 to v.3.2.0 we have discovered that there is a missing Dates of Existence Label field when creating an Agent record. As this field is missing, when dates are entered we get a Validation error on saving the record. Our developers have posted the issue to GitHub but we haven't had any response to this yet. Is this something anyone on this list has come across? https://github.com/archivesspace/archivesspace/issues/2833 Cheers Sarah Sarah Tester (she/her) Community Stories Liaison Digital Content [cid:image003.png at 01D8DEE3.B4741AC0] 03 367 9963 [cid:image004.png at 01D8DEE3.B4741AC0] Sarah.Tester at ccc.govt.nz [cid:image005.png at 01D8DEE3.B4741AC0] Library 180 Smith Street, 180 Smith Street, Christchurch [cid:image006.png at 01D8DEE3.B4741AC0] PO Box 73045, Christchurch 8154 [cid:image007.png at 01D8DEE3.B4741AC0] ccc.govt.nz ________________________________ [cid:image008.png at 01D8DEE3.B4741AC0] ********************************************************************** This electronic email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. The views expressed in this message are those of the individual sender and may not necessarily reflect the views of the Christchurch City Council. If you are not the correct recipient of this email please advise the sender and delete. Christchurch City Council http://www.ccc.govt.nz ********************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 651 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 668 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 685 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 729 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 713 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 3673 bytes Desc: image008.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.jpg Type: image/jpeg Size: 647 bytes Desc: image009.jpg URL: From christine.dibella at lyrasis.org Wed Oct 12 18:27:13 2022 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 12 Oct 2022 22:27:13 +0000 Subject: [Archivesspace_Users_Group] Validation error: missing dates of existence label field In-Reply-To: References: Message-ID: Hello Sarah, Because being unable to validate agent records with dates of existence is not happening across the board, this sounds like an issue with your upgrade or possibly with a plugin you're running and how it interacts with 3.2.0. There were quite a few changes to the translations files between the version you moved from and the version you moved to. Depending on whether your translation files were customized before for earlier versions of ArchivesSpace, it's possible that not all the new or changed values were applied in the upgrade. Our tech folks should be able to help you sort that out. Of course, if others are experiencing this issue, please let us know. But I'm going to put a technical support ticket in for you on this, and you'll see another message directly to you about that in a little bit. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tester, Sarah Sent: Wednesday, October 12, 2022 4:49 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Validation error: missing dates of existence label field Kia ora all As part of our upgrade from v2.8.0 to v.3.2.0 we have discovered that there is a missing Dates of Existence Label field when creating an Agent record. As this field is missing, when dates are entered we get a Validation error on saving the record. Our developers have posted the issue to GitHub but we haven't had any response to this yet. Is this something anyone on this list has come across? https://github.com/archivesspace/archivesspace/issues/2833 Cheers Sarah Sarah Tester (she/her) Community Stories Liaison Digital Content [cid:image003.png at 01D8DE68.3F1BA110] 03 367 9963 [cid:image004.png at 01D8DE68.3F1BA110] Sarah.Tester at ccc.govt.nz [cid:image005.png at 01D8DE68.3F1BA110] Library 180 Smith Street, 180 Smith Street, Christchurch [cid:image006.png at 01D8DE68.3F1BA110] PO Box 73045, Christchurch 8154 [cid:image007.png at 01D8DE68.3F1BA110] ccc.govt.nz ________________________________ [cid:image008.png at 01D8DE68.3F1BA110] ********************************************************************** This electronic email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. The views expressed in this message are those of the individual sender and may not necessarily reflect the views of the Christchurch City Council. If you are not the correct recipient of this email please advise the sender and delete. Christchurch City Council http://www.ccc.govt.nz ********************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 647 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 651 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 668 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 685 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 729 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 713 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 3673 bytes Desc: image008.png URL: From Ron.VandenBranden at antwerpen.be Thu Oct 13 10:32:13 2022 From: Ron.VandenBranden at antwerpen.be (Ron Van den Branden) Date: Thu, 13 Oct 2022 14:32:13 +0000 Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? Message-ID: Hi, We?re in the process of migrating data to ArchivesSpace, and one thing I?m still struggling with is how to encode open-ended date ranges, using standardized dates only. In other words: how to express: * the fact that only a start date is known * or the fact that only an end date is known ?while still indicating this known date is the start / end of a range whose other end is not known; as opposite to expressing a precise singular/punctual date. Given the fact that ArchivesSpace currently uses 2 distinct date models for accessions, resources/archival objects and digital objects vs agents (see https://www.mail-archive.com/archivesspace_users_group at lyralists.lyrasis.org/msg05341.html), I?ll outline the observations and options I?m seeing. [1] Accessions, resources, archival objects, digital objects: * ?Single? date only offers a single date field, labeled ?Begin? * ?Inclusive? date offers both a ?Begin? and ?End? date field, only one of which is required Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as ?Begin? date * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ?inclusive? date, with known date as either ?Begin? or ?End? date ? This leads me to the question whether in practice ?single? dates are used at all for anything except accession dates, creation dates of digital objects, or as dates for only the lowest-level archival objects? [2] Agents: * ?Single? date only offers a single date field, which can be labeled as either ?Begin? or ?End? * ?Inclusive? date offers both a ?Begin? and ?End? date field, of which ?Begin? is mandatory Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as either ?Begin? or ?End? date Note: in EAC output, the begin/end qualification is dismissed: both are exported without distinction as e.g. 2022-10-08 * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ? ==> problem if only end date is known, since begin date is mandatory In other words: how would one differentiate between, e.g.: * birth date of a living person (1990 - ) * birth date of a deceased person, whose death date is unknown (1800 - ?) * death date of a person whose birth date is unknown (? - 1950) ? The documentation in the ArchivesSpace Help Center merely documents the different fields, but I couldn?t find much guidance on how to use them in practice. The DACS, EAD, and EAC documentation is rather sparse as well regarding open-ended date ranges. Therefore, any guidance on this matter would be much appreciated! Best, Ron Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en Erfgoed Minderbroedersstraat 22, 2000 Antwerpen ? Grote Markt 1, 2000 Antwerpen gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 letterenhuis.be | instagram | facebook Proclaimer Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcross at clemson.edu Thu Oct 13 10:56:01 2022 From: jcross at clemson.edu (James E. Cross) Date: Thu, 13 Oct 2022 14:56:01 +0000 Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? In-Reply-To: References: Message-ID: Another thought: use single date in both cases and let the ?Date Expression? field indicate that it is open-ended, i.e. single date ?1990,? date expression ?1990 - ? or single date ?1990,? date expression ?1990 (end date)? The date expression is what the user will see in the PUI. Jim James Cross Manuscripts Archivist Special Collections and Archives Clemson University Strom Thurmond Institute Building 230 Kappa Street Clemson, SC 29634 jcross at clemson.edu 864.656.5182 http://library.clemson.edu/specialcollections/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Ron Van den Branden Sent: Thursday, October 13, 2022 10:32 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? Hi, We?re in the process of migrating data to ArchivesSpace, and one thing I?m still struggling with is how to encode open-ended date ranges, using standardized dates only. In other words: how to express: * the fact that only a start date is known * or the fact that only an end date is known ?while still indicating this known date is the start / end of a range whose other end is not known; as opposite to expressing a precise singular/punctual date. Given the fact that ArchivesSpace currently uses 2 distinct date models for accessions, resources/archival objects and digital objects vs agents (see https://www.mail-archive.com/archivesspace_users_group at lyralists.lyrasis.org/msg05341.html), I?ll outline the observations and options I?m seeing. [1] Accessions, resources, archival objects, digital objects: * ?Single? date only offers a single date field, labeled ?Begin? * ?Inclusive? date offers both a ?Begin? and ?End? date field, only one of which is required Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as ?Begin? date * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ?inclusive? date, with known date as either ?Begin? or ?End? date ? This leads me to the question whether in practice ?single? dates are used at all for anything except accession dates, creation dates of digital objects, or as dates for only the lowest-level archival objects? [2] Agents: * ?Single? date only offers a single date field, which can be labeled as either ?Begin? or ?End? * ?Inclusive? date offers both a ?Begin? and ?End? date field, of which ?Begin? is mandatory Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as either ?Begin? or ?End? date Note: in EAC output, the begin/end qualification is dismissed: both are exported without distinction as e.g. 2022-10-08 * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ? ==> problem if only end date is known, since begin date is mandatory In other words: how would one differentiate between, e.g.: * birth date of a living person (1990 - ) * birth date of a deceased person, whose death date is unknown (1800 - ?) * death date of a person whose birth date is unknown (? - 1950) ? The documentation in the ArchivesSpace Help Center merely documents the different fields, but I couldn?t find much guidance on how to use them in practice. The DACS, EAD, and EAC documentation is rather sparse as well regarding open-ended date ranges. Therefore, any guidance on this matter would be much appreciated! Best, Ron Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en Erfgoed Minderbroedersstraat 22, 2000 Antwerpen ? Grote Markt 1, 2000 Antwerpen gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 letterenhuis.be | instagram | facebook Proclaimer Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kate_bowers at harvard.edu Thu Oct 13 10:57:12 2022 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Thu, 13 Oct 2022 14:57:12 +0000 Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? In-Reply-To: References: Message-ID: Can you explain the case for open-ended dates for resources, accessions, archival, or digital objects? From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Ron Van den Branden Sent: Thursday, October 13, 2022 10:32 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? Hi, We?re in the process of migrating data to ArchivesSpace, and one thing I?m still struggling with is how to encode open-ended date ranges, using standardized dates only. In other words: how to express: * the fact that only a start date is known * or the fact that only an end date is known ?while still indicating this known date is the start / end of a range whose other end is not known; as opposite to expressing a precise singular/punctual date. Given the fact that ArchivesSpace currently uses 2 distinct date models for accessions, resources/archival objects and digital objects vs agents (see https://www.mail-archive.com/archivesspace_users_group at lyralists.lyrasis.org/msg05341.html), I?ll outline the observations and options I?m seeing. [1] Accessions, resources, archival objects, digital objects: * ?Single? date only offers a single date field, labeled ?Begin? * ?Inclusive? date offers both a ?Begin? and ?End? date field, only one of which is required Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as ?Begin? date * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ?inclusive? date, with known date as either ?Begin? or ?End? date ? This leads me to the question whether in practice ?single? dates are used at all for anything except accession dates, creation dates of digital objects, or as dates for only the lowest-level archival objects? [2] Agents: * ?Single? date only offers a single date field, which can be labeled as either ?Begin? or ?End? * ?Inclusive? date offers both a ?Begin? and ?End? date field, of which ?Begin? is mandatory Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as either ?Begin? or ?End? date Note: in EAC output, the begin/end qualification is dismissed: both are exported without distinction as e.g. 2022-10-08 * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ? ==> problem if only end date is known, since begin date is mandatory In other words: how would one differentiate between, e.g.: * birth date of a living person (1990 - ) * birth date of a deceased person, whose death date is unknown (1800 - ?) * death date of a person whose birth date is unknown (? - 1950) ? The documentation in the ArchivesSpace Help Center merely documents the different fields, but I couldn?t find much guidance on how to use them in practice. The DACS, EAD, and EAC documentation is rather sparse as well regarding open-ended date ranges. Therefore, any guidance on this matter would be much appreciated! Best, Ron Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en Erfgoed Minderbroedersstraat 22, 2000 Antwerpen ? Grote Markt 1, 2000 Antwerpen gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 letterenhuis.be | instagram | facebook Proclaimer Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ron.VandenBranden at antwerpen.be Thu Oct 13 11:52:11 2022 From: Ron.VandenBranden at antwerpen.be (Ron Van den Branden) Date: Thu, 13 Oct 2022 15:52:11 +0000 Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? In-Reply-To: References: Message-ID: Hi Kate, I realize my analysis might have been biased by a data-oriented view on our current data, which contains quite a number of archival objects with only a start date, and some with only an end date. I?ve asked my colleagues, and open-ended dates are indeed uncommon for resources, accessions, archival, or digital objects: they?ll be mostly ranges with a known start and end date. How to interpret these single dates in our data is probably a matter of internal interpretation on our end, but still: what is the intended/preferred notation in ArchivesSpace? If the creation time span for a subseries is determined as e.g. 1969, how should this be encoded: * Single date * Begin date = 1969 * Inclusive date * Begin date = 1969 * End date = 1969 ? Best, Ron Van: archivesspace_users_group-bounces at lyralists.lyrasis.org Namens Bowers, Kate A. Verzonden: donderdag 13 oktober 2022 16:57 Aan: Archivesspace Users Group Onderwerp: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges? Can you explain the case for open-ended dates for resources, accessions, archival, or digital objects? From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Ron Van den Branden Sent: Thursday, October 13, 2022 10:32 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? Hi, We?re in the process of migrating data to ArchivesSpace, and one thing I?m still struggling with is how to encode open-ended date ranges, using standardized dates only. In other words: how to express: * the fact that only a start date is known * or the fact that only an end date is known ?while still indicating this known date is the start / end of a range whose other end is not known; as opposite to expressing a precise singular/punctual date. Given the fact that ArchivesSpace currently uses 2 distinct date models for accessions, resources/archival objects and digital objects vs agents (see https://www.mail-archive.com/archivesspace_users_group at lyralists.lyrasis.org/msg05341.html), I?ll outline the observations and options I?m seeing. [1] Accessions, resources, archival objects, digital objects: * ?Single? date only offers a single date field, labeled ?Begin? * ?Inclusive? date offers both a ?Begin? and ?End? date field, only one of which is required Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as ?Begin? date * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ?inclusive? date, with known date as either ?Begin? or ?End? date ? This leads me to the question whether in practice ?single? dates are used at all for anything except accession dates, creation dates of digital objects, or as dates for only the lowest-level archival objects? [2] Agents: * ?Single? date only offers a single date field, which can be labeled as either ?Begin? or ?End? * ?Inclusive? date offers both a ?Begin? and ?End? date field, of which ?Begin? is mandatory Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as either ?Begin? or ?End? date Note: in EAC output, the begin/end qualification is dismissed: both are exported without distinction as e.g. 2022-10-08 * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ? ==> problem if only end date is known, since begin date is mandatory In other words: how would one differentiate between, e.g.: * birth date of a living person (1990 - ) * birth date of a deceased person, whose death date is unknown (1800 - ?) * death date of a person whose birth date is unknown (? - 1950) ? The documentation in the ArchivesSpace Help Center merely documents the different fields, but I couldn?t find much guidance on how to use them in practice. The DACS, EAD, and EAC documentation is rather sparse as well regarding open-ended date ranges. Therefore, any guidance on this matter would be much appreciated! Best, Ron Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en Erfgoed Minderbroedersstraat 22, 2000 Antwerpen ? Grote Markt 1, 2000 Antwerpen gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 letterenhuis.be | instagram | facebook Proclaimer Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ron.VandenBranden at antwerpen.be Thu Oct 13 12:01:35 2022 From: Ron.VandenBranden at antwerpen.be (Ron Van den Branden) Date: Thu, 13 Oct 2022 16:01:35 +0000 Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? In-Reply-To: References: Message-ID: Hi Jim, Thanks for your thoughts. We?re aiming at minimizing the use of date expressions as much as possible, in order to: * Reduce the workload and avoid the need to record date information twice (once as date expression, once as standardized date) * Reduce the amount of possible input error and ambiguity caused by that redundancy In other words: if registrants have to enter a date, it would seem most efficient if they could express this as just a standardized date, which is both precise and machine-processable. Also, for exchangeability, a precise standardized representation of dates would seem preferable over date expressions, wouldn?t it? Best, Ron Van: archivesspace_users_group-bounces at lyralists.lyrasis.org Namens James E. Cross Verzonden: donderdag 13 oktober 2022 16:56 Aan: Archivesspace Users Group Onderwerp: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges? Another thought: use single date in both cases and let the ?Date Expression? field indicate that it is open-ended, i.e. single date ?1990,? date expression ?1990 - ? or single date ?1990,? date expression ?1990 (end date)? The date expression is what the user will see in the PUI. Jim James Cross Manuscripts Archivist Special Collections and Archives Clemson University Strom Thurmond Institute Building 230 Kappa Street Clemson, SC 29634 jcross at clemson.edu 864.656.5182 http://library.clemson.edu/specialcollections/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Ron Van den Branden Sent: Thursday, October 13, 2022 10:32 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? Hi, We?re in the process of migrating data to ArchivesSpace, and one thing I?m still struggling with is how to encode open-ended date ranges, using standardized dates only. In other words: how to express: * the fact that only a start date is known * or the fact that only an end date is known ?while still indicating this known date is the start / end of a range whose other end is not known; as opposite to expressing a precise singular/punctual date. Given the fact that ArchivesSpace currently uses 2 distinct date models for accessions, resources/archival objects and digital objects vs agents (see https://www.mail-archive.com/archivesspace_users_group at lyralists.lyrasis.org/msg05341.html), I?ll outline the observations and options I?m seeing. [1] Accessions, resources, archival objects, digital objects: * ?Single? date only offers a single date field, labeled ?Begin? * ?Inclusive? date offers both a ?Begin? and ?End? date field, only one of which is required Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as ?Begin? date * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ?inclusive? date, with known date as either ?Begin? or ?End? date ? This leads me to the question whether in practice ?single? dates are used at all for anything except accession dates, creation dates of digital objects, or as dates for only the lowest-level archival objects? [2] Agents: * ?Single? date only offers a single date field, which can be labeled as either ?Begin? or ?End? * ?Inclusive? date offers both a ?Begin? and ?End? date field, of which ?Begin? is mandatory Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as either ?Begin? or ?End? date Note: in EAC output, the begin/end qualification is dismissed: both are exported without distinction as e.g. 2022-10-08 * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ? ==> problem if only end date is known, since begin date is mandatory In other words: how would one differentiate between, e.g.: * birth date of a living person (1990 - ) * birth date of a deceased person, whose death date is unknown (1800 - ?) * death date of a person whose birth date is unknown (? - 1950) ? The documentation in the ArchivesSpace Help Center merely documents the different fields, but I couldn?t find much guidance on how to use them in practice. The DACS, EAD, and EAC documentation is rather sparse as well regarding open-ended date ranges. Therefore, any guidance on this matter would be much appreciated! Best, Ron Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en Erfgoed Minderbroedersstraat 22, 2000 Antwerpen ? Grote Markt 1, 2000 Antwerpen gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 letterenhuis.be | instagram | facebook Proclaimer Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmc35 at psu.edu Thu Oct 13 12:14:41 2022 From: kmc35 at psu.edu (Clair, Kevin) Date: Thu, 13 Oct 2022 16:14:41 +0000 Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? In-Reply-To: References: Message-ID: Hi Ron, ArchivesSpace doesn't require that both Begin and End fields are populated when the date type is Inclusive. We have a handful of dates in our database with an expression of "after" or "post" a particular year, where we've set the Begin to that year and left the End null. As far as indexing is concerned it gets us where we'd like to be. (Whether the ways we've done this in the past is DACS-compliant is a discussion for another time.) -k ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Ron Van den Branden Sent: Thursday, October 13, 2022 11:52 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges? Hi Kate, I realize my analysis might have been biased by a data-oriented view on our current data, which contains quite a number of archival objects with only a start date, and some with only an end date. I?ve asked my colleagues, and open-ended dates are indeed uncommon for resources, accessions, archival, or digital objects: they?ll be mostly ranges with a known start and end date. How to interpret these single dates in our data is probably a matter of internal interpretation on our end, but still: what is the intended/preferred notation in ArchivesSpace? If the creation time span for a subseries is determined as e.g. 1969, how should this be encoded: * Single date * Begin date = 1969 * Inclusive date * Begin date = 1969 * End date = 1969 ? Best, Ron Van: archivesspace_users_group-bounces at lyralists.lyrasis.org Namens Bowers, Kate A. Verzonden: donderdag 13 oktober 2022 16:57 Aan: Archivesspace Users Group Onderwerp: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges? Can you explain the case for open-ended dates for resources, accessions, archival, or digital objects? From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Ron Van den Branden Sent: Thursday, October 13, 2022 10:32 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? Hi, We?re in the process of migrating data to ArchivesSpace, and one thing I?m still struggling with is how to encode open-ended date ranges, using standardized dates only. In other words: how to express: * the fact that only a start date is known * or the fact that only an end date is known ?while still indicating this known date is the start / end of a range whose other end is not known; as opposite to expressing a precise singular/punctual date. Given the fact that ArchivesSpace currently uses 2 distinct date models for accessions, resources/archival objects and digital objects vs agents (see https://www.mail-archive.com/archivesspace_users_group at lyralists.lyrasis.org/msg05341.html), I?ll outline the observations and options I?m seeing. [1] Accessions, resources, archival objects, digital objects: * ?Single? date only offers a single date field, labeled ?Begin? * ?Inclusive? date offers both a ?Begin? and ?End? date field, only one of which is required Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as ?Begin? date * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ?inclusive? date, with known date as either ?Begin? or ?End? date ? This leads me to the question whether in practice ?single? dates are used at all for anything except accession dates, creation dates of digital objects, or as dates for only the lowest-level archival objects? [2] Agents: * ?Single? date only offers a single date field, which can be labeled as either ?Begin? or ?End? * ?Inclusive? date offers both a ?Begin? and ?End? date field, of which ?Begin? is mandatory Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as either ?Begin? or ?End? date Note: in EAC output, the begin/end qualification is dismissed: both are exported without distinction as e.g. 2022-10-08 * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ? ==> problem if only end date is known, since begin date is mandatory In other words: how would one differentiate between, e.g.: * birth date of a living person (1990 - ) * birth date of a deceased person, whose death date is unknown (1800 - ?) * death date of a person whose birth date is unknown (? - 1950) ? The documentation in the ArchivesSpace Help Center merely documents the different fields, but I couldn?t find much guidance on how to use them in practice. The DACS, EAD, and EAC documentation is rather sparse as well regarding open-ended date ranges. Therefore, any guidance on this matter would be much appreciated! Best, Ron Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en Erfgoed Minderbroedersstraat 22, 2000 Antwerpen ? Grote Markt 1, 2000 Antwerpen gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 letterenhuis.be | instagram | facebook Proclaimer Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmichelson at smith.edu Thu Oct 13 12:50:12 2022 From: dmichelson at smith.edu (Dan Michelson) Date: Thu, 13 Oct 2022 12:50:12 -0400 Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? In-Reply-To: References: Message-ID: Hi All, Just as a quick addition to this conversation, there is an approved ticket pending development that would (in my biased opinion) greatly improve how date records are structured and created in ArchivesSpace. If this were implemented right now, you could simply import the records as inclusive dates with a date begin of 1969 and a date end of 2022 (with certainty set to "not after" on the end date). All the best, Dan On Thu, Oct 13, 2022 at 12:14 PM Clair, Kevin wrote: > Hi Ron, > > ArchivesSpace doesn't require that both Begin and End fields are populated > when the date type is Inclusive. We have a handful of dates in our database > with an expression of "after" or "post" a particular year, where we've set > the Begin to that year and left the End null. As far as indexing is > concerned it gets us where we'd like to be. > > (Whether the ways we've done this in the past is DACS-compliant is a > discussion for another time.) -k > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Ron > Van den Branden > *Sent:* Thursday, October 13, 2022 11:52 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] how to encode open-ended date > ranges? > > > Hi Kate, > > > > I realize my analysis might have been biased by a data-oriented view on > our current data, which contains quite a number of archival objects with > only a start date, and some with only an end date. I?ve asked my > colleagues, and open-ended dates are indeed uncommon for resources, > accessions, archival, or digital objects: they?ll be mostly ranges with a > known start and end date. > > > > How to interpret these single dates in our data is probably a matter of > internal interpretation on our end, but still: what is the > intended/preferred notation in ArchivesSpace? If the creation time span for > a subseries is determined as e.g. 1969, how should this be encoded: > > - Single date > - Begin date = 1969 > - Inclusive date > - Begin date = 1969 > - End date = 1969 > > ? > > > > Best, > > > > Ron > > > > *Van:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *Namens *Bowers, > Kate A. > *Verzonden:* donderdag 13 oktober 2022 16:57 > *Aan:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Onderwerp:* Re: [Archivesspace_Users_Group] how to encode open-ended > date ranges? > > > > Can you explain the case for open-ended dates for resources, accessions, > archival, or digital objects? > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Ron > Van den Branden > *Sent:* Thursday, October 13, 2022 10:32 AM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] how to encode open-ended date > ranges? > > > > Hi, > > > > We?re in the process of migrating data to ArchivesSpace, and one thing I?m > still struggling with is how to encode open-ended date ranges, using > standardized dates only. In other words: how to express: > > - the fact that only a start date is known > - or the fact that only an end date is known > > ?while still indicating this known date is the start / end of a range > whose other end is not known; as opposite to expressing a precise > singular/punctual date. > > > > Given the fact that ArchivesSpace currently uses 2 distinct date models > for accessions, resources/archival objects and digital objects vs agents > (see > https://www.mail-archive.com/archivesspace_users_group at lyralists.lyrasis.org/msg05341.html > ), > I?ll outline the observations and options I?m seeing. > > > > [1] Accessions, resources, archival objects, digital objects: > > - ?Single? date only offers a single date field, labeled ?Begin? > - ?Inclusive? date offers both a ?Begin? and ?End? date field, only > one of which is required > > Would this be a good strategy: > > - ?singular/punctual? dates: ?single? date, one value as ?Begin? date > - date range: ?inclusive? date, start and end dates as ?Begin? and > ?End? dates, respectively > - open-ended date range: ?inclusive? date, with known date as either > ?Begin? or ?End? date > > ? > > This leads me to the question whether in practice ?single? dates are used > at all for anything except accession dates, creation dates of digital > objects, or as dates for only the lowest-level archival objects? > > > > [2] Agents: > > - ?Single? date only offers a single date field, which can be labeled > as either ?Begin? or ?End? > - ?Inclusive? date offers both a ?Begin? and ?End? date field, of > which ?Begin? is mandatory > > Would this be a good strategy: > > - ?singular/punctual? dates: ?single? date, one value as either > ?Begin? or ?End? date > > Note: in EAC output, the begin/end qualification is dismissed: both are > exported without distinction as e.g. > 2022-10-08 > > - date range: ?inclusive? date, start and end dates as ?Begin? and > ?End? dates, respectively > > > - open-ended date range: ? > ? problem if only end date is known, since begin date is mandatory > > In other words: how would one differentiate between, e.g.: > > - birth date of a living person (1990 - ) > - birth date of a deceased person, whose death date is unknown (1800 - > ?) > - death date of a person whose birth date is unknown (? - 1950) > > ? > > > > The documentation in the ArchivesSpace Help Center merely documents the > different fields, but I couldn?t find much guidance on how to use them in > practice. The DACS, EAD, and EAC documentation is rather sparse as well > regarding open-ended date ranges. Therefore, any guidance on this matter > would be much appreciated! > > > > Best, > > > > Ron > > > > *Ron Van den Branden | functioneel analist - applicatiebeheerder > Letterenhuis* > > Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en > Erfgoed > > Minderbroedersstraat 22, 2000 Antwerpen > > ? Grote Markt 1, 2000 Antwerpen > > gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 > > letterenhuis.be > > | instagram > > | facebook > > > > > *Proclaimer* > > Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, > niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de > afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van > de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie > bevatten. Als stad nemen we privacy heel serieus en willen we als een goede > huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht > per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk > om het meteen te verwijderen en het niet verder te verspreiden of te > kopi?ren. > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Dan Michelson Collections Archivist Smith College Special Collections For current library access and services details, see Library Services During COVID-19 . -------------- next part -------------- An HTML attachment was scrubbed... URL: From benn.joseph at northwestern.edu Thu Oct 13 14:09:19 2022 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Thu, 13 Oct 2022 18:09:19 +0000 Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? In-Reply-To: References: Message-ID: We?re largely trying to avoid using date expressions too, for the same reasons?and this ticket is something we?re hoping will be approved at some point to make the normalized dates a little easier to read for users. --Benn From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Ron Van den Branden Sent: Thursday, October 13, 2022 11:02 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges? Hi Jim, Thanks for your thoughts. We?re aiming at minimizing the use of date expressions as much as possible, in order to: * Reduce the workload and avoid the need to record date information twice (once as date expression, once as standardized date) * Reduce the amount of possible input error and ambiguity caused by that redundancy In other words: if registrants have to enter a date, it would seem most efficient if they could express this as just a standardized date, which is both precise and machine-processable. Also, for exchangeability, a precise standardized representation of dates would seem preferable over date expressions, wouldn?t it? Best, Ron Van: archivesspace_users_group-bounces at lyralists.lyrasis.org > Namens James E. Cross Verzonden: donderdag 13 oktober 2022 16:56 Aan: Archivesspace Users Group > Onderwerp: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges? Another thought: use single date in both cases and let the ?Date Expression? field indicate that it is open-ended, i.e. single date ?1990,? date expression ?1990 - ? or single date ?1990,? date expression ?1990 (end date)? The date expression is what the user will see in the PUI. Jim James Cross Manuscripts Archivist Special Collections and Archives Clemson University Strom Thurmond Institute Building 230 Kappa Street Clemson, SC 29634 jcross at clemson.edu 864.656.5182 http://library.clemson.edu/specialcollections/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Ron Van den Branden Sent: Thursday, October 13, 2022 10:32 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? Hi, We?re in the process of migrating data to ArchivesSpace, and one thing I?m still struggling with is how to encode open-ended date ranges, using standardized dates only. In other words: how to express: * the fact that only a start date is known * or the fact that only an end date is known ?while still indicating this known date is the start / end of a range whose other end is not known; as opposite to expressing a precise singular/punctual date. Given the fact that ArchivesSpace currently uses 2 distinct date models for accessions, resources/archival objects and digital objects vs agents (see https://www.mail-archive.com/archivesspace_users_group at lyralists.lyrasis.org/msg05341.html), I?ll outline the observations and options I?m seeing. [1] Accessions, resources, archival objects, digital objects: * ?Single? date only offers a single date field, labeled ?Begin? * ?Inclusive? date offers both a ?Begin? and ?End? date field, only one of which is required Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as ?Begin? date * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ?inclusive? date, with known date as either ?Begin? or ?End? date ? This leads me to the question whether in practice ?single? dates are used at all for anything except accession dates, creation dates of digital objects, or as dates for only the lowest-level archival objects? [2] Agents: * ?Single? date only offers a single date field, which can be labeled as either ?Begin? or ?End? * ?Inclusive? date offers both a ?Begin? and ?End? date field, of which ?Begin? is mandatory Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as either ?Begin? or ?End? date Note: in EAC output, the begin/end qualification is dismissed: both are exported without distinction as e.g. 2022-10-08 * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ? ==> problem if only end date is known, since begin date is mandatory In other words: how would one differentiate between, e.g.: * birth date of a living person (1990 - ) * birth date of a deceased person, whose death date is unknown (1800 - ?) * death date of a person whose birth date is unknown (? - 1950) ? The documentation in the ArchivesSpace Help Center merely documents the different fields, but I couldn?t find much guidance on how to use them in practice. The DACS, EAD, and EAC documentation is rather sparse as well regarding open-ended date ranges. Therefore, any guidance on this matter would be much appreciated! Best, Ron Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en Erfgoed Minderbroedersstraat 22, 2000 Antwerpen ? Grote Markt 1, 2000 Antwerpen gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 letterenhuis.be | instagram | facebook Proclaimer Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren. -------------- next part -------------- An HTML attachment was scrubbed... URL: From edgar-garcia at northwestern.edu Thu Oct 13 17:16:08 2022 From: edgar-garcia at northwestern.edu (Edgar Garcia) Date: Thu, 13 Oct 2022 21:16:08 +0000 Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? In-Reply-To: References: Message-ID: I'd like to add, as someone previously on the Dev-Pri group, if you have interest in the feature that Benn pointed to which he submitted, clicking on Watch, and Voting for the ticket (available after logging into Jira near the upper right portion) will greatly help in getting this ticket completed. I can see that the ticket was already passed into ready for implementation back in February and is waiting to be picked up but with more activity, a developer might pick it up faster. Regards, Edgar Edgar Garcia Senior Software Developer IT Infrastructure Northwestern University Libraries Evanston, IL ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Benn Joseph Sent: Thursday, October 13, 2022 1:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges? We?re largely trying to avoid using date expressions too, for the same reasons?and this ticket is something we?re hoping will be approved at some point to make the normalized dates a little easier to read for users. --Benn From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Ron Van den Branden Sent: Thursday, October 13, 2022 11:02 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges? Hi Jim, Thanks for your thoughts. We?re aiming at minimizing the use of date expressions as much as possible, in order to: * Reduce the workload and avoid the need to record date information twice (once as date expression, once as standardized date) * Reduce the amount of possible input error and ambiguity caused by that redundancy In other words: if registrants have to enter a date, it would seem most efficient if they could express this as just a standardized date, which is both precise and machine-processable. Also, for exchangeability, a precise standardized representation of dates would seem preferable over date expressions, wouldn?t it? Best, Ron Van: archivesspace_users_group-bounces at lyralists.lyrasis.org > Namens James E. Cross Verzonden: donderdag 13 oktober 2022 16:56 Aan: Archivesspace Users Group > Onderwerp: Re: [Archivesspace_Users_Group] how to encode open-ended date ranges? Another thought: use single date in both cases and let the ?Date Expression? field indicate that it is open-ended, i.e. single date ?1990,? date expression ?1990 - ? or single date ?1990,? date expression ?1990 (end date)? The date expression is what the user will see in the PUI. Jim James Cross Manuscripts Archivist Special Collections and Archives Clemson University Strom Thurmond Institute Building 230 Kappa Street Clemson, SC 29634 jcross at clemson.edu 864.656.5182 http://library.clemson.edu/specialcollections/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Ron Van den Branden Sent: Thursday, October 13, 2022 10:32 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] how to encode open-ended date ranges? Hi, We?re in the process of migrating data to ArchivesSpace, and one thing I?m still struggling with is how to encode open-ended date ranges, using standardized dates only. In other words: how to express: * the fact that only a start date is known * or the fact that only an end date is known ?while still indicating this known date is the start / end of a range whose other end is not known; as opposite to expressing a precise singular/punctual date. Given the fact that ArchivesSpace currently uses 2 distinct date models for accessions, resources/archival objects and digital objects vs agents (see https://www.mail-archive.com/archivesspace_users_group at lyralists.lyrasis.org/msg05341.html), I?ll outline the observations and options I?m seeing. [1] Accessions, resources, archival objects, digital objects: * ?Single? date only offers a single date field, labeled ?Begin? * ?Inclusive? date offers both a ?Begin? and ?End? date field, only one of which is required Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as ?Begin? date * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ?inclusive? date, with known date as either ?Begin? or ?End? date ? This leads me to the question whether in practice ?single? dates are used at all for anything except accession dates, creation dates of digital objects, or as dates for only the lowest-level archival objects? [2] Agents: * ?Single? date only offers a single date field, which can be labeled as either ?Begin? or ?End? * ?Inclusive? date offers both a ?Begin? and ?End? date field, of which ?Begin? is mandatory Would this be a good strategy: * ?singular/punctual? dates: ?single? date, one value as either ?Begin? or ?End? date Note: in EAC output, the begin/end qualification is dismissed: both are exported without distinction as e.g. 2022-10-08 * date range: ?inclusive? date, start and end dates as ?Begin? and ?End? dates, respectively * open-ended date range: ? ==> problem if only end date is known, since begin date is mandatory In other words: how would one differentiate between, e.g.: * birth date of a living person (1990 - ) * birth date of a deceased person, whose death date is unknown (1800 - ?) * death date of a person whose birth date is unknown (? - 1950) ? The documentation in the ArchivesSpace Help Center merely documents the different fields, but I couldn?t find much guidance on how to use them in practice. The DACS, EAD, and EAC documentation is rather sparse as well regarding open-ended date ranges. Therefore, any guidance on this matter would be much appreciated! Best, Ron Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving | Musea en Erfgoed Minderbroedersstraat 22, 2000 Antwerpen ? Grote Markt 1, 2000 Antwerpen gsm +32 0485 02 80 50 | tel. +32 3 222 93 30 letterenhuis.be | instagram | facebook Proclaimer Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk offici?le documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopi?ren. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Oct 17 09:50:56 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 17 Oct 2022 13:50:56 +0000 Subject: [Archivesspace_Users_Group] Join the ArchivesSpace Trainers Corps for their next Office Hour on Wednesday, November 30, at 2pm ET/11am PT In-Reply-To: References: Message-ID: Dear ArchivesSpace Users, Join the ArchivesSpace Trainers Corps for their next ?Office Hour? on Wednesday, November 30, at 2pm ET/11am PT. In these office hours, members of the ArchivesSpace Trainers Corps demo a task or tool frequently used by ArchivesSpace users and take questions related to the demo and topic. For this open call, the Trainers Corps will briefly demo spawning functionality, including enhancements beginning with the 3.3 versions of ArchivesSpace. Following the presentation, you will have the opportunity to ask questions about the topic, followed by a general Q&A about spawning in ArchivesSpace. ArchivesSpace Trainers Corps ?Office Hour? Date: November 30, 2022 Time: 2:00pm ET / 11:00am PT Topic: Spawning Functionality in ArchivesSpace Registration: https://lyrasis.zoom.us/meeting/register/tZMlc-CrrjooHNZ46CeQu55vxUAot1lrs4_p Community discussions like the Trainers Corps office hour are not recorded but notes will be made available on the ArchivesSpace wiki in the days following the session. If you have any questions, feel free to contact us at ArchivesSpaceHome at lyrasis.org. Best, Jessica Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From reesj at mail.nlm.nih.gov Mon Oct 17 12:18:36 2022 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Mon, 17 Oct 2022 16:18:36 +0000 Subject: [Archivesspace_Users_Group] Hard re-indexing question Message-ID: Hi all, We recently tried a hard re-index and discovered that for the PUI, subjects linked only to digital objects were not re-indexed and dropped from the PUI. Is this expected behavior? Related, is there a table/tables in the dbase that tell Solr when to index that we could investigate, as opposed to the soft-reindex approach of deleting the data directory? Our developers are experienced controlling indexing in our Blacklight apps via a specific table its Solr looks at, for example, and are trying to understand aspace behavior a bit more. Thanks, John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Mon Oct 17 12:48:09 2022 From: blake.carver at lyrasis.org (Blake Carver) Date: Mon, 17 Oct 2022 16:48:09 +0000 Subject: [Archivesspace_Users_Group] Hard re-indexing question In-Reply-To: References: Message-ID: >> We recently tried a hard re-index and discovered that for the PUI, subjects linked only to digital objects were not re-indexed and dropped from the PUI. Is this expected behavior? Maybe related to what's in your deleted_records table? How many rows in that table? >> Related, is there a table/tables in the dbase that tell Solr when to index that we could investigate, Many things have a system_mtime that you can set to NOW(). -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Tue Oct 18 04:09:07 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Tue, 18 Oct 2022 09:09:07 +0100 Subject: [Archivesspace_Users_Group] Hard re-indexing question In-Reply-To: References: Message-ID: There is a bug involving the "deleted_records" table that can cause records to disappear after a re-index: https://archivesspace.atlassian.net/browse/ANW-1607 But it only affects things that have been transferred from one repository to another, then back again. And that doesn't apply to subjects, as they don't belong to any one repository. There could be another mechanism to trigger than same bug for subjects, if so the SQL file attached to that issue could be adapted to find and fix them. If subjects are missing from the public interface but not from the staff interface, then it is a problem with the indexer, or the code it calls to check that each subject is linked to at least one published record. Andrew. On 17/10/2022 17:48, Blake Carver wrote: > > >> We recently tried a hard re-index and discovered that for the PUI, > subjects linked only to digital objects were not re-indexed and > dropped from the PUI. Is this expected behavior? > > > Maybe related to what's in your deleted_records table? How many rows > in that table? > > >> Related, is there a table/tables in the dbase that tell Solr when > to index that we could investigate, > > > Many things have a system_mtime that you can set to NOW(). > > > > _______________________________________________ > 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: From reesj at mail.nlm.nih.gov Tue Oct 18 08:53:55 2022 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Tue, 18 Oct 2022 12:53:55 +0000 Subject: [Archivesspace_Users_Group] [EXTERNAL] Re: Hard re-indexing question In-Reply-To: References: Message-ID: Thanks. They weren't deleted records, but published-then-suppressed records. Being once published, their subject terms were published and then persisted as ghost terms in the PUI with no linked records. Until either the subject term was touched (when we ran the full re-index) or the published state of the DO record was toggled (suppression doesn't change system_mtime), subject terms weren't re-indexed for the PUI. We learned something new. John From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Andrew Morrison Sent: Tuesday, October 18, 2022 4:09 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] Hard re-indexing question There is a bug involving the "deleted_records" table that can cause records to disappear after a re-index: https://archivesspace.atlassian.net/browse/ANW-1607 But it only affects things that have been transferred from one repository to another, then back again. And that doesn't apply to subjects, as they don't belong to any one repository. There could be another mechanism to trigger than same bug for subjects, if so the SQL file attached to that issue could be adapted to find and fix them. If subjects are missing from the public interface but not from the staff interface, then it is a problem with the indexer, or the code it calls to check that each subject is linked to at least one published record. Andrew. On 17/10/2022 17:48, Blake Carver wrote: >> We recently tried a hard re-index and discovered that for the PUI, subjects linked only to digital objects were not re-indexed and dropped from the PUI. Is this expected behavior? Maybe related to what's in your deleted_records table? How many rows in that table? >> Related, is there a table/tables in the dbase that tell Solr when to index that we could investigate, Many things have a system_mtime that you can set to NOW(). _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matsuyama-h at nakka-art.jp Tue Oct 18 22:52:29 2022 From: matsuyama-h at nakka-art.jp (=?utf-8?B?5p2+5bGx44CA44Gy44Go44G/?=) Date: Wed, 19 Oct 2022 02:52:29 +0000 Subject: [Archivesspace_Users_Group] Missing Japanese charactires in a PUI generated PDF In-Reply-To: References: <8F23C982-43E0-49A1-A8FB-CD37ABBA1EEC@harvard.edu> <322750FA-FA40-4251-A9BC-835005217DE6@ou.edu> Message-ID: Hi again, There is an update on this topic. We tried the way, PUI customization plugin, that Dave kindly shared. However, we haven?t got Japanese texts yet; an outcome attached, and we?ve been stuck. If there is anything missing or wrong, please let us know. Any suggestions would be greatly appreciated! What we did is the following; 1. put the 24 files in the archivesspace/lib directory. 2. put the Kurinto fonts in the stylesheets/fonts. 3. put the sources from Github in our directory as follows. - plugins/local/public/models/hvd_pdf.rb - plugins/local/public/models/finding_aid_pdf.rb - plugins/local/public/models/fixup_document.rb which you didn?t specify, but we used because it?s lorded with hvd_pdf.rb. Our ArchivesSpace is v3.0.1. Thanks! Hitomi Matsuyama, Audiovisual Archivist Nakanoshima Museum of Art, Osaka 4-3-1 Nakanoshima, Kita-ku Osaka 530-0005 JAPAN tel. +81 (0)6 64 79 05 58 email. matsuyama-h at nakka-art.jp From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of ?????? Sent: Saturday, September 17, 2022 5:45 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Missing Japanese charactires in a PUI generated PDF Dear Dave and Bailey, Thanks a lot for both of your practical advice! We?ll try to follow Dave?s instruction first, though it?ll take some time. We'll update you on what we get after this implementation, with questions or a better solution. Hitomi Hitomi Matsuyama, Audiovisual Archivist Nakanoshima Museum of Art, Osaka 4-3-1 Nakanoshima, Kita-ku Osaka 530-0005 JAPAN tel. +81 (0)6 64 79 05 58 email. matsuyama-h at nakka-art.jp From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Hoffner, Bailey E. Sent: Thursday, September 15, 2022 11:53 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Missing Japanese charactires in a PUI generated PDF As a follow-up, we?ve had the same issue with Chinese language characters and, the stop-gap workaround we?re using at the moment until we can implement a better solution, is to use the the New School Bulk Updater plugin to export a spreadsheet for the finding aid which then at least serves as an easy-to-generate searchable file outside of AS, even though it?s not the same experience as a PDF. Good luck and we?ll continue to tune into these language-based questions related to AS! -Bailey Bailey Hoffner, MLIS Pronouns: she/her or they/them Metadata and Collections Management Archivist University of Oklahoma Libraries baileys at ou.edu From: > on behalf of "Mayo, Dave" > Reply-To: Archivesspace Users Group > Date: Wednesday, September 14, 2022 at 10:01 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Missing Japanese charactires in a PUI generated PDF Hi! This is something we?ve recently had to deal with ? I?m not 100% sure from what you?ve posted that it?s the same issue we had, but there are a few issues with the PUI?s current PDF generation support that make font handling challenging. So, first of all ? if you?re setting up a fallback hierarchy and the font with Japanese characters isn?t in the first position, the PDF generation library isn?t seeing it at all. The flying saucer ipdf library doesn?t support font fallback, which is a real problem if you need to support multiple languages. So, first thing I?d try is making sure that the text in question is _solely_ the font supporting Japanese. If the Japanese characters render, that?ll at least verify that that?s the reason. Our solution, which I?m hoping to work up and submit as a pull request, was to replace the existing library with https://github.com/danfickle/openhtmltopdf - a project based on flying saucer but with several enhancements. Implementing it is somewhat complex: 1. Openhtmltopdf and _all dependencies thereof_ need to be provided by putting them in the archivesspace/lib directory (the directory the MySQL connector goes in during install) Currently we?re doing this in our dockerfile via: wget -P /archivesspace/lib https://repo1.maven.org/maven2/com/google/zxing/core/3.5.0/core-3.5.0.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/junit/junit/4.13.2/junit-4.13.2.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/com/openhtmltopdf/openhtmltopdf-core/1.0.10/openhtmltopdf-core-1.0.10.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/com/openhtmltopdf/openhtmltopdf-pdfbox/1.0.10/openhtmltopdf-pdfbox-1.0.10.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/de/rototor/pdfbox/graphics2d/0.34/graphics2d-0.34.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/apache/pdfbox/pdfbox/2.0.26/pdfbox-2.0.26.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/apache/pdfbox/xmpbox/2.0.26/xmpbox-2.0.26.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/apache/pdfbox/fontbox/2.0.26/fontbox-2.0.26.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/jfree/jfreechart/1.5.3/jfreechart-1.5.3.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/freemarker/freemarker/2.3.27-incubating/freemarker-2.3.27-incubating.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.rhino/1.7.10_1/org.apache.servicemix.bundles.rhino-1.7.10_1-sources.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/openjdk/jmh/jmh-core/1.29/jmh-core-1.29.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/codelibs/jhighlight/1.1.0/jhighlight-1.1.0.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/thymeleaf/extras/thymeleaf-extras-java8time/3.0.4.RELEASE/thymeleaf-extras-java8time-3.0.4.RELEASE.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/thymeleaf/thymeleaf/3.1.0.M2/thymeleaf-3.1.0.M2.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/com/ibm/icu/icu4j/59.1/icu4j-59.1.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/apache/xmlgraphics/batik-codec/1.14/batik-codec-1.14.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/apache/xmlgraphics/batik-ext/1.14/batik-ext-1.14.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/apache/xmlgraphics/batik-transcoder/1.14/batik-transcoder-1.14.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/apache/xmlgraphics/xmlgraphics-commons/2.7/xmlgraphics-commons-2.7.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/org/verapdf/validation-model/1.18.8/validation-model-1.18.8.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/de/rototor/snuggletex/snuggletex-core/1.3.0/snuggletex-core-1.3.0.jar && \ wget -P /archivesspace/lib https://repo1.maven.org/maven2/net/sourceforge/jeuclid/jeuclid-core/3.1.9/jeuclid-core-3.1.9.jar && \ 2. Then, the code that generates the PDFs needs to be overridden with code based on the new library. We do this in our PUI customization plugin here: https://github.com/harvard-library/aspace-hvd-pui/blob/bd4b1c3cf728674cc3445dee39a16282848c2cca/public/models/hvd_pdf.rb#L152 We were already overriding PDF generation, the model in core ArchivesSpace is located here: https://github.com/archivesspace/archivesspace/blob/ceeb72d1796a8b67104814065ffea23215403f78/public/app/models/finding_aid_pdf.rb#L94 I believe my co-worker Doug still couldn?t get a web font to work ever really ? we ended up using the Kurinto fonts (and some others) provided with archivesspace and used by the XSLT PDF processing in the backend. https://github.com/harvard-library/aspace-hvd-pui/blob/bd4b1c3cf728674cc3445dee39a16282848c2cca/public/models/hvd_pdf.rb#L165 I hope this is somewhat helpful! I very much want to try and package this up in a less terrible way, either by getting this incorporated into core or through creating a plugin ? a plugin would need to either copy the libraries into the right place on install or have a manual step of downloading and installing the libraries, so it?d be a bit inelegant. If you have any questions, I?d be happy to try and answer them! -- Dave Mayo (he/him) Senior Digital Library Software Engineer Harvard University > HUIT > LTS From: > on behalf of ?????? > Reply-To: Archivesspace Users Group > Date: Tuesday, September 13, 2022 at 9:41 PM To: "'archivesspace_users_group at lyralists.lyrasis.org'" > Subject: [Archivesspace_Users_Group] Missing Japanese charactires in a PUI generated PDF Hi all. We?ve been struggling with an issue of a PUI generated PDF, in which no Japanese characters are displayed. Could anyone tell us what we should try next, or anything wrong in our procedure? We?d tried as follows; 1. Created "./plugins/local/public/views/pdf/_header.html.erb", and edited. We confirmed that the CSS was applied. 2. In the style of 1., we specified these 3 fonts, "serif", "sans-serif", and the font used in converting itext into Japanese; body { font-family: KozMinPro-Regular; } 3. In addition, we loaded Google Fonts and executed. It didn?t work. @import url('https://fonts.googleapis.com/css2?family=Sawarabi+Gothic&display=swap'); body { font-family: 'Sawarabi Gothic', sans-serif; } We?ve looked through the previous Q&As; http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2017-August/005046.html http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2017-August/005047.html We would appreciate a lot your generous assistance! Hitomi Matsuyama, Audiovisual Archivist Nakanoshima Museum of Art, Osaka 4-3-1 Nakanoshima, Kita-ku Osaka 530-0005 JAPAN tel. +81 (0)6 64 79 05 58 email. matsuyama-h at nakka-art.jp -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: A018.pdf Type: application/pdf Size: 26400 bytes Desc: A018.pdf URL: From atruitt at ohiohistory.org Wed Oct 19 14:54:27 2022 From: atruitt at ohiohistory.org (Aimee Truitt) Date: Wed, 19 Oct 2022 18:54:27 +0000 Subject: [Archivesspace_Users_Group] Bulk Importing Subject Headings Message-ID: Hello Everyone, I am currently working on a project to bulk import subject headings. My spreadsheet lists: Authority ID Source Scope Note Term Type External Documents Title External Documents Location External Documents Publish(?) An example of a term I am trying to add, is as follows: Authority ID: homoit0000021 Source: homoit Scope Note: People without gender. OHC guidelines: Only use for individuals who self-identify with this term. Term: Agender people Type: Topical External Documents Title: Homosaurus Vocabulary Entry External Documents Location: https://homosaurus.org/v3/homoit0000021 External Documents Publish?: TRUE I have ~470 subject terms to add. Has anyone tried to do something similar and have any suggestions, tips/tricks, plug-ins, etc? Any help you could give would be greatly appreciated. Thank you, Aimee Aimee Truitt (she/her) | Catalog and Metadata Coordinator Ohio History Connection | 800 E. 17th Ave., Columbus, OH 43211 p. 614.297.2589 | f. 614.297.2546 | atruitt at ohiohistory.org The Ohio History Connection's mission is to spark discovery of Ohio's stories. Embrace the present, share the past and transform the future. Support the Ohio History Connection: www.ohiohistory.org/give. -------------- next part -------------- An HTML attachment was scrubbed... URL: From snewhouse at sciencehistory.org Wed Oct 19 16:32:46 2022 From: snewhouse at sciencehistory.org (Newhouse, Sarah) Date: Wed, 19 Oct 2022 20:32:46 +0000 Subject: [Archivesspace_Users_Group] id=0 error on EAD XML import References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.4f8fbd2c-f445-4a13-beb0-cc96b61dd3ce@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.b20a056f-fb3d-4bd8-be24-bbe066b171df@emailsignatures365.codetwo.com> Message-ID: Hi all, I'm trying to import a test EAD file that I transformed from MARC XML as a trial run for doing this in batches. I knew it would be janky, but I can't narrow in on the specific form of the jank here. When I import I get the error below (it's long, apologies). My two best guesses are a) ASpace is missing something in each XML element needed to create an ID in every one of the JSON fields below? (which appears to be the entire resource record) b) there's something missing from the element in the XML file? (which there shouldn't be - I copied it in manually from an ASpace EAD export) I know this id_0 error is vague and has confused other people before, but I couldn't find enough information to help me narrow in on the specific issue is here. Thanks! ******************************************************** The following errors were found: id_0 : Property is required but was missing For JSONModel(:resource): #"resource", "external_ids"=>[], "subjects"=>[{"ref"=>"/subjects/import_e9b747a7-9d78-4dac-b424-51ff0dabc301"}, {"ref"=>"/subjects/import_b6e2afcf-be53-480e-981d-cc359ca31719"}, {"ref"=>"/subjects/import_24b83fea-3081-4770-a77b-a2b3e870d75a"}, {"ref"=>"/subjects/import_b5b565e8-4cf4-44ee-bef4-bb5d80ea6788"}, {"ref"=>"/subjects/import_30ccd3c2-8d46-4373-a803-9ff8f7ad3d7a"}, {"ref"=>"/subjects/import_68e70347-cfb7-4ccb-b1f9-2349ae2a3448"}, {"ref"=>"/subjects/import_c06a6464-07d2-4bb4-8305-c75da3453954"}, {"ref"=>"/subjects/import_7713afda-99d0-4382-b478-29c7c3a1167c"}, {"ref"=>"/subjects/import_0330ec33-8f81-46ed-b221-01bbf11d0cf2"}, {"ref"=>"/subjects/import_87b9ccf4-4873-4aa4-a951-a3eebb894f03"}, {"ref"=>"/subjects/import_eb959373-7080-4a29-9a16-6cf2f30ad375"}, {"ref"=>"/subjects/import_5412219d-8ae6-4cf9-904f-f2ef463377b7"}, {"ref"=>"/subjects/import_2158afa2-e11b-4f15-a145-8d26f01eea6a"}, {"ref"=>"/subjects/import_1e46c0e2-5f32-4c0e-97f9-07ddf8eb9531"}, {"ref"=>"/subjects/import_310a1db4-7b94-4a72-82ca-120f408b82d7"}, {"ref"=>"/subjects/import_80cf34db-8f1e-4d19-8b01-a2f5332471a4"}, {"ref"=>"/subjects/import_a201450a-2a58-45fe-b85f-b499b45b4023"}, {"ref"=>"/subjects/import_1a9edf46-9143-42dd-a46c-ba3894c8d00d"}, {"ref"=>"/subjects/import_ab2fd197-ab6e-4c56-8c66-73832460557d"}], "linked_events"=>[], "extents"=>[{"jsonmodel_type"=>"extent", "import_context"=>" ... ", "number"=>"169", "extent_type"=>"Linear Feet", "portion"=>"whole"}], "lang_materials"=>[{"jsonmodel_type"=>"lang_material", "notes"=>[], "import_context"=>" ... ", "language_and_script"=>{"jsonmodel_type"=>"language_and_script", "language"=>"und"}}], "dates"=>[{"jsonmodel_type"=>"date", "import_context"=>" ... ", "date_type"=>"inclusive", "expression"=>"1921-1998.", "label"=>"creation"}], "external_documents"=>[], "rights_statements"=>[], "linked_agents"=>[{"ref"=>"/agents/people/import_b71f978e-703f-4bc5-8c8e-a3f9f4b5d47f", "role"=>"creator", "relator"=>"creator", "terms"=>[]}, {"ref"=>"/agents/families/import_1c6bec99-db8e-43c9-85b0-c2e36da5f606", "role"=>"subject", "relator"=>"subject", "terms"=>[]}, {"ref"=>"/agents/families/import_e71eb985-1fe4-4725-8270-7d170afcc236", "role"=>"subject", "relator"=>"subject", "terms"=>[]}], "import_previous_arks"=>[], "is_slug_auto"=>true, "restrictions"=>false, "revision_statements"=>[], "instances"=>[], "deaccessions"=>[], "related_accessions"=>[], "classifications"=>[], "notes"=>[{"jsonmodel_type"=>"note_singlepart", "content"=>["This collection consists of fifteen series, which include: Biographical Information; Associations, Societies, and Organizations; Awards and Honors; Personal Files; Consulting, Research, and General Correspondence - Domestic; Consulting, Research, and General Correspondence - Foreign; Lectures; Manuscripts; Patent Applications; Patent Information; Polytechnic Files; Reports; Chronological Correspondence; Othmer Images - Photographs, Negatives, and Slides; and Artifacts. The bulk of the paper archives is correspondence pertaining to issues of chemical engineering. His personal life is also represented, particularly in Series I and IV."], "import_context"=>" ... ", "type"=>"abstract", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Othmer was born in Omaha, Nebraska on May 11, 1904. In 1927, he earned a Ph. D. in chemical engineering from the University of Michigan. In 1932, he began a career as a professor for the Chemical Engineering Department of Brooklyn Polytechnic Institute, where he remained until his death in 1995. He also consulted for hundreds of companies on numerous chemical engineering issues. He received over 150 patents worldwide. He invented the Othmer Still, a basic laboratory device for the determination of vapor-liquid equilibrium data. He collaborated with Dr. Raymond Kirk to create the Kirk-Othmer Encyclopedia of Chemical Technology."}], "import_context"=>" ... ", "type"=>"bioghist", "persistent_id"=>"a2", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Collection also includes furniture and unboxed artifacts."}], "import_context"=>" ... ", "type"=>"odd", "persistent_id"=>"a5", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Othmer's patents, lectures, and manuscripts have been bound."}], "import_context"=>" ... ", "type"=>"altformavail", "persistent_id"=>"a9", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"The Donald F. Othmer Papers, Othmer Library of Chemical History, Chemical Heritage Foundation, Philadelphia, Pennsylvania."}], "import_context"=>" ... ", "type"=>"prefercite", "persistent_id"=>"a18", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Donald F. Othmer; Bequest; 1996."}], "import_context"=>" ... ", "type"=>"acqinfo", "persistent_id"=>"a19", "publish"=>true}, {"jsonmodel_type"=>"note_bibliography", "content"=>["Publications: Thackray, Arnold. and Crow, Amy Beth, eds. Donald Frederick and Mildred Topp Othmer: A Commemorative of Their Lives and Legacies. Philadelphia: Chemical Heritage Foundation, 1999."], "items"=>[], "import_context"=>" ... ", "persistent_id"=>"a11", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Unpublished finding aid available."}], "import_context"=>" ... ", "type"=>"otherfindaid", "persistent_id"=>"a8", "publish"=>true}], "metadata_rights_declarations"=>[], "uri"=>"/repositories/import/resources/import_4f6627d1-465a-4884-8fac-f679bc179286", "publish"=>true, "finding_aid_language"=>"eng", "finding_aid_script"=>"Latn", "finding_aid_title"=>"Finding Aid toThe Donald F. Othmer Papers,1921-1998.", "finding_aid_author"=>"Finding aid prepared by MarcEdit", "finding_aid_language_note"=>"Finding aid written in English.", "level"=>"collection", "title"=>"The Donald F. Othmer Papers,"}> In : <ead class="cdata"> ... </ead> __________________________________ Sarah Newhouse (she, her, hers) Digital Preservation Archivist Othmer Library of Chemical History t. +1.215.873.8249 Science History Institute Chemistry * Engineering * Life Sciences 315 Chestnut Street * Philadelphia, PA 19106 * U.S.A. Learn about the scientific discoveries that changed our world at sciencehistory.org/learn -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Wed Oct 19 17:19:27 2022 From: mark.custer at yale.edu (Custer, Mark) Date: Wed, 19 Oct 2022 21:19:27 +0000 Subject: [Archivesspace_Users_Group] id=0 error on EAD XML import In-Reply-To: References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.4f8fbd2c-f445-4a13-beb0-cc96b61dd3ce@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.b20a056f-fb3d-4bd8-be24-bbe066b171df@emailsignatures365.codetwo.com> Message-ID: Sarah, I suspect that your EAD file is missing an archdesc/did/unitid field. This is where ArchivesSpace pulls information to create its Identifier field for the new Resource (see the attached screenshot), which is a required element. If you add something there, then I believe it should work. Here?s an example from one of our EAD files, https://github.com/YaleArchivesSpace/Archives-at-Yale-EAD3/blob/master/brbl-ead/1000.xml#L80 (this file is EAD3, but the archdesc/did/unitid construction looks the same in EAD2002). As for why you don?t have one in your file, I expect that?s because the call number is stored in a related MARC holdings record, or somewhere else that?s not being migrated as part of the MARC XML to EAD conversion (e.g., an 099 field). Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Newhouse, Sarah Date: Wednesday, October 19, 2022 at 4:33 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] id=0 error on EAD XML import Hi all, I?m trying to import a test EAD file that I transformed from MARC XML as a trial run for doing this in batches. I knew it would be janky, but I can?t narrow in on the specific form of the jank here. When I import I get the error below (it?s long, apologies). My two best guesses are a) ASpace is missing something in each XML element needed to create an ID in every one of the JSON fields below? (which appears to be the entire resource record) b) there?s something missing from the element in the XML file? (which there shouldn?t be ? I copied it in manually from an ASpace EAD export) I know this id_0 error is vague and has confused other people before, but I couldn?t find enough information to help me narrow in on the specific issue is here. Thanks! ******************************************************** The following errors were found: id_0 : Property is required but was missing For JSONModel(:resource): #"resource", "external_ids"=>[], "subjects"=>[{"ref"=>"/subjects/import_e9b747a7-9d78-4dac-b424-51ff0dabc301"}, {"ref"=>"/subjects/import_b6e2afcf-be53-480e-981d-cc359ca31719"}, {"ref"=>"/subjects/import_24b83fea-3081-4770-a77b-a2b3e870d75a"}, {"ref"=>"/subjects/import_b5b565e8-4cf4-44ee-bef4-bb5d80ea6788"}, {"ref"=>"/subjects/import_30ccd3c2-8d46-4373-a803-9ff8f7ad3d7a"}, {"ref"=>"/subjects/import_68e70347-cfb7-4ccb-b1f9-2349ae2a3448"}, {"ref"=>"/subjects/import_c06a6464-07d2-4bb4-8305-c75da3453954"}, {"ref"=>"/subjects/import_7713afda-99d0-4382-b478-29c7c3a1167c"}, {"ref"=>"/subjects/import_0330ec33-8f81-46ed-b221-01bbf11d0cf2"}, {"ref"=>"/subjects/import_87b9ccf4-4873-4aa4-a951-a3eebb894f03"}, {"ref"=>"/subjects/import_eb959373-7080-4a29-9a16-6cf2f30ad375"}, {"ref"=>"/subjects/import_5412219d-8ae6-4cf9-904f-f2ef463377b7"}, {"ref"=>"/subjects/import_2158afa2-e11b-4f15-a145-8d26f01eea6a"}, {"ref"=>"/subjects/import_1e46c0e2-5f32-4c0e-97f9-07ddf8eb9531"}, {"ref"=>"/subjects/import_310a1db4-7b94-4a72-82ca-120f408b82d7"}, {"ref"=>"/subjects/import_80cf34db-8f1e-4d19-8b01-a2f5332471a4"}, {"ref"=>"/subjects/import_a201450a-2a58-45fe-b85f-b499b45b4023"}, {"ref"=>"/subjects/import_1a9edf46-9143-42dd-a46c-ba3894c8d00d"}, {"ref"=>"/subjects/import_ab2fd197-ab6e-4c56-8c66-73832460557d"}], "linked_events"=>[], "extents"=>[{"jsonmodel_type"=>"extent", "import_context"=>" ... ", "number"=>"169", "extent_type"=>"Linear Feet", "portion"=>"whole"}], "lang_materials"=>[{"jsonmodel_type"=>"lang_material", "notes"=>[], "import_context"=>" ... ", "language_and_script"=>{"jsonmodel_type"=>"language_and_script", "language"=>"und"}}], "dates"=>[{"jsonmodel_type"=>"date", "import_context"=>" ... ", "date_type"=>"inclusive", "expression"=>"1921-1998.", "label"=>"creation"}], "external_documents"=>[], "rights_statements"=>[], "linked_agents"=>[{"ref"=>"/agents/people/import_b71f978e-703f-4bc5-8c8e-a3f9f4b5d47f", "role"=>"creator", "relator"=>"creator", "terms"=>[]}, {"ref"=>"/agents/families/import_1c6bec99-db8e-43c9-85b0-c2e36da5f606", "role"=>"subject", "relator"=>"subject", "terms"=>[]}, {"ref"=>"/agents/families/import_e71eb985-1fe4-4725-8270-7d170afcc236", "role"=>"subject", "relator"=>"subject", "terms"=>[]}], "import_previous_arks"=>[], "is_slug_auto"=>true, "restrictions"=>false, "revision_statements"=>[], "instances"=>[], "deaccessions"=>[], "related_accessions"=>[], "classifications"=>[], "notes"=>[{"jsonmodel_type"=>"note_singlepart", "content"=>["This collection consists of fifteen series, which include: Biographical Information; Associations, Societies, and Organizations; Awards and Honors; Personal Files; Consulting, Research, and General Correspondence - Domestic; Consulting, Research, and General Correspondence - Foreign; Lectures; Manuscripts; Patent Applications; Patent Information; Polytechnic Files; Reports; Chronological Correspondence; Othmer Images - Photographs, Negatives, and Slides; and Artifacts. The bulk of the paper archives is correspondence pertaining to issues of chemical engineering. His personal life is also represented, particularly in Series I and IV."], "import_context"=>" ... ", "type"=>"abstract", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Othmer was born in Omaha, Nebraska on May 11, 1904. In 1927, he earned a Ph. D. in chemical engineering from the University of Michigan. In 1932, he began a career as a professor for the Chemical Engineering Department of Brooklyn Polytechnic Institute, where he remained until his death in 1995. He also consulted for hundreds of companies on numerous chemical engineering issues. He received over 150 patents worldwide. He invented the Othmer Still, a basic laboratory device for the determination of vapor-liquid equilibrium data. He collaborated with Dr. Raymond Kirk to create the Kirk-Othmer Encyclopedia of Chemical Technology."}], "import_context"=>" ... ", "type"=>"bioghist", "persistent_id"=>"a2", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Collection also includes furniture and unboxed artifacts."}], "import_context"=>" ... ", "type"=>"odd", "persistent_id"=>"a5", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Othmer's patents, lectures, and manuscripts have been bound."}], "import_context"=>" ... ", "type"=>"altformavail", "persistent_id"=>"a9", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"The Donald F. Othmer Papers, Othmer Library of Chemical History, Chemical Heritage Foundation, Philadelphia, Pennsylvania."}], "import_context"=>" ... ", "type"=>"prefercite", "persistent_id"=>"a18", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Donald F. Othmer; Bequest; 1996."}], "import_context"=>" ... ", "type"=>"acqinfo", "persistent_id"=>"a19", "publish"=>true}, {"jsonmodel_type"=>"note_bibliography", "content"=>["Publications: Thackray, Arnold. and Crow, Amy Beth, eds. Donald Frederick and Mildred Topp Othmer: A Commemorative of Their Lives and Legacies. Philadelphia: Chemical Heritage Foundation, 1999."], "items"=>[], "import_context"=>" ... ", "persistent_id"=>"a11", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Unpublished finding aid available."}], "import_context"=>" ... ", "type"=>"otherfindaid", "persistent_id"=>"a8", "publish"=>true}], "metadata_rights_declarations"=>[], "uri"=>"/repositories/import/resources/import_4f6627d1-465a-4884-8fac-f679bc179286", "publish"=>true, "finding_aid_language"=>"eng", "finding_aid_script"=>"Latn", "finding_aid_title"=>"Finding Aid toThe Donald F. Othmer Papers,1921-1998.", "finding_aid_author"=>"Finding aid prepared by MarcEdit", "finding_aid_language_note"=>"Finding aid written in English.", "level"=>"collection", "title"=>"The Donald F. Othmer Papers,"}> In : <ead class="cdata"> ... </ead> __________________________________ Sarah Newhouse (she, her, hers) Digital Preservation Archivist Othmer Library of Chemical History t. +1.215.873.8249 Science History Institute Chemistry ? Engineering ? Life Sciences 315 Chestnut Street ? Philadelphia, PA 19106 ? U.S.A. Learn about the scientific discoveries that changed our world at sciencehistory.org/learn -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2022-10-19 at 5.18.20 PM.png Type: image/png Size: 162903 bytes Desc: Screen Shot 2022-10-19 at 5.18.20 PM.png URL: From russellr at rice.edu Wed Oct 19 17:24:25 2022 From: russellr at rice.edu (Rebecca Russell) Date: Wed, 19 Oct 2022 16:24:25 -0500 Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML Message-ID: Hello, We are trying to figure out if there is a plug-in or other way to configure user-defined fields (resources) so they export to MARC-XML? Many thanks in advance for any help with this question, Rebecca -- Rebecca Russell Archivist / Special Collections Librarian Woodson Research Center Pronouns: she/her 713-348-5133 |http://library.rice.edu/woodson -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Wed Oct 19 17:33:18 2022 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Wed, 19 Oct 2022 21:33:18 +0000 Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML In-Reply-To: References: Message-ID: Hi Rebecca This should get you started: https://github.com/jdshaw/dartmouth_udf_exports Specifically: https://github.com/jdshaw/dartmouth_udf_exports/blob/main/backend/lib/marc_user_defined_field_serialize.rb Its very much customized to our needs, but you should be able to use it as a starting point. Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Rebecca Russell Sent: Wednesday, October 19, 2022 5:24 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML Hello, We are trying to figure out if there is a plug-in or other way to configure user-defined fields (resources) so they export to MARC-XML? Many thanks in advance for any help with this question, Rebecca -- Rebecca Russell Archivist / Special Collections Librarian Woodson Research Center Pronouns: she/her 713-348-5133 | http://library.rice.edu/woodson -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Thu Oct 20 04:35:26 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Thu, 20 Oct 2022 09:35:26 +0100 Subject: [Archivesspace_Users_Group] id=0 error on EAD XML import In-Reply-To: References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.4f8fbd2c-f445-4a13-beb0-cc96b61dd3ce@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.b20a056f-fb3d-4bd8-be24-bbe066b171df@emailsignatures365.codetwo.com> Message-ID: <47f73b0c-2d53-a5cb-5a94-17896c0a8f6d@bodleian.ox.ac.uk> Don't be surprised if the import fails again, with the same message but for a subrecord, or with a different message. That is because the ArchivesSpace EAD importer uses a SAX parser method (https://en.wikipedia.org/wiki/Simple_API_for_XML) to read the XML, not a DOM (Document Object Model) method. The former is faster and uses less memory, but cannot scan an entire XML file for issues and report back with a list of things to fix, as the latter would. That is why many people use a pre-import validation step to find most of the issues that might occur, without the laborious process of creating an import job, waiting for it to fail, then re-running. Harvard have made theirs into a web service which you might find useful: https://eadchecker.lib.harvard.edu/ I think it is fairly generic (unlike a similar validation script used here which imposes editorial restrictions as well.) Andrew. On 19/10/2022 22:19, Custer, Mark wrote: > > Sarah, > > I suspect that your EAD file is missing an archdesc/did/unitid field. > This is where ArchivesSpace pulls information to create its Identifier > field for the new Resource (see the attached screenshot), which is a > required element. > > If you add something there, then I believe it should work.? Here?s an > example from one of our EAD files, > https://github.com/YaleArchivesSpace/Archives-at-Yale-EAD3/blob/master/brbl-ead/1000.xml#L80 > (this file is EAD3, but the archdesc/did/unitid construction looks the > same in EAD2002). > > As for why you don?t have one in your file, I expect that?s because > the call number is stored in a related MARC holdings record, or > somewhere else that?s not being migrated as part of the MARC XML to > EAD conversion (e.g., an 099 field). > > Mark > > *From: *archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Newhouse, Sarah > *Date: *Wednesday, October 19, 2022 at 4:33 PM > *To: *Archivesspace Users Group > > *Subject: *[Archivesspace_Users_Group] id=0 error on EAD XML import > > Hi all, > > I?m trying to import a test EAD file that I transformed from MARC XML > as a trial run for doing this in batches. I knew it would be janky, > but I can?t narrow in on the specific form of the jank here. When I > import I get the error below (it?s long, apologies). My two best > guesses are > a) ASpace is missing something in each XML element needed to create an > ID in every one of the JSON fields below? ?(which appears to be the > entire resource record) > b) there?s something missing from the element in the XML file? > (which there shouldn?t be ? I copied it in manually from an ASpace EAD > export) > > I know this id_0 error is vague and has confused other people before, > but I couldn?t find enough information to help me narrow in on the > specific issue is here. > > Thanks! > > ******************************************************** > > The following errors were found: > ??????? id_0 : Property is required but was missing > > > For JSONModel(:resource): > ?#"resource", "external_ids"=>[], "subjects"=>[{"ref"=>"/subjects/import_e9b747a7-9d78-4dac-b424-51ff0dabc301"}, {"ref"=>"/subjects/import_b6e2afcf-be53-480e-981d-cc359ca31719"}, {"ref"=>"/subjects/import_24b83fea-3081-4770-a77b-a2b3e870d75a"}, {"ref"=>"/subjects/import_b5b565e8-4cf4-44ee-bef4-bb5d80ea6788"}, {"ref"=>"/subjects/import_30ccd3c2-8d46-4373-a803-9ff8f7ad3d7a"}, {"ref"=>"/subjects/import_68e70347-cfb7-4ccb-b1f9-2349ae2a3448"}, {"ref"=>"/subjects/import_c06a6464-07d2-4bb4-8305-c75da3453954"}, {"ref"=>"/subjects/import_7713afda-99d0-4382-b478-29c7c3a1167c"}, {"ref"=>"/subjects/import_0330ec33-8f81-46ed-b221-01bbf11d0cf2"}, {"ref"=>"/subjects/import_87b9ccf4-4873-4aa4-a951-a3eebb894f03"}, {"ref"=>"/subjects/import_eb959373-7080-4a29-9a16-6cf2f30ad375"}, {"ref"=>"/subjects/import_5412219d-8ae6-4cf9-904f-f2ef463377b7"}, {"ref"=>"/subjects/import_2158afa2-e11b-4f15-a145-8d26f01eea6a"}, {"ref"=>"/subjects/import_1e46c0e2-5f32-4c0e-97f9-07ddf8eb9531"}, {"ref"=>"/subjects/import_310a1db4-7b94-4a72-82ca-120f408b82d7"}, {"ref"=>"/subjects/import_80cf34db-8f1e-4d19-8b01-a2f5332471a4"}, {"ref"=>"/subjects/import_a201450a-2a58-45fe-b85f-b499b45b4023"}, {"ref"=>"/subjects/import_1a9edf46-9143-42dd-a46c-ba3894c8d00d"}, {"ref"=>"/subjects/import_ab2fd197-ab6e-4c56-8c66-73832460557d"}], "linked_events"=>[], "extents"=>[{"jsonmodel_type"=>"extent", "import_context"=>" ... ", "number"=>"169", "extent_type"=>"Linear Feet", "portion"=>"whole"}], "lang_materials"=>[{"jsonmodel_type"=>"lang_material", "notes"=>[], "import_context"=>" ... ", "language_and_script"=>{"jsonmodel_type"=>"language_and_script", "language"=>"und"}}], "dates"=>[{"jsonmodel_type"=>"date", "import_context"=>" ... ", "date_type"=>"inclusive", "expression"=>"1921-1998.", "label"=>"creation"}], "external_documents"=>[], "rights_statements"=>[], "linked_agents"=>[{"ref"=>"/agents/people/import_b71f978e-703f-4bc5-8c8e-a3f9f4b5d47f", "role"=>"creator", "relator"=>"creator", "terms"=>[]}, {"ref"=>"/agents/families/import_1c6bec99-db8e-43c9-85b0-c2e36da5f606", "role"=>"subject", "relator"=>"subject", "terms"=>[]}, {"ref"=>"/agents/families/import_e71eb985-1fe4-4725-8270-7d170afcc236", "role"=>"subject", "relator"=>"subject", "terms"=>[]}], "import_previous_arks"=>[], "is_slug_auto"=>true, "restrictions"=>false, "revision_statements"=>[], "instances"=>[], "deaccessions"=>[], "related_accessions"=>[], "classifications"=>[], "notes"=>[{"jsonmodel_type"=>"note_singlepart", "content"=>["This collection consists of fifteen series, which include: Biographical Information; Associations, Societies, and Organizations; Awards and Honors; Personal Files; Consulting, Research, and General Correspondence - Domestic; Consulting, Research, and General Correspondence - Foreign; Lectures; Manuscripts; Patent Applications; Patent Information; Polytechnic Files; Reports; Chronological Correspondence; Othmer Images - Photographs, Negatives, and Slides; and Artifacts. The bulk of the paper archives is correspondence pertaining to issues of chemical engineering. His personal life is also represented, particularly in Series I and IV."], "import_context"=>" ... ", "type"=>"abstract", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Othmer was born in Omaha, Nebraska on May 11, 1904. In 1927, he earned a Ph. D. in chemical engineering from the University of Michigan. In 1932, he began a career as a professor for the Chemical Engineering Department of Brooklyn Polytechnic Institute, where he remained until his death in 1995. He also consulted for hundreds of companies on numerous chemical engineering issues. He received over 150 patents worldwide. He invented the Othmer Still, a basic laboratory device for the determination of vapor-liquid equilibrium data. He collaborated with Dr. Raymond Kirk to create the Kirk-Othmer Encyclopedia of Chemical Technology."}], "import_context"=>" ... ", "type"=>"bioghist", "persistent_id"=>"a2", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Collection also includes furniture and unboxed artifacts."}], "import_context"=>" ... ", "type"=>"odd", "persistent_id"=>"a5", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Othmer's patents, lectures, and manuscripts have been bound."}], "import_context"=>" ... ", "type"=>"altformavail", "persistent_id"=>"a9", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"The Donald F. Othmer Papers, Othmer Library of Chemical History, Chemical Heritage Foundation, Philadelphia, Pennsylvania."}], "import_context"=>" ... ", "type"=>"prefercite", "persistent_id"=>"a18", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Donald F. Othmer; Bequest; 1996."}], "import_context"=>" ... ", "type"=>"acqinfo", "persistent_id"=>"a19", "publish"=>true}, {"jsonmodel_type"=>"note_bibliography", "content"=>["Publications: Thackray, Arnold. and Crow, Amy Beth, eds. Donald Frederick and Mildred Topp Othmer: A Commemorative of Their Lives and Legacies. Philadelphia: Chemical Heritage Foundation, 1999."], "items"=>[], "import_context"=>" ... ", "persistent_id"=>"a11", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Unpublished finding aid available."}], "import_context"=>" ... ", "type"=>"otherfindaid", "persistent_id"=>"a8", "publish"=>true}], "metadata_rights_declarations"=>[], "uri"=>"/repositories/import/resources/import_4f6627d1-465a-4884-8fac-f679bc179286", "publish"=>true, "finding_aid_language"=>"eng", "finding_aid_script"=>"Latn", "finding_aid_title"=>"Finding Aid toThe Donald F. Othmer Papers,1921-1998.", "finding_aid_author"=>"Finding aid prepared by MarcEdit", "finding_aid_language_note"=>"Finding aid written in English.", "level"=>"collection", "title"=>"The Donald F. Othmer Papers,"}> > > > In : > ?<ead class="cdata"> ... </ead> > > __________________________________ > > Sarah Newhouse /(she, her, hers)/ > Digital Preservation Archivist > Othmer Library of Chemical History > t. +1.215.873.8249 > > *Science History Institute * > Chemistry ??Engineering ??Life Sciences > 315 Chestnut Street ? Philadelphia, PA 19106 ? U.S.A. > Learn about the scientific discoveries that changed our world at > sciencehistory.org/learn > > > > _______________________________________________ > 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: From snewhouse at sciencehistory.org Thu Oct 20 09:27:58 2022 From: snewhouse at sciencehistory.org (Newhouse, Sarah) Date: Thu, 20 Oct 2022 13:27:58 +0000 Subject: [Archivesspace_Users_Group] id=0 error on EAD XML import In-Reply-To: <47f73b0c-2d53-a5cb-5a94-17896c0a8f6d@bodleian.ox.ac.uk> References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.4f8fbd2c-f445-4a13-beb0-cc96b61dd3ce@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.b20a056f-fb3d-4bd8-be24-bbe066b171df@emailsignatures365.codetwo.com> <47f73b0c-2d53-a5cb-5a94-17896c0a8f6d@bodleian.ox.ac.uk> Message-ID: These are both incredibly helpful responses ? thank you Andrew and Mark! __________________________________ Sarah Newhouse (she, her, hers) Digital Preservation Archivist Othmer Library of Chemical History t. +1.215.873.8249 Science History Institute Chemistry ? Engineering ? Life Sciences 315 Chestnut Street ? Philadelphia, PA 19106 ? U.S.A. Learn about the scientific discoveries that changed our world at sciencehistory.org/learn From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Andrew Morrison Sent: Thursday, October 20, 2022 4:35 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] id=0 error on EAD XML import Don't be surprised if the import fails again, with the same message but for a subrecord, or with a different message. That is because the ArchivesSpace EAD importer uses a SAX parser method (https://en.wikipedia.org/wiki/Simple_API_for_XML) to read the XML, not a DOM (Document Object Model) method. The former is faster and uses less memory, but cannot scan an entire XML file for issues and report back with a list of things to fix, as the latter would. That is why many people use a pre-import validation step to find most of the issues that might occur, without the laborious process of creating an import job, waiting for it to fail, then re-running. Harvard have made theirs into a web service which you might find useful: https://eadchecker.lib.harvard.edu/ I think it is fairly generic (unlike a similar validation script used here which imposes editorial restrictions as well.) Andrew. On 19/10/2022 22:19, Custer, Mark wrote: Sarah, I suspect that your EAD file is missing an archdesc/did/unitid field. This is where ArchivesSpace pulls information to create its Identifier field for the new Resource (see the attached screenshot), which is a required element. If you add something there, then I believe it should work. Here?s an example from one of our EAD files, https://github.com/YaleArchivesSpace/Archives-at-Yale-EAD3/blob/master/brbl-ead/1000.xml#L80 (this file is EAD3, but the archdesc/did/unitid construction looks the same in EAD2002). As for why you don?t have one in your file, I expect that?s because the call number is stored in a related MARC holdings record, or somewhere else that?s not being migrated as part of the MARC XML to EAD conversion (e.g., an 099 field). Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Newhouse, Sarah Date: Wednesday, October 19, 2022 at 4:33 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] id=0 error on EAD XML import Hi all, I?m trying to import a test EAD file that I transformed from MARC XML as a trial run for doing this in batches. I knew it would be janky, but I can?t narrow in on the specific form of the jank here. When I import I get the error below (it?s long, apologies). My two best guesses are a) ASpace is missing something in each XML element needed to create an ID in every one of the JSON fields below? (which appears to be the entire resource record) b) there?s something missing from the element in the XML file? (which there shouldn?t be ? I copied it in manually from an ASpace EAD export) I know this id_0 error is vague and has confused other people before, but I couldn?t find enough information to help me narrow in on the specific issue is here. Thanks! ******************************************************** The following errors were found: id_0 : Property is required but was missing For JSONModel(:resource): #"resource", "external_ids"=>[], "subjects"=>[{"ref"=>"/subjects/import_e9b747a7-9d78-4dac-b424-51ff0dabc301"}, {"ref"=>"/subjects/import_b6e2afcf-be53-480e-981d-cc359ca31719"}, {"ref"=>"/subjects/import_24b83fea-3081-4770-a77b-a2b3e870d75a"}, {"ref"=>"/subjects/import_b5b565e8-4cf4-44ee-bef4-bb5d80ea6788"}, {"ref"=>"/subjects/import_30ccd3c2-8d46-4373-a803-9ff8f7ad3d7a"}, {"ref"=>"/subjects/import_68e70347-cfb7-4ccb-b1f9-2349ae2a3448"}, {"ref"=>"/subjects/import_c06a6464-07d2-4bb4-8305-c75da3453954"}, {"ref"=>"/subjects/import_7713afda-99d0-4382-b478-29c7c3a1167c"}, {"ref"=>"/subjects/import_0330ec33-8f81-46ed-b221-01bbf11d0cf2"}, {"ref"=>"/subjects/import_87b9ccf4-4873-4aa4-a951-a3eebb894f03"}, {"ref"=>"/subjects/import_eb959373-7080-4a29-9a16-6cf2f30ad375"}, {"ref"=>"/subjects/import_5412219d-8ae6-4cf9-904f-f2ef463377b7"}, {"ref"=>"/subjects/import_2158afa2-e11b-4f15-a145-8d26f01eea6a"}, {"ref"=>"/subjects/import_1e46c0e2-5f32-4c0e-97f9-07ddf8eb9531"}, {"ref"=>"/subjects/import_310a1db4-7b94-4a72-82ca-120f408b82d7"}, {"ref"=>"/subjects/import_80cf34db-8f1e-4d19-8b01-a2f5332471a4"}, {"ref"=>"/subjects/import_a201450a-2a58-45fe-b85f-b499b45b4023"}, {"ref"=>"/subjects/import_1a9edf46-9143-42dd-a46c-ba3894c8d00d"}, {"ref"=>"/subjects/import_ab2fd197-ab6e-4c56-8c66-73832460557d"}], "linked_events"=>[], "extents"=>[{"jsonmodel_type"=>"extent", "import_context"=>" ... ", "number"=>"169", "extent_type"=>"Linear Feet", "portion"=>"whole"}], "lang_materials"=>[{"jsonmodel_type"=>"lang_material", "notes"=>[], "import_context"=>" ... ", "language_and_script"=>{"jsonmodel_type"=>"language_and_script", "language"=>"und"}}], "dates"=>[{"jsonmodel_type"=>"date", "import_context"=>" ... ", "date_type"=>"inclusive", "expression"=>"1921-1998.", "label"=>"creation"}], "external_documents"=>[], "rights_statements"=>[], "linked_agents"=>[{"ref"=>"/agents/people/import_b71f978e-703f-4bc5-8c8e-a3f9f4b5d47f", "role"=>"creator", "relator"=>"creator", "terms"=>[]}, {"ref"=>"/agents/families/import_1c6bec99-db8e-43c9-85b0-c2e36da5f606", "role"=>"subject", "relator"=>"subject", "terms"=>[]}, {"ref"=>"/agents/families/import_e71eb985-1fe4-4725-8270-7d170afcc236", "role"=>"subject", "relator"=>"subject", "terms"=>[]}], "import_previous_arks"=>[], "is_slug_auto"=>true, "restrictions"=>false, "revision_statements"=>[], "instances"=>[], "deaccessions"=>[], "related_accessions"=>[], "classifications"=>[], "notes"=>[{"jsonmodel_type"=>"note_singlepart", "content"=>["This collection consists of fifteen series, which include: Biographical Information; Associations, Societies, and Organizations; Awards and Honors; Personal Files; Consulting, Research, and General Correspondence - Domestic; Consulting, Research, and General Correspondence - Foreign; Lectures; Manuscripts; Patent Applications; Patent Information; Polytechnic Files; Reports; Chronological Correspondence; Othmer Images - Photographs, Negatives, and Slides; and Artifacts. The bulk of the paper archives is correspondence pertaining to issues of chemical engineering. His personal life is also represented, particularly in Series I and IV."], "import_context"=>" ... ", "type"=>"abstract", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Othmer was born in Omaha, Nebraska on May 11, 1904. In 1927, he earned a Ph. D. in chemical engineering from the University of Michigan. In 1932, he began a career as a professor for the Chemical Engineering Department of Brooklyn Polytechnic Institute, where he remained until his death in 1995. He also consulted for hundreds of companies on numerous chemical engineering issues. He received over 150 patents worldwide. He invented the Othmer Still, a basic laboratory device for the determination of vapor-liquid equilibrium data. He collaborated with Dr. Raymond Kirk to create the Kirk-Othmer Encyclopedia of Chemical Technology."}], "import_context"=>" ... ", "type"=>"bioghist", "persistent_id"=>"a2", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Collection also includes furniture and unboxed artifacts."}], "import_context"=>" ... ", "type"=>"odd", "persistent_id"=>"a5", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Othmer's patents, lectures, and manuscripts have been bound."}], "import_context"=>" ... ", "type"=>"altformavail", "persistent_id"=>"a9", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"The Donald F. Othmer Papers, Othmer Library of Chemical History, Chemical Heritage Foundation, Philadelphia, Pennsylvania."}], "import_context"=>" ... ", "type"=>"prefercite", "persistent_id"=>"a18", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Donald F. Othmer; Bequest; 1996."}], "import_context"=>" ... ", "type"=>"acqinfo", "persistent_id"=>"a19", "publish"=>true}, {"jsonmodel_type"=>"note_bibliography", "content"=>["Publications: Thackray, Arnold. and Crow, Amy Beth, eds. Donald Frederick and Mildred Topp Othmer: A Commemorative of Their Lives and Legacies. Philadelphia: Chemical Heritage Foundation, 1999."], "items"=>[], "import_context"=>" ... ", "persistent_id"=>"a11", "publish"=>true}, {"jsonmodel_type"=>"note_multipart", "subnotes"=>[{"publish"=>true, "jsonmodel_type"=>"note_text", "content"=>"Unpublished finding aid available."}], "import_context"=>" ... ", "type"=>"otherfindaid", "persistent_id"=>"a8", "publish"=>true}], "metadata_rights_declarations"=>[], "uri"=>"/repositories/import/resources/import_4f6627d1-465a-4884-8fac-f679bc179286", "publish"=>true, "finding_aid_language"=>"eng", "finding_aid_script"=>"Latn", "finding_aid_title"=>"Finding Aid toThe Donald F. Othmer Papers,1921-1998.", "finding_aid_author"=>"Finding aid prepared by MarcEdit", "finding_aid_language_note"=>"Finding aid written in English.", "level"=>"collection", "title"=>"The Donald F. Othmer Papers,"}> In : <ead class="cdata"> ... </ead> __________________________________ Sarah Newhouse (she, her, hers) Digital Preservation Archivist Othmer Library of Chemical History t. +1.215.873.8249 Science History Institute Chemistry ? Engineering ? Life Sciences 315 Chestnut Street ? Philadelphia, PA 19106 ? U.S.A. Learn about the scientific discoveries that changed our world at sciencehistory.org/learn _______________________________________________ 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: From mweppler at csustan.edu Thu Oct 20 13:03:05 2022 From: mweppler at csustan.edu (Mary Weppler) Date: Thu, 20 Oct 2022 17:03:05 +0000 Subject: [Archivesspace_Users_Group] OAI-PMH settings - issues with digital objects not being harvested Message-ID: Hello, We are part of a trial community partnership with JSTOR in which they are harvesting two of our collections. One of the collections was successfully harvested, including the digital objects: https://www.jstor.org/site/csustan/economist-shoe-service/?searchkey=1666285079367 This collection consists of an archival object with several child records, each of which also had a single digital object. The second (problematic) collection was harvested at the archival object level, however each of the child archival objects (decades) have up to 200 digital objects: https://www.jstor.org/site/csustan/signal/ The harvesting team has not been able to harvest the individual digital objects associated with these child archival objects. The team has stated that there must be an issue with our OAI-PMH settings. We are at a loss as to what the issue could be, as we've checked the OAI settings and cannot see anything amiss. Has anyone else encountered this issue? Thank you! Mary Mary Weppler-Van Diver Library Faculty, Librarian & CA Special Collections and University Archives Email: mweppler at csustan.edu Phone: 209-664-6538 -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Fri Oct 21 04:09:56 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Fri, 21 Oct 2022 09:09:56 +0100 Subject: [Archivesspace_Users_Group] Bulk Importing Subject Headings In-Reply-To: References: Message-ID: I haven't done this myself, but I think the only way to bulk-load all those fields would be via an API script. That means building a JSON representation of each subject record, using something like Python, then sending it to this ArchivesSpace backend endpoint: https://archivesspace.github.io/archivesspace/api/?python#create-a-subject However, if just loading just the term and source fields would be good enough, it could be done by building an EAD or MARCXML file and loading that via the staff interface. Andrew. On 19/10/2022 19:54, Aimee Truitt wrote: > > Hello Everyone, > > I am currently working on a project to bulk import subject headings. > My spreadsheet lists: > > *Authority ID* > > *Source* > > *Scope Note* > > *Term* > > *Type* > > *External Documents Title* > > *External Documents Location* > > *External Documents Publish(?)* > > An example of a term I am trying to add, is as follows: > > *Authority ID:* homoit0000021 > > *Source:* homoit > > *Scope Note:* People without gender. OHC guidelines: Only use for > individuals who self-identify with this term. > > *Term:* Agender people > > *Type:* Topical > > *External Documents Title:* Homosaurus Vocabulary Entry > > *External Documents Location*: https://homosaurus.org/v3/homoit0000021 > > *External Documents Publish?:* TRUE > > I have ~470 subject terms to add. Has anyone tried to do something > similar and have any suggestions, tips/tricks, plug-ins, etc? Any help > you could give would be greatly appreciated. > > Thank you, > > Aimee > > *Aimee Truitt (she/her) | Catalog and Metadata Coordinator* > > Ohio History Connection | 800 E. 17^th Ave., Columbus, OH 43211 > > p. 614.297.2589? | f. 614.297.2546 |atruitt at ohiohistory.org > > > *The Ohio History Connection?s **mission* > *is to spark discovery of Ohio?s > stories. Embrace the present, share the past and transform the future. > Support the Ohio History Connection: **www.ohiohistory.org/give* > *. * > > > _______________________________________________ > 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: From andrew.morrison at bodleian.ox.ac.uk Fri Oct 21 04:45:58 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Fri, 21 Oct 2022 09:45:58 +0100 Subject: [Archivesspace_Users_Group] OAI-PMH settings - issues with digital objects not being harvested In-Reply-To: References: Message-ID: <36022b00-b437-e8f0-4eae-aac034d79001@bodleian.ox.ac.uk> You do not say what metadata format they are harvesting via OAI-PMH. If it is EAD 2002, and they are expecting daogrp elements, then ArchivesSpace only does that for multiple file versions in a digital object, not for multiple digital objects linked to a single archival object. Andrew. On 20/10/2022 18:03, Mary Weppler wrote: > Hello, > > We are part of a trial community partnership with JSTOR in which they > are harvesting two of our collections.? One of the collections was > successfully harvested, including the digital objects: > https://www.jstor.org/site/csustan/economist-shoe-service/?searchkey=1666285079367 > This collection consists of an archival object with several child > records, each of which also had a single digital object. > > The second (problematic) collection was harvested at the archival > object level, however each of the child archival objects (decades) > have up to 200 digital objects: https://www.jstor.org/site/csustan/signal/ > The harvesting team has not been able to harvest the individual > digital objects associated with these child archival objects.? The > team has stated that there must be an issue with our OAI-PMH > settings.? We are at a loss as to what the issue could be, as we've > checked the OAI settings and cannot see anything amiss.? Has anyone > else encountered this issue? > > Thank you! > > Mary > > Mary Weppler-Van Diver > Library Faculty, Librarian & CA > > Special Collections and University Archives > > Email: mweppler at csustan.edu > Phone: 209-664-6538 > > _______________________________________________ > 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: From mweppler at csustan.edu Fri Oct 21 14:17:34 2022 From: mweppler at csustan.edu (Mary Weppler) Date: Fri, 21 Oct 2022 18:17:34 +0000 Subject: [Archivesspace_Users_Group] OAI-PMH settings - issues with digital objects not being harvested In-Reply-To: <36022b00-b437-e8f0-4eae-aac034d79001@bodleian.ox.ac.uk> References: <36022b00-b437-e8f0-4eae-aac034d79001@bodleian.ox.ac.uk> Message-ID: Hello Andrew, Thank you very much for your assistance.! They are not using EAD. I asked about this, but apparently it is not a metadata format they use for this process. Regarding EAD and harvesting multiple digital objects associated with a single archival object, do you know if there is a later version of EAD that will do this? Thank you again, Mary Mary Weppler-Van Diver Library Faculty, Librarian & CA Special Collections and University Archives Email: mweppler at csustan.edu Phone: 209-664-6538 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Andrew Morrison Sent: Friday, October 21, 2022 1:45 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] OAI-PMH settings - issues with digital objects not being harvested CAUTION: This message originated from outside of Stanislaus State. Do not click on links or open attachments unless you recognize the sender and are expecting the message. You do not say what metadata format they are harvesting via OAI-PMH. If it is EAD 2002, and they are expecting daogrp elements, then ArchivesSpace only does that for multiple file versions in a digital object, not for multiple digital objects linked to a single archival object. Andrew. On 20/10/2022 18:03, Mary Weppler wrote: Hello, We are part of a trial community partnership with JSTOR in which they are harvesting two of our collections. One of the collections was successfully harvested, including the digital objects: https://www.jstor.org/site/csustan/economist-shoe-service/?searchkey=1666285079367 This collection consists of an archival object with several child records, each of which also had a single digital object. The second (problematic) collection was harvested at the archival object level, however each of the child archival objects (decades) have up to 200 digital objects: https://www.jstor.org/site/csustan/signal/ The harvesting team has not been able to harvest the individual digital objects associated with these child archival objects. The team has stated that there must be an issue with our OAI-PMH settings. We are at a loss as to what the issue could be, as we've checked the OAI settings and cannot see anything amiss. Has anyone else encountered this issue? Thank you! Mary Mary Weppler-Van Diver Library Faculty, Librarian & CA Special Collections and University Archives Email: mweppler at csustan.edu Phone: 209-664-6538 _______________________________________________ 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: From andrew.morrison at bodleian.ox.ac.uk Mon Oct 24 10:34:32 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Mon, 24 Oct 2022 15:34:32 +0100 Subject: [Archivesspace_Users_Group] OAI-PMH settings - issues with digital objects not being harvested In-Reply-To: References: <36022b00-b437-e8f0-4eae-aac034d79001@bodleian.ox.ac.uk> Message-ID: <1f09d5d8-ddf7-1ef5-d2cf-f7f30f9e77bc@bodleian.ox.ac.uk> ArchivesSpace will output multiple digital objects linked to a single archival object, but it will do so as separate dao elements, not together in one daogrp. It was only a guess on my part that it might have been an explanation. But, as EAD is not being used, it doesn't matter. You might get some help from someone else if you say what metadata format is being harvested. Andrew. On 21/10/2022 19:17, Mary Weppler wrote: > Hello Andrew, > > Thank you very much for your assistance.! They are not using EAD.? I > asked about this, but apparently it is not a metadata format they use > for this process. > > Regarding EAD and harvesting multiple digital objects associated with > a single archival object, do you know if there is a later version of > EAD that will do this? > > Thank you again, > > Mary > > Mary Weppler-Van Diver > Library Faculty, Librarian & CA > > Special Collections and University Archives > > Email: mweppler at csustan.edu > Phone: 209-664-6538 > ------------------------------------------------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Andrew Morrison > *Sent:* Friday, October 21, 2022 1:45 AM > *To:* archivesspace_users_group at lyralists.lyrasis.org > > *Subject:* Re: [Archivesspace_Users_Group] OAI-PMH settings - issues > with digital objects not being harvested > > _CAUTION: _This message originated from outside of Stanislaus State. > Do not click on links or open attachments unless you recognize the > sender and are expecting the message. > > You do not say what metadata format they are harvesting via OAI-PMH. > If it is EAD 2002, and they are expecting daogrp elements, then > ArchivesSpace only does that for multiple file versions in a digital > object, not for multiple digital objects linked to a single archival > object. > > > Andrew. > > > > On 20/10/2022 18:03, Mary Weppler wrote: >> Hello, >> >> We are part of a trial community partnership with JSTOR in which they >> are harvesting two of our collections.? One of the collections was >> successfully harvested, including the digital objects: >> https://www.jstor.org/site/csustan/economist-shoe-service/?searchkey=1666285079367 >> >> This collection consists of an archival object with several child >> records, each of which also had a single digital object. >> >> The second (problematic) collection was harvested at the archival >> object level, however each of the child archival objects (decades) >> have up to 200 digital objects: >> https://www.jstor.org/site/csustan/signal/ >> >> The harvesting team has not been able to harvest the individual >> digital objects associated with these child archival objects.? The >> team has stated that there must be an issue with our OAI-PMH >> settings.? We are at a loss as to what the issue could be, as we've >> checked the OAI settings and cannot see anything amiss. Has anyone >> else encountered this issue? >> >> Thank you! >> >> Mary >> >> Mary Weppler-Van Diver >> Library Faculty, Librarian & CA >> >> Special Collections and University Archives >> >> Email: mweppler at csustan.edu >> Phone: 209-664-6538 >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > 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: From mang.sun at rice.edu Mon Oct 24 16:19:29 2022 From: mang.sun at rice.edu (mang.sun at rice.edu) Date: Mon, 24 Oct 2022 15:19:29 -0500 Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML In-Reply-To: References: Message-ID: We see the following error in the exported marcxml file with the plugin enabled. Our AS version is 2.7.1. {"error":"wrong number of arguments (2 for 1)"} Mang Sun Rice U. On Wed, Oct 19, 2022 at 4:33 PM Joshua D. Shaw wrote: > Hi Rebecca > > This should get you started: > https://github.com/jdshaw/dartmouth_udf_exports > > Specifically: > https://github.com/jdshaw/dartmouth_udf_exports/blob/main/backend/lib/marc_user_defined_field_serialize.rb > > Its very much customized to our needs, but you should be able to use it as > a starting point. > > Joshua > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Rebecca Russell > *Sent:* Wednesday, October 19, 2022 5:24 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] User-defined fields in MARC-XML > > Hello, > > We are trying to figure out if there is a plug-in or other way to > configure user-defined fields (resources) so they export to MARC-XML? > > Many thanks in advance for any help with this question, > > Rebecca > > > -- > Rebecca Russell > > Archivist / Special Collections Librarian > Woodson Research Center > > Pronouns: she/her > > 713-348-5133 | http://library.rice.edu/woodson > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!hoZD86BZEammKoA9cQbsKq6cfvPbZJm3YheC1Aj7moUqNqJ1_XeftPrZU8gRA7KPQBEN57BH-3bis0109hOBv-joBc9B7-4aK1w$ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Tue Oct 25 07:28:52 2022 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Tue, 25 Oct 2022 11:28:52 +0000 Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML In-Reply-To: References: Message-ID: Without knowing what line is being referenced in the error, its hard to know exactly what the issue might be, but I wouldn't suggest just using this plugin as is since its very much customized for Dartmouth's use and probably won't be what another institution might need (There are hard coded references to Rauner Library in there!) Having said that, if you can pass along the line referenced in the error, that should help with figuring out why the error is occurring. Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of mang.sun at rice.edu Sent: Monday, October 24, 2022 4:19 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML We see the following error in the exported marcxml file with the plugin enabled. Our AS version is 2.7.1. {"error":"wrong number of arguments (2 for 1)"} Mang Sun Rice U. On Wed, Oct 19, 2022 at 4:33 PM Joshua D. Shaw > wrote: Hi Rebecca This should get you started: https://github.com/jdshaw/dartmouth_udf_exports Specifically: https://github.com/jdshaw/dartmouth_udf_exports/blob/main/backend/lib/marc_user_defined_field_serialize.rb Its very much customized to our needs, but you should be able to use it as a starting point. Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Rebecca Russell > Sent: Wednesday, October 19, 2022 5:24 PM To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML Hello, We are trying to figure out if there is a plug-in or other way to configure user-defined fields (resources) so they export to MARC-XML? Many thanks in advance for any help with this question, Rebecca -- Rebecca Russell Archivist / Special Collections Librarian Woodson Research Center Pronouns: she/her 713-348-5133 | http://library.rice.edu/woodson _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!hoZD86BZEammKoA9cQbsKq6cfvPbZJm3YheC1Aj7moUqNqJ1_XeftPrZU8gRA7KPQBEN57BH-3bis0109hOBv-joBc9B7-4aK1w$ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mang.sun at rice.edu Tue Oct 25 09:59:52 2022 From: mang.sun at rice.edu (mang.sun at rice.edu) Date: Tue, 25 Oct 2022 08:59:52 -0500 Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML In-Reply-To: References: Message-ID: Joshua, below are the lines around the error found in the log. D, [2022-10-25T08:53:44.232663 #6127] DEBUG -- : Thread-2024: GET /repositories/2/resources/marc21/1292.xml?include_unpublished_marc=true [session: #"ms20", :login_time=>2022-10-25 08:51:09 -0500, :expirable=>true}, @system_mtime=2022-10-25 13:53:36 UTC, @id="80b6daef6fb6042b94f968ca2b5bf558a98ab137c258093385cdf2c7c36b303c">] D, [2022-10-25T08:53:44.236593 #6127] DEBUG -- : Thread-2024: Post-processed params: {:id=>1292, :repo_id=>2, :include_unpublished_marc=>true} E, [2022-10-25T08:53:44.410857 #6127] ERROR -- : Thread-2024: Unhandled exception! E, [2022-10-25T08:53:44.411180 #6127] ERROR -- : *wrong number of arguments (2 for 1)* */proj/WebApps/archivesspace271/plugins/dartmouth_udf_exports/backend/lib/aspace_patches.rb:96:in `from_aspace_object'* /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/models/marc21.rb:96:in `from_archival_object' /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/models/marc21.rb:105:in `from_resource' /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:81:in `generate_marc' /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:92:in `block in ArchivesSpaceService' Mang On Tue, Oct 25, 2022 at 6:29 AM Joshua D. Shaw wrote: > Without knowing what line is being referenced in the error, its hard to > know exactly what the issue might be, but I wouldn't suggest just using > this plugin as is since its very much customized for Dartmouth's use and > probably won't be what another institution might need (There are hard coded > references to Rauner Library in there!) > > Having said that, if you can pass along the line referenced in the error, > that should help with figuring out why the error is occurring. > > Joshua > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > mang.sun at rice.edu > *Sent:* Monday, October 24, 2022 4:19 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML > > We see the following error in the exported marcxml file with the plugin > enabled. Our AS version is 2.7.1. > > {"error":"wrong number of arguments (2 for 1)"} > > > Mang Sun > Rice U. > > On Wed, Oct 19, 2022 at 4:33 PM Joshua D. Shaw < > Joshua.D.Shaw at dartmouth.edu> wrote: > > Hi Rebecca > > This should get you started: > https://github.com/jdshaw/dartmouth_udf_exports > > Specifically: > https://github.com/jdshaw/dartmouth_udf_exports/blob/main/backend/lib/marc_user_defined_field_serialize.rb > > Its very much customized to our needs, but you should be able to use it as > a starting point. > > Joshua > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Rebecca Russell > *Sent:* Wednesday, October 19, 2022 5:24 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] User-defined fields in MARC-XML > > Hello, > > We are trying to figure out if there is a plug-in or other way to > configure user-defined fields (resources) so they export to MARC-XML? > > Many thanks in advance for any help with this question, > > Rebecca > > > -- > Rebecca Russell > > Archivist / Special Collections Librarian > Woodson Research Center > > Pronouns: she/her > > 713-348-5133 | http://library.rice.edu/woodson > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!hoZD86BZEammKoA9cQbsKq6cfvPbZJm3YheC1Aj7moUqNqJ1_XeftPrZU8gRA7KPQBEN57BH-3bis0109hOBv-joBc9B7-4aK1w$ > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!hQ0mk4EfR5xh6XBjQ__e4TlFtAapdDQnjWVI3gYNxiAw0AbX718I1pcn2TqTewR7gASmBCVpKsabyHY8ye8VV1k5yefcLyOQWhM$ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Tue Oct 25 10:15:44 2022 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Tue, 25 Oct 2022 14:15:44 +0000 Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML In-Reply-To: References: Message-ID: Hey Mang Do you happen to have any other plugins that might be patching the MARC export model (https://github.com/archivesspace/archivesspace/blob/v2.7.1/backend/app/exporters/models/marc21.rb)? It looks like this error is indicating that a call to self.from_aspace_object is supplying two arguments, but somewhere there's a version of that method that's only accepting one argument. In earlier versions of AS, that method only accepted one argument, so I'm wondering about an old plugin or something similar? Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of mang.sun at rice.edu Sent: Tuesday, October 25, 2022 9:59 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML Joshua, below are the lines around the error found in the log. D, [2022-10-25T08:53:44.232663 #6127] DEBUG -- : Thread-2024: GET /repositories/2/resources/marc21/1292.xml?include_unpublished_marc=true [session: #"ms20", :login_time=>2022-10-25 08:51:09 -0500, :expirable=>true}, @system_mtime=2022-10-25 13:53:36 UTC, @id="80b6daef6fb6042b94f968ca2b5bf558a98ab137c258093385cdf2c7c36b303c">] D, [2022-10-25T08:53:44.236593 #6127] DEBUG -- : Thread-2024: Post-processed params: {:id=>1292, :repo_id=>2, :include_unpublished_marc=>true} E, [2022-10-25T08:53:44.410857 #6127] ERROR -- : Thread-2024: Unhandled exception! E, [2022-10-25T08:53:44.411180 #6127] ERROR -- : wrong number of arguments (2 for 1) /proj/WebApps/archivesspace271/plugins/dartmouth_udf_exports/backend/lib/aspace_patches.rb:96:in `from_aspace_object' /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/models/marc21.rb:96:in `from_archival_object' /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/models/marc21.rb:105:in `from_resource' /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:81:in `generate_marc' /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:92:in `block in ArchivesSpaceService' Mang On Tue, Oct 25, 2022 at 6:29 AM Joshua D. Shaw > wrote: Without knowing what line is being referenced in the error, its hard to know exactly what the issue might be, but I wouldn't suggest just using this plugin as is since its very much customized for Dartmouth's use and probably won't be what another institution might need (There are hard coded references to Rauner Library in there!) Having said that, if you can pass along the line referenced in the error, that should help with figuring out why the error is occurring. Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of mang.sun at rice.edu > Sent: Monday, October 24, 2022 4:19 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML We see the following error in the exported marcxml file with the plugin enabled. Our AS version is 2.7.1. {"error":"wrong number of arguments (2 for 1)"} Mang Sun Rice U. On Wed, Oct 19, 2022 at 4:33 PM Joshua D. Shaw > wrote: Hi Rebecca This should get you started: https://github.com/jdshaw/dartmouth_udf_exports Specifically: https://github.com/jdshaw/dartmouth_udf_exports/blob/main/backend/lib/marc_user_defined_field_serialize.rb Its very much customized to our needs, but you should be able to use it as a starting point. Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Rebecca Russell > Sent: Wednesday, October 19, 2022 5:24 PM To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML Hello, We are trying to figure out if there is a plug-in or other way to configure user-defined fields (resources) so they export to MARC-XML? Many thanks in advance for any help with this question, Rebecca -- Rebecca Russell Archivist / Special Collections Librarian Woodson Research Center Pronouns: she/her 713-348-5133 | http://library.rice.edu/woodson _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!hoZD86BZEammKoA9cQbsKq6cfvPbZJm3YheC1Aj7moUqNqJ1_XeftPrZU8gRA7KPQBEN57BH-3bis0109hOBv-joBc9B7-4aK1w$ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!hQ0mk4EfR5xh6XBjQ__e4TlFtAapdDQnjWVI3gYNxiAw0AbX718I1pcn2TqTewR7gASmBCVpKsabyHY8ye8VV1k5yefcLyOQWhM$ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mang.sun at rice.edu Tue Oct 25 11:03:53 2022 From: mang.sun at rice.edu (mang.sun at rice.edu) Date: Tue, 25 Oct 2022 10:03:53 -0500 Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML In-Reply-To: References: Message-ID: No, Joshua. Even after I temporarily disabled all the other plugins but the Dartmouth one, the problem is still there. Mang On Tue, Oct 25, 2022 at 9:16 AM Joshua D. Shaw wrote: > Hey Mang > > Do you happen to have any other plugins that might be patching the MARC > export model ( > https://github.com/archivesspace/archivesspace/blob/v2.7.1/backend/app/exporters/models/marc21.rb > > )? > > It looks like this error is indicating that a call to > self.from_aspace_object is supplying two arguments, but somewhere there's a > version of that method that's only accepting one argument. > > In earlier versions of AS, that method only accepted one argument, so I'm > wondering about an old plugin or something similar? > > Joshua > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > mang.sun at rice.edu > *Sent:* Tuesday, October 25, 2022 9:59 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML > > Joshua, > below are the lines around the error found in the log. > > D, [2022-10-25T08:53:44.232663 #6127] DEBUG -- : Thread-2024: GET > /repositories/2/resources/marc21/1292.xml?include_unpublished_marc=true > [session: #"ms20", > :login_time=>2022-10-25 08:51:09 -0500, :expirable=>true}, > @system_mtime=2022-10-25 13:53:36 UTC, > @id="80b6daef6fb6042b94f968ca2b5bf558a98ab137c258093385cdf2c7c36b303c">] > D, [2022-10-25T08:53:44.236593 #6127] DEBUG -- : Thread-2024: > Post-processed params: {:id=>1292, :repo_id=>2, > :include_unpublished_marc=>true} > E, [2022-10-25T08:53:44.410857 #6127] ERROR -- : Thread-2024: Unhandled > exception! > E, [2022-10-25T08:53:44.411180 #6127] ERROR -- : > *wrong number of arguments (2 for 1)* > */proj/WebApps/archivesspace271/plugins/dartmouth_udf_exports/backend/lib/aspace_patches.rb:96:in > `from_aspace_object'* > /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/models/marc21.rb:96:in > `from_archival_object' > /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/models/marc21.rb:105:in > `from_resource' > /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:81:in > `generate_marc' > /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:92:in > `block in ArchivesSpaceService' > > Mang > > On Tue, Oct 25, 2022 at 6:29 AM Joshua D. Shaw < > Joshua.D.Shaw at dartmouth.edu> wrote: > > Without knowing what line is being referenced in the error, its hard to > know exactly what the issue might be, but I wouldn't suggest just using > this plugin as is since its very much customized for Dartmouth's use and > probably won't be what another institution might need (There are hard coded > references to Rauner Library in there!) > > Having said that, if you can pass along the line referenced in the error, > that should help with figuring out why the error is occurring. > > Joshua > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > mang.sun at rice.edu > *Sent:* Monday, October 24, 2022 4:19 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML > > We see the following error in the exported marcxml file with the plugin > enabled. Our AS version is 2.7.1. > > {"error":"wrong number of arguments (2 for 1)"} > > > Mang Sun > Rice U. > > On Wed, Oct 19, 2022 at 4:33 PM Joshua D. Shaw < > Joshua.D.Shaw at dartmouth.edu> wrote: > > Hi Rebecca > > This should get you started: > https://github.com/jdshaw/dartmouth_udf_exports > > Specifically: > https://github.com/jdshaw/dartmouth_udf_exports/blob/main/backend/lib/marc_user_defined_field_serialize.rb > > Its very much customized to our needs, but you should be able to use it as > a starting point. > > Joshua > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Rebecca Russell > *Sent:* Wednesday, October 19, 2022 5:24 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] User-defined fields in MARC-XML > > Hello, > > We are trying to figure out if there is a plug-in or other way to > configure user-defined fields (resources) so they export to MARC-XML? > > Many thanks in advance for any help with this question, > > Rebecca > > > -- > Rebecca Russell > > Archivist / Special Collections Librarian > Woodson Research Center > > Pronouns: she/her > > 713-348-5133 | http://library.rice.edu/woodson > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!hoZD86BZEammKoA9cQbsKq6cfvPbZJm3YheC1Aj7moUqNqJ1_XeftPrZU8gRA7KPQBEN57BH-3bis0109hOBv-joBc9B7-4aK1w$ > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!hQ0mk4EfR5xh6XBjQ__e4TlFtAapdDQnjWVI3gYNxiAw0AbX718I1pcn2TqTewR7gASmBCVpKsabyHY8ye8VV1k5yefcLyOQWhM$ > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!mDxECcBD1G4AEk4aTz6M542xY4ZLgiCwlxvmKcWAz2_1OQKsCd6cakb-4q6XcdTo23ykb-nwpNpPsFjf6M21GR1KFxF13ANKntE$ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Tue Oct 25 11:19:22 2022 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Tue, 25 Oct 2022 15:19:22 +0000 Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML In-Reply-To: References: Message-ID: Interesting. Let me fire up a 2.7.1 instance locally and see what's up. We haven't been on 2.7.1 in a while so it might take me a sec to see what's up. jds ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of mang.sun at rice.edu Sent: Tuesday, October 25, 2022 11:03 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML No, Joshua. Even after I temporarily disabled all the other plugins but the Dartmouth one, the problem is still there. Mang On Tue, Oct 25, 2022 at 9:16 AM Joshua D. Shaw > wrote: Hey Mang Do you happen to have any other plugins that might be patching the MARC export model (https://github.com/archivesspace/archivesspace/blob/v2.7.1/backend/app/exporters/models/marc21.rb)? It looks like this error is indicating that a call to self.from_aspace_object is supplying two arguments, but somewhere there's a version of that method that's only accepting one argument. In earlier versions of AS, that method only accepted one argument, so I'm wondering about an old plugin or something similar? Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of mang.sun at rice.edu > Sent: Tuesday, October 25, 2022 9:59 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML Joshua, below are the lines around the error found in the log. D, [2022-10-25T08:53:44.232663 #6127] DEBUG -- : Thread-2024: GET /repositories/2/resources/marc21/1292.xml?include_unpublished_marc=true [session: #"ms20", :login_time=>2022-10-25 08:51:09 -0500, :expirable=>true}, @system_mtime=2022-10-25 13:53:36 UTC, @id="80b6daef6fb6042b94f968ca2b5bf558a98ab137c258093385cdf2c7c36b303c">] D, [2022-10-25T08:53:44.236593 #6127] DEBUG -- : Thread-2024: Post-processed params: {:id=>1292, :repo_id=>2, :include_unpublished_marc=>true} E, [2022-10-25T08:53:44.410857 #6127] ERROR -- : Thread-2024: Unhandled exception! E, [2022-10-25T08:53:44.411180 #6127] ERROR -- : wrong number of arguments (2 for 1) /proj/WebApps/archivesspace271/plugins/dartmouth_udf_exports/backend/lib/aspace_patches.rb:96:in `from_aspace_object' /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/models/marc21.rb:96:in `from_archival_object' /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/models/marc21.rb:105:in `from_resource' /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:81:in `generate_marc' /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:92:in `block in ArchivesSpaceService' Mang On Tue, Oct 25, 2022 at 6:29 AM Joshua D. Shaw > wrote: Without knowing what line is being referenced in the error, its hard to know exactly what the issue might be, but I wouldn't suggest just using this plugin as is since its very much customized for Dartmouth's use and probably won't be what another institution might need (There are hard coded references to Rauner Library in there!) Having said that, if you can pass along the line referenced in the error, that should help with figuring out why the error is occurring. Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of mang.sun at rice.edu > Sent: Monday, October 24, 2022 4:19 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML We see the following error in the exported marcxml file with the plugin enabled. Our AS version is 2.7.1. {"error":"wrong number of arguments (2 for 1)"} Mang Sun Rice U. On Wed, Oct 19, 2022 at 4:33 PM Joshua D. Shaw > wrote: Hi Rebecca This should get you started: https://github.com/jdshaw/dartmouth_udf_exports Specifically: https://github.com/jdshaw/dartmouth_udf_exports/blob/main/backend/lib/marc_user_defined_field_serialize.rb Its very much customized to our needs, but you should be able to use it as a starting point. Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Rebecca Russell > Sent: Wednesday, October 19, 2022 5:24 PM To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML Hello, We are trying to figure out if there is a plug-in or other way to configure user-defined fields (resources) so they export to MARC-XML? Many thanks in advance for any help with this question, Rebecca -- Rebecca Russell Archivist / Special Collections Librarian Woodson Research Center Pronouns: she/her 713-348-5133 | http://library.rice.edu/woodson _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!hoZD86BZEammKoA9cQbsKq6cfvPbZJm3YheC1Aj7moUqNqJ1_XeftPrZU8gRA7KPQBEN57BH-3bis0109hOBv-joBc9B7-4aK1w$ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!hQ0mk4EfR5xh6XBjQ__e4TlFtAapdDQnjWVI3gYNxiAw0AbX718I1pcn2TqTewR7gASmBCVpKsabyHY8ye8VV1k5yefcLyOQWhM$ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!mDxECcBD1G4AEk4aTz6M542xY4ZLgiCwlxvmKcWAz2_1OQKsCd6cakb-4q6XcdTo23ykb-nwpNpPsFjf6M21GR1KFxF13ANKntE$ -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Wed Oct 26 09:42:30 2022 From: livsolis at utexas.edu (Olivia S Solis) Date: Wed, 26 Oct 2022 08:42:30 -0500 Subject: [Archivesspace_Users_Group] collection_id/Resource Identifier in import spreadsheet Message-ID: Hello all, We have been using the spreadsheet importer for bulk adding archival objects for years, using the EAD ID column to link to the correct resource. We had a situation pop up where we may not have that number assigned yet, but we want to upload part of the inventory. I tried using column B (collection_id/Resource identifier) to link to the right resource. I don't know what I am doing wrong, but I can't get the AOs to get created with column B. The documentation in the original Harvard spreadsheet (which we still use a version of because of a lot of customization added) defined the field like so: "The Resource "Identifier", aka collection-level unit_id, OR, could be internal resource record number from URL." I keep getting the following error: Row 6: ERROR Row 6 will not be processed due to errors: This row is missing BOTH an EAD ID and URI I tried the Identifier field: [image: Screen Shot 2022-10-26 at 8.34.36 AM.png] I tried it as it appears in the database: "camh-arc-004438", null,null,null I tried the path given in the URI: [image: Screen Shot 2022-10-26 at 8.34.50 AM.png] And I tried just the numeric ID, in the case above 4398. What am I doing wrong here? I can't think of many other identifiers that are unique to the record. Thanks, Olivia -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2022-10-26 at 8.34.36 AM.png Type: image/png Size: 5718 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2022-10-26 at 8.34.50 AM.png Type: image/png Size: 6317 bytes Desc: not available URL: From leah.tams at duke.edu Wed Oct 26 09:54:17 2022 From: leah.tams at duke.edu (Leah Tams) Date: Wed, 26 Oct 2022 13:54:17 +0000 Subject: [Archivesspace_Users_Group] collection_id/Resource Identifier in import spreadsheet In-Reply-To: References: Message-ID: Hi Olivia, I wonder if the identifier should actually appear with periods, rather than hyphens, between the elements? That is how we input them in our import spreadsheet at Duke. They appear as RL-12345 in ASpace, but in the spreadsheet we have to put RL.12345. I don?t have access to our database, though, so I?m not sure what they look like on that end. Best, Leah she/her/hers MSLS in Archives & Records Management Accessions Coordinator Rubenstein Rare Book & Manuscript Library Duke University leah.tams at duke.edu | leahtams.org From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Olivia S Solis Sent: Wednesday, October 26, 2022 9:43 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] collection_id/Resource Identifier in import spreadsheet Hello all, We have been using the spreadsheet importer for bulk adding archival objects for years, using the EAD ID column to link to the correct resource. We had a situation pop up where we may not have that number assigned yet, but we want to upload part of the inventory. I tried using column B (collection_id/Resource identifier) to link to the right resource. I don't know what I am doing wrong, but I can't get the AOs to get created with column B. The documentation in the original Harvard spreadsheet (which we still use a version of because of a lot of customization added) defined the field like so: "The Resource "Identifier", aka collection-level unit_id, OR, could be internal resource record number from URL." I keep getting the following error: Row 6: ERROR Row 6 will not be processed due to errors: This row is missing BOTH an EAD ID and URI I tried the Identifier field: [Screen Shot 2022-10-26 at 8.34.36 AM.png] I tried it as it appears in the database: "camh-arc-004438", null,null,null I tried the path given in the URI: [Screen Shot 2022-10-26 at 8.34.50 AM.png] And I tried just the numeric ID, in the case above 4398. What am I doing wrong here? I can't think of many other identifiers that are unique to the record. Thanks, Olivia -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5718 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 6317 bytes Desc: image002.png URL: From livsolis at utexas.edu Wed Oct 26 09:58:16 2022 From: livsolis at utexas.edu (Olivia S Solis) Date: Wed, 26 Oct 2022 08:58:16 -0500 Subject: [Archivesspace_Users_Group] collection_id/Resource Identifier in import spreadsheet In-Reply-To: References: Message-ID: Our identifier is all in the first box. We have an autoincrement system that works just there. Would the dashes cause problems? On Wed, Oct 26, 2022 at 8:54 AM Leah Tams wrote: > Hi Olivia, > > > > I wonder if the identifier should actually appear with periods, rather > than hyphens, between the elements? That is how we input them in our import > spreadsheet at Duke. They appear as RL-12345 in ASpace, but in the > spreadsheet we have to put RL.12345. I don?t have access to our database, > though, so I?m not sure what they look like on that end. > > > > Best, > > Leah > > > > *she/her/hers* > > MSLS in Archives & Records Management > > Accessions Coordinator > > Rubenstein Rare Book & Manuscript Library > > Duke University > > leah.tams at duke.edu | leahtams.org > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Olivia > S Solis > *Sent:* Wednesday, October 26, 2022 9:43 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] collection_id/Resource Identifier > in import spreadsheet > > > > Hello all, > > > > We have been using the spreadsheet importer for bulk adding archival > objects for years, using the EAD ID column to link to the correct resource. > We had a situation pop up where we may not have that number assigned yet, > but we want to upload part of the inventory. I tried using column B > (collection_id/Resource identifier) to link to the right resource. > > > > I don't know what I am doing wrong, but I can't get the AOs to get created > with column B. The documentation in the original Harvard spreadsheet (which > we still use a version of because of a lot of customization added) defined > the field like so: "The Resource "Identifier", aka collection-level > unit_id, OR, could be internal resource record number from URL." > > > > I keep getting the following error: Row 6: ERROR Row 6 will not be > processed due to errors: This row is missing BOTH an EAD ID and URI > > I tried the Identifier field: > > [image: Screen Shot 2022-10-26 at 8.34.36 AM.png] > > I tried it as it appears in the database: "camh-arc-004438", null,null,null > > I tried the path given in the URI: > > [image: Screen Shot 2022-10-26 at 8.34.50 AM.png] > > And I tried just the numeric ID, in the case above 4398. > > > > What am I doing wrong here? I can't think of many other identifiers that > are unique to the record. > > > > Thanks, > > Olivia > > > > -- > > Olivia Solis, MSIS (she/her) > > Metadata Coordinator > > Dolph Briscoe Center for American History > > The University of Texas at Austin > > 2300 Red River St. Stop D1100 > > Austin TX, 78712-1426 > > (512) 232-8013 > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > >> This message is from an external sender. Learn more about why this << > >> matters at https://links.utexas.edu/rtyclf. << > -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5718 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 6317 bytes Desc: not available URL: From lcalahan at umn.edu Wed Oct 26 11:23:50 2022 From: lcalahan at umn.edu (Lisa Calahan) Date: Wed, 26 Oct 2022 10:23:50 -0500 Subject: [Archivesspace_Users_Group] collection_id/Resource Identifier in import spreadsheet In-Reply-To: References: Message-ID: I wonder if the identifier needs to match the data in the EAD ID field within the Finding Aid Data subrecord? I had an issue with that before and it solved my problem, but I'm not using the Harvard spreadsheet. Might be worth a try, though? Lisa On Wed, Oct 26, 2022 at 8:58 AM Olivia S Solis wrote: > Our identifier is all in the first box. We have an autoincrement system > that works just there. Would the dashes cause problems? > > On Wed, Oct 26, 2022 at 8:54 AM Leah Tams wrote: > >> Hi Olivia, >> >> >> >> I wonder if the identifier should actually appear with periods, rather >> than hyphens, between the elements? That is how we input them in our import >> spreadsheet at Duke. They appear as RL-12345 in ASpace, but in the >> spreadsheet we have to put RL.12345. I don?t have access to our database, >> though, so I?m not sure what they look like on that end. >> >> >> >> Best, >> >> Leah >> >> >> >> *she/her/hers* >> >> MSLS in Archives & Records Management >> >> Accessions Coordinator >> >> Rubenstein Rare Book & Manuscript Library >> >> Duke University >> >> leah.tams at duke.edu | leahtams.org >> >> >> >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >> archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Olivia >> S Solis >> *Sent:* Wednesday, October 26, 2022 9:43 AM >> *To:* Archivesspace Users Group < >> archivesspace_users_group at lyralists.lyrasis.org> >> *Subject:* [Archivesspace_Users_Group] collection_id/Resource Identifier >> in import spreadsheet >> >> >> >> Hello all, >> >> >> >> We have been using the spreadsheet importer for bulk adding archival >> objects for years, using the EAD ID column to link to the correct resource. >> We had a situation pop up where we may not have that number assigned yet, >> but we want to upload part of the inventory. I tried using column B >> (collection_id/Resource identifier) to link to the right resource. >> >> >> >> I don't know what I am doing wrong, but I can't get the AOs to get >> created with column B. The documentation in the original Harvard >> spreadsheet (which we still use a version of because of a lot of >> customization added) defined the field like so: "The Resource "Identifier", >> aka collection-level unit_id, OR, could be internal resource record number >> from URL." >> >> >> >> I keep getting the following error: Row 6: ERROR Row 6 will not be >> processed due to errors: This row is missing BOTH an EAD ID and URI >> >> I tried the Identifier field: >> >> [image: Screen Shot 2022-10-26 at 8.34.36 AM.png] >> >> I tried it as it appears in the database: "camh-arc-004438", >> null,null,null >> >> I tried the path given in the URI: >> >> [image: Screen Shot 2022-10-26 at 8.34.50 AM.png] >> >> And I tried just the numeric ID, in the case above 4398. >> >> >> >> What am I doing wrong here? I can't think of many other identifiers that >> are unique to the record. >> >> >> >> Thanks, >> >> Olivia >> >> >> >> -- >> >> Olivia Solis, MSIS (she/her) >> >> Metadata Coordinator >> >> Dolph Briscoe Center for American History >> >> The University of Texas at Austin >> >> 2300 Red River St. Stop D1100 >> >> Austin TX, 78712-1426 >> >> (512) 232-8013 >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> This message is from an external sender. Learn more about why this << >> >> matters at https://links.utexas.edu/rtyclf. << >> > > > -- > Olivia Solis, MSIS (she/her) > Metadata Coordinator > Dolph Briscoe Center for American History > The University of Texas at Austin > 2300 Red River St. Stop D1100 > Austin TX, 78712-1426 > (512) 232-8013 > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Pronouns: she/they Head of Archival Processing University of Minnesota Libraries Archives and Special Collections Elmer L. Andersen Library *I acknowledge that the University of Minnesota is located on the traditional, ancestral and contemporary lands of Indigenous people and was built with money from slaveholders . * -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5718 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 6317 bytes Desc: not available URL: From livsolis at utexas.edu Wed Oct 26 11:40:03 2022 From: livsolis at utexas.edu (Olivia S Solis) Date: Wed, 26 Oct 2022 10:40:03 -0500 Subject: [Archivesspace_Users_Group] collection_id/Resource Identifier in import spreadsheet In-Reply-To: References: Message-ID: Well, we definitely have successfully used the EAD ID field value to link via column C in the spreadsheet importer for a long time. We have a specific use case where we want to add lines of inventory to a resource before we assign the EAD ID. Our EAD ID and the value of what is in Identifier are not the same. I'm having trouble figuring out in what form the plugin wants info in column B. :( On Wed, Oct 26, 2022 at 10:24 AM Lisa Calahan wrote: > I wonder if the identifier needs to match the data in the EAD ID field > within the Finding Aid Data subrecord? I had an issue with that before and > it solved my problem, but I'm not using the Harvard spreadsheet. > > Might be worth a try, though? > Lisa > > On Wed, Oct 26, 2022 at 8:58 AM Olivia S Solis > wrote: > >> Our identifier is all in the first box. We have an autoincrement system >> that works just there. Would the dashes cause problems? >> >> On Wed, Oct 26, 2022 at 8:54 AM Leah Tams wrote: >> >>> Hi Olivia, >>> >>> >>> >>> I wonder if the identifier should actually appear with periods, rather >>> than hyphens, between the elements? That is how we input them in our import >>> spreadsheet at Duke. They appear as RL-12345 in ASpace, but in the >>> spreadsheet we have to put RL.12345. I don?t have access to our database, >>> though, so I?m not sure what they look like on that end. >>> >>> >>> >>> Best, >>> >>> Leah >>> >>> >>> >>> *she/her/hers* >>> >>> MSLS in Archives & Records Management >>> >>> Accessions Coordinator >>> >>> Rubenstein Rare Book & Manuscript Library >>> >>> Duke University >>> >>> leah.tams at duke.edu | leahtams.org >>> >>> >>> >>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >>> archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Olivia >>> S Solis >>> *Sent:* Wednesday, October 26, 2022 9:43 AM >>> *To:* Archivesspace Users Group < >>> archivesspace_users_group at lyralists.lyrasis.org> >>> *Subject:* [Archivesspace_Users_Group] collection_id/Resource >>> Identifier in import spreadsheet >>> >>> >>> >>> Hello all, >>> >>> >>> >>> We have been using the spreadsheet importer for bulk adding archival >>> objects for years, using the EAD ID column to link to the correct resource. >>> We had a situation pop up where we may not have that number assigned yet, >>> but we want to upload part of the inventory. I tried using column B >>> (collection_id/Resource identifier) to link to the right resource. >>> >>> >>> >>> I don't know what I am doing wrong, but I can't get the AOs to get >>> created with column B. The documentation in the original Harvard >>> spreadsheet (which we still use a version of because of a lot of >>> customization added) defined the field like so: "The Resource "Identifier", >>> aka collection-level unit_id, OR, could be internal resource record number >>> from URL." >>> >>> >>> >>> I keep getting the following error: Row 6: ERROR Row 6 will not be >>> processed due to errors: This row is missing BOTH an EAD ID and URI >>> >>> I tried the Identifier field: >>> >>> [image: Screen Shot 2022-10-26 at 8.34.36 AM.png] >>> >>> I tried it as it appears in the database: "camh-arc-004438", >>> null,null,null >>> >>> I tried the path given in the URI: >>> >>> [image: Screen Shot 2022-10-26 at 8.34.50 AM.png] >>> >>> And I tried just the numeric ID, in the case above 4398. >>> >>> >>> >>> What am I doing wrong here? I can't think of many other identifiers that >>> are unique to the record. >>> >>> >>> >>> Thanks, >>> >>> Olivia >>> >>> >>> >>> -- >>> >>> Olivia Solis, MSIS (she/her) >>> >>> Metadata Coordinator >>> >>> Dolph Briscoe Center for American History >>> >>> The University of Texas at Austin >>> >>> 2300 Red River St. Stop D1100 >>> >>> Austin TX, 78712-1426 >>> >>> (512) 232-8013 >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >> This message is from an external sender. Learn more about why this << >>> >> matters at https://links.utexas.edu/rtyclf. << >>> >> >> >> -- >> Olivia Solis, MSIS (she/her) >> Metadata Coordinator >> Dolph Briscoe Center for American History >> The University of Texas at Austin >> 2300 Red River St. Stop D1100 >> Austin TX, 78712-1426 >> (512) 232-8013 >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > Pronouns: she/they > Head of Archival Processing > University of Minnesota Libraries > Archives and Special Collections > Elmer L. Andersen Library > > *I acknowledge that the University of Minnesota is located > on the > traditional, ancestral and contemporary lands of Indigenous people > and > was built with money from slaveholders > . * > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > >> This message is from an external sender. Learn more about why this << > >> matters at https://links.utexas.edu/rtyclf. << > -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5718 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 6317 bytes Desc: not available URL: From vaddonizio at atlas-sys.com Wed Oct 26 14:07:46 2022 From: vaddonizio at atlas-sys.com (Valerie Addonizio) Date: Wed, 26 Oct 2022 18:07:46 +0000 Subject: [Archivesspace_Users_Group] collection_id/Resource Identifier in import spreadsheet In-Reply-To: References: Message-ID: Hi Olivia! Are you on the most recent version of ArchivesSpace and have you refreshened your import spreadsheet with the most recent template? https://github.com/archivesspace/archivesspace/tree/master/templates or accessible from inside ASpace from Gear Menu --> Bulk Import Templates. Using that version linked above, I would use Column D, res_uri, which takes the URI that you already identified at the top of the resource record, something similar to /repositories/2/resources/42. I find that column much more user friendly. I am not sure that you strictly need the most recent version of AS for that template to work, but I would consider updating your templates every time you update ASpace itself. -Valerie From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Olivia S Solis Sent: Wednesday, October 26, 2022 11:40 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] collection_id/Resource Identifier in import spreadsheet Well, we definitely have successfully used the EAD ID field value to link via column C in the spreadsheet importer for a long time. We have a specific use case where we want to add lines of inventory to a resource before we assign the EAD ID. Our EAD ID and the value of what is in Identifier are not the same. I'm having trouble figuring out in what form the plugin wants info in column B. :( On Wed, Oct 26, 2022 at 10:24 AM Lisa Calahan > wrote: I wonder if the identifier needs to match the data in the EAD ID field within the Finding Aid Data subrecord? I had an issue with that before and it solved my problem, but I'm not using the Harvard spreadsheet. Might be worth a try, though? Lisa On Wed, Oct 26, 2022 at 8:58 AM Olivia S Solis > wrote: Our identifier is all in the first box. We have an autoincrement system that works just there. Would the dashes cause problems? On Wed, Oct 26, 2022 at 8:54 AM Leah Tams > wrote: Hi Olivia, I wonder if the identifier should actually appear with periods, rather than hyphens, between the elements? That is how we input them in our import spreadsheet at Duke. They appear as RL-12345 in ASpace, but in the spreadsheet we have to put RL.12345. I don?t have access to our database, though, so I?m not sure what they look like on that end. Best, Leah she/her/hers MSLS in Archives & Records Management Accessions Coordinator Rubenstein Rare Book & Manuscript Library Duke University leah.tams at duke.edu | leahtams.org From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Olivia S Solis Sent: Wednesday, October 26, 2022 9:43 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] collection_id/Resource Identifier in import spreadsheet Hello all, We have been using the spreadsheet importer for bulk adding archival objects for years, using the EAD ID column to link to the correct resource. We had a situation pop up where we may not have that number assigned yet, but we want to upload part of the inventory. I tried using column B (collection_id/Resource identifier) to link to the right resource. I don't know what I am doing wrong, but I can't get the AOs to get created with column B. The documentation in the original Harvard spreadsheet (which we still use a version of because of a lot of customization added) defined the field like so: "The Resource "Identifier", aka collection-level unit_id, OR, could be internal resource record number from URL." I keep getting the following error: Row 6: ERROR Row 6 will not be processed due to errors: This row is missing BOTH an EAD ID and URI I tried the Identifier field: [Screen Shot 2022-10-26 at 8.34.36 AM.png] I tried it as it appears in the database: "camh-arc-004438", null,null,null I tried the path given in the URI: [Screen Shot 2022-10-26 at 8.34.50 AM.png] And I tried just the numeric ID, in the case above 4398. What am I doing wrong here? I can't think of many other identifiers that are unique to the record. Thanks, Olivia -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> This message is from an external sender. Learn more about why this << >> matters at https://links.utexas.edu/rtyclf. << -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Pronouns: she/they Head of Archival Processing University of Minnesota Libraries Archives and Special Collections Elmer L. Andersen Library I acknowledge that the University of Minnesota is located on the traditional, ancestral and contemporary lands of Indigenous people and was built with money from slaveholders. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> This message is from an external sender. Learn more about why this << >> matters at https://links.utexas.edu/rtyclf. << -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5718 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 6317 bytes Desc: image002.png URL: From mang.sun at rice.edu Wed Oct 26 16:38:04 2022 From: mang.sun at rice.edu (mang.sun at rice.edu) Date: Wed, 26 Oct 2022 15:38:04 -0500 Subject: [Archivesspace_Users_Group] User-defined fields in MARC-XML In-Reply-To: References: Message-ID: Finally, thanks to Joshua's help off the list, the problem was found caused by the outdated plugin I downloaded from https://github.com/hudmol/dartmouth_udf_exports. Checking out one from https://github.com/jdshaw/dartmouth_udf_exports solved the issue. Mang On Tue, Oct 25, 2022 at 10:19 AM Joshua D. Shaw wrote: > Interesting. Let me fire up a 2.7.1 instance locally and see what's up. We > haven't been on 2.7.1 in a while so it might take me a sec to see what's up. > > jds > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > mang.sun at rice.edu > *Sent:* Tuesday, October 25, 2022 11:03 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML > > No, Joshua. Even after I temporarily disabled all the other plugins but > the Dartmouth one, the problem is still there. > > Mang > > On Tue, Oct 25, 2022 at 9:16 AM Joshua D. Shaw < > Joshua.D.Shaw at dartmouth.edu> wrote: > > Hey Mang > > Do you happen to have any other plugins that might be patching the MARC > export model ( > https://github.com/archivesspace/archivesspace/blob/v2.7.1/backend/app/exporters/models/marc21.rb > > )? > > It looks like this error is indicating that a call to > self.from_aspace_object is supplying two arguments, but somewhere there's a > version of that method that's only accepting one argument. > > In earlier versions of AS, that method only accepted one argument, so I'm > wondering about an old plugin or something similar? > > Joshua > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > mang.sun at rice.edu > *Sent:* Tuesday, October 25, 2022 9:59 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML > > Joshua, > below are the lines around the error found in the log. > > D, [2022-10-25T08:53:44.232663 #6127] DEBUG -- : Thread-2024: GET > /repositories/2/resources/marc21/1292.xml?include_unpublished_marc=true > [session: #"ms20", > :login_time=>2022-10-25 08:51:09 -0500, :expirable=>true}, > @system_mtime=2022-10-25 13:53:36 UTC, > @id="80b6daef6fb6042b94f968ca2b5bf558a98ab137c258093385cdf2c7c36b303c">] > D, [2022-10-25T08:53:44.236593 #6127] DEBUG -- : Thread-2024: > Post-processed params: {:id=>1292, :repo_id=>2, > :include_unpublished_marc=>true} > E, [2022-10-25T08:53:44.410857 #6127] ERROR -- : Thread-2024: Unhandled > exception! > E, [2022-10-25T08:53:44.411180 #6127] ERROR -- : > *wrong number of arguments (2 for 1)* > */proj/WebApps/archivesspace271/plugins/dartmouth_udf_exports/backend/lib/aspace_patches.rb:96:in > `from_aspace_object'* > /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/models/marc21.rb:96:in > `from_archival_object' > /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/models/marc21.rb:105:in > `from_resource' > /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:81:in > `generate_marc' > /proj/WebApps/archivesspace271/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:92:in > `block in ArchivesSpaceService' > > Mang > > On Tue, Oct 25, 2022 at 6:29 AM Joshua D. Shaw < > Joshua.D.Shaw at dartmouth.edu> wrote: > > Without knowing what line is being referenced in the error, its hard to > know exactly what the issue might be, but I wouldn't suggest just using > this plugin as is since its very much customized for Dartmouth's use and > probably won't be what another institution might need (There are hard coded > references to Rauner Library in there!) > > Having said that, if you can pass along the line referenced in the error, > that should help with figuring out why the error is occurring. > > Joshua > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > mang.sun at rice.edu > *Sent:* Monday, October 24, 2022 4:19 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] User-defined fields in MARC-XML > > We see the following error in the exported marcxml file with the plugin > enabled. Our AS version is 2.7.1. > > {"error":"wrong number of arguments (2 for 1)"} > > > Mang Sun > Rice U. > > On Wed, Oct 19, 2022 at 4:33 PM Joshua D. Shaw < > Joshua.D.Shaw at dartmouth.edu> wrote: > > Hi Rebecca > > This should get you started: > https://github.com/jdshaw/dartmouth_udf_exports > > Specifically: > https://github.com/jdshaw/dartmouth_udf_exports/blob/main/backend/lib/marc_user_defined_field_serialize.rb > > Its very much customized to our needs, but you should be able to use it as > a starting point. > > Joshua > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Rebecca Russell > *Sent:* Wednesday, October 19, 2022 5:24 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] User-defined fields in MARC-XML > > Hello, > > We are trying to figure out if there is a plug-in or other way to > configure user-defined fields (resources) so they export to MARC-XML? > > Many thanks in advance for any help with this question, > > Rebecca > > > -- > Rebecca Russell > > Archivist / Special Collections Librarian > Woodson Research Center > > Pronouns: she/her > > 713-348-5133 | http://library.rice.edu/woodson > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!hoZD86BZEammKoA9cQbsKq6cfvPbZJm3YheC1Aj7moUqNqJ1_XeftPrZU8gRA7KPQBEN57BH-3bis0109hOBv-joBc9B7-4aK1w$ > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!hQ0mk4EfR5xh6XBjQ__e4TlFtAapdDQnjWVI3gYNxiAw0AbX718I1pcn2TqTewR7gASmBCVpKsabyHY8ye8VV1k5yefcLyOQWhM$ > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!mDxECcBD1G4AEk4aTz6M542xY4ZLgiCwlxvmKcWAz2_1OQKsCd6cakb-4q6XcdTo23ykb-nwpNpPsFjf6M21GR1KFxF13ANKntE$ > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!BuQPrrmRaQ!n59nMfmKC1iRMfDccAXVdRC5LNgwNN2s7ScDUiu26_7C7aBA02CWCtUZNrnrtOeOXX3p6RjdgBBC4Lt1PhjC6UG2u8-_1kQYQhY$ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Thu Oct 27 09:03:27 2022 From: livsolis at utexas.edu (Olivia S Solis) Date: Thu, 27 Oct 2022 08:03:27 -0500 Subject: [Archivesspace_Users_Group] collection_id/Resource Identifier in import spreadsheet In-Reply-To: References: Message-ID: Thank you! That is it. We have added a lot of validation to the spreadsheet, so redoing that every update would take a lot of work. But we can certainly do a diff for any column header changes. Thank you everyone for all your help! -Olivia On Wed, Oct 26, 2022 at 1:07 PM Valerie Addonizio wrote: > Hi Olivia! > > > > Are you on the most recent version of ArchivesSpace and have you > refreshened your import spreadsheet with the most recent template? > https://github.com/archivesspace/archivesspace/tree/master/templates or > accessible from inside ASpace from Gear Menu --> Bulk Import Templates. > > > > Using that version linked above, I would use Column D, *res_uri*, which > takes the URI that you already identified at the top of the resource > record, something similar to /repositories/2/resources/42. I find that > column much more user friendly. > > > > I am not sure that you strictly need *the* most recent version of AS for > that template to work, but I would consider updating your templates every > time you update ASpace itself. > > > > -Valerie > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Olivia > S Solis > *Sent:* Wednesday, October 26, 2022 11:40 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] collection_id/Resource > Identifier in import spreadsheet > > > > Well, we definitely have successfully used the EAD ID field value to link > via column C in the spreadsheet importer for a long time. We have a > specific use case where we want to add lines of inventory to a resource > before we assign the EAD ID. Our EAD ID and the value of what is in > Identifier are not the same. I'm having trouble figuring out in what form > the plugin wants info in column B. :( > > > > On Wed, Oct 26, 2022 at 10:24 AM Lisa Calahan wrote: > > I wonder if the identifier needs to match the data in the EAD ID field > within the Finding Aid Data subrecord? I had an issue with that before and > it solved my problem, but I'm not using the Harvard spreadsheet. > > > > Might be worth a try, though? > > Lisa > > > > On Wed, Oct 26, 2022 at 8:58 AM Olivia S Solis > wrote: > > Our identifier is all in the first box. We have an autoincrement system > that works just there. Would the dashes cause problems? > > > > On Wed, Oct 26, 2022 at 8:54 AM Leah Tams wrote: > > Hi Olivia, > > > > I wonder if the identifier should actually appear with periods, rather > than hyphens, between the elements? That is how we input them in our import > spreadsheet at Duke. They appear as RL-12345 in ASpace, but in the > spreadsheet we have to put RL.12345. I don?t have access to our database, > though, so I?m not sure what they look like on that end. > > > > Best, > > Leah > > > > *she/her/hers* > > MSLS in Archives & Records Management > > Accessions Coordinator > > Rubenstein Rare Book & Manuscript Library > > Duke University > > leah.tams at duke.edu | leahtams.org > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Olivia > S Solis > *Sent:* Wednesday, October 26, 2022 9:43 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] collection_id/Resource Identifier > in import spreadsheet > > > > Hello all, > > > > We have been using the spreadsheet importer for bulk adding archival > objects for years, using the EAD ID column to link to the correct resource. > We had a situation pop up where we may not have that number assigned yet, > but we want to upload part of the inventory. I tried using column B > (collection_id/Resource identifier) to link to the right resource. > > > > I don't know what I am doing wrong, but I can't get the AOs to get created > with column B. The documentation in the original Harvard spreadsheet (which > we still use a version of because of a lot of customization added) defined > the field like so: "The Resource "Identifier", aka collection-level > unit_id, OR, could be internal resource record number from URL." > > > > I keep getting the following error: Row 6: ERROR Row 6 will not be > processed due to errors: This row is missing BOTH an EAD ID and URI > > I tried the Identifier field: > > [image: Screen Shot 2022-10-26 at 8.34.36 AM.png] > > I tried it as it appears in the database: "camh-arc-004438", null,null,null > > I tried the path given in the URI: > > [image: Screen Shot 2022-10-26 at 8.34.50 AM.png] > > And I tried just the numeric ID, in the case above 4398. > > > > What am I doing wrong here? I can't think of many other identifiers that > are unique to the record. > > > > Thanks, > > Olivia > > > > -- > > Olivia Solis, MSIS (she/her) > > Metadata Coordinator > > Dolph Briscoe Center for American History > > The University of Texas at Austin > > 2300 Red River St. Stop D1100 > > Austin TX, 78712-1426 > > (512) 232-8013 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > >> This message is from an external sender. Learn more about why this << > >> matters at https://links.utexas.edu/rtyclf. << > > > > > -- > > Olivia Solis, MSIS (she/her) > > Metadata Coordinator > > Dolph Briscoe Center for American History > > The University of Texas at Austin > > 2300 Red River St. Stop D1100 > > Austin TX, 78712-1426 > > (512) 232-8013 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > > Pronouns: she/they > > Head of Archival Processing > University of Minnesota Libraries > Archives and Special Collections > Elmer L. Andersen Library > > > > *I acknowledge that the University of Minnesota is located > on the > traditional, ancestral and contemporary lands of Indigenous people > and > was built with money from slaveholders > . * > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > >> This message is from an external sender. Learn more about why this << > >> matters at https://links.utexas.edu/rtyclf. << > > > > > -- > > Olivia Solis, MSIS (she/her) > > Metadata Coordinator > > Dolph Briscoe Center for American History > > The University of Texas at Austin > > 2300 Red River St. Stop D1100 > > Austin TX, 78712-1426 > > (512) 232-8013 > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > >> This message is from an external sender. Learn more about why this << > >> matters at https://links.utexas.edu/rtyclf. << > -- Olivia Solis, MSIS (she/her) Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5718 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 6317 bytes Desc: not available URL: From japryse at ou.edu Thu Oct 27 10:01:16 2022 From: japryse at ou.edu (Pryse, JA) Date: Thu, 27 Oct 2022 14:01:16 +0000 Subject: [Archivesspace_Users_Group] plug-in questions In-Reply-To: References: Message-ID: Greetings, Long story short: * Our instance of ArchivesSpace is controlled by a disbanded IT group at the University. One disbanded group member has been helping us along the way out of the kindness of their heart. This kind person either left or went to work at another campus. Therefore, we have lost our one person that could actually locate and adjust our AS. * We do not have the bulk importer or any importer plug-in and obviously cannot add it to our instance because it is in the ?upside down?. * We used to be able to roundtrip EAD through Oxygen transforms (aspace-plus-excel-at-yale.xpr and the like). We cannot perform this any longer for some reason. * We have 120,000 items to enter for a grant project coming due very soon. * There is 1 of me and 1 half-time student Can anyone help me figure out how to get around having to have the plug-in (this is just not an option until we gain control over our own instance) OR troubleshoot with me the reason we cannot transform or bulk upload EAD or csv as of last year? Thank you kindly, JA Pryse All Collections Finding Aid: https://arc.ou.edu/ Digital Archives: James R. Jones-Carl Albert Center Digital Archives YouTube: Congressional Archives Carl Albert Twitter: @CarlAlbertCtr Facebook: @CarlAlbertCenter -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt.lawson at uni.edu Thu Oct 27 10:56:02 2022 From: matt.lawson at uni.edu (Matthew Lawson) Date: Thu, 27 Oct 2022 09:56:02 -0500 Subject: [Archivesspace_Users_Group] plug-in questions In-Reply-To: References: Message-ID: I guess I'm not exactly answering the question you are asking, but I think your AS server may be hosted by Amazon (AWS) . If so, who pays the AWS bill? That department should have access. I will be installing a plugin for AS 3.1.1 on a locally hosted linux VM on Monday. I'd be willing to share my experiences. -Matt On Thu, Oct 27, 2022 at 9:01 AM Pryse, JA wrote: > Greetings, > > > > Long story short: > > > > - Our instance of ArchivesSpace is controlled by a disbanded IT group > at the University. One disbanded group member has been helping us along the > way out of the kindness of their heart. This kind person either left or > went to work at another campus. Therefore, we have *lost our one > person that could actually locate and adjust our AS*. > - We do not have the bulk importer or any importer plug-in and > obviously cannot add it to our instance because it is in the ?upside down?. > - We used to be able to roundtrip EAD through Oxygen transforms > (aspace-plus-excel-at-yale.xpr and the like). We cannot perform this any > longer for some reason. > - We have 120,000 items to enter for a grant project coming due very > soon. > - There is 1 of me and 1 half-time student > > > > Can anyone help me figure out how to get around having to have the plug-in > (this is just not an option until we gain control over our own instance) OR > troubleshoot with me the reason we cannot transform or bulk upload EAD or > csv as of last year? > > > > Thank you kindly, > > > > JA Pryse > > All Collections Finding Aid: https://arc.ou.edu/ > > Digital Archives: James R. Jones-Carl Albert Center Digital Archives > > > YouTube: Congressional Archives Carl Albert > > > Twitter: @CarlAlbertCtr > > Facebook: @CarlAlbertCenter > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Matt Lawson Cloud Systems Application Administrator IT :: Network & Infrastructure Services :: Specialized Systems 319-273-3931 ITTC 117 / Cedar Falls, IA 50614 uni.edu / *#1UNI* [image: UNI / University of Northern Iowa] -------------- next part -------------- An HTML attachment was scrubbed... URL: From japryse at ou.edu Thu Oct 27 14:13:44 2022 From: japryse at ou.edu (Pryse, JA) Date: Thu, 27 Oct 2022 18:13:44 +0000 Subject: [Archivesspace_Users_Group] plug-in questions In-Reply-To: References: Message-ID: Matt, well?.that?s been the mystery for a few years. We pay a minimal fee to I.T. for our instance but it resides in an unknown (to us) place. I don?t have access to our AS. I think I.T. will surely provide something (a copy of download the data for us) this to us if we are to get on board with a host. I really just don?t know. That, you see is where I am wanting to mine your brains and experiences for alternatives or ideas. From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Matthew Lawson Sent: Thursday, October 27, 2022 9:56 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] plug-in questions I guess I'm not exactly answering the question you are asking, but I think your AS server may be hosted by Amazon (AWS). If so, who pays the AWS bill? That department should have access. I will be installing a plugin for AS 3.1.1 on a locally hosted linux VM on Monday. I'd be willing to share my experiences. -Matt On Thu, Oct 27, 2022 at 9:01 AM Pryse, JA > wrote: Greetings, Long story short: * Our instance of ArchivesSpace is controlled by a disbanded IT group at the University. One disbanded group member has been helping us along the way out of the kindness of their heart. This kind person either left or went to work at another campus. Therefore, we have lost our one person that could actually locate and adjust our AS. * We do not have the bulk importer or any importer plug-in and obviously cannot add it to our instance because it is in the ?upside down?. * We used to be able to roundtrip EAD through Oxygen transforms (aspace-plus-excel-at-yale.xpr and the like). We cannot perform this any longer for some reason. * We have 120,000 items to enter for a grant project coming due very soon. * There is 1 of me and 1 half-time student Can anyone help me figure out how to get around having to have the plug-in (this is just not an option until we gain control over our own instance) OR troubleshoot with me the reason we cannot transform or bulk upload EAD or csv as of last year? Thank you kindly, JA Pryse All Collections Finding Aid: https://arc.ou.edu/ Digital Archives: James R. Jones-Carl Albert Center Digital Archives YouTube: Congressional Archives Carl Albert Twitter: @CarlAlbertCtr Facebook: @CarlAlbertCenter _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Matt Lawson Cloud Systems Application Administrator IT :: Network & Infrastructure Services :: Specialized Systems 319-273-3931 ITTC 117 / Cedar Falls, IA 50614 uni.edu / #1UNI [UNI / University of Northern Iowa] -------------- next part -------------- An HTML attachment was scrubbed... URL: From kbreneman at ubalt.edu Thu Oct 27 15:03:05 2022 From: kbreneman at ubalt.edu (Kyle Breneman) Date: Thu, 27 Oct 2022 19:03:05 +0000 Subject: [Archivesspace_Users_Group] Anyone noticed a Jetty timeout in their logs? Message-ID: Has anyone noticed a Jetty timeout in their logs? I'm trying to make sense of java.util.concurrent.TimeoutException, and I think it has something to do with Jetty settings. If anyone has experience with this, I would love to talk to you. [cid:image001.jpg at 01D8EA15.3699C6D0] Kyle Breneman Integrated Digital Services Librarian The University of Baltimore kbreneman at ubalt.edu I believe in freedom of thought and freedom of speech. Do you? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 51296 bytes Desc: image001.jpg URL: From Jessica.Crouch at lyrasis.org Mon Oct 31 14:45:46 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 31 Oct 2022 18:45:46 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - October 2022 In-Reply-To: References: Message-ID: [cid:image001.jpg at 01D8A330.1E6801C0] ArchivesSpace Update ? October 2022 Upcoming Schedule at a Glance: November 9: Using Data Import, Export, and Report Functionality in ArchivesSpace Training (full; no longer accepting registrations) November 30: Trainers Corps Office Hour - Spawning functionality in ArchivesSpace December 14: Member Discussion - ArchivesSpace Digital Objects Module Development ArchivesSpace 3.3.1 is now available. This patch release fixes a bug when using default values that was introduced by 3.3.0 and adds some missing labels. People who haven't already upgraded to 3.3.0 should go directly to this release when they do upgrade, and we recommend upgrading to 3.3.1 if you have already upgraded to 3.3.0 and use or plan to use default values for record creation. More information about what?s in the release and the link to download it are at https://github.com/archivesspace/archivesspace/releases/tag/v3.3.1. Information on upgrading to a new version of ArchivesSpace is available at https://archivesspace.github.io/tech-docs/administration/upgrading.html. If you have questions or need any assistance, please let us know. A special thanks to our Registered Service Providers, Atlas Systems for identifying the default values issue and LYRASIS Digital Technology Services for the quick submission of a fix to it. Training Announcement: Using Data Import, Export, and Report Functionality in ArchivesSpace ArchivesSpace will be offering our next community-wide training on November 9, 2022, from 12pm-3pm ET/9am-12pm PT. This training will cover import, export and report functionality in ArchivesSpace. This training is currently full but a recording of the training will be made available to ArchivesSpace members in the Help Center in the days following the training. At the end of this session, participants will: * Understand the data import options available within the ArchivesSpace staff user interface and how to access import templates * Know how to import new data into ArchivesSpace using the staff user interface * Know how to use data import functionality in the staff user interface for legacy data clean-up * Understand the data export options available within the ArchivesSpace staff user interface * Understand how to create custom report templates within ArchivesSpace * Understand how to run out-of-the-box and custom reports within ArchivesSpace This training assumes a basic understanding of archival workflows and metadata formats as well as experience navigating the staff user interface. If you plan to attend this workshop without the required background, we encourage you to review the recorded ArchivesSpace basics training available on our Getting Started webpage. ArchivesSpace Trainers Corps Office Hour on November 30 Join the ArchivesSpace Trainers Corps for their next ?Office Hour? on Wednesday, November 30, at 2pm ET/11am PT. In these office hours, members of the ArchivesSpace Trainers Corps demo a task or tool frequently used by ArchivesSpace users and take questions related to the demo and topic. For this open call, the Trainers Corps will briefly demo spawning functionality, including enhancements beginning with the 3.3 versions of ArchivesSpace. Following the presentation, you will have the opportunity to ask questions about the topic, followed by a general Q&A about spawning in ArchivesSpace. Date: November 30, 2022 Time: 2:00pm ET / 11:00am PT Topic: Spawning Functionality in ArchivesSpace Registration: https://lyrasis.zoom.us/meeting/register/tZMlc-CrrjooHNZ46CeQu55vxUAot1lrs4_p Community discussions like the Trainers Corps office hour are not recorded but notes will be made available on the ArchivesSpace wiki in the days following the session. If you have any questions, feel free to contact us at ArchivesSpaceHome at lyrasis.org. Member Discussion - Future Development of the ArchivesSpace Digital Objects Module Join the ArchivesSpace program team and your fellow ArchivesSpace members on December 14, 2022, at 1pm ET/10am PT for a discussion of future development of the ArchivesSpace Digital Objects Module. Date: December 14, 2022 Time: 1:00pm-2:30pm ET/10:00am-11:30am PT (find your local time) Registration: https://lyrasis.zoom.us/meeting/register/tZEpce-trjkoGdSGvc2uCimrn5zVU0UM-027 In this discussion facilitated by members of the ArchivesSpace program team, members will be able to share their own use cases and goals for the digital objects module. Members are encouraged to review current community-submitted feature requests for the digital objects module on the ArchivesSpace JIRA prior to the discussion. If you are unable to locate a current feature request that represents your use case, you are encouraged to submit a feature request following these instructions. Members are also encouraged to review the digital objects section of the ArchivesSpace user manual in anticipation of this discussion. This discussion is open to ArchivesSpace members only and registration is required. Attendees must register using an email address affiliated with a member organization. This is in recognition of the crucial role that ArchivesSpace members play in directly financially supporting the sustainability and development of the application. Having input in large development projects and discussions like this one is one of the member benefits of ArchivesSpace. This discussion will not be recorded but notes will be made available on the ArchivesSpace wiki in the days following the discussion. If you are interested in ArchivesSpace membership and contributing to the future development of the application, email the ArchivesSpace program team at ArchivesSpaceHome at lyrasis.org. Integrations Survey now OPEN [posted on behalf of the Integrations sub-team of the Technical Advisory Council (TAC)] You are invited to partake in a NEW online survey starting August 24th, in conjunction with the 2022 ArchivesSpace Member Forum. It will remain open until November 30th. Click here to complete the 2022 Integrations Survey. The survey's intended purpose is to gather updated and new information about known and available integrations with ArchivesSpace and provide a centralized listing which will include the intended purpose(s), links to resources and other information, when available. The Integrations sub-team plans to launch this survey on an annual or biennial basis to ensure the information is up to date. Users, administrators, and developers are encouraged to participate. You do not need to be a member institution to complete this survey. If you filled out a previous survey a few years ago, please do not hesitate to participate as your information may have changed and this is a newly designed survey. Data collected will be compiled and made available on the Integrations Confluence pages, which are publicly accessible. Updates to the pages are ongoing and some content may still change. *If you are providing information about an integration, please note you will be asked for links to user and technical documentation (if publicly available), developer sites, and/or contact information. You may want to gather that information before starting this survey. Your participation will help the greater community and is highly anticipated and appreciated. If you have any questions, please do not hesitate to reach out by emailing ArchivesSpaceHome at lyrasis.org with the subject heading, ?2022 Integrations Survey?. Thank you for your consideration of this matter. Integrations, TAC Membership Update We are excited to welcome our newest members to our community! Our new members since September 30 include: * Wake Forest University, (Winston-Salem, NC) As of October 31, we have 465 General members, 15 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. ________________________________ ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA?s Collection Management Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 22525 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 29139 bytes Desc: image002.jpg URL: