From Jessica.Crouch at lyrasis.org Wed Oct 2 08:51:38 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Wed, 2 Oct 2019 12:51:38 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: Batch editing barcodes through the ArchivesSpace API Message-ID: <91715B73-248D-4C1D-8B21-CC1CD3B760E6@lyrasis.org> Webinar Announcement: Batch editing barcodes through the ArchivesSpace API When: Wednesday, October 23, 2019 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? noon PT) Where: https://lyrasis.zoom.us/j/555121121 Dial In: One tap mobile +19292056099,,555121121# US (New York) +16699006833,,555121121# US (San Jose) Dial by your location +1 929 205 6099 US (New York) +1 669 900 6833 US (San Jose) 888 475 4499 US Toll-free 877 853 5257 US Toll-free Meeting ID: 555 121 121 Find your local number: https://zoom.us/u/awkFNWPxh No registration required. The webinar will be recorded and available for viewing at a later date on the ArchivesSpace YouTube channel. Webinar Description: Vakil Smallen, International Brotherhood of Teamsters Labor History Archivist at George Washington University, will walk through the steps of a workflow developed at GWU for batch editing barcodes in ArchivesSpace through the API. As a person with a limited technical background, Vakil will discuss how he found a solution to a common problem using tools previously unknown to him. He?ll offer ideas for others to get confidence and learn more when wading into similarly unfamiliar waters. Webinar Resources: Vakil originally highlighted this workflow in a blog post for the Research Libraries Section of SAA. There he includes all programs and resources he used in this process. Vakil will be using Python 3.7 in Jupyter Notebook as available in the Anaconda suite and OpenRefine in this demonstration. The Python scripts used in this webinar are posted to GitHub and available here: https://github.com/gwu-libraries/aspace-scripts/blob/master/jupyter_notebooks/nea_barcodes/Get_Top_Containers%20from%20One%20Collection-Anonymized.ipynb https://github.com/gwu-libraries/aspace-scripts/blob/master/jupyter_notebooks/nea_barcodes/Merge%20Two%20CSV%20files%20with%20a%20common%20data%20point%20for%20Github.ipynb https://github.com/gwu-libraries/aspace-scripts/blob/master/jupyter_notebooks/nea_barcodes/Post%20Barcodes%20Base%20Script.ipynb Presenter: Vakil Smallen is the International Brotherhood of Teamsters Labor History Archivist at George Washington University, a position he has held since April 2019. Before that, he was the National Education Association Project Archivist at George Washington University for 8 years. He received his MLS from the University of Maryland. Vakil's undergraduate degree was in English Literature and Language. Who should attend: Anyone interested in seeing a demonstration of a process for batch editing barcodes through the API. This webinar may be particularly useful for archivists who do not have a deep technical background and are looking for a simple workflow for making batch edits. Questions? Please contact Jessica at jessica.crouch at lyrasis.org Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29061 bytes Desc: image001.jpg URL: From lib-it at utc.edu Wed Oct 2 08:54:00 2019 From: lib-it at utc.edu (Library IT Service Desk) Date: Wed, 2 Oct 2019 08:54:00 -0400 (EDT) Subject: [Archivesspace_Users_Group] [LibIT Jira] Welcome to Library IT Service Desk Message-ID: <737604385.25.1570020840010@plibjira11.lib.utc.edu> Hi, archivesspace_users_group-request at lyralists.lyrasis.org has invited you to the Library IT Service Desk portal! Visit the portal to raise requests and get help. https://libit.utc.edu/servicedesk/customer/portal/1/user/visitportal?username=archivesspace_users_group%40lyralists.lyrasis.org&token=fd82cb494d4f02519b26a1371e1727482b3df9e4&sda_source=notification-email --------------------------------------------------------------------------------- Library IT Help Center sent you this message, powered by Jira Service Desk https://www.atlassian.com/software/jira/service-desk/powered-by?utm_medium=email&utm_source=service-desk_email-notification_server&utm_campaign=service-desk_email-notification_server -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 5931 bytes Desc: not available URL: From lib-it at utc.edu Wed Oct 2 08:54:00 2019 From: lib-it at utc.edu (archivesspace_users_group-request@lyralists.lyrasis.org) Date: Wed, 2 Oct 2019 08:54:00 -0400 (EDT) Subject: [Archivesspace_Users_Group] LIBITSD1-46 Archivesspace_Users_Group Digest, Vol 86, Issue 1 In-Reply-To: References: Message-ID: ?-?-?-? Reply above this line. Just confirming that we got your request. We're on it. __________________________ archivesspace_users_group-request at lyralists.lyrasis.org added you as a participant. View request: https://libit.utc.edu/servicedesk/customer/portal/1/LIBITSD1-46?sda_source=notification-email Turn off this request's notifications: https://libit.utc.edu/servicedesk/customer/portal/1/LIBITSD1-46/unsubscribe?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJxc2giOiI1ODFmZWYzNzdlOWMwZDBhOTA4MjVkYWQ0ODQ1NmZjZDQyZjY5MWI4NWI4M2QzZWQzZGMxNTlmYjJhMzlmOTExIiwiaXNzIjoic2VydmljZWRlc2stand0LXRva2VuLWlzc3VlciIsImNvbnRleHQiOnsidXNlciI6IkpJUkFVU0VSMTA0MDMiLCJpc3N1ZSI6IkxJQklUU0QxLTQ2In0sImV4cCI6MTU3MjQ0MDAyNCwiaWF0IjoxNTcwMDIwODI0fQ.6ymeN3_wO_AU8lWJTA387eEGZEBRJCmzR3r0G0vLZwE This is shared with archivesspace_users_group-request at lyralists.lyrasis.org and archivesspace_users_group at lyralists.lyrasis.org ------------------------------ Library IT Help Center, powered by Jira Service Desk, sent you this message. https://www.atlassian.com/software/jira/service-desk/powered-by?utm_medium=email&utm_source=service-desk_email-notification_server&utm_campaign=service-desk_email-notification_server -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Oct 2 09:36:44 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 2 Oct 2019 13:36:44 +0000 Subject: [Archivesspace_Users_Group] ignore LIB IT messages to the Users Group this morning Message-ID: Hello everyone, Just wanted to note that the two messages from LIB IT earlier today can be ignored. The links in them are not harmful, but they?re also not related to ArchivesSpace. One of our member institutions inadvertently subscribed an address that sends auto-replies. That address has now been unsubscribed. And a friendly reminder to turn off auto-replies for listservs and other messages that don?t go to a single user?s email address. ? Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- 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 jessica.wagnerwebster at baruch.cuny.edu Thu Oct 3 11:24:26 2019 From: jessica.wagnerwebster at baruch.cuny.edu (Jessica Wagner Webster) Date: Thu, 3 Oct 2019 15:24:26 +0000 Subject: [Archivesspace_Users_Group] publishing agent records Message-ID: Hi all, Is there any way to batch publish agent records associated with particular resource records, or do you have to do them individually? Also, is there any way to filter the list of agent records by which parent resource record they?re attached to? We?re finding that we have a large number of agent records associated with individual folders or items, and we can?t figure out which they are except by going item-by-item or agent-by-agent. Any tips would be appreciated. Thanks, Jessica Jessica Wagner Webster Digital Initiatives Librarian, Assistant Professor Baruch College, Newman Library 151 East 25th Street, Room 523 New York, NY 10010 (646) 312-1672 Jessica.WagnerWebster at baruch.cuny.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmcneely at brandeis.edu Fri Oct 4 13:41:33 2019 From: mmcneely at brandeis.edu (Maggie M) Date: Fri, 4 Oct 2019 13:41:33 -0400 Subject: [Archivesspace_Users_Group] Accessions upload with CSV- what about multiple extents? Message-ID: Hello all, When using the Accession CSV file template to import an accession record, there does not seem to be a way to duplicate a field to include, for example, multiple extents. I currently document multiple extents when it is a hybrid collection of paper and electronic files. So first extent would be # of linear feet and the next would be # of megabytes. Is there a way to add a second field, in this case extent, to the import file so that ASpace will record both? On experimenting with simply creating a repeated value, ASpace chooses the second extent and records that only. Many many thanks for any information or suggestions. Maggie McNeely Maggie McNeely, University Archivist Brandeis University Library MS 045 415 South Street Waltham, MA 02453-2728 Phone: 781-736-4686 Fax: 781-736-4719 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Adrienne.Pruitt at tufts.edu Mon Oct 7 13:57:27 2019 From: Adrienne.Pruitt at tufts.edu (Pruitt, Adrienne) Date: Mon, 7 Oct 2019 17:57:27 +0000 Subject: [Archivesspace_Users_Group] Enhanced fork of ASpace-import-excel plugin available Message-ID: Hello, all, This message may be of interest to those who use, or are considering, the aspace-import-excel plugin (https://github.com/harvard-library/aspace-import-excel). Tufts University Digital Collections and Archives is pleased to announce the release of a new version of the aspace-import-excel plugin, with the enhancements listed below. This work was funded by Tufts Digital Collections and Archives, with specifications and testing coordinated by Tufts Collection Management Archivist Adrienne Pruitt and all development work performed by Bobbi Fox. Enhancements: * Ability to turn 'publish' off/on individually for all notes (if not filled in: default to resource's publish switch) * Ability to import agents in as creator, source, and subject, with all available relators, and not just as creators. (If empty/missing, default is 'creator', as it is now) * Ability to add more agents per object by extending the spreadsheet * Ability to import more than one date per object * Ability for an archival object to have multiple physical instances * Ability for an archival object to have multiple extents To take advantage of these features, you must use an extended version of the Excel Spreadsheet template. There is extensive User Documentation describing use of the template and the new features. This version is backward compatible; you may continue to use the original spreadsheet template for those occasions where your workflow doesn't need these enhancements. The release can found at https://github.com/tufts-digital-collections-archives/aspace-import-excel/releases/tag/v3.0.1 In GitHub speak, this is a "fork" (deviation) from the original aspace-import-excel plugin maintained by the Harvard Library. We have issued a GitHub "pull request" -- a request that these changes be integrated into the Harvard Library repository -- so that any further work be concentrated in one repository. If that request is successful, another message will be sent. In the meantime, if you need technical help or notice a problem, please email bobbi at bobbifox.net. Cheers, Adrienne Pruitt, Tufts University Digital Collections and Archives Bobbi Fox, maintainer of aspace-import-excel Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mbagget1 at utk.edu Tue Oct 8 11:48:08 2019 From: mbagget1 at utk.edu (Baggett, Mark Patrick) Date: Tue, 8 Oct 2019 15:48:08 +0000 Subject: [Archivesspace_Users_Group] Overriding the Default Email Templates Message-ID: Hello, I'm relatively new to ArchivesSpace, but I've encountered something that I don't seem to be able to override in a local plugin: email templates. In my plugin, I have my new templates inside /public/views/request_mailer, but this doesn't seem to have any effect. In the same plugin, I have been able to override the _request_form.html.erb at /public/views/shared. From increasing the debugging levels and tailing archivesspace.out, I can tell that my new form sends my data to the email templates, but none of this shows up since I can't seem to figure out how to override the existing templates themselves. Has anyone done this before and do you have any examples online in GitHub or another repository remote? I know from reading the ArchivesSpace documentation that "in order to override or extend the behavior of core models and controllers, you cannot simply put your replacement with the same name in the corresponding directory path," but it also seems to suggest elsewhere that you can "override behavior" by matching "the path to the file that contains the behavior to be overridden." I assume this is one of the cases where you simply cannot just replace the same name with the corresponding directory path. Thanks in advance for any advice you many have, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Oct 9 11:13:06 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 9 Oct 2019 15:13:06 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v2.7.0 now available Message-ID: ArchivesSpace is announcing the availability of v2.7.0. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.7.0. This release contains program-led and community pull requests that provide feature enhancements, bug and security fixes, and documentation updates, as well as infrastructure improvements, which were a significant focus of this release. A full list of the changes and improvements is provided on the release page. In addition to small interface and functionality changes, this release contains two larger areas of feature enhancement. One relates to recording information about language of description and materials. These changes were made to facilitate better standards compliance in these areas. For language of description language and script can now be recorded using controlled values as well as notes. For language of materials multiple languages and scripts can now be recorded using controlled values and notes. Existing language information in records has been migrated to the new or newly structured fields. While some ways of recording information could be easily accommodated in this migration, because there are so many different ways language information could have been recorded previously, some situations will require data cleanup. As you look at language information in your records, if you see patterns in your data, please let us know. We are creating a few plugins that could be helpful with bulk cleanup work in this area. The second major feature enhancement, made to accommodate requests to use persistent identifiers in OAI-PMH harvests and exports, is that resources and archival objects can now be represented by Archival Resource Keys (ARKs). ARKs can either be generated by ArchivesSpace or created outside the application. By the way, we're looking to host a webinar on ARKs in 2020; if you're using ARKs already or planning to use them now that ArchivesSpace can generate them, please get in touch about this possibility for sharing your knowledge with the community. Thanks very much to community members Mark Cooper, Mark Custer, Alex Duryee, Dave Mayo, Austin Schaffer, and Greg Wiedeman, and program team members Laney McGlohon, Lora Woodford, and Sarah Morrissey for their code contributions to this release. Thanks also to the contract developer we have been able to engage through member funds, Manny Rodriguez (via LibraryHost), for his efforts on the ARKs feature. Thanks to LYRASIS Digital Technology Services for their technical support with our testing servers and running trial migrations. Last, but by no means least, as always this release would not have been possible without the efforts of our Development Prioritization sub-team, Testing sub-team, Technical Documentation sub-team, and Core Committers Group. Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not yet upgraded to a recent version, we recommend going directly to 2.7.0. Please let us know if you have any questions or need help upgrading. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6594 bytes Desc: image002.jpg URL: From npwb2 at cam.ac.uk Thu Oct 10 10:50:56 2019 From: npwb2 at cam.ac.uk (Nick Butler) Date: Thu, 10 Oct 2019 14:50:56 +0000 Subject: [Archivesspace_Users_Group] Creating location records - how? Message-ID: <4de74ca42b84b1197ba89217a388c42f08096518.camel@cam.ac.uk> Hi all, We're currently running v2.5.2 on our development system (we aren't live yet) and we're running into a peculiar problem with the permission "update_location_record". As far as we can tell, two users have been set up with the same level of permissions yet only one can create and edit location records. Pulling their records via the [:GET] /users/:id API endpoint shows that one has the "update_location_record" for all their repositories and also for the "_archivesspace" global repository, yet the other doesn't have this permission anywhere. The full list of permissions acquired via the [:GET] /permissions endpoint doesn't even include this permission; nor does the permission table of our underlying database. I tried adding it to the other user's record by POSTing a modified user object to the [:POST] /users/:id endpoint but this seems to have had no effect. Basically, how does one go about getting this permission? And is there a reason it doesn't show up in either the database or [:GET] /permissions? Could this be something that's resolved by upgrading from v2.5.2? Any advice would be very welcome, as this will become quite a pressing issue for us soon. Many thanks, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Thu Oct 10 11:01:19 2019 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Thu, 10 Oct 2019 11:01:19 -0400 Subject: [Archivesspace_Users_Group] Creating location records - how? In-Reply-To: <4de74ca42b84b1197ba89217a388c42f08096518.camel@cam.ac.uk> References: <4de74ca42b84b1197ba89217a388c42f08096518.camel@cam.ac.uk> Message-ID: We just ran into this issue last week. From what I can tell, the permission to update location records is tied to the permission to manage the repository ("manage this repository (change groups and other settings)"). I couldn't find any documentation to back this up but found this setting in the code: https://github.com/archivesspace/archivesspace/blob/8ffdb952cce8c8804392c229772ae68a00065bcc/backend/app/lib/bootstrap_access_control.rb#L209-L212 On Thu, Oct 10, 2019 at 10:51 AM Nick Butler wrote: > Hi all, > > We're currently running v2.5.2 on our development system (we aren't live > yet) and we're running into a peculiar problem with the permission > "update_location_record". > > As far as we can tell, two users have been set up with the same level of > permissions yet only one can create and edit location records. Pulling > their records via the [:GET] /users/:id API endpoint shows that one has the > "update_location_record" for all their repositories and also for the > "_archivesspace" global repository, yet the other doesn't have this > permission anywhere. The full list of permissions acquired via the [:GET] / > permissions endpoint doesn't even include this permission; nor does the > permission table of our underlying database. I tried adding it to the other > user's record by POSTing a modified user object to the [:POST] /users/:id > endpoint but this seems to have had no effect. > > Basically, how does one go about getting this permission? And is there a > reason it doesn't show up in either the database or [:GET] /permissions? > Could this be something that's resolved by upgrading from v2.5.2? Any > advice would be very welcome, as this will become quite a pressing issue > for us soon. > > Many thanks, > Nick > > -- > > *Nick Butler* > *Software Developer* > *Digital Services* > *Cambridge University Library* > *West Road* > *Cambridge CB3 9DR, UK* > > *npwb2 at cam.ac.uk* > > *Internal tel: 33067* > > _______________________________________________ > 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 npwb2 at cam.ac.uk Thu Oct 10 11:06:43 2019 From: npwb2 at cam.ac.uk (Nick Butler) Date: Thu, 10 Oct 2019 15:06:43 +0000 Subject: [Archivesspace_Users_Group] Creating location records - how? In-Reply-To: References: <4de74ca42b84b1197ba89217a388c42f08096518.camel@cam.ac.uk> Message-ID: Hi Trevor, Thank you very much for your speedy and helpful response - giving the user the manage_repository permission did indeed fix the issue. I don't think I'd have found that file otherwise, and it looks like a useful point of reference. Many thanks, Nick -----Original Message----- From: Trevor Thornton > Reply-To: Archivesspace Users Group > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Creating location records - how? Date: Thu, 10 Oct 2019 11:01:19 -0400 We just ran into this issue last week. From what I can tell, the permission to update location records is tied to the permission to manage the repository ("manage this repository (change groups and other settings)"). I couldn't find any documentation to back this up but found this setting in the code: https://github.com/archivesspace/archivesspace/blob/8ffdb952cce8c8804392c229772ae68a00065bcc/backend/app/lib/bootstrap_access_control.rb#L209-L212 On Thu, Oct 10, 2019 at 10:51 AM Nick Butler > wrote: Hi all, We're currently running v2.5.2 on our development system (we aren't live yet) and we're running into a peculiar problem with the permission "update_location_record". As far as we can tell, two users have been set up with the same level of permissions yet only one can create and edit location records. Pulling their records via the [:GET] /users/:id API endpoint shows that one has the "update_location_record" for all their repositories and also for the "_archivesspace" global repository, yet the other doesn't have this permission anywhere. The full list of permissions acquired via the [:GET] /permissions endpoint doesn't even include this permission; nor does the permission table of our underlying database. I tried adding it to the other user's record by POSTing a modified user object to the [:POST] /users/:id endpoint but this seems to have had no effect. Basically, how does one go about getting this permission? And is there a reason it doesn't show up in either the database or [:GET] /permissions? Could this be something that's resolved by upgrading from v2.5.2? Any advice would be very welcome, as this will become quite a pressing issue for us soon. Many thanks, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ 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 -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From npwb2 at cam.ac.uk Fri Oct 11 05:53:18 2019 From: npwb2 at cam.ac.uk (Nick Butler) Date: Fri, 11 Oct 2019 09:53:18 +0000 Subject: [Archivesspace_Users_Group] Creating location records - how? In-Reply-To: References: <4de74ca42b84b1197ba89217a388c42f08096518.camel@cam.ac.uk> Message-ID: Hi all, Looking at this a little bit more, it seems to be the case that the "update_location_record" permission is given globally whilst the "manage_repository" permission is set at repository level. This means that if a user has managerial level permissions at repository A but only very basic level permissions at repository B, they are still able to create, amend and delete locations at both A and B. Is there any reason that "update_location_record" isn't a repository level permission? We will have quite a number of repositories and a fair few staff members who will be given different permission levels in more than one of them. It just seems bizarre that someone who is merely in the "repository-viewers" group at a repository should be allowed to delete said repository's locations, purely because another repository has put them in the "repository-managers" group. Best wishes, Nick -----Original Message----- From: Nick Butler > Reply-To: Archivesspace Users Group > To: archivesspace_users_group at lyralists.lyrasis.org > Subject: Re: [Archivesspace_Users_Group] Creating location records - how? Date: Thu, 10 Oct 2019 15:06:43 +0000 Hi Trevor, Thank you very much for your speedy and helpful response - giving the user the manage_repository permission did indeed fix the issue. I don't think I'd have found that file otherwise, and it looks like a useful point of reference. Many thanks, Nick -----Original Message----- From: Trevor Thornton > Reply-To: Archivesspace Users Group > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Creating location records - how? Date: Thu, 10 Oct 2019 11:01:19 -0400 We just ran into this issue last week. From what I can tell, the permission to update location records is tied to the permission to manage the repository ("manage this repository (change groups and other settings)"). I couldn't find any documentation to back this up but found this setting in the code: https://github.com/archivesspace/archivesspace/blob/8ffdb952cce8c8804392c229772ae68a00065bcc/backend/app/lib/bootstrap_access_control.rb#L209-L212 On Thu, Oct 10, 2019 at 10:51 AM Nick Butler > wrote: Hi all, We're currently running v2.5.2 on our development system (we aren't live yet) and we're running into a peculiar problem with the permission "update_location_record". As far as we can tell, two users have been set up with the same level of permissions yet only one can create and edit location records. Pulling their records via the [:GET] /users/:id API endpoint shows that one has the "update_location_record" for all their repositories and also for the "_archivesspace" global repository, yet the other doesn't have this permission anywhere. The full list of permissions acquired via the [:GET] /permissions endpoint doesn't even include this permission; nor does the permission table of our underlying database. I tried adding it to the other user's record by POSTing a modified user object to the [:POST] /users/:id endpoint but this seems to have had no effect. Basically, how does one go about getting this permission? And is there a reason it doesn't show up in either the database or [:GET] /permissions? Could this be something that's resolved by upgrading from v2.5.2? Any advice would be very welcome, as this will become quite a pressing issue for us soon. Many thanks, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ 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 -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmichelson at smith.edu Fri Oct 11 07:52:26 2019 From: dmichelson at smith.edu (Daniel Michelson) Date: Fri, 11 Oct 2019 07:52:26 -0400 Subject: [Archivesspace_Users_Group] Creating location records - how? In-Reply-To: References: <4de74ca42b84b1197ba89217a388c42f08096518.camel@cam.ac.uk> Message-ID: Hi Nick, Since locations are shared across repositories, users only need permissions from one repository. This is also true of all other shared records, such as agents and subjects. Hope this helps. Dan On Fri, Oct 11, 2019, 5:53 AM Nick Butler wrote: > Hi all, > > Looking at this a little bit more, it seems to be the case that the > "update_location_record" permission is given globally whilst the > "manage_repository" permission is set at repository level. This means that > if a user has managerial level permissions at repository A but only very > basic level permissions at repository B, they are still able to create, > amend and delete locations at both A and B. > > Is there any reason that "update_location_record" isn't a repository level > permission? We will have quite a number of repositories and a fair few > staff members who will be given different permission levels in more than > one of them. It just seems bizarre that someone who is merely in the > "repository-viewers" group at a repository should be allowed to delete said > repository's locations, purely because another repository has put them in > the "repository-managers" group. > > Best wishes, > Nick > > -----Original Message----- > *From*: Nick Butler > > *Reply-To*: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org > > > > *To*: archivesspace_users_group at lyralists.lyrasis.org < > archivesspace_users_group at lyralists.lyrasis.org > <%22archivesspace_users_group at lyralists.lyrasis.org%22%20%3carchivesspace_users_group at lyralists.lyrasis.org%3e> > > > *Subject*: Re: [Archivesspace_Users_Group] Creating location records - > how? > *Date*: Thu, 10 Oct 2019 15:06:43 +0000 > > Hi Trevor, > > Thank you very much for your speedy and helpful response - giving the user > the manage_repository permission did indeed fix the issue. I don't think > I'd have found that file otherwise, and it looks like a useful point of > reference. > > Many thanks, > Nick > > -----Original Message----- > *From*: Trevor Thornton > > *Reply-To*: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org > > > > *To*: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org > > > > *Subject*: Re: [Archivesspace_Users_Group] Creating location records - > how? > *Date*: Thu, 10 Oct 2019 11:01:19 -0400 > > We just ran into this issue last week. From what I can tell, the > permission to update location records is tied to the permission to manage > the repository ("manage this repository (change groups and other > settings)"). I couldn't find any documentation to back this up but found > this setting in the code: > > > https://github.com/archivesspace/archivesspace/blob/8ffdb952cce8c8804392c229772ae68a00065bcc/backend/app/lib/bootstrap_access_control.rb#L209-L212 > > On Thu, Oct 10, 2019 at 10:51 AM Nick Butler wrote: > > Hi all, > > We're currently running v2.5.2 on our development system (we aren't live > yet) and we're running into a peculiar problem with the permission > "update_location_record". > > As far as we can tell, two users have been set up with the same level of > permissions yet only one can create and edit location records. Pulling > their records via the [:GET] /users/:id API endpoint shows that one has the > "update_location_record" for all their repositories and also for the > "_archivesspace" global repository, yet the other doesn't have this > permission anywhere. The full list of permissions acquired via the [:GET] / > permissions endpoint doesn't even include this permission; nor does the > permission table of our underlying database. I tried adding it to the other > user's record by POSTing a modified user object to the [:POST] /users/:id > endpoint but this seems to have had no effect. > > Basically, how does one go about getting this permission? And is there a > reason it doesn't show up in either the database or [:GET] /permissions? > Could this be something that's resolved by upgrading from v2.5.2? Any > advice would be very welcome, as this will become quite a pressing issue > for us soon. > > Many thanks, > Nick > > -- > > *Nick Butler* > *Software Developer* > *Digital Services* > *Cambridge University Library* > *West Road* > *Cambridge CB3 9DR, UK* > > *npwb2 at cam.ac.uk* > > *Internal tel: 33067* > > _______________________________________________ > 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 > > > -- > > *Nick Butler* > *Software Developer* > *Digital Services* > *Cambridge University Library* > *West Road* > *Cambridge CB3 9DR, UK* > > *npwb2 at cam.ac.uk* > > *Internal tel: 33067* > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > -- > > *Nick Butler* > *Software Developer* > *Digital Services* > *Cambridge University Library* > *West Road* > *Cambridge CB3 9DR, UK* > > *npwb2 at cam.ac.uk* > > *Internal tel: 33067* > > _______________________________________________ > 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 npwb2 at cam.ac.uk Fri Oct 11 09:29:32 2019 From: npwb2 at cam.ac.uk (Nick Butler) Date: Fri, 11 Oct 2019 13:29:32 +0000 Subject: [Archivesspace_Users_Group] Creating location records - how? In-Reply-To: References: <4de74ca42b84b1197ba89217a388c42f08096518.camel@cam.ac.uk> Message-ID: Hi Dan, Many thanks for the clarification - clearly haven't quite got my head around this enough yet! Best wishes, Nick -----Original Message----- From: Daniel Michelson > Reply-To: Archivesspace Users Group > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Creating location records - how? Date: Fri, 11 Oct 2019 07:52:26 -0400 Hi Nick, Since locations are shared across repositories, users only need permissions from one repository. This is also true of all other shared records, such as agents and subjects. Hope this helps. Dan On Fri, Oct 11, 2019, 5:53 AM Nick Butler > wrote: Hi all, Looking at this a little bit more, it seems to be the case that the "update_location_record" permission is given globally whilst the "manage_repository" permission is set at repository level. This means that if a user has managerial level permissions at repository A but only very basic level permissions at repository B, they are still able to create, amend and delete locations at both A and B. Is there any reason that "update_location_record" isn't a repository level permission? We will have quite a number of repositories and a fair few staff members who will be given different permission levels in more than one of them. It just seems bizarre that someone who is merely in the "repository-viewers" group at a repository should be allowed to delete said repository's locations, purely because another repository has put them in the "repository-managers" group. Best wishes, Nick -----Original Message----- From: Nick Butler > Reply-To: Archivesspace Users Group > To: archivesspace_users_group at lyralists.lyrasis.org > Subject: Re: [Archivesspace_Users_Group] Creating location records - how? Date: Thu, 10 Oct 2019 15:06:43 +0000 Hi Trevor, Thank you very much for your speedy and helpful response - giving the user the manage_repository permission did indeed fix the issue. I don't think I'd have found that file otherwise, and it looks like a useful point of reference. Many thanks, Nick -----Original Message----- From: Trevor Thornton > Reply-To: Archivesspace Users Group > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Creating location records - how? Date: Thu, 10 Oct 2019 11:01:19 -0400 We just ran into this issue last week. From what I can tell, the permission to update location records is tied to the permission to manage the repository ("manage this repository (change groups and other settings)"). I couldn't find any documentation to back this up but found this setting in the code: https://github.com/archivesspace/archivesspace/blob/8ffdb952cce8c8804392c229772ae68a00065bcc/backend/app/lib/bootstrap_access_control.rb#L209-L212 On Thu, Oct 10, 2019 at 10:51 AM Nick Butler > wrote: Hi all, We're currently running v2.5.2 on our development system (we aren't live yet) and we're running into a peculiar problem with the permission "update_location_record". As far as we can tell, two users have been set up with the same level of permissions yet only one can create and edit location records. Pulling their records via the [:GET] /users/:id API endpoint shows that one has the "update_location_record" for all their repositories and also for the "_archivesspace" global repository, yet the other doesn't have this permission anywhere. The full list of permissions acquired via the [:GET] /permissions endpoint doesn't even include this permission; nor does the permission table of our underlying database. I tried adding it to the other user's record by POSTing a modified user object to the [:POST] /users/:id endpoint but this seems to have had no effect. Basically, how does one go about getting this permission? And is there a reason it doesn't show up in either the database or [:GET] /permissions? Could this be something that's resolved by upgrading from v2.5.2? Any advice would be very welcome, as this will become quite a pressing issue for us soon. Many thanks, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ 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 -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ 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 -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rachel.donahue at lac-group.com Fri Oct 11 11:52:24 2019 From: rachel.donahue at lac-group.com (Rachel Donahue) Date: Fri, 11 Oct 2019 11:52:24 -0400 Subject: [Archivesspace_Users_Group] Oddities when updating Agents via the API Message-ID: Hi all, I'm running some bulk updates to Agents (in this case people) via the API and noticed some rather odd changes to sub-records when I check the JSON after successfully running the update. 1. Every sub-record (e.g. names, telephones) has replaced "created_by" with the user authenticated by the API and create_time with the time of the API call. The Agent itself retains its created_by and time, thankfully, but all the bits and pieces lose it. 2. Possibly related to this, a new telephone number is created even though nothing about the phone number has changed. (e.g. what was /telephone/99 is now /telephone/204) 3. The lock_version for the sub-records isn't changing from 0. The only thing changing in these updates is the name source and we're using ArchivesSpace 2.6.0. I have been reposting the entire object in the update--is it possible to post *only* the changing fields and perhaps avoid the problem? While this isn't a make-or-break problem, I'd really like to retain the created_by information for names, as it is often *not* the same as the person who created the initial record. I'm also not sure if this is a bug or something I'm doing wrong. Any insights would be much appreciated! Best, Rachel -- Please note that I currently *do not have access to ARS email*. If you need to contact me, use my LAC address: rachel.donahue at lac-group.com The information contained in this e-mail message is confidential. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you think that you have received this e-mail message in error, please contact the sender. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alicia.detelich at yale.edu Fri Oct 11 12:17:07 2019 From: alicia.detelich at yale.edu (Detelich, Alicia) Date: Fri, 11 Oct 2019 16:17:07 +0000 Subject: [Archivesspace_Users_Group] Oddities when updating Agents via the API In-Reply-To: References: Message-ID: <5604120B-A726-4ED2-8537-0B94A6B49194@yale.edu> Hi Rachel, Basically, what you are seeing is that whenever a record is posted, all of its subrecords are deleted and recreated, even if no changes are made to the subrecords themselves. When this happens a new database identifier, create time, lock version etc. are assigned to each subrecord. I don?t think it?s a bug, per se, but it is an odd behavior that has come up numerous times in my work as well. I am not sure why the decision to design subrecords that way was made by the original developers of the application (if anyone has thoughts please let me know!), nor do I have a sense of the amount of work/consequences involved in updating the application so that subrecords are persistent. There isn?t a way to only post the changing fields via the API, since only top-level records (resources, archival objects, etc.) have their own URIs. An alternative solution would be to do a (very careful!) database update to the relevant field(s) in the relevant name table(s). Hope this helps, Alicia Alicia Detelich Archivist Manuscripts and Archives Yale University Libraries From: on behalf of Rachel Donahue Reply-To: Archivesspace Users Group Date: Friday, October 11, 2019 at 11:52 AM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Oddities when updating Agents via the API Hi all, I'm running some bulk updates to Agents (in this case people) via the API and noticed some rather odd changes to sub-records when I check the JSON after successfully running the update. 1. Every sub-record (e.g. names, telephones) has replaced "created_by" with the user authenticated by the API and create_time with the time of the API call. The Agent itself retains its created_by and time, thankfully, but all the bits and pieces lose it. 2. Possibly related to this, a new telephone number is created even though nothing about the phone number has changed. (e.g. what was /telephone/99 is now /telephone/204) 3. The lock_version for the sub-records isn't changing from 0. The only thing changing in these updates is the name source and we're using ArchivesSpace 2.6.0. I have been reposting the entire object in the update--is it possible to post *only* the changing fields and perhaps avoid the problem? While this isn't a make-or-break problem, I'd really like to retain the created_by information for names, as it is often *not* the same as the person who created the initial record. I'm also not sure if this is a bug or something I'm doing wrong. Any insights would be much appreciated! Best, Rachel -- Please note that I currently do not have access to ARS email. If you need to contact me, use my LAC address: rachel.donahue at lac-group.com The information contained in this e-mail message is confidential. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you think that you have received this e-mail message in error, please contact the sender. -------------- next part -------------- An HTML attachment was scrubbed... URL: From freya.anderson at alaska.gov Fri Oct 11 13:06:42 2019 From: freya.anderson at alaska.gov (Anderson, Freya N (EED)) Date: Fri, 11 Oct 2019 17:06:42 +0000 Subject: [Archivesspace_Users_Group] How records show up on internet searches Message-ID: Hello all We?ve been doing some sample searches to see how our records show up in Google and other search engines. We?re glad that they?re showing up in the results, but the page names that show up bold at the top of the listings are generic, with no information about the actual collection they refer to. For example, from a Google result:<%0dHistorical%20Collections%20Finding%20Aids%20-%20Alaska%20State%20Library%0dhttps:/alaska.libraryhost.com%20?%20repositories%20?%20resources%0d> Historical Collections Finding Aids - Alaska State Library<%0dHistorical%20Collections%20Finding%20Aids%20-%20Alaska%20State%20Library%0dhttps:/alaska.libraryhost.com%20?%20repositories%20?%20resources%0d> https://alaska.libraryhost.com ? repositories ? resources<%0dHistorical%20Collections%20Finding%20Aids%20-%20Alaska%20State%20Library%0dhttps:/alaska.libraryhost.com%20?%20repositories%20?%20resources%0d> Exxon Valdez Papers, 1987-1990. Guides and documents accompanying the 104 Video Recordings (AV 025) related to the Exxon Valdez oil spill, 1989-1991, ... Is there any way for us to set this up so that the actual content, in this case ?Exxon Valdez Papers, 1987-1990? shows up in the top line? It seems like it would be a lot more user friendly that way. As you can probably see from the URL, we?re using a hosted version of ArchivesSpace. Thanks! Freya [cid:image001.png at 01D507DF.8CCD64B0] Freya Anderson (she/her) Head, Information Services Acting Head, Historical Collections phone: 907.465.1315 Andrew P. Kashevaroff Building Mail: PO Box 110571, Juneau, AK 99811 Visit: 395 Whittier St., Juneau, AK 99801 email | web | sign up for event notifications | The Information Center for Government -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 16891 bytes Desc: image001.png URL: From dave_mayo at harvard.edu Sun Oct 13 16:52:04 2019 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Sun, 13 Oct 2019 20:52:04 +0000 Subject: [Archivesspace_Users_Group] Oddities when updating Agents via the API In-Reply-To: References: Message-ID: <50E41CB5-5A5C-4359-B742-BDF5C9787A2E@harvard.edu> There are a lot of sub-records in ASpace that are essentially treated as ephemeral but which have full concrete tables backing them; they?re not addressable in the system, their representations in the JSONModel are as primitive values (strings, array of strings, etc) rather than objects, etc. Instances are kind of this way ? you can?t grab an instance, only the things attached to it, but it has a database ID, etc. You _might_ be able to insert refs to the subrecords that aren?t changing, rather than the values/records themselves? That _might_ keep the values the same, but I?m not sure it?ll be legal everywhere. You could also try explicitly setting created_by and created_at; I am at a conf but could poke at this later (maybe tonight or tomorrow) if you?ll remind me. -- Dave Mayo (he/him) Senior Digital Library Software Engineer Harvard University > HUIT > LTS From: on behalf of Rachel Donahue Reply-To: Archivesspace Users Group Date: Friday, October 11, 2019 at 11:52 AM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Oddities when updating Agents via the API Hi all, I'm running some bulk updates to Agents (in this case people) via the API and noticed some rather odd changes to sub-records when I check the JSON after successfully running the update. 1. Every sub-record (e.g. names, telephones) has replaced "created_by" with the user authenticated by the API and create_time with the time of the API call. The Agent itself retains its created_by and time, thankfully, but all the bits and pieces lose it. 2. Possibly related to this, a new telephone number is created even though nothing about the phone number has changed. (e.g. what was /telephone/99 is now /telephone/204) 3. The lock_version for the sub-records isn't changing from 0. The only thing changing in these updates is the name source and we're using ArchivesSpace 2.6.0. I have been reposting the entire object in the update--is it possible to post *only* the changing fields and perhaps avoid the problem? While this isn't a make-or-break problem, I'd really like to retain the created_by information for names, as it is often *not* the same as the person who created the initial record. I'm also not sure if this is a bug or something I'm doing wrong. Any insights would be much appreciated! Best, Rachel -- Please note that I currently do not have access to ARS email. If you need to contact me, use my LAC address: rachel.donahue at lac-group.com The information contained in this e-mail message is confidential. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you think that you have received this e-mail message in error, please contact the sender. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Oct 14 10:29:51 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 14 Oct 2019 14:29:51 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Southeastern Regional Forum - Registration is now open! Message-ID: [cid:image001.jpg at 01D5827A.4AF81150] Registration is now open for the ArchivesSpace Southeastern Regional Forum on November 15, 2019, at the Hollings Special Collections Library at ArchivesSpace member institution University of South Carolina. As with previous forums, this will be a free opportunity for staff from ArchivesSpace member institutions in the region to meet and share information with each other and the program team about all things ArchivesSpace with a focus on local interests and activities. SCHEDULE OVERVIEW The specifics of the program continue to be shaped by the working group. The most current information is available on the ArchivesSpace wiki page for the forum. ? Pre-forum Happy Hour: An optional happy hour will be held the evening before the forum. Appetizers (including vegetarian options) will be provided. You are welcome to purchase your own drinks or additional food. ? ? Morning program: The morning will highlight shared stories and experiences through focused discussions and presentations. ? ? Lunch: Lunch will be on your own. There are a number of lunch options on the USC campus and the surrounding area, a list of suggestions is available on the ArchivesSpace wiki. ? Afternoon program: The afternoon will feature two workshops. To secure your place in a workshop, pre-registration is required. You will need to bring your own laptop for each workshop. Tablets and chromebooks are strongly discouraged. Workshops A: ArchivesSpace Basics This workshop will cover the basic elements of ArchivesSpace including getting started and demonstrating the most commonly used modules. There will also be time to demonstrate audience requested functions. Workshop B: Migration and Data Control in ArchivesSpace Kelly Spring will draw from her own experience at East Carolina University migrating to ArchivesSpace for this workshop, where she will demonstrate methodologies and workflows for both initial migration and data clean up after migration has occurred. PARKING & TRANSPORTATION Directions and maps can be found on the ArchivesSpace wiki page for the forum. QUESTIONS? If you have questions, please email Jessica at jessica.crouch at lyrasis.org. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 980381 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 29061 bytes Desc: image002.jpg URL: From rachel.donahue at lac-group.com Tue Oct 15 09:34:47 2019 From: rachel.donahue at lac-group.com (Rachel Donahue) Date: Tue, 15 Oct 2019 09:34:47 -0400 Subject: [Archivesspace_Users_Group] Oddities when updating Agents via the API In-Reply-To: References: Message-ID: Alicia and Dave, Thank you so much for your help! I was thrown by telephone having it's own URI, but I guess I'll just have to accept the new creation dates. We're using a hosted instance, so I unfortunately don't have MySQL access. Dave-- the JSON payload already contains the original created_by information, so I don't think maually setting it by API is going to work. Like I said, not make or break, just nice-to-have. The information for subrecords doesn't even show in the staff interface, so I'm likely the only one who would ever notice that it's happening. Best, Rachel -- Please note that I currently *do not have access to ARS email*. If you need to contact me, use my LAC address: rachel.donahue at lac-group.com The information contained in this e-mail message is confidential. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you think that you have received this e-mail message in error, please contact the sender. > > Message: 16 > Date: Fri, 11 Oct 2019 16:17:07 +0000 > From: "Detelich, Alicia" > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] Oddities when updating Agents > via the API > Message-ID: <5604120B-A726-4ED2-8537-0B94A6B49194 at yale.edu> > Content-Type: text/plain; charset="utf-8" > > Hi Rachel, > > Basically, what you are seeing is that whenever a record is posted, all of > its subrecords are deleted and recreated, even if no changes are made to > the subrecords themselves. When this happens a new database identifier, > create time, lock version etc. are assigned to each subrecord. I don?t > think it?s a bug, per se, but it is an odd behavior that has come up > numerous times in my work as well. > > I am not sure why the decision to design subrecords that way was made by > the original developers of the application (if anyone has thoughts please > let me know!), nor do I have a sense of the amount of work/consequences > involved in updating the application so that subrecords are persistent. > > There isn?t a way to only post the changing fields via the API, since only > top-level records (resources, archival objects, etc.) have their own URIs. > An alternative solution would be to do a (very careful!) database update to > the relevant field(s) in the relevant name table(s). > > Hope this helps, > > Alicia > > Alicia Detelich > Archivist > Manuscripts and Archives > Yale University Libraries > > From: on behalf > of Rachel Donahue > Reply-To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Date: Friday, October 11, 2019 at 11:52 AM > To: "archivesspace_users_group at lyralists.lyrasis.org" < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] Oddities when updating Agents via the > API > > Hi all, > > I'm running some bulk updates to Agents (in this case people) via the API > and noticed some rather odd changes to sub-records when I check the JSON > after successfully running the update. > > 1. Every sub-record (e.g. names, telephones) has replaced "created_by" > with the user authenticated by the API and create_time with the time of the > API call. The Agent itself retains its created_by and time, thankfully, but > all the bits and pieces lose it. > 2. Possibly related to this, a new telephone number is created even though > nothing about the phone number has changed. (e.g. what was /telephone/99 is > now /telephone/204) > 3. The lock_version for the sub-records isn't changing from 0. > > The only thing changing in these updates is the name source and we're > using ArchivesSpace 2.6.0. I have been reposting the entire object in the > update--is it possible to post *only* the changing fields and perhaps avoid > the problem? > > While this isn't a make-or-break problem, I'd really like to retain the > created_by information for names, as it is often *not* the same as the > person who created the initial record. I'm also not sure if this is a bug > or something I'm doing wrong. Any insights would be much appreciated! > > Best, > Rachel > > > Message: 18 > Date: Sun, 13 Oct 2019 20:52:04 +0000 > From: "Mayo, Dave" > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] Oddities when updating Agents > via the API > Message-ID: <50E41CB5-5A5C-4359-B742-BDF5C9787A2E at harvard.edu> > Content-Type: text/plain; charset="utf-8" > > There are a lot of sub-records in ASpace that are essentially treated as > ephemeral but which have full concrete tables backing them; they?re not > addressable in the system, their representations in the JSONModel are as > primitive values (strings, array of strings, etc) rather than objects, > etc. Instances are kind of this way ? you can?t grab an instance, only the > things attached to it, but it has a database ID, etc. > > You _might_ be able to insert refs to the subrecords that aren?t changing, > rather than the values/records themselves? That _might_ keep the values > the same, but I?m not sure it?ll be legal everywhere. You could also try > explicitly setting created_by and created_at; I am at a conf but could poke > at this later (maybe tonight or tomorrow) if you?ll remind me. > > -- > Dave Mayo (he/him) > Senior Digital Library Software Engineer > Harvard University > HUIT > LTS > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mgolson at stanford.edu Wed Oct 16 14:52:40 2019 From: mgolson at stanford.edu (Michael G Olson) Date: Wed, 16 Oct 2019 18:52:40 +0000 Subject: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 Message-ID: Hi everyone, Here at Stanford Libraries we just ran an upgrade from 1.5.4 to version 2.6.0 and noticed some odd behavior we?d like to validate with our peers. We received no error messages while running the upgrade. That said, for one of our repositories (we have many) we?ve noticed that by clicking on the resource tree we get an error message. I?m speculating here but my guess is that the extent for this resources were not defined in such a way the application knows the relationship between parent and child. Here is the error message we?re seeing. .[cid:F9667546-C659-4BE4-90B8-F0FECF129BE6 at stanford.edu] For this particular example here is how our extents had been entered in application. [cid:37E27617-7C70-41B3-9EAD-24F61085F107 at stanford.edu] My questions are has anyone seen this sort of behavior before? Is this something we can fix in the upgraded application or do we need to implement a fix before the upgrade. Any insights anyone has on this issue would be much appreciated! Michael -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cub_001.jpeg Type: image/jpeg Size: 3772 bytes Desc: cub_001.jpeg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cub_002.jpeg Type: image/jpeg Size: 16694 bytes Desc: cub_002.jpeg URL: From sdm7g at virginia.edu Wed Oct 16 15:15:44 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 16 Oct 2019 19:15:44 +0000 Subject: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 In-Reply-To: References: Message-ID: <52BBC9F0-C64D-4FA0-AB92-8B6BC5CA89E7@virginia.edu> Error messages/images are too compressed or small to read. Just a blur. Can you resend or else transcribe ? ? Steve M. > On Oct 16, 2019, at 2:52 PM, Michael G Olson wrote: > > Hi everyone, > > Here at Stanford Libraries we just ran an upgrade from 1.5.4 to version 2.6.0 and noticed some odd behavior we?d like to validate with our peers. We received no error messages while running the upgrade. That said, for one of our repositories (we have many) we?ve noticed that by clicking on the resource tree we get an error message. I?m speculating here but my guess is that the extent for this resources were not defined in such a way the application knows the relationship between parent and child. Here is the error message we?re seeing. > > . > > For this particular example here is how our extents had been entered in application. > > > > My questions are has anyone seen this sort of behavior before? Is this something we can fix in the upgraded application or do we need to implement a fix before the upgrade. Any insights anyone has on this issue would be much appreciated! > > Michael > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4974 bytes Desc: not available URL: From mgolson at stanford.edu Wed Oct 16 15:24:53 2019 From: mgolson at stanford.edu (Michael G Olson) Date: Wed, 16 Oct 2019 19:24:53 +0000 Subject: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 In-Reply-To: <52BBC9F0-C64D-4FA0-AB92-8B6BC5CA89E7@virginia.edu> References: , <52BBC9F0-C64D-4FA0-AB92-8B6BC5CA89E7@virginia.edu> Message-ID: Hi Steve, all, Sorry about that? the error message we?re receiving when we click on the Collection tree is, "Oops! We're having trouble fetching this tree. Please try refreshing the page.? If you open the image titled extent you'll see how our archivist entered the extent for this particular collection. It looks like this isn't really defined as a true child of the collection. thanks, Michael ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Majewski, Steven Dennis (sdm7g) Sent: Wednesday, October 16, 2019 12:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 Error messages/images are too compressed or small to read. Just a blur. Can you resend or else transcribe ? ? Steve M. On Oct 16, 2019, at 2:52 PM, Michael G Olson > wrote: Hi everyone, Here at Stanford Libraries we just ran an upgrade from 1.5.4 to version 2.6.0 and noticed some odd behavior we?d like to validate with our peers. We received no error messages while running the upgrade. That said, for one of our repositories (we have many) we?ve noticed that by clicking on the resource tree we get an error message. I?m speculating here but my guess is that the extent for this resources were not defined in such a way the application knows the relationship between parent and child. Here is the error message we?re seeing. . For this particular example here is how our extents had been entered in application. My questions are has anyone seen this sort of behavior before? Is this something we can fix in the upgraded application or do we need to implement a fix before the upgrade. Any insights anyone has on this issue would be much appreciated! Michael _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cub_001.jpeg Type: image/jpeg Size: 51798 bytes Desc: cub_001.jpeg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: extent.jpeg Type: image/jpeg Size: 67517 bytes Desc: extent.jpeg URL: From alexanderduryee at nypl.org Wed Oct 16 17:39:16 2019 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Wed, 16 Oct 2019 17:39:16 -0400 Subject: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 In-Reply-To: References: <52BBC9F0-C64D-4FA0-AB92-8B6BC5CA89E7@virginia.edu> Message-ID: Michael, Do you see anything interesting in the system logs or your browser's Javascript console when you try to open the collection? I don't see anything in the Extent record that you attached that would cause the Resource record to throw an error like that. Thanks, --Alex On Wed, Oct 16, 2019 at 3:25 PM Michael G Olson wrote: > Hi Steve, all, > > Sorry about that? the error message we?re receiving when we click on the > Collection tree is, "Oops! We're having trouble fetching this tree. > Please try refreshing the page.? > > If you open the image titled extent you'll see how our archivist entered > the extent for this particular collection. It looks like this isn't really > defined as a true child of the collection. > > thanks, > > Michael > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Majewski, Steven Dennis (sdm7g) > *Sent:* Wednesday, October 16, 2019 12:15 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from > 1.5.4 to 2.6.0 > > > Error messages/images are too compressed or small to read. Just a blur. > Can you resend or else transcribe ? ? Steve M. > > > On Oct 16, 2019, at 2:52 PM, Michael G Olson wrote: > > Hi everyone, > > Here at Stanford Libraries we just ran an upgrade from 1.5.4 to version > 2.6.0 and noticed some odd behavior we?d like to validate with our peers. > We received no error messages while running the upgrade. That said, for > one of our repositories (we have many) we?ve noticed that by clicking on > the resource tree we get an error message. I?m speculating here but my > guess is that the extent for this resources were not defined in such a way > the application knows the relationship between parent and child. Here is > the error message we?re seeing. > > . > > For this particular example here is how our extents had been entered in > application. > > > > My questions are has anyone seen this sort of behavior before? Is this > something we can fix in the upgraded application or do we need to implement > a fix before the upgrade. Any insights anyone has on this issue would be > much appreciated! > > Michael > > > _______________________________________________ > 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 > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From mgolson at stanford.edu Wed Oct 16 18:17:32 2019 From: mgolson at stanford.edu (Michael G Olson) Date: Wed, 16 Oct 2019 22:17:32 +0000 Subject: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 In-Reply-To: References: <52BBC9F0-C64D-4FA0-AB92-8B6BC5CA89E7@virginia.edu> Message-ID: <1BF8771E-8D10-4CCA-BA0D-5E9A730BD68D@stanford.edu> Hi Alex, Great ideas, thank you! We didn?t get any errors when we ran the upgrade. I just took a look at this resource in the Java console. I didn?t see any obvious errors in the Java script consul but I was able to see the logic that should be generating the tree view. My best guess is that what is going on is that we were using extents on the collection resource in a way that was not actually intended. We also have a few examples where our archivist correctly encoded constituent parts as proper child objects and in these particular examples we don?t get a tree view error. Thanks for your help! Michael On Oct 16, 2019, at 2:39 PM, Alexander Duryee > wrote: Michael, Do you see anything interesting in the system logs or your browser's Javascript console when you try to open the collection? I don't see anything in the Extent record that you attached that would cause the Resource record to throw an error like that. Thanks, --Alex On Wed, Oct 16, 2019 at 3:25 PM Michael G Olson > wrote: Hi Steve, all, Sorry about that? the error message we?re receiving when we click on the Collection tree is, "Oops! We're having trouble fetching this tree. Please try refreshing the page.? If you open the image titled extent you'll see how our archivist entered the extent for this particular collection. It looks like this isn't really defined as a true child of the collection. thanks, Michael ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Wednesday, October 16, 2019 12:15 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 Error messages/images are too compressed or small to read. Just a blur. Can you resend or else transcribe ? ? Steve M. On Oct 16, 2019, at 2:52 PM, Michael G Olson > wrote: Hi everyone, Here at Stanford Libraries we just ran an upgrade from 1.5.4 to version 2.6.0 and noticed some odd behavior we?d like to validate with our peers. We received no error messages while running the upgrade. That said, for one of our repositories (we have many) we?ve noticed that by clicking on the resource tree we get an error message. I?m speculating here but my guess is that the extent for this resources were not defined in such a way the application knows the relationship between parent and child. Here is the error message we?re seeing. . For this particular example here is how our extents had been entered in application. My questions are has anyone seen this sort of behavior before? Is this something we can fix in the upgraded application or do we need to implement a fix before the upgrade. Any insights anyone has on this issue would be much appreciated! Michael _______________________________________________ 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 -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org _______________________________________________ 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 Wed Oct 16 21:35:57 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Thu, 17 Oct 2019 01:35:57 +0000 Subject: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 In-Reply-To: <1BF8771E-8D10-4CCA-BA0D-5E9A730BD68D@stanford.edu> References: <52BBC9F0-C64D-4FA0-AB92-8B6BC5CA89E7@virginia.edu> , <1BF8771E-8D10-4CCA-BA0D-5E9A730BD68D@stanford.edu> Message-ID: If you brought over the /data/ directory, try getting rid of everything in there and restarting. Could just be an index issue. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Michael G Olson Sent: Wednesday, October 16, 2019 6:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 Hi Alex, Great ideas, thank you! We didn?t get any errors when we ran the upgrade. I just took a look at this resource in the Java console. I didn?t see any obvious errors in the Java script consul but I was able to see the logic that should be generating the tree view. My best guess is that what is going on is that we were using extents on the collection resource in a way that was not actually intended. We also have a few examples where our archivist correctly encoded constituent parts as proper child objects and in these particular examples we don?t get a tree view error. Thanks for your help! Michael On Oct 16, 2019, at 2:39 PM, Alexander Duryee > wrote: Michael, Do you see anything interesting in the system logs or your browser's Javascript console when you try to open the collection? I don't see anything in the Extent record that you attached that would cause the Resource record to throw an error like that. Thanks, --Alex On Wed, Oct 16, 2019 at 3:25 PM Michael G Olson > wrote: Hi Steve, all, Sorry about that? the error message we?re receiving when we click on the Collection tree is, "Oops! We're having trouble fetching this tree. Please try refreshing the page.? If you open the image titled extent you'll see how our archivist entered the extent for this particular collection. It looks like this isn't really defined as a true child of the collection. thanks, Michael ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Wednesday, October 16, 2019 12:15 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 Error messages/images are too compressed or small to read. Just a blur. Can you resend or else transcribe ? ? Steve M. On Oct 16, 2019, at 2:52 PM, Michael G Olson > wrote: Hi everyone, Here at Stanford Libraries we just ran an upgrade from 1.5.4 to version 2.6.0 and noticed some odd behavior we?d like to validate with our peers. We received no error messages while running the upgrade. That said, for one of our repositories (we have many) we?ve noticed that by clicking on the resource tree we get an error message. I?m speculating here but my guess is that the extent for this resources were not defined in such a way the application knows the relationship between parent and child. Here is the error message we?re seeing. . For this particular example here is how our extents had been entered in application. My questions are has anyone seen this sort of behavior before? Is this something we can fix in the upgraded application or do we need to implement a fix before the upgrade. Any insights anyone has on this issue would be much appreciated! Michael _______________________________________________ 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 -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org _______________________________________________ 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 Thu Oct 17 09:09:40 2019 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Thu, 17 Oct 2019 13:09:40 +0000 Subject: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 In-Reply-To: References: <52BBC9F0-C64D-4FA0-AB92-8B6BC5CA89E7@virginia.edu> , <1BF8771E-8D10-4CCA-BA0D-5E9A730BD68D@stanford.edu>, Message-ID: Are there any children for this tree - ie any archival objects underneath? If not, this may be related to this issue: https://archivesspace.atlassian.net/browse/ANW-782 Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Blake Carver Sent: Wednesday, October 16, 2019 9:35 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 If you brought over the /data/ directory, try getting rid of everything in there and restarting. Could just be an index issue. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Michael G Olson Sent: Wednesday, October 16, 2019 6:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 Hi Alex, Great ideas, thank you! We didn?t get any errors when we ran the upgrade. I just took a look at this resource in the Java console. I didn?t see any obvious errors in the Java script consul but I was able to see the logic that should be generating the tree view. My best guess is that what is going on is that we were using extents on the collection resource in a way that was not actually intended. We also have a few examples where our archivist correctly encoded constituent parts as proper child objects and in these particular examples we don?t get a tree view error. Thanks for your help! Michael On Oct 16, 2019, at 2:39 PM, Alexander Duryee > wrote: Michael, Do you see anything interesting in the system logs or your browser's Javascript console when you try to open the collection? I don't see anything in the Extent record that you attached that would cause the Resource record to throw an error like that. Thanks, --Alex On Wed, Oct 16, 2019 at 3:25 PM Michael G Olson > wrote: Hi Steve, all, Sorry about that? the error message we?re receiving when we click on the Collection tree is, "Oops! We're having trouble fetching this tree. Please try refreshing the page.? If you open the image titled extent you'll see how our archivist entered the extent for this particular collection. It looks like this isn't really defined as a true child of the collection. thanks, Michael ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Majewski, Steven Dennis (sdm7g) > Sent: Wednesday, October 16, 2019 12:15 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0 Error messages/images are too compressed or small to read. Just a blur. Can you resend or else transcribe ? ? Steve M. On Oct 16, 2019, at 2:52 PM, Michael G Olson > wrote: Hi everyone, Here at Stanford Libraries we just ran an upgrade from 1.5.4 to version 2.6.0 and noticed some odd behavior we?d like to validate with our peers. We received no error messages while running the upgrade. That said, for one of our repositories (we have many) we?ve noticed that by clicking on the resource tree we get an error message. I?m speculating here but my guess is that the extent for this resources were not defined in such a way the application knows the relationship between parent and child. Here is the error message we?re seeing. . For this particular example here is how our extents had been entered in application. My questions are has anyone seen this sort of behavior before? Is this something we can fix in the upgraded application or do we need to implement a fix before the upgrade. Any insights anyone has on this issue would be much appreciated! Michael _______________________________________________ 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 -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org _______________________________________________ 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 dawne_lucas at unc.edu Thu Oct 17 10:29:49 2019 From: dawne_lucas at unc.edu (Lucas, Dawne Howard) Date: Thu, 17 Oct 2019 14:29:49 +0000 Subject: [Archivesspace_Users_Group] Related accession and resource links on agent records In-Reply-To: References: <52BBC9F0-C64D-4FA0-AB92-8B6BC5CA89E7@virginia.edu> , <1BF8771E-8D10-4CCA-BA0D-5E9A730BD68D@stanford.edu>, , Message-ID: Hi all, We recently migrated into ASpace from AT. I?ve been cleaning up agent records, and have noticed that some agent records don?t show which accession and resource records they are linked to. The resource and accession records indicate the link to the agent record, but not vice versa. Some of the agent records do display the links though, so I?m not sure why they appear on some records and not others. Have other people noticed this inconsistency, and is there an explanation for it? Thanks! -Dawne -- Dawne Howard Lucas, MA, MSLS she/her/hers Technical Services Archivist Wilson Special Collections Library University of North Carolina at Chapel Hill 200 South Road, CB# 3926 Chapel Hill, NC 27515 T: 919-966-1776 E: dawne_lucas at unc.edu Web: http://guides.lib.unc.edu/health-history ORCID: orcid.org/ 0000-0001-9657-8509 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rachel.donahue at lac-group.com Thu Oct 17 10:31:40 2019 From: rachel.donahue at lac-group.com (Rachel Donahue) Date: Thu, 17 Oct 2019 10:31:40 -0400 Subject: [Archivesspace_Users_Group] Related accession and resource links on agent records In-Reply-To: References: <52BBC9F0-C64D-4FA0-AB92-8B6BC5CA89E7@virginia.edu> <1BF8771E-8D10-4CCA-BA0D-5E9A730BD68D@stanford.edu> Message-ID: Do you by any chance have multiple repositories? Agents will only show related resources and accessions of the repository you currently have selected. --Rachel -- Please note that I currently *do not have access to ARS email*. If you need to contact me, use my LAC address: rachel.donahue at lac-group.com The information contained in this e-mail message is confidential. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you think that you have received this e-mail message in error, please contact the sender. On Thu, Oct 17, 2019 at 10:29 AM Lucas, Dawne Howard wrote: > Hi all, > > > > We recently migrated into ASpace from AT. I?ve been cleaning up agent > records, and have noticed that some agent records don?t show which > accession and resource records they are linked to. The resource and > accession records indicate the link to the agent record, but not vice > versa. Some of the agent records do display the links though, so I?m not > sure why they appear on some records and not others. > > > > Have other people noticed this inconsistency, and is there an explanation > for it? > > > > Thanks! > > -Dawne > > > > -- > > Dawne Howard Lucas, MA, MSLS > > she/her/hers > > Technical Services Archivist > > Wilson Special Collections Library > > University of North Carolina at Chapel Hill > > 200 South Road, CB# 3926 > > Chapel Hill, NC 27515 > > T: 919-966-1776 > > E: dawne_lucas at unc.edu > > Web: http://guides.lib.unc.edu/health-history > > ORCID: orcid.org/ 0000-0001-9657-8509 > > > _______________________________________________ > 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 dawne_lucas at unc.edu Thu Oct 17 10:32:25 2019 From: dawne_lucas at unc.edu (Lucas, Dawne Howard) Date: Thu, 17 Oct 2019 14:32:25 +0000 Subject: [Archivesspace_Users_Group] Related accession and resource links on agent records In-Reply-To: References: <52BBC9F0-C64D-4FA0-AB92-8B6BC5CA89E7@virginia.edu> <1BF8771E-8D10-4CCA-BA0D-5E9A730BD68D@stanford.edu> , Message-ID: Thanks, Rachel. We only have one repository. -Dawne -- Dawne Howard Lucas, MA, MSLS she/her/hers Technical Services Archivist Wilson Special Collections Library University of North Carolina at Chapel Hill 200 South Road, CB# 3926 Chapel Hill, NC 27515 T: 919-966-1776 E: dawne_lucas at unc.edu Web: http://guides.lib.unc.edu/health-history ORCID: orcid.org/ 0000-0001-9657-8509 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Rachel Donahue Sent: Thursday, October 17, 2019 10:31:40 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Related accession and resource links on agent records Do you by any chance have multiple repositories? Agents will only show related resources and accessions of the repository you currently have selected. --Rachel -- Please note that I currently do not have access to ARS email. If you need to contact me, use my LAC address: rachel.donahue at lac-group.com The information contained in this e-mail message is confidential. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you think that you have received this e-mail message in error, please contact the sender. On Thu, Oct 17, 2019 at 10:29 AM Lucas, Dawne Howard > wrote: Hi all, We recently migrated into ASpace from AT. I?ve been cleaning up agent records, and have noticed that some agent records don?t show which accession and resource records they are linked to. The resource and accession records indicate the link to the agent record, but not vice versa. Some of the agent records do display the links though, so I?m not sure why they appear on some records and not others. Have other people noticed this inconsistency, and is there an explanation for it? Thanks! -Dawne -- Dawne Howard Lucas, MA, MSLS she/her/hers Technical Services Archivist Wilson Special Collections Library University of North Carolina at Chapel Hill 200 South Road, CB# 3926 Chapel Hill, NC 27515 T: 919-966-1776 E: dawne_lucas at unc.edu Web: http://guides.lib.unc.edu/health-history ORCID: orcid.org/ 0000-0001-9657-8509 _______________________________________________ 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 Mon Oct 21 11:59:15 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 21 Oct 2019 15:59:15 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: Integrating ArchivesSpace and Aeon Message-ID: ArchivesSpace is pleased to announce the second webinar in our new webinar series focused on Integrations with ArchivesSpace. Each webinar in this series will highlight an integration with another application used in archives that ArchivesSpace members have worked on or requested. The webinar series will feature both open source and proprietary systems. Our second webinar in this series will feature an ArchivesSpace integration with Aeon, an automated request and workflow management software specifically designed for special collections libraries and archives from Atlas Systems. When: November 6, 2019 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? noon PT; 7 p.m. ? 8 p.m. BST) Where: Zoom https://lyrasis.zoom.us/j/582583780 Meeting ID: 582 583 780 One tap mobile +19292056099,,582583780# US (New York) +16699006833,,582583780# US (San Jose) Dial by your location +1 929 205 6099 US (New York) +1 669 900 6833 US (San Jose) 877 853 5257 US Toll-free 888 475 4499 US Toll-free Meeting ID: 582 583 780 Find your local number: https://zoom.us/u/awkFNWPxh Webinar description: This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Katie Gillespie (Atlas Systems) will present the Aeon and ArchivesSpace integration request plugin and discuss the different ways this plugin has been deployed at individual institutions. Katie will also discuss development work that is currently being planned to expand and improve the plugin and the accompanying Aeon client addon. A discussion will follow. Current users of the plugin, as well as those who have integrated Aeon and ArchivesSpace at their own institution through other workflows, are encouraged to attend and offer insight into their own integrations, lessons learned and plans for the future. Users who are interested in integrating Aeon and ArchivesSpace are also encouraged to attend and offer insight into their own needs and initial feedback on the proposed plugin improvements. Presenters: Katie Gillespie is the Special Collections & Archives Program Manager at Atlas Systems. She works with current and new Aeon sites on implementation and training. She also serves as the Aeon Product Lead, working as a liaison for customer requests and enhancements to help drive Aeon development. Katie received her MLIS from Simmons College in 2015 and her Bachelor?s from Ohio University. Who should attend: Anyone interested in possibilities for integrating ArchivesSpace with Aeon, those who have integrated ArchivesSpace and Aeon and would like to offer insight to others, and those who are interested in getting ideas for building an integration workflow. Questions? Contact Jessica at jessica.crouch at lyrasis.org if you have questions about this webinar or the Integrations with ArchivesSpace webinar series. The next Integrations with ArchivesSpace webinar will be: Integrating ArchivesSpace with Archive-It, December 4, 2019, at 2pm ET (11am PT) Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29060 bytes Desc: image001.jpg URL: From Jessica.Crouch at lyrasis.org Tue Oct 22 09:27:44 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 22 Oct 2019 13:27:44 +0000 Subject: [Archivesspace_Users_Group] Reminder - Webinar Tomorrow: Batch editing barcodes through the ArchivesSpace API Message-ID: <36660F0E-F65D-48C9-B009-34DCEAF3C494@lyrasis.org> Webinar Announcement: Batch editing barcodes through the ArchivesSpace API When: Wednesday, October 23, 2019 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? noon PT) Where: https://lyrasis.zoom.us/j/555121121 Dial In: One tap mobile +19292056099,,555121121# US (New York) +16699006833,,555121121# US (San Jose) Dial by your location +1 929 205 6099 US (New York) +1 669 900 6833 US (San Jose) 888 475 4499 US Toll-free 877 853 5257 US Toll-free Meeting ID: 555 121 121 Find your local number: https://zoom.us/u/awkFNWPxh No registration required. The webinar will be recorded and available for viewing at a later date on the ArchivesSpace YouTube channel. Webinar Description: Vakil Smallen, International Brotherhood of Teamsters Labor History Archivist at George Washington University, will walk through the steps of a workflow developed at GWU for batch editing barcodes in ArchivesSpace through the API. As a person with a limited technical background, Vakil will discuss how he found a solution to a common problem using tools previously unknown to him. He?ll offer ideas for others to get confidence and learn more when wading into similarly unfamiliar waters. Webinar Resources: Vakil originally highlighted this workflow in a blog post for the Research Libraries Section of SAA. There he includes all programs and resources he used in this process. Vakil will be using Python 3.7 in Jupyter Notebook as available in the Anaconda suite and OpenRefine in this demonstration. The Python scripts used in this webinar are posted to GitHub and available here: https://github.com/gwu-libraries/aspace-scripts/blob/master/jupyter_notebooks/nea_barcodes/Get_Top_Containers%20from%20One%20Collection-Anonymized.ipynb https://github.com/gwu-libraries/aspace-scripts/blob/master/jupyter_notebooks/nea_barcodes/Merge%20Two%20CSV%20files%20with%20a%20common%20data%20point%20for%20Github.ipynb https://github.com/gwu-libraries/aspace-scripts/blob/master/jupyter_notebooks/nea_barcodes/Post%20Barcodes%20Base%20Script.ipynb Presenter: Vakil Smallen is the International Brotherhood of Teamsters Labor History Archivist at George Washington University, a position he has held since April 2019. Before that, he was the National Education Association Project Archivist at George Washington University for 8 years. He received his MLS from the University of Maryland. Vakil's undergraduate degree was in English Literature and Language. Who should attend: Anyone interested in seeing a demonstration of a process for batch editing barcodes through the API. This webinar may be particularly useful for archivists who do not have a deep technical background and are looking for a simple workflow for making batch edits. Questions? Please contact Jessica at jessica.crouch at lyrasis.org Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [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 ltang5 at msu.edu Thu Oct 24 12:00:07 2019 From: ltang5 at msu.edu (Tang, Lydia) Date: Thu, 24 Oct 2019 16:00:07 +0000 Subject: [Archivesspace_Users_Group] merging ArchivesSpace instances and LCNAF genres plug in questions Message-ID: Hello, all! My institution will be starting a project to migrate our two separate ArchivesSpace instances into a single, shared instance (maintaining multiple repositories). Has anyone else attempted this? I have a feeling that it will involve a lot of API work and challenges may include: * Reconciling duplicate/slightly varying Agents and Subjects * Potentially losing events, background jobs, and locations of the instance that is migrated * Potentially losing date and creator information of migrated objects (maybe?) * Anything else? It?s an unenviable project, but it will hopefully be beneficial! I?ve submitted a Jira ticket about a database migrator ? if people have thoughts and opinions, please feel free to comment on this or the list! https://archivesspace.atlassian.net/browse/ANW-884 On a slightly related note, do people have ideas on how to assess and compare agents and subjects for reconciliation?: On a slightly further afield question (and unfortunately, one that I?m passing along for a colleague but that I personally don?t have experience with), I wanted to ask if anyone has been able to tweak the LCNAF plug in to direct it to genre terms as well? Thanks for your thoughts and help! Lydia -- Dr. Lydia Tang, CA, DAS, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Librarian Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 She/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From npwb2 at cam.ac.uk Mon Oct 28 08:14:09 2019 From: npwb2 at cam.ac.uk (Nick Butler) Date: Mon, 28 Oct 2019 12:14:09 +0000 Subject: [Archivesspace_Users_Group] Is it possible to customise the OAI-PMH feeds? Message-ID: <4eeaef558dee6dfbddb69c9fcd4578b78f79101c.camel@cam.ac.uk> Hi all, Is it possible to customise, say, the oai_dc feed to include more information (e.g. notes fields)? This would allow us to pipe records directly into our Primo discovery layer without having to export them as oai_ead and convert them as a separate step. I've found the oai_dc.rb file but changes to this file don't appear to persist beyond the next time ArchivesSpace is restarted. Many thanks in advance for any advice. Best wishes, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From boze.1 at nd.edu Mon Oct 28 10:09:07 2019 From: boze.1 at nd.edu (Andy Boze) Date: Mon, 28 Oct 2019 10:09:07 -0400 Subject: [Archivesspace_Users_Group] Is it possible to customise the OAI-PMH feeds? In-Reply-To: <4eeaef558dee6dfbddb69c9fcd4578b78f79101c.camel@cam.ac.uk> References: <4eeaef558dee6dfbddb69c9fcd4578b78f79101c.camel@cam.ac.uk> Message-ID: <288b094b-cf16-7a87-f051-772c52d6ca13@nd.edu> Hi, Nick. Do you need to work with DC records? We recently started harvesting records directly into Primo from ArchivesSpace using oai-ead. It's working very well. Before we started using ASpace a year ago, we did have to export the records from our previous system to EAD and then import them into Primo. You can see our records in Primo at < https://ndu-primo-stage.hosted.exlibrisgroup.com/primo-explore/search?query=any,contains,ndu_aspace*&tab=nd_campus&search_scope=nd_campus&vid=NDU&lang=en_US&offset=0 >. This is our test system, as we're still tinkering with the display of the records. Andy On 10/28/19 8:14 AM, Nick Butler wrote: > Hi all, > > Is it possible to customise, say, the oai_dc feed to include more information (e.g. notes fields)? This would allow us to pipe records directly into our Primo discovery layer without having to export them as oai_ead and convert them as a separate step. > > I've found the oai_dc.rb file but changes to this file don't appear to persist beyond the next time ArchivesSpace is restarted. > > Many thanks in advance for any advice. > > Best wishes, > Nick > > -- > > Nick Butler > Software Developer > Digital Services > Cambridge University Library > West Road > Cambridge CB3 9DR, UK > > npwb2 at cam.ac.uk > > Internal tel: 33067 > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Andy Boze, Associate Librarian University of Notre Dame 271H Hesburgh Library (574) 631-8708 From andrew.morrison at bodleian.ox.ac.uk Mon Oct 28 10:49:57 2019 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Mon, 28 Oct 2019 14:49:57 +0000 Subject: [Archivesspace_Users_Group] Is it possible to customise the OAI-PMH feeds? In-Reply-To: <4eeaef558dee6dfbddb69c9fcd4578b78f79101c.camel@cam.ac.uk> References: <4eeaef558dee6dfbddb69c9fcd4578b78f79101c.camel@cam.ac.uk> Message-ID: <1572274197.7643.22.camel@bodleian.ox.ac.uk> If you do want to modify oai_dc.rb, you either need to do so to a fork of the source then build your own production system, or monkey patch the OAIDCMapper class via a plug-in containing a backend/plugin_init.rb Andrew. On Mon, 2019-10-28 at 12:14 +0000, Nick Butler wrote: Hi all, Is it possible to customise, say, the oai_dc feed to include more information (e.g. notes fields)? This would allow us to pipe records directly into our Primo discovery layer without having to export them as oai_ead and convert them as a separate step. I've found the oai_dc.rb file but changes to this file don't appear to persist beyond the next time ArchivesSpace is restarted. Many thanks in advance for any advice. Best wishes, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ 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 npwb2 at cam.ac.uk Mon Oct 28 11:53:32 2019 From: npwb2 at cam.ac.uk (Nick Butler) Date: Mon, 28 Oct 2019 15:53:32 +0000 Subject: [Archivesspace_Users_Group] Is it possible to customise the OAI-PMH feeds? In-Reply-To: <288b094b-cf16-7a87-f051-772c52d6ca13@nd.edu> References: <4eeaef558dee6dfbddb69c9fcd4578b78f79101c.camel@cam.ac.uk> <288b094b-cf16-7a87-f051-772c52d6ca13@nd.edu> Message-ID: <5340cca303b05029158f83069f89be6f3dfc0b57.camel@cam.ac.uk> Hi Andy, Thank you very much for your message! No, there's no reason we need to work with DC records, but I hadn't realised Primo was capable of receiving EAD records. Did you happen to come across any documentation for this? I'm assuming we'd need a custom Primo splitter for this? Many thanks, Nick -----Original Message----- From: Andy Boze > Reply-To: Boze.1 at nd.edu, Archivesspace Users Group > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Is it possible to customise the OAI-PMH feeds? Date: Mon, 28 Oct 2019 10:09:07 -0400 Hi, Nick. Do you need to work with DC records? We recently started harvesting records directly into Primo from ArchivesSpace using oai-ead. It's working very well. Before we started using ASpace a year ago, we did have to export the records from our previous system to EAD and then import them into Primo. You can see our records in Primo at < https://ndu-primo-stage.hosted.exlibrisgroup.com/primo-explore/search?query=any,contains,ndu_aspace*&tab=nd_campus&search_scope=nd_campus&vid=NDU&lang=en_US&offset=0 >. This is our test system, as we're still tinkering with the display of the records. Andy On 10/28/19 8:14 AM, Nick Butler wrote: Hi all, Is it possible to customise, say, the oai_dc feed to include more information (e.g. notes fields)? This would allow us to pipe records directly into our Primo discovery layer without having to export them as oai_ead and convert them as a separate step. I've found the oai_dc.rb file but changes to this file don't appear to persist beyond the next time ArchivesSpace is restarted. Many thanks in advance for any advice. Best wishes, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk> Internal tel: 33067 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From npwb2 at cam.ac.uk Mon Oct 28 12:14:04 2019 From: npwb2 at cam.ac.uk (Nick Butler) Date: Mon, 28 Oct 2019 16:14:04 +0000 Subject: [Archivesspace_Users_Group] Is it possible to customise the OAI-PMH feeds? In-Reply-To: <1572274197.7643.22.camel@bodleian.ox.ac.uk> References: <4eeaef558dee6dfbddb69c9fcd4578b78f79101c.camel@cam.ac.uk> <1572274197.7643.22.camel@bodleian.ox.ac.uk> Message-ID: <5002ee3b54fc12fc61e10476030c01c8731a2de3.camel@cam.ac.uk> Hi Andrew, Thank you very much for this approach - a quick monkey patch works perfectly! If it's possible to get Primo to accept EAD then we'll probably try to go down that route (we may be in the same situation with other OAI providers at a later date), but this is precisely what I asked for and may end up being very useful indeed. Best wishes, Nick -----Original Message----- From: Andrew Morrison > Reply-To: Archivesspace Users Group > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Is it possible to customise the OAI-PMH feeds? Date: Mon, 28 Oct 2019 14:49:57 +0000 If you do want to modify oai_dc.rb, you either need to do so to a fork of the source then build your own production system, or monkey patch the OAIDCMapper class via a plug-in containing a backend/plugin_init.rb Andrew. On Mon, 2019-10-28 at 12:14 +0000, Nick Butler wrote: Hi all, Is it possible to customise, say, the oai_dc feed to include more information (e.g. notes fields)? This would allow us to pipe records directly into our Primo discovery layer without having to export them as oai_ead and convert them as a separate step. I've found the oai_dc.rb file but changes to this file don't appear to persist beyond the next time ArchivesSpace is restarted. Many thanks in advance for any advice. Best wishes, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ 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 -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From boze.1 at nd.edu Mon Oct 28 12:29:38 2019 From: boze.1 at nd.edu (Andy Boze) Date: Mon, 28 Oct 2019 12:29:38 -0400 Subject: [Archivesspace_Users_Group] Is it possible to customise the OAI-PMH feeds? In-Reply-To: <5340cca303b05029158f83069f89be6f3dfc0b57.camel@cam.ac.uk> References: <4eeaef558dee6dfbddb69c9fcd4578b78f79101c.camel@cam.ac.uk> <288b094b-cf16-7a87-f051-772c52d6ca13@nd.edu> <5340cca303b05029158f83069f89be6f3dfc0b57.camel@cam.ac.uk> Message-ID: Hi, Nick. You can use the standard OAI splitter in Primo regardless of the metadata format you've selected for ArchivesSpace to send. The OAI-PMH record structure is the same for any of the formats. See < http://www.openarchives.org/OAI/openarchivesprotocol.html >. You'll just use your normalization rules to deal with whatever format you've chosen. I hope this helps. Let me know if you need more details. Andy On 10/28/19 11:53 AM, Nick Butler wrote: > Hi Andy, > > Thank you very much for your message! No, there's no reason we need to work with DC records, but I hadn't realised Primo was capable of receiving EAD records. Did you happen to come across any documentation for this? I'm assuming we'd need a custom Primo splitter for this? > > Many thanks, > Nick > > -----Original Message----- > From: Andy Boze > > Reply-To: Boze.1 at nd.edu, Archivesspace Users Group > > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] Is it possible to customise the OAI-PMH feeds? > Date: Mon, 28 Oct 2019 10:09:07 -0400 > > > Hi, Nick. > > > Do you need to work with DC records? We recently started harvesting > > records directly into Primo from ArchivesSpace using oai-ead. It's > > working very well. Before we started using ASpace a year ago, we did > > have to export the records from our previous system to EAD and then > > import them into Primo. > > > You can see our records in Primo at < > > https://ndu-primo-stage.hosted.exlibrisgroup.com/primo-explore/search?query=any,contains,ndu_aspace*&tab=nd_campus&search_scope=nd_campus&vid=NDU&lang=en_US&offset=0 > > >. This is our test system, as we're still tinkering with the display > > of the records. > > > Andy > > > On 10/28/19 8:14 AM, Nick Butler wrote: > > Hi all, > > > Is it possible to customise, say, the oai_dc feed to include more information (e.g. notes fields)? This would allow us to pipe records directly into our Primo discovery layer without having to export them as oai_ead and convert them as a separate step. > > > I've found the oai_dc.rb file but changes to this file don't appear to persist beyond the next time ArchivesSpace is restarted. > > > Many thanks in advance for any advice. > > > Best wishes, > > Nick > > > -- > > > Nick Butler > > Software Developer > > Digital Services > > Cambridge University Library > > West Road > > Cambridge CB3 9DR, UK > > > npwb2 at cam.ac.uk> > > > Internal tel: 33067 > > > > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > > Nick Butler > Software Developer > Digital Services > Cambridge University Library > West Road > Cambridge CB3 9DR, UK > > npwb2 at cam.ac.uk > > Internal tel: 33067 > -- Andy Boze, Associate Librarian University of Notre Dame 271H Hesburgh Library (574) 631-8708 From kstrosch at wellesley.edu Mon Oct 28 15:52:38 2019 From: kstrosch at wellesley.edu (Kara Hart) Date: Mon, 28 Oct 2019 15:52:38 -0400 Subject: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI? Message-ID: Hi all, I want to be able to add static web pages to ArchivesSpace. I'd like to incorporate the header, top nav, and footer and be able to just add what I want in the middle. I'm basically hoping to create general FAQ, search help, about pages that live in my ArchivesSpace local plugin. Is this possible? I did find a way to add a page by putting a .html doc into /archivesspace/plugins/local/public/assets, but I have to manually copy in the head, navigation, header, and footer, which is obviously not ideal for updating and probably other reasons. If there isn't a way to do this, where is the proper place to suggest this enhancement? Should I create a new feature request in Jira the project ANW? ( https://archivesspace.atlassian.net/projects/ANW/issues/?filter=allissues&=) Thanks for any help, Kara ~~~ Kara S. Hart Systems Librarian - Library & Technology Services - Wellesley College -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at hudmol.com Mon Oct 28 18:02:16 2019 From: james at hudmol.com (James Bullen) Date: Mon, 28 Oct 2019 18:02:16 -0400 Subject: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI? In-Reply-To: References: Message-ID: <179E90E2-E4C7-40C4-8D7A-40DFBE49ACE3@hudmol.com> Hi Kara, This seemed like a useful thing that I don?t think exists yet, so I made a plugin to do it: https://github.com/hudmol/static_pages Maybe it can be a useful starting point. Cheers, James > On Oct 28, 2019, at 3:52 PM, Kara Hart wrote: > > Hi all, > I want to be able to add static web pages to ArchivesSpace. I'd like to incorporate the header, top nav, and footer and be able to just add what I want in the middle. I'm basically hoping to create general FAQ, search help, about pages that live in my ArchivesSpace local plugin. Is this possible? > > I did find a way to add a page by putting a .html doc into /archivesspace/plugins/local/public/assets, but I have to manually copy in the head, navigation, header, and footer, which is obviously not ideal for updating and probably other reasons. > > If there isn't a way to do this, where is the proper place to suggest this enhancement? Should I create a new feature request in Jira the project ANW? (https://archivesspace.atlassian.net/projects/ANW/issues/?filter=allissues&= ) > > Thanks for any help, > Kara > > > ~~~ Kara S. Hart > Systems Librarian - Library & Technology Services - Wellesley College > > > !DSPAM:5db7471d288581084719066! _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:5db7471d288581084719066! -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at hudmol.com Tue Oct 29 09:35:08 2019 From: james at hudmol.com (James Bullen) Date: Tue, 29 Oct 2019 09:35:08 -0400 Subject: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI? In-Reply-To: <179E90E2-E4C7-40C4-8D7A-40DFBE49ACE3@hudmol.com> References: <179E90E2-E4C7-40C4-8D7A-40DFBE49ACE3@hudmol.com> Message-ID: <1AACCB05-0F3A-4F7C-AC52-B980C96B49D9@hudmol.com> Just a quick follow up on this, I had misread the spec and only provided the static page facility on the staff interface - should have been on the PUI. Andrew Morrison noticed my oops and corrected it, so now it should work on both. Cheers, James > On Oct 28, 2019, at 6:02 PM, James Bullen wrote: > > > Hi Kara, > > This seemed like a useful thing that I don?t think exists yet, so I made a plugin to do it: > > https://github.com/hudmol/static_pages > > Maybe it can be a useful starting point. > > > Cheers, > James > > > >> On Oct 28, 2019, at 3:52 PM, Kara Hart > wrote: >> >> Hi all, >> I want to be able to add static web pages to ArchivesSpace. I'd like to incorporate the header, top nav, and footer and be able to just add what I want in the middle. I'm basically hoping to create general FAQ, search help, about pages that live in my ArchivesSpace local plugin. Is this possible? >> >> I did find a way to add a page by putting a .html doc into /archivesspace/plugins/local/public/assets, but I have to manually copy in the head, navigation, header, and footer, which is obviously not ideal for updating and probably other reasons. >> >> If there isn't a way to do this, where is the proper place to suggest this enhancement? Should I create a new feature request in Jira the project ANW? (https://archivesspace.atlassian.net/projects/ANW/issues/?filter=allissues&= ) >> >> Thanks for any help, >> Kara >> >> >> ~~~ Kara S. Hart >> Systems Librarian - Library & Technology Services - Wellesley College >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> !DSPAM:5db7471d288581084719066! > > !DSPAM:5db76577327211158617254! _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:5db76577327211158617254! -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.morrison at bodleian.ox.ac.uk Tue Oct 29 10:54:40 2019 From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison) Date: Tue, 29 Oct 2019 14:54:40 +0000 Subject: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI? In-Reply-To: <1AACCB05-0F3A-4F7C-AC52-B980C96B49D9@hudmol.com> References: <179E90E2-E4C7-40C4-8D7A-40DFBE49ACE3@hudmol.com> <1AACCB05-0F3A-4F7C-AC52-B980C96B49D9@hudmol.com> Message-ID: <1572360874.7643.73.camel@bodleian.ox.ac.uk> Hi James, Your original version will be useful to us, because we're probably going to want to add extra help pages to our staff interface for cataloguers transferring over from Archivists' Toolkit. And reading the static HTML from a file instead of building from ERB templates means they can be updated without restarting the service. Andrew. On Tue, 2019-10-29 at 09:35 -0400, James Bullen wrote: Just a quick follow up on this, I had misread the spec and only provided the static page facility on the staff interface - should have been on the PUI. Andrew Morrison noticed my oops and corrected it, so now it should work on both. Cheers, James On Oct 28, 2019, at 6:02 PM, James Bullen > wrote: Hi Kara, This seemed like a useful thing that I don?t think exists yet, so I made a plugin to do it: https://github.com/hudmol/static_pages Maybe it can be a useful starting point. Cheers, James On Oct 28, 2019, at 3:52 PM, Kara Hart > wrote: Hi all, I want to be able to add static web pages to ArchivesSpace. I'd like to incorporate the header, top nav, and footer and be able to just add what I want in the middle. I'm basically hoping to create general FAQ, search help, about pages that live in my ArchivesSpace local plugin. Is this possible? I did find a way to add a page by putting a .html doc into /archivesspace/plugins/local/public/assets, but I have to manually copy in the head, navigation, header, and footer, which is obviously not ideal for updating and probably other reasons. If there isn't a way to do this, where is the proper place to suggest this enhancement? Should I create a new feature request in Jira the project ANW? (https://archivesspace.atlassian.net/projects/ANW/issues/?filter=allissues&=) Thanks for any help, Kara ~~~ Kara S. Hart Systems Librarian - Library & Technology Services - Wellesley College _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group !DSPAM:5db7471d288581084719066! !DSPAM:5db76577327211158617254! _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group !DSPAM:5db76577327211158617254! _______________________________________________ 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 mmcderm2 at bowdoin.edu Tue Oct 29 13:00:25 2019 From: mmcderm2 at bowdoin.edu (Mike McDermott) Date: Tue, 29 Oct 2019 17:00:25 +0000 Subject: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI? In-Reply-To: <1572360874.7643.73.camel@bodleian.ox.ac.uk> References: <179E90E2-E4C7-40C4-8D7A-40DFBE49ACE3@hudmol.com> <1AACCB05-0F3A-4F7C-AC52-B980C96B49D9@hudmol.com> <1572360874.7643.73.camel@bodleian.ox.ac.uk> Message-ID: This looks really cool. But ? What am I doing wrong. When I put html in the file to be included, it comes out on the page looking like this: <div class="row>"> <h2>This is a test</h2> <p>This is always a test</p> <p>Tests are what I do.</p> <h3>here is a heading</h3> <p>This is always a test</p> <p>Tests are what I do.</p> <h3>here is a heading</h3> <p>This is always a test</p> <p>Tests are what I do.</p> </div> So it is rendered on the page as looking like html code instead of the page elements. Mike McDermott From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Andrew Morrison Sent: Tuesday, October 29, 2019 10:55 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI? Hi James, Your original version will be useful to us, because we're probably going to want to add extra help pages to our staff interface for cataloguers transferring over from Archivists' Toolkit. And reading the static HTML from a file instead of building from ERB templates means they can be updated without restarting the service. Andrew. On Tue, 2019-10-29 at 09:35 -0400, James Bullen wrote: Just a quick follow up on this, I had misread the spec and only provided the static page facility on the staff interface - should have been on the PUI. Andrew Morrison noticed my oops and corrected it, so now it should work on both. Cheers, James On Oct 28, 2019, at 6:02 PM, James Bullen > wrote: Hi Kara, This seemed like a useful thing that I don?t think exists yet, so I made a plugin to do it: https://github.com/hudmol/static_pages Maybe it can be a useful starting point. Cheers, James On Oct 28, 2019, at 3:52 PM, Kara Hart > wrote: Hi all, I want to be able to add static web pages to ArchivesSpace. I'd like to incorporate the header, top nav, and footer and be able to just add what I want in the middle. I'm basically hoping to create general FAQ, search help, about pages that live in my ArchivesSpace local plugin. Is this possible? I did find a way to add a page by putting a .html doc into /archivesspace/plugins/local/public/assets, but I have to manually copy in the head, navigation, header, and footer, which is obviously not ideal for updating and probably other reasons. If there isn't a way to do this, where is the proper place to suggest this enhancement? Should I create a new feature request in Jira the project ANW? (https://archivesspace.atlassian.net/projects/ANW/issues/?filter=allissues&=) Thanks for any help, Kara ~~~ Kara S. Hart Systems Librarian - Library & Technology Services - Wellesley College _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group !DSPAM:5db7471d288581084719066! !DSPAM:5db76577327211158617254! _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group !DSPAM:5db76577327211158617254! _______________________________________________ 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 james at hudmol.com Tue Oct 29 13:05:02 2019 From: james at hudmol.com (James Bullen) Date: Tue, 29 Oct 2019 13:05:02 -0400 Subject: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI? In-Reply-To: References: <179E90E2-E4C7-40C4-8D7A-40DFBE49ACE3@hudmol.com> <1AACCB05-0F3A-4F7C-AC52-B980C96B49D9@hudmol.com> <1572360874.7643.73.camel@bodleian.ox.ac.uk> Message-ID: <47E757FB-5C6C-4132-A57D-7A23DD4B7D24@hudmol.com> That?s funny - shows how much testing I did. Should be good now. > On Oct 29, 2019, at 1:00 PM, Mike McDermott wrote: > > This looks really cool. > But ? What am I doing wrong. > When I put html in the file to be included, it comes out on the page looking like this: > > <div class="row>"> > <h2>This is a test</h2> > <p>This is always a test</p> > <p>Tests are what I do.</p> > <h3>here is a heading</h3> > <p>This is always a test</p> > <p>Tests are what I do.</p> > <h3>here is a heading</h3> > <p>This is always a test</p> > <p>Tests are what I do.</p> > </div> > > So it is rendered on the page as looking like html code instead of the page elements. > > Mike McDermott > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Andrew Morrison > Sent: Tuesday, October 29, 2019 10:55 AM > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI? > > Hi James, > > Your original version will be useful to us, because we're probably going to want to add extra help pages to our staff interface for cataloguers transferring over from Archivists' Toolkit. And reading the static HTML from a file instead of building from ERB templates means they can be updated without restarting the service. > > Andrew. > > > On Tue, 2019-10-29 at 09:35 -0400, James Bullen wrote: > > Just a quick follow up on this, > > I had misread the spec and only provided the static page facility on the staff interface - should have been on the PUI. Andrew Morrison noticed my oops and corrected it, so now it should work on both. > > > Cheers, > James > > > > On Oct 28, 2019, at 6:02 PM, James Bullen > wrote: > > > Hi Kara, > > This seemed like a useful thing that I don?t think exists yet, so I made a plugin to do it: > > https://github.com/hudmol/static_pages > > Maybe it can be a useful starting point. > > > Cheers, > James > > > > > On Oct 28, 2019, at 3:52 PM, Kara Hart > wrote: > > Hi all, > I want to be able to add static web pages to ArchivesSpace. I'd like to incorporate the header, top nav, and footer and be able to just add what I want in the middle. I'm basically hoping to create general FAQ, search help, about pages that live in my ArchivesSpace local plugin. Is this possible? > > I did find a way to add a page by putting a .html doc into /archivesspace/plugins/local/public/assets, but I have to manually copy in the head, navigation, header, and footer, which is obviously not ideal for updating and probably other reasons. > > If there isn't a way to do this, where is the proper place to suggest this enhancement? Should I create a new feature request in Jira the project ANW? (https://archivesspace.atlassian.net/projects/ANW/issues/?filter=allissues&= ) > > Thanks for any help, > Kara > > > ~~~ Kara S. Hart > Systems Librarian - Library & Technology Services > - > Wellesley College > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > !DSPAM:5db76577327211158617254! _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:5db76577327211158617254! > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group !DSPAM:5db8703835431594758647! _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:5db8703835431594758647! -------------- next part -------------- An HTML attachment was scrubbed... URL: From mmcderm2 at bowdoin.edu Tue Oct 29 14:18:57 2019 From: mmcderm2 at bowdoin.edu (Mike McDermott) Date: Tue, 29 Oct 2019 18:18:57 +0000 Subject: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI? In-Reply-To: <47E757FB-5C6C-4132-A57D-7A23DD4B7D24@hudmol.com> References: <179E90E2-E4C7-40C4-8D7A-40DFBE49ACE3@hudmol.com> <1AACCB05-0F3A-4F7C-AC52-B980C96B49D9@hudmol.com> <1572360874.7643.73.camel@bodleian.ox.ac.uk> <47E757FB-5C6C-4132-A57D-7A23DD4B7D24@hudmol.com> Message-ID: Nice ? looks good. Thanks! From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of James Bullen Sent: Tuesday, October 29, 2019 1:05 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI? That?s funny - shows how much testing I did. Should be good now. On Oct 29, 2019, at 1:00 PM, Mike McDermott > wrote: This looks really cool. But ? What am I doing wrong. When I put html in the file to be included, it comes out on the page looking like this: <div class="row>"> <h2>This is a test</h2> <p>This is always a test</p> <p>Tests are what I do.</p> <h3>here is a heading</h3> <p>This is always a test</p> <p>Tests are what I do.</p> <h3>here is a heading</h3> <p>This is always a test</p> <p>Tests are what I do.</p> </div> So it is rendered on the page as looking like html code instead of the page elements. Mike McDermott From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Andrew Morrison Sent: Tuesday, October 29, 2019 10:55 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI? Hi James, Your original version will be useful to us, because we're probably going to want to add extra help pages to our staff interface for cataloguers transferring over from Archivists' Toolkit. And reading the static HTML from a file instead of building from ERB templates means they can be updated without restarting the service. Andrew. On Tue, 2019-10-29 at 09:35 -0400, James Bullen wrote: Just a quick follow up on this, I had misread the spec and only provided the static page facility on the staff interface - should have been on the PUI. Andrew Morrison noticed my oops and corrected it, so now it should work on both. Cheers, James On Oct 28, 2019, at 6:02 PM, James Bullen > wrote: Hi Kara, This seemed like a useful thing that I don?t think exists yet, so I made a plugin to do it: https://github.com/hudmol/static_pages Maybe it can be a useful starting point. Cheers, James On Oct 28, 2019, at 3:52 PM, Kara Hart > wrote: Hi all, I want to be able to add static web pages to ArchivesSpace. I'd like to incorporate the header, top nav, and footer and be able to just add what I want in the middle. I'm basically hoping to create general FAQ, search help, about pages that live in my ArchivesSpace local plugin. Is this possible? I did find a way to add a page by putting a .html doc into /archivesspace/plugins/local/public/assets, but I have to manually copy in the head, navigation, header, and footer, which is obviously not ideal for updating and probably other reasons. If there isn't a way to do this, where is the proper place to suggest this enhancement? Should I create a new feature request in Jira the project ANW? (https://archivesspace.atlassian.net/projects/ANW/issues/?filter=allissues&=) Thanks for any help, Kara ~~~ Kara S. Hart Systems Librarian - Library & Technology Services - Wellesley College _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group !DSPAM:5db76577327211158617254! _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group !DSPAM:5db76577327211158617254! _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group !DSPAM:5db8703835431594758647! _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group !DSPAM:5db8703835431594758647! -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at msu.edu Tue Oct 29 15:17:36 2019 From: ltang5 at msu.edu (Tang, Lydia) Date: Tue, 29 Oct 2019 19:17:36 +0000 Subject: [Archivesspace_Users_Group] Announcing a Development Prioritization survey! Deadline November 20 Message-ID: Hello everyone, The Development Prioritization subteam is pleased to share a development prioritization survey with you! The goal of this survey is to inform the Development Prioritization subteam and Program Team of areas of the application that ArchivesSpace member institutions want prioritized for development in the next 2-3 years.** Please share your feedback! https://www.surveymonkey.com/r/WPZYHLX Please fill out the survey if you have any thoughts on which areas of ArchiveSpace should be prioritized in development. We will be extremely grateful for your participation by Wednesday, November 20. As always, please feel free to vote, comment, and create JIRA tickets with ideas on how to propel the program forward. Please reach out if you have any questions or concerns! Lydia Tang and Maggie Hughes, on behalf of the Development Prioritization subteam ** Small print: Please note that this survey does not include sections of the ArchivesSpace application that are not under the purview of the Development Prioritization subteam in its work with the ArchivesSpace Program Team, which include User and Technical Documentation, Integrations, Testing, and Metadata Standards. Additionally, the Agents Module of ArchivesSpace is not included in this survey as there is considerable work happening on this section of the application to provide better standards support -- a release with that work is expected in the next 6 months. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kws2126 at columbia.edu Wed Oct 30 13:44:07 2019 From: kws2126 at columbia.edu (Kevin W. Schlottmann) Date: Wed, 30 Oct 2019 13:44:07 -0400 Subject: [Archivesspace_Users_Group] Language data in 2.7.0 not exporting to EAD Message-ID: Hi all, We're testing 2.7.0 on our hosted dev instance, and we noticed that in the EAD export, the language of materials information (neither the encoded data nor the language note) is coming through in the EAD export. Is anyone else experiencing this? The MARC export appears to be work fine (008, 040$b, 041, 546 all seem to be exporting correctly). Best, Kevin -- Kevin Schlottmann Head of Archives Processing Rare Book & Manuscript Library Butler Library, Room 801 Columbia University 535 W. 114th St., New York, NY 10027 (212) 854-8483 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rachel.searcy at nyu.edu Thu Oct 31 08:57:29 2019 From: rachel.searcy at nyu.edu (Rachel Aileen Searcy) Date: Thu, 31 Oct 2019 08:57:29 -0400 Subject: [Archivesspace_Users_Group] Language data in 2.7.0 not exporting to EAD In-Reply-To: References: Message-ID: Hi Kevin, We are also currently testing 2.7.0 on a local dev instance and I can confirm that we are also experiencing an issue with the Language of Materials Note not exporting. I did test this on the 2.7.0 community sandbox and the records I exported there did show that note in the EAD. We also have a plugin that modifies our EAD export to work nicely with our finding aid publication and display mechanisms, which might explain our issues and I'm still investigating... Thanks for bringing this to attention! Rachel On Wed, Oct 30, 2019 at 1:44 PM Kevin W. Schlottmann wrote: > Hi all, > > We're testing 2.7.0 on our hosted dev instance, and we noticed that in the > EAD export, the language of materials information (neither the encoded data > nor the language note) is coming through in the EAD export. Is anyone else > experiencing this? > > The MARC export appears to be work fine (008, 040$b, 041, 546 all seem to > be exporting correctly). > > Best, > > Kevin > -- > Kevin Schlottmann > Head of Archives Processing > Rare Book & Manuscript Library > Butler Library, Room 801 > Columbia University > 535 W. 114th St., New York, NY 10027 > (212) 854-8483 > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=CUGD7S_0q8aCI95jC3EIOf4MHnhcmU3IfPexJGvSD3Y&s=WRGz2lv2MQg_qKhRZvKDeTtdI2QtNlezr4j9GpFFQPE&e= > -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu My pronouns are she/her -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Thu Oct 31 09:13:11 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 31 Oct 2019 13:13:11 +0000 Subject: [Archivesspace_Users_Group] Language data in 2.7.0 not exporting to EAD In-Reply-To: References: Message-ID: Hi Kevin and Rachel, Right now the behavior for language of materials is that controlled values are exported in EAD2002 when there is not language of materials note. If there is a language of materials note, that takes precedence and is all that comes out in the EAD. All language-related fields and notes come out in an EAD3 export. This was done according to a community specification. If you are seeing behavior different than that, it would be great to know if you notice any differences depending on what combination or number of language-related values are in the record. We?d like to hear from others (or the Metadata Standards subteam, though, since Kevin?s the leader of that group, I guess we are!) to confirm before making changes to this for a future release of ArchivesSpace. Feedback during the release candidate phase is always especially useful (an unsolicited plug for more community testing ?), but it?s appreciated at any time. In the interim, export behavior like this can be changed with a custom export plugin. It sounds like NYU already has one for EAD exports, and there are good examples to share from around the community (though I?d imagine all predate this recent language work). Because the languages area was reworked, some language-related fields now have different names or properties, so it would be a good time to update those custom export plugins to work with 2.7.0 and future versions in any case. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Rachel Aileen Searcy Sent: Thursday, October 31, 2019 8:57 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Language data in 2.7.0 not exporting to EAD Hi Kevin, We are also currently testing 2.7.0 on a local dev instance and I can confirm that we are also experiencing an issue with the Language of Materials Note not exporting. I did test this on the 2.7.0 community sandbox and the records I exported there did show that note in the EAD. We also have a plugin that modifies our EAD export to work nicely with our finding aid publication and display mechanisms, which might explain our issues and I'm still investigating... Thanks for bringing this to attention! Rachel On Wed, Oct 30, 2019 at 1:44 PM Kevin W. Schlottmann > wrote: Hi all, We're testing 2.7.0 on our hosted dev instance, and we noticed that in the EAD export, the language of materials information (neither the encoded data nor the language note) is coming through in the EAD export. Is anyone else experiencing this? The MARC export appears to be work fine (008, 040$b, 041, 546 all seem to be exporting correctly). Best, Kevin -- Kevin Schlottmann Head of Archives Processing Rare Book & Manuscript Library Butler Library, Room 801 Columbia University 535 W. 114th St., New York, NY 10027 (212) 854-8483 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=CUGD7S_0q8aCI95jC3EIOf4MHnhcmU3IfPexJGvSD3Y&s=WRGz2lv2MQg_qKhRZvKDeTtdI2QtNlezr4j9GpFFQPE&e= -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu My pronouns are she/her -------------- 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 gboggio at mitre.org Thu Oct 31 10:37:04 2019 From: gboggio at mitre.org (Boggio, Jerry) Date: Thu, 31 Oct 2019 14:37:04 +0000 Subject: [Archivesspace_Users_Group] Customizing Staff Side logo Message-ID: We are looking for help as to where to place our logo file for use on the Staff page. We followed the directions below, but our logo is not being found. We are able to use the logo on the Public page and are running ArchivesSpace version 2.6. There appears to be a typo in the following page http://archivesspace.github.io/archivesspace/user/theming-archivesspace/#Making-small-changes: The Staff Side logo will need a small plugin file and cannot be set in your config.rb file. This needs to be changed in the plugins/local/frontend/views/site/_branding.html.erb file. You'll most likely need to create one or more of the directories. Then create that _branding.html.erb file and paste in the following code:
<%= image_tag "archivesspace/archivesspace.small.png", :class=>"img-responsive" %>
Change the "archivesspace/archivesspace.small.png" to the path to your image /assets/images/logo.png and place your login the plugins/local/frontend/assets/images/ directory. You'll most likely need to create one or more of the directories. Note: the original page had "...place your login the..." which I assume that to mean "...place your logo in the...". We put the logo in the following location: /apps/archivesspace/plugins/local/frontend/assets/images/Mitre_Corp_Logo_small.png Created the following file: [archspc at archspcdev1 site]$ pwd /apps/archivesspace/plugins/local/frontend/views/site [archspc at archspcdev1 site]$ more _branding.html.erb
<%= image_tag "archivesspace/Mitre_Corp_Logo_small.png", :class=>"img-responsive" %>
[archspc at archspcdev1 site]$ This appears to be incorrect as when bringing up the Staff page no logo is displayed, but do see what appears to be a place holder on the page. Information from the log file /apps/archivesspace/logs/archivesspace.out: ************************************************************ Welcome to ArchivesSpace! You can now point your browser to http://localhost:8080 ************************************************************ I, [2019-10-31T09:44:47.829167 #62349] INFO -- : Thread-2016: Staff Indexer [2019-10-31 09:44:47 -0400] Index round complete I, [2019-10-31T09:45:03.362859 #62349] INFO -- : Started GET "/" for 10.14.244.173 at 2019-10-31 09:45:03 -0400 I, [2019-10-31T09:45:04.429697 #62349] INFO -- : Processing by WelcomeController#index as HTML I, [2019-10-31T09:45:05.983788 #62349] INFO -- : Rendering welcome/index.html.erb within layouts/application I, [2019-10-31T09:45:06.060828 #62349] INFO -- : Rendered shared/_flash_messages.html.erb (13.6ms) I, [2019-10-31T09:45:08.815583 #62349] INFO -- : Thread-2038: PUI Indexer [2019-10-31 09:45:08 -0400] Running index round I, [2019-10-31T09:45:10.396144 #62349] INFO -- : Rendered welcome/index.html.erb within layouts/application (4411.3ms) I, [2019-10-31T09:45:11.001334 #62349] INFO -- : Rendered shared/_header_user.html.erb (498.8ms) I, [2019-10-31T09:45:11.004587 #62349] INFO -- : Rendered shared/_header_global.html.erb (520.2ms) I, [2019-10-31T09:45:12.042084 #62349] INFO -- : Rendered /apps/archivesspace/plugins/local/frontend/views/site/_branding.html.erb (1016.8ms) I, [2019-10-31T09:45:13.317327 #62349] INFO -- : Thread-2038: PUI Indexer [2019-10-31 09:45:13 -0400] Index round complete I, [2019-10-31T09:45:14.038365 #62349] INFO -- : Rendered shared/_advanced_search.html.erb (445.0ms) I, [2019-10-31T09:45:14.039334 #62349] INFO -- : Rendered shared/_header_repository.html.erb (1953.5ms) I, [2019-10-31T09:45:14.235100 #62349] INFO -- : Rendered site/_footer.html.erb (168.5ms) I, [2019-10-31T09:45:14.417472 #62349] INFO -- : Rendered shared/_templates.html.erb (155.2ms) I, [2019-10-31T09:45:14.420458 #62349] INFO -- : Completed 200 OK in 9989ms (Views: 8484.9ms) I, [2019-10-31T09:45:17.830453 #62349] INFO -- : Thread-2016: Staff Indexer [2019-10-31 09:45:17 -0400] Running index round I, [2019-10-31T09:45:18.581338 #62349] INFO -- : Started GET "/images/archivesspace/Mitre_Corp_Logo_small.png" for 10.14.244.173 at 2019-10-31 09:45:18 -0400 F, [2019-10-31T09:45:18.665371 #62349] FATAL -- : F, [2019-10-31T09:45:18.666039 #62349] FATAL -- : ActionController::RoutingError (No route matches [GET] "/images/archivesspace/Mitre_Corp_Logo_small.png"): F, [2019-10-31T09:45:18.666471 #62349] FATAL -- : F, [2019-10-31T09:45:18.666913 #62349] FATAL -- : actionpack (5.0.7.2) lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call' actionpack (5.0.7.2) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call' railties (5.0.7.2) lib/rails/rack/logger.rb:36:in `call_app' railties (5.0.7.2) lib/rails/rack/logger.rb:24:in `block in call' activesupport (5.0.7.2) lib/active_support/tagged_logging.rb:69:in `block in tagged' activesupport (5.0.7.2) lib/active_support/tagged_logging.rb:26:in `tagged' activesupport (5.0.7.2) lib/active_support/tagged_logging.rb:69:in `tagged' railties (5.0.7.2) lib/rails/rack/logger.rb:24:in `call' actionpack (5.0.7.2) lib/action_dispatch/middleware/request_id.rb:24:in `call' rack (2.0.7) lib/rack/method_override.rb:22:in `call' rack (2.0.7) lib/rack/runtime.rb:22:in `call' activesupport (5.0.7.2) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call' actionpack (5.0.7.2) lib/action_dispatch/middleware/executor.rb:12:in `call' actionpack (5.0.7.2) lib/action_dispatch/middleware/static.rb:136:in `call' rack (2.0.7) lib/rack/sendfile.rb:111:in `call' railties (5.0.7.2) lib/rails/engine.rb:522:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' I, [2019-10-31T09:45:22.376691 #62349] INFO -- : Thread-2016: Staff Indexer [2019-10-31 09:45:22 -0400] Index round complete I, [2019-10-31T09:45:43.318504 #62349] INFO -- : Thread-2038: PUI Indexer [2019-10-31 09:45:43 -0400] Running index round I, [2019-10-31T09:45:45.941843 #62349] INFO -- : Thread-2038: PUI Indexer [2019-10-31 09:45:45 -0400] Index round complete Please advise where we may have placed our logo file, file formats supported for logos, or other directories are needed. Also, can the path used in the _branding.html.erb file be fully qualified so that we make sure we are getting the file from where we expect? Thank you! Gerard (Jerry) Boggio | MITRE Corporation | R504 - Collaboration & Info Management | 781-271-2719 | Bedford, MA | 2K132 -------------- next part -------------- An HTML attachment was scrubbed... URL: From npwb2 at cam.ac.uk Thu Oct 31 10:44:33 2019 From: npwb2 at cam.ac.uk (Nick Butler) Date: Thu, 31 Oct 2019 14:44:33 +0000 Subject: [Archivesspace_Users_Group] Customizing Staff Side logo In-Reply-To: References: Message-ID: <8cca4e292bbcd1d9c37e4130dbe01e3760a97f1f.camel@cam.ac.uk> Hi Jerry, You need the path starting from the /assets folder. Try changing "archivesspace/Mitre_Corp_Logo_small.png" to "/assets/images/Mitre_Corp_Logo_small.png". That works for us, at least. Best wishes, Nick -----Original Message----- From: "Boggio, Jerry" > Reply-To: Archivesspace Users Group > To: archivesspace_users_group at lyralists.lyrasis.org > CC: "Sutherland, Bryan" >, "Boggio, Jerry" > Subject: [Archivesspace_Users_Group] Customizing Staff Side logo Date: Thu, 31 Oct 2019 14:37:04 +0000 We are looking for help as to where to place our logo file for use on the Staff page. We followed the directions below, but our logo is not being found. We are able to use the logo on the Public page and are running ArchivesSpace version 2.6. There appears to be a typo in the following page http://archivesspace.github.io/archivesspace/user/theming-archivesspace/#Making-small-changes: The Staff Side logo will need a small plugin file and cannot be set in your config.rb file. This needs to be changed in the plugins/local/frontend/views/site/_branding.html.erb file. You?ll most likely need to create one or more of the directories. Then create that _branding.html.erb file and paste in the following code:
<%= image_tag "archivesspace/archivesspace.small.png", :class=>"img-responsive" %>
Change the "archivesspace/archivesspace.small.png" to the path to your image /assets/images/logo.png and place your login the plugins/local/frontend/assets/images/ directory. You?ll most likely need to create one or more of the directories. Note: the original page had ??place your login the?? which I assume that to mean ??place your logo in the??. We put the logo in the following location: /apps/archivesspace/plugins/local/frontend/assets/images/Mitre_Corp_Logo_small.png Created the following file: [archspc at archspcdev1 site]$ pwd /apps/archivesspace/plugins/local/frontend/views/site [archspc at archspcdev1 site]$ more _branding.html.erb
<%= image_tag "archivesspace/Mitre_Corp_Logo_small.png", :class=>"img-responsive" %>
[archspc at archspcdev1 site]$ This appears to be incorrect as when bringing up the Staff page no logo is displayed, but do see what appears to be a place holder on the page. Information from the log file /apps/archivesspace/logs/archivesspace.out: ************************************************************ Welcome to ArchivesSpace! You can now point your browser to http://localhost:8080 ************************************************************ I, [2019-10-31T09:44:47.829167 #62349] INFO -- : Thread-2016: Staff Indexer [2019-10-31 09:44:47 -0400] Index round complete I, [2019-10-31T09:45:03.362859 #62349] INFO -- : Started GET "/" for 10.14.244.173 at 2019-10-31 09:45:03 -0400 I, [2019-10-31T09:45:04.429697 #62349] INFO -- : Processing by WelcomeController#index as HTML I, [2019-10-31T09:45:05.983788 #62349] INFO -- : Rendering welcome/index.html.erb within layouts/application I, [2019-10-31T09:45:06.060828 #62349] INFO -- : Rendered shared/_flash_messages.html.erb (13.6ms) I, [2019-10-31T09:45:08.815583 #62349] INFO -- : Thread-2038: PUI Indexer [2019-10-31 09:45:08 -0400] Running index round I, [2019-10-31T09:45:10.396144 #62349] INFO -- : Rendered welcome/index.html.erb within layouts/application (4411.3ms) I, [2019-10-31T09:45:11.001334 #62349] INFO -- : Rendered shared/_header_user.html.erb (498.8ms) I, [2019-10-31T09:45:11.004587 #62349] INFO -- : Rendered shared/_header_global.html.erb (520.2ms) I, [2019-10-31T09:45:12.042084 #62349] INFO -- : Rendered /apps/archivesspace/plugins/local/frontend/views/site/_branding.html.erb (1016.8ms) I, [2019-10-31T09:45:13.317327 #62349] INFO -- : Thread-2038: PUI Indexer [2019-10-31 09:45:13 -0400] Index round complete I, [2019-10-31T09:45:14.038365 #62349] INFO -- : Rendered shared/_advanced_search.html.erb (445.0ms) I, [2019-10-31T09:45:14.039334 #62349] INFO -- : Rendered shared/_header_repository.html.erb (1953.5ms) I, [2019-10-31T09:45:14.235100 #62349] INFO -- : Rendered site/_footer.html.erb (168.5ms) I, [2019-10-31T09:45:14.417472 #62349] INFO -- : Rendered shared/_templates.html.erb (155.2ms) I, [2019-10-31T09:45:14.420458 #62349] INFO -- : Completed 200 OK in 9989ms (Views: 8484.9ms) I, [2019-10-31T09:45:17.830453 #62349] INFO -- : Thread-2016: Staff Indexer [2019-10-31 09:45:17 -0400] Running index round I, [2019-10-31T09:45:18.581338 #62349] INFO -- : Started GET "/images/archivesspace/Mitre_Corp_Logo_small.png" for 10.14.244.173 at 2019-10-31 09:45:18 -0400 F, [2019-10-31T09:45:18.665371 #62349] FATAL -- : F, [2019-10-31T09:45:18.666039 #62349] FATAL -- : ActionController::RoutingError (No route matches [GET] "/images/archivesspace/Mitre_Corp_Logo_small.png"): F, [2019-10-31T09:45:18.666471 #62349] FATAL -- : F, [2019-10-31T09:45:18.666913 #62349] FATAL -- : actionpack (5.0.7.2) lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call' actionpack (5.0.7.2) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call' railties (5.0.7.2) lib/rails/rack/logger.rb:36:in `call_app' railties (5.0.7.2) lib/rails/rack/logger.rb:24:in `block in call' activesupport (5.0.7.2) lib/active_support/tagged_logging.rb:69:in `block in tagged' activesupport (5.0.7.2) lib/active_support/tagged_logging.rb:26:in `tagged' activesupport (5.0.7.2) lib/active_support/tagged_logging.rb:69:in `tagged' railties (5.0.7.2) lib/rails/rack/logger.rb:24:in `call' actionpack (5.0.7.2) lib/action_dispatch/middleware/request_id.rb:24:in `call' rack (2.0.7) lib/rack/method_override.rb:22:in `call' rack (2.0.7) lib/rack/runtime.rb:22:in `call' activesupport (5.0.7.2) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call' actionpack (5.0.7.2) lib/action_dispatch/middleware/executor.rb:12:in `call' actionpack (5.0.7.2) lib/action_dispatch/middleware/static.rb:136:in `call' rack (2.0.7) lib/rack/sendfile.rb:111:in `call' railties (5.0.7.2) lib/rails/engine.rb:522:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' I, [2019-10-31T09:45:22.376691 #62349] INFO -- : Thread-2016: Staff Indexer [2019-10-31 09:45:22 -0400] Index round complete I, [2019-10-31T09:45:43.318504 #62349] INFO -- : Thread-2038: PUI Indexer [2019-10-31 09:45:43 -0400] Running index round I, [2019-10-31T09:45:45.941843 #62349] INFO -- : Thread-2038: PUI Indexer [2019-10-31 09:45:45 -0400] Index round complete Please advise where we may have placed our logo file, file formats supported for logos, or other directories are needed. Also, can the path used in the _branding.html.erb file be fully qualified so that we make sure we are getting the file from where we expect? Thank you! Gerard (Jerry) Boggio | MITRE Corporation | R504 - Collaboration & Info Management | 781-271-2719 | Bedford, MA | 2K132 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gboggio at mitre.org Thu Oct 31 10:56:38 2019 From: gboggio at mitre.org (Boggio, Jerry) Date: Thu, 31 Oct 2019 14:56:38 +0000 Subject: [Archivesspace_Users_Group] [EXT] Re: Customizing Staff Side logo In-Reply-To: <12422_1572533078_5DBAF356_12422_1074_1_8cca4e292bbcd1d9c37e4130dbe01e3760a97f1f.camel@cam.ac.uk> References: <12422_1572533078_5DBAF356_12422_1074_1_8cca4e292bbcd1d9c37e4130dbe01e3760a97f1f.camel@cam.ac.uk> Message-ID: That worked! Thank you Nick! Gerard (Jerry) Boggio | MITRE Corporation | R504 - Collaboration & Info Management | 781-271-2719 | Bedford, MA | 2K132 From: Nick Butler Sent: Thursday, October 31, 2019 10:45 AM To: archivesspace_users_group at lyralists.lyrasis.org Cc: Sutherland, Bryan ; Boggio, Jerry Subject: [EXT] Re: [Archivesspace_Users_Group] Customizing Staff Side logo Hi Jerry, You need the path starting from the /assets folder. Try changing "archivesspace/Mitre_Corp_Logo_small.png" to "/assets/images/Mitre_Corp_Logo_small.png". That works for us, at least. Best wishes, Nick -----Original Message----- From: "Boggio, Jerry" > Reply-To: Archivesspace Users Group > To: archivesspace_users_group at lyralists.lyrasis.org > CC: "Sutherland, Bryan" >, "Boggio, Jerry" > Subject: [Archivesspace_Users_Group] Customizing Staff Side logo Date: Thu, 31 Oct 2019 14:37:04 +0000 We are looking for help as to where to place our logo file for use on the Staff page. We followed the directions below, but our logo is not being found. We are able to use the logo on the Public page and are running ArchivesSpace version 2.6. There appears to be a typo in the following page http://archivesspace.github.io/archivesspace/user/theming-archivesspace/#Making-small-changes: The Staff Side logo will need a small plugin file and cannot be set in your config.rb file. This needs to be changed in the plugins/local/frontend/views/site/_branding.html.erb file. You?ll most likely need to create one or more of the directories. Then create that _branding.html.erb file and paste in the following code:
<%= image_tag "archivesspace/archivesspace.small.png", :class=>"img-responsive" %>
Change the "archivesspace/archivesspace.small.png" to the path to your image /assets/images/logo.png and place your login the plugins/local/frontend/assets/images/ directory. You?ll most likely need to create one or more of the directories. Note: the original page had ??place your login the?? which I assume that to mean ??place your logo in the??. We put the logo in the following location: /apps/archivesspace/plugins/local/frontend/assets/images/Mitre_Corp_Logo_small.png Created the following file: [archspc at archspcdev1 site]$ pwd /apps/archivesspace/plugins/local/frontend/views/site [archspc at archspcdev1 site]$ more _branding.html.erb
<%= image_tag "archivesspace/Mitre_Corp_Logo_small.png", :class=>"img-responsive" %>
[archspc at archspcdev1 site]$ This appears to be incorrect as when bringing up the Staff page no logo is displayed, but do see what appears to be a place holder on the page. Information from the log file /apps/archivesspace/logs/archivesspace.out: ************************************************************ Welcome to ArchivesSpace! You can now point your browser to http://localhost:8080 ************************************************************ I, [2019-10-31T09:44:47.829167 #62349] INFO -- : Thread-2016: Staff Indexer [2019-10-31 09:44:47 -0400] Index round complete I, [2019-10-31T09:45:03.362859 #62349] INFO -- : Started GET "/" for 10.14.244.173 at 2019-10-31 09:45:03 -0400 I, [2019-10-31T09:45:04.429697 #62349] INFO -- : Processing by WelcomeController#index as HTML I, [2019-10-31T09:45:05.983788 #62349] INFO -- : Rendering welcome/index.html.erb within layouts/application I, [2019-10-31T09:45:06.060828 #62349] INFO -- : Rendered shared/_flash_messages.html.erb (13.6ms) I, [2019-10-31T09:45:08.815583 #62349] INFO -- : Thread-2038: PUI Indexer [2019-10-31 09:45:08 -0400] Running index round I, [2019-10-31T09:45:10.396144 #62349] INFO -- : Rendered welcome/index.html.erb within layouts/application (4411.3ms) I, [2019-10-31T09:45:11.001334 #62349] INFO -- : Rendered shared/_header_user.html.erb (498.8ms) I, [2019-10-31T09:45:11.004587 #62349] INFO -- : Rendered shared/_header_global.html.erb (520.2ms) I, [2019-10-31T09:45:12.042084 #62349] INFO -- : Rendered /apps/archivesspace/plugins/local/frontend/views/site/_branding.html.erb (1016.8ms) I, [2019-10-31T09:45:13.317327 #62349] INFO -- : Thread-2038: PUI Indexer [2019-10-31 09:45:13 -0400] Index round complete I, [2019-10-31T09:45:14.038365 #62349] INFO -- : Rendered shared/_advanced_search.html.erb (445.0ms) I, [2019-10-31T09:45:14.039334 #62349] INFO -- : Rendered shared/_header_repository.html.erb (1953.5ms) I, [2019-10-31T09:45:14.235100 #62349] INFO -- : Rendered site/_footer.html.erb (168.5ms) I, [2019-10-31T09:45:14.417472 #62349] INFO -- : Rendered shared/_templates.html.erb (155.2ms) I, [2019-10-31T09:45:14.420458 #62349] INFO -- : Completed 200 OK in 9989ms (Views: 8484.9ms) I, [2019-10-31T09:45:17.830453 #62349] INFO -- : Thread-2016: Staff Indexer [2019-10-31 09:45:17 -0400] Running index round I, [2019-10-31T09:45:18.581338 #62349] INFO -- : Started GET "/images/archivesspace/Mitre_Corp_Logo_small.png" for 10.14.244.173 at 2019-10-31 09:45:18 -0400 F, [2019-10-31T09:45:18.665371 #62349] FATAL -- : F, [2019-10-31T09:45:18.666039 #62349] FATAL -- : ActionController::RoutingError (No route matches [GET] "/images/archivesspace/Mitre_Corp_Logo_small.png"): F, [2019-10-31T09:45:18.666471 #62349] FATAL -- : F, [2019-10-31T09:45:18.666913 #62349] FATAL -- : actionpack (5.0.7.2) lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call' actionpack (5.0.7.2) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call' railties (5.0.7.2) lib/rails/rack/logger.rb:36:in `call_app' railties (5.0.7.2) lib/rails/rack/logger.rb:24:in `block in call' activesupport (5.0.7.2) lib/active_support/tagged_logging.rb:69:in `block in tagged' activesupport (5.0.7.2) lib/active_support/tagged_logging.rb:26:in `tagged' activesupport (5.0.7.2) lib/active_support/tagged_logging.rb:69:in `tagged' railties (5.0.7.2) lib/rails/rack/logger.rb:24:in `call' actionpack (5.0.7.2) lib/action_dispatch/middleware/request_id.rb:24:in `call' rack (2.0.7) lib/rack/method_override.rb:22:in `call' rack (2.0.7) lib/rack/runtime.rb:22:in `call' activesupport (5.0.7.2) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call' actionpack (5.0.7.2) lib/action_dispatch/middleware/executor.rb:12:in `call' actionpack (5.0.7.2) lib/action_dispatch/middleware/static.rb:136:in `call' rack (2.0.7) lib/rack/sendfile.rb:111:in `call' railties (5.0.7.2) lib/rails/engine.rb:522:in `call' uri:classloader:/rack/handler/servlet.rb:22:in `call' I, [2019-10-31T09:45:22.376691 #62349] INFO -- : Thread-2016: Staff Indexer [2019-10-31 09:45:22 -0400] Index round complete I, [2019-10-31T09:45:43.318504 #62349] INFO -- : Thread-2038: PUI Indexer [2019-10-31 09:45:43 -0400] Running index round I, [2019-10-31T09:45:45.941843 #62349] INFO -- : Thread-2038: PUI Indexer [2019-10-31 09:45:45 -0400] Index round complete Please advise where we may have placed our logo file, file formats supported for logos, or other directories are needed. Also, can the path used in the _branding.html.erb file be fully qualified so that we make sure we are getting the file from where we expect? Thank you! Gerard (Jerry) Boggio | MITRE Corporation | R504 - Collaboration & Info Management | 781-271-2719 | Bedford, MA | 2K132 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Thu Oct 31 11:47:57 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 31 Oct 2019 15:47:57 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - October 2019 Message-ID: <54A9077A-9E59-41C7-B923-76086C0E52F0@lyrasis.org> ArchivesSpace Update - October 2019 Development ArchivesSpace v2.7.0 is now available. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.7.0. This release contains program-led and community pull requests that provide feature enhancements, bug and security fixes, and documentation updates, as well as infrastructure improvements, which were a significant focus of this release. A full list of the changes and improvements is provided on the release page. In addition to small interface and functionality changes, this release contains two larger areas of feature enhancement. One relates to recording information about language of description and materials. These changes were made to facilitate better standards compliance in these areas. The second major feature enhancement, made to accommodate requests to use persistent identifiers in OAI-PMH harvests and exports, is that resources and archival objects can now be represented by Archival Resource Keys (ARKs). ARKs can either be generated by ArchivesSpace or created outside the application. Thanks very much to community members Mark Cooper, Mark Custer, Alex Duryee, Dave Mayo, Austin Schaffer, and Greg Wiedeman, and program team members Laney McGlohon, Lora Woodford, and Sarah Morrissey for their code contributions to this release. Thanks also to the contract developer we have been able to engage through member funds, Manny Rodriguez (via LibraryHost), for his efforts on the ARKs feature. Thanks to LYRASIS Digital Technology Services for their technical support with our testing servers and running trial migrations. Last, but by no means least, as always this release would not have been possible without the efforts of our Development Prioritization sub-team, Testing sub-team, Technical Documentation sub-team, and Core Committers Group. Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not yet upgraded to a recent version, we recommend going directly to 2.7.0. Please let us know if you have any questions or need help upgrading. Registration is now open for the Southeastern Regional Forum Registration is now open for the ArchivesSpace Southeastern Regional Forum on November 15, 2019, at the Hollings Special Collections Library at ArchivesSpace member institution University of South Carolina. As with previous forums, this will be a free opportunity for staff from ArchivesSpace member institutions in the region to meet and share information with each other and the program team about all things ArchivesSpace with a focus on local interests and activities. For more information, visit the ArchivesSpace wiki page for the forum. Volunteer for the next ArchivesSpace online forum We are currently looking for volunteers for the working group for our second ArchivesSpace online forum! Planned for late winter or early spring 2020, this event will build on the success of the 2019 Online Forum, which had over 400 registrants, participating from 7 different countries. We would love this event to highlight the work institutions near and far are doing to adapt and integrate ArchivesSpace into their systems and workflows. We expect to offer a variety of activities aimed at building community connections and contacts among our users. All ideas are welcome! All community members are welcome to volunteer for this working group. We especially encourage our Small and Very Small members as well as non-U.S. members to join in envisioning the next iteration of this event. We will schedule meetings and the forum itself in ways that allow for participation across time zones. If you would like to volunteer, please respond by December 1, 2019. And if you have any questions, contact Jessica at jessica.crouch at lyrasis.org. Upcoming Webinar: Integrating ArchivesSpace with Aeon November 6, 2019, 2-3pm ET (11-noon PT; 7-8pm BST) Visit the ArchivesSpace blog for details. ArchivesSpace is pleased to announce the second webinar in our new webinar series focused on Integrations with ArchivesSpace. Our second webinar in this series will feature an ArchivesSpace integration with Aeon, an automated request and workflow management software specifically designed for special collections libraries and archives from Atlas Systems. Webinar description: This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Katie Gillespie (Atlas Systems) will present the Aeon and ArchivesSpace integration request plugin and discuss the different ways this plugin has been deployed at individual institutions. Katie will also discuss development work that is currently being planned to expand and improve the plugin and the accompanying Aeon client addon. Joanne Archer (University of Maryland) will walk through her repository?s decision to use ArchivesSpace and Aeon together. She will offer insight into the process of integration, including decisions that were made, lessons learned and how integration has made life easier. A discussion will follow. Current users of the plugin, as well as those who have integrated Aeon and ArchivesSpace at their own institutions through other workflows, are encouraged to attend and offer insight into their own integrations, lessons learned and plans for the future. Users who are interested in integrating Aeon and ArchivesSpace are also encouraged to attend and offer insight into their own needs and initial feedback on the proposed plugin improvements. Questions? Contact Jessica at jessica.crouch at lyrasis.org if you have questions about this webinar or the Integrations with ArchivesSpace webinar series. The next Integrations with ArchivesSpace webinar will be: Integrating ArchivesSpace with Archive-It, December 4, 2019, at 2pm ET (11am PT) Development prioritization survey - respond by November 20 From Lydia Tang and Maggie Hughes, on behalf of the Development Prioritization subteam The Development Prioritization subteam recently released a prioritization survey, with the goal of informing the Development Prioritization subteam and Program Team of areas of the application that ArchivesSpace member institutions want prioritized for development in the next 2-3 years. Please share your feedback! https://www.surveymonkey.com/r/WPZYHLX Please fill out the survey if you have any thoughts on which areas of ArchivesSpace should be prioritized in development. We will be extremely grateful for your participation by Wednesday, November 20. As always, please feel free to vote, comment, and create JIRA tickets with ideas on how to propel the program forward. Please reach out if you have any questions or concerns! ArchivesSpace at MARAC Lora Woodford will be at the Mid-Atlantic Regional Archives Conference in Cambridge, Maryland, November 7-9. Come find her in the exhibit hall to talk about the ArchivesSpace application, our community activities, membership, and more. Webinar recordings now available Thank to everyone who attended our most recent webinars. Recordings of those webinars are now available on the ArchivesSpace YouTube channel, via the ArchivesSpace blog and via the links below: Introducing the PBSpace Plugin (recorded September 23, 2019) Integrating ArchivesSpace and Preservica (recorded October 1, 2019) Batch editing barcodes in the ArchivesSpace API (recorded October 23, 2019) Membership Update We are excited to welcome our newest members to our community! Our new members since September 30 include: * Chinese Historical Society of Southern California (Los Angeles, CA) * Montgomery County Archives (Clarksville, TN) * Nakanoshima Museum of Art, Osaka (Osaka, Japan) * National Archives of Australia (Canberra, Australia) * New Zealand Institute of Plant and Food Research (Auckland, New Zealand) * University of Colorado, Boulder (Boulder, CA) As of October 31, we have 406 General members, 19 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 Tools 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 Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29060 bytes Desc: image001.jpg URL: From jdtillman at sdsu.edu Thu Oct 31 15:26:08 2019 From: jdtillman at sdsu.edu (Josh Tillman) Date: Thu, 31 Oct 2019 12:26:08 -0700 Subject: [Archivesspace_Users_Group] Archon to AS migration data issue Message-ID: Hello, I'm having an issue with the Archon to AS migration. After the migration tool runs, there are empty duplicate boxes showing up at the collection-level. Is there a way to remove them all at once or prevent them from duplicating in the first place? Or does each one have to be deleted manually? Thank you, Josh Tillman PHP Programmer and Database Administrator Library Information Technologies & Digital Initiatives San Diego State University 5500 Campanile Drive San Diego, CA 92182-8050 619.594.1811 jdtillman at sdsu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: