From Jessica.Crouch at lyrasis.org Mon Aug 1 09:22:47 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 1 Aug 2022 13:22:47 +0000 Subject: [Archivesspace_Users_Group] Survey Participation Requested: Selecting ArchivesSpace Community-wide Training Topics In-Reply-To: References: Message-ID: Dear ArchivesSpace users, Thank you to those who attended the first training offering in the new ArchivesSpace Community-wide Training program. The ArchivesSpace Trainers Corps is requesting community input to help determine future training topics. A survey for this purpose is available at https://www.surveymonkey.com/r/2P9T83M. Responses to this survey will be used by the Trainers Corps to prioritize offering the top 3 selections over the course of the next year. ArchivesSpace community-wide trainings will be 2-3 hours in length, depending on the topic. These trainings are offered for a fee but ArchivesSpace members receive a substantial discount. Survey responses are due by August 22, 2022. To learn more about ArchivesSpace community-wide training, visit https://archivesspace.org/using-archivesspace/trainings. Best, Jessica Crouch 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: image002.jpg Type: image/jpeg Size: 29147 bytes Desc: image002.jpg URL: From akroeger at unomaha.edu Mon Aug 1 10:08:35 2022 From: akroeger at unomaha.edu (Angela Kroeger) Date: Mon, 1 Aug 2022 14:08:35 +0000 Subject: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH Message-ID: I'm not sure if this is an ArchivesSpace issue or an Alma/Primo issue. I'm starting with ArchivesSpace. We have a hosted ArchivesSpace instance, with one repository set up to expose resource records via OAI-PMH. On the other end, we have an Alma discovery import profile set up to load these records into Primo VE. (The records are only being loaded and displayed in the Primo VE discovery layer; they are not being loaded into the Alma catalog.) This has been running smoothly for many months. Our new problem (or more likely an old problem that we never had the opportunity to notice before) is that resource records that have been unpublished and suppressed in ArchivesSpace are still showing up in Primo VE. I've looked at both the OAI-PMH settings in ArchivesSpace and the discovery import profile in Alma/Primo, and I can't see any setting to toggle inclusion/exclusion of suppressed records. How can I prevent suppressed ArchivesSpace records from being exposed for OAI-PMH harvesting? Or is the problem on the Primo VE side, with it failing to remove suppressed records? Thank you! --Angela Angela Kroeger Metadata Coordinator Archives and Special Collections UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu They | Them | Their [cid:ddf0ccc2-b7f8-49b0-ad79-34a97f5f9999] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-eijzhrdo.png Type: image/png Size: 5582 bytes Desc: Outlook-eijzhrdo.png URL: From snewhouse at sciencehistory.org Mon Aug 1 10:19:21 2022 From: snewhouse at sciencehistory.org (Newhouse, Sarah) Date: Mon, 1 Aug 2022 14:19:21 +0000 Subject: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH In-Reply-To: References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.66c02c9e-ea3d-4fda-899a-d2bf4c937ee1@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.598de6c4-64d5-4c68-880d-a64186540b49@emailsignatures365.codetwo.com> Message-ID: Hi Angela, At my previous job we had a similar problem with Archive-It OAI imports into PrimoVE. We had to go ask ExLibris to remove the records from Primo as this was something we couldn't do ourselves (!). I don't remember the details, as our cataloging librarian handled it, but I think you should start with the assumption that this is a PrimoVE issue. __________________________________ 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 Angela Kroeger Sent: Monday, August 1, 2022 10:09 AM To: ArchivesSpace Users Group Subject: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH I'm not sure if this is an ArchivesSpace issue or an Alma/Primo issue. I'm starting with ArchivesSpace. We have a hosted ArchivesSpace instance, with one repository set up to expose resource records via OAI-PMH. On the other end, we have an Alma discovery import profile set up to load these records into Primo VE. (The records are only being loaded and displayed in the Primo VE discovery layer; they are not being loaded into the Alma catalog.) This has been running smoothly for many months. Our new problem (or more likely an old problem that we never had the opportunity to notice before) is that resource records that have been unpublished and suppressed in ArchivesSpace are still showing up in Primo VE. I've looked at both the OAI-PMH settings in ArchivesSpace and the discovery import profile in Alma/Primo, and I can't see any setting to toggle inclusion/exclusion of suppressed records. How can I prevent suppressed ArchivesSpace records from being exposed for OAI-PMH harvesting? Or is the problem on the Primo VE side, with it failing to remove suppressed records? Thank you! --Angela Angela Kroeger Metadata Coordinator Archives and Special Collections UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu They | Them | Their [cid:image001.png at 01D8A590.295D3E80] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5582 bytes Desc: image001.png URL: From akroeger at unomaha.edu Mon Aug 1 14:14:53 2022 From: akroeger at unomaha.edu (Angela Kroeger) Date: Mon, 1 Aug 2022 18:14:53 +0000 Subject: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH In-Reply-To: References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.66c02c9e-ea3d-4fda-899a-d2bf4c937ee1@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.598de6c4-64d5-4c68-880d-a64186540b49@emailsignatures365.codetwo.com> Message-ID: Thank you for the information, Sarah. Narrowing the issue down to the Primo side is very helpful. I'll ask on the Alma-L list to see if anyone has found a way to handle this themselves, and if not, I'll open a support ticket with Ex Libris. --Angela Angela Kroeger Metadata Coordinator Archives and Special Collections UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu They | Them | Their [cid:5cdf15b9-f16f-4346-bc8a-b6aa898fd1e9] ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Newhouse, Sarah Sent: Monday, August 1, 2022 9:19 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH Non-NU Email ________________________________ Hi Angela, At my previous job we had a similar problem with Archive-It OAI imports into PrimoVE. We had to go ask ExLibris to remove the records from Primo as this was something we couldn?t do ourselves (!). I don?t remember the details, as our cataloging librarian handled it, but I think you should start with the assumption that this is a PrimoVE issue. __________________________________ 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 Angela Kroeger Sent: Monday, August 1, 2022 10:09 AM To: ArchivesSpace Users Group Subject: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH I'm not sure if this is an ArchivesSpace issue or an Alma/Primo issue. I'm starting with ArchivesSpace. We have a hosted ArchivesSpace instance, with one repository set up to expose resource records via OAI-PMH. On the other end, we have an Alma discovery import profile set up to load these records into Primo VE. (The records are only being loaded and displayed in the Primo VE discovery layer; they are not being loaded into the Alma catalog.) This has been running smoothly for many months. Our new problem (or more likely an old problem that we never had the opportunity to notice before) is that resource records that have been unpublished and suppressed in ArchivesSpace are still showing up in Primo VE. I've looked at both the OAI-PMH settings in ArchivesSpace and the discovery import profile in Alma/Primo, and I can't see any setting to toggle inclusion/exclusion of suppressed records. How can I prevent suppressed ArchivesSpace records from being exposed for OAI-PMH harvesting? Or is the problem on the Primo VE side, with it failing to remove suppressed records? Thank you! --Angela Angela Kroeger Metadata Coordinator Archives and Special Collections UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu They | Them | Their [cid:image001.png at 01D8A590.295D3E80] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5582 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-tpwopqie.png Type: image/png Size: 5582 bytes Desc: Outlook-tpwopqie.png URL: From jesse.martinez at bc.edu Mon Aug 1 16:20:41 2022 From: jesse.martinez at bc.edu (Jesse Martinez) Date: Mon, 1 Aug 2022 16:20:41 -0400 Subject: [Archivesspace_Users_Group] ASpace 3.2.0: ArgumentError (wrong number of arguments (given 1, expected 2)): In-Reply-To: <583631e6-5bac-575a-e76c-26e88ff2beaf@gmail.com> References: <3d98bc8d-fd3b-7a36-e9b1-aa9e95a833cf@gmail.com> <583631e6-5bac-575a-e76c-26e88ff2beaf@gmail.com> Message-ID: Hi Mark, By any chance do you have customizations for your ASpace instance? The logs you shared refer to this file: https://github.com/archivesspace/archivesspace/blob/v3.2.0/public/app/models/concerns/tree_nodes.rb but at line 213, which doesn't exist in the core repo. If you do have customizations then you may also need to check the plugins_init.rb file in your plugins directory, since that's the only way to override a model or controller in ASpace. (See for instance our customizations here at BC.) I suspect there's some issue at this line: https://github.com/archivesspace/archivesspace/blob/v3.2.0/public/app/models/concerns/tree_nodes.rb#L21 where the "primary_type" variable isn't being set somewhere. Jesse On Thu, Jul 28, 2022 at 2:01 PM Mark Cyzyk wrote: > > Thanks, Jesse, > > I turned on full Debug output in the error log and booted up ASpace in my > Vagrant box. > > Attached is the log from boot through hitting Refresh (twice) on that > erroring Archival Object. > > Much appreciated, > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins Universitymcyzyk at jhu.edu > > Verba volant, scripta manent. > > On 7/28/22 11:33, Jesse Martinez wrote: > > Hi Mark, > > Could you share more of the error log? That may help indicate where in the > breadcrumb view template file that is getting some incomplete data from the > objects_controller. > > Thanks, > Jesse > > On Thu, Jul 28, 2022 at 11:20 AM Mark Cyzyk wrote: > >> >> Dear Aspace List, >> >> We've found another issue in our recent ASpace upgrade to 3.2.0, and this >> one affects our Prod instance, Dev instance, and my personal Vagrant >> instance: >> >> Drilling down on Archival Objects errors out: >> >> https://aspace.library.jhu.edu/repositories/3/archival_objects/30091 >> >> From log in my Vagrant version: >> I, [2022-07-28T14:23:05.216039 #2200] INFO -- : >> [2a38bc08-bb6a-4c63-bd4f-08524e5f205a] Started GET >> "/repositories/3/archival_objects/30091" for 10.0.2.2 at 2022-07-28 >> 14:23:05 +0000 >> I, [2022-07-28T14:23:05.237131 #2200] INFO -- : >> [2a38bc08-bb6a-4c63-bd4f-08524e5f205a] Processing by ObjectsController#show >> as HTML >> I, [2022-07-28T14:23:05.238808 #2200] INFO -- : >> [2a38bc08-bb6a-4c63-bd4f-08524e5f205a] Parameters: {"repo_slug"=>"3", >> "obj_type"=>"archival_objects", "slug_or_id"=>"30091"} >> D, [2022-07-28T14:23:05.260721 #2200] DEBUG -- : >> [2a38bc08-bb6a-4c63-bd4f-08524e5f205a] POST Search url: >> http://localhost:8089/search/records?publish=true&page_size=10&resolve%5B%5D=repository%3Aid&resolve%5B%5 >> > >> D, [2022-07-28T14:23:05.429279 #2200] DEBUG -- : >> [2a38bc08-bb6a-4c63-bd4f-08524e5f205a] POST Search url: >> http://localhost:8089/search/records?publish=true&page_size=10&uri%5B%5D=%2Frepositories%2F3%2Fresources% >> > >> D, [2022-07-28T14:23:05.483432 #2200] DEBUG -- : >> [2a38bc08-bb6a-4c63-bd4f-08524e5f205a] POST Search url: >> http://localhost:8089/search/records?publish=true&page_size=10&uri%5B%5D=%2Frepositories%2F3%2Fresources% >> > >> I, [2022-07-28T14:23:05.568721 #2200] INFO -- : >> [2a38bc08-bb6a-4c63-bd4f-08524e5f205a] Completed 500 Internal Server Error >> in 329ms >> F, [2022-07-28T14:23:05.574794 #2200] FATAL -- : >> [2a38bc08-bb6a-4c63-bd4f-08524e5f205a] >> F, [2022-07-28T14:23:05.575216 #2200] FATAL -- : >> [2a38bc08-bb6a-4c63-bd4f-08524e5f205a] ArgumentError (wrong number of >> arguments (given 1, expected 2)): >> F, [2022-07-28T14:23:05.575577 #2200] FATAL -- : >> [2a38bc08-bb6a-4c63-bd4f-08524e5f205a] >> F, [2022-07-28T14:23:05.575867 #2200] FATAL -- : >> [2a38bc08-bb6a-4c63-bd4f-08524e5f205a] >> app/models/concerns/tree_nodes.rb:213:in `breadcrumb_identifier' >> [2a38bc08-bb6a-4c63-bd4f-08524e5f205a] >> app/controllers/objects_controller.rb:103:in `show' >> >> >> Not sure what to do. >> >> Looks like this is an exception being caught by Ruby: >> >> https://ruby-doc.org/core-2.5.3/ArgumentError.html >> >> >> Not finding anything in our User Group list archive on this. >> >> Advice appreciated! >> >> Mark >> >> -- >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> Mark Cyzyk, M.A., M.L.S. >> Library Applications Group >> The Sheridan Libraries >> The Johns Hopkins Universitymcyzyk at jhu.edu >> >> Verba volant, scripta manent. >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > Jesse Martinez > Senior Library Applications Developer > O'Neill Library, Boston College > jesse.martinez at bc.edu > 617-552-2509 > he/him/his > > > -- Jesse Martinez Senior Library Applications Developer O'Neill Library, Boston College jesse.martinez at bc.edu 617-552-2509 he/him/his -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Tue Aug 2 06:42:51 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Tue, 2 Aug 2022 11:42:51 +0100 Subject: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH In-Reply-To: References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.66c02c9e-ea3d-4fda-899a-d2bf4c937ee1@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.598de6c4-64d5-4c68-880d-a64186540b49@emailsignatures365.codetwo.com> Message-ID: From my experience with Primo in a previous job, despite its many flaws, it is unlikely to be the cause here. There is an open issue with ArchivesSpace which may be relevant: https://archivesspace.atlassian.net/browse/ANW-1301 Especially the comment I've just added. I have no experience with Archive-It, but it declares only "transient" (i.e. partial or inconsistent) support for deletions: https://archive-it.org/oai?verb=Identify Whereas ArchivesSpace declares "persistent" (i.e. full) support: https://test.archivesspace.org/oai?verb=Identify As suppressing/unpublishing records is distinct from deletion, technically it is correct. But it is probably contrary to your expectations, hence the solution (delete from Primo or get Ex Libris to do it if you cannot) may be the same. Andrew. On 01/08/2022 19:14, Angela Kroeger wrote: > Thank you for the information, Sarah. Narrowing the issue down to the > Primo side is very helpful. > > I'll ask on the Alma-L list to see if anyone has found a way to handle > this themselves, and if not, I'll open a support ticket with Ex Libris. > > --Angela > > *Angela Kroeger* > Metadata Coordinator > Archives and Special Collections > UNO Libraries | Criss Library 107 > University of Nebraska at Omaha | unomaha.edu > > 402.554.4159 > akroeger at unomaha.edu > They | Them | Their > > > ------------------------------------------------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Newhouse, Sarah > *Sent:* Monday, August 1, 2022 9:19 AM > *To:* Archivesspace Users Group > > *Subject:* Re: [Archivesspace_Users_Group] Suppressed ArchivesSpace > records in OAI-PMH > Non-NU Email > ------------------------------------------------------------------------ > > Hi Angela, > > At my previous job we had a similar problem with Archive-It OAI > imports into PrimoVE. We had to go ask ExLibris to remove the records > from Primo as this was something we couldn?t do ourselves (!). I don?t > remember the details, as our cataloging librarian handled it, but I > think you should start with the assumption that this is a PrimoVE issue. > > __________________________________ > > 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 *Angela Kroeger > *Sent:* Monday, August 1, 2022 10:09 AM > *To:* ArchivesSpace Users Group > > *Subject:* [Archivesspace_Users_Group] Suppressed ArchivesSpace > records in OAI-PMH > > I'm not sure if this is an ArchivesSpace issue or an Alma/Primo issue. > I'm starting with ArchivesSpace. > > We have a hosted ArchivesSpace instance, with one repository set up to > expose resource records via OAI-PMH. On the other end, we have an Alma > discovery import profile set up to load these records into Primo VE. > (The records are only being loaded and displayed in the Primo VE > discovery layer; they are not being loaded into the Alma catalog.) > This has been running smoothly for many months. > > Our new problem (or more likely an old problem that we never had the > opportunity to notice before) is that resource records that have been > unpublished and suppressed in ArchivesSpace are still showing up in > Primo VE. > > I've looked at both the OAI-PMH settings in ArchivesSpace and the > discovery import profile in Alma/Primo, and I can't see any setting to > toggle inclusion/exclusion of suppressed records. > > How can I prevent suppressed ArchivesSpace records from being exposed > for OAI-PMH harvesting? > > Or is the problem on the Primo VE side, with it failing to remove > suppressed records? > > Thank you! > > --Angela > > *Angela Kroeger* > > Metadata Coordinator > Archives and Special Collections > UNO Libraries | Criss Library 107 > University of Nebraska at Omaha | unomaha.edu > > 402.554.4159 > akroeger at unomaha.edu > They | Them | Their > > > _______________________________________________ > 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: Outlook-tpwopqie.png Type: image/png Size: 5582 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5582 bytes Desc: not available URL: From Boze.1 at nd.edu Tue Aug 2 10:27:01 2022 From: Boze.1 at nd.edu (Andy Boze) Date: Tue, 2 Aug 2022 10:27:01 -0400 Subject: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH In-Reply-To: References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.66c02c9e-ea3d-4fda-899a-d2bf4c937ee1@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.598de6c4-64d5-4c68-880d-a64186540b49@emailsignatures365.codetwo.com> Message-ID: <1201add2-68ea-8623-e304-b6e9d5177b0d@nd.edu> We treated this as an ArchivesSpace bug. According tp openarchives.org, "If a record is no longer available then it is said to be deleted." ArchivesSpace only indicates that a record is deleted when it is actually deleted from the database, not when it becomes suppressed (contrary to what we believe it should). We use Primo BackOffice, so I'm not familiar with VE. For our harvest, we do a regular harvest twice daily, then once a week we run a Cleanup (Delete DS and ReLoad) pipe, which effectively removes records that are no longer in the ASpace OAI data stream, even without having an explicit "delete" record. Andy On 8/2/2022 6:42 AM, Andrew Morrison wrote: > From my experience with Primo in a previous job, despite its many > flaws, it is unlikely to be the cause here. > > > There is an open issue with ArchivesSpace which may be relevant: > > > https://archivesspace.atlassian.net/browse/ANW-1301 > > > Especially the comment I've just added. > > > I have no experience with Archive-It, but it declares only "transient" > (i.e. partial or inconsistent) support for deletions: > > > https://archive-it.org/oai?verb=Identify > > > Whereas ArchivesSpace declares "persistent" (i.e. full) support: > > > https://test.archivesspace.org/oai?verb=Identify > > > As suppressing/unpublishing records is distinct from deletion, > technically it is correct. But it is probably contrary to your > expectations, hence the solution (delete from Primo or get Ex Libris to > do it if you cannot) may be the same. > > > Andrew. > > > > > On 01/08/2022 19:14, Angela Kroeger wrote: >> Thank you for the information, Sarah. Narrowing the issue down to the >> Primo side is very helpful. >> >> I'll ask on the Alma-L list to see if anyone has found a way to handle >> this themselves, and if not, I'll open a support ticket with Ex Libris. >> >> --Angela >> >> *Angela Kroeger* >> Metadata Coordinator >> Archives and Special Collections >> UNO Libraries | Criss Library 107 >> University of Nebraska at Omaha | unomaha.edu >> >> 402.554.4159 >> akroeger at unomaha.edu >> They | Them | Their >> >> >> ------------------------------------------------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org >> on behalf of >> Newhouse, Sarah >> *Sent:* Monday, August 1, 2022 9:19 AM >> *To:* Archivesspace Users Group >> >> *Subject:* Re: [Archivesspace_Users_Group] Suppressed ArchivesSpace >> records in OAI-PMH >> Non-NU Email >> ------------------------------------------------------------------------ >> >> Hi Angela, >> >> At my previous job we had a similar problem with Archive-It OAI >> imports into PrimoVE. We had to go ask ExLibris to remove the records >> from Primo as this was something we couldn?t do ourselves (!). I don?t >> remember the details, as our cataloging librarian handled it, but I >> think you should start with the assumption that this is a PrimoVE issue. >> >> __________________________________ >> >> 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 *Angela Kroeger >> *Sent:* Monday, August 1, 2022 10:09 AM >> *To:* ArchivesSpace Users Group >> >> *Subject:* [Archivesspace_Users_Group] Suppressed ArchivesSpace >> records in OAI-PMH >> >> I'm not sure if this is an ArchivesSpace issue or an Alma/Primo issue. >> I'm starting with ArchivesSpace. >> >> We have a hosted ArchivesSpace instance, with one repository set up to >> expose resource records via OAI-PMH. On the other end, we have an Alma >> discovery import profile set up to load these records into Primo VE. >> (The records are only being loaded and displayed in the Primo VE >> discovery layer; they are not being loaded into the Alma catalog.) >> This has been running smoothly for many months. >> >> Our new problem (or more likely an old problem that we never had the >> opportunity to notice before) is that resource records that have been >> unpublished and suppressed in ArchivesSpace are still showing up in >> Primo VE. >> >> I've looked at both the OAI-PMH settings in ArchivesSpace and the >> discovery import profile in Alma/Primo, and I can't see any setting to >> toggle inclusion/exclusion of suppressed records. >> >> How can I prevent suppressed ArchivesSpace records from being exposed >> for OAI-PMH harvesting? >> >> Or is the problem on the Primo VE side, with it failing to remove >> suppressed records? >> >> Thank you! >> >> --Angela >> >> *Angela Kroeger* >> >> Metadata Coordinator >> Archives and Special Collections >> UNO Libraries | Criss Library 107 >> University of Nebraska at Omaha | unomaha.edu >> >> 402.554.4159 >> akroeger at unomaha.edu >> They | Them | Their >> >> >> _______________________________________________ >> 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 > -- Andy Boze, Associate Librarian University of Notre Dame 271H Hesburgh Library (574) 631-8708 From hanstra at nd.edu Tue Aug 2 13:58:50 2022 From: hanstra at nd.edu (Tom Hanstra) Date: Tue, 2 Aug 2022 13:58:50 -0400 Subject: [Archivesspace_Users_Group] Docker build Message-ID: I would like to look at running ArchivesSpace within a Docker image. I see at least a couple of pre-built containers available in DockerHub. Is the ArchivesSpace version the preferred version or are others better? And is there good documentation somewhere on how to run AS within a docker container, including proper setup instructions? Thanks for any help you can provide to get me started, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Tue Aug 2 16:17:01 2022 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Tue, 2 Aug 2022 20:17:01 +0000 Subject: [Archivesspace_Users_Group] Docker build In-Reply-To: References: Message-ID: Hey Tom Here's a repo describing the setup we use: https://github.com/dartmouth-dltg/aspace-docker This is pre? AS v3.2.0, so no external solr - we're still running AS v3.1.1 in prooduction. jds ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tom Hanstra Sent: Tuesday, August 2, 2022 1:58 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Docker build I would like to look at running ArchivesSpace within a Docker image. I see at least a couple of pre-built containers available in DockerHub. Is the ArchivesSpace version the preferred version or are others better? And is there good documentation somewhere on how to run AS within a docker container, including proper setup instructions? Thanks for any help you can provide to get me started, Tom -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://ci3.googleusercontent.com/mail-sig/AIorK4wQjvBdM9TFi5bR5RBsq_1dY3HTxh-Kg_4W690bwTCSKeVGyazMoj0wdmkNgJ0kfjeRnparhiw] -------------- next part -------------- An HTML attachment was scrubbed... URL: From schanzme at msu.edu Tue Aug 2 21:13:42 2022 From: schanzme at msu.edu (Schanz, Megan) Date: Wed, 3 Aug 2022 01:13:42 +0000 Subject: [Archivesspace_Users_Group] Docker build In-Reply-To: References: Message-ID: Hi Tom, This is our setup: https://gitlab.msu.edu/msu-libraries/public/archivesspace-docker that uses separate Docker containers for ArchivesSpace and Solr, running v3.1.1. - Megan _____________________________________ Megan Schanz Application Developer & Systems Administrator Michigan State University Libraries ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Joshua D. Shaw Sent: Tuesday, August 2, 2022 4:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Docker build Hey Tom Here's a repo describing the setup we use: https://github.com/dartmouth-dltg/aspace-docker This is pre? AS v3.2.0, so no external solr - we're still running AS v3.1.1 in prooduction. jds ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tom Hanstra Sent: Tuesday, August 2, 2022 1:58 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Docker build I would like to look at running ArchivesSpace within a Docker image. I see at least a couple of pre-built containers available in DockerHub. Is the ArchivesSpace version the preferred version or are others better? And is there good documentation somewhere on how to run AS within a docker container, including proper setup instructions? Thanks for any help you can provide to get me started, Tom -- Tom Hanstra Sr. Systems Administrator hanstra at nd.edu [https://ci3.googleusercontent.com/mail-sig/AIorK4wQjvBdM9TFi5bR5RBsq_1dY3HTxh-Kg_4W690bwTCSKeVGyazMoj0wdmkNgJ0kfjeRnparhiw] -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Wed Aug 3 09:48:08 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Wed, 3 Aug 2022 13:48:08 +0000 Subject: [Archivesspace_Users_Group] Register now for the ArchivesSpace Member Forum In-Reply-To: References: Message-ID: [Graphical user interface Description automatically generated with medium confidence] Dear ArchivesSpace members, Registration is now open for the 8th Annual ArchivesSpace Member Forum! Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. We will be holding a half-day, in-person member meeting on August 24, 2022, in the Commonwealth Room on the third floor of the Sheraton Boston Hotel. In addition to this in-person meeting, we will also hold two virtual workshops on August 30-31, 2022. These free events are a chance for ArchivesSpace members to come together to highlight the work they are doing in ArchivesSpace, show off new plugins or tools they?ve developed, and attend instructional sessions and discussions on a variety of topics. As with our previous Annual Member Forums, it is being held in conjunction with the Society of American Archivists annual meeting, but it is not part of SAA and does not require registration for the SAA Annual Meeting. In-person meeting details: When: August 24, 2022 from 9:00am-12:30pm ET Where: Commonwealth Room, Third Floor, Sheraton Boston Hotel Virtual workshops details: When: August 30-31st, 2022 Where: Online; via Zoom Who Can Attend: The ArchivesSpace Member Forum is open to individuals from ArchivesSpace member institutions only. To register, you must use an institutional email address associated with an ArchivesSpace member institution. Registrations using personal email addresses and addresses associated with non-member institutions will not be accepted. This means that events with limited capacity may fill before you are able to correct your registration. Online registration: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/3128066258/ArchivesSpace+Member+Forum+2022 Registrations for each day are separate and you must register individually for all days/events you are interested in attending. Registration information is linked above each event on the agenda. All in-person sessions and virtual workshops will be recorded. Propose a session or topic: Everyone attending the in-person meeting is strongly encouraged to submit a proposal. Brief 15-20 minute sessions showing off your organization?s implementation of ArchivesSpace, a tool or plug-in you?ve developed, a project your organization has undertaken or a new workflow you?ve developed are highly encouraged. There is a short Google form for proposals available at https://forms.gle/V7gtps3E9vnvdLXX7. Proposals will be reviewed on a rolling basis. The last day that proposals will be accepted is August 8, 2022, and all notifications will be made by August 10, 2022. Please feel free to contact ArchivesSpace Community Engagement Coordinator Jessica Crouch (jessica.crouch at lyrasis.org) with questions. We look forward to seeing you in-person or virtually. Best, Jessica Crouch Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 288899 bytes Desc: image001.jpg URL: From akroeger at unomaha.edu Wed Aug 3 11:51:58 2022 From: akroeger at unomaha.edu (Angela Kroeger) Date: Wed, 3 Aug 2022 15:51:58 +0000 Subject: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH In-Reply-To: <1201add2-68ea-8623-e304-b6e9d5177b0d@nd.edu> References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.66c02c9e-ea3d-4fda-899a-d2bf4c937ee1@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.598de6c4-64d5-4c68-880d-a64186540b49@emailsignatures365.codetwo.com> <1201add2-68ea-8623-e304-b6e9d5177b0d@nd.edu> Message-ID: Thank you, Andrew and Andy, for the additional information about how ArchivesSpace presents suppressed and deleted records. It seems that part of the issue is on the ArchivesSpace side and part of it is on the Primo VE side. Based on advice I got on the Alma-L list, I deleted all ArchivesSpace records from Primo VE, then reloaded from scratch. The new load didn't include the suppressed records, so that resolved that particular issue. (This is a manual process that I will need to do periodically.) However, the process of discovering this solution led me to a much bigger problem. A colleague at another institution in my consortium was told they couldn't load their ArchivesSpace records into Primo VE because they don't have their own ArchivesSpace instance. I went into our shared ArchivesSpace instance and changed repositories to see this other institution's OAI-PMH settings, and was surprised/horrified to see that the settings I had believed were specific to our repository are in fact global settings. So the repository set I created for my institution blocks other members of the consortium from loading their ArchivesSpace repositories into Primo VE, and if anyone changes the repository set to work with their records, it will break my institution's loads. I'm afraid the answer will be no, but I'll ask anyway: Is there any way to create more than one repository set in the ArchivesSpace OAI-PMH settings? Looking at it, all I can see is "Update OAI-PMH Settings" which would wipe out the previous set. Why is "repository set" a global setting and not down in the "per repository" settings? Thank you! --Angela Angela Kroeger Metadata Coordinator Archives and Special Collections UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu They | Them | Their [cid:460d11c6-89e8-4a7a-a070-65b043b8d1cb] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-3mejvx3t.png Type: image/png Size: 5582 bytes Desc: Outlook-3mejvx3t.png URL: From brian.duckett at nih.gov Wed Aug 3 11:54:53 2022 From: brian.duckett at nih.gov (Duckett, Brian (NIH/NLM) [C]) Date: Wed, 3 Aug 2022 15:54:53 +0000 Subject: [Archivesspace_Users_Group] Guidance for Human Readable URLs In-Reply-To: References: Message-ID: Hello Christine, Thank You again for the wiki link. After some investigation we have narrowed the issue we are experiencing: * Slugs are null In the database even though the is_slug_auto column in the database is true (set to 1) There are references to a `background job` in the wiki documentation. I am hoping you can clarify when and how the background job is run, as well as if this is the process that will correct the issue noted above. We have done some troubleshooting. * When editing the resource, simple pressing save will populate the slug * Dropping and Re-Importing the entire database corrects the issue also Thank You, Brian Duckett Cloud Developer, AWS Developer Associate, AWS DevOps Professional (Contractor, GDIT) National Library of Medicine, OCCS/OD From: Duckett, Brian (NIH/NLM) [C] Sent: Friday, July 29, 2022 3:46 PM To: Archivesspace Users Group Cc: Kalyanasundaram, Sriram (NIH/NLM) [C]; Whitaker, John (NIH/NLM) [C]; Liu, Steve (NIH/NLM) [C] Subject: RE: Guidance for Human Readable URLs Hello Christine, Thank You. The information in the wiki is exactly what we are looking for. Thank You, Brian Duckett Cloud Developer, AWS Developer Associate, AWS DevOps Professional (Contractor, GDIT) National Library of Medicine, OCCS/OD From: Christine Di Bella Sent: Thursday, July 28, 2022 11:52 AM To: Archivesspace Users Group Cc: Kalyanasundaram, Sriram (NIH/NLM) [C]; Whitaker, John (NIH/NLM) [C]; Liu, Steve (NIH/NLM) [C] Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] Guidance for Human Readable URLs Hello Brian, Have you looked at the user manual section on this feature: https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/890208314/Human-Readable+URLs? If not, that would be a good place to start for an overview. Hopefully some folks on here can give more advice from the point of view of actual implementations. 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 Duckett, Brian (NIH/NLM) [C] Sent: Tuesday, July 26, 2022 2:03 PM To: archivesspace_users_group at lyralists.lyrasis.org Cc: Liu, Steve (NIH/NLM) [C] ; Whitaker, John (NIH/NLM) [C] ; Kalyanasundaram, Sriram (NIH/NLM) [C] Subject: [Archivesspace_Users_Group] Guidance for Human Readable URLs Hello, We are requesting guidance on how to implement human readable URLs in the ArchivesSpace application. Our production instance supports this to an extent. For example, the following listed URL is a ?human readable? URL for the standard ArchivesSpace URL https://archivesspace.nlm.nih.gov/repositories/4/resources/968 * https://archivesspace.nlm.nih.gov/repositories/ammp/resources/__101576736 We would like to implement this naming standard across all public facing links. Guidance on integrating this implementation for search would also be highly appreciated. Thank You, Brian 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: 72335A8664E84E26BA5F2B2731A5F491.jpg Type: image/jpeg Size: 8792 bytes Desc: 72335A8664E84E26BA5F2B2731A5F491.jpg URL: From christine.dibella at lyrasis.org Wed Aug 3 12:36:24 2022 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 3 Aug 2022 16:36:24 +0000 Subject: [Archivesspace_Users_Group] Guidance for Human Readable URLs In-Reply-To: References: Message-ID: Hello Brian, You are correct that, even when human readable URLs are turned on, the slugs field is only populated when a new record is created or when an existing record is opened and updated. The Generate Slugs in Bulk background job is to populate the slugs field for all of the relevant records in the database. Once you enable human readable URLs in your configuration settings, that background job will appear in the list of background jobs for people with sufficient permissions. [cid:image002.png at 01D8A735.41BB2A40] [cid:image003.png at 01D8A735.A36B1980] It uses your configuration settings for generating individual slugs. From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Duckett, Brian (NIH/NLM) [C] Sent: Wednesday, August 3, 2022 11:55 AM To: Archivesspace Users Group Cc: Liu, Steve (NIH/NLM) [C] ; Whitaker, John (NIH/NLM) [C] ; Kalyanasundaram, Sriram (NIH/NLM) [C] Subject: Re: [Archivesspace_Users_Group] Guidance for Human Readable URLs Hello Christine, Thank You again for the wiki link. After some investigation we have narrowed the issue we are experiencing: * Slugs are null In the database even though the is_slug_auto column in the database is true (set to 1) There are references to a `background job` in the wiki documentation. I am hoping you can clarify when and how the background job is run, as well as if this is the process that will correct the issue noted above. We have done some troubleshooting. * When editing the resource, simple pressing save will populate the slug * Dropping and Re-Importing the entire database corrects the issue also Thank You, Brian Duckett Cloud Developer, AWS Developer Associate, AWS DevOps Professional (Contractor, GDIT) National Library of Medicine, OCCS/OD From: Duckett, Brian (NIH/NLM) [C] Sent: Friday, July 29, 2022 3:46 PM To: Archivesspace Users Group Cc: Kalyanasundaram, Sriram (NIH/NLM) [C]; Whitaker, John (NIH/NLM) [C]; Liu, Steve (NIH/NLM) [C] Subject: RE: Guidance for Human Readable URLs Hello Christine, Thank You. The information in the wiki is exactly what we are looking for. Thank You, Brian Duckett Cloud Developer, AWS Developer Associate, AWS DevOps Professional (Contractor, GDIT) National Library of Medicine, OCCS/OD From: Christine Di Bella Sent: Thursday, July 28, 2022 11:52 AM To: Archivesspace Users Group Cc: Kalyanasundaram, Sriram (NIH/NLM) [C]; Whitaker, John (NIH/NLM) [C]; Liu, Steve (NIH/NLM) [C] Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] Guidance for Human Readable URLs Hello Brian, Have you looked at the user manual section on this feature: https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/890208314/Human-Readable+URLs? If not, that would be a good place to start for an overview. Hopefully some folks on here can give more advice from the point of view of actual implementations. 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 Duckett, Brian (NIH/NLM) [C] Sent: Tuesday, July 26, 2022 2:03 PM To: archivesspace_users_group at lyralists.lyrasis.org Cc: Liu, Steve (NIH/NLM) [C] >; Whitaker, John (NIH/NLM) [C] >; Kalyanasundaram, Sriram (NIH/NLM) [C] > Subject: [Archivesspace_Users_Group] Guidance for Human Readable URLs Hello, We are requesting guidance on how to implement human readable URLs in the ArchivesSpace application. Our production instance supports this to an extent. For example, the following listed URL is a "human readable" URL for the standard ArchivesSpace URL https://archivesspace.nlm.nih.gov/repositories/4/resources/968 * https://archivesspace.nlm.nih.gov/repositories/ammp/resources/__101576736 We would like to implement this naming standard across all public facing links. Guidance on integrating this implementation for search would also be highly appreciated. Thank You, Brian 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 8792 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 100441 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 271032 bytes Desc: image003.png URL: From andrew.morrison at bodleian.ox.ac.uk Thu Aug 4 07:29:06 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Thu, 4 Aug 2022 12:29:06 +0100 Subject: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH In-Reply-To: References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.66c02c9e-ea3d-4fda-899a-d2bf4c937ee1@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.598de6c4-64d5-4c68-880d-a64186540b49@emailsignatures365.codetwo.com> <1201add2-68ea-8623-e304-b6e9d5177b0d@nd.edu> Message-ID: There is an open issue for this: https://archivesspace.atlassian.net/browse/ANW-1339 It would probably be helpful to detail your use-case there (e.g. do you have different rulesets in Primo for each repository in ArchivesSpace?) Andrew. On 03/08/2022 16:51, Angela Kroeger wrote: > Thank you, Andrew and Andy, for the additional information about how > ArchivesSpace presents suppressed and deleted records. It seems that > part of the issue is on the ArchivesSpace side and part of it is on > the Primo VE side. > > Based on advice I got on the Alma-L list, I deleted all ArchivesSpace > records from Primo VE, then reloaded from scratch. The new load didn't > include the suppressed records, so that resolved that particular > issue. (This is a manual process that I will need to do periodically.) > > However, the process of discovering this solution led me to a much > bigger problem. > > A colleague at another institution in my consortium was told they > couldn't load their ArchivesSpace records into Primo VE because they > don't have their own ArchivesSpace instance. I went into our shared > ArchivesSpace instance and changed repositories to see this other > institution's OAI-PMH settings, and was surprised/horrified to see > that the settings I had believed were specific to our repository are > in fact global settings. So the repository set I created for my > institution blocks other members of the consortium from loading their > ArchivesSpace repositories into Primo VE, and if anyone changes the > repository set to work with their records, it will break my > institution's loads. > > I'm afraid the answer will be no, but I'll ask anyway: > > Is there any way to create more than one repository set in the > ArchivesSpace OAI-PMH settings? Looking at it, all I can see is > "Update OAI-PMH Settings" which would wipe out the previous set. > > Why is "repository set" a global setting and not down in the "per > repository" settings? > > Thank you! > > --Angela > > *Angela Kroeger* > Metadata Coordinator > Archives and Special Collections > UNO Libraries | Criss Library 107 > University of Nebraska at Omaha | unomaha.edu > > 402.554.4159 > akroeger at unomaha.edu > They | Them | Their > > > _______________________________________________ > 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: Outlook-3mejvx3t.png Type: image/png Size: 5582 bytes Desc: not available URL: From akroeger at unomaha.edu Thu Aug 4 09:17:22 2022 From: akroeger at unomaha.edu (Angela Kroeger) Date: Thu, 4 Aug 2022 13:17:22 +0000 Subject: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH In-Reply-To: References: <0bc9ca69-de9a-4006-bb1e-b786269e2036.5bc9e4a4-201a-4113-8500-06887445b2b4.66c02c9e-ea3d-4fda-899a-d2bf4c937ee1@emailsignatures365.codetwo.com> <0bc9ca69-de9a-4006-bb1e-b786269e2036.1fe061b8-c04b-4022-ab6c-ea3cb89cd359.598de6c4-64d5-4c68-880d-a64186540b49@emailsignatures365.codetwo.com> <1201add2-68ea-8623-e304-b6e9d5177b0d@nd.edu> Message-ID: Andrew asked, "do you have different rulesets in Primo for each repository in ArchivesSpace?" No. Is that actually possible? As your open ticket with ArchivesSpace notes, you can only create a single OAI-PMH set in ArchivesSpace, so we can't have separate sets for reach repository. If we could, then we probably would have separate import profiles for each repository. Is there another way in Primo VE to latch onto a single repository from an ArchivesSpace instance, without using the repository set from ArchivesSpace? --Angela Angela Kroeger Metadata Coordinator Archives and Special Collections UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu They | Them | Their [cid:b9f96028-fe49-46b9-bb8b-6ddb1d02f2ab] ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Andrew Morrison Sent: Thursday, August 4, 2022 6:29 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Suppressed ArchivesSpace records in OAI-PMH Non-NU Email ________________________________ There is an open issue for this: https://archivesspace.atlassian.net/browse/ANW-1339 It would probably be helpful to detail your use-case there (e.g. do you have different rulesets in Primo for each repository in ArchivesSpace?) Andrew. On 03/08/2022 16:51, Angela Kroeger wrote: Thank you, Andrew and Andy, for the additional information about how ArchivesSpace presents suppressed and deleted records. It seems that part of the issue is on the ArchivesSpace side and part of it is on the Primo VE side. Based on advice I got on the Alma-L list, I deleted all ArchivesSpace records from Primo VE, then reloaded from scratch. The new load didn't include the suppressed records, so that resolved that particular issue. (This is a manual process that I will need to do periodically.) However, the process of discovering this solution led me to a much bigger problem. A colleague at another institution in my consortium was told they couldn't load their ArchivesSpace records into Primo VE because they don't have their own ArchivesSpace instance. I went into our shared ArchivesSpace instance and changed repositories to see this other institution's OAI-PMH settings, and was surprised/horrified to see that the settings I had believed were specific to our repository are in fact global settings. So the repository set I created for my institution blocks other members of the consortium from loading their ArchivesSpace repositories into Primo VE, and if anyone changes the repository set to work with their records, it will break my institution's loads. I'm afraid the answer will be no, but I'll ask anyway: Is there any way to create more than one repository set in the ArchivesSpace OAI-PMH settings? Looking at it, all I can see is "Update OAI-PMH Settings" which would wipe out the previous set. Why is "repository set" a global setting and not down in the "per repository" settings? Thank you! --Angela Angela Kroeger Metadata Coordinator Archives and Special Collections UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu They | Them | Their [cid:part1.JqRw517S.hvsVdJ7d at bodleian.ox.ac.uk] _______________________________________________ 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: Outlook-3mejvx3t.png Type: image/png Size: 5582 bytes Desc: Outlook-3mejvx3t.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-erv2qa2s.png Type: image/png Size: 5582 bytes Desc: Outlook-erv2qa2s.png URL: From hanstra at nd.edu Thu Aug 4 16:57:47 2022 From: hanstra at nd.edu (Tom Hanstra) Date: Thu, 4 Aug 2022 16:57:47 -0400 Subject: [Archivesspace_Users_Group] Docker build In-Reply-To: References: Message-ID: Thanks, Megan and Joshua. I do see that the ArchivesSpace repository includes some Docker build files so I was hoping to look at that first. Unfortunately, what I cannot seem to track down is documentation on how that exactly works. Has anyone used the images and compose files in the repository who might be able to help me better understand what is there and how it can be used? In general, are there sites using Docker deployments in production? I'm surprised by the lack of response on this. Tom On Tue, Aug 2, 2022 at 9:13 PM Schanz, Megan wrote: > Hi Tom, > > This is our setup: > https://gitlab.msu.edu/msu-libraries/public/archivesspace-docker that > uses separate Docker containers for ArchivesSpace and Solr, running v3.1.1. > > - Megan > > > > _____________________________________ > > Megan Schanz > Application Developer & Systems Administrator > Michigan State University Libraries > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Joshua D. Shaw > *Sent:* Tuesday, August 2, 2022 4:17 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Docker build > > Hey Tom > > Here's a repo describing the setup we use: > https://github.com/dartmouth-dltg/aspace-docker > > > This is *pre*? AS v3.2.0, so no external solr - we're still running AS > v3.1.1 in prooduction. > > jds > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Tom > Hanstra > *Sent:* Tuesday, August 2, 2022 1:58 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Docker build > > I would like to look at running ArchivesSpace within a Docker image. I see > at least a couple of pre-built containers available in DockerHub. Is the > ArchivesSpace version the preferred version or are others better? And is > there good documentation somewhere on how to run AS within a docker > container, including proper setup instructions? > > Thanks for any help you can provide to get me started, > Tom > > -- > *Tom Hanstra* > *Sr. Systems Administrator* > hanstra at nd.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- *Tom Hanstra* *Sr. Systems Administrator* hanstra at nd.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Aug 8 10:04:37 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 8 Aug 2022 14:04:37 +0000 Subject: [Archivesspace_Users_Group] Deadline extended - Submit a session proposal for the ArchivesSpace in-person annual meeting, August 24, 2022 In-Reply-To: References: Message-ID: Dear ArchivesSpace members, We are thrilled to be holding a portion of our 8th Annual ArchivesSpace Member Forum in-person at the Sheraton Hotel Boston on August 24, 2022 and registration is now open for both in-person and virtual elements of the forum. However, we currently do not have a sufficient number of presentations to move forward with developing the schedule for the in-person meeting. We plan to hold the meeting in some form no matter what but the success of our forums is dependent on the participation of members and their willingness to share their knowledge and experience with others in the community. We?ve been fortunate to have a core of very active community members do this in past years, but with fewer people attending this year at this point we need others to step up. To that end, everyone attending the in-person meeting is strongly encouraged to consider submitting a proposal. Brief 15-20 minute sessions showing off your organization?s implementation of ArchivesSpace, a tool or plug-in you?ve developed, a project your organization has undertaken or a new workflow you?ve developed are highly encouraged. There is a short Google form for proposals available at https://forms.gle/V7gtps3E9vnvdLXX7. Proposals will be reviewed on a rolling basis and will continue to be accepted until August 12th. Please feel free to contact ArchivesSpace Community Engagement Coordinator Jessica Crouch (jessica.crouch at lyrasis.org) with questions. We look forward to seeing you in-person or virtually. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From shand at ap.org Mon Aug 8 15:24:28 2022 From: shand at ap.org (Hand, Sarit) Date: Mon, 8 Aug 2022 19:24:28 +0000 Subject: [Archivesspace_Users_Group] The Integrations sub-team of the ArchivesSpace Technical Advisory Council (TAC) announces launch of NEW survey! Message-ID: Dear ArchivesSpace Users, Administrators and Developers. 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. 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. A link to the survey will be sent out on August 24th to this and other groups where this announcement has been posted. 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 subject heading, "2022 Integrations Survey". Thank you for your consideration of this matter. Integrations, TAC Sarit Hand Digital Archivist AP Corporate Archives TAC Member Integrations sub-team leader The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1500 and delete this email. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gboggio at mitre.org Tue Aug 9 14:21:48 2022 From: gboggio at mitre.org (Jerry Boggio) Date: Tue, 9 Aug 2022 18:21:48 +0000 Subject: [Archivesspace_Users_Group] Phantom records post-migration to version 3.2.0 Message-ID: Hello ASpace Users; We just upgraded from ArchivesSpace version 2.7.1 to version 3.2.0 and now have "phantom" records in Resources and Subjects. By phantom I mean records show up in ASpace, but are not in the database and when trying to view the record returns: [cid:image001.png at 01D8ABFA.197129D0] As part of this upgrade on our Test machine we: * Started using External Solr as opposed to Internal * Purged the contents of the following directories, but did not delete the directories: * /apps/archivesspace/data/indexer_pui_state * /apps/archivesspace/data/indexer_state * /apps/archivesspace/data/tmp * Kept, but moved /apps/archivesspace/data/solr_backups to /apps/archivesspace/data/old_solr_backups; and created a new /apps/archivesspace/data/solr_backups directory * Refreshed our Test MySQL database from our v2.7.1 Prod version and ran the setup-database.sh script to convert to v3.2.0. We are running MySQL version 8. This left the following directory structure under the data directory: /apps/archivesspace/data>ll total 36 drwxr-xr-x 5 archspc users 147 Oct 16 2019 archivesspace_demo_db drwxr-xr-x 9 archspc users 4096 Oct 18 2019 demo_db_backups -rw-r--r-- 1 archspc users 32 Oct 8 2019 frontend_cookie_secret_cookie_secret.dat -rw-r--r-- 1 archspc users 32 May 14 2020 frontend_cookie_secret.dat drwxr-xr-x 2 archspc users 4096 Aug 9 13:59 indexer_pui_state drwxr-xr-x 2 archspc users 4096 Aug 9 13:59 indexer_state drwxr-xr-x 13 archspc users 4096 Aug 9 00:00 old_solr_backups -rw-r--r-- 1 archspc users 32 Oct 8 2019 public_cookie_secret_cookie_secret.dat -rw-r--r-- 1 archspc users 32 May 14 2020 public_cookie_secret.dat drwxr-xr-x 3 archspc users 22 Oct 28 2019 shared drwxr-xr-x 2 archspc users 6 Aug 9 10:33 solr_backups drwxr-xr-x 13 archspc users 4096 Aug 9 13:59 tmp /apps/archivesspace/data> External Solr was installed on the same Linux server as ArchivesSpace. We installed solr-8.10.0, but see that a newer version solr-8.11.2 is available. Should we be using the newer version? How can we clear the External Solr index in order to rebuild it? What needs to be done to eliminate these phantom records? We are assuming it is something left over from the prior version. Please advise or let us know if you need more information. Thank you. Gerard (Jerry) Boggio | MITRE Corporation | R124 - Collaboration & Info Management | 781-271-2719 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 39627 bytes Desc: image001.png URL: From don.mennerich at nyu.edu Tue Aug 9 16:10:33 2022 From: don.mennerich at nyu.edu (Donald Mennerich) Date: Tue, 9 Aug 2022 16:10:33 -0400 Subject: [Archivesspace_Users_Group] Phantom records post-migration to version 3.2.0 In-Reply-To: References: Message-ID: Greg, One easy way to rebuild the index is to install the Lyrasis reindexer plugin: https://github.com/lyrasis/aspace-reindexer. Once installed, you can either have it rebuild the index via the startup config or by the endpoint that the plugin adds to the API. We recently migrated from 3.0.2 to 3.2.0 and everything went smoothly for us. Once the new version of Aspace was running we hit the endpoint and the database rebuilt. Don Donald R. Mennerich, digital archivist New York University Libraries don.mennerich at nyu.edu (212) 992-6264 On Tue, Aug 9, 2022 at 2:31 PM Jerry Boggio wrote: > Hello ASpace Users; > > > > We just upgraded from ArchivesSpace version 2.7.1 to version 3.2.0 and now > have ?phantom? records in Resources and Subjects. By phantom I mean records > show up in ASpace, but are not in the database and when trying to view the > record returns: > > > > > > As part of this upgrade on our Test machine we: > > - Started using External Solr as opposed to Internal > - Purged the contents of the following directories, but did not delete > the directories: > - /apps/archivesspace/data/indexer_pui_state > - /apps/archivesspace/data/indexer_state > - /apps/archivesspace/data/tmp > - Kept, but moved /apps/archivesspace/data/solr_backups to > /apps/archivesspace/data/old_solr_backups; and created a new > /apps/archivesspace/data/solr_backups directory > - Refreshed our Test MySQL database from our v2.7.1 Prod version and > ran the setup-database.sh script to convert to v3.2.0. We are running MySQL > version 8. > > > > This left the following directory structure under the data directory: > > /apps/archivesspace/data>ll > > total 36 > > drwxr-xr-x 5 archspc users 147 Oct 16 2019 archivesspace_demo_db > > drwxr-xr-x 9 archspc users 4096 Oct 18 2019 demo_db_backups > > -rw-r--r-- 1 archspc users 32 Oct 8 2019 > frontend_cookie_secret_cookie_secret.dat > > -rw-r--r-- 1 archspc users 32 May 14 2020 frontend_cookie_secret.dat > > drwxr-xr-x 2 archspc users 4096 Aug 9 13:59 indexer_pui_state > > drwxr-xr-x 2 archspc users 4096 Aug 9 13:59 indexer_state > > drwxr-xr-x 13 archspc users 4096 Aug 9 00:00 old_solr_backups > > -rw-r--r-- 1 archspc users 32 Oct 8 2019 > public_cookie_secret_cookie_secret.dat > > -rw-r--r-- 1 archspc users 32 May 14 2020 public_cookie_secret.dat > > drwxr-xr-x 3 archspc users 22 Oct 28 2019 shared > > drwxr-xr-x 2 archspc users 6 Aug 9 10:33 solr_backups > > drwxr-xr-x 13 archspc users 4096 Aug 9 13:59 tmp > > /apps/archivesspace/data> > > > > External Solr was installed on the same Linux server as ArchivesSpace. We > installed solr-8.10.0, but see that a newer version solr-8.11.2 is > available. Should we be using the newer version? How can we clear the > External Solr index in order to rebuild it? > > > > What needs to be done to eliminate these phantom records? We are assuming > it is something left over from the prior version. > > > > Please advise or let us know if you need more information. > > > > Thank you. > > *Gerard (Jerry) Boggio* | *MITRE Corporation* | R124 - Collaboration & > Info Management | 781-271-2719 > > > _______________________________________________ > 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__;!!BhJSzQqDqA!Qs-NxBhzce8gwDrB1UySKPtJ8x2TEvwxkmhinor9K7Ksy-DrkniV7fE27FCHkZaOoeKlfypJiCrVfoPdee0$ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 39627 bytes Desc: not available URL: From abrent3 at gmu.edu Wed Aug 10 10:03:29 2022 From: abrent3 at gmu.edu (Amanda T Brent) Date: Wed, 10 Aug 2022 14:03:29 +0000 Subject: [Archivesspace_Users_Group] Agents as Creators not appearing on PUI Message-ID: Hello all, Fairly new to ASpace and I've realized our PUI doesn't display Agents as Creators, though it appears on the back end. Subjects and all other notes we want seem to appear just fine. I've read up on Agents but can't find anything related to this specific problem. Any insight is much appreciated! Amanda Menjivar (Brent), MLS Processing Coordinator Special Collections Research Center George Mason University Phone: 703.993.3559 Pronouns: She/Her/Hers Note: Due to there being no available staff for the University Records Management program at this time, general services (e.g., intake of boxes, appraisal of files, confidential shredding, etc.) are suspended. Non-routine and emergency requests will be reviewed and attempted. Please contact Lynn Eaton (leaton at gmu.edu) for further information. -------------- next part -------------- An HTML attachment was scrubbed... URL: From leah.tams at duke.edu Wed Aug 10 10:19:35 2022 From: leah.tams at duke.edu (Leah Tams) Date: Wed, 10 Aug 2022 14:19:35 +0000 Subject: [Archivesspace_Users_Group] Agents as Creators not appearing on PUI In-Reply-To: References: Message-ID: Hi Amanda, Make sure the Agent is a published record. The "Publish All" feature for a resource record will not publish associated Agent records, so you'll need to do that separately. I think this will fix your issue! 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 Amanda T Brent Sent: Wednesday, August 10, 2022 10:03 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Agents as Creators not appearing on PUI Hello all, Fairly new to ASpace and I've realized our PUI doesn't display Agents as Creators, though it appears on the back end. Subjects and all other notes we want seem to appear just fine. I've read up on Agents but can't find anything related to this specific problem. Any insight is much appreciated! Amanda Menjivar (Brent), MLS Processing Coordinator Special Collections Research Center George Mason University Phone: 703.993.3559 Pronouns: She/Her/Hers Note: Due to there being no available staff for the University Records Management program at this time, general services (e.g., intake of boxes, appraisal of files, confidential shredding, etc.) are suspended. Non-routine and emergency requests will be reviewed and attempted. Please contact Lynn Eaton (leaton at gmu.edu) for further information. -------------- next part -------------- An HTML attachment was scrubbed... URL: From PeregoyA at ccp.arizona.edu Wed Aug 10 11:16:57 2022 From: PeregoyA at ccp.arizona.edu (Peregoy, Alexis Barr - (aperegoy)) Date: Wed, 10 Aug 2022 15:16:57 +0000 Subject: [Archivesspace_Users_Group] Agents as Creators not appearing on PUI In-Reply-To: References: Message-ID: Hi Amanda, Have you checked the publish box for each one? That feature is often overlooked, especially if imported from LCNAF. I?ve had this issue before, too! Alexis Peregoy [A close up of a logo Description automatically generated] Alexis Peregoy Associate Archivist, Center for Creative Photography (520) 621-0050 | ccp.arizona.edu (she/her/hers) ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Amanda T Brent Sent: Wednesday, August 10, 2022 7:03:29 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [EXT][Archivesspace_Users_Group] Agents as Creators not appearing on PUI External Email Hello all, Fairly new to ASpace and I've realized our PUI doesn't display Agents as Creators, though it appears on the back end. Subjects and all other notes we want seem to appear just fine. I've read up on Agents but can't find anything related to this specific problem. Any insight is much appreciated! Amanda Menjivar (Brent), MLS Processing Coordinator Special Collections Research Center George Mason University Phone: 703.993.3559 Pronouns: She/Her/Hers Note: Due to there being no available staff for the University Records Management program at this time, general services (e.g., intake of boxes, appraisal of files, confidential shredding, etc.) are suspended. Non-routine and emergency requests will be reviewed and attempted. Please contact Lynn Eaton (leaton at gmu.edu) for further information. -------------- next part -------------- An HTML attachment was scrubbed... URL: From abrent3 at gmu.edu Wed Aug 10 11:51:53 2022 From: abrent3 at gmu.edu (Amanda T Brent) Date: Wed, 10 Aug 2022 15:51:53 +0000 Subject: [Archivesspace_Users_Group] Agents as Creators not appearing on PUI In-Reply-To: References: Message-ID: Thank you Leah and Alexis!! Publishing solved the problem! Amanda Menjivar (Brent), MLS Processing Coordinator Special Collections Research Center George Mason University Phone: 703.993.3559 Pronouns: She/Her/Hers Note: Due to there being no available staff for the University Records Management program at this time, general services (e.g., intake of boxes, appraisal of files, confidential shredding, etc.) are suspended. Non-routine and emergency requests will be reviewed and attempted. Please contact Lynn Eaton (leaton at gmu.edu) for further information. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Leah Tams Sent: Wednesday, August 10, 2022 10:19 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Agents as Creators not appearing on PUI Hi Amanda, Make sure the Agent is a published record. The ?Publish All? feature for a resource record will not publish associated Agent records, so you?ll need to do that separately. I think this will fix your issue! 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 Amanda T Brent Sent: Wednesday, August 10, 2022 10:03 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Agents as Creators not appearing on PUI Hello all, Fairly new to ASpace and I've realized our PUI doesn't display Agents as Creators, though it appears on the back end. Subjects and all other notes we want seem to appear just fine. I've read up on Agents but can't find anything related to this specific problem. Any insight is much appreciated! Amanda Menjivar (Brent), MLS Processing Coordinator Special Collections Research Center George Mason University Phone: 703.993.3559 Pronouns: She/Her/Hers Note: Due to there being no available staff for the University Records Management program at this time, general services (e.g., intake of boxes, appraisal of files, confidential shredding, etc.) are suspended. Non-routine and emergency requests will be reviewed and attempted. Please contact Lynn Eaton (leaton at gmu.edu) for further information. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gboggio at mitre.org Thu Aug 11 10:45:08 2022 From: gboggio at mitre.org (Jerry Boggio) Date: Thu, 11 Aug 2022 14:45:08 +0000 Subject: [Archivesspace_Users_Group] Phantom records post-migration to version 3.2.0 In-Reply-To: References: Message-ID: Hi Don and other ArchivesSpace Users; Referring to the page Don suggested: ArchivesSpace Reindexer plugin This plugin can be used in two ways: 1. On system startup to initiate a reindex 2. Via the api to trigger a reindex TODO: consider running as a job and making it available that way too. On startup * Set AppConfig[:reindex_on_startup] = true in config.rb * Restart ArchivesSpace Via the api curl -H "X-ArchivesSpace-Session: $SESSION" -X POST http://localhost:4567/plugins/reindex We have set "AppConfig[:reindex_on_startup] = true" in config.rb before the last restart and still have "phantom" records. Looking at the API call, which port should be used here? The port for the External Solr Index, the one specified, or something else? We would also like to know the cause of the "phantom" records. Does it have something to do with the setup-database.sh script? By the way, when running the check_index.sh script in Linux it generates an error. Should there be a new script for External Solr? /apps/archivesspace/scripts>ll total 52 -rw-r--r-- 1 archspc users 317 Apr 16 2021 backup.bat -rwxr-xr-x 1 archspc users 365 Apr 16 2021 backup.sh -rwxr-xr-x 1 archspc users 271 Apr 16 2021 checkindex.bat -rwxr-xr-x 1 archspc users 360 Apr 16 2021 checkindex.sh -rw-r--r-- 1 archspc users 290 Apr 16 2021 ead_export.bat -rwxr-xr-x 1 archspc users 350 Apr 16 2021 ead_export.sh -rwxr-xr-x 1 archspc users 217 Apr 16 2021 find-base.sh -rw-r--r-- 1 archspc users 496 Apr 16 2021 initialize-plugin.bat -rwxr-xr-x 1 archspc users 804 Dec 22 2021 initialize-plugin.sh -rw-r--r-- 1 archspc users 295 Apr 16 2021 password-reset.bat -rwxr-xr-x 1 archspc users 353 Apr 16 2021 password-reset.sh drwxr-xr-x 2 archspc users 46 Feb 4 2022 rb -rwxr-xr-x 1 archspc users 304 Apr 16 2021 setup-database.bat -rwxr-xr-x 1 archspc users 322 Apr 16 2021 setup-database.sh /apps/archivesspace/scripts>./checkindex.sh RuntimeError: Solr war file not found find_solr_war at ../scripts/rb/checkindex.rb:29 check at ../scripts/rb/checkindex.rb:10
at ../scripts/rb/checkindex.rb:86 /apps/archivesspace/scripts> I know there are a lot of questions here and we would appreciate your help in getting answers to all of them. Thank you again! Gerard (Jerry) Boggio | MITRE Corporation | R124 - Collaboration & Info Management | 781-271-2719 Greg, One easy way to rebuild the index is to install the Lyrasis reindexer plugin: https://github.com/lyrasis/aspace-reindexer. Once installed, you can either have it rebuild the index via the startup config or by the endpoint that the plugin adds to the API. We recently migrated from 3.0.2 to 3.2.0 and everything went smoothly for us. Once the new version of Aspace was running we hit the endpoint and the database rebuilt. Don Donald R. Mennerich, digital archivist New York University Libraries don.mennerich at nyu.edu (212) 992-6264 From: Jerry Boggio Sent: Tuesday, August 9, 2022 2:22 PM To: archivesspace_users_group at lyralists.lyrasis.org Cc: Erin Faulder Subject: Phantom records post-migration to version 3.2.0 Hello ASpace Users; We just upgraded from ArchivesSpace version 2.7.1 to version 3.2.0 and now have "phantom" records in Resources and Subjects. By phantom I mean records show up in ASpace, but are not in the database and when trying to view the record returns: [cid:image001.png at 01D8AD6E.CDB2E210] As part of this upgrade on our Test machine we: * Started using External Solr as opposed to Internal * Purged the contents of the following directories, but did not delete the directories: * /apps/archivesspace/data/indexer_pui_state * /apps/archivesspace/data/indexer_state * /apps/archivesspace/data/tmp * Kept, but moved /apps/archivesspace/data/solr_backups to /apps/archivesspace/data/old_solr_backups; and created a new /apps/archivesspace/data/solr_backups directory * Refreshed our Test MySQL database from our v2.7.1 Prod version and ran the setup-database.sh script to convert to v3.2.0. We are running MySQL version 8. This left the following directory structure under the data directory: /apps/archivesspace/data>ll total 36 drwxr-xr-x 5 archspc users 147 Oct 16 2019 archivesspace_demo_db drwxr-xr-x 9 archspc users 4096 Oct 18 2019 demo_db_backups -rw-r--r-- 1 archspc users 32 Oct 8 2019 frontend_cookie_secret_cookie_secret.dat -rw-r--r-- 1 archspc users 32 May 14 2020 frontend_cookie_secret.dat drwxr-xr-x 2 archspc users 4096 Aug 9 13:59 indexer_pui_state drwxr-xr-x 2 archspc users 4096 Aug 9 13:59 indexer_state drwxr-xr-x 13 archspc users 4096 Aug 9 00:00 old_solr_backups -rw-r--r-- 1 archspc users 32 Oct 8 2019 public_cookie_secret_cookie_secret.dat -rw-r--r-- 1 archspc users 32 May 14 2020 public_cookie_secret.dat drwxr-xr-x 3 archspc users 22 Oct 28 2019 shared drwxr-xr-x 2 archspc users 6 Aug 9 10:33 solr_backups drwxr-xr-x 13 archspc users 4096 Aug 9 13:59 tmp /apps/archivesspace/data> External Solr was installed on the same Linux server as ArchivesSpace. We installed solr-8.10.0, but see that a newer version solr-8.11.2 is available. Should we be using the newer version? How can we clear the External Solr index in order to rebuild it? What needs to be done to eliminate these phantom records? We are assuming it is something left over from the prior version. Please advise or let us know if you need more information. Thank you. Gerard (Jerry) Boggio | MITRE Corporation | R124 - Collaboration & Info Management | 781-271-2719 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 39627 bytes Desc: image001.png URL: From sfrieldsmith at sandiego.edu Thu Aug 11 12:37:31 2022 From: sfrieldsmith at sandiego.edu (Sarah Frieldsmith) Date: Thu, 11 Aug 2022 09:37:31 -0700 Subject: [Archivesspace_Users_Group] Restore from snapshot - which files? Message-ID: We had an unfortunate incident where our AS server was restored to a much earlier state. Alos very unfortunately, we do not have a proper backup. We do have a snapshot. What files/directories beyond the database might need to be restored? Appreciate any help with this! *Sarah Frieldsmith* *Systems Librarian* University of San Diego -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.cooper at lyrasis.org Thu Aug 11 14:00:08 2022 From: mark.cooper at lyrasis.org (Mark Cooper) Date: Thu, 11 Aug 2022 18:00:08 +0000 Subject: [Archivesspace_Users_Group] Restore from snapshot - which files? In-Reply-To: References: Message-ID: Hi Sarah, The database is the key piece. You should ultimately be able to reconstruct everything around that. Take a SQL dump of your ArchivesSpace database from the most recent stable restore point and keep that backed up while you work things out. I'm not clear on what your situation is exactly but I can provide some general guidance: Ideally you would find your ArchivesSpace config.rb file so your settings are ready to go. You would find this in the ArchivesSpace "config" directory. Likewise plugins, in the ArchivesSpace "plugins" directory. The Solr index can be rebuilt. You don't need to restore. A normal range would be for this take from 10 minutes to a few hours depending on the size of your database. It can take longer if you have an especially large database and / or some non-standard configuration elements (record inheritance, plugins with search customizations for the indexer). You don't mention your ArchivesSpace version but if you were running external Solr on the same host then you'll need to set that up again, or you may prefer to restore it depending on what options you have internally. However you should follow up with a full reindex if you do any permutation of restoring or retaining a pre-existing index just to be sure you're in sync with the restored database. The easiest place to start would be to use the same version of ArchivesSpace as you were running recently. Run the database setup script first (to catch any potential version drift), then start ArchivesSpace as usual and review things carefully. Because your config and plugins (if any) are also coming, via the snapshot, from a potentially older version of ArchivesSpace than you were running you should review those in case you need to "catch up" on any changes. Best, Mark LYRASIS ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Sarah Frieldsmith Sent: Thursday, August 11, 2022 9:37 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Restore from snapshot - which files? We had an unfortunate incident where our AS server was restored to a much earlier state. Alos very unfortunately, we do not have a proper backup. We do have a snapshot. What files/directories beyond the database might need to be restored? Appreciate any help with this! Sarah Frieldsmith Systems Librarian University of San Diego -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Fri Aug 12 03:39:04 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Fri, 12 Aug 2022 08:39:04 +0100 Subject: [Archivesspace_Users_Group] Phantom records post-migration to version 3.2.0 In-Reply-To: References: Message-ID: <27e176cc-70f2-a176-96f3-1f8fc4d26f5d@bodleian.ox.ac.uk> That plug-in does the equivalent of the "Full reindex" process described here: https://archivesspace.github.io/tech-docs/administration/indexes.html So, it is not something you want running upon startup of a production system, as records will be unavailable until they've been re-indexed, which might take a long time, depending on the size of your collections. It was probably written to help automate the management of Lyrasis's own sandbox.archivesspace.org and test.archivesspace.org servers, which only contain a few test records. A one-off "full reindex" is probably required to fix your phantom records. But you need to watch the application log to monitor that the indexing process starts, and runs all the way to the end, without errors. Personally, I'd trigger it manually, but if your prefer to use the plug-in, then you need to change 4567 in the curl command to the port on which your backend is listening. Usually that is 8089, but double-check the AppConfig[:backend_url] setting in config.rb. If you don't know how to obtain the session token in $SESSION, see the instructions here: https://archivesspace.github.io/tech-docs/api/ If you want to figure out the cause of the phantom records, you should identify some by comparing what's in Solr against what's in MySQL, before running the re-index. Then you could check when they were deleted in the "deleted_records" MySQL table. Andrew. On 11/08/2022 15:45, Jerry Boggio wrote: > > Hi Don and other ArchivesSpace Users; > > Referring to the page Don suggested: > > *ArchivesSpace Reindexer plugin* > > This plugin can be used in two ways: > > 1.On system startup to initiate a reindex > > 2.Via the api to trigger a reindex > > TODO: consider running as a job and making it available that way too. > > *On startup* > > ?Set AppConfig[:reindex_on_startup] = true?in config.rb > > ?Restart ArchivesSpace > > *Via the api* > > curl -H "X-ArchivesSpace-Session: $SESSION" -X POST > http://localhost:4567/plugins/reindex > > We have set ?AppConfig[:reindex_on_startup] = true?inconfig.rb before > the last restart and still have ?phantom? records. > > Looking at the API call, which port should be used here? The port for > the External Solr Index, the one specified, or something else? > > We would also like to know the cause of the ?phantom? records. Does it > have something to do with the setup-database.sh script? > > By the way, when running the check_index.sh script in Linux it > generates an error. Should there be a new script for External Solr? > > /apps/archivesspace/scripts>ll > > total 52 > > -rw-r--r-- 1 archspc users 317 Apr 16? 2021 backup.bat > > -rwxr-xr-x 1 archspc users 365 Apr 16? 2021 backup.sh > > -rwxr-xr-x 1 archspc users 271 Apr 16? 2021 checkindex.bat > > *-rwxr-xr-x 1 archspc users 360 Apr 16? 2021 checkindex.sh*** > > -rw-r--r-- 1 archspc users 290 Apr 16? 2021 ead_export.bat > > -rwxr-xr-x 1 archspc users 350 Apr 16? 2021 ead_export.sh > > -rwxr-xr-x 1 archspc users 217 Apr 16? 2021 find-base.sh > > -rw-r--r-- 1 archspc users 496 Apr 16? 2021 initialize-plugin.bat > > -rwxr-xr-x 1 archspc users 804 Dec 22? 2021 initialize-plugin.sh > > -rw-r--r-- 1 archspc users 295 Apr 16? 2021 password-reset.bat > > -rwxr-xr-x 1 archspc users 353 Apr 16? 2021 password-reset.sh > > drwxr-xr-x 2 archspc users? 46 Feb? 4? 2022 rb > > -rwxr-xr-x 1 archspc users 304 Apr 16? 2021 setup-database.bat > > -rwxr-xr-x 1 archspc users 322 Apr 16? 2021 setup-database.sh > > /apps/archivesspace/scripts>./checkindex.sh > > *RuntimeError: Solr war file not found*** > > find_solr_war at ../scripts/rb/checkindex.rb:29 > > check at ../scripts/rb/checkindex.rb:10 > >
at ../scripts/rb/checkindex.rb:86 > > /apps/archivesspace/scripts> > > I know there are a lot of questions here and we would appreciate your > help in getting answers to all of them. > > Thank you again! > > *Gerard (Jerry) Boggio* | *MITRE Corporation* | R124 - Collaboration & > Info Management| 781-271-2719 > > Greg, > One easy way to rebuild the index is to install the Lyrasis reindexer > plugin: https://github.com/lyrasis/aspace-reindexer. Once installed, you > can either have it rebuild the index via the startup config or by > the endpoint that the plugin adds to the API. We recently migrated from > 3.0.2 to 3.2.0 and everything went smoothly for us. Once the new > version of > Aspace was running we hit the endpoint and the database rebuilt. > Don > Donald R. Mennerich, digital archivist > New York University Libraries > don.mennerich at nyu.edu > > (212) 992-6264 > > *From:* Jerry Boggio > *Sent:* Tuesday, August 9, 2022 2:22 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Cc:* Erin Faulder > *Subject:* Phantom records post-migration to version 3.2.0 > > Hello ASpace Users; > > We just upgraded from ArchivesSpace version 2.7.1 to version 3.2.0 and > now have ?phantom? records in Resources and Subjects. By phantom I > mean records show up in ASpace, but are not in the database and when > trying to view the record returns: > > As part of this upgrade on our Test machine ?we: > > * Started using External Solr as opposed to Internal > * Purged the contents of the following directories, but did not > delete the directories: > o /apps/archivesspace/data/indexer_pui_state > o /apps/archivesspace/data/indexer_state > o /apps/archivesspace/data/tmp > * Kept, but moved /apps/archivesspace/data/solr_backups ?to > ?/apps/archivesspace/data/old_solr_backups; and created a new > /apps/archivesspace/data/solr_backups ?directory > * Refreshed our Test MySQL database from our v2.7.1 Prod version and > ran the setup-database.sh script to convert to v3.2.0. We are > running MySQL version 8. > > This left the following directory structure under the data directory: > > /apps/archivesspace/data>ll > > total 36 > > drwxr-xr-x? 5 archspc users? 147 Oct 16? 2019 archivesspace_demo_db > > drwxr-xr-x? 9 archspc users 4096 Oct 18? 2019 demo_db_backups > > -rw-r--r--? 1 archspc users?? 32 Oct? 8? 2019 > frontend_cookie_secret_cookie_secret.dat > > -rw-r--r--? 1 archspc users?? 32 May 14? 2020 frontend_cookie_secret.dat > > drwxr-xr-x? 2 archspc users 4096 Aug? 9 13:59 indexer_pui_state > > drwxr-xr-x? 2 archspc users 4096 Aug? 9 13:59 indexer_state > > drwxr-xr-x 13 archspc users 4096 Aug? 9 00:00 old_solr_backups > > -rw-r--r--? 1 archspc users?? 32 Oct? 8? 2019 > public_cookie_secret_cookie_secret.dat > > -rw-r--r--? 1 archspc users?? 32 May 14? 2020 public_cookie_secret.dat > > drwxr-xr-x? 3 archspc users?? 22 Oct 28? 2019 shared > > drwxr-xr-x? 2 archspc users??? 6 Aug? 9 10:33 solr_backups > > drwxr-xr-x 13 archspc users 4096 Aug? 9 13:59 tmp > > /apps/archivesspace/data> > > External Solr was installed on the same Linux server as ArchivesSpace. > We installed solr-8.10.0, but see that a newer version solr-8.11.2 is > available. Should we be using the newer version? How can we clear the > External Solr index in order to rebuild it? > > What needs to be done to eliminate these phantom records? We are > assuming it is something left over from the prior version. > > Please advise or let us know if you need more information. > > Thank you. > > *Gerard (Jerry) Boggio* | *MITRE Corporation* | R124 - Collaboration & > Info Management| 781-271-2719 > > > _______________________________________________ > 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.png Type: image/png Size: 39627 bytes Desc: not available URL: From Steve.Giessler at mail.wvu.edu Fri Aug 12 17:30:57 2022 From: Steve.Giessler at mail.wvu.edu (Steven Giessler) Date: Fri, 12 Aug 2022 21:30:57 +0000 Subject: [Archivesspace_Users_Group] date_type accession record errors Message-ID: Dear ArchivesSpace Users Group, Here at West Virginia University, we have a problem where a batch upload of accession records are resulting in new errors appearing in the logs with: F, [2022-08-11T20:14:53.833183 #10996] FATAL -- : F, [2022-08-11T20:14:53.833850 #10996] FATAL -- : ActionView::Template::Error (No such template: "date_type_Single"): F, [2022-08-11T20:14:53.834690 #10996] FATAL -- : 45: <% end %> When you try to Edit each record, and you cannot edit but simply get the dreaded: ?We're sorry, but something went wrong.? Based on the error message in the logs we see when we click ?Edit,? we believe that the Value field single was accidentally capitalized during the batch uploads in .csv files used for the uploads. So, it should have been lower case ?single? instead of ?Single? (we surmise). The first attached screenshot (I hope screenshots are allowed to be included with postings here) shows that we now have a couple of extra value columns now for date_type, with records separated into two groups for each of the erroneous Value fields (Single, and Inclusive which you can see are the last two rows under Controlled Value List: Date Type (date_type). The 2nd attached screenshot shows a sample of the column in the .csv used for the batch upload with the capitalized date_1_type fields. We are thinking to fix this, we probably need to merge ?Single? items with ?single? and ?Inclusive? items with ?inclusive? with lower case Values being the ones they get merged into and then deleting the corresponding capitalized Value instances. Does this make sense? If so, how can we clean this up? I am guessing we may need to edit the MySQL database directly? Or is there a better way through the GUI? With many other Controlled Value Lists there are three options (Suppress/Merge/Delete) in the GUI for each Value, but not so for date_type which only has ?Suppress? as an option. If we could Merge and then Delete we could probably clean this up in the GUI, but that doesn?t appear to be an option for us. We are presently running ArchivesSpace version 2.8.0 on Red Hat Enterprise Linux 7. Thank you in advance for any suggestions, Steve Giessler Professional Technologist WVU Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2022-08-12 at 5.05.17 PM.png Type: image/png Size: 1080382 bytes Desc: Screen Shot 2022-08-12 at 5.05.17 PM.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2022-08-12 at 5.25.43 PM.png Type: image/png Size: 43874 bytes Desc: Screen Shot 2022-08-12 at 5.25.43 PM.png URL: From mark.cooper at lyrasis.org Fri Aug 12 21:04:05 2022 From: mark.cooper at lyrasis.org (Mark Cooper) Date: Sat, 13 Aug 2022 01:04:05 +0000 Subject: [Archivesspace_Users_Group] date_type accession record errors In-Reply-To: References: Message-ID: Hi Steve, I think you're essentially correct here. Direct DB updates are generally frowned upon but are the easiest way out in this case. I'm going completely off memory so backup and try things carefully as I may not be 100% accurate with the SQL: Get the ids for the controlled values from the `enumeration_value` table. === SELECT ev.id, ev.value FROM enumeration_value ev JOIN enumeration e ON e.id = ev.enumeration_id WHERE e.name = 'date_type'; === Update the `date` table `date_type_id` replacing the capitalized value id with the lower case value id. Simplest update would be something like: === UPDATE `date` SET date_type_id = $lower_case_value_id WHERE date_type_id = $capitalized_value_id; === With no relationships to the capitalized value it should be possible to delete it: === DELETE FROM `enumeration_value` WHERE id = $capitalized_value_id; === And I'm not completely sure but I think newer versions of ASpace prevent this from occurring, but I could be wrong on that. Best, Mark LYRASIS ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Steven Giessler Sent: Friday, August 12, 2022 2:30 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] date_type accession record errors Dear ArchivesSpace Users Group, Here at West Virginia University, we have a problem where a batch upload of accession records are resulting in new errors appearing in the logs with: F, [2022-08-11T20:14:53.833183 #10996] FATAL -- : F, [2022-08-11T20:14:53.833850 #10996] FATAL -- : ActionView::Template::Error (No such template: "date_type_Single"): F, [2022-08-11T20:14:53.834690 #10996] FATAL -- : 45: <% end %> When you try to Edit each record, and you cannot edit but simply get the dreaded: ?We're sorry, but something went wrong.? Based on the error message in the logs we see when we click ?Edit,? we believe that the Value field single was accidentally capitalized during the batch uploads in .csv files used for the uploads. So, it should have been lower case ?single? instead of ?Single? (we surmise). The first attached screenshot (I hope screenshots are allowed to be included with postings here) shows that we now have a couple of extra value columns now for date_type, with records separated into two groups for each of the erroneous Value fields (Single, and Inclusive which you can see are the last two rows under Controlled Value List: Date Type (date_type). The 2nd attached screenshot shows a sample of the column in the .csv used for the batch upload with the capitalized date_1_type fields. We are thinking to fix this, we probably need to merge ?Single? items with ?single? and ?Inclusive? items with ?inclusive? with lower case Values being the ones they get merged into and then deleting the corresponding capitalized Value instances. Does this make sense? If so, how can we clean this up? I am guessing we may need to edit the MySQL database directly? Or is there a better way through the GUI? With many other Controlled Value Lists there are three options (Suppress/Merge/Delete) in the GUI for each Value, but not so for date_type which only has ?Suppress? as an option. If we could Merge and then Delete we could probably clean this up in the GUI, but that doesn?t appear to be an option for us. We are presently running ArchivesSpace version 2.8.0 on Red Hat Enterprise Linux 7. Thank you in advance for any suggestions, Steve Giessler Professional Technologist WVU Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From benefiea at gvsu.edu Mon Aug 15 09:48:21 2022 From: benefiea at gvsu.edu (Annie Benefiel) Date: Mon, 15 Aug 2022 13:48:21 +0000 Subject: [Archivesspace_Users_Group] 1st quarter ArchivesSpace Board Meeting Report Message-ID: Dear ArchivesSpace members, As the new chair of the ArchivesSpace Governance Board, I am writing to report on the group's 1st Quarter meeting, which was held July 28, 2022. We heard updates and discussed the following topics: * An operations report which highlighted the membership renewal process and progress on recently approved board measures including implementing changes to the Educational Program and Community-Wide Training efforts * The continued excellent work of TAC and UAC. The new chairs are working closely on a council handbook and group orientation. These efforts are designed to help clarify direction and resources available during council transitions and beyond. * The May 27 Governance/Community session which was designed to help clarify the governance board's role and provide opportunities for members to identify their representatives for further engagement. The board agreed to do this on an annual basis. * Updates on the diversity and equity work being done at member institutions and how they could enhance our own equity endeavors * Financial reports, which show that the program's financial position continues to be strong * Continuing our efforts to foster program sustainability using the It Takes a Village (ITaV) framework. We have undertaken activities relating to governance and will continue to review and refine practices and define benchmarks. As always, the Board welcomes your feedback. Feel free to reach out directly to me or to your elected representative. I'm pleased to be working with you as Governance Board chair this year. I'd like to thank my fellow board members and everyone in the ArchivesSpace community for your continued energy and commitment to this program. I really appreciate how resilient and responsive this community has been and I'm excited to see how we continue to grow. Sincerely, Annie Benefiel Chair, ArchivesSpace Governance Board University Archivist and Digital Collections Librarian University Libraries Grand Valley State University Seidman House Allendale, MI 49401 Pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From don.mennerich at nyu.edu Mon Aug 15 13:02:21 2022 From: don.mennerich at nyu.edu (Donald Mennerich) Date: Mon, 15 Aug 2022 10:02:21 -0700 Subject: [Archivesspace_Users_Group] Phantom records post-migration to version 3.2.0 In-Reply-To: References: Message-ID: Jerry, Glad it worked out for you, and apologies for getting your name mixed up as 'Greg'. Don Donald R. Mennerich, digital archivist New York University Libraries don.mennerich at nyu.edu (212) 992-6264 On Mon, Aug 15, 2022 at 6:56 AM Jerry Boggio wrote: > Issue resolved. What I neglected to do was add the following to config.rb: > > > > AppConfig[:plugins] = ['local', 'lcnaf', 'aspace-reindexer-main'] > > > > Initially 'aspace-reindexer-main' was in a subdirectory plugins/mitre and > I expected that adding the mitre directory would find the files within that > directory, but apparently 'aspace-reindexer-main' needed to be moved up to > the plugins directory or specified as 'mitreaspace-reindexer-main'. > > > > Once again, thank you! > > *Gerard (Jerry) Boggio* | *MITRE Corporation* | R124 - Collaboration & > Info Management | 781-271-2719 > > > > *From:* Jerry Boggio > *Sent:* Thursday, August 11, 2022 10:45 AM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Cc:* don.mennerich at nyu.edu > *Subject:* RE: Phantom records post-migration to version 3.2.0 > > > > Hi Don and other ArchivesSpace Users; > > > > Referring to the page Don suggested: > > > > *ArchivesSpace Reindexer plugin* > > This plugin can be used in two ways: > > 1. On system startup to initiate a reindex > > 2. Via the api to trigger a reindex > > TODO: consider running as a job and making it available that way too. > > *On startup* > > ? Set AppConfig[:reindex_on_startup] = true in config.rb > > ? Restart ArchivesSpace > > *Via the api* > > curl -H "X-ArchivesSpace-Session: $SESSION" -X POST > http://localhost:4567/plugins/reindex > > > > > We have set ?AppConfig[:reindex_on_startup] = true? in config.rb before > the last restart and still have ?phantom? records. > > Looking at the API call, which port should be used here? The port for the > External Solr Index, the one specified, or something else? > > We would also like to know the cause of the ?phantom? records. Does it > have something to do with the setup-database.sh script? > > By the way, when running the check_index.sh script in Linux it generates > an error. Should there be a new script for External Solr? > > /apps/archivesspace/scripts>ll > > total 52 > > -rw-r--r-- 1 archspc users 317 Apr 16 2021 backup.bat > > -rwxr-xr-x 1 archspc users 365 Apr 16 2021 backup.sh > > -rwxr-xr-x 1 archspc users 271 Apr 16 2021 checkindex.bat > > *-rwxr-xr-x 1 archspc users 360 Apr 16 2021 checkindex.sh* > > -rw-r--r-- 1 archspc users 290 Apr 16 2021 ead_export.bat > > -rwxr-xr-x 1 archspc users 350 Apr 16 2021 ead_export.sh > > -rwxr-xr-x 1 archspc users 217 Apr 16 2021 find-base.sh > > -rw-r--r-- 1 archspc users 496 Apr 16 2021 initialize-plugin.bat > > -rwxr-xr-x 1 archspc users 804 Dec 22 2021 initialize-plugin.sh > > -rw-r--r-- 1 archspc users 295 Apr 16 2021 password-reset.bat > > -rwxr-xr-x 1 archspc users 353 Apr 16 2021 password-reset.sh > > drwxr-xr-x 2 archspc users 46 Feb 4 2022 rb > > -rwxr-xr-x 1 archspc users 304 Apr 16 2021 setup-database.bat > > -rwxr-xr-x 1 archspc users 322 Apr 16 2021 setup-database.sh > > /apps/archivesspace/scripts>./checkindex.sh > > *RuntimeError: Solr war file not found* > > find_solr_war at ../scripts/rb/checkindex.rb:29 > > check at ../scripts/rb/checkindex.rb:10 > >
at ../scripts/rb/checkindex.rb:86 > > /apps/archivesspace/scripts> > > > > I know there are a lot of questions here and we would appreciate your help > in getting answers to all of them. > > > > Thank you again! > > *Gerard (Jerry) Boggio* | *MITRE Corporation* | R124 - Collaboration & > Info Management | 781-271-2719 > > > > > > Greg, > > > > One easy way to rebuild the index is to install the Lyrasis reindexer > > plugin: https://github.com/lyrasis/aspace-reindexer. Once installed, you > > can either have it rebuild the index via the startup config or by > > the endpoint that the plugin adds to the API. We recently migrated from > > 3.0.2 to 3.2.0 and everything went smoothly for us. Once the new version of > > Aspace was running we hit the endpoint and the database rebuilt. > > > > Don > > > > Donald R. Mennerich, digital archivist > > New York University Libraries > > don.mennerich at nyu.edu (212) 992-6264 > > > > > > *From:* Jerry Boggio > *Sent:* Tuesday, August 9, 2022 2:22 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Cc:* Erin Faulder > *Subject:* Phantom records post-migration to version 3.2.0 > > > > Hello ASpace Users; > > > > We just upgraded from ArchivesSpace version 2.7.1 to version 3.2.0 and now > have ?phantom? records in Resources and Subjects. By phantom I mean records > show up in ASpace, but are not in the database and when trying to view the > record returns: > > > > > > As part of this upgrade on our Test machine we: > > - Started using External Solr as opposed to Internal > - Purged the contents of the following directories, but did not delete > the directories: > - /apps/archivesspace/data/indexer_pui_state > - /apps/archivesspace/data/indexer_state > - /apps/archivesspace/data/tmp > - Kept, but moved /apps/archivesspace/data/solr_backups to > /apps/archivesspace/data/old_solr_backups; and created a new > /apps/archivesspace/data/solr_backups directory > - Refreshed our Test MySQL database from our v2.7.1 Prod version and > ran the setup-database.sh script to convert to v3.2.0. We are running MySQL > version 8. > > > > This left the following directory structure under the data directory: > > /apps/archivesspace/data>ll > > total 36 > > drwxr-xr-x 5 archspc users 147 Oct 16 2019 archivesspace_demo_db > > drwxr-xr-x 9 archspc users 4096 Oct 18 2019 demo_db_backups > > -rw-r--r-- 1 archspc users 32 Oct 8 2019 > frontend_cookie_secret_cookie_secret.dat > > -rw-r--r-- 1 archspc users 32 May 14 2020 frontend_cookie_secret.dat > > drwxr-xr-x 2 archspc users 4096 Aug 9 13:59 indexer_pui_state > > drwxr-xr-x 2 archspc users 4096 Aug 9 13:59 indexer_state > > drwxr-xr-x 13 archspc users 4096 Aug 9 00:00 old_solr_backups > > -rw-r--r-- 1 archspc users 32 Oct 8 2019 > public_cookie_secret_cookie_secret.dat > > -rw-r--r-- 1 archspc users 32 May 14 2020 public_cookie_secret.dat > > drwxr-xr-x 3 archspc users 22 Oct 28 2019 shared > > drwxr-xr-x 2 archspc users 6 Aug 9 10:33 solr_backups > > drwxr-xr-x 13 archspc users 4096 Aug 9 13:59 tmp > > /apps/archivesspace/data> > > > > External Solr was installed on the same Linux server as ArchivesSpace. We > installed solr-8.10.0, but see that a newer version solr-8.11.2 is > available. Should we be using the newer version? How can we clear the > External Solr index in order to rebuild it? > > > > What needs to be done to eliminate these phantom records? We are assuming > it is something left over from the prior version. > > > > Please advise or let us know if you need more information. > > > > Thank you. > > *Gerard (Jerry) Boggio* | *MITRE Corporation* | R124 - Collaboration & > Info Management | 781-271-2719 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 39627 bytes Desc: not available URL: From gboggio at mitre.org Mon Aug 15 09:56:43 2022 From: gboggio at mitre.org (Jerry Boggio) Date: Mon, 15 Aug 2022 13:56:43 +0000 Subject: [Archivesspace_Users_Group] Phantom records post-migration to version 3.2.0 In-Reply-To: References: Message-ID: Issue resolved. What I neglected to do was add the following to config.rb: AppConfig[:plugins] = ['local', 'lcnaf', 'aspace-reindexer-main'] Initially 'aspace-reindexer-main' was in a subdirectory plugins/mitre and I expected that adding the mitre directory would find the files within that directory, but apparently 'aspace-reindexer-main' needed to be moved up to the plugins directory or specified as 'mitreaspace-reindexer-main'. Once again, thank you! Gerard (Jerry) Boggio | MITRE Corporation | R124 - Collaboration & Info Management | 781-271-2719 From: Jerry Boggio Sent: Thursday, August 11, 2022 10:45 AM To: archivesspace_users_group at lyralists.lyrasis.org Cc: don.mennerich at nyu.edu Subject: RE: Phantom records post-migration to version 3.2.0 Hi Don and other ArchivesSpace Users; Referring to the page Don suggested: ArchivesSpace Reindexer plugin This plugin can be used in two ways: 1. On system startup to initiate a reindex 2. Via the api to trigger a reindex TODO: consider running as a job and making it available that way too. On startup * Set AppConfig[:reindex_on_startup] = true in config.rb * Restart ArchivesSpace Via the api curl -H "X-ArchivesSpace-Session: $SESSION" -X POST http://localhost:4567/plugins/reindex We have set "AppConfig[:reindex_on_startup] = true" in config.rb before the last restart and still have "phantom" records. Looking at the API call, which port should be used here? The port for the External Solr Index, the one specified, or something else? We would also like to know the cause of the "phantom" records. Does it have something to do with the setup-database.sh script? By the way, when running the check_index.sh script in Linux it generates an error. Should there be a new script for External Solr? /apps/archivesspace/scripts>ll total 52 -rw-r--r-- 1 archspc users 317 Apr 16 2021 backup.bat -rwxr-xr-x 1 archspc users 365 Apr 16 2021 backup.sh -rwxr-xr-x 1 archspc users 271 Apr 16 2021 checkindex.bat -rwxr-xr-x 1 archspc users 360 Apr 16 2021 checkindex.sh -rw-r--r-- 1 archspc users 290 Apr 16 2021 ead_export.bat -rwxr-xr-x 1 archspc users 350 Apr 16 2021 ead_export.sh -rwxr-xr-x 1 archspc users 217 Apr 16 2021 find-base.sh -rw-r--r-- 1 archspc users 496 Apr 16 2021 initialize-plugin.bat -rwxr-xr-x 1 archspc users 804 Dec 22 2021 initialize-plugin.sh -rw-r--r-- 1 archspc users 295 Apr 16 2021 password-reset.bat -rwxr-xr-x 1 archspc users 353 Apr 16 2021 password-reset.sh drwxr-xr-x 2 archspc users 46 Feb 4 2022 rb -rwxr-xr-x 1 archspc users 304 Apr 16 2021 setup-database.bat -rwxr-xr-x 1 archspc users 322 Apr 16 2021 setup-database.sh /apps/archivesspace/scripts>./checkindex.sh RuntimeError: Solr war file not found find_solr_war at ../scripts/rb/checkindex.rb:29 check at ../scripts/rb/checkindex.rb:10
at ../scripts/rb/checkindex.rb:86 /apps/archivesspace/scripts> I know there are a lot of questions here and we would appreciate your help in getting answers to all of them. Thank you again! Gerard (Jerry) Boggio | MITRE Corporation | R124 - Collaboration & Info Management | 781-271-2719 Greg, One easy way to rebuild the index is to install the Lyrasis reindexer plugin: https://github.com/lyrasis/aspace-reindexer. Once installed, you can either have it rebuild the index via the startup config or by the endpoint that the plugin adds to the API. We recently migrated from 3.0.2 to 3.2.0 and everything went smoothly for us. Once the new version of Aspace was running we hit the endpoint and the database rebuilt. Don Donald R. Mennerich, digital archivist New York University Libraries don.mennerich at nyu.edu (212) 992-6264 From: Jerry Boggio > Sent: Tuesday, August 9, 2022 2:22 PM To: archivesspace_users_group at lyralists.lyrasis.org Cc: Erin Faulder > Subject: Phantom records post-migration to version 3.2.0 Hello ASpace Users; We just upgraded from ArchivesSpace version 2.7.1 to version 3.2.0 and now have "phantom" records in Resources and Subjects. By phantom I mean records show up in ASpace, but are not in the database and when trying to view the record returns: [cid:image001.png at 01D8B08D.51AB0770] As part of this upgrade on our Test machine we: * Started using External Solr as opposed to Internal * Purged the contents of the following directories, but did not delete the directories: * /apps/archivesspace/data/indexer_pui_state * /apps/archivesspace/data/indexer_state * /apps/archivesspace/data/tmp * Kept, but moved /apps/archivesspace/data/solr_backups to /apps/archivesspace/data/old_solr_backups; and created a new /apps/archivesspace/data/solr_backups directory * Refreshed our Test MySQL database from our v2.7.1 Prod version and ran the setup-database.sh script to convert to v3.2.0. We are running MySQL version 8. This left the following directory structure under the data directory: /apps/archivesspace/data>ll total 36 drwxr-xr-x 5 archspc users 147 Oct 16 2019 archivesspace_demo_db drwxr-xr-x 9 archspc users 4096 Oct 18 2019 demo_db_backups -rw-r--r-- 1 archspc users 32 Oct 8 2019 frontend_cookie_secret_cookie_secret.dat -rw-r--r-- 1 archspc users 32 May 14 2020 frontend_cookie_secret.dat drwxr-xr-x 2 archspc users 4096 Aug 9 13:59 indexer_pui_state drwxr-xr-x 2 archspc users 4096 Aug 9 13:59 indexer_state drwxr-xr-x 13 archspc users 4096 Aug 9 00:00 old_solr_backups -rw-r--r-- 1 archspc users 32 Oct 8 2019 public_cookie_secret_cookie_secret.dat -rw-r--r-- 1 archspc users 32 May 14 2020 public_cookie_secret.dat drwxr-xr-x 3 archspc users 22 Oct 28 2019 shared drwxr-xr-x 2 archspc users 6 Aug 9 10:33 solr_backups drwxr-xr-x 13 archspc users 4096 Aug 9 13:59 tmp /apps/archivesspace/data> External Solr was installed on the same Linux server as ArchivesSpace. We installed solr-8.10.0, but see that a newer version solr-8.11.2 is available. Should we be using the newer version? How can we clear the External Solr index in order to rebuild it? What needs to be done to eliminate these phantom records? We are assuming it is something left over from the prior version. Please advise or let us know if you need more information. Thank you. Gerard (Jerry) Boggio | MITRE Corporation | R124 - Collaboration & Info Management | 781-271-2719 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 39627 bytes Desc: image001.png URL: From jcross at clemson.edu Mon Aug 15 13:17:15 2022 From: jcross at clemson.edu (James E. Cross) Date: Mon, 15 Aug 2022 17:17:15 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace PUI and diacritics Message-ID: Pardon me for what may seem to be a very basic question, but does the ArchivesSpace PUI have the ability to search for names with diacritical marks? I assume so but I would like to be sure. Thank you. James Cross Manuscripts Archivist James Edward Cross, C.A. CLEMSON UNIVERSITY Manuscripts Archivist Special Collections and Archives Clemson University Libraries Box 343001 Clemson, SC 29634-3001 Phone: (864) 656-5182 Website: http://library.clemson.edu/depts/specialcollections/ Pronouns: he/him/his Traditional Cherokee Lands | Site of Fort Hill Plantation Please do not feel obligated to respond to this message outside of your normal working hours. -------------- next part -------------- An HTML attachment was scrubbed... URL: From PeregoyA at ccp.arizona.edu Mon Aug 15 13:25:22 2022 From: PeregoyA at ccp.arizona.edu (Peregoy, Alexis Barr - (aperegoy)) Date: Mon, 15 Aug 2022 17:25:22 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace PUI and diacritics In-Reply-To: References: Message-ID: Hi James, Yes, it does! As an example - if you go to aspace.ccp.arizona.edu and type in Lola ?lvarez Bravo, you will see it appear in the search result. Alexis [A close up of a logo Description automatically generated] Alexis Peregoy Associate Archivist, Center for Creative Photography (520) 621-0050 | ccp.arizona.edu (she/her/hers) ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of James E. Cross Sent: Monday, August 15, 2022 10:17 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [EXT][Archivesspace_Users_Group] ArchivesSpace PUI and diacritics External Email Pardon me for what may seem to be a very basic question, but does the ArchivesSpace PUI have the ability to search for names with diacritical marks? I assume so but I would like to be sure. Thank you. James Cross Manuscripts Archivist James Edward Cross, C.A. CLEMSON UNIVERSITY Manuscripts Archivist Special Collections and Archives Clemson University Libraries Box 343001 Clemson, SC 29634-3001 Phone: (864) 656-5182 Website: http://library.clemson.edu/depts/specialcollections/ Pronouns: he/him/his Traditional Cherokee Lands | Site of Fort Hill Plantation Please do not feel obligated to respond to this message outside of your normal working hours. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-A close up.png Type: image/png Size: 2640 bytes Desc: Outlook-A close up.png URL: From jcross at clemson.edu Mon Aug 15 13:38:44 2022 From: jcross at clemson.edu (James E. Cross) Date: Mon, 15 Aug 2022 17:38:44 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace PUI and diacritics In-Reply-To: References: Message-ID: Thank you! Jim From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Peregoy, Alexis Barr - (aperegoy) Sent: Monday, August 15, 2022 1:25 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace PUI and diacritics Hi James, Yes, it does! As an example - if you go to aspace.ccp.arizona.edu and type in Lola ?lvarez Bravo, you will see it appear in the search result. Alexis [A close up of a logo Description automatically generated] Alexis Peregoy Associate Archivist, Center for Creative Photography (520) 621-0050 | ccp.arizona.edu (she/her/hers) ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of James E. Cross > Sent: Monday, August 15, 2022 10:17 AM To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [EXT][Archivesspace_Users_Group] ArchivesSpace PUI and diacritics External Email Pardon me for what may seem to be a very basic question, but does the ArchivesSpace PUI have the ability to search for names with diacritical marks? I assume so but I would like to be sure. Thank you. James Cross Manuscripts Archivist James Edward Cross, C.A. CLEMSON UNIVERSITY Manuscripts Archivist Special Collections and Archives Clemson University Libraries Box 343001 Clemson, SC 29634-3001 Phone: (864) 656-5182 Website: http://library.clemson.edu/depts/specialcollections/ Pronouns: he/him/his Traditional Cherokee Lands | Site of Fort Hill Plantation Please do not feel obligated to respond to this message outside of your normal working hours. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2640 bytes Desc: image001.png URL: From rachel at weeksvillesociety.org Mon Aug 15 14:33:12 2022 From: rachel at weeksvillesociety.org (Rachel Finn) Date: Mon, 15 Aug 2022 14:33:12 -0400 Subject: [Archivesspace_Users_Group] Preferred DAMS? Message-ID: Hi, Everyone. I am the solo librarian and archivist at Weeksville Heritage Center in Brooklyn, NY. WHC is part of the diversity cohort this year and so I'm settling into ArchivesSpace... WHC also has a library catalog that I'm setting up. I need to find a DAMS that can be the home for digitized materials and oral histories that can be easily linked to the two systems mentioned above. We have Macs. I've been seriously leaning toward CollectiveAccess. I'm interested in knowing what systems you all are using and what you think of them, as well as what if any experience you have with Collective Access. Currently parts of the collection live on Omeka and there is also a possibility that I'll just stick with that so I'd like to hear any thoughts on Omeka, too. Thanks in advance. --Rachel ================= Rachel Finn Collections Manager Weeksville Heritage Center telephone: 718-756-5250 x330 email: rachel at weeksvillesociety.org WEEKSVILLE HERITAGE CENTER COVID-19 VISITOR PROCEDURES HELP STOP THE SPREAD! As a member of the NYC Cultural Institutions Group, Weeksville Heritage Center requires all visitors over the age of 5 to provide proof of vaccination against COVID-19 for indoor activities. Key to NYC Where to get vaccinated today -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Tue Aug 16 08:59:14 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 16 Aug 2022 12:59:14 +0000 Subject: [Archivesspace_Users_Group] There's still time to register for the ArchivesSpace Member Forum In-Reply-To: References: Message-ID: [Graphical user interface Description automatically generated with medium confidence] Dear ArchivesSpace members, Registration is now open for the 8th Annual ArchivesSpace Member Forum! Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. We will be holding a half-day, in-person member meeting on August 24, 2022, in the Commonwealth Room on the third floor of the Sheraton Boston Hotel. In addition to this in-person meeting, we will also hold two virtual workshops on August 30-31, 2022. These free events are a chance for ArchivesSpace members to come together to highlight the work they are doing in ArchivesSpace, show off new plugins or tools they?ve developed, and attend instructional sessions and discussions on a variety of topics. As with our previous Annual Member Forums, it is being held in conjunction with the Society of American Archivists annual meeting, but it is not part of SAA and does not require registration for the SAA Annual Meeting. In-person meeting details: When: August 24, 2022 from 9:00am-12:30pm ET Where: Commonwealth Room, Third Floor, Sheraton Boston Hotel In an effort to minimize risk and keep our community members safe, no food will be provided at the forum. Beverages will be provided, though we ask you to remain masked whenever you are not drinking. Virtual workshops details: When: August 30-31st, 2022 Where: Online; via Zoom Who Can Attend: The ArchivesSpace Member Forum is open to individuals from ArchivesSpace member institutions only. To register, you must use an institutional email address associated with an ArchivesSpace member institution. Registrations using personal email addresses and addresses associated with non-member institutions will not be accepted. This means that events with limited capacity may fill before you are able to correct your registration. Online registration: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/3128066258/ArchivesSpace+Member+Forum+2022 Registrations for each day are separate and you must register individually for all days/events you are interested in attending. Registration information is linked above each event on the agenda. All in-person sessions and virtual workshops will be recorded. Propose a session or topic: The program is still developing. If you would like to propose a session or topic for the forum, there is a short Google form for proposals available at https://forms.gle/V7gtps3E9vnvdLXX7. Proposals will be reviewed on a rolling basis. Please feel free to contact ArchivesSpace Community Engagement Coordinator Jessica Crouch (jessica.crouch at lyrasis.org) with questions. We look forward to seeing you in-person or virtually. Best, Jessica Crouch Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 288893 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Tue Aug 16 16:31:46 2022 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 16 Aug 2022 20:31:46 +0000 Subject: [Archivesspace_Users_Group] release candidate available - ArchivesSpace v3.3.0-RC1 In-Reply-To: References: Message-ID: Hello ArchivesSpace members, The ArchivesSpace team is pleased to announce a release candidate, v3.3.0-RC1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v3.3.0-RC1 or test it out without downloading at http://test.archivesspace.org/staff (username admin /password admin). This release candidate includes many small bug fixes and feature enhancements. Of particular note are some enhancements to spawning from accessions and an option for logged in users to change their own passwords. As part of the spawning improvements, the plugin Hudson Molonglo developed for The New School Archives and Special Collections to link accessions to archival objects has been incorporated into the core code of ArchivesSpace. A particular thanks to our Testing sub-team for their work testing individual JIRAs and doing regression testing across the application. Please try this release candidate out and let us know at ArchivesSpaceHome at lyrasis.org by August 29 if you notice any problems with the specific areas addressed in this release, or if anything that was working before no longer is. Pending the results of this testing, we will aim to release the production version of 3.3.0 shortly afterwards. Please get in touch if you have any questions. Thanks as always for your feedback and support. 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 shand at ap.org Wed Aug 17 17:24:58 2022 From: shand at ap.org (Hand, Sarit) Date: Wed, 17 Aug 2022 21:24:58 +0000 Subject: [Archivesspace_Users_Group] Preferred DAMS? In-Reply-To: References: Message-ID: Hi Rachel, The TAC Integrations sub-team has been updating its pages, ArchivesSpace Integrations. If you look in the navigation pane you will see integration pages separated by categories of system types which you can also see here. Next week, a new survey is going out to collect updated information about systems that others use which integrated with ASpace. If you are not in a rush, you could wait for those results but I do not expect them to be updated on the pages before the new year. Hope that helps. Cheers [cid:image005.png at 01D8B25E.453FAAE0] Sarit Hand Digital Archivist AP Corporate Archives 200 Liberty Street New York, NY 10281 T 212.621.7035 shand at ap.org ap.org [cid:image006.png at 01D8B25E.453FAAE0] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Rachel Finn Sent: Monday, August 15, 2022 2:33 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Preferred DAMS? [EXTERNAL] Hi, Everyone. I am the solo librarian and archivist at Weeksville Heritage Center in Brooklyn, NY. WHC is part of the diversity cohort this year and so I'm settling into ArchivesSpace... WHC also has a library catalog that I'm setting up. I need to find a DAMS that can be the home for digitized materials and oral histories that can be easily linked to the two systems mentioned above. We have Macs. I've been seriously leaning toward CollectiveAccess. I'm interested in knowing what systems you all are using and what you think of them, as well as what if any experience you have with Collective Access. Currently parts of the collection live on Omeka and there is also a possibility that I'll just stick with that so I'd like to hear any thoughts on Omeka, too. Thanks in advance. --Rachel ================= Rachel Finn Collections Manager Weeksville Heritage Center telephone: 718-756-5250 x330 email: rachel at weeksvillesociety.org WEEKSVILLE HERITAGE CENTER COVID-19 VISITOR PROCEDURES HELP STOP THE SPREAD! As a member of the NYC Cultural Institutions Group, Weeksville Heritage Center requires all visitors over the age of 5 to provide proof of vaccination against COVID-19 for indoor activities. Key to NYC Where to get vaccinated today The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1500 and delete this email. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 1093 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 5546 bytes Desc: image006.png URL: From Jessica.Crouch at lyrasis.org Thu Aug 18 08:58:49 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 18 Aug 2022 12:58:49 +0000 Subject: [Archivesspace_Users_Group] Survey Participation Requested by August 22: Selecting ArchivesSpace Community-wide Training Topics In-Reply-To: References: Message-ID: Dear ArchivesSpace users, Thank you to those who attended the first training offering in the new ArchivesSpace Community-wide Training program. The ArchivesSpace Trainers Corps is requesting community input to help determine future training topics. A survey for this purpose is available at https://www.surveymonkey.com/r/2P9T83M. Responses to this survey will be used by the Trainers Corps to prioritize offering the top 3 selections over the course of the next year. ArchivesSpace community-wide trainings will be 2-3 hours in length, depending on the topic. These trainings are offered for a fee but ArchivesSpace members receive a substantial discount. Survey responses are due by August 22, 2022. To learn more about ArchivesSpace community-wide training, visit https://archivesspace.org/using-archivesspace/trainings. Best, Jessica Crouch 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: image002.jpg Type: image/jpeg Size: 29147 bytes Desc: image002.jpg URL: From rachel at weeksvillesociety.org Mon Aug 22 10:42:14 2022 From: rachel at weeksvillesociety.org (Rachel Finn) Date: Mon, 22 Aug 2022 10:42:14 -0400 Subject: [Archivesspace_Users_Group] Preferred DAMS? In-Reply-To: References: Message-ID: Thanks everyone. Sorry I went quiet there. Responses we're going right to spam for a minute. This is all helpful. --Rachel ================= Rachel Finn Collections Manager Weeksville Heritage Center telephone: 718-756-5250 x330 email: rachel at weeksvillesociety.org WEEKSVILLE HERITAGE CENTER COVID-19 VISITOR PROCEDURES HELP STOP THE SPREAD! As a member of the NYC Cultural Institutions Group, Weeksville Heritage Center requires all visitors over the age of 5 to provide proof of vaccination against COVID-19 for indoor activities. Key to NYC Where to get vaccinated today On Wed, Aug 17, 2022 at 5:25 PM Hand, Sarit wrote: > Hi Rachel, > > > > The TAC Integrations sub-team has been updating its pages, ArchivesSpace > Integrations > . > If you look in the navigation pane you will see integration pages separated > by categories of system types which you can also see here > . > > > > > Next week, a new survey is going out to collect updated information about > systems that others use which integrated with ASpace. If you are not in a > rush, you could wait for those results but I do not expect them to be > updated on the pages before the new year. > > > > Hope that helps. > > Cheers > > > > > > *Sarit Hand* > > Digital Archivist > AP Corporate Archives > > 200 Liberty Street > > New York, NY 10281 > > T 212.621.7035 > > > > shand at ap.org > ap.org > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Rachel > Finn > *Sent:* Monday, August 15, 2022 2:33 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Preferred DAMS? > > > > [EXTERNAL] > > Hi, Everyone. > > > > I am the solo librarian and archivist at Weeksville Heritage Center in > Brooklyn, NY. WHC is part of the diversity cohort this year and so I'm > settling into ArchivesSpace... WHC also has a library catalog that I'm > setting up. > > > > I need to find a DAMS that can be the home for digitized materials and > oral histories that can be easily linked to the two systems mentioned > above. We have Macs. > > > > I've been seriously leaning toward CollectiveAccess. I'm interested in > knowing what systems you all are using and what you think of them, as well > as what if any experience you have with Collective Access. Currently parts > of the collection live on Omeka and there is also a possibility that I'll > just stick with that so I'd like to hear any thoughts on Omeka, too. > > > > Thanks in advance. > > > > --Rachel > > ================= > > *Rachel Finn* > > Collections Manager > > *Weeksville Heritage Center * > > telephone: 718-756-5250 x330 > > email: rachel at weeksvillesociety.org > > > > *WEEKSVILLE HERITAGE CENTER * > > *COVID-19 VISITOR PROCEDURES* > > *HELP STOP THE SPREAD!* > > > > As a member of the NYC Cultural Institutions Group, > > Weeksville Heritage Center requires all visitors over the age of > > 5 to provide proof of vaccination against COVID-19 for indoor activities. > > > > Key to NYC > > > Where to get vaccinated today > > > > > > > > > > The information contained in this communication is intended for the use of > the designated recipients named above. If the reader of this communication > is not the intended recipient, you are hereby notified that you have > received this communication in error, and that any review, dissemination, > distribution or copying of this communication is strictly prohibited. If > you have received this communication in error, please notify The Associated > Press immediately by telephone at +1-212-621-1500 and delete this email. > Thank you. > _______________________________________________ > 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: image005.png Type: image/png Size: 1093 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 5546 bytes Desc: not available URL: From Steve.Giessler at mail.wvu.edu Mon Aug 22 17:10:10 2022 From: Steve.Giessler at mail.wvu.edu (Steven Giessler) Date: Mon, 22 Aug 2022 21:10:10 +0000 Subject: [Archivesspace_Users_Group] date_type accession record errors Message-ID: <9BDAE9B4-4A9B-4717-9C34-3ECA9497C110@mail.wvu.edu> Thank you Mark for your reply, much appreciated. We ended up fixing it via the API using some Python code that our Digital Archivist, Elizabeth James, wrote. She ran her code after we took a snapshot of the VM, and it worked fine to suppress and then merge the records. So, all is well with our instance now thanks to Elizabeth! Just wanted to give you an update on this. Thanks again! Steve Giessler Professional Technologist WVU Libraries From: on behalf of Mark Cooper Reply-To: Archivesspace Users Group Date: Friday, August 12, 2022 at 9:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] date_type accession record errors Hi Steve, I think you're essentially correct here. Direct DB updates are generally frowned upon but are the easiest way out in this case. I'm going completely off memory so backup and try things carefully as I may not be 100% accurate with the SQL: Get the ids for the controlled values from the `enumeration_value` table. === SELECT ev.id, ev.value FROM enumeration_value ev JOIN enumeration e ON e.id = ev.enumeration_id WHERE e.name = 'date_type'; === Update the `date` table `date_type_id` replacing the capitalized value id with the lower case value id. Simplest update would be something like: === UPDATE `date` SET date_type_id = $lower_case_value_id WHERE date_type_id = $capitalized_value_id; === With no relationships to the capitalized value it should be possible to delete it: === DELETE FROM `enumeration_value` WHERE id = $capitalized_value_id; === And I'm not completely sure but I think newer versions of ASpace prevent this from occurring, but I could be wrong on that. Best, Mark LYRASIS ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Steven Giessler Sent: Friday, August 12, 2022 2:30 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] date_type accession record errors Dear ArchivesSpace Users Group, Here at West Virginia University, we have a problem where a batch upload of accession records are resulting in new errors appearing in the logs with: F, [2022-08-11T20:14:53.833183 #10996] FATAL -- : F, [2022-08-11T20:14:53.833850 #10996] FATAL -- : ActionView::Template::Error (No such template: "date_type_Single"): F, [2022-08-11T20:14:53.834690 #10996] FATAL -- : 45: <% end %> When you try to Edit each record, and you cannot edit but simply get the dreaded: ?We're sorry, but something went wrong.? Based on the error message in the logs we see when we click ?Edit,? we believe that the Value field single was accidentally capitalized during the batch uploads in .csv files used for the uploads. So, it should have been lower case ?single? instead of ?Single? (we surmise). The first attached screenshot (I hope screenshots are allowed to be included with postings here) shows that we now have a couple of extra value columns now for date_type, with records separated into two groups for each of the erroneous Value fields (Single, and Inclusive which you can see are the last two rows under Controlled Value List: Date Type (date_type). The 2nd attached screenshot shows a sample of the column in the .csv used for the batch upload with the capitalized date_1_type fields. We are thinking to fix this, we probably need to merge ?Single? items with ?single? and ?Inclusive? items with ?inclusive? with lower case Values being the ones they get merged into and then deleting the corresponding capitalized Value instances. Does this make sense? If so, how can we clean this up? I am guessing we may need to edit the MySQL database directly? Or is there a better way through the GUI? With many other Controlled Value Lists there are three options (Suppress/Merge/Delete) in the GUI for each Value, but not so for date_type which only has ?Suppress? as an option. If we could Merge and then Delete we could probably clean this up in the GUI, but that doesn?t appear to be an option for us. We are presently running ArchivesSpace version 2.8.0 on Red Hat Enterprise Linux 7. Thank you in advance for any suggestions, Steve Giessler Professional Technologist WVU Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From shand at ap.org Wed Aug 24 07:22:50 2022 From: shand at ap.org (Hand, Sarit) Date: Wed, 24 Aug 2022 11:22:50 +0000 Subject: [Archivesspace_Users_Group] *NEW* 2022 The Integrations sub-team of the ArchivesSpace Technical Advisory Council (TAC) Integrations Survey now OPEN. Message-ID: Dear ArchivesSpace Users, Administrators and Developers, 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 [cid:image005.png at 01D8B652.2182E6B0] Sarit Hand Digital Archivist AP Corporate Archives 200 Liberty Street New York, NY 10281 T 212.621.7035 shand at ap.org ap.org [cid:image006.png at 01D8B652.2182E6B0] The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1500 and delete this email. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 1093 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 5548 bytes Desc: image006.png URL: From mladair at umich.edu Thu Aug 25 10:38:04 2022 From: mladair at umich.edu (Matthew Adair) Date: Thu, 25 Aug 2022 10:38:04 -0400 Subject: [Archivesspace_Users_Group] Updating top container barcode via API Message-ID: Hi folks - I've been trying to come up with a routine to update barcodes in top containers via the API but so far, no luck. The server keeps returning a "409 conflict" error. Anybody know what the minimum requirements for the JSON payload would be to update a container barcode? Or, perhaps more details on the 409 conflict error? Thanks, Matt ---- *Matt Adair* Archivist for Digital Imaging and Infrastructure Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734-647-3537 http://bentley.umich.edu @UmichBentley *The Bentley Historical Library acknowledges that coerced cessions of land by the Anishnaabeg and Wyandot made the University of Michigan possible, and we seek to reaffirm the ancestral and contemporary ties of these peoples to the lands where the University now stands.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Thu Aug 25 11:03:01 2022 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Thu, 25 Aug 2022 11:03:01 -0400 Subject: [Archivesspace_Users_Group] Updating top container barcode via API In-Reply-To: References: Message-ID: Those conflict errors might mean that you're adding a barcode that already exists, which is restricted at the database level so there's no way around it. The standard (or at least a common) approach for doing updates via the API is to first get the record you want to update, modify the JSON you get back (to add the barcode in your case), then send that updated JSON with your POST request. When I went through the process of adding top container barcodes, I opted to make the updates directly to the database because I found it to be easier to script. Doing it this way requires you to update the Solr index manually ? removing data/indexer_state/6_top_container.dat should do that (not sure if the '6' in that filename is consistent, but it will always end with top_container.dat). On Thu, Aug 25, 2022 at 10:38 AM Matthew Adair wrote: > Hi folks - > I've been trying to come up with a routine to update barcodes in top > containers via the API but so far, no luck. The server keeps returning a > "409 conflict" error. > > Anybody know what the minimum requirements for the JSON payload would be > to update a container barcode? Or, perhaps more details on the 409 > conflict error? > > Thanks, > Matt > > ---- > *Matt Adair* > Archivist for Digital Imaging and Infrastructure > > > Bentley Historical Library > 1150 Beal Avenue > Ann Arbor, Michigan 48109-2113 > 734-647-3537 > http://bentley.umich.edu > @UmichBentley > > *The Bentley Historical Library acknowledges that coerced cessions of land > by the Anishnaabeg and Wyandot made the University of Michigan possible, > and we seek to reaffirm the ancestral and contemporary ties of these > peoples to the lands where the University now stands.* > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From mladair at umich.edu Thu Aug 25 11:37:36 2022 From: mladair at umich.edu (Matthew Adair) Date: Thu, 25 Aug 2022 11:37:36 -0400 Subject: [Archivesspace_Users_Group] Updating top container barcode via API In-Reply-To: References: Message-ID: Thanks Trevor, It turns out I was overthinking the process. I was removing the read only fields (like long_display_string) and others that weren't necessarily being updated. I was assuming including those would cause an error. But, just using the original JSON payload and adding the barcode field did the trick. Matt ---- *Matt Adair* Archivist for Digital Imaging and Infrastructure Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734-647-3537 http://bentley.umich.edu @UmichBentley *The Bentley Historical Library acknowledges that coerced cessions of land by the Anishnaabeg and Wyandot made the University of Michigan possible, and we seek to reaffirm the ancestral and contemporary ties of these peoples to the lands where the University now stands.* On Thu, Aug 25, 2022 at 11:10 AM Trevor Thornton wrote: > Those conflict errors might mean that you're adding a barcode that already > exists, which is restricted at the database level so there's no way around > it. > > The standard (or at least a common) approach for doing updates via the API > is to first get the record you want to update, modify the JSON you get back > (to add the barcode in your case), then send that updated JSON with your > POST request. > > When I went through the process of adding top container barcodes, I opted > to make the updates directly to the database because I found it to be > easier to script. Doing it this way requires you to update the Solr index > manually ? removing data/indexer_state/6_top_container.dat should do that > (not sure if the '6' in that filename is consistent, but it will always end > with top_container.dat). > > On Thu, Aug 25, 2022 at 10:38 AM Matthew Adair wrote: > >> Hi folks - >> I've been trying to come up with a routine to update barcodes in top >> containers via the API but so far, no luck. The server keeps returning a >> "409 conflict" error. >> >> Anybody know what the minimum requirements for the JSON payload would be >> to update a container barcode? Or, perhaps more details on the 409 >> conflict error? >> >> Thanks, >> Matt >> >> ---- >> *Matt Adair* >> Archivist for Digital Imaging and Infrastructure >> >> >> Bentley Historical Library >> 1150 Beal Avenue >> Ann Arbor, Michigan 48109-2113 >> 734-647-3537 >> http://bentley.umich.edu >> @UmichBentley >> >> *The Bentley Historical Library acknowledges that coerced cessions of >> land by the Anishnaabeg and Wyandot made the University of Michigan >> possible, and we seek to reaffirm the ancestral and contemporary ties of >> these peoples to the lands where the University now stands.* >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > Trevor Thornton > Applications Developer, Digital Library Initiatives > North Carolina State University Libraries > _______________________________________________ > 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 kbreneman at ubalt.edu Thu Aug 25 13:20:21 2022 From: kbreneman at ubalt.edu (Kyle Breneman) Date: Thu, 25 Aug 2022 17:20:21 +0000 Subject: [Archivesspace_Users_Group] Holdings for Current Repository info does not display Message-ID: We've just switched over to ArchivesSpace 3.2.0, and we've noticed that the Holdings for Current Repository column does not populate when we try to add a location to a Top Container in the staff interface (attached). This is puzzling as we can see the Holdings for Current Repository information if we go to Browse>>Locations from the Browse drop-down menu in the staff interface. Any ideas for what could be causing this problem, where the Holdings for Current Repository information is not displaying? (I've tried re-indexing.) 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: Screen Shot 2022-08-23 at 2.37.52 PM.png Type: image/png Size: 313134 bytes Desc: Screen Shot 2022-08-23 at 2.37.52 PM.png URL: From daniel.cornwall at alaska.gov Thu Aug 25 18:41:08 2022 From: daniel.cornwall at alaska.gov (Cornwall, Daniel D (EED)) Date: Thu, 25 Aug 2022 22:41:08 +0000 Subject: [Archivesspace_Users_Group] Have you seen this before? - translation missing: en.search_results.four_part_id_contain In-Reply-To: References: Message-ID: Hi All, In our public interface we've noticed an odd error message that shows up only when we are searching by identifier: Search all record types where * translation missing: en.search_results.four_part_id_contain We don't see this on any other option and I didn't find this error message in support searches. We are running a hosted version of ArchivesSpace 3.2. I just wanted to see if we were alone in seeing this message before contacting support. - Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: From scheirw at newschool.edu Tue Aug 30 14:48:50 2022 From: scheirw at newschool.edu (Wendy Scheir) Date: Tue, 30 Aug 2022 14:48:50 -0400 Subject: [Archivesspace_Users_Group] Unable to delete agent? Message-ID: Hello, Can someone help us interpret this error message we're getting when trying to delete an agent? Record deletion failed: Java::JavaSql::SQLIntegrityConstraintViolationException: Cannot delete or update a parent row: a foreign key constraint fails (`archivesspace`.`user`, CONSTRAINT `user_ibfk_1` FOREIGN KEY (`agent_record_id`) REFERENCES `agent_person` (`id`)) 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 jcross at clemson.edu Tue Aug 30 15:36:03 2022 From: jcross at clemson.edu (James E. Cross) Date: Tue, 30 Aug 2022 19:36:03 +0000 Subject: [Archivesspace_Users_Group] Extent calculations in cubic feet Message-ID: If you changed your base measurement from linear to cubic feet in the config. file, what happens when you calculate extent? You are only providing one measurement (let us say width) for extent dimension, but it really should be using all three for cubic feet. And how would the stacking limit come into play? Thanks! Jim Cross James Edward Cross, C.A. CLEMSON UNIVERSITY Manuscripts Archivist Special Collections and Archives Clemson University Libraries Box 343001 Clemson, SC 29634-3001 Phone: (864) 656-5182 Website: http://library.clemson.edu/depts/specialcollections/ Pronouns: he/him/his Traditional Cherokee Lands | Site of Fort Hill Plantation Please do not feel obligated to respond to this message outside of your normal working hours. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jasteytler at minlib.net Tue Aug 30 15:43:32 2022 From: jasteytler at minlib.net (Jessica Steytler) Date: Tue, 30 Aug 2022 15:43:32 -0400 Subject: [Archivesspace_Users_Group] Extent calculations in cubic feet In-Reply-To: References: Message-ID: I was struggling with the cubic vs linear at my newer job-- that I'd been using cubic at the old place. I did the calculation and then put in the total with the cubic designation, which we set as the default. All this was BEFORE there was an extent calculator, so I do not have any data whatsoever with that tool in the mix. Then when I moved to a new place where I had to start from scratch for ASpace and was head-down planning on cubic... but have been waffling big time on it, as we don't have a huge collection and unlikely to have off-site storage, etc etc. But cubic vs linear's been a thing that's been on my radar. I'll be interested to see what conversation might pop on this. I just don't have any lived experience when it comes to extent calculator. Cheers! ----- Jessica Steytler | she/her Reference - Special Collections Public Library of Brookline 617-730-2375 http://brooklinelibrary.org From andrew.morrison at bodleian.ox.ac.uk Wed Aug 31 03:37:34 2022 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Wed, 31 Aug 2022 08:37:34 +0100 Subject: [Archivesspace_Users_Group] Unable to delete agent? In-Reply-To: References: Message-ID: That message means the agent you are trying to delete is also a user of the staff interface. The database is set up to prevent deletion of rows in the "agent_person" table if doing so would leave a dangling reference in the "user" table. To delete the user, and with it their associated agent record, go to System > Manage Users, find the user in the list (which might be tricky if their username is different to their real name), edit, and click Delete. Andrew. On 30/08/2022 19:48, Wendy Scheir wrote: > Hello, > Can someone help us interpret this error message we're getting when > trying to delete an agent? > Record deletion failed: Java::JavaSql::SQLIntegrityConstraintViolationException: Cannot delete or update a parent row: a foreign key constraint fails (`archivesspace`.`user`, CONSTRAINT `user_ibfk_1` FOREIGN KEY (`agent_record_id`) REFERENCES `agent_person` (`id`)) > > > 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 > > > _______________________________________________ > 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 lynn.moulton at bc.edu Wed Aug 31 12:53:50 2022 From: lynn.moulton at bc.edu (Lynn Moulton) Date: Wed, 31 Aug 2022 12:53:50 -0400 Subject: [Archivesspace_Users_Group] Extent calculations in cubic feet In-Reply-To: References: Message-ID: Hi James, If I'm understanding your question correctly, the following may be helpful. The ASpace extent calculator uses the container profiles as the basis for the calculation, and a complete profile includes width, depth, and height. So if you change your config from linear feet to cubic, the calculator should use all three dimensions that are included in the container profile. And the stacking limit won't come into play, because the calculator will use the actual box height. The stacking limit is for the space calculator, not the extent calculator. However, we're still using linear feet here, so I'm making an assumption about the config change also changing the extent calculation. Perhaps someone at a cubic feet organization could confirm. Best, Lynn Moulton Senior Processing Archivist John J. Burns Library Boston College On Tue, Aug 30, 2022 at 3:36 PM James E. Cross wrote: > If you changed your base measurement from linear to cubic feet in the > config. file, what happens when you calculate extent? You are only > providing one measurement (let us say width) for extent dimension, but it > really should be using all three for cubic feet. And how would the stacking > limit come into play? > > > > Thanks! > > > > Jim Cross > > > > > > *James Edward Cross, C.A.* CLEMSON UNIVERSITY > > Manuscripts Archivist > > Special Collections and Archives > > Clemson University Libraries > > Box 343001 > > Clemson, SC 29634-3001 > > Phone: (864) 656-5182 > > Website: http://library.clemson.edu/depts/specialcollections/ > > Pronouns: he/him/his > > Traditional Cherokee Lands | Site of Fort Hill Plantation > > *Please do not feel obligated to respond to this message outside of your > normal working hours.* > > > > > _______________________________________________ > 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 Jessica.Crouch at lyrasis.org Wed Aug 31 16:36:44 2022 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Wed, 31 Aug 2022 20:36:44 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - August 2022 In-Reply-To: References: Message-ID: [cid:image001.jpg at 01D8A330.1E6801C0] ArchivesSpace Update ? August 2022 Upcoming Schedule at a Glance: September 8: ArchivesSpace Member Match Mixer (open to Member Match participants only) Development The ArchivesSpace team is pleased to announce a release candidate, v3.3.0-RC2. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v3.3.0-RC2 or test it out without downloading at http://test.archivesspace.org/staff (username admin /password admin). This is an update to RC1 that addresses an issue found with one of the migrations. This release candidate includes many small bug fixes and feature enhancements. Of particular note are some enhancements to spawning from accessions and an option for logged in users to change their own passwords. As part of the spawning improvements, the plugin Hudson Molonglo developed for The New School Archives and Special Collections to link accessions to archival objects has been incorporated into the core code of ArchivesSpace. Please try this release candidate out and let us know at ArchivesSpaceHome at lyrasis.org by September 6 if you notice any problems with the specific areas addressed in this release, or if anything that was working before no longer is. Pending the results of this testing, we will aim to release the production version of 3.3.0 shortly afterwards. ArchivesSpace 8th Annual Member Forum Thank you to everyone who attended the 8th Annual ArchivesSpace Member Forum. Recordings from the August 24th in-person forum and August 30-31 virtual trainings will be available on the forum wiki in the coming days. In the meantime, there is a brief forum evaluation available at https://www.surveymonkey.com/r/PZMTVGS. Your feedback helps us learn what went well and what you?d like to see for the future. Thank you again to those who could be with us. We look forward to seeing you again soon! ArchivesSpace Member Match Mixer [posted on behalf of the Member Engagement sub-team] We hope all Member Match participants have had a chance to engage with your match/es, and have planned your first ?meeting? so that you can begin to determine when and how you?d like to stay in touch over the course of this Member Match year. The modes of interaction and frequency are entirely up to you as matches, so have fun and don?t be afraid to dive right in! The first Member Match event of the year will be a virtual mixer on September 8th from 1:00pm-2:00pm ET/10:00am-1:00pm PT. Title: Member Match Mixer - Sharing Tips & Tricks! Date: Thursday, September 8th Time: 1:00pm-2:00pm ET/10:00am-1:00pm PT For our quarterly Member Match events, we?ll focus on community interaction among all Member Match participants, but there is no reason why you can?t use these topics to spur further discussion with your match/es. We?re going to kick things off at this Mixer with an informal discussion of some of your favorite tips and tricks to use with ArchivesSpace. Please come prepared with your top 1-3 favorite tips/tricks ? these can relate to any module in ArchivesSpace and/or related tools and technologies that you think others should know about. To register for this upcoming Member Match Mixer, review the post sent to the Member Match listserv. If you have any questions or concerns ? especially if you?ve had trouble connecting with any of your match/es ? please don?t hesitate to reach out to the Member Engagement Sub-team at ArchivesSpaceHome at lyrasis.org. We hope to see you at the Mixer! 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 July 31 include: * Alice Austen House, (Staten Island, NY) * Bowling Green State University, (Bowling Green, OH) * Scottish Rite Masonic Museum and Library, (Lexington, MA) * Shaw University, (Raleigh, NC) As of August 31, we have 468 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: