From Joshua.D.Shaw at dartmouth.edu Tue Jan 5 09:41:56 2021 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Tue, 5 Jan 2021 14:41:56 +0000 Subject: [Archivesspace_Users_Group] Indexer Thread Counts Message-ID: Hey all- Couple of questions about indexer thread counts 1) Before I dive too deeply into the code to figure this out, I'm wondering if anyone knows if the setting for AppConfig[:pui_indexer_thread_count] is counted as part of AppConfig[:indexer_thread_count] or if its additive? IE if the stock config setting amounts to 5 threads (4+1) or 4 threads. 2) Is there a reason that the PUI indexer thread count is set so much lower than the staff side? I'm thinking of upping the PUI thread count to something closer to the staff side since we have the cores to support that, but I'm wondering if there might be some unforeseen negative side effects. Thanks! Joshua ___________________ Joshua Shaw (he, him) Technology Coordinator Rauner Special Collections Library & Digital Library Technologies Group Dartmouth College 603.646.0405 -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at hudmol.com Tue Jan 5 17:19:24 2021 From: james at hudmol.com (James Bullen) Date: Wed, 6 Jan 2021 09:19:24 +1100 Subject: [Archivesspace_Users_Group] Indexer Thread Counts In-Reply-To: References: Message-ID: <42E14B6B-A471-45DE-9DC1-285532D25188@hudmol.com> Hi Joshua, 1) Yes, additive 2) The public index was considered less time critical There?s no problem with increasing the PUI indexer thread count if you have the resources. Cheers, James > On Jan 6, 2021, at 1:41 AM, Joshua D. Shaw wrote: > > Hey all- > > Couple of questions about indexer thread counts > > 1) Before I dive too deeply into the code to figure this out, I'm wondering if anyone knows if the setting for AppConfig[:pui_indexer_thread_count] is counted as part of AppConfig[:indexer_thread_count] or if its additive? IE if the stock config setting amounts to 5 threads (4+1) or 4 threads. > > 2) Is there a reason that the PUI indexer thread count is set so much lower than the staff side? > > I'm thinking of upping the PUI thread count to something closer to the staff side since we have the cores to support that, but I'm wondering if there might be some unforeseen negative side effects. > > Thanks! > Joshua > > ___________________ > Joshua Shaw (he, him) > Technology Coordinator > Rauner Special Collections Library & Digital Library Technologies Group > Dartmouth College > 603.646.0405 > _______________________________________________ > 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 Joshua.D.Shaw at dartmouth.edu Tue Jan 5 17:43:00 2021 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Tue, 5 Jan 2021 22:43:00 +0000 Subject: [Archivesspace_Users_Group] Indexer Thread Counts In-Reply-To: <42E14B6B-A471-45DE-9DC1-285532D25188@hudmol.com> References: , <42E14B6B-A471-45DE-9DC1-285532D25188@hudmol.com> Message-ID: Thanks, James! jds ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of James Bullen Sent: Tuesday, January 5, 2021 5:19 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Indexer Thread Counts Hi Joshua, 1) Yes, additive 2) The public index was considered less time critical There?s no problem with increasing the PUI indexer thread count if you have the resources. Cheers, James On Jan 6, 2021, at 1:41 AM, Joshua D. Shaw > wrote: Hey all- Couple of questions about indexer thread counts 1) Before I dive too deeply into the code to figure this out, I'm wondering if anyone knows if the setting for AppConfig[:pui_indexer_thread_count] is counted as part of AppConfig[:indexer_thread_count] or if its additive? IE if the stock config setting amounts to 5 threads (4+1) or 4 threads. 2) Is there a reason that the PUI indexer thread count is set so much lower than the staff side? I'm thinking of upping the PUI thread count to something closer to the staff side since we have the cores to support that, but I'm wondering if there might be some unforeseen negative side effects. Thanks! Joshua ___________________ Joshua Shaw (he, him) Technology Coordinator Rauner Special Collections Library & Digital Library Technologies Group Dartmouth College 603.646.0405 _______________________________________________ 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 Jan 6 11:14:39 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Wed, 6 Jan 2021 16:14:39 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: An Introduction to ArchivesSpace v3.0 and the Expanded Agents Module In-Reply-To: References: Message-ID: <8962E6C9-741A-4B6D-AFCB-B28BD90FA310@lyrasis.org> Dear ArchivesSpace Users, ArchivesSpace will be offering a webinar focusing on the upcoming ArchivesSpace v3.0 release and the expanded agent module functionality that is the exclusive focus of this update. While the required fields to create a valid agent record will remain minimal, the expanded agents functionality will allow for greater compliance with metadata standards used to describe persons, families, and corporate entities like MARCXML authority and EAC-CPF, facilitate better exchange with databases like LCNAF and SNAC and support better contextualization of agents by providing more ways to apply controlled access headings or information about the agent and their relationships. When: January 13, 2020 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_Esz2CPatRWmDlRNqMeWlIA In order to provide a secure webinar experience and ensure adequate space in our Zoom environment, registration is now required for our webinars. Our webinars continue to be free and open to anyone using or interested in ArchivesSpace. This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Webinar description: In this webinar, ArchivesSpace community members will provide background information and context on the necessity of the new agents functionality made available in ArchivesSpace v3.0. They will also discuss the benefits of the expanded agents module and why an institution may want to implement the new fields and sub-records. After, ArchivesSpace Program Manager, Christine Di Bella will provide a demo of the new agents module with a Q&A to follow. Who should attend: Anyone currently using or considering using the ArchivesSpace agents module, those looking to better integrate ArchivesSpace with SNAC and LCNAF and those looking to better comply with metadata standards used to describe agents. 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: 29062 bytes Desc: image001.jpg URL: From Kim.Pham60 at du.edu Wed Jan 6 14:53:46 2021 From: Kim.Pham60 at du.edu (Kim Pham) Date: Wed, 6 Jan 2021 19:53:46 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 2.8.1 Edit Default Values In-Reply-To: References: , Message-ID: Hi Andrew - Ahh, it looks like that's what I needed to do, it works now. Thanks a lot! Kim Pham Information Technologies Librarian, University of Denver 303-871-2285 @tolloid ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Andrew Morrison Sent: Wednesday, December 30, 2020 03:49 To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] ArchivesSpace 2.8.1 Edit Default Values Is "Pre-populate Records?" checked in your own user preferences? User preferences take precedence over repository preferences, and both take precedence over global preferences. Initially your user preferences are unset, so a checkbox like "Pre-populate Records?" will appear unticked, but if it is enabled in repository or global preferences then it will work. However, if you edit your user preferences, for example to change the columns in a list view, when you click save that unticked checkbox means the feature will be disabled, for you, from that point on. I do not think there is any way to return a user account to its initial state except by deleting a row in the MySQL database. It would be better if single checkboxes were replaced with three radio buttons labeled something like "Yes", "No", and "Use repository/global setting". Better yet, if admins could lock them into the last of those three, preventing users from changing them, then you could enforce policies like always user default values. But I suspect that would require a lot of work to implement and test. Another thing to look out for is that default values are set up on a per-repository basis. So you can have "Pre-populate Records?" enabled in global preferences, but it will only actually work globally if all the repositories in your system have been set up with default values. Andrew. On 22/12/2020 16:23, Kim Pham wrote: Hello, I'm having trouble with the edit default values feature in 2.8.1. I'm trying it with Resource records, and it works in our current 2.7.0 version, but it is not working in the 2.8.1 version that we want to launch. I enabled Pre-populate in the global and repository preferences but our values still don't show up. I also tried the online sandbox http://sandbox.archivesspace.org/. Is anyone else experiencing issues with this feature? Thanks, Kim Pham Information Technologies Librarian, University of Denver 303-871-2285 @tolloid _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Thu Jan 7 07:32:54 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Thu, 7 Jan 2021 12:32:54 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 2.8.1 Edit Default Values In-Reply-To: References: Message-ID: <75d27c29-3657-333d-1f66-dc6e640e4c73@bodleian.ox.ac.uk> I have created a ticket to propose improvements to checkboxes in preferences: https://archivesspace.atlassian.net/browse/ANW-1172 Andrew. On 06/01/2021 19:53, Kim Pham wrote: > Hi Andrew - Ahh, it looks like that's what I needed to do, it works > now. Thanks a lot! > > Kim Pham > Information Technologies Librarian, University of Denver > 303-871-2285 > @tolloid > ------------------------------------------------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Andrew Morrison > *Sent:* Wednesday, December 30, 2020 03:49 > *To:* archivesspace_users_group at lyralists.lyrasis.org > > *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace 2.8.1 Edit > Default Values > > Is "Pre-populate Records?" checked in your own user preferences? User > preferences take precedence over repository preferences, and both take > precedence over global preferences. Initially your user preferences > are unset, so a checkbox like "Pre-populate Records?" will appear > unticked, but if it is enabled in repository or global preferences > then it will work. However, if you edit your user preferences, for > example to change the columns in a list view, when you click save that > unticked checkbox means the feature will be disabled, for you, from > that point on. > > > I do not think there is any way to return a user account to its > initial state except by deleting a row in the MySQL database. It would > be better if single checkboxes were replaced with three radio buttons > labeled something like "Yes", "No", and "Use repository/global > setting". Better yet, if admins could lock them into the last of those > three, preventing users from changing them, then you could enforce > policies like always user default values. But I suspect that would > require a lot of work to implement and test. > > > Another thing to look out for is that default values are set up on a > per-repository basis. So you can have "Pre-populate Records?" enabled > in global preferences, but it will only actually work globally if all > the repositories in your system have been set up with default values. > > > Andrew. > > > > > On 22/12/2020 16:23, Kim Pham wrote: >> Hello, >> >> I'm having trouble with the edit default values feature in 2.8.1. I'm >> trying it with Resource records, and it works in our current 2.7.0 >> version, but it is not working in the 2.8.1 version that we want to >> launch. I enabled Pre-populate in the global and repository >> preferences but our values still don't show up. I also tried the >> online sandbox http://sandbox.archivesspace.org/ >> . >> Is anyone else experiencing issues with this feature? Thanks, >> >> Kim Pham >> Information Technologies Librarian, University of Denver >> 303-871-2285 >> @tolloid >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From pshowell at anderson.edu Fri Jan 8 14:37:55 2021 From: pshowell at anderson.edu (Preston Howell) Date: Fri, 8 Jan 2021 14:37:55 -0500 Subject: [Archivesspace_Users_Group] Issues Upgrading Message-ID: Good afternoon all I have spent some time over the last couple of days updating software on our server running our instance of ArchivesSpace, including updating from 2.7.1 to 2.8.1. The server is currently running Ubuntu 20.04. I didn't realize that this update would mean Java 11 would be installed as default. I've now changed it to Java 8, but am unable to get ASpace to start. Attached is a screenshot of my log file. I'm kinda stumped at this point. Any help would be appreciated. Thanks in advance. [image: Screen Shot 2021-01-08 at 2.33.30 PM.png] -- Preston Howell | Library Technology Specialist | Nicholson Library Anderson University | 1100 E. 5th St., Anderson, IN 46012 (765) 641-4270 | anderson.edu Confidentiality Notice: Because email is not a secure medium, confidentiality of email cannot be guaranteed. This message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution, or copying is prohibited. If you are not the intended recipient, please contact the sender by replying to this email and destroy/delete all copies of this email message. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2021-01-08 at 2.33.30 PM.png Type: image/png Size: 50272 bytes Desc: not available URL: From blake.carver at lyrasis.org Fri Jan 8 14:55:21 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 8 Jan 2021 19:55:21 +0000 Subject: [Archivesspace_Users_Group] Issues Upgrading In-Reply-To: References: Message-ID: That part of the log isn't super helpful. I'd guess the real error is above that someplace. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Preston Howell Sent: Friday, January 8, 2021 2:37 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Issues Upgrading Good afternoon all I have spent some time over the last couple of days updating software on our server running our instance of ArchivesSpace, including updating from 2.7.1 to 2.8.1. The server is currently running Ubuntu 20.04. I didn't realize that this update would mean Java 11 would be installed as default. I've now changed it to Java 8, but am unable to get ASpace to start. Attached is a screenshot of my log file. I'm kinda stumped at this point. Any help would be appreciated. Thanks in advance. [Screen Shot 2021-01-08 at 2.33.30 PM.png] -- [https://lh6.googleusercontent.com/gy91ZxMadyMT9F5z4RB8Jq9gwC66YtvxoxTTXMHZvO5v5Y3cEFgymICQ-xTQCrF3oG2m-DS3Fy6CClg-IuPeMYnffW5KaWy-d59DPcuN-UvmhprdIzBte6aS6nD8PJH3gI_w38AD] Preston Howell | Library Technology Specialist | Nicholson Library Anderson University | 1100 E. 5th St., Anderson, IN 46012 (765) 641-4270 | anderson.edu Confidentiality Notice: Because email is not a secure medium, confidentiality of email cannot be guaranteed. This message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution, or copying is prohibited. If you are not the intended recipient, please contact the sender by replying to this email and destroy/delete all copies of this email message. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2021-01-08 at 2.33.30 PM.png Type: image/png Size: 50272 bytes Desc: Screen Shot 2021-01-08 at 2.33.30 PM.png URL: From pshowell at anderson.edu Fri Jan 8 15:06:36 2021 From: pshowell at anderson.edu (Preston Howell) Date: Fri, 8 Jan 2021 15:06:36 -0500 Subject: [Archivesspace_Users_Group] Issues Upgrading In-Reply-To: References: Message-ID: That is the entirety of the log file On Fri, Jan 8, 2021 at 2:55 PM Blake Carver wrote: > That part of the log isn't super helpful. I'd guess the real error is > above that someplace. > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Preston Howell > *Sent:* Friday, January 8, 2021 2:37 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Issues Upgrading > > Good afternoon all > > I have spent some time over the last couple of days updating software on > our server running our instance of ArchivesSpace, including updating from > 2.7.1 to 2.8.1. The server is currently running Ubuntu 20.04. I didn't > realize that this update would mean Java 11 would be installed as default. > I've now changed it to Java 8, but am unable to get ASpace to start. > Attached is a screenshot of my log file. I'm kinda stumped at this point. > Any help would be appreciated. > > Thanks in advance. > > [image: Screen Shot 2021-01-08 at 2.33.30 PM.png] > > -- > > Preston Howell | Library Technology Specialist | Nicholson Library > Anderson University | 1100 E. 5th St., Anderson, IN 46012 > (765) 641-4270 | anderson.edu > > Confidentiality Notice: Because email is not a secure medium, > confidentiality of email cannot be guaranteed. This message is for the > sole use of the intended recipient(s) and may contain confidential and > privileged information. Any unauthorized review, use, disclosure, > distribution, or copying is prohibited. If you are not the intended > recipient, please contact the sender by replying to this email and > destroy/delete all copies of this email message. > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Preston Howell | Library Technology Specialist | Nicholson Library Anderson University | 1100 E. 5th St., Anderson, IN 46012 (765) 641-4270 | anderson.edu Confidentiality Notice: Because email is not a secure medium, confidentiality of email cannot be guaranteed. This message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution, or copying is prohibited. If you are not the intended recipient, please contact the sender by replying to this email and destroy/delete all copies of this email message. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2021-01-08 at 2.33.30 PM.png Type: image/png Size: 50272 bytes Desc: not available URL: From benn.joseph at northwestern.edu Fri Jan 8 15:24:24 2021 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Fri, 8 Jan 2021 20:24:24 +0000 Subject: [Archivesspace_Users_Group] PUI infinite scroll bugginess Message-ID: Hi everyone, For the PUI, I don't know if scrolling within the main Collection Organization area has always been this clunky, but we've been struggling with it lately and have heard some complaints from staff and researchers about viewing content in this section. The problem we see is that trying to scroll through content in the infinite scroll area under Collection Organization results in the entire browser page scrolling up and down with it; this is exacerbated when using Firefox, where the content in the infinite scroll area also scrolls very slowly when using a mouse wheel (using a trackpad results in a more predictable scrolling speed within the main Collection Organization area, but you still have to deal with the entire page scrolling up and down at the same time). There are a lot of tickets that relate to scrolling in Collection Organization, and I've read through the Usability Sub-team 2020 Collection Organization View recommendations too (ANW-1118) but can't find anything that specifically addresses this issue. Is this normal, and I just didn't notice it before?? Thanks, --Benn Benn Joseph Head, Collections Services McCormick Library of Special Collections & University Archives Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kim.Pham60 at du.edu Fri Jan 8 16:53:35 2021 From: Kim.Pham60 at du.edu (Kim Pham) Date: Fri, 8 Jan 2021 21:53:35 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Upgrade and Testing Templates Message-ID: Hi All, We recently went through an upgrade from ArchivesSpace 2.7.0 to 2.8.1. I wanted to share a version of our process documentation + testing templates, in case someone might find this useful in the future. It definitely helped us make the upgrade process very easy. Please feel free to ask questions or send me your comments. Thanks! ArchivesSpace Upgrade Documentation: https://docs.google.com/document/d/1rjQWS7JhAyRFouNdeqsPZ2RIB8ShIODA3NxS-pVdj6Q ArchivesSpace Testing Process: https://docs.google.com/spreadsheets/d/1X2qVZKKkxrj5iVJwFBF-K256g9d7qe4IYcC49s9Dqc4 Kim Pham Information Technologies Librarian, University of Denver 303-871-2285 @tolloid -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kim.Pham60 at du.edu Sat Jan 9 18:28:52 2021 From: Kim.Pham60 at du.edu (Kim Pham) Date: Sat, 9 Jan 2021 23:28:52 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 2.8.1 Edit Default Values In-Reply-To: <75d27c29-3657-333d-1f66-dc6e640e4c73@bodleian.ox.ac.uk> References: , <75d27c29-3657-333d-1f66-dc6e640e4c73@bodleian.ox.ac.uk> Message-ID: <47ab9604-5a0e-4539-8054-bc8c6aa26d5a@email.android.com> Great idea thank you On Jan. 7, 2021 05:33, Andrew Morrison wrote: I have created a ticket to propose improvements to checkboxes in preferences: https://archivesspace.atlassian.net/browse/ANW-1172 Andrew. On 06/01/2021 19:53, Kim Pham wrote: Hi Andrew - Ahh, it looks like that's what I needed to do, it works now. Thanks a lot! Kim Pham Information Technologies Librarian, University of Denver 303-871-2285 @tolloid ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Andrew Morrison Sent: Wednesday, December 30, 2020 03:49 To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] ArchivesSpace 2.8.1 Edit Default Values Is "Pre-populate Records?" checked in your own user preferences? User preferences take precedence over repository preferences, and both take precedence over global preferences. Initially your user preferences are unset, so a checkbox like "Pre-populate Records?" will appear unticked, but if it is enabled in repository or global preferences then it will work. However, if you edit your user preferences, for example to change the columns in a list view, when you click save that unticked checkbox means the feature will be disabled, for you, from that point on. I do not think there is any way to return a user account to its initial state except by deleting a row in the MySQL database. It would be better if single checkboxes were replaced with three radio buttons labeled something like "Yes", "No", and "Use repository/global setting". Better yet, if admins could lock them into the last of those three, preventing users from changing them, then you could enforce policies like always user default values. But I suspect that would require a lot of work to implement and test. Another thing to look out for is that default values are set up on a per-repository basis. So you can have "Pre-populate Records?" enabled in global preferences, but it will only actually work globally if all the repositories in your system have been set up with default values. Andrew. On 22/12/2020 16:23, Kim Pham wrote: Hello, I'm having trouble with the edit default values feature in 2.8.1. I'm trying it with Resource records, and it works in our current 2.7.0 version, but it is not working in the 2.8.1 version that we want to launch. I enabled Pre-populate in the global and repository preferences but our values still don't show up. I also tried the online sandbox http://sandbox.archivesspace.org/. Is anyone else experiencing issues with this feature? Thanks, Kim Pham Information Technologies Librarian, University of Denver 303-871-2285 @tolloid _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmichelson at smith.edu Mon Jan 11 07:02:18 2021 From: dmichelson at smith.edu (Daniel Michelson) Date: Mon, 11 Jan 2021 07:02:18 -0500 Subject: [Archivesspace_Users_Group] PUI infinite scroll bugginess In-Reply-To: References: Message-ID: Hi Benn, This problem has been in ArchivesSpace (at least for Firefox) since I started using the application in 2017. Some related tickets have been approved by Dev/Pri, but are still pending implementation: - https://archivesspace.atlassian.net/browse/ANW-425 - https://archivesspace.atlassian.net/browse/ANW-276 - https://archivesspace.atlassian.net/browse/ANW-306 Personally, I think the Collection Organization feature is one of the weakest parts of the PUI. Since it is also the closest to the traditional *EAD Cookbook* style finding aid that many repositories previously used, I suspect that a lot of the folks with negative opinions of the PUI are put off by it. All the best, Dan On Fri, Jan 8, 2021 at 3:24 PM Benn Joseph wrote: > Hi everyone, > > For the PUI, I don?t know if scrolling within the main Collection > Organization area has always been this clunky, but we?ve been struggling > with it lately and have heard some complaints from staff and researchers > about viewing content in this section. > > > > The problem we see is that trying to scroll through content in the > infinite scroll area under Collection Organization results in the entire > browser page scrolling up and down with it; this is exacerbated when using > Firefox, where the content in the infinite scroll area also scrolls *very > slowly *when using a mouse wheel (using a trackpad results in a more > predictable scrolling speed within the main Collection Organization area, > but you still have to deal with the entire page scrolling up and down at > the same time). > > > > There are a lot of tickets that relate to scrolling in Collection > Organization, and I?ve read through the Usability Sub-team 2020 Collection > Organization View recommendations too (ANW-1118) but can?t find anything > that specifically addresses this issue. Is this normal, and I just didn?t > notice it before?? > > > > Thanks, > > --Benn > > > > *Benn Joseph* > > Head, Collections Services > > McCormick Library of Special Collections & University Archives > > Northwestern University Libraries > > Northwestern University > > www.library.northwestern.edu > > benn.joseph at northwestern.edu > > 847.467.6581 > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Dan Michelson Project Manager Archivist Smith College Special Collections Due to COVID-19, Special Collections is offering limited, remote reference and digitization services and ongoing consultations for faculty, students, and other researchers. Smith course support is our primary responsibility at this time. All other requests and inquiries will be responded to as we are able. For information about Smith College?s response to Covid-19, please visit the Smith College Libraries and Smith College websites. For information about library services during this time, information is available on our website. -------------- next part -------------- An HTML attachment was scrubbed... URL: From benn.joseph at northwestern.edu Mon Jan 11 15:08:58 2021 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Mon, 11 Jan 2021 20:08:58 +0000 Subject: [Archivesspace_Users_Group] PUI infinite scroll bugginess In-Reply-To: References: Message-ID: Thanks Dan; I will keep an eye on those tickets for now. --Benn From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Daniel Michelson Sent: Monday, January 11, 2021 6:02 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] PUI infinite scroll bugginess Hi Benn, This problem has been in ArchivesSpace (at least for Firefox) since I started using the application in 2017. Some related tickets have been approved by Dev/Pri, but are still pending implementation: * https://archivesspace.atlassian.net/browse/ANW-425 * https://archivesspace.atlassian.net/browse/ANW-276 * https://archivesspace.atlassian.net/browse/ANW-306 Personally, I think the Collection Organization feature is one of the weakest parts of the PUI. Since it is also the closest to the traditional EAD Cookbook style finding aid that many repositories previously used, I suspect that a lot of the folks with negative opinions of the PUI are put off by it. All the best, Dan On Fri, Jan 8, 2021 at 3:24 PM Benn Joseph > wrote: Hi everyone, For the PUI, I don?t know if scrolling within the main Collection Organization area has always been this clunky, but we?ve been struggling with it lately and have heard some complaints from staff and researchers about viewing content in this section. The problem we see is that trying to scroll through content in the infinite scroll area under Collection Organization results in the entire browser page scrolling up and down with it; this is exacerbated when using Firefox, where the content in the infinite scroll area also scrolls very slowly when using a mouse wheel (using a trackpad results in a more predictable scrolling speed within the main Collection Organization area, but you still have to deal with the entire page scrolling up and down at the same time). There are a lot of tickets that relate to scrolling in Collection Organization, and I?ve read through the Usability Sub-team 2020 Collection Organization View recommendations too (ANW-1118) but can?t find anything that specifically addresses this issue. Is this normal, and I just didn?t notice it before?? Thanks, --Benn Benn Joseph Head, Collections Services McCormick Library of Special Collections & University Archives Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Dan Michelson Project Manager Archivist Smith College Special Collections Due to COVID-19, Special Collections is offering limited, remote reference and digitization services and ongoing consultations for faculty, students, and other researchers. Smith course support is our primary responsibility at this time. All other requests and inquiries will be responded to as we are able. For information about Smith College?s response to Covid-19, please visit the Smith College Libraries and Smith College websites. For information about library services during this time, information is available on our website. -------------- next part -------------- An HTML attachment was scrubbed... URL: From akroeger at unomaha.edu Tue Jan 12 10:44:15 2021 From: akroeger at unomaha.edu (Angela Kroeger) Date: Tue, 12 Jan 2021 15:44:15 +0000 Subject: [Archivesspace_Users_Group] Unable to view suppressed records Message-ID: As admin, I am able to view suppressed records. When I search the repository, suppressed records appear in the search results with a prominent "suppressed" flag ahead of the title. However, for users who are not admins, there doesn't seem to be any way for them to view suppressed records, even when they are assigned to a group that has "view suppressed records in this repository" checked in the permission list. For example, someone in the Manager group is unable to view the resource record they themself just suppressed. I have confirmed that the Manager permission includes both "suppress the major record types in this repository" and "view suppressed records in this repository." And I have confirmed that the user in indeed in the Manager group. They should be able to view suppressed records, but testing both search and browse for known suppressed resource records confirms that these records are not visible to them. What am I missing? What else do I need to do to allow Managers to actually view suppressed records? Thank you! 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:5e6a7e54-2a0e-4175-8db5-1da43e431d01] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-yrkz3ocx.png Type: image/png Size: 5582 bytes Desc: Outlook-yrkz3ocx.png URL: From dmichelson at smith.edu Tue Jan 12 10:56:35 2021 From: dmichelson at smith.edu (Daniel Michelson) Date: Tue, 12 Jan 2021 10:56:35 -0500 Subject: [Archivesspace_Users_Group] Unable to view suppressed records In-Reply-To: References: Message-ID: Hi Angela, There are actually two requirements for viewing suppressed records. First is the user permissions, but in addition, the first setting in user preferences ("Show Suppressed?") must be checked. Hope that helps. All the best, Dan On Tue, Jan 12, 2021 at 10:44 AM Angela Kroeger wrote: > As admin, I am able to view suppressed records. When I search the > repository, suppressed records appear in the search results with a > prominent "suppressed" flag ahead of the title. > > However, for users who are not admins, there doesn't seem to be any way > for them to view suppressed records, even when they are assigned to a group > that has "view suppressed records in this repository" checked in the > permission list. > > For example, someone in the Manager group is unable to view the resource > record they themself just suppressed. I have confirmed that the Manager > permission includes both "suppress the major record types in this > repository" and "view suppressed records in this repository." And I have > confirmed that the user in indeed in the Manager group. They should be able > to view suppressed records, but testing both search and browse for known > suppressed resource records confirms that these records are not visible to > them. > > What am I missing? What else do I need to do to allow Managers to actually > view suppressed records? > > Thank you! > > *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 > -- Dan Michelson Project Manager Archivist Smith College Special Collections Due to COVID-19, Special Collections is offering limited, remote reference and digitization services and ongoing consultations for faculty, students, and other researchers. Smith course support is our primary responsibility at this time. All other requests and inquiries will be responded to as we are able. For information about Smith College?s response to Covid-19, please visit the Smith College Libraries and Smith College websites. For information about library services during this time, information is available on our website. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-yrkz3ocx.png Type: image/png Size: 5582 bytes Desc: not available URL: From akroeger at unomaha.edu Tue Jan 12 11:20:02 2021 From: akroeger at unomaha.edu (Angela Kroeger) Date: Tue, 12 Jan 2021 16:20:02 +0000 Subject: [Archivesspace_Users_Group] Unable to view suppressed records In-Reply-To: References: , Message-ID: Thank you, Dan! This is exactly what I needed. I'll inform the affected users that they need to edit their preferences. --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:53e5ab63-5fa9-4ac6-9f11-d689a27ff4b0] ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Daniel Michelson Sent: Tuesday, January 12, 2021 9:56 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Unable to view suppressed records Non-NU Email ________________________________ Hi Angela, There are actually two requirements for viewing suppressed records. First is the user permissions, but in addition, the first setting in user preferences ("Show Suppressed?") must be checked. Hope that helps. All the best, Dan On Tue, Jan 12, 2021 at 10:44 AM Angela Kroeger > wrote: As admin, I am able to view suppressed records. When I search the repository, suppressed records appear in the search results with a prominent "suppressed" flag ahead of the title. However, for users who are not admins, there doesn't seem to be any way for them to view suppressed records, even when they are assigned to a group that has "view suppressed records in this repository" checked in the permission list. For example, someone in the Manager group is unable to view the resource record they themself just suppressed. I have confirmed that the Manager permission includes both "suppress the major record types in this repository" and "view suppressed records in this repository." And I have confirmed that the user in indeed in the Manager group. They should be able to view suppressed records, but testing both search and browse for known suppressed resource records confirms that these records are not visible to them. What am I missing? What else do I need to do to allow Managers to actually view suppressed records? Thank you! 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:176f74c019bb2209c141] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Dan Michelson Project Manager Archivist Smith College Special Collections Due to COVID-19, Special Collections is offering limited, remote reference and digitization services and ongoing consultations for faculty, students, and other researchers. Smith course support is our primary responsibility at this time. All other requests and inquiries will be responded to as we are able. For information about Smith College?s response to Covid-19, please visit the Smith College Libraries and Smith College websites. For information about library services during this time, information is available on our website. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-yrkz3ocx.png Type: image/png Size: 5582 bytes Desc: Outlook-yrkz3ocx.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Outlook-zggvr0bj.png Type: image/png Size: 5582 bytes Desc: Outlook-zggvr0bj.png URL: From bsutherland at mitre.org Tue Jan 12 11:40:54 2021 From: bsutherland at mitre.org (Bryan W Sutherland) Date: Tue, 12 Jan 2021 16:40:54 +0000 Subject: [Archivesspace_Users_Group] Item Spawn Message-ID: Does anyone know of a way to spawn items within a resource? I'm adding items to an existing resource which include a lot of repetitive information, so I'm trying to speed up the data entry. Any information would be greatly appreciated. Thanks! Bryan Sutherland Collections Management Archivist The MITRE Corporation Bedford, MA 781-271-8941 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Tue Jan 12 12:54:50 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 12 Jan 2021 17:54:50 +0000 Subject: [Archivesspace_Users_Group] Webinar Reminder: An Introduction to ArchivesSpace v3.0 and the Expanded Agents Module Message-ID: Dear ArchivesSpace Users, ArchivesSpace will be offering a webinar this Wednesday, January 13th, at 2:00pm ET focusing on the upcoming ArchivesSpace v3.0 release and the expanded agent module functionality that is the exclusive focus of this update. While the required fields to create a valid agent record will remain minimal, the expanded agents functionality will allow for greater compliance with metadata standards used to describe persons, families, and corporate entities like MARCXML authority and EAC-CPF, facilitate better exchange with databases like LCNAF and SNAC and support better contextualization of agents by providing more ways to apply controlled access headings or information about the agent and their relationships. When: January 13, 2020 Time: 2:00pm ? 3:00pm ET (11:00am ? 12:00pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_Esz2CPatRWmDlRNqMeWlIA In order to provide a secure webinar experience and ensure adequate space in our Zoom environment, registration is now required for our webinars. Our webinars continue to be free and open to anyone using or interested in ArchivesSpace. This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Webinar description: In this webinar, ArchivesSpace community members will provide background information and context on the necessity of the new agents functionality made available in ArchivesSpace v3.0. They will also discuss the benefits of the expanded agents module and why an institution may want to implement the new fields and sub-records. After, ArchivesSpace Program Manager, Christine Di Bella will provide a demo of the new agents module with a Q&A to follow. Who should attend: Anyone currently using or considering using the ArchivesSpace agents module, those looking to better integrate ArchivesSpace with SNAC and LCNAF and those looking to better comply with metadata standards used to describe agents. 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: 29063 bytes Desc: image001.jpg URL: From philip.webster at sheffield.ac.uk Wed Jan 13 07:56:32 2021 From: philip.webster at sheffield.ac.uk (philip.webster at sheffield.ac.uk) Date: Wed, 13 Jan 2021 12:56:32 -0000 Subject: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1) Message-ID: <005c01d6e9ab$84fa3d80$8eeeb880$@sheffield.ac.uk> Hi, We're currently in the process of deploying ArchivesSpace 2.8.1 to our production server following a lengthy period of testing and development on some other servers. Strangely, the public user interface is failing to load due to a Ruby dependency not being pulled in when the service starts up. The dependency is SASSC, which is present in the gems folder within the ArchivesSpace 2.8.1 installation. An error message appears in the logs suggesting that SASSC isn't being imported due to it not having native extensions built, and in turn that causes a 500 error to be visible in the browser together with a stack trace showing the root cause to be the missing library. I tried building the extension using the native Ruby tools in our Linux distribution and found that had no effect. After some lengthy investigation it turned out that the development and test servers do not even have the native Ruby packages installed, and that everything runs entirely through jRuby. That being the case, I have no idea how to solve the issue with this dependency. None of this is mentioned in the documentation, so I'm at a loss as to what to do next. Does anyone have any suggestions? Thanks, Philip Webster The University of Sheffield -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsharp at hplct.org Wed Jan 13 10:39:27 2021 From: jsharp at hplct.org (Sharp, Jennifer) Date: Wed, 13 Jan 2021 15:39:27 +0000 Subject: [Archivesspace_Users_Group] Language notes Message-ID: Hi, I have a question regarding the language notes. We recently upgraded from 2.6 to 2.8.1, and I learned afterward about the language note changes that came with 2.7. We are in the process of doing some heavy editing to the finding aid for our largest collection, and it looks like every time we edit one of the Archival Objects, it automatically adds the language information. I've tried a few things, and haven't been able to get rid of it. Would either of the batch_update_langmaterials plugins help with this? I found that a similar question was asked in December 2019, but there don't seem to be any group replies. Thanks, Jennifer --- Jennifer Sharp, MSI Archivist, Hartford History Center Hartford Public Library jsharp at hplct.org o: 860.695.6332 c: 860.929.6915 VIEW OUR EXHIBIT: October 1920: A Celebration of the Centennial of Women's Suffrage -------------- next part -------------- An HTML attachment was scrubbed... URL: From yatsonskyn at uncw.edu Thu Jan 14 18:06:21 2021 From: yatsonskyn at uncw.edu (Yatsonsky, Nicole) Date: Thu, 14 Jan 2021 23:06:21 +0000 Subject: [Archivesspace_Users_Group] Small (?) annoying problem In-Reply-To: References: , Message-ID: Hi Jill, Just wanted to say for your second issue that I have been having the same one since the update. I'm on Windows using Chrome. It seems that now when you're at the end of a page and there is an option for a drop-down menu-I'm seeing it when trying to add locations or container profiles similarly, too, so it may be localized to the top container functionality in general-instead of the dropdown menu now populating up, to make it easier to access, it drops down below the view of the page and must be scrolled to see. Definitely not a major problem, but certainly a small annoyance like you say, especially if you're at the bottom of a large container list and it would be easier to use there than scrolling all the way back up to the top option, as suggested. Nicole Yatsonsky, CA Special Collections Library Specialist Randall Library UNC Wilmington 910.962.3412 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Lora Woodford Sent: Wednesday, December 2, 2020 10:01 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Small (?) annoying problem [This email originated from outside of UNCW] Hi Jill, On the first issue - having to re-search after editing a top container - there's some good news. The latest release (v2.8.1) includes this functionality (generously contributed by developers at Harvard): https://github.com/archivesspace/archivesspace/pull/1887 Feel free to test out your workflow in the ArchivesSpace sandbox (http://sandbox.archivesspace.org/) and, hopefully, it performs as you'd like. Feedback welcome. On the second issue, have you tried using the "Bulk Operations" dropdown located at the top of the page? (It's duplicated on both the top and bottom of the page). I'm not able to replicate the problem you're seeing here locally (v2.8.1, Mac, Chrome), but perhaps you'll find using the top dropdown to be a decent enough work around as you're completing this work. Hope that helps. Lora Woodford From: archivesspace_users_group-bounces at lyralists.lyrasis.org > Date: Tuesday, December 1, 2020 at 3:27 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] FW: Small (?) annoying problem Hello all, I have found something that seems small. Until you are putting container and location profiles in for 160 boxes. If you use the Manage Top Containers section and get your list of boxes, but choose to only edit only one, you have to re-search for all those boxes once the edit has been saved. My collection has 160 boxes, I find one that is on a shelf alone and choose just that one to update. Once I've saved, I cannot go backwards to my entire list, but must re-search to get it again. My second small annoying problem is that my screen is not quite big enough vertically to see all the drop downs. I will attach an image where I tried to update a single location for a number of boxes. I only see the first two choices of the dropdown menu. I have done this enough to know to tab down once for single and twice for multiple. When I am putting in shelves, this can happen too. Say I want to put a box on shelf 6. I will be able to see 1-4 only. I use the magic tab down to guess, but sometimes it does not work and I have to re-do it several times to get the right shelf. That was a lot of words. I am updating several hundred locations and containers, and I'm getting peeved. Also, I have been kicked out 4 times in the last 3 hours, which we haven't figured out yet. Local IT has helped me check this end and I have turned off extensions, etc. But I keep getting kicked out. Jill Jill Sweetapple Pronouns: She/Her/Hers Head of Archives and Special Collections American Baptist Historical Society 3001 Mercer University Dr. Atlanta, GA 30341-4115 (01) 678/547-6680 www.abhsarchives.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Fri Jan 15 09:50:46 2021 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Fri, 15 Jan 2021 14:50:46 +0000 Subject: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1) In-Reply-To: <005c01d6e9ab$84fa3d80$8eeeb880$@sheffield.ac.uk> References: <005c01d6e9ab$84fa3d80$8eeeb880$@sheffield.ac.uk> Message-ID: <38415ef2-6db3-fe32-7ec3-e83def609cad@bodleian.ox.ac.uk> Which version of Java are you running? See http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2020-February/007388.html Andrew. On 13/01/2021 12:56, philip.webster at sheffield.ac.uk wrote: > > Hi, > > We're currently in the process of deploying ArchivesSpace 2.8.1 to our > production server following a lengthy period of testing and > development on some other servers. Strangely, the public user > interface is failing to load due to a Ruby dependency not being pulled > in when the service starts up. The dependency is SASSC, which is > present in the gems folder within the ArchivesSpace 2.8.1 installation. > > An error message appears in the logs suggesting that SASSC isn't being > imported due to it not having native extensions built, and in turn > that causes a 500 error to be visible in the browser together with a > stack trace showing the root cause to be the missing library. I tried > building the extension using the native Ruby tools in our Linux > distribution and found that had no effect. After some lengthy > investigation it turned out that the development and test servers do > not even have the native Ruby packages installed, and that everything > runs entirely through jRuby. That being the case, I have no idea how > to solve the issue with this dependency. > > None of this is mentioned in the documentation, so I?m at a loss as to > what to do next. > > Does anyone have any suggestions? > > Thanks, > > Philip Webster > > The University of Sheffield > > > _______________________________________________ > 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 christine.dibella at lyrasis.org Fri Jan 15 09:59:38 2021 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 15 Jan 2021 14:59:38 +0000 Subject: [Archivesspace_Users_Group] Language notes In-Reply-To: References: Message-ID: Hi Jennifer, I think the resolution to the previous question happened off the list. It turned out that there was language information on the archival objects previously, but that didn't become clear until the upgrade because it was more prominent afterwards than before. The site cleaned it up with some MySQL queries. Let me know if you'd like help walking through that process and I can turn this into a tech support ticket. 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 Sharp, Jennifer Sent: Wednesday, January 13, 2021 10:39 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Language notes Hi, I have a question regarding the language notes. We recently upgraded from 2.6 to 2.8.1, and I learned afterward about the language note changes that came with 2.7. We are in the process of doing some heavy editing to the finding aid for our largest collection, and it looks like every time we edit one of the Archival Objects, it automatically adds the language information. I've tried a few things, and haven't been able to get rid of it. Would either of the batch_update_langmaterials plugins help with this? I found that a similar question was asked in December 2019, but there don't seem to be any group replies. Thanks, Jennifer --- Jennifer Sharp, MSI Archivist, Hartford History Center Hartford Public Library jsharp at hplct.org o: 860.695.6332 c: 860.929.6915 VIEW OUR EXHIBIT: October 1920: A Celebration of the Centennial of Women's Suffrage -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6608 bytes Desc: image001.jpg URL: From jsharp at hplct.org Fri Jan 15 13:35:41 2021 From: jsharp at hplct.org (Sharp, Jennifer) Date: Fri, 15 Jan 2021 18:35:41 +0000 Subject: [Archivesspace_Users_Group] Language notes In-Reply-To: References: Message-ID: Thanks, Christine. Some help would be great. Jennifer From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Christine Di Bella Sent: Friday, January 15, 2021 10:00 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Language notes Hi Jennifer, I think the resolution to the previous question happened off the list. It turned out that there was language information on the archival objects previously, but that didn't become clear until the upgrade because it was more prominent afterwards than before. The site cleaned it up with some MySQL queries. Let me know if you'd like help walking through that process and I can turn this into a tech support ticket. 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 Sharp, Jennifer Sent: Wednesday, January 13, 2021 10:39 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Language notes Hi, I have a question regarding the language notes. We recently upgraded from 2.6 to 2.8.1, and I learned afterward about the language note changes that came with 2.7. We are in the process of doing some heavy editing to the finding aid for our largest collection, and it looks like every time we edit one of the Archival Objects, it automatically adds the language information. I've tried a few things, and haven't been able to get rid of it. Would either of the batch_update_langmaterials plugins help with this? I found that a similar question was asked in December 2019, but there don't seem to be any group replies. Thanks, Jennifer --- Jennifer Sharp, MSI Archivist, Hartford History Center Hartford Public Library jsharp at hplct.org o: 860.695.6332 c: 860.929.6915 VIEW OUR EXHIBIT: October 1920: A Celebration of the Centennial of Women's Suffrage -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 4014 bytes Desc: image002.jpg URL: From philip.webster at sheffield.ac.uk Mon Jan 18 11:57:33 2021 From: philip.webster at sheffield.ac.uk (Philip Webster) Date: Mon, 18 Jan 2021 16:57:33 -0000 Subject: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1) In-Reply-To: <38415ef2-6db3-fe32-7ec3-e83def609cad@bodleian.ox.ac.uk> References: <005c01d6e9ab$84fa3d80$8eeeb880$@sheffield.ac.uk> <38415ef2-6db3-fe32-7ec3-e83def609cad@bodleian.ox.ac.uk> Message-ID: <00ae01d6edbb$04e06390$0ea12ab0$@sheffield.ac.uk> Hi, Java -version on the affected server gives the following: openjdk version "11.0.9.1" 2020-11-04 OpenJDK Runtime Environment (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04) OpenJDK 64-Bit Server VM (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04, mixed mode, sharing) Regards, Phil From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Andrew Morrison Sent: 15 January 2021 14:51 To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1) Which version of Java are you running? See http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2020-Fe bruary/007388.html Andrew. On 13/01/2021 12:56, philip.webster at sheffield.ac.uk wrote: Hi, We're currently in the process of deploying ArchivesSpace 2.8.1 to our production server following a lengthy period of testing and development on some other servers. Strangely, the public user interface is failing to load due to a Ruby dependency not being pulled in when the service starts up. The dependency is SASSC, which is present in the gems folder within the ArchivesSpace 2.8.1 installation. An error message appears in the logs suggesting that SASSC isn't being imported due to it not having native extensions built, and in turn that causes a 500 error to be visible in the browser together with a stack trace showing the root cause to be the missing library. I tried building the extension using the native Ruby tools in our Linux distribution and found that had no effect. After some lengthy investigation it turned out that the development and test servers do not even have the native Ruby packages installed, and that everything runs entirely through jRuby. That being the case, I have no idea how to solve the issue with this dependency. None of this is mentioned in the documentation, so I'm at a loss as to what to do next. Does anyone have any suggestions? Thanks, Philip Webster The University of Sheffield _______________________________________________ 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 blake.carver at lyrasis.org Mon Jan 18 12:17:10 2021 From: blake.carver at lyrasis.org (Blake Carver) Date: Mon, 18 Jan 2021 17:17:10 +0000 Subject: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1) In-Reply-To: <00ae01d6edbb$04e06390$0ea12ab0$@sheffield.ac.uk> References: <005c01d6e9ab$84fa3d80$8eeeb880$@sheffield.ac.uk> <38415ef2-6db3-fe32-7ec3-e83def609cad@bodleian.ox.ac.uk>, <00ae01d6edbb$04e06390$0ea12ab0$@sheffield.ac.uk> Message-ID: Yep, that's it. ArchivesSpace is unhappy with 11. Java 8 only: https://archivesspace.github.io/tech-docs/administration/getting_started.html ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Philip Webster Sent: Monday, January 18, 2021 11:57 AM To: 'Archivesspace Users Group' Subject: Re: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1) Hi, Java ?version on the affected server gives the following: openjdk version "11.0.9.1" 2020-11-04 OpenJDK Runtime Environment (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04) OpenJDK 64-Bit Server VM (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04, mixed mode, sharing) Regards, Phil From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Andrew Morrison Sent: 15 January 2021 14:51 To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1) Which version of Java are you running? See http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2020-February/007388.html Andrew. On 13/01/2021 12:56, philip.webster at sheffield.ac.uk wrote: Hi, We're currently in the process of deploying ArchivesSpace 2.8.1 to our production server following a lengthy period of testing and development on some other servers. Strangely, the public user interface is failing to load due to a Ruby dependency not being pulled in when the service starts up. The dependency is SASSC, which is present in the gems folder within the ArchivesSpace 2.8.1 installation. An error message appears in the logs suggesting that SASSC isn't being imported due to it not having native extensions built, and in turn that causes a 500 error to be visible in the browser together with a stack trace showing the root cause to be the missing library. I tried building the extension using the native Ruby tools in our Linux distribution and found that had no effect. After some lengthy investigation it turned out that the development and test servers do not even have the native Ruby packages installed, and that everything runs entirely through jRuby. That being the case, I have no idea how to solve the issue with this dependency. None of this is mentioned in the documentation, so I?m at a loss as to what to do next. Does anyone have any suggestions? Thanks, Philip Webster The University of Sheffield _______________________________________________ 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 library at princeofpeaceabbey.org Mon Jan 18 14:21:51 2021 From: library at princeofpeaceabbey.org (library at princeofpeaceabbey.org) Date: Mon, 18 Jan 2021 13:21:51 -0600 Subject: [Archivesspace_Users_Group] Ruby SASSC issue affecting PUI (2.8.1) In-Reply-To: References: <005c01d6e9ab$84fa3d80$8eeeb880$@sheffield.ac.uk> <38415ef2-6db3-fe32-7ec3-e83def609cad@bodleian.ox.ac.uk> <00ae01d6edbb$04e06390$0ea12ab0$@sheffield.ac.uk> Message-ID: <20210118132151.Horde.0Dih_t0A17FQn5BrXzYrE-t@webmail.princeofpeaceabbey.org> Quoting Blake Carver : Blake: I am using Amazon Corretto\jdk 1.8.0_265 instead of Java 8 Br Raphael If this is a second sending I did not see that I sent it > Yep, that's it. ArchivesSpace is unhappy with 11. > Java 8 only: > https://archivesspace.github.io/tech-docs/administration/getting_started.html > ________________________________ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf > of Philip Webster > Sent: Monday, January 18, 2021 11:57 AM > To: 'Archivesspace Users Group' > > Subject: Re: [Archivesspace_Users_Group] Ruby SASSC issue affecting > PUI (2.8.1) > > > Hi, > > Java ?version on the affected server gives the following: > > openjdk version "11.0.9.1" 2020-11-04 > > OpenJDK Runtime Environment (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04) > > OpenJDK 64-Bit Server VM (build 11.0.9.1+1-Ubuntu-0ubuntu1.18.04, > mixed mode, sharing) > > > > Regards, > > > > Phil > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf > Of Andrew Morrison > Sent: 15 January 2021 14:51 > To: archivesspace_users_group at lyralists.lyrasis.org > Subject: Re: [Archivesspace_Users_Group] Ruby SASSC issue affecting > PUI (2.8.1) > > > > Which version of Java are you running? > > See > http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2020-February/007388.html > > Andrew. > > > > On 13/01/2021 12:56, > philip.webster at sheffield.ac.uk > wrote: > > Hi, > > We're currently in the process of deploying ArchivesSpace 2.8.1 to > our production server following a lengthy period of testing and > development on some other servers. Strangely, the public user > interface is failing to load due to a Ruby dependency not being > pulled in when the service starts up. The dependency is SASSC, which > is present in the gems folder within the ArchivesSpace 2.8.1 > installation. > > > > An error message appears in the logs suggesting that SASSC isn't > being imported due to it not having native extensions built, and in > turn that causes a 500 error to be visible in the browser together > with a stack trace showing the root cause to be the missing library. > I tried building the extension using the native Ruby tools in our > Linux distribution and found that had no effect. After some lengthy > investigation it turned out that the development and test servers do > not even have the native Ruby packages installed, and that > everything runs entirely through jRuby. That being the case, I have > no idea how to solve the issue with this dependency. > > > > None of this is mentioned in the documentation, so I?m at a loss as > to what to do next. > > > > Does anyone have any suggestions? > > > > Thanks, > > > > Philip Webster > > The University of Sheffield > > > > > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From christine.dibella at lyrasis.org Tue Jan 19 16:35:24 2021 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 19 Jan 2021 21:35:24 +0000 Subject: [Archivesspace_Users_Group] Grant Funds Available through LYRASIS Message-ID: Shared on behalf of our colleagues in LYRASIS. The informational webinar has already happened, but please contact Leigh Grinstead at catalystfund at lyrasis.org if you have questions or project ideas. It is that time of year again and we?re excited to announce that 2021 LYRASIS Catalyst Fund application cycle is now open and we?re accepting proposals and ideas through February 19. That?s where I hope you can come in, by forwarding this email announcement out to your colleagues, Tweet?heck, mention it on any social media platform?and help us spread the word. The more buzz, the better! The application is only two-pages in length, and our program lead will meet with institutions to discuss concepts, provide feedback, and review applications ahead of time. For those of you that may be unfamiliar, the Catalyst Fund is an award program to test and try new ideas and innovative projects submitted by LYRASIS members. 2021 applications will be reviewed by librarians, archivists, and museum professionals during March and April with recipients announced in June 2021. Only LYRASIS Members may apply for the Catalyst Fund. However, LYRASIS members may partner with non-member institutions and can act as the lead applicant for a collaboration or team pulled together for the purposes of the grant. Apply Today Criteria for Consideration This year, in addition to our general call for proposals, the Catalyst Fund is piloting a new thematic track and welcoming applications focused specifically on Open-Source Software (OSS). Applications in this track will still apply the same core values and creative concepts of the Fund: to test-and-try new approaches to shared problems; focusing on cross institutional collaboration; issues such as diversity, equity, inclusion, accessibility; other community-driven projects; and projects having community impact. The OSS track will look for projects to help the advancement, evolution, expansion, and/or application of OSS to provide innovation solutions for the LYRASIS community. Applications do not need to address this theme, but funds have been reserved specifically for those that do. Click to view the criteria used by the Leaders Circle for consideration and selection of projects to fund. What if you are Not Ready to Apply This Year? Then Become a Reviewer! Are you a critical thinker interested in contributing to innovation within the library, archives, museum, and complementary research communities? If so, please consider sharing your knowledge, expertise, and experience by reviewing applications to the Catalyst Fund. Reviewers will rate applications and provide feedback for consideration by the Leaders Circle in making the final selections. For more information about the Catalyst Fund ? Join us for Catalyst Fund: The Application Process & Overview Webinar, a free webinar on January 19 from 3:00 - 4:00 PM Eastern. Register More questions? Email catalystfund at lyrasis.org we are here to help. Leigh A. Grinstead Catalyst Fund Program Lead & Senior Digital Services Consultant 1438 West Peachtree Street NW Suite 150 Atlanta, GA 30309 she, her, hers The 2021 LYRASIS Catalyst Fund application cycle is now open and we are accepting proposals and ideas through February 19. More questions? Email us at catalystfund at lyrasis.org [cid:image001.jpg at 01D6E9BB.A6D87C90] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4263 bytes Desc: image001.jpg URL: From robinsa1 at newschool.edu Wed Jan 20 10:10:15 2021 From: robinsa1 at newschool.edu (Anna Robinson-Sweet) Date: Wed, 20 Jan 2021 10:10:15 -0500 Subject: [Archivesspace_Users_Group] Default values for notes in resource records Message-ID: Hello, I am aware that default values appear when a new accession or resource record is created, and am wondering if anyone has found a way to have the defaults appear when a new note is added to an existing resource record. For example, if we have a default value set for the Conditions of Access, and add this note to an existing resource record is there a way to have the default populate? Thanks! Anna -- *ANNA ROBINSON-SWEET* *ASSOCIATE ARCHIVIST* THE NEW SCHOOL ARCHIVES & SPECIAL COLLECTIONS she/her pronouns 66 FIFTH AVENUE, NEW YORK, NY 10011 robinsa1 at newschool.edu T 212.229.2942 x3375 @TNSArchives newschool.edu/100 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pshowell at anderson.edu Wed Jan 20 10:57:52 2021 From: pshowell at anderson.edu (Preston Howell) Date: Wed, 20 Jan 2021 10:57:52 -0500 Subject: [Archivesspace_Users_Group] Issues Upgrading In-Reply-To: References: Message-ID: Ok. I ended up reverting back to 2.7.1 and upgrading to 2.8.0 first. When I did this I got an error when running the setup database script. This then caused the same error that I noted earlier. On Fri, Jan 8, 2021 at 3:06 PM Preston Howell wrote: > That is the entirety of the log file > > On Fri, Jan 8, 2021 at 2:55 PM Blake Carver > wrote: > >> That part of the log isn't super helpful. I'd guess the real error is >> above that someplace. >> ------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >> Preston Howell >> *Sent:* Friday, January 8, 2021 2:37 PM >> *To:* Archivesspace Users Group < >> archivesspace_users_group at lyralists.lyrasis.org> >> *Subject:* [Archivesspace_Users_Group] Issues Upgrading >> >> Good afternoon all >> >> I have spent some time over the last couple of days updating software on >> our server running our instance of ArchivesSpace, including updating from >> 2.7.1 to 2.8.1. The server is currently running Ubuntu 20.04. I didn't >> realize that this update would mean Java 11 would be installed as default. >> I've now changed it to Java 8, but am unable to get ASpace to start. >> Attached is a screenshot of my log file. I'm kinda stumped at this point. >> Any help would be appreciated. >> >> Thanks in advance. >> >> [image: Screen Shot 2021-01-08 at 2.33.30 PM.png] >> >> -- >> >> Preston Howell | Library Technology Specialist | Nicholson Library >> Anderson University | 1100 E. 5th St., Anderson, IN 46012 >> (765) 641-4270 | anderson.edu >> >> Confidentiality Notice: Because email is not a secure medium, >> confidentiality of email cannot be guaranteed. This message is for the >> sole use of the intended recipient(s) and may contain confidential and >> privileged information. Any unauthorized review, use, disclosure, >> distribution, or copying is prohibited. If you are not the intended >> recipient, please contact the sender by replying to this email and >> destroy/delete all copies of this email message. >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > > -- > > Preston Howell | Library Technology Specialist | Nicholson Library > Anderson University | 1100 E. 5th St., Anderson, IN 46012 > (765) 641-4270 | anderson.edu > > Confidentiality Notice: Because email is not a secure medium, > confidentiality of email cannot be guaranteed. This message is for the > sole use of the intended recipient(s) and may contain confidential and > privileged information. Any unauthorized review, use, disclosure, > distribution, or copying is prohibited. If you are not the intended > recipient, please contact the sender by replying to this email and > destroy/delete all copies of this email message. > -- Preston Howell | Library Technology Specialist | Nicholson Library Anderson University | 1100 E. 5th St., Anderson, IN 46012 (765) 641-4270 | anderson.edu Confidentiality Notice: Because email is not a secure medium, confidentiality of email cannot be guaranteed. This message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution, or copying is prohibited. If you are not the intended recipient, please contact the sender by replying to this email and destroy/delete all copies of this email message. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2021-01-08 at 2.33.30 PM.png Type: image/png Size: 50272 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.jpg Type: image/jpeg Size: 806820 bytes Desc: not available URL: From Jessica.Crouch at lyrasis.org Fri Jan 22 10:07:38 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Fri, 22 Jan 2021 15:07:38 +0000 Subject: [Archivesspace_Users_Group] Call for speakers for the ArchivesSpace 3rd Annual Online Forum In-Reply-To: <9A6648A7-4F95-4946-B2A5-CD216172152B@lyrasis.org> References: <9A6648A7-4F95-4946-B2A5-CD216172152B@lyrasis.org> Message-ID: <7AC738CB-1EDD-4BFC-A6BC-67DD9A568210@lyrasis.org> Dear ArchivesSpace Users, Mark your calendars for our third annual Online Forum! Taking place March 29-31, 2021, our online forum will be a three-day event spanning a variety of time zones and ArchivesSpace experience levels. A full schedule and information about how to register for the event will be released closer to March. Anyone who uses ArchivesSpace or is interested in ArchivesSpace is welcome to attend. We are now accepting both session proposals and ideas for topics via our online form at https://forms.gle/dvukC8Y6a2evvswv8. We will be reviewing proposals on a rolling basis, so we encourage you to get your proposals in early. Submissions will be closed on March 5, 2021 with final notification from the planning team by March 17, 2021. As in years past, our Online Forum will include a mix of opportunities to share and learn from each other about many different aspects of ArchivesSpace and all submissions are welcome. The ArchivesSpace program team is particularly interested in presentations or workshops related to the following topics: * Using ArchivesSpace in a work from home environment * Using ArchivesSpace as a long arranger or at a small archive * Managing paraprofessionals, students and volunteers using ArchivesSpace * Demonstrations of workflows using different modules or features of the application * Examples of anti-racism, anti-colonialism and redescription work being executed in ArchivesSpace * Presentations related to the technical aspects of ArchivesSpace, including how to download a local instance of ArchivesSpace for either testing or production, understanding and managing the ArchivesSpace database, and using the API. We anticipate recording many parts of the forum, but for it to be a success we will also need as many live participants as possible. We encourage you to dip in and out of the live program as much as you can. You will no doubt ?meet? a different set of colleagues each time. A special thanks to our Online Forum planning group for the tremendous work they?re doing to plan this forum. We?re looking forward to a great event, with your help! 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: 5767 bytes Desc: image001.jpg URL: From mcyzyk at jhu.edu Fri Jan 22 12:19:18 2021 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Fri, 22 Jan 2021 12:19:18 -0500 Subject: [Archivesspace_Users_Group] Two questions Message-ID: <68448ec0-7676-097e-6b0b-1db79cb88265@jhu.edu> Hello ASpace List, I have two questions and thought I'd post them here: 1.? We are getting a "translation missing: en.instance_container.barcode" error in our ASpace 2.0. I'm sensing I need to add a translation to the "instance_container" section of /locales/en.yml: instance_container: ??? <<: *instance_attributes ??? barcode: Barcode But is this correct? 2.? A query from one of our archivists: Since the ArchivesSpace upgrade to 2.8 a couple months ago, I've encountered some issues with adding container information to archival object records. Specifically, when a container already exists in ArchivesSpace, I am not able to link to it in a new AO record by typing in the box number or barcode as I used to be able to do. I get a "no matching results. Try 'Browse'" message in the dropdown. I can locate the existing container record as usual and then link to it, but it is cumbersome. A workaround I have found is that when I open the container record, hit Edit, and then resave, the barcode or box number pop up when I try to type it in the Instance field of an AO record. Any thoughts on a remedy to this? Advice MUCH appreciated! Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From carrie.daniels at louisville.edu Fri Jan 22 12:57:02 2021 From: carrie.daniels at louisville.edu (Daniels,Carrie) Date: Fri, 22 Jan 2021 17:57:02 +0000 Subject: [Archivesspace_Users_Group] Top Container/Location issue Message-ID: Hello ArchivesSpace world - I'm seeing behavior in version 2.8.1 that I hope is "just" a bug. It's a location issue, but seems to be a little different from the other location issues that have already been reported, and I'm wondering if anyone else is encountering it. When adding a location to a top container, we used to be able to enter location coordinates in the Location field in order to bring up a suggested list. It wasn't perfect, but normally the location we were looking for was in the first couple suggestions. Since moving to 2.8.1, this functionality seems to be missing. When we enter any of the coordinates, we either get the first few entries from the entire list of locations, or we get a more random list that includes entries that completely lack matches to the coordinate(s) we entered. We can, of course, use the browse function, but as others have noted recently, when you are working with many boxes, it gets old really fast! Thanks, Carrie Carrie Daniels (she/her/hers) University Archivist and Director, Archives & Special Collections University of Louisville -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Fri Jan 22 13:18:29 2021 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Fri, 22 Jan 2021 13:18:29 -0500 Subject: [Archivesspace_Users_Group] Top Container/Location issue In-Reply-To: References: Message-ID: Hi Carrie- In 2.8 the ordering of those results is specified in the preferences, which you can get to via the dropdown menu on the top right next to your user name. Preferences can be set globally, by repository or by user (presumably the more specific ones override the less specific ones but I haven't tested that). On the preferences page, look for "Location Browse Columns", and under that look for "Default Sort Column". Setting that to "relevance" should get the locations to sort the way you're used to. By default, they sort alphabetically by name. -Trevor On Fri, Jan 22, 2021 at 12:57 PM Daniels,Carrie < carrie.daniels at louisville.edu> wrote: > Hello ArchivesSpace world - > > > > I?m seeing behavior in version 2.8.1 that I hope is ?just? a bug. It?s a > location issue, but seems to be a little different from the other location > issues that have already been reported, and I?m wondering if anyone else is > encountering it. > > > > When adding a location to a top container, we used to be able to enter > location coordinates in the Location field in order to bring up a suggested > list. It wasn?t perfect, but normally the location we were looking for was > in the first couple suggestions. Since moving to 2.8.1, this functionality > seems to be missing. When we enter any of the coordinates, we either get > the first few entries from the entire list of locations, or we get a more > random list that includes entries that completely lack matches to the > coordinate(s) we entered. We can, of course, use the browse function, but > as others have noted recently, when you are working with many boxes, it > gets old really fast! > > > > Thanks, > > Carrie > > > > Carrie Daniels > > (she/her/hers) > > University Archivist and Director, > > Archives & Special Collections > > University of Louisville > > > _______________________________________________ > 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 trthorn2 at ncsu.edu Fri Jan 22 14:23:42 2021 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Fri, 22 Jan 2021 14:23:42 -0500 Subject: [Archivesspace_Users_Group] Top Container/Location issue In-Reply-To: References: Message-ID: I responded too quickly. We had a similar issue with searching for subjects and agents to link to a record, and adjusting the default sort column preferences fixed it (when you started typing in a subject or name the list of suggestions matched what you typed). But the same doesn't seem to be true for searching locations to link to a top container. It does do something, though, because the list of results changes when that preference changes, but the results aren't what you'd expect, and don't match what you get when you use the search filter on the main locations page. On Fri, Jan 22, 2021 at 1:18 PM Trevor Thornton wrote: > Hi Carrie- > > In 2.8 the ordering of those results is specified in the preferences, > which you can get to via the dropdown menu on the top right next to your > user name. Preferences can be set globally, by repository or by user > (presumably the more specific ones override the less specific ones but I > haven't tested that). > > On the preferences page, look for "Location Browse Columns", and under > that look for "Default Sort Column". Setting that to "relevance" should get > the locations to sort the way you're used to. By default, they sort > alphabetically by name. > > -Trevor > > On Fri, Jan 22, 2021 at 12:57 PM Daniels,Carrie < > carrie.daniels at louisville.edu> wrote: > >> Hello ArchivesSpace world - >> >> >> >> I?m seeing behavior in version 2.8.1 that I hope is ?just? a bug. It?s a >> location issue, but seems to be a little different from the other location >> issues that have already been reported, and I?m wondering if anyone else is >> encountering it. >> >> >> >> When adding a location to a top container, we used to be able to enter >> location coordinates in the Location field in order to bring up a suggested >> list. It wasn?t perfect, but normally the location we were looking for was >> in the first couple suggestions. Since moving to 2.8.1, this functionality >> seems to be missing. When we enter any of the coordinates, we either get >> the first few entries from the entire list of locations, or we get a more >> random list that includes entries that completely lack matches to the >> coordinate(s) we entered. We can, of course, use the browse function, but >> as others have noted recently, when you are working with many boxes, it >> gets old really fast! >> >> >> >> Thanks, >> >> Carrie >> >> >> >> Carrie Daniels >> >> (she/her/hers) >> >> University Archivist and Director, >> >> Archives & Special Collections >> >> University of Louisville >> >> >> _______________________________________________ >> 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 > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From carrie.daniels at louisville.edu Sat Jan 23 16:41:53 2021 From: carrie.daniels at louisville.edu (Daniels,Carrie) Date: Sat, 23 Jan 2021 21:41:53 +0000 Subject: [Archivesspace_Users_Group] Top Container/Location issue In-Reply-To: References: Message-ID: Thanks, Trevor ? I do love the user preferences options ? thanks for the reminder. But you are right, it doesn?t solve my problem. Thanks for the ideas, though! Carrie From: on behalf of Trevor Thornton Reply-To: "Archivesspace_Users_Group at lyralists.lyrasis.org" Date: Friday, January 22, 2021 at 2:24 PM To: "Archivesspace_Users_Group at lyralists.lyrasis.org" Subject: Re: [Archivesspace_Users_Group] Top Container/Location issue CAUTION: This email originated from outside of our organization. Do not click links, open attachments, or respond unless you recognize the sender's email address and know the contents are safe. I responded too quickly. We had a similar issue with searching for subjects and agents to link to a record, and adjusting the default sort column preferences fixed it (when you started typing in a subject or name the list of suggestions matched what you typed). But the same doesn't seem to be true for searching locations to link to a top container. It does do something, though, because the list of results changes when that preference changes, but the results aren't what you'd expect, and don't match what you get when you use the search filter on the main locations page. On Fri, Jan 22, 2021 at 1:18 PM Trevor Thornton > wrote: Hi Carrie- In 2.8 the ordering of those results is specified in the preferences, which you can get to via the dropdown menu on the top right next to your user name. Preferences can be set globally, by repository or by user (presumably the more specific ones override the less specific ones but I haven't tested that). On the preferences page, look for "Location Browse Columns", and under that look for "Default Sort Column". Setting that to "relevance" should get the locations to sort the way you're used to. By default, they sort alphabetically by name. -Trevor On Fri, Jan 22, 2021 at 12:57 PM Daniels,Carrie > wrote: Hello ArchivesSpace world - I?m seeing behavior in version 2.8.1 that I hope is ?just? a bug. It?s a location issue, but seems to be a little different from the other location issues that have already been reported, and I?m wondering if anyone else is encountering it. When adding a location to a top container, we used to be able to enter location coordinates in the Location field in order to bring up a suggested list. It wasn?t perfect, but normally the location we were looking for was in the first couple suggestions. Since moving to 2.8.1, this functionality seems to be missing. When we enter any of the coordinates, we either get the first few entries from the entire list of locations, or we get a more random list that includes entries that completely lack matches to the coordinate(s) we entered. We can, of course, use the browse function, but as others have noted recently, when you are working with many boxes, it gets old really fast! Thanks, Carrie Carrie Daniels (she/her/hers) University Archivist and Director, Archives & Special Collections University of Louisville _______________________________________________ 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 -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Mon Jan 25 11:02:05 2021 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Mon, 25 Jan 2021 11:02:05 -0500 Subject: [Archivesspace_Users_Group] Top Container/Location issue In-Reply-To: References: Message-ID: Hi again- I was digging into this a little deeper because the same problem was reported later on Friday by one of our staff testing 2.8.1. I was wrong when I said the results when searching for a location from a top container view were inconsistent with a search from the main locations page. In testing it again I found that they were both wrong the same way. What I discovered, however, was that, when I search/filter on the main locations list, the expected results were actually on the last page, at the end, which suggests that the sort direction was wrong. Changing it from ascending to descending (in the preferences) fixed the issue for me ? I got the results I expected, both in the main locations list and when searching from a top container. My guess is that it's sorting by relevance score (higher score = more relevant) rather than relevance rank, so the sort order when using 'ascending' is the opposite of what I expected it would be. I could still be missing something ? let me know if this works for you. -Trevor On Sat, Jan 23, 2021 at 4:42 PM Daniels,Carrie < carrie.daniels at louisville.edu> wrote: > Thanks, Trevor ? > > I do love the user preferences options ? thanks for the reminder. But you > are right, it doesn?t solve my problem. Thanks for the ideas, though! > > Carrie > > > > > > *From: * on > behalf of Trevor Thornton > *Reply-To: *"Archivesspace_Users_Group at lyralists.lyrasis.org" < > archivesspace_users_group at lyralists.lyrasis.org> > *Date: *Friday, January 22, 2021 at 2:24 PM > *To: *"Archivesspace_Users_Group at lyralists.lyrasis.org" < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject: *Re: [Archivesspace_Users_Group] Top Container/Location issue > > > > *CAUTION:* This email originated from outside of our organization. Do not > click links, open attachments, or respond unless you recognize the sender's > email address and know the contents are safe. > > I responded too quickly. We had a similar issue with searching for > subjects and agents to link to a record, and adjusting the default sort > column preferences fixed it (when you started typing in a subject or name > the list of suggestions matched what you typed). But the same doesn't seem > to be true for searching locations to link to a top container. > > > > It does do something, though, because the list of results changes when > that preference changes, but the results aren't what you'd expect, and > don't match what you get when you use the search filter on the main > locations page. > > > > On Fri, Jan 22, 2021 at 1:18 PM Trevor Thornton wrote: > > Hi Carrie- > > > > In 2.8 the ordering of those results is specified in the preferences, > which you can get to via the dropdown menu on the top right next to your > user name. Preferences can be set globally, by repository or by user > (presumably the more specific ones override the less specific ones but I > haven't tested that). > > > > On the preferences page, look for "Location Browse Columns", and under > that look for "Default Sort Column". Setting that to "relevance" should get > the locations to sort the way you're used to. By default, they sort > alphabetically by name. > > > > -Trevor > > > > On Fri, Jan 22, 2021 at 12:57 PM Daniels,Carrie < > carrie.daniels at louisville.edu> wrote: > > Hello ArchivesSpace world - > > > > I?m seeing behavior in version 2.8.1 that I hope is ?just? a bug. It?s a > location issue, but seems to be a little different from the other location > issues that have already been reported, and I?m wondering if anyone else is > encountering it. > > > > When adding a location to a top container, we used to be able to enter > location coordinates in the Location field in order to bring up a suggested > list. It wasn?t perfect, but normally the location we were looking for was > in the first couple suggestions. Since moving to 2.8.1, this functionality > seems to be missing. When we enter any of the coordinates, we either get > the first few entries from the entire list of locations, or we get a more > random list that includes entries that completely lack matches to the > coordinate(s) we entered. We can, of course, use the browse function, but > as others have noted recently, when you are working with many boxes, it > gets old really fast! > > > > Thanks, > > Carrie > > > > Carrie Daniels > > (she/her/hers) > > University Archivist and Director, > > Archives & Special Collections > > University of Louisville > > > > _______________________________________________ > 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 > > > > > -- > > 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 > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From yatsonskyn at uncw.edu Mon Jan 25 11:25:03 2021 From: yatsonskyn at uncw.edu (Yatsonsky, Nicole) Date: Mon, 25 Jan 2021 16:25:03 +0000 Subject: [Archivesspace_Users_Group] Top Container/Location issue In-Reply-To: References: Message-ID: Thanks, Carrie, for bringing this up! I was going to, as I hadn't seen anyone else mention it and it had been incredibly frustrating that even when you type in the exact location it still wouldn't pull up the correct one, but I wasn't sure if maybe it was just us. I tried Trevor's suggestions on using "Relevance" and "Descending" in preferences and it isn't 100% perfect but it's much better than it was. I'd say about 80% have now come up in the list since, in comparison to hardly any before. Thanks, Trevor! Maybe there will be a general fix on the backend at some point. Nicole Yatsonsky, CA Special Collections Library Specialist Randall Library UNC Wilmington From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Trevor Thornton Sent: Monday, January 25, 2021 11:02 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Top Container/Location issue [This email originated from outside of UNCW] Hi again- I was digging into this a little deeper because the same problem was reported later on Friday by one of our staff testing 2.8.1. I was wrong when I said the results when searching for a location from a top container view were inconsistent with a search from the main locations page. In testing it again I found that they were both wrong the same way. What I discovered, however, was that, when I search/filter on the main locations list, the expected results were actually on the last page, at the end, which suggests that the sort direction was wrong. Changing it from ascending to descending (in the preferences) fixed the issue for me - I got the results I expected, both in the main locations list and when searching from a top container. My guess is that it's sorting by relevance score (higher score = more relevant) rather than relevance rank, so the sort order when using 'ascending' is the opposite of what I expected it would be. I could still be missing something - let me know if this works for you. -Trevor On Sat, Jan 23, 2021 at 4:42 PM Daniels,Carrie > wrote: Thanks, Trevor - I do love the user preferences options - thanks for the reminder. But you are right, it doesn't solve my problem. Thanks for the ideas, though! Carrie From: > on behalf of Trevor Thornton > Reply-To: "Archivesspace_Users_Group at lyralists.lyrasis.org" > Date: Friday, January 22, 2021 at 2:24 PM To: "Archivesspace_Users_Group at lyralists.lyrasis.org" > Subject: Re: [Archivesspace_Users_Group] Top Container/Location issue CAUTION: This email originated from outside of our organization. Do not click links, open attachments, or respond unless you recognize the sender's email address and know the contents are safe. I responded too quickly. We had a similar issue with searching for subjects and agents to link to a record, and adjusting the default sort column preferences fixed it (when you started typing in a subject or name the list of suggestions matched what you typed). But the same doesn't seem to be true for searching locations to link to a top container. It does do something, though, because the list of results changes when that preference changes, but the results aren't what you'd expect, and don't match what you get when you use the search filter on the main locations page. On Fri, Jan 22, 2021 at 1:18 PM Trevor Thornton > wrote: Hi Carrie- In 2.8 the ordering of those results is specified in the preferences, which you can get to via the dropdown menu on the top right next to your user name. Preferences can be set globally, by repository or by user (presumably the more specific ones override the less specific ones but I haven't tested that). On the preferences page, look for "Location Browse Columns", and under that look for "Default Sort Column". Setting that to "relevance" should get the locations to sort the way you're used to. By default, they sort alphabetically by name. -Trevor On Fri, Jan 22, 2021 at 12:57 PM Daniels,Carrie > wrote: Hello ArchivesSpace world - I'm seeing behavior in version 2.8.1 that I hope is "just" a bug. It's a location issue, but seems to be a little different from the other location issues that have already been reported, and I'm wondering if anyone else is encountering it. When adding a location to a top container, we used to be able to enter location coordinates in the Location field in order to bring up a suggested list. It wasn't perfect, but normally the location we were looking for was in the first couple suggestions. Since moving to 2.8.1, this functionality seems to be missing. When we enter any of the coordinates, we either get the first few entries from the entire list of locations, or we get a more random list that includes entries that completely lack matches to the coordinate(s) we entered. We can, of course, use the browse function, but as others have noted recently, when you are working with many boxes, it gets old really fast! Thanks, Carrie Carrie Daniels (she/her/hers) University Archivist and Director, Archives & Special Collections University of Louisville _______________________________________________ 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 -- 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 -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Mon Jan 25 12:41:54 2021 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Mon, 25 Jan 2021 12:41:54 -0500 Subject: [Archivesspace_Users_Group] Top Container/Location issue In-Reply-To: References: Message-ID: With regard to a general fix, here's what I'm seeing: 1. Those search/select fields (where you start typing and see a list of matching records, then choose the one you're looking for) is using the default sort column and direction set in the preferences for that record type. This is the same default sort and direction used for the main lists of resources, locations, etc. (i.e. what you see when you browse records before you enter a search term) 2. When 'relevance' is selected as the sort column and the direction is set to 'ascending', the order of the results is the reverse of what's expected (most relevant at the end of the list). This seems to be true for all record types and not just locations. 3. In order for the locations search/select field to work effectively (or closer to), the default sort column and direction should be "relevance" and "descending". We've also found this to be true when trying to search resources by identifier. 4. If the default sort is set that way (relevance descending) the default record lists (when you browse by resources, locations, etc., before you enter a search term to filter by) will be in an effectively arbitrary order. In most cases, the expected sort on these pages would be by title, ascending. So the problem seems to be that there is one set of sort defaults that's being used for 2 different things (for lists and for type-ahead search/select) which have different requirements. And there is the secondary issue of relevance sorting going in the wrong direction. I can create a JIRA ticket for this, but if anyone else can confirm that what I've said here is really what's going on I'd appreciate the affirmation. Thanks, Trevor On Mon, Jan 25, 2021 at 11:25 AM Yatsonsky, Nicole wrote: > Thanks, Carrie, for bringing this up! I was going to, as I hadn?t seen > anyone else mention it and it had been incredibly frustrating that even > when you type in the exact location it still wouldn?t pull up the correct > one, but I wasn?t sure if maybe it was just us. > > > > I tried Trevor?s suggestions on using ?Relevance? and ?Descending? in > preferences and it isn?t 100% perfect but it?s much better than it was. I?d > say about 80% have now come up in the list since, in comparison to hardly > any before. > > > > Thanks, Trevor! Maybe there will be a general fix on the backend at some > point. > > > > Nicole Yatsonsky, CA > > *Special Collections Library Specialist* > > *Randall Library* > > UNC Wilmington > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Trevor > Thornton > *Sent:* Monday, January 25, 2021 11:02 AM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Top Container/Location issue > > > > *[This email originated from outside of UNCW]* > > Hi again- > > > > I was digging into this a little deeper because the same problem was > reported later on Friday by one of our staff testing 2.8.1. > > > > I was wrong when I said the results when searching for a location from a > top container view were inconsistent with a search from the main locations > page. In testing it again I found that they were both wrong the same way. > > > > What I discovered, however, was that, when I search/filter on the main > locations list, the expected results were actually on the last page, at the > end, which suggests that the sort direction was wrong. Changing it from > ascending to descending (in the preferences) fixed the issue for me ? I got > the results I expected, both in the main locations list and when searching > from a top container. > > > > My guess is that it's sorting by relevance score (higher score = more > relevant) rather than relevance rank, so the sort order when using > 'ascending' is the opposite of what I expected it would be. > > > > I could still be missing something ? let me know if this works for you. > > > > -Trevor > > > > > > On Sat, Jan 23, 2021 at 4:42 PM Daniels,Carrie < > carrie.daniels at louisville.edu> wrote: > > Thanks, Trevor ? > > I do love the user preferences options ? thanks for the reminder. But you > are right, it doesn?t solve my problem. Thanks for the ideas, though! > > Carrie > > > > > > *From: * on > behalf of Trevor Thornton > *Reply-To: *"Archivesspace_Users_Group at lyralists.lyrasis.org" < > archivesspace_users_group at lyralists.lyrasis.org> > *Date: *Friday, January 22, 2021 at 2:24 PM > *To: *"Archivesspace_Users_Group at lyralists.lyrasis.org" < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject: *Re: [Archivesspace_Users_Group] Top Container/Location issue > > > > *CAUTION:* This email originated from outside of our organization. Do not > click links, open attachments, or respond unless you recognize the sender's > email address and know the contents are safe. > > I responded too quickly. We had a similar issue with searching for > subjects and agents to link to a record, and adjusting the default sort > column preferences fixed it (when you started typing in a subject or name > the list of suggestions matched what you typed). But the same doesn't seem > to be true for searching locations to link to a top container. > > > > It does do something, though, because the list of results changes when > that preference changes, but the results aren't what you'd expect, and > don't match what you get when you use the search filter on the main > locations page. > > > > On Fri, Jan 22, 2021 at 1:18 PM Trevor Thornton wrote: > > Hi Carrie- > > > > In 2.8 the ordering of those results is specified in the preferences, > which you can get to via the dropdown menu on the top right next to your > user name. Preferences can be set globally, by repository or by user > (presumably the more specific ones override the less specific ones but I > haven't tested that). > > > > On the preferences page, look for "Location Browse Columns", and under > that look for "Default Sort Column". Setting that to "relevance" should get > the locations to sort the way you're used to. By default, they sort > alphabetically by name. > > > > -Trevor > > > > On Fri, Jan 22, 2021 at 12:57 PM Daniels,Carrie < > carrie.daniels at louisville.edu> wrote: > > Hello ArchivesSpace world - > > > > I?m seeing behavior in version 2.8.1 that I hope is ?just? a bug. It?s a > location issue, but seems to be a little different from the other location > issues that have already been reported, and I?m wondering if anyone else is > encountering it. > > > > When adding a location to a top container, we used to be able to enter > location coordinates in the Location field in order to bring up a suggested > list. It wasn?t perfect, but normally the location we were looking for was > in the first couple suggestions. Since moving to 2.8.1, this functionality > seems to be missing. When we enter any of the coordinates, we either get > the first few entries from the entire list of locations, or we get a more > random list that includes entries that completely lack matches to the > coordinate(s) we entered. We can, of course, use the browse function, but > as others have noted recently, when you are working with many boxes, it > gets old really fast! > > > > Thanks, > > Carrie > > > > Carrie Daniels > > (she/her/hers) > > University Archivist and Director, > > Archives & Special Collections > > University of Louisville > > > > _______________________________________________ > 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 > > > > > -- > > 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 > > > > > > -- > > 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 > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From carrie.daniels at louisville.edu Mon Jan 25 19:04:20 2021 From: carrie.daniels at louisville.edu (Daniels,Carrie) Date: Tue, 26 Jan 2021 00:04:20 +0000 Subject: [Archivesspace_Users_Group] Top Container/Location issue In-Reply-To: References: Message-ID: <90036376-78CD-4A1F-967A-58A8176D746C@louisville.edu> Thanks again, Trevor - That made all the difference -- changing the preferences to Relevance and Descending helped immensely! As Nicole said, not 100% perfect, but a vast improvement. Carrie From: on behalf of "Yatsonsky, Nicole" Reply-To: "Archivesspace_Users_Group at lyralists.lyrasis.org" Date: Monday, January 25, 2021 at 11:25 AM To: "Archivesspace_Users_Group at lyralists.lyrasis.org" Subject: Re: [Archivesspace_Users_Group] Top Container/Location issue CAUTION: This email originated from outside of our organization. Do not click links, open attachments, or respond unless you recognize the sender's email address and know the contents are safe. Thanks, Carrie, for bringing this up! I was going to, as I hadn?t seen anyone else mention it and it had been incredibly frustrating that even when you type in the exact location it still wouldn?t pull up the correct one, but I wasn?t sure if maybe it was just us. I tried Trevor?s suggestions on using ?Relevance? and ?Descending? in preferences and it isn?t 100% perfect but it?s much better than it was. I?d say about 80% have now come up in the list since, in comparison to hardly any before. Thanks, Trevor! Maybe there will be a general fix on the backend at some point. Nicole Yatsonsky, CA Special Collections Library Specialist Randall Library UNC Wilmington From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Trevor Thornton Sent: Monday, January 25, 2021 11:02 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Top Container/Location issue [This email originated from outside of UNCW] Hi again- I was digging into this a little deeper because the same problem was reported later on Friday by one of our staff testing 2.8.1. I was wrong when I said the results when searching for a location from a top container view were inconsistent with a search from the main locations page. In testing it again I found that they were both wrong the same way. What I discovered, however, was that, when I search/filter on the main locations list, the expected results were actually on the last page, at the end, which suggests that the sort direction was wrong. Changing it from ascending to descending (in the preferences) fixed the issue for me ? I got the results I expected, both in the main locations list and when searching from a top container. My guess is that it's sorting by relevance score (higher score = more relevant) rather than relevance rank, so the sort order when using 'ascending' is the opposite of what I expected it would be. I could still be missing something ? let me know if this works for you. -Trevor On Sat, Jan 23, 2021 at 4:42 PM Daniels,Carrie > wrote: Thanks, Trevor ? I do love the user preferences options ? thanks for the reminder. But you are right, it doesn?t solve my problem. Thanks for the ideas, though! Carrie From: > on behalf of Trevor Thornton > Reply-To: "Archivesspace_Users_Group at lyralists.lyrasis.org" > Date: Friday, January 22, 2021 at 2:24 PM To: "Archivesspace_Users_Group at lyralists.lyrasis.org" > Subject: Re: [Archivesspace_Users_Group] Top Container/Location issue CAUTION: This email originated from outside of our organization. Do not click links, open attachments, or respond unless you recognize the sender's email address and know the contents are safe. I responded too quickly. We had a similar issue with searching for subjects and agents to link to a record, and adjusting the default sort column preferences fixed it (when you started typing in a subject or name the list of suggestions matched what you typed). But the same doesn't seem to be true for searching locations to link to a top container. It does do something, though, because the list of results changes when that preference changes, but the results aren't what you'd expect, and don't match what you get when you use the search filter on the main locations page. On Fri, Jan 22, 2021 at 1:18 PM Trevor Thornton > wrote: Hi Carrie- In 2.8 the ordering of those results is specified in the preferences, which you can get to via the dropdown menu on the top right next to your user name. Preferences can be set globally, by repository or by user (presumably the more specific ones override the less specific ones but I haven't tested that). On the preferences page, look for "Location Browse Columns", and under that look for "Default Sort Column". Setting that to "relevance" should get the locations to sort the way you're used to. By default, they sort alphabetically by name. -Trevor On Fri, Jan 22, 2021 at 12:57 PM Daniels,Carrie > wrote: Hello ArchivesSpace world - I?m seeing behavior in version 2.8.1 that I hope is ?just? a bug. It?s a location issue, but seems to be a little different from the other location issues that have already been reported, and I?m wondering if anyone else is encountering it. When adding a location to a top container, we used to be able to enter location coordinates in the Location field in order to bring up a suggested list. It wasn?t perfect, but normally the location we were looking for was in the first couple suggestions. Since moving to 2.8.1, this functionality seems to be missing. When we enter any of the coordinates, we either get the first few entries from the entire list of locations, or we get a more random list that includes entries that completely lack matches to the coordinate(s) we entered. We can, of course, use the browse function, but as others have noted recently, when you are working with many boxes, it gets old really fast! Thanks, Carrie Carrie Daniels (she/her/hers) University Archivist and Director, Archives & Special Collections University of Louisville _______________________________________________ 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 -- 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 -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From vaddonizio at atlas-sys.com Tue Jan 26 09:03:16 2021 From: vaddonizio at atlas-sys.com (Valerie Addonizio) Date: Tue, 26 Jan 2021 14:03:16 +0000 Subject: [Archivesspace_Users_Group] Two questions In-Reply-To: <68448ec0-7676-097e-6b0b-1db79cb88265@jhu.edu> References: <68448ec0-7676-097e-6b0b-1db79cb88265@jhu.edu> Message-ID: Hi Mark, re: your second question on the 2.8.0 update, did you undertake a full reindex as part of the update? Would staff be willing to undertake one now? The symptom of opening a record, saving it, and then [insert behavior] works is something I associate with indexing and might be worth a try. -V From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Mark Cyzyk Sent: Friday, January 22, 2021 12:19 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Two questions Hello ASpace List, I have two questions and thought I'd post them here: 1. We are getting a "translation missing: en.instance_container.barcode" error in our ASpace 2.0. I'm sensing I need to add a translation to the "instance_container" section of /locales/en.yml: instance_container: <<: *instance_attributes barcode: Barcode But is this correct? 2. A query from one of our archivists: Since the ArchivesSpace upgrade to 2.8 a couple months ago, I've encountered some issues with adding container information to archival object records. Specifically, when a container already exists in ArchivesSpace, I am not able to link to it in a new AO record by typing in the box number or barcode as I used to be able to do. I get a "no matching results. Try 'Browse'" message in the dropdown. I can locate the existing container record as usual and then link to it, but it is cumbersome. A workaround I have found is that when I open the container record, hit Edit, and then resave, the barcode or box number pop up when I try to type it in the Instance field of an AO record. Any thoughts on a remedy to this? Advice MUCH appreciated! Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Adrienne.Pruitt at tufts.edu Tue Jan 26 15:52:06 2021 From: Adrienne.Pruitt at tufts.edu (Pruitt, Adrienne) Date: Tue, 26 Jan 2021 20:52:06 +0000 Subject: [Archivesspace_Users_Group] Offsite boxes and ASpace In-Reply-To: References: , Message-ID: Hello, all, This question - of making onsite/offsite locations visible to users - has come up at Tufts, and it looks like Yale, at least, has solved it. (Hooray!) If anyone has a good solution for this (plugin or otherwise), would you mind pointing me to it? Thank you very much! Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Custer, Mark Sent: Friday, November 17, 2017 3:35 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Offsite boxes and ASpace Hi Olivia, Hear, hear!!! ? Just a quick note to say that this is something that we?ve discussed at Yale, as well, and I think that we might start to address it via a plugin at some point (it would be a nice feature to go directly into the core code, but in order for that to happen, I?d think that the Location module would need to be updated so that staff could indicate which locations were the offsite ones without having to add that data to a config file). Also, I believe that the location information is already in the PUI index, so it would just be a matter of choosing when/where to display that data. I don?t think that there?s a good EAD solution, unless you implement a specific way to use the physloc note, as you mentioned, but even then you?ve got to do some grouping since those boxes are often repeated in a finding aid, and any top-level, auto-generated note should be easy to read. Here?s what I?d like our ASpace PUI site to have (eventually): * We could configure which locations are offsite (for us, we?d just need to add 3 location IDs to an array of offsite locations). In the future, though, it would be nice if you could use the Location module in ASpace to designate this rather than doing it in a configuration file; and anything that?s not tagged as being offsite would then be inferred to be on site. * Each top-container landing page would have an automatically generated note indicating that the materials were stored offsite and requires X amount of time to retrieve (and, of course, the part about how long it would take would need to be configurable, as well) * Each archival object, accession, and resource associated via an instance with one of those top containers would have the same message. * We?d also have 2 facets to indicate onsite vs. offsite (or, available today vs. needs X amount of lead time, whatever would make the most sense). How handy would that be to exclude ?offsite? archival components if you?re only going to be in town for a day or two? * If a resource or accession had any offsite material attached to it, then an auto-generated note would display at the top level description, indicating as much (e.g. Boxes 1-3 and 5 in this collection require five business days to retrieve, upon receipt of request) All that said, it would be great to have the same info available in the staff interface, too. Have any other institutions tackled this problem already? For now, we really only indicate this by manually adding notes to our MARC Holdings records, and I?d love not to repeat that practice in our finding aids for the reasons you mentioned, Olivia. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Olivia S Solis Sent: Friday, 17 November, 2017 12:39 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Offsite boxes and ASpace Hello all, We're trying to figure out a situation that can't be uncommon. We've got a lot of onsite boxes. We've got a lot of offsite boxes. Researchers need to request offsite boxes a week in advance. Many of our collections have nebulous access restrictions like, "Portions of this collection are stored offsite". I want clarity for our researchers. We're slowly carrying out a shelf read project and soon will know exactly where every box is. How have some of you all who have all of your containers anchored to locations communicated that something is offsite to researchers? We publish EAD records to a regional consortium and are working on setting up Aeon to integrate with it and, eventually, the ASpace public interface. I have thought about adding a physical location tag for all archival objects that have associated offsite boxes stating such, but I don't like this for a couple of reasons: 1. It will look horrible. Whole series and collections that are stored offsite will have this repetitive information in archival object after archival object. 2. It will not automatically update when the box moves. For various logistical reasons, many of our boxes move around a lot or are slated to move to new locations. The whole point of having box location information in a database is that we only will have to change the information in one place. Even if there's not a good EAD solution, we can point researchers to the public interface. I've not much experience with the public interface, but should it be difficult to customize the box display so that you can see building information associated with a box? I'm just curious how other institutions have tackled this problem. I'd like it to be readily apparent to researchers when they need a week to access a box. Thanks! Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Jan 27 09:52:18 2021 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 27 Jan 2021 14:52:18 +0000 Subject: [Archivesspace_Users_Group] new program: ArchivesSpace Diversity Partnership Message-ID: (We'll be announcing this on various listservs in the coming days, but please feel free to share widely across your networks and with anyone you think may be interested. As mentioned in the announcement we're also hosting an informational webinar on February 10 and available for questions anytime.) In the wake of the George Floyd and Breonna Taylor murders, and in the spirit of protest that followed, the ArchivesSpace community began a conversation last spring about what it could do to promote diversity and inclusion while combating systemic racism in our field. That continuing conversation has led to a series of initiatives that we will undertake in the coming years, including the ArchivesSpace Diversity Partnership. The ArchivesSpace Diversity Partnership is a new program that offers support for implementing the ArchivesSpace application to institutions that are themselves or primarily serve communities underrepresented in the ArchivesSpace community. Participating organizations will receive, at no cost to them, ArchivesSpace membership, hosting with a Registered Service Provider, training, and user and technical support for the duration of a three-year term. Eligible organizations include: * academic Minority-Serving Institutions such as Historically Black Colleges and Universities (HBCUs), Hispanic Serving Institutions (HSIs), and Tribal Colleges and Universities * non-profit or community archives primarily run by or serving BIPOC (Black, Indigenous, and People of Color) * tribal archives To be eligible for this new program, organizations cannot already be ArchivesSpace members or current hosting clients of any ArchivesSpace provider. This program will launch with a small cohort of institutions on July 1, 2021. The three-year term will conclude on June 30, 2024. More information about the ArchivesSpace Diversity Partnership, including information about how to apply, is available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2049998863/ArchivesSpace+Diversity+Partnership. Members of the planning group are happy to talk about the program at any time - please contact us at ArchivesSpaceHome at lyrasis.org. Potential applicants who are interested in the experience of using ArchivesSpace at an underrepresented institution can contact Brittany Newberry (bnewberry at auctr.edu). She is happy to talk about Atlanta University Center's experience implementing ArchivesSpace as an HBCU. We are also holding an informational webinar on February 10 at 2:00 p.m. ET/11:00 a.m. PT. Registration for the webinar is available at https://lyrasis.zoom.us/webinar/register/WN_f6s6-6JeT_6q6I_TgIqWVA. The webinar will be recorded. Thanks to all who participated in the discussions and feedback opportunities that have made this program possible. Please get in touch if you have questions or ideas on this or the other initiatives our community will be undertaking to make ArchivesSpace more diverse and inclusive. Christine Sent on behalf of the Planning Group Jessica Crouch, ArchivesSpace Community Engagement Coordinator Christine Di Bella, ArchivesSpace Program Manager Brittany Newberry, Atlanta University Center and ArchivesSpace User Advisory Council Chair Sean Quimby, University of Pennsylvania and ArchivesSpace Governance Board Vice Chair Madeline Sheldon, LYRASIS Digital Technology Services ------ 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: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From mark.custer at yale.edu Thu Jan 28 11:27:14 2021 From: mark.custer at yale.edu (Custer, Mark) Date: Thu, 28 Jan 2021 16:27:14 +0000 Subject: [Archivesspace_Users_Group] Offsite boxes and ASpace In-Reply-To: References: , , Message-ID: Adrienne, Here's a link to the plugin that Hudson Molonglo developed, which we've been using for about the past six months in production: https://github.com/hudmol/yale_onsite_locations If you have any questions about it, let us know. I would love to see this in the ArchivesSpace core code, but we went with a plugin approach last year so that we could get this feature added ASAP to our instance and so that we could test out how it performs (so far, so great!). The plugin adds an "Onsite?" checkbox to every location, with the default value being set to True. And once you start flipping some locations to Onsite = False, then information is stored in the index to indicate whether the Resource and Archival Object and Top Container records are stored onsite or offsite. And since Resource and Archival Objects can be linked to multiple top containers, those records can have a hybrid status. So, that's why we now have a facet for "Storage Location", as seen in the attached image. We haven't really highlighted this new feature to users yet, but I am very interested in seeing how it gets used over time. We also talked about adding a feature in the staff interface to calculate a note for the collection to indicate which boxes were onsite vs. offsite based on this information, like the "Calculate Date / Extent" function, but didn't wind up adding that to the plugin, although I still like the idea. And Olivia, since I was still interested in adding such a note to our EAD, even after all these years (has it been over three years? ?), I did update our EAD3 export option to include the location information in our EAD files. I did not go with a physloc note, since I agree with you that it would look horrible having that information repeat everywhere if it were to display in the finding aid, so I went with an option of adding the location URI fragment into an attribute on each container element that is associated with an ASpace location record. Then, since we know which locations that we consider to be onsite vs. offsite, our nightly export process will add a note to each finding aid in the EAD3 control section. Here's an example: https://github.com/YaleArchivesSpace/Archives-at-Yale-EAD3/blob/5734391e95a954a99cb03ee54282fd14d028c8e3/brbl-ead/10764.xml#L34-L41 We aren't using that note for anything right now, but I think that it could be useful for creating our MARC holdings records, as well as for adding to our PDF finding aids, etc. But right now, it's just there so that staff could potentially use it to review and see if it looks like things are assigned as expected. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Pruitt, Adrienne Sent: Tuesday, January 26, 2021 3:52 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Offsite boxes and ASpace Hello, all, This question - of making onsite/offsite locations visible to users - has come up at Tufts, and it looks like Yale, at least, has solved it. (Hooray!) If anyone has a good solution for this (plugin or otherwise), would you mind pointing me to it? Thank you very much! Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Custer, Mark Sent: Friday, November 17, 2017 3:35 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Offsite boxes and ASpace Hi Olivia, Hear, hear!!! ? Just a quick note to say that this is something that we?ve discussed at Yale, as well, and I think that we might start to address it via a plugin at some point (it would be a nice feature to go directly into the core code, but in order for that to happen, I?d think that the Location module would need to be updated so that staff could indicate which locations were the offsite ones without having to add that data to a config file). Also, I believe that the location information is already in the PUI index, so it would just be a matter of choosing when/where to display that data. I don?t think that there?s a good EAD solution, unless you implement a specific way to use the physloc note, as you mentioned, but even then you?ve got to do some grouping since those boxes are often repeated in a finding aid, and any top-level, auto-generated note should be easy to read. Here?s what I?d like our ASpace PUI site to have (eventually): * We could configure which locations are offsite (for us, we?d just need to add 3 location IDs to an array of offsite locations). In the future, though, it would be nice if you could use the Location module in ASpace to designate this rather than doing it in a configuration file; and anything that?s not tagged as being offsite would then be inferred to be on site. * Each top-container landing page would have an automatically generated note indicating that the materials were stored offsite and requires X amount of time to retrieve (and, of course, the part about how long it would take would need to be configurable, as well) * Each archival object, accession, and resource associated via an instance with one of those top containers would have the same message. * We?d also have 2 facets to indicate onsite vs. offsite (or, available today vs. needs X amount of lead time, whatever would make the most sense). How handy would that be to exclude ?offsite? archival components if you?re only going to be in town for a day or two? * If a resource or accession had any offsite material attached to it, then an auto-generated note would display at the top level description, indicating as much (e.g. Boxes 1-3 and 5 in this collection require five business days to retrieve, upon receipt of request) All that said, it would be great to have the same info available in the staff interface, too. Have any other institutions tackled this problem already? For now, we really only indicate this by manually adding notes to our MARC Holdings records, and I?d love not to repeat that practice in our finding aids for the reasons you mentioned, Olivia. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Olivia S Solis Sent: Friday, 17 November, 2017 12:39 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Offsite boxes and ASpace Hello all, We're trying to figure out a situation that can't be uncommon. We've got a lot of onsite boxes. We've got a lot of offsite boxes. Researchers need to request offsite boxes a week in advance. Many of our collections have nebulous access restrictions like, "Portions of this collection are stored offsite". I want clarity for our researchers. We're slowly carrying out a shelf read project and soon will know exactly where every box is. How have some of you all who have all of your containers anchored to locations communicated that something is offsite to researchers? We publish EAD records to a regional consortium and are working on setting up Aeon to integrate with it and, eventually, the ASpace public interface. I have thought about adding a physical location tag for all archival objects that have associated offsite boxes stating such, but I don't like this for a couple of reasons: 1. It will look horrible. Whole series and collections that are stored offsite will have this repetitive information in archival object after archival object. 2. It will not automatically update when the box moves. For various logistical reasons, many of our boxes move around a lot or are slated to move to new locations. The whole point of having box location information in a database is that we only will have to change the information in one place. Even if there's not a good EAD solution, we can point researchers to the public interface. I've not much experience with the public interface, but should it be difficult to customize the box display so that you can see building information associated with a box? I'm just curious how other institutions have tackled this problem. I'd like it to be readily apparent to researchers when they need a week to access a box. Thanks! Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2021-01-28 at 11.12.41 AM.png Type: image/png Size: 30569 bytes Desc: Screen Shot 2021-01-28 at 11.12.41 AM.png URL: From Jessica.Crouch at lyrasis.org Fri Jan 29 12:01:06 2021 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Fri, 29 Jan 2021 17:01:06 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - January 2021 In-Reply-To: References: Message-ID: <8D9516B9-4BA7-405C-8B9C-3AA0D0C369AE@lyrasis.org> [cid:image001.jpg at 01D6F636.6C977360] Development Thank you all for your patience as we finalize the ArchivesSpace v3.0 release candidate. In anticipation of this release, we recommend reviewing the recording of our recent webinar about the expanded agent module functionality that is the exclusive focus of this update. While the required fields to create a valid agent record will remain minimal, the expanded agents functionality will allow for greater compliance with metadata standards used to describe persons, families, and corporate entities like MARCXML authority and EAC-CPF, facilitate better exchange with databases like LCNAF and SNAC and support better contextualization of agents by providing more ways to apply controlled access headings or information about the agent and their relationships. A recording of the webinar as well as a link to a test instance where you can try out the new functionality is available at https://archivesspace.org/archives/6660. Announcing the ArchivesSpace Diversity Partnership In the wake of the George Floyd and Breonna Taylor murders, and in the spirit of protest that followed, the ArchivesSpace community has been working on a series of initiatives that we will undertake in the coming years to promote diversity and inclusion while combating systemic racism in our field. We are pleased to now announce the launch of one of these initiatives, the ArchivesSpace Diversity Partnership. The ArchivesSpace Diversity Partnership is a new program that offers support for implementing the ArchivesSpace application to institutions that are themselves or primarily serve communities underrepresented in the ArchivesSpace community. Participating organizations will receive, at no cost to them, ArchivesSpace membership, hosting with a Registered Service Provider, training, and user and technical support for the duration of a three-year term. Eligible organizations include: * academic Minority-Serving Institutions such as Historically Black Colleges and Universities (HBCUs), Hispanic Serving Institutions (HSIs), and Tribal Colleges and Universities * non-profit or community archives primarily run by or serving BIPOC (Black, Indigenous, and People of Color) * tribal archives This program will launch with a small cohort of institutions on July 1, 2021. The three-year term will conclude on June 30, 2024. More information about the ArchivesSpace Diversity Partnership, including information about how to apply, is available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2049998863/ArchivesSpace+Diversity+Partnership. We're hosting an informational webinar (described below) and members of the planning group are happy to talk about the program at any time - please contact us at ArchivesSpaceHome at lyrasis.org. Potential applicants who are interested in the experience of using ArchivesSpace at an underrepresented institution can contact Brittany Newberry (bnewberry at auctr.edu). She is happy to talk about Atlanta University Center?s experience implementing ArchivesSpace as an HBCU. Webinar Announcement: ArchivesSpace Diversity Partnership Informational Webinar The ArchivesSpace Diversity Partnership is a new program that offers support for implementing the ArchivesSpace application to institutions that are themselves or primarily serve communities underrepresented in the ArchivesSpace community. Participating organizations will receive, at no cost to them, ArchivesSpace membership, hosting with a Registered Service Provider, training, and user and technical support for the duration of a three-year term. In this webinar, members of the ArchivesSpace Diversity Partnership planning team will discuss the program and answer questions from potential applicants and others interested in the program. This webinar will be recorded and made available on the ArchivesSpace YouTube channel. When: February 10, 2021 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_Esz2CPatRWmDlRNqMeWlIA In order to provide a secure webinar experience and ensure adequate space in our Zoom environment, registration is now required for our webinars. Our webinars continue to be free and open to anyone using or interested in ArchivesSpace. Who should attend: Anyone interested in the ArchivesSpace Diversity Partnership or who has questions about the application process. Call for Speakers for the 3rd Annual ArchivesSpace Online Forum Mark your calendars for our third annual Online Forum! Taking place March 29-31, 2021, our online forum will be a three-day event spanning a variety of time zones and ArchivesSpace experience levels. A full schedule and information about how to register for the event will be released closer to March. Anyone who uses ArchivesSpace or is interested in ArchivesSpace is welcome to attend. We are now accepting both session proposals and ideas for topics via our online form at https://forms.gle/dvukC8Y6a2evvswv8. We will be reviewing proposals on a rolling basis, so we encourage you to get your proposals in early. Submissions will be closed on March 5, 2021, with final notification from the planning team by March 17, 2021. As in years past, our Online Forum will include a mix of opportunities to share and learn from each other about many different aspects of ArchivesSpace and all submissions are welcome. The ArchivesSpace program team is particularly interested in presentations or workshops related to the following topics: * Using ArchivesSpace in a work from home environment * Using ArchivesSpace as a long arranger or at a small archive * Managing paraprofessionals, students and volunteers using ArchivesSpace * Demonstrations of workflows using different modules or features of the application * Examples of anti-racism, anti-colonialism and redescription work being executed in ArchivesSpace * Presentations related to the technical aspects of ArchivesSpace, including how to download a local instance of ArchivesSpace for either testing or production, understanding and managing the ArchivesSpace database, and using the API. We anticipate recording many parts of the forum, but for it to be a success we will also need as many live participants as possible. We encourage you to dip in and out of the live program as much as you can. You will no doubt ?meet? a different set of colleagues each time. A special thanks to our Online Forum planning group for the tremendous work they?re doing to plan this forum. We?re looking forward to a great event, with your help! A Message from the ArchivesSpace Usability Sub-team The Usability sub-team of the ArchivesSpace User Advisory Council develops functional and practical recommendations to the program to streamline navigation, clarify the visual layout, identify accessibility improvements, and enhance the ease of use of the staff and public interface of the ArchivesSpace application. We have prepared a brief list of issues submitted by users to JIRA, the ArchivesSpace development catalog, that we are seeking community feedback on. Your feedback will help guide our efforts, so we appreciate your input. To leave feedback on an issue, please comment on the ticket related to the issue linked below. If you prefer, you can also indicate your interest by clicking the ?thumbs up? icon at the top right of the page. (Reminder: If you need to create an Atlassian account to comment/vote on tickets or to access the ArchivesSpace Help Center, you can sign up here.) Issue: Warning before creating duplicate top containers Feedback sought: Do you want the ability to have a warning before creating a duplicate top container? Issue: Making the component unique identifier more relevant Feedback sought: How do you use the component unique identifier (CUI)? Could it be better adapted to your needs? Issue: Enhance repository processing note capabilities Feedback sought: Should repository processing notes be importable/exportable? Thank you for your feedback and consideration! Membership Update We are excited to welcome our newest members to our community! Our new members since December 30 include: * Dallas Museum of Art Archives (Dallas, TX) * Gilcrease Museum (Tulsa, OK) * Hagerstown Community College (Hagerstown, MD) * Rhodes College (Memphis, TN) As of January 29, we have 418 General members, 21 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: 22470 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 29064 bytes Desc: image002.jpg URL: From scheirw at newschool.edu Fri Jan 29 16:31:39 2021 From: scheirw at newschool.edu (Wendy Scheir) Date: Fri, 29 Jan 2021 16:31:39 -0500 Subject: [Archivesspace_Users_Group] Digital Object import title variance Message-ID: Hello, all, I'm hoping someone can help troubleshoot what to me is in inexplicable occurrence in the import digital objects process. Digital Object titles are importing into ASpace in 3 different ways: (1) Some digital objects are represented with solely the title as it was entered into the Title field of the DO import spreadsheet: [image: Screenshot_title only.png] (2) Other digital objects are represented with the title as entered into the Title field of the DO import spreadsheet, preceded by the words "Link to digitized . . . "[image: Screenshot_link to digitized and then title.png] (3) Still other digital objects do not import the title as entered into the Title field of the DO import spreadsheet at all, only the words "Link to image from this folder" [image: Screenshot_link to image from this folder.png] Many thanks for any insight you can provide, Wendy -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot_title only.png Type: image/png Size: 7860 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot_link to digitized and then title.png Type: image/png Size: 6147 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot_link to image from this folder.png Type: image/png Size: 5993 bytes Desc: not available URL: From suzanna.calev at wilkes.edu Fri Jan 29 16:40:54 2021 From: suzanna.calev at wilkes.edu (Calev, Suzanna) Date: Fri, 29 Jan 2021 16:40:54 -0500 Subject: [Archivesspace_Users_Group] Example of a CSV excel spreadsheet? Message-ID: Hi everyone, I apologize if this is extremely obvious, but I'm still trying to figure out how to do things in AS. I'm trying to create a csv file from the templates provided in the AS documentation and I'm confused as to what to put in certain sections. For example, the publish column, do we say yes or no? or put something else to indicate whether we want it to be published? For the hierarchy one, we are just putting numbers 1, 2, or 3 to indicate if the item is a resource, child, or grandchild of the parent item? For the EAD ID, should you be entering a unique number into the resource so that it identifies what resource you're using? or is that for the component unique identifier column? I think what would really help me is to see an example of what other people have done for a particular collection, even if it's just a few rows, if anyone is willing to share with me what they've entered into the different columns for your csv files, I think it would help me figure out how to configure my own for the photo collection metadata I'm trying to upload. Thank you, Suzanna -- Suzanna Calev, MLIS & MA Archivist/Public Services Librarian Farley Library 187 South Franklin Street Wilkes-Barre, PA 18766 Office: 570-408-2012 Archives: 570-408-4264 Cell: 917-656-3515 suzanna.calev at wilkes.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Fri Jan 29 16:59:31 2021 From: noah.huffman at duke.edu (Noah Huffman) Date: Fri, 29 Jan 2021 21:59:31 +0000 Subject: [Archivesspace_Users_Group] Example of a CSV excel spreadsheet? In-Reply-To: References: Message-ID: Hi Suzanna, I?ve attached a sample import spreadsheet. This sheet may not use the most up-to-date template, but it should give you an idea of how the data should be formatted and it should still import successfully. Obviously, you?ll note that this is fake data, but hopefully illustrative.? For the publish column, use TRUE if you want to the imported record to be visible in the ArchivesSpace public interface, FALSE if not. I think if you leave that column blank it will default to TRUE, which will effectively check all the ?publish? checkboxes for the imported archival objects. For the EADID column, the value in your spreadsheet must match the value in the EAD ID field of your resource record in ArchivesSpace. Here?s a link to video tutorial on using the Spreadsheet importer (formerly known as the Harvard Import Tool): https://youtu.be/xl-KjVCmm9g Hope this helps, -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ Pronouns: he / him / his From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Calev, Suzanna Sent: Friday, January 29, 2021 4:41 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Example of a CSV excel spreadsheet? Hi everyone, I apologize if this is extremely obvious, but I'm still trying to figure out how to do things in AS. I'm trying to create a csv file from the templates provided in the AS documentation and I'm confused as to what to put in certain sections. For example, the publish column, do we say yes or no? or put something else to indicate whether we want it to be published? For the hierarchy one, we are just putting numbers 1, 2, or 3 to indicate if the item is a resource, child, or grandchild of the parent item? For the EAD ID, should you be entering a unique number into the resource so that it identifies what resource you're using? or is that for the component unique identifier column? I think what would really help me is to see an example of what other people have done for a particular collection, even if it's just a few rows, if anyone is willing to share with me what they've entered into the different columns for your csv files, I think it would help me figure out how to configure my own for the photo collection metadata I'm trying to upload. Thank you, Suzanna -- Suzanna Calev, MLIS & MA Archivist/Public Services Librarian Farley Library 187 South Franklin Street Wilkes-Barre, PA 18766 Office: 570-408-2012 Archives: 570-408-4264 Cell: 917-656-3515 suzanna.calev at wilkes.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: noahs_ark_test_import_excel_to_aspace.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 51634 bytes Desc: noahs_ark_test_import_excel_to_aspace.xlsx URL: From suzanna.calev at wilkes.edu Fri Jan 29 17:40:06 2021 From: suzanna.calev at wilkes.edu (Calev, Suzanna) Date: Fri, 29 Jan 2021 17:40:06 -0500 Subject: [Archivesspace_Users_Group] Example of a CSV excel spreadsheet? In-Reply-To: References: Message-ID: Dear Noah, Thank you so much for this! What I'm wondering, do you need to keep the rows 1-3 and 5 for AS to recognize the metadata or is it only row 4 that is being recognized? does it matter if you do or don't keep those rows in? Also if you're trying to connect digital objects from a server or a DAMS to this metadata, is there a separate workflow that you use to connect them? I saw a different DO archivesspace template and do you need to do that separately or can you add it to this csv file? My institution uses Omeka and typically I have to upload the digital files to the Omeka server and then upload the CSV file to have it recognize and connect the digital file pathways to the DO. Since we're hosting AS on our own servers I was wondering if there's something I should be doing with AS to connect them with the files in Omeka or if I wanted to upload them directly from our server? Just curious if that's something you've done. Thank you so much for your help, Suzanna On Fri, Jan 29, 2021 at 5:00 PM Noah Huffman wrote: > Hi Suzanna, > > > > I?ve attached a sample import spreadsheet. This sheet may not use the most > up-to-date template, but it should give you an idea of how the data should > be formatted and it should still import successfully. Obviously, you?ll > note that this is fake data, but hopefully illustrative.J > > > > For the publish column, use TRUE if you want to the imported record to be > visible in the ArchivesSpace public interface, FALSE if not. I think if you > leave that column blank it will default to TRUE, which will effectively > check all the ?publish? checkboxes for the imported archival objects. > > > > For the EADID column, the value in your spreadsheet must match the value > in the EAD ID field of your resource record in ArchivesSpace. > > > > Here?s a link to video tutorial on using the Spreadsheet importer > (formerly known as the Harvard Import Tool): https://youtu.be/xl-KjVCmm9g > > > > Hope this helps, > > -Noah > > > > ================ > > Noah Huffman > > Archivist for Metadata, Systems, and Digital Records > > David M. Rubenstein Rare Book & Manuscript Library > > Duke University | 919-660-5982 > > http://library.duke.edu/rubenstein/ > > Pronouns: he / him / his > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Calev, > Suzanna > *Sent:* Friday, January 29, 2021 4:41 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Example of a CSV excel spreadsheet? > > > > Hi everyone, > > I apologize if this is extremely obvious, but I'm still trying to figure > out how to do things in AS. I'm trying to create a csv file from the > templates provided in the AS documentation and I'm confused as to what to > put in certain sections. For example, the publish column, do we say yes or > no? or put something else to indicate whether we want it to be published? > For the hierarchy one, we are just putting numbers 1, 2, or 3 to indicate > if the item is a resource, child, or grandchild of the parent item? > > For the EAD ID, should you be entering a unique number into the resource > so that it identifies what resource you're using? or is that for the > component unique identifier column? > > > > I think what would really help me is to see an example of what other > people have done for a particular collection, even if it's just a few rows, > if anyone is willing to share with me what they've entered into the > different columns for your csv files, I think it would help me figure out > how to configure my own for the photo collection metadata I'm trying to > upload. > > Thank you, > > Suzanna > > > -- > > Suzanna Calev, MLIS & MA > > Archivist/Public Services Librarian > Farley Library > 187 South Franklin Street > Wilkes-Barre, PA 18766 > > Office: 570-408-2012 > > Archives: 570-408-4264 > > Cell: 917-656-3515 > > suzanna.calev at wilkes.edu > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Suzanna Calev, MLIS & MA Archivist/Public Services Librarian Farley Library 187 South Franklin Street Wilkes-Barre, PA 18766 Office: 570-408-2012 Archives: 570-408-4264 Cell: 917-656-3515 suzanna.calev at wilkes.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Adrienne.Pruitt at tufts.edu Fri Jan 29 21:36:02 2021 From: Adrienne.Pruitt at tufts.edu (Pruitt, Adrienne) Date: Sat, 30 Jan 2021 02:36:02 +0000 Subject: [Archivesspace_Users_Group] Offsite boxes and ASpace In-Reply-To: References: , , , Message-ID: <9302EFBB-8215-4795-8EB4-F28641BA5738@tufts.edu> Thank you very much, Mark! This will be so useful. -Adrienne On Jan 28, 2021, at 11:27 AM, Custer, Mark wrote: ? Adrienne, Here's a link to the plugin that Hudson Molonglo developed, which we've been using for about the past six months in production: https://github.com/hudmol/yale_onsite_locations If you have any questions about it, let us know. I would love to see this in the ArchivesSpace core code, but we went with a plugin approach last year so that we could get this feature added ASAP to our instance and so that we could test out how it performs (so far, so great!). The plugin adds an "Onsite?" checkbox to every location, with the default value being set to True. And once you start flipping some locations to Onsite = False, then information is stored in the index to indicate whether the Resource and Archival Object and Top Container records are stored onsite or offsite. And since Resource and Archival Objects can be linked to multiple top containers, those records can have a hybrid status. So, that's why we now have a facet for "Storage Location", as seen in the attached image. We haven't really highlighted this new feature to users yet, but I am very interested in seeing how it gets used over time. We also talked about adding a feature in the staff interface to calculate a note for the collection to indicate which boxes were onsite vs. offsite based on this information, like the "Calculate Date / Extent" function, but didn't wind up adding that to the plugin, although I still like the idea. And Olivia, since I was still interested in adding such a note to our EAD, even after all these years (has it been over three years? ?), I did update our EAD3 export option to include the location information in our EAD files. I did not go with a physloc note, since I agree with you that it would look horrible having that information repeat everywhere if it were to display in the finding aid, so I went with an option of adding the location URI fragment into an attribute on each container element that is associated with an ASpace location record. Then, since we know which locations that we consider to be onsite vs. offsite, our nightly export process will add a note to each finding aid in the EAD3 control section. Here's an example: https://github.com/YaleArchivesSpace/Archives-at-Yale-EAD3/blob/5734391e95a954a99cb03ee54282fd14d028c8e3/brbl-ead/10764.xml#L34-L41 We aren't using that note for anything right now, but I think that it could be useful for creating our MARC holdings records, as well as for adding to our PDF finding aids, etc. But right now, it's just there so that staff could potentially use it to review and see if it looks like things are assigned as expected. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Pruitt, Adrienne Sent: Tuesday, January 26, 2021 3:52 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Offsite boxes and ASpace Hello, all, This question - of making onsite/offsite locations visible to users - has come up at Tufts, and it looks like Yale, at least, has solved it. (Hooray!) If anyone has a good solution for this (plugin or otherwise), would you mind pointing me to it? Thank you very much! Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Custer, Mark Sent: Friday, November 17, 2017 3:35 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Offsite boxes and ASpace Hi Olivia, Hear, hear!!! ? Just a quick note to say that this is something that we?ve discussed at Yale, as well, and I think that we might start to address it via a plugin at some point (it would be a nice feature to go directly into the core code, but in order for that to happen, I?d think that the Location module would need to be updated so that staff could indicate which locations were the offsite ones without having to add that data to a config file). Also, I believe that the location information is already in the PUI index, so it would just be a matter of choosing when/where to display that data. I don?t think that there?s a good EAD solution, unless you implement a specific way to use the physloc note, as you mentioned, but even then you?ve got to do some grouping since those boxes are often repeated in a finding aid, and any top-level, auto-generated note should be easy to read. Here?s what I?d like our ASpace PUI site to have (eventually): * We could configure which locations are offsite (for us, we?d just need to add 3 location IDs to an array of offsite locations). In the future, though, it would be nice if you could use the Location module in ASpace to designate this rather than doing it in a configuration file; and anything that?s not tagged as being offsite would then be inferred to be on site. * Each top-container landing page would have an automatically generated note indicating that the materials were stored offsite and requires X amount of time to retrieve (and, of course, the part about how long it would take would need to be configurable, as well) * Each archival object, accession, and resource associated via an instance with one of those top containers would have the same message. * We?d also have 2 facets to indicate onsite vs. offsite (or, available today vs. needs X amount of lead time, whatever would make the most sense). How handy would that be to exclude ?offsite? archival components if you?re only going to be in town for a day or two? * If a resource or accession had any offsite material attached to it, then an auto-generated note would display at the top level description, indicating as much (e.g. Boxes 1-3 and 5 in this collection require five business days to retrieve, upon receipt of request) All that said, it would be great to have the same info available in the staff interface, too. Have any other institutions tackled this problem already? For now, we really only indicate this by manually adding notes to our MARC Holdings records, and I?d love not to repeat that practice in our finding aids for the reasons you mentioned, Olivia. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Olivia S Solis Sent: Friday, 17 November, 2017 12:39 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Offsite boxes and ASpace Hello all, We're trying to figure out a situation that can't be uncommon. We've got a lot of onsite boxes. We've got a lot of offsite boxes. Researchers need to request offsite boxes a week in advance. Many of our collections have nebulous access restrictions like, "Portions of this collection are stored offsite". I want clarity for our researchers. We're slowly carrying out a shelf read project and soon will know exactly where every box is. How have some of you all who have all of your containers anchored to locations communicated that something is offsite to researchers? We publish EAD records to a regional consortium and are working on setting up Aeon to integrate with it and, eventually, the ASpace public interface. I have thought about adding a physical location tag for all archival objects that have associated offsite boxes stating such, but I don't like this for a couple of reasons: 1. It will look horrible. Whole series and collections that are stored offsite will have this repetitive information in archival object after archival object. 2. It will not automatically update when the box moves. For various logistical reasons, many of our boxes move around a lot or are slated to move to new locations. The whole point of having box location information in a database is that we only will have to change the information in one place. Even if there's not a good EAD solution, we can point researchers to the public interface. I've not much experience with the public interface, but should it be difficult to customize the box display so that you can see building information associated with a box? I'm just curious how other institutions have tackled this problem. I'd like it to be readily apparent to researchers when they need a week to access a box. Thanks! Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: