From mayoc at bc.edu Wed Jul 1 08:13:17 2020 From: mayoc at bc.edu (Chris Mayo) Date: Wed, 1 Jul 2020 08:13:17 -0400 Subject: [Archivesspace_Users_Group] help with API route for archival object notes In-Reply-To: References: Message-ID: Hi Karen, To be a little more specific, I'm getting the sense (since I've struggled with needing to update some notes but not others as well) that what you're asking is how to create the path to a specific note when you don't know in advance which note it's going to be. If you want to only modify notes that have html tags in them, you'll need to give it the path to ['notes'] part of the structure, and then run a for-loop, since that part is a list. You can ask it to look at each note in the list of notes and only make changes if it comes across one of the bad tags you're looking for. In python this would look something like for note in json['notes'] if 'bad tag' in note: modify the note I'm afraid that I am enough of a scripter to only use Python to interact with the API, if you're using Postman or anything like that I'm not entirely sure how you'd accomplish something like this, and maybe somebody else can advise. The thing that was hardest for me about learning how to interact with JSON was coming to realize that as far as the scripting language is concerned, anything inside square brackets [ ] is a list, and anything inside curly braces { } is a dictionary, and they can be interacted with as those data types. Hope that helps, and sorry if I misread what your problem was! Chris On Tue, Jun 30, 2020 at 7:35 PM James Bullen wrote: > > Hi Karen, > > The general rule is that anything you can GET from a uri can be modified > and POSTed back to update it. > > So, GET the JSON for the archival_object as you are doing. Then modify the > JSON (in this case the notes bit of it) to look how you want. Then POST it > back to the same uri. > > Notes are nested subrecords (as are dates and others). These don?t have a > life of their own, they are really just repeating parts of the top level > record that they are contained within. > > Hope that helps.. > > > Cheers, > James > > > On Jul 1, 2020, at 8:22 AM, Karen Miller > wrote: > > Good morning, ArchivesSpace users. > > I am a cataloger (*not* a developer) using the API to update > ArchivesSpace. So far I?ve figured out how to add LCCNs to the authority_Id > of Agent records and do a couple more updates that, in retrospect, were > pretty simple. > > The next task I?d like to tackle, however, just seems like maybe it can?t > be done. We?ve got a lot of notes with html tags in them and I would like > to update those to valid tags. I can get the JSON for the notes in any > particular archival object, but I don?t know how to specify the route to > the note to change it. The JSON looks like this: > > 'notes': [{'content': ['This is a note with a bad tag'], > 'jsonmodel_type': 'note_singlepart', > 'persistent_id': '75ba0ec57e374b8b154551a69b4c311f', > 'publish': True, > 'type': 'abstract'}, > {'jsonmodel_type': 'note_multipart', > 'persistent_id': '66afa07b3214260078123236bbe1ff27', > 'publish': True, > 'subnotes': [{'content': 'This is a dippy note.', > 'jsonmodel_type': 'note_text', > 'publish': True}], > 'type': 'scopecontent'}], > > I got this using the route ?repositories/10/archival_objects/489763?, but > I don?t know how to specify the note that I want in the JSON. For the agent > authority_id I used the route ??/agents/people/ and specified > the field like this: > > ['names'][0]['authority_id'] > > I?m hoping this is an easy question for somebody with more experience with > the API and (especially) with JSON than I. I?m a little afraid the answer > is that it can?t be done. Any advice will be appreciated! > > Karen > > *Karen D. Miller* > Monographic Cataloger/Metadata Specialist > Northwestern University Libraries > Northwestern University > 1970 Campus Drive > Evanston, IL 60208 > www.library.northwestern.edu > k-miller3 at northwestern.edu > 874.467.3462 > > _______________________________________________ > 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 > -- Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs -------------- next part -------------- An HTML attachment was scrubbed... URL: From k-miller3 at northwestern.edu Wed Jul 1 10:50:06 2020 From: k-miller3 at northwestern.edu (Karen Miller) Date: Wed, 1 Jul 2020 14:50:06 +0000 Subject: [Archivesspace_Users_Group] help with API route for archival object notes In-Reply-To: References: Message-ID: Hi Chris. I?ve been able to successfully retrieve & update nested elements from the Agent record, just not from the archival object notes record. But your description of them as ?repeating parts? of that record is helpful. Thanks! Karen From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of James Bullen Sent: Tuesday, June 30, 2020 6:35 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] help with API route for archival object notes Hi Karen, The general rule is that anything you can GET from a uri can be modified and POSTed back to update it. So, GET the JSON for the archival_object as you are doing. Then modify the JSON (in this case the notes bit of it) to look how you want. Then POST it back to the same uri. Notes are nested subrecords (as are dates and others). These don?t have a life of their own, they are really just repeating parts of the top level record that they are contained within. Hope that helps.. Cheers, James On Jul 1, 2020, at 8:22 AM, Karen Miller > wrote: Good morning, ArchivesSpace users. I am a cataloger (*not* a developer) using the API to update ArchivesSpace. So far I?ve figured out how to add LCCNs to the authority_Id of Agent records and do a couple more updates that, in retrospect, were pretty simple. The next task I?d like to tackle, however, just seems like maybe it can?t be done. We?ve got a lot of notes with html tags in them and I would like to update those to valid tags. I can get the JSON for the notes in any particular archival object, but I don?t know how to specify the route to the note to change it. The JSON looks like this: 'notes': [{'content': ['This is a note with a bad tag'], 'jsonmodel_type': 'note_singlepart', 'persistent_id': '75ba0ec57e374b8b154551a69b4c311f', 'publish': True, 'type': 'abstract'}, {'jsonmodel_type': 'note_multipart', 'persistent_id': '66afa07b3214260078123236bbe1ff27', 'publish': True, 'subnotes': [{'content': 'This is a dippy note.', 'jsonmodel_type': 'note_text', 'publish': True}], 'type': 'scopecontent'}], I got this using the route ?repositories/10/archival_objects/489763?, but I don?t know how to specify the note that I want in the JSON. For the agent authority_id I used the route ??/agents/people/ and specified the field like this: ['names'][0]['authority_id'] I?m hoping this is an easy question for somebody with more experience with the API and (especially) with JSON than I. I?m a little afraid the answer is that it can?t be done. Any advice will be appreciated! Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 _______________________________________________ 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 k-miller3 at northwestern.edu Wed Jul 1 10:54:03 2020 From: k-miller3 at northwestern.edu (Karen Miller) Date: Wed, 1 Jul 2020 14:54:03 +0000 Subject: [Archivesspace_Users_Group] help with API route for archival object notes In-Reply-To: References: Message-ID: Hi Chris, Yes, I think you understood my problem exactly! I am using Python with the API and I?m not very familiar with either Python or JSON. I am pretty adept at SQL, so I am pretty sure I can identify and export the URIs of archival objects that have notes that contain HTML. It?s the issue of identifying that part of the JSON for Python to understand that I?m struggling with. I think I?ll read up a bit more on dictionaries (I?ve been plowing through a book about beginning Python but gave up after reading about lists) and look into using the for loop with my notes. If I run into another brick wall, I?ll probably be back. Thanks! Karen From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Chris Mayo Sent: Wednesday, July 01, 2020 7:13 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] help with API route for archival object notes Hi Karen, To be a little more specific, I'm getting the sense (since I've struggled with needing to update some notes but not others as well) that what you're asking is how to create the path to a specific note when you don't know in advance which note it's going to be. If you want to only modify notes that have html tags in them, you'll need to give it the path to ['notes'] part of the structure, and then run a for-loop, since that part is a list. You can ask it to look at each note in the list of notes and only make changes if it comes across one of the bad tags you're looking for. In python this would look something like for note in json['notes'] if 'bad tag' in note: modify the note I'm afraid that I am enough of a scripter to only use Python to interact with the API, if you're using Postman or anything like that I'm not entirely sure how you'd accomplish something like this, and maybe somebody else can advise. The thing that was hardest for me about learning how to interact with JSON was coming to realize that as far as the scripting language is concerned, anything inside square brackets [ ] is a list, and anything inside curly braces { } is a dictionary, and they can be interacted with as those data types. Hope that helps, and sorry if I misread what your problem was! Chris On Tue, Jun 30, 2020 at 7:35 PM James Bullen > wrote: Hi Karen, The general rule is that anything you can GET from a uri can be modified and POSTed back to update it. So, GET the JSON for the archival_object as you are doing. Then modify the JSON (in this case the notes bit of it) to look how you want. Then POST it back to the same uri. Notes are nested subrecords (as are dates and others). These don?t have a life of their own, they are really just repeating parts of the top level record that they are contained within. Hope that helps.. Cheers, James On Jul 1, 2020, at 8:22 AM, Karen Miller > wrote: Good morning, ArchivesSpace users. I am a cataloger (*not* a developer) using the API to update ArchivesSpace. So far I?ve figured out how to add LCCNs to the authority_Id of Agent records and do a couple more updates that, in retrospect, were pretty simple. The next task I?d like to tackle, however, just seems like maybe it can?t be done. We?ve got a lot of notes with html tags in them and I would like to update those to valid tags. I can get the JSON for the notes in any particular archival object, but I don?t know how to specify the route to the note to change it. The JSON looks like this: 'notes': [{'content': ['This is a note with a bad tag'], 'jsonmodel_type': 'note_singlepart', 'persistent_id': '75ba0ec57e374b8b154551a69b4c311f', 'publish': True, 'type': 'abstract'}, {'jsonmodel_type': 'note_multipart', 'persistent_id': '66afa07b3214260078123236bbe1ff27', 'publish': True, 'subnotes': [{'content': 'This is a dippy note.', 'jsonmodel_type': 'note_text', 'publish': True}], 'type': 'scopecontent'}], I got this using the route ?repositories/10/archival_objects/489763?, but I don?t know how to specify the note that I want in the JSON. For the agent authority_id I used the route ??/agents/people/ and specified the field like this: ['names'][0]['authority_id'] I?m hoping this is an easy question for somebody with more experience with the API and (especially) with JSON than I. I?m a little afraid the answer is that it can?t be done. Any advice will be appreciated! Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 _______________________________________________ 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 -- Chris Mayo Digital Production Librarian Boston College chris.mayo at bc.edu pronouns: they/them/theirs -------------- next part -------------- An HTML attachment was scrubbed... URL: From k-miller3 at northwestern.edu Wed Jul 1 11:23:20 2020 From: k-miller3 at northwestern.edu (Karen Miller) Date: Wed, 1 Jul 2020 15:23:20 +0000 Subject: [Archivesspace_Users_Group] help with API route for archival object notes References: Message-ID: Hello, James. Sorry, I just realized I addressed you as Chris instead of as James! My apologies! I was so thrilled to get some assistance that I skimmed through the signatures too quickly. Best, Karen From: Karen Miller Sent: Wednesday, July 01, 2020 9:50 AM To: 'Archivesspace Users Group' Subject: RE: [Archivesspace_Users_Group] help with API route for archival object notes Hi Chris. I?ve been able to successfully retrieve & update nested elements from the Agent record, just not from the archival object notes record. But your description of them as ?repeating parts? of that record is helpful. Thanks! Karen From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of James Bullen Sent: Tuesday, June 30, 2020 6:35 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] help with API route for archival object notes Hi Karen, The general rule is that anything you can GET from a uri can be modified and POSTed back to update it. So, GET the JSON for the archival_object as you are doing. Then modify the JSON (in this case the notes bit of it) to look how you want. Then POST it back to the same uri. Notes are nested subrecords (as are dates and others). These don?t have a life of their own, they are really just repeating parts of the top level record that they are contained within. Hope that helps.. Cheers, James On Jul 1, 2020, at 8:22 AM, Karen Miller > wrote: Good morning, ArchivesSpace users. I am a cataloger (*not* a developer) using the API to update ArchivesSpace. So far I?ve figured out how to add LCCNs to the authority_Id of Agent records and do a couple more updates that, in retrospect, were pretty simple. The next task I?d like to tackle, however, just seems like maybe it can?t be done. We?ve got a lot of notes with html tags in them and I would like to update those to valid tags. I can get the JSON for the notes in any particular archival object, but I don?t know how to specify the route to the note to change it. The JSON looks like this: 'notes': [{'content': ['This is a note with a bad tag'], 'jsonmodel_type': 'note_singlepart', 'persistent_id': '75ba0ec57e374b8b154551a69b4c311f', 'publish': True, 'type': 'abstract'}, {'jsonmodel_type': 'note_multipart', 'persistent_id': '66afa07b3214260078123236bbe1ff27', 'publish': True, 'subnotes': [{'content': 'This is a dippy note.', 'jsonmodel_type': 'note_text', 'publish': True}], 'type': 'scopecontent'}], I got this using the route ?repositories/10/archival_objects/489763?, but I don?t know how to specify the note that I want in the JSON. For the agent authority_id I used the route ??/agents/people/ and specified the field like this: ['names'][0]['authority_id'] I?m hoping this is an easy question for somebody with more experience with the API and (especially) with JSON than I. I?m a little afraid the answer is that it can?t be done. Any advice will be appreciated! Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 _______________________________________________ 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 noah.huffman at duke.edu Wed Jul 1 11:58:54 2020 From: noah.huffman at duke.edu (Noah Huffman) Date: Wed, 1 Jul 2020 15:58:54 +0000 Subject: [Archivesspace_Users_Group] help with API route for archival object notes In-Reply-To: References: Message-ID: Hi Karen, I believe each note has a persistent identifier, so if you can use SQL to get the note identifiers you can address the problem notes that way. Here?s an example of some SQL that gets access restriction notes on archival objects including the identifiers: https://github.com/duke-libraries/archivesspace-duke-scripts/blob/master/sql/access_restriction_notes_on_aos.sql And, here?s an example of a python script that uses those note identifiers to make updates to those notes (based on a script I borrowed from Alicia Detelich at Yale): https://github.com/duke-libraries/archivesspace-duke-scripts/blob/master/python/duke_as_replace_notes.py#L40 I haven?t used these in a while, so I can?t confirm if they still work, but the general idea should still hold. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ Pronouns: he / him / his From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Karen Miller Sent: Wednesday, July 1, 2020 11:23 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] help with API route for archival object notes Hello, James. Sorry, I just realized I addressed you as Chris instead of as James! My apologies! I was so thrilled to get some assistance that I skimmed through the signatures too quickly. Best, Karen From: Karen Miller Sent: Wednesday, July 01, 2020 9:50 AM To: 'Archivesspace Users Group' > Subject: RE: [Archivesspace_Users_Group] help with API route for archival object notes Hi Chris. I?ve been able to successfully retrieve & update nested elements from the Agent record, just not from the archival object notes record. But your description of them as ?repeating parts? of that record is helpful. Thanks! Karen From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of James Bullen Sent: Tuesday, June 30, 2020 6:35 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] help with API route for archival object notes Hi Karen, The general rule is that anything you can GET from a uri can be modified and POSTed back to update it. So, GET the JSON for the archival_object as you are doing. Then modify the JSON (in this case the notes bit of it) to look how you want. Then POST it back to the same uri. Notes are nested subrecords (as are dates and others). These don?t have a life of their own, they are really just repeating parts of the top level record that they are contained within. Hope that helps.. Cheers, James On Jul 1, 2020, at 8:22 AM, Karen Miller > wrote: Good morning, ArchivesSpace users. I am a cataloger (*not* a developer) using the API to update ArchivesSpace. So far I?ve figured out how to add LCCNs to the authority_Id of Agent records and do a couple more updates that, in retrospect, were pretty simple. The next task I?d like to tackle, however, just seems like maybe it can?t be done. We?ve got a lot of notes with html tags in them and I would like to update those to valid tags. I can get the JSON for the notes in any particular archival object, but I don?t know how to specify the route to the note to change it. The JSON looks like this: 'notes': [{'content': ['This is a note with a bad tag'], 'jsonmodel_type': 'note_singlepart', 'persistent_id': '75ba0ec57e374b8b154551a69b4c311f', 'publish': True, 'type': 'abstract'}, {'jsonmodel_type': 'note_multipart', 'persistent_id': '66afa07b3214260078123236bbe1ff27', 'publish': True, 'subnotes': [{'content': 'This is a dippy note.', 'jsonmodel_type': 'note_text', 'publish': True}], 'type': 'scopecontent'}], I got this using the route ?repositories/10/archival_objects/489763?, but I don?t know how to specify the note that I want in the JSON. For the agent authority_id I used the route ??/agents/people/ and specified the field like this: ['names'][0]['authority_id'] I?m hoping this is an easy question for somebody with more experience with the API and (especially) with JSON than I. I?m a little afraid the answer is that it can?t be done. Any advice will be appreciated! Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 _______________________________________________ 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 mjb9 at williams.edu Wed Jul 1 12:08:02 2020 From: mjb9 at williams.edu (Matthew Baya) Date: Wed, 1 Jul 2020 12:08:02 -0400 Subject: [Archivesspace_Users_Group] Error creating a new resource In-Reply-To: References: Message-ID: I'm including the logs below of what happens when we try to create a resource. All the user sees is a message in red letters saying "We're sorry but something went wrong" I think the key error in the logs is this; F, [2020-06-30T08:55:35.268000 #437747500] FATAL -- : ActionView::Template::Error (No such template: "rights_type_intellectual_property"): but I'm not sure what it means or where to fix it. This was working up until recently My only guess is that maybe this is some kind of setting we had set in the older version of Archivesspace and now that we're running the new one it's causing problems. Does anyone have any suggestions on how we can remedy this? Thanks -Matt I, [2020-06-30T08:55:34.021000 #437747500] INFO -- : Started GET "/resources/new" for 137.165.101.126 at 2020-06-30 08:55:34 -0400 I, [2020-06-30T08:55:34.023000 #437747500] INFO -- : Processing by ResourcesController#new as HTML I, [2020-06-30T08:55:34.142000 #437747500] INFO -- : Rendering resources/new.html.erb within layouts/application I, [2020-06-30T08:55:34.152000 #437747500] INFO -- : Rendered shared/_breadcrumb.html.erb (9.0ms) I, [2020-06-30T08:55:34.155000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.155000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.156000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.156000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.156000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.157000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.157000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.157000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.158000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.158000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.158000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.159000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.159000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.159000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.160000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (1.0ms) I, [2020-06-30T08:55:34.160000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.160000 #437747500] INFO -- : Rendered shared/_sidebar.html.erb (6.0ms) I, [2020-06-30T08:55:34.160000 #437747500] INFO -- : Rendered resources/_sidebar.html.erb (6.0ms) I, [2020-06-30T08:55:34.161000 #437747500] INFO -- : Rendered shared/_toolbar_new_records.html.erb (0.0ms) I, [2020-06-30T08:55:34.162000 #437747500] INFO -- : Rendered shared/_flash_messages.html.erb (0.0ms) I, [2020-06-30T08:55:34.162000 #437747500] INFO -- : Rendered shared/_form_messages.html.erb (1.0ms) I, [2020-06-30T08:55:34.248000 #437747500] INFO -- : Started GET "/" for 137.165.12.1 at 2020-06-30 08:55:34 -0400 I, [2020-06-30T08:55:34.250000 #437747500] INFO -- : Processing by WelcomeController#index as HTML I, [2020-06-30T08:55:34.300000 #437747500] INFO -- : Rendering welcome/index.html.erb within layouts/application I, [2020-06-30T08:55:34.300000 #437747500] INFO -- : Rendered shared/_flash_messages.html.erb (0.0ms) I, [2020-06-30T08:55:34.300000 #437747500] INFO -- : Rendered welcome/index.html.erb within layouts/application (0.0ms) I, [2020-06-30T08:55:34.303000 #437747500] INFO -- : Rendering /opt/archivesspace/prod/archivesspace/plugins/aspace-import-excel/frontend/views/layout_head.html.erb I, [2020-06-30T08:55:34.303000 #437747500] INFO -- : Rendered /opt/archivesspace/prod/archivesspace/plugins/aspace-import-excel/frontend/views/layout_head.html.erb (0.0ms) I, [2020-06-30T08:55:34.304000 #437747500] INFO -- : Rendered shared/_login.html.erb (1.0ms) I, [2020-06-30T08:55:34.304000 #437747500] INFO -- : Rendered shared/_header_user.html.erb (1.0ms) I, [2020-06-30T08:55:34.305000 #437747500] INFO -- : Rendered shared/_header_global.html.erb (2.0ms) I, [2020-06-30T08:55:34.305000 #437747500] INFO -- : Rendered site/_branding.html.erb (0.0ms) I, [2020-06-30T08:55:34.305000 #437747500] INFO -- : Rendered site/_footer.html.erb (0.0ms) I, [2020-06-30T08:55:34.307000 #437747500] INFO -- : Rendered shared/_templates.html.erb (2.0ms) I, [2020-06-30T08:55:34.307000 #437747500] INFO -- : Completed 200 OK in 57ms (Views: 7.9ms) I, [2020-06-30T08:55:35.064000 #437747500] INFO -- : Rendered language_and_scripts/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.065000 #437747500] INFO -- : Rendered lang_materials/_template.html.erb (1.0ms) I, [2020-06-30T08:55:35.065000 #437747500] INFO -- : Rendered lang_materials/_subrecord_form_action.html.erb (0.0ms) I, [2020-06-30T08:55:35.102000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (39.0ms) I, [2020-06-30T08:55:35.103000 #437747500] INFO -- : Rendered dates/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.110000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (8.0ms) I, [2020-06-30T08:55:35.111000 #437747500] INFO -- : Rendered extents/_template.html.erb (1.0ms) I, [2020-06-30T08:55:35.117000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (7.0ms) I, [2020-06-30T08:55:35.164000 #437747500] INFO -- : Rendered revision_statements/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.165000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (1.0ms) I, [2020-06-30T08:55:35.166000 #437747500] INFO -- : Rendered related_accessions/_template.html.erb (1.0ms) I, [2020-06-30T08:55:35.166000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (1.0ms) I, [2020-06-30T08:55:35.168000 #437747500] INFO -- : Rendered terms/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.169000 #437747500] INFO -- : Rendered linked_agents/_template.html.erb (1.0ms) I, [2020-06-30T08:55:35.170000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (3.0ms) I, [2020-06-30T08:55:35.176000 #437747500] INFO -- : Rendered subjects/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.178000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (7.0ms) I, [2020-06-30T08:55:35.197000 #437747500] INFO -- : Rendered notes/_template.html.erb (19.0ms) I, [2020-06-30T08:55:35.244000 #437747500] INFO -- : Rendered notes/_form.html.erb (66.0ms) I, [2020-06-30T08:55:35.245000 #437747500] INFO -- : Rendered external_documents/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.246000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (2.0ms) I, [2020-06-30T08:55:35.247000 #437747500] INFO -- : Rendered rights_statements/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.257000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (11.0ms) I, [2020-06-30T08:55:35.257000 #437747500] INFO -- : Rendered resources/_form_container.html.erb (1096.0ms) I, [2020-06-30T08:55:35.257000 #437747500] INFO -- : Rendered resources/new.html.erb within layouts/application (1114.0ms) I, [2020-06-30T08:55:35.261000 #437747500] INFO -- : Completed 500 Internal Server Error in 1237ms F, [2020-06-30T08:55:35.268000 #437747500] FATAL -- : F, [2020-06-30T08:55:35.268000 #437747500] FATAL -- : ActionView::Template::Error (No such template: "rights_type_intellectual_property"): F, [2020-06-30T08:55:35.268000 #437747500] FATAL -- : 45: <% end %> 46: <% else %> 47: <%= form.list_for(form[name], "#{name}[]") do |item| %> 48: <% form.emit_template(template, item) %> 49: <% end %> 50: <% end %> 51: F, [2020-06-30T08:55:35.268000 #437747500] FATAL -- : F, [2020-06-30T08:55:35.268000 #437747500] FATAL -- : app/helpers/aspace_form_helper.rb:487:in `emit_template' app/views/rights_statements/_template.html.erb:57:in `block in _app_views_rights_statements__template_html_erb__2098435309_2698' app/helpers/aspace_form_helper.rb:492:in `emit_template' app/views/shared/_subrecord_form.html.erb:48:in `block in _app_views_shared__subrecord_form_html_erb__1528586581_2670' app/helpers/aspace_form_helper.rb:136:in `block in list_for' app/helpers/aspace_form_helper.rb:232:in `push' app/helpers/aspace_form_helper.rb:133:in `block in list_for' app/helpers/aspace_form_helper.rb:132:in `list_for' app/views/shared/_subrecord_form.html.erb:47:in `_app_views_shared__subrecord_form_html_erb__1528586581_2670' app/helpers/application_helper.rb:307:in `render_aspace_partial' app/views/resources/_form_container.html.erb:83:in `_app_views_resources__form_container_html_erb__1484080424_2976' app/helpers/application_helper.rb:307:in `render_aspace_partial' app/views/resources/new.html.erb:14:in `block in _app_views_resources_new_html_erb___934010705_2972' app/helpers/aspace_form_helper.rb:848:in `form_context' app/views/resources/new.html.erb:5:in `block in _app_views_resources_new_html_erb___934010705_2972' app/views/resources/new.html.erb:4:in `_app_views_resources_new_html_erb___934010705_2972' *Matthew Baya* Williams College OIT, Networks & Systems 413-597-3567 -------------- next part -------------- An HTML attachment was scrubbed... URL: From knoxa at uncw.edu Wed Jul 1 12:24:48 2020 From: knoxa at uncw.edu (Knox, Ashley M.) Date: Wed, 1 Jul 2020 16:24:48 +0000 Subject: [Archivesspace_Users_Group] human readable URLs -- translation missing resource Message-ID: After implementing human readable URLs, did anyone see this in the staff interface beside the new field labels? 'translation missing: resource.public_url' and 'translation missing:resource.slug' It should only say public url and slug. Thank you for any tips. Of the available options, we changed these two items from false to true. use_human_readable_URLs - determines whether the options for creating human-readable URLs are shown in the staff interface and whether the URL shown in the public user interface for a record is the human-readable URL. (In order to prevent broken links, if this option was turned on at one time and then was turned off, the slugs created during that time remain in the records and the associated URLs will still work, but they will not be visible or editable through the staff interface. Only if the slugs are removed from the records will those URLs cease to work.) auto_generate_slugs_with_id - by default, auto-generated slugs are based on the name or title in the record. If you choose this option, records with meaningful identifiers (like accessions and resources) will have slugs based on those IDs. Within this configuration there are two additional options. Ashley Knox Digital Initiatives Librarian Randall Library University of North Carolina Wilmington knoxa at uncw.edu http://library.uncw.edu http://digitalcollections.uncw.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Wed Jul 1 12:56:32 2020 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 1 Jul 2020 16:56:32 +0000 Subject: [Archivesspace_Users_Group] Error creating a new resource In-Reply-To: References: , Message-ID: So I think the problem is the migration mapping changed during upgrades and if it's in a note it didn't update, and that breaks things. You'll need to find where that is being used in the notes and update it in the db, copyright and institutional became other. You can see the changes here: https://github.com/archivesspace/archivesspace/blob/master/common/db/migrations/088_rights_management.rb#L297-L311 So you'll need to find those with the old value and change that to the new. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Matthew Baya Sent: Wednesday, July 1, 2020 12:08 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Error creating a new resource I'm including the logs below of what happens when we try to create a resource. All the user sees is a message in red letters saying "We're sorry but something went wrong" I think the key error in the logs is this; F, [2020-06-30T08:55:35.268000 #437747500] FATAL -- : ActionView::Template::Error (No such template: "rights_type_intellectual_property"): but I'm not sure what it means or where to fix it. This was working up until recently My only guess is that maybe this is some kind of setting we had set in the older version of Archivesspace and now that we're running the new one it's causing problems. Does anyone have any suggestions on how we can remedy this? Thanks -Matt I, [2020-06-30T08:55:34.021000 #437747500] INFO -- : Started GET "/resources/new" for 137.165.101.126 at 2020-06-30 08:55:34 -0400 I, [2020-06-30T08:55:34.023000 #437747500] INFO -- : Processing by ResourcesController#new as HTML I, [2020-06-30T08:55:34.142000 #437747500] INFO -- : Rendering resources/new.html.erb within layouts/application I, [2020-06-30T08:55:34.152000 #437747500] INFO -- : Rendered shared/_breadcrumb.html.erb (9.0ms) I, [2020-06-30T08:55:34.155000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.155000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.156000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.156000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.156000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.157000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.157000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.157000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.158000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.158000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.158000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.159000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.159000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.159000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.160000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (1.0ms) I, [2020-06-30T08:55:34.160000 #437747500] INFO -- : Rendered shared/_sidebar_entry.html.erb (0.0ms) I, [2020-06-30T08:55:34.160000 #437747500] INFO -- : Rendered shared/_sidebar.html.erb (6.0ms) I, [2020-06-30T08:55:34.160000 #437747500] INFO -- : Rendered resources/_sidebar.html.erb (6.0ms) I, [2020-06-30T08:55:34.161000 #437747500] INFO -- : Rendered shared/_toolbar_new_records.html.erb (0.0ms) I, [2020-06-30T08:55:34.162000 #437747500] INFO -- : Rendered shared/_flash_messages.html.erb (0.0ms) I, [2020-06-30T08:55:34.162000 #437747500] INFO -- : Rendered shared/_form_messages.html.erb (1.0ms) I, [2020-06-30T08:55:34.248000 #437747500] INFO -- : Started GET "/" for 137.165.12.1 at 2020-06-30 08:55:34 -0400 I, [2020-06-30T08:55:34.250000 #437747500] INFO -- : Processing by WelcomeController#index as HTML I, [2020-06-30T08:55:34.300000 #437747500] INFO -- : Rendering welcome/index.html.erb within layouts/application I, [2020-06-30T08:55:34.300000 #437747500] INFO -- : Rendered shared/_flash_messages.html.erb (0.0ms) I, [2020-06-30T08:55:34.300000 #437747500] INFO -- : Rendered welcome/index.html.erb within layouts/application (0.0ms) I, [2020-06-30T08:55:34.303000 #437747500] INFO -- : Rendering /opt/archivesspace/prod/archivesspace/plugins/aspace-import-excel/frontend/views/layout_head.html.erb I, [2020-06-30T08:55:34.303000 #437747500] INFO -- : Rendered /opt/archivesspace/prod/archivesspace/plugins/aspace-import-excel/frontend/views/layout_head.html.erb (0.0ms) I, [2020-06-30T08:55:34.304000 #437747500] INFO -- : Rendered shared/_login.html.erb (1.0ms) I, [2020-06-30T08:55:34.304000 #437747500] INFO -- : Rendered shared/_header_user.html.erb (1.0ms) I, [2020-06-30T08:55:34.305000 #437747500] INFO -- : Rendered shared/_header_global.html.erb (2.0ms) I, [2020-06-30T08:55:34.305000 #437747500] INFO -- : Rendered site/_branding.html.erb (0.0ms) I, [2020-06-30T08:55:34.305000 #437747500] INFO -- : Rendered site/_footer.html.erb (0.0ms) I, [2020-06-30T08:55:34.307000 #437747500] INFO -- : Rendered shared/_templates.html.erb (2.0ms) I, [2020-06-30T08:55:34.307000 #437747500] INFO -- : Completed 200 OK in 57ms (Views: 7.9ms) I, [2020-06-30T08:55:35.064000 #437747500] INFO -- : Rendered language_and_scripts/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.065000 #437747500] INFO -- : Rendered lang_materials/_template.html.erb (1.0ms) I, [2020-06-30T08:55:35.065000 #437747500] INFO -- : Rendered lang_materials/_subrecord_form_action.html.erb (0.0ms) I, [2020-06-30T08:55:35.102000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (39.0ms) I, [2020-06-30T08:55:35.103000 #437747500] INFO -- : Rendered dates/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.110000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (8.0ms) I, [2020-06-30T08:55:35.111000 #437747500] INFO -- : Rendered extents/_template.html.erb (1.0ms) I, [2020-06-30T08:55:35.117000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (7.0ms) I, [2020-06-30T08:55:35.164000 #437747500] INFO -- : Rendered revision_statements/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.165000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (1.0ms) I, [2020-06-30T08:55:35.166000 #437747500] INFO -- : Rendered related_accessions/_template.html.erb (1.0ms) I, [2020-06-30T08:55:35.166000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (1.0ms) I, [2020-06-30T08:55:35.168000 #437747500] INFO -- : Rendered terms/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.169000 #437747500] INFO -- : Rendered linked_agents/_template.html.erb (1.0ms) I, [2020-06-30T08:55:35.170000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (3.0ms) I, [2020-06-30T08:55:35.176000 #437747500] INFO -- : Rendered subjects/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.178000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (7.0ms) I, [2020-06-30T08:55:35.197000 #437747500] INFO -- : Rendered notes/_template.html.erb (19.0ms) I, [2020-06-30T08:55:35.244000 #437747500] INFO -- : Rendered notes/_form.html.erb (66.0ms) I, [2020-06-30T08:55:35.245000 #437747500] INFO -- : Rendered external_documents/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.246000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (2.0ms) I, [2020-06-30T08:55:35.247000 #437747500] INFO -- : Rendered rights_statements/_template.html.erb (0.0ms) I, [2020-06-30T08:55:35.257000 #437747500] INFO -- : Rendered shared/_subrecord_form.html.erb (11.0ms) I, [2020-06-30T08:55:35.257000 #437747500] INFO -- : Rendered resources/_form_container.html.erb (1096.0ms) I, [2020-06-30T08:55:35.257000 #437747500] INFO -- : Rendered resources/new.html.erb within layouts/application (1114.0ms) I, [2020-06-30T08:55:35.261000 #437747500] INFO -- : Completed 500 Internal Server Error in 1237ms F, [2020-06-30T08:55:35.268000 #437747500] FATAL -- : F, [2020-06-30T08:55:35.268000 #437747500] FATAL -- : ActionView::Template::Error (No such template: "rights_type_intellectual_property"): F, [2020-06-30T08:55:35.268000 #437747500] FATAL -- : 45: <% end %> 46: <% else %> 47: <%= form.list_for(form[name], "#{name}[]") do |item| %> 48: <% form.emit_template(template, item) %> 49: <% end %> 50: <% end %> 51: F, [2020-06-30T08:55:35.268000 #437747500] FATAL -- : F, [2020-06-30T08:55:35.268000 #437747500] FATAL -- : app/helpers/aspace_form_helper.rb:487:in `emit_template' app/views/rights_statements/_template.html.erb:57:in `block in _app_views_rights_statements__template_html_erb__2098435309_2698' app/helpers/aspace_form_helper.rb:492:in `emit_template' app/views/shared/_subrecord_form.html.erb:48:in `block in _app_views_shared__subrecord_form_html_erb__1528586581_2670' app/helpers/aspace_form_helper.rb:136:in `block in list_for' app/helpers/aspace_form_helper.rb:232:in `push' app/helpers/aspace_form_helper.rb:133:in `block in list_for' app/helpers/aspace_form_helper.rb:132:in `list_for' app/views/shared/_subrecord_form.html.erb:47:in `_app_views_shared__subrecord_form_html_erb__1528586581_2670' app/helpers/application_helper.rb:307:in `render_aspace_partial' app/views/resources/_form_container.html.erb:83:in `_app_views_resources__form_container_html_erb__1484080424_2976' app/helpers/application_helper.rb:307:in `render_aspace_partial' app/views/resources/new.html.erb:14:in `block in _app_views_resources_new_html_erb___934010705_2972' app/helpers/aspace_form_helper.rb:848:in `form_context' app/views/resources/new.html.erb:5:in `block in _app_views_resources_new_html_erb___934010705_2972' app/views/resources/new.html.erb:4:in `_app_views_resources_new_html_erb___934010705_2972' Matthew Baya Williams College OIT, Networks & Systems 413-597-3567 -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at hudmol.com Wed Jul 1 23:42:49 2020 From: james at hudmol.com (James Bullen) Date: Thu, 2 Jul 2020 13:42:49 +1000 Subject: [Archivesspace_Users_Group] help with API route for archival object notes In-Reply-To: References: Message-ID: Hi Karen, No worries. Chris? help was more to the point anyway ;) From your example, you should be able to reference the content with the bad tag like this: [?notes?][0][?content?][0] Cheers, James > On Jul 2, 2020, at 1:23 AM, Karen Miller wrote: > > Hello, James. > > Sorry, I just realized I addressed you as Chris instead of as James! My apologies! I was so thrilled to get some assistance that I skimmed through the signatures too quickly. > > Best, > Karen > > From: Karen Miller > Sent: Wednesday, July 01, 2020 9:50 AM > To: 'Archivesspace Users Group' > > Subject: RE: [Archivesspace_Users_Group] help with API route for archival object notes > > Hi Chris. > > I?ve been able to successfully retrieve & update nested elements from the Agent record, just not from the archival object notes record. But your description of them as ?repeating parts? of that record is helpful. Thanks! > > Karen > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of James Bullen > Sent: Tuesday, June 30, 2020 6:35 PM > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] help with API route for archival object notes > > > Hi Karen, > > The general rule is that anything you can GET from a uri can be modified and POSTed back to update it. > > So, GET the JSON for the archival_object as you are doing. Then modify the JSON (in this case the notes bit of it) to look how you want. Then POST it back to the same uri. > > Notes are nested subrecords (as are dates and others). These don?t have a life of their own, they are really just repeating parts of the top level record that they are contained within. > > Hope that helps.. > > > Cheers, > James > > > > On Jul 1, 2020, at 8:22 AM, Karen Miller > wrote: > > Good morning, ArchivesSpace users. > > I am a cataloger (*not* a developer) using the API to update ArchivesSpace. So far I?ve figured out how to add LCCNs to the authority_Id of Agent records and do a couple more updates that, in retrospect, were pretty simple. > > The next task I?d like to tackle, however, just seems like maybe it can?t be done. We?ve got a lot of notes with html tags in them and I would like to update those to valid tags. I can get the JSON for the notes in any particular archival object, but I don?t know how to specify the route to the note to change it. The JSON looks like this: > > 'notes': [{'content': ['This is a note with a bad tag'], > 'jsonmodel_type': 'note_singlepart', > 'persistent_id': '75ba0ec57e374b8b154551a69b4c311f', > 'publish': True, > 'type': 'abstract'}, > {'jsonmodel_type': 'note_multipart', > 'persistent_id': '66afa07b3214260078123236bbe1ff27', > 'publish': True, > 'subnotes': [{'content': 'This is a dippy note.', > 'jsonmodel_type': 'note_text', > 'publish': True}], > 'type': 'scopecontent'}], > > I got this using the route ?repositories/10/archival_objects/489763?, but I don?t know how to specify the note that I want in the JSON. For the agent authority_id I used the route ??/agents/people/ and specified the field like this: > > ['names'][0]['authority_id'] > > I?m hoping this is an easy question for somebody with more experience with the API and (especially) with JSON than I. I?m a little afraid the answer is that it can?t be done. Any advice will be appreciated! > > Karen > > Karen D. Miller > Monographic Cataloger/Metadata Specialist > Northwestern University Libraries > Northwestern University > 1970 Campus Drive > Evanston, IL 60208 > www.library.northwestern.edu > k-miller3 at northwestern.edu > 874.467.3462 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From k-miller3 at northwestern.edu Thu Jul 2 10:30:46 2020 From: k-miller3 at northwestern.edu (Karen Miller) Date: Thu, 2 Jul 2020 14:30:46 +0000 Subject: [Archivesspace_Users_Group] help with API route for archival object notes In-Reply-To: References: Message-ID: Thank you, Noah! The Python script looks like it?s exactly what I need. And I appreciate the SQL as well; one less thing for me to code! I think I have just enough Python skills now (i.e., almost none + a reference manual) to make your script work. Although I really miss cataloging print materials during the pandemic, I am really pleased to be able to learn a new skill while working from home. And I couldn?t have done it without examples, encouragement, and help from the ArchivesSpace community. Thank you! Karen From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Noah Huffman Sent: Wednesday, July 01, 2020 10:59 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] help with API route for archival object notes Hi Karen, I believe each note has a persistent identifier, so if you can use SQL to get the note identifiers you can address the problem notes that way. Here?s an example of some SQL that gets access restriction notes on archival objects including the identifiers: https://github.com/duke-libraries/archivesspace-duke-scripts/blob/master/sql/access_restriction_notes_on_aos.sql And, here?s an example of a python script that uses those note identifiers to make updates to those notes (based on a script I borrowed from Alicia Detelich at Yale): https://github.com/duke-libraries/archivesspace-duke-scripts/blob/master/python/duke_as_replace_notes.py#L40 I haven?t used these in a while, so I can?t confirm if they still work, but the general idea should still hold. -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ Pronouns: he / him / his From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Karen Miller Sent: Wednesday, July 1, 2020 11:23 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] help with API route for archival object notes Hello, James. Sorry, I just realized I addressed you as Chris instead of as James! My apologies! I was so thrilled to get some assistance that I skimmed through the signatures too quickly. Best, Karen From: Karen Miller Sent: Wednesday, July 01, 2020 9:50 AM To: 'Archivesspace Users Group' > Subject: RE: [Archivesspace_Users_Group] help with API route for archival object notes Hi Chris. I?ve been able to successfully retrieve & update nested elements from the Agent record, just not from the archival object notes record. But your description of them as ?repeating parts? of that record is helpful. Thanks! Karen From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of James Bullen Sent: Tuesday, June 30, 2020 6:35 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] help with API route for archival object notes Hi Karen, The general rule is that anything you can GET from a uri can be modified and POSTed back to update it. So, GET the JSON for the archival_object as you are doing. Then modify the JSON (in this case the notes bit of it) to look how you want. Then POST it back to the same uri. Notes are nested subrecords (as are dates and others). These don?t have a life of their own, they are really just repeating parts of the top level record that they are contained within. Hope that helps.. Cheers, James On Jul 1, 2020, at 8:22 AM, Karen Miller > wrote: Good morning, ArchivesSpace users. I am a cataloger (*not* a developer) using the API to update ArchivesSpace. So far I?ve figured out how to add LCCNs to the authority_Id of Agent records and do a couple more updates that, in retrospect, were pretty simple. The next task I?d like to tackle, however, just seems like maybe it can?t be done. We?ve got a lot of notes with html tags in them and I would like to update those to valid tags. I can get the JSON for the notes in any particular archival object, but I don?t know how to specify the route to the note to change it. The JSON looks like this: 'notes': [{'content': ['This is a note with a bad tag'], 'jsonmodel_type': 'note_singlepart', 'persistent_id': '75ba0ec57e374b8b154551a69b4c311f', 'publish': True, 'type': 'abstract'}, {'jsonmodel_type': 'note_multipart', 'persistent_id': '66afa07b3214260078123236bbe1ff27', 'publish': True, 'subnotes': [{'content': 'This is a dippy note.', 'jsonmodel_type': 'note_text', 'publish': True}], 'type': 'scopecontent'}], I got this using the route ?repositories/10/archival_objects/489763?, but I don?t know how to specify the note that I want in the JSON. For the agent authority_id I used the route ??/agents/people/ and specified the field like this: ['names'][0]['authority_id'] I?m hoping this is an easy question for somebody with more experience with the API and (especially) with JSON than I. I?m a little afraid the answer is that it can?t be done. Any advice will be appreciated! Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 _______________________________________________ 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 k-miller3 at northwestern.edu Thu Jul 2 10:30:47 2020 From: k-miller3 at northwestern.edu (Karen Miller) Date: Thu, 2 Jul 2020 14:30:47 +0000 Subject: [Archivesspace_Users_Group] help with API route for archival object notes In-Reply-To: References: Message-ID: Thanks, James. I will try this code as well as what Noah suggested. I really like being able to test out a specific change interactively before trying it in a script, so this is useful. Understanding how to access specific data in the JSON has been a big challenge for me. Karen From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of James Bullen Sent: Wednesday, July 01, 2020 10:43 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] help with API route for archival object notes Hi Karen, No worries. Chris? help was more to the point anyway ;) From your example, you should be able to reference the content with the bad tag like this: [?notes?][0][?content?][0] Cheers, James On Jul 2, 2020, at 1:23 AM, Karen Miller > wrote: Hello, James. Sorry, I just realized I addressed you as Chris instead of as James! My apologies! I was so thrilled to get some assistance that I skimmed through the signatures too quickly. Best, Karen From: Karen Miller Sent: Wednesday, July 01, 2020 9:50 AM To: 'Archivesspace Users Group' > Subject: RE: [Archivesspace_Users_Group] help with API route for archival object notes Hi Chris. I?ve been able to successfully retrieve & update nested elements from the Agent record, just not from the archival object notes record. But your description of them as ?repeating parts? of that record is helpful. Thanks! Karen From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of James Bullen Sent: Tuesday, June 30, 2020 6:35 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] help with API route for archival object notes Hi Karen, The general rule is that anything you can GET from a uri can be modified and POSTed back to update it. So, GET the JSON for the archival_object as you are doing. Then modify the JSON (in this case the notes bit of it) to look how you want. Then POST it back to the same uri. Notes are nested subrecords (as are dates and others). These don?t have a life of their own, they are really just repeating parts of the top level record that they are contained within. Hope that helps.. Cheers, James On Jul 1, 2020, at 8:22 AM, Karen Miller > wrote: Good morning, ArchivesSpace users. I am a cataloger (*not* a developer) using the API to update ArchivesSpace. So far I?ve figured out how to add LCCNs to the authority_Id of Agent records and do a couple more updates that, in retrospect, were pretty simple. The next task I?d like to tackle, however, just seems like maybe it can?t be done. We?ve got a lot of notes with html tags in them and I would like to update those to valid tags. I can get the JSON for the notes in any particular archival object, but I don?t know how to specify the route to the note to change it. The JSON looks like this: 'notes': [{'content': ['This is a note with a bad tag'], 'jsonmodel_type': 'note_singlepart', 'persistent_id': '75ba0ec57e374b8b154551a69b4c311f', 'publish': True, 'type': 'abstract'}, {'jsonmodel_type': 'note_multipart', 'persistent_id': '66afa07b3214260078123236bbe1ff27', 'publish': True, 'subnotes': [{'content': 'This is a dippy note.', 'jsonmodel_type': 'note_text', 'publish': True}], 'type': 'scopecontent'}], I got this using the route ?repositories/10/archival_objects/489763?, but I don?t know how to specify the note that I want in the JSON. For the agent authority_id I used the route ??/agents/people/ and specified the field like this: ['names'][0]['authority_id'] I?m hoping this is an easy question for somebody with more experience with the API and (especially) with JSON than I. I?m a little afraid the answer is that it can?t be done. Any advice will be appreciated! Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Thu Jul 2 10:55:45 2020 From: blake.carver at lyrasis.org (Blake Carver) Date: Thu, 2 Jul 2020 14:55:45 +0000 Subject: [Archivesspace_Users_Group] human readable URLs -- translation missing resource In-Reply-To: References: Message-ID: What version of ArchivesSpace are you running? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Knox, Ashley M. Sent: Wednesday, July 1, 2020 12:24 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] human readable URLs -- translation missing resource After implementing human readable URLs, did anyone see this in the staff interface beside the new field labels? 'translation missing: resource.public_url' and 'translation missing:resource.slug' It should only say public url and slug. Thank you for any tips. Of the available options, we changed these two items from false to true. use_human_readable_URLs - determines whether the options for creating human-readable URLs are shown in the staff interface and whether the URL shown in the public user interface for a record is the human-readable URL. (In order to prevent broken links, if this option was turned on at one time and then was turned off, the slugs created during that time remain in the records and the associated URLs will still work, but they will not be visible or editable through the staff interface. Only if the slugs are removed from the records will those URLs cease to work.) auto_generate_slugs_with_id - by default, auto-generated slugs are based on the name or title in the record. If you choose this option, records with meaningful identifiers (like accessions and resources) will have slugs based on those IDs. Within this configuration there are two additional options. Ashley Knox Digital Initiatives Librarian Randall Library University of North Carolina Wilmington knoxa at uncw.edu http://library.uncw.edu http://digitalcollections.uncw.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Thu Jul 2 11:22:07 2020 From: blake.carver at lyrasis.org (Blake Carver) Date: Thu, 2 Jul 2020 15:22:07 +0000 Subject: [Archivesspace_Users_Group] human readable URLs -- translation missing resource In-Reply-To: References: , Message-ID: Also, check your locales/en.yml are those values in there? Maybe the older locales were copied over and the new values are missing? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Blake Carver Sent: Thursday, July 2, 2020 10:55 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] human readable URLs -- translation missing resource What version of ArchivesSpace are you running? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Knox, Ashley M. Sent: Wednesday, July 1, 2020 12:24 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] human readable URLs -- translation missing resource After implementing human readable URLs, did anyone see this in the staff interface beside the new field labels? 'translation missing: resource.public_url' and 'translation missing:resource.slug' It should only say public url and slug. Thank you for any tips. Of the available options, we changed these two items from false to true. use_human_readable_URLs - determines whether the options for creating human-readable URLs are shown in the staff interface and whether the URL shown in the public user interface for a record is the human-readable URL. (In order to prevent broken links, if this option was turned on at one time and then was turned off, the slugs created during that time remain in the records and the associated URLs will still work, but they will not be visible or editable through the staff interface. Only if the slugs are removed from the records will those URLs cease to work.) auto_generate_slugs_with_id - by default, auto-generated slugs are based on the name or title in the record. If you choose this option, records with meaningful identifiers (like accessions and resources) will have slugs based on those IDs. Within this configuration there are two additional options. Ashley Knox Digital Initiatives Librarian Randall Library University of North Carolina Wilmington knoxa at uncw.edu http://library.uncw.edu http://digitalcollections.uncw.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Thu Jul 2 14:46:55 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 2 Jul 2020 18:46:55 +0000 Subject: [Archivesspace_Users_Group] Take a break with ArchivesSpace on Friday cancelled this week In-Reply-To: <6A076B5D-058B-45C0-8043-65CA448DF734@lyrasis.org> References: <6A076B5D-058B-45C0-8043-65CA448DF734@lyrasis.org> Message-ID: <19B3A349-A99A-4ACE-8133-FE47B33450E9@lyrasis.org> Dear ArchivesSpace Users, LYRASIS will be observing the 4th of July holiday tomorrow and staff will not be available for our standing Friday afternoon break. We will resume our Friday breaks with ArchivesSpace next Friday, July 10th. Thank you to everyone who joined us last week for a great chat. We look forward to seeing you again next Friday. Best, Jessica Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29073 bytes Desc: image001.jpg URL: From Jessica.Crouch at lyrasis.org Mon Jul 6 12:20:30 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 6 Jul 2020 16:20:30 +0000 Subject: [Archivesspace_Users_Group] Registration Now Open - ArchivesSpace 6th Annual Member Forum Message-ID: [A picture containing woman, holding, standing Description automatically generated] Registration is now open for the 6th Annual ArchivesSpace Member Forum! Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. Unlike previous years, ArchivesSpace will be holding its sixth Annual Member Forum virtually, on August 3-7, 2020, from 12pm-3pm ET each day via Zoom. This free event is a chance for ArchivesSpace members to come together to highlight the work they are doing in ArchivesSpace, show off new plugins or tools they?ve developed, and attend workshops and trainings on a variety of topics. As with our previous Annual Member Forums, it is being held in conjunction with the Society of American Archivists annual meeting, but it is not part of SAA and does not require registration for the SAA Annual Meeting. When: Presentations and breakout discussions will be held on August 3-4, 2020 from 12pm-3pm ET, and all individuals from ArchivesSpace member institutions are welcome to attend some or all of the sessions on these days. Small workshops covering specific elements of the ArchivesSpace application will be offered August 5-7, 2020 from 12pm-3pm ET. These workshops will be limited in capacity. Registrations for each day are separate and you must register for individually for all days you are interested in attending. Where: All online via Zoom, with opportunities to join via computer or phone. Who Can Attend: The ArchivesSpace Member Forum is open to individuals from ArchivesSpace member institutions only. To register, you must use an institutional email address associated with an ArchivesSpace member institution. Registrations using personal email addresses and addresses associated with non-member institutions will not be accepted. This means that events with limited capacity may fill before you are able to correct your registration. Online registration: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1422819333/ArchivesSpace+Member+Forum+2020 Registrations for each day of the Forum are separate. You will need to register for each day you are interested in attending to guarantee your spot. Registration for each activity is linked above the session in the agenda. Workshop attendance is limited. Discussion sessions on Tuesday, August 4, will occur in two separate zoom rooms. You must register for both Zoom Room A and B if you want to attend discussions in both rooms. The number of registrations available for the workshops on August 5-7 is limited. The total number of attendees is noted next to the registration. To give as many people as possible a chance to attend, you may register for only one workshop. Propose a session or topic: The program is still developing. If you would like to propose a session or topic for the forum, there is a short Google form for proposals available at https://forms.gle/DsZNqe2cANy5mS4S7. Proposals will be reviewed on a rolling basis. The last day that proposals will be accepted is July 15, 2020, and all notifications will be made by July 22, 2020. We will be recording the sessions on August 3, 2020 but will not be recording discussions or workshops. We encourage you to dip in and out of the live programs on August 3-4, 2020 as much as you can. Please feel free to contact ArchivesSpace Community Engagement Coordinator Jessica Crouch (jessica.crouch at lyrasis.org) with questions. We look forward to seeing many of you there! Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 66178 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 8535 bytes Desc: image002.jpg URL: From baileys at ou.edu Mon Jul 6 12:58:09 2020 From: baileys at ou.edu (Hoffner, Bailey E.) Date: Mon, 6 Jul 2020 16:58:09 +0000 Subject: [Archivesspace_Users_Group] AS Member Forum - Discussion Opportunity Message-ID: Hello All, I?ll be moderating a discussion for the upcoming Member Forum on ?Managing your ArchivesSpace Implementation in a Pandemic? with a specific focus on radical empathy (see full description on the schedule/registration page). I wanted to reach out to see if there are any other member institutions that would like to join me in this conversation. * Have you been navigating a similar at-home work environment while implementing AS? * Do you have specific input related to centering humans during this process, and how you have managed to extend radical empathy while continuing to make progress towards goals? * Would you like to share your own experiences of having radical empathy extended to you during this time? * Anything else that you might like to share! Please reach out to baileys at ou.edu if you?d like to join in this conversation. Thanks so much! -Bailey Bailey Hoffner, MLIS Metadata and Collections Management Archivist University of Oklahoma Libraries 405-325-1566 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lisa.Crane at claremont.edu Mon Jul 6 20:19:09 2020 From: Lisa.Crane at claremont.edu (Lisa Crane) Date: Tue, 7 Jul 2020 00:19:09 +0000 Subject: [Archivesspace_Users_Group] Importing container list Message-ID: Hello all! I am importing a container list using a brief EAD and I keep getting the following message: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! The following errors were found: indicator : Property is required but was missing For JSONModel(:top_container): #"top_container", "active_restrictions"=>[], "container_locations"=>[], "series"=>[], "collection"=>[], "uri"=>"/repositories/import/top_containers/import_4ba44ff1-d7a5-4818-aa78-25d4150a6ca9", "type"=>"box"}> In : <container class="cdata" label="Box" type="box"> ... </container> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Here is what one of my containers looks like: America 1956-1981 1 1 I can't tell what "property" I am missing? I have imported a lot of container lists using this method and have had no issues. Did something change that now requires me to add an additional "property"? Please advise. All the best, Lisa Lisa L. Crane | Western Americana Manuscripts Librarian | The Claremont Colleges Library 800 North Dartmouth Ave. | Claremont, CA 91711-5053 Phone (909) 607-0862 | lisa.crane at claremont.edu Pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Mon Jul 6 21:12:42 2020 From: mark.custer at yale.edu (Custer, Mark) Date: Tue, 7 Jul 2020 01:12:42 +0000 Subject: [Archivesspace_Users_Group] Importing container list In-Reply-To: References: Message-ID: Lisa, The snippet you provided below looks fine. Can you attach an example EAD file? Given the error about the "indicator" missing, though, it's possible that the file has an empty container tag in the EAD (e.g. ). If so, that would likely cause an error since every top container requires a container indicator (e.g. "1", from your EAD snippet). It also seems like the error is saying that the container element in question has a "class" attribute, which it shouldn't (although that should just be ignored by the importer), but it's impossible to say without seeing the full EAD file. Unfortunately the import error message won't give you a line number in the EAD file, but if you have specific ID attributes in your file, that can really help to hunt down the errors. For instance, if you added something like id='amitheproblem_1' to the first container element, id='amitheproblem_2' to the next, etc, then when the ArchivesSpace importer hits the first error, it should return that ID value after the "In:" part of the message. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Lisa Crane Sent: Monday, July 6, 2020 8:19 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Importing container list Hello all! I am importing a container list using a brief EAD and I keep getting the following message: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! The following errors were found: indicator : Property is required but was missing For JSONModel(:top_container): #"top_container", "active_restrictions"=>[], "container_locations"=>[], "series"=>[], "collection"=>[], "uri"=>"/repositories/import/top_containers/import_4ba44ff1-d7a5-4818-aa78-25d4150a6ca9", "type"=>"box"}> In : <container class="cdata" label="Box" type="box"> ... </container> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Here is what one of my containers looks like: America 1956-1981 1 1 I can?t tell what ?property? I am missing? I have imported a lot of container lists using this method and have had no issues. Did something change that now requires me to add an additional ?property?? Please advise. All the best, Lisa Lisa L. Crane | Western Americana Manuscripts Librarian | The Claremont Colleges Library 800 North Dartmouth Ave. | Claremont, CA 91711-5053 Phone (909) 607-0862 | lisa.crane at claremont.edu Pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lisa.Crane at claremont.edu Tue Jul 7 11:20:28 2020 From: Lisa.Crane at claremont.edu (Lisa Crane) Date: Tue, 7 Jul 2020 15:20:28 +0000 Subject: [Archivesspace_Users_Group] Importing container list In-Reply-To: References: Message-ID: Thank you, Mark! I was missing a box number! THANK YOU for the tip re: id='amitheproblem_1'! All the best, Lisa Lisa L. Crane | Western Americana Manuscripts Librarian | The Claremont Colleges Library 800 North Dartmouth Ave. | Claremont, CA 91711-5053 Phone (909) 607-0862 | lisa.crane at claremont.edu Pronouns: she/her/hers From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Monday, July 6, 2020 6:13 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Importing container list Lisa, The snippet you provided below looks fine. Can you attach an example EAD file? Given the error about the "indicator" missing, though, it's possible that the file has an empty container tag in the EAD (e.g. ). If so, that would likely cause an error since every top container requires a container indicator (e.g. "1", from your EAD snippet). It also seems like the error is saying that the container element in question has a "class" attribute, which it shouldn't (although that should just be ignored by the importer), but it's impossible to say without seeing the full EAD file. Unfortunately the import error message won't give you a line number in the EAD file, but if you have specific ID attributes in your file, that can really help to hunt down the errors. For instance, if you added something like id='amitheproblem_1' to the first container element, id='amitheproblem_2' to the next, etc, then when the ArchivesSpace importer hits the first error, it should return that ID value after the "In:" part of the message. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Lisa Crane > Sent: Monday, July 6, 2020 8:19 PM To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] Importing container list Hello all! I am importing a container list using a brief EAD and I keep getting the following message: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! The following errors were found: indicator : Property is required but was missing For JSONModel(:top_container): #"top_container", "active_restrictions"=>[], "container_locations"=>[], "series"=>[], "collection"=>[], "uri"=>"/repositories/import/top_containers/import_4ba44ff1-d7a5-4818-aa78-25d4150a6ca9", "type"=>"box"}> In : <container class="cdata" label="Box" type="box"> ... </container> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Here is what one of my containers looks like: America 1956-1981 1 1 I can't tell what "property" I am missing? I have imported a lot of container lists using this method and have had no issues. Did something change that now requires me to add an additional "property"? Please advise. All the best, Lisa Lisa L. Crane | Western Americana Manuscripts Librarian | The Claremont Colleges Library 800 North Dartmouth Ave. | Claremont, CA 91711-5053 Phone (909) 607-0862 | lisa.crane at claremont.edu Pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Tue Jul 7 11:32:43 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 7 Jul 2020 15:32:43 +0000 Subject: [Archivesspace_Users_Group] Webinar Tomorrow: Is It Roy E. Harrington or Roy S. Harrington?: How to Make Technology Work for You In an ArchivesSpace Data Cleanup Project Message-ID: <9FADCFD7-5026-4C82-81DC-077CF1AE4BED@lyrasis.org> Dear ArchivesSpace Users, ArchivesSpace will be offering another webinar focusing on ArchivesSpace data cleanup projects that can be accomplished in a work from home environment tomorrow, July 8, at 2pm ET. Most of us are doing our jobs under much different conditions than usual. As a browser-based system you can access from anywhere, ArchivesSpace is a tool that can be used when working remotely and many ArchivesSpace users are finding themselves executing large scale data cleanup projects that have only recently been prioritized. Title: Is It Roy E. Harrington or Roy S. Harrington?: How to Make Technology Work for You In an ArchivesSpace Data Cleanup Project When: July 8, 2020 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? 12:00pm PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_T5x0GFR8QHicozJwCsm05Q In order to provide a secure webinar experience and ensure adequate space in our Zoom environment, registration is now required for our webinars. Our webinars continue to be free and open to anyone using or interested in ArchivesSpace. Webinar description: This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Three processing archivists from the Rockefeller Archive Center will discuss collaborative approaches to mass data cleanup in ArchivesSpace. Presenters will share how they planned, reassessed, and executed various automated and manual processes for enhancing the quality of their institution?s descriptive data. This data includes agent records, dates, and access restriction notes. This discussion is based off of the RAC ArchivesSpace Cleanup blog series. Webinar presenters: Amy Berish is an Archivist at the Rockefeller Archive Center where she works as a member of the Processing team. Aside from processing incoming collections, she also contributes to various digital projects. Amy holds a Masters in Library and Information Science from the University of Pittsburgh. Katie Martin is an Assistant Archivist at the Rockefeller Archive Center where she processes collections of the Ford Foundation and works on projects with the digital team. She earned degrees in History and American Studies from Purdue University and received her MLS with a specialization in archives and records management from Indiana University. Darren Young is an Assistant Archivist at the Rockefeller Archive Center where he processes collections of the Ford Foundation and collaborates with the digital team on select projects. He earned a BA degree with majors in English Literature and History at the University of Connecticut and received his MLIS with a concentration in Archives Management from Simmons College (now Simmons University). Who should attend: While this webinar will focus on projects that can be undertaken in a work from home environment, this webinar will be useful to any archivist focusing on data cleanup in ArchivesSpace, those needing to export data out of ArchivesSpace and archivists working with legacy data. Questions? Contact Jessica at jessica.crouch at lyrasis.org if you have questions about this webinar or our other online events. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 8537 bytes Desc: image001.jpg URL: From Jessica.Crouch at lyrasis.org Thu Jul 9 11:18:10 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 9 Jul 2020 15:18:10 +0000 Subject: [Archivesspace_Users_Group] Take a break with ArchivesSpace on Fridays In-Reply-To: <43C3FEA3-953D-4C61-BE1D-862242BE1B4A@lyrasis.org> References: <4C151ED1-3A98-4217-908A-55C7BA8ED233@lyrasis.org> <939F1E31-3ECB-44AD-93A6-6634E8BFF8F7@lyrasis.org> <512F3C3D-C506-4E11-B5FB-4B9EBF4775B0@lyrasis.org> <614B918C-6F58-4D55-89F5-18680C71701B@lyrasis.org> <69AD5D49-2C12-450D-9763-D88A59297611@lyrasis.org> <43C3FEA3-953D-4C61-BE1D-862242BE1B4A@lyrasis.org> Message-ID: <3FCF35AF-3D09-48D1-963B-FB6788AD90F9@lyrasis.org> Dear ArchivesSpace Users, We?ll be resuming our casual Friday open calls via zoom at 12pm ET tomorrow. With no set agenda or presentation for these calls, this forum is an opportunity to connect, chat and recharge. Use this as a time to get help or talk about ArchivesSpace (or anything else) in an informal setting or just have a beverage with other ArchivesSpace users during this stressful time. Most of us are doing our jobs under much different conditions than usual. As a browser based system you can access from anywhere, the ArchivesSpace application may offer a sense of archival normalcy as we each adjust. And with a welcoming and robust member community all over the world, ArchivesSpace can also offer camaraderie when many of us may feel isolated from our colleagues or the professional communities we interact with regularly. We look forward to seeing everyone again tomorrow. When: Fridays Time: 12:00 p.m. ? 1:00 p.m. ET (9:00 a.m. ? 10:00 a.m. PT) Where: Zoom Join the call via the information below: Join Zoom Meeting https://lyrasis.zoom.us/j/281962467 Meeting ID: 281 962 467 One tap mobile +19292056099,,281962467# US (New York) +13126266799,,281962467# US (Chicago) Dial by your location +1 929 205 6099 US (New York) +1 312 626 6799 US (Chicago) +1 301 715 8592 US +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 253 215 8782 US 888 475 4499 US Toll-free 877 853 5257 US Toll-free Meeting ID: 281 962 467 Find your local number: https://lyrasis.zoom.us/u/awkFNWPxh We seek to provide a welcoming, fun, and safe community experience for everyone and adhere to Code4Lib?s CodeofConduct4Lib. The full text of the code of conduct is available at: http://bit.ly/coc4lib. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29073 bytes Desc: image001.jpg URL: From elizabeth.russell1 at maine.edu Fri Jul 10 13:09:45 2020 From: elizabeth.russell1 at maine.edu (Elizabeth Russell) Date: Fri, 10 Jul 2020 13:09:45 -0400 Subject: [Archivesspace_Users_Group] Collection use stats Message-ID: Hello Everyone! Does anyone know if there is an ability to somehow record collection use in ASpace? Right now we use paper requests, and then tabulate them - it's very time consuming, so we're wondering what our digital options are. I can't really figure out a way to use ASpace this way, but do you know of any plug-ins, etc. that could do this? I'm sure some of you are in the same boat - our budget was slashed so our thoughts about Aeon were dashed! Best, Beth -- Beth Russell Archivist / Special Collections Librarian University of Maine, 5729 Raymond H. Fogler Library Orono, ME 04469-5729 207.581.1676 elizabeth.russell1 at maine.edu http://www.library.umaine.edu/speccoll -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgd1 at williams.edu Fri Jul 10 13:06:10 2020 From: jgd1 at williams.edu (Drmacich, Jessika) Date: Fri, 10 Jul 2020 13:06:10 -0400 Subject: [Archivesspace_Users_Group] Resource records updates not appearing in public interface Message-ID: Hi all, As I update resource records in the staff interface, the updated records are not appearing as they should (or at all) in the public interface. Does anyone have any suggestions to remedy this? My IT cohort is attempting to update the config file, but I am not sure this is the answer. Could it be a server space issue? * we are running on the most updated version My very best, Jessika *Jessika Drmacich * *Records Manager & Digital Resources Archivist * *Williams College Libraries* *Special Collections* *413-597-4725 (o)* *she/her/hers* *Please Note: Due to COVID-19 library services have changed. See **the library?s Spring 2020 webpage for information on how to access collections and services. I am now working from home and I will be checking email regularly. I?m also available for virtual consultations via GoogleMeet.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From alancaster at cals.org Fri Jul 10 13:13:53 2020 From: alancaster at cals.org (Anna Lancaster) Date: Fri, 10 Jul 2020 17:13:53 +0000 Subject: [Archivesspace_Users_Group] Resource records updates not appearing in public interface In-Reply-To: References: Message-ID: I just had a similar issue and reindexing fixed the problem Anna Anna Lancaster Central Arkansas Library System From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Drmacich, Jessika Sent: Friday, July 10, 2020 12:06 PM To: Archivesspace Users Group ; Matthew Baya Subject: [Archivesspace_Users_Group] Resource records updates not appearing in public interface Hi all, As I update resource records in the staff interface, the updated records are not appearing as they should (or at all) in the public interface. Does anyone have any suggestions to remedy this? My IT cohort is attempting to update the config file, but I am not sure this is the answer. Could it be a server space issue? * we are running on the most updated version My very best, Jessika Jessika Drmacich Records Manager & Digital Resources Archivist Williams College Libraries Special Collections 413-597-4725 (o) she/her/hers Please Note: Due to COVID-19 library services have changed. See the library?s Spring 2020 webpage for information on how to access collections and services. I am now working from home and I will be checking email regularly. I?m also available for virtual consultations via GoogleMeet. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgd1 at williams.edu Fri Jul 10 13:18:04 2020 From: jgd1 at williams.edu (Jessika Drmacich) Date: Fri, 10 Jul 2020 13:18:04 -0400 Subject: [Archivesspace_Users_Group] Resource records updates not appearing in public interface In-Reply-To: References: Message-ID: <937B8797-BD65-4DE3-9357-ADB5131A86DC@williams.edu> Thanks, Anna! I just forwarded this to my systems cohort. We will try this and set up re-indexing once a week to make sure it happens. > On Jul 10, 2020, at 1:13 PM, Anna Lancaster wrote: > > ? > I just had a similar issue and reindexing fixed the problem > > Anna > > Anna Lancaster > Central Arkansas Library System > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Drmacich, Jessika > Sent: Friday, July 10, 2020 12:06 PM > To: Archivesspace Users Group ; Matthew Baya > Subject: [Archivesspace_Users_Group] Resource records updates not appearing in public interface > > Hi all, > > As I update resource records in the staff interface, the updated records are not appearing as they should (or at all) in the public interface. > > Does anyone have any suggestions to remedy this? My IT cohort is attempting to update the config file, but I am not sure this is the answer. Could it be a server space issue? > > * we are running on the most updated version > > My very best, > > Jessika > > Jessika Drmacich > Records Manager & Digital Resources Archivist > Williams College Libraries > Special Collections > 413-597-4725 (o) > she/her/hers > > Please Note: Due to COVID-19 library services have changed. See the library?s Spring 2020 webpage for information on how to access collections and services. I am now working from home and I will be checking email regularly. I?m also available for virtual consultations via GoogleMeet. > _______________________________________________ > 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 mcyzyk at jhu.edu Fri Jul 10 15:26:07 2020 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Fri, 10 Jul 2020 15:26:07 -0400 Subject: [Archivesspace_Users_Group] Unhandled Socket Exception Message-ID: Dear Aspace List, I am This Close to duplicating our ASpace in my Vagrant box.? But the very last step, booting it up, results in some nastiness: > Unhandled Java exception: java.net.SocketException: Permission denied > java.net.SocketException: Permission denied > ????????????????????????????? bind0 at sun/nio/ch/Net.java:-2 > ?????????????????????????????? bind at sun/nio/ch/Net.java:433 > ?????????????????????????????? bind at sun/nio/ch/Net.java:425 > ?????????????????????????????? bind at > sun/nio/ch/ServerSocketChannelImpl.java:220 > ?????????????????????????????? bind at > sun/nio/ch/ServerSocketAdaptor.java:85 > ?????????????????????????????? open at > org/eclipse/jetty/server/nio/SelectChannelConnector.java:182 > ??????????????????????????? doStart at > org/eclipse/jetty/server/AbstractConnector.java:311 > ??????????????????????????? doStart at > org/eclipse/jetty/server/nio/SelectChannelConnector.java:260 > ????????????????????????????? start at > org/eclipse/jetty/util/component/AbstractLifeCycle.java:59 > ??????????????????????????? doStart at > org/eclipse/jetty/server/Server.java:283 > ????????????????????????????? start at > org/eclipse/jetty/util/component/AbstractLifeCycle.java:59 > ???????????????????????????? invoke at java/lang/reflect/Method.java:498 > ? invokeDirectWithExceptionHandling at > org/jruby/javasupport/JavaMethod.java:438 > ?????????????????????? invokeDirect at > org/jruby/javasupport/JavaMethod.java:302 > ?????????????? invokeOther148:start at launcher/launcher.rb:92 > ?????????????????????? start_server at launcher/launcher.rb:92 > ??????? invokeOther321:start_server at launcher/launcher.rb:173 > ?????????????????????????????? main at launcher/launcher.rb:173 > ??????????????? invokeOther454:main at launcher/launcher.rb:261 > ????????????????????????????
at launcher/launcher.rb:261 > ??????????????? invokeWithArguments at > java/lang/invoke/MethodHandle.java:627 > ????????????????????????? runScript at org/jruby/Ruby.java:827 > ??????????????????????? runNormally at org/jruby/Ruby.java:746 > ??????????????????????? runNormally at org/jruby/Ruby.java:764 > ??????????????????????? runFromMain at org/jruby/Ruby.java:577 > ????????????????????? doRunFromMain at org/jruby/Main.java:417 > ??????????????????????? internalRun at org/jruby/Main.java:305 > ??????????????????????????????? run at org/jruby/Main.java:232 > ?????????????????????????????? main at org/jruby/Main.java:204 This is on Ubuntu**20.04 LTS, OpenJDK8, ASpace 2.5.1.? (And is all is preparation for upgrading to 2.7.1) From what I'm reading this may have something to do with the Java MySQL Connector attempting to use "native sockets" instead of IPV4 for its connectivity.? So just before attempting to boot ASpace, I do this: sudo export JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true" Still no joy. Any advice on how to handle this Unhandled Socket Exception would be greatly appreciated. THIS close! Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at jhu.edu Mon Jul 13 09:12:59 2020 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Mon, 13 Jul 2020 09:12:59 -0400 Subject: [Archivesspace_Users_Group] Unhandled Socket Exception In-Reply-To: References: Message-ID: <77daf504-8e50-5cfc-241b-92607d3ec882@jhu.edu> All, So there is a record of this in the List, I just figured out the solution to this problem: I was trying to run ASpace as a non-root user on Port 80.? You cannot do that.? The Port must be above 1024 for a non-root user. Onward! Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/10/20 3:26 PM, Mark Cyzyk wrote: > > Dear Aspace List, > > I am This Close to duplicating our ASpace in my Vagrant box.? But the > very last step, booting it up, results in some nastiness: > >> Unhandled Java exception: java.net.SocketException: Permission denied >> java.net.SocketException: Permission denied >> ????????????????????????????? bind0 at sun/nio/ch/Net.java:-2 >> ?????????????????????????????? bind at sun/nio/ch/Net.java:433 >> ?????????????????????????????? bind at sun/nio/ch/Net.java:425 >> ?????????????????????????????? bind at >> sun/nio/ch/ServerSocketChannelImpl.java:220 >> ?????????????????????????????? bind at >> sun/nio/ch/ServerSocketAdaptor.java:85 >> ?????????????????????????????? open at >> org/eclipse/jetty/server/nio/SelectChannelConnector.java:182 >> ??????????????????????????? doStart at >> org/eclipse/jetty/server/AbstractConnector.java:311 >> ??????????????????????????? doStart at >> org/eclipse/jetty/server/nio/SelectChannelConnector.java:260 >> ????????????????????????????? start at >> org/eclipse/jetty/util/component/AbstractLifeCycle.java:59 >> ??????????????????????????? doStart at >> org/eclipse/jetty/server/Server.java:283 >> ????????????????????????????? start at >> org/eclipse/jetty/util/component/AbstractLifeCycle.java:59 >> ???????????????????????????? invoke at java/lang/reflect/Method.java:498 >> ? invokeDirectWithExceptionHandling at >> org/jruby/javasupport/JavaMethod.java:438 >> ?????????????????????? invokeDirect at >> org/jruby/javasupport/JavaMethod.java:302 >> ?????????????? invokeOther148:start at launcher/launcher.rb:92 >> ?????????????????????? start_server at launcher/launcher.rb:92 >> ??????? invokeOther321:start_server at launcher/launcher.rb:173 >> ?????????????????????????????? main at launcher/launcher.rb:173 >> ??????????????? invokeOther454:main at launcher/launcher.rb:261 >> ????????????????????????????
at launcher/launcher.rb:261 >> ??????????????? invokeWithArguments at >> java/lang/invoke/MethodHandle.java:627 >> ????????????????????????? runScript at org/jruby/Ruby.java:827 >> ??????????????????????? runNormally at org/jruby/Ruby.java:746 >> ??????????????????????? runNormally at org/jruby/Ruby.java:764 >> ??????????????????????? runFromMain at org/jruby/Ruby.java:577 >> ????????????????????? doRunFromMain at org/jruby/Main.java:417 >> ??????????????????????? internalRun at org/jruby/Main.java:305 >> ??????????????????????????????? run at org/jruby/Main.java:232 >> ?????????????????????????????? main at org/jruby/Main.java:204 > > This is on Ubuntu**20.04 LTS, OpenJDK8, ASpace 2.5.1.? (And is all is > preparation for upgrading to 2.7.1) > > From what I'm reading this may have something to do with the Java > MySQL Connector attempting to use "native sockets" instead of IPV4 for > its connectivity.? So just before attempting to boot ASpace, I do this: > > sudo export JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true" > > > Still no joy. > > Any advice on how to handle this Unhandled Socket Exception would be > greatly appreciated. > > THIS close! > > Mark > -- > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Jul 13 10:58:42 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 13 Jul 2020 14:58:42 +0000 Subject: [Archivesspace_Users_Group] Deadline extended - Call for speakers for the ArchivesSpace 6th Annual Member Forum Message-ID: Dear ArchivesSpace Members, The deadline for submitting proposals for the sixth Annual Member Forum being held virtually on August 3-7, 2020, from 12pm-3pm ET has been extended to July 27, 2020. Just as in previous years, this free event is a chance for ArchivesSpace members to come together to highlight the work they are doing in ArchivesSpace, show off new plugins or tools they?ve developed, and attend workshops and trainings on a variety of topics. As with our previous Annual Member Forums, it is being held in conjunction with the Society of American Archivists annual meeting, but it is not part of SAA and does not require registration for the SAA Annual Meeting. There is a short Google form for proposals available at https://forms.gle/DsZNqe2cANy5mS4S7. Proposals will be reviewed on a rolling basis. The last day that proposals will be accepted has been extended to July 27, 2020, and all notifications will be made by July 29, 2020. Presentations and breakout discussions will be held on August 3-4, 2020, and all individuals from ArchivesSpace member institutions are welcome to attend some or all of the sessions on these days. Small workshops covering specific elements of the ArchivesSpace application will be offered August 5-7, 2020. These workshops will be limited in capacity. To view the agenda or register for the forum, visit https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1422819333/ArchivesSpace+Member+Forum+2020. If you have any questions or other suggestions at this point, please feel free to email Jessica at jessica.crouch at lyrasis.org. We look forward to ?seeing? you soon! Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29062 bytes Desc: image001.jpg URL: From Jessica.Crouch at lyrasis.org Tue Jul 14 12:47:52 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 14 Jul 2020 16:47:52 +0000 Subject: [Archivesspace_Users_Group] Webinar Tomorrow: Integrating ArchivesSpace with Drupal and Islandora at University of Nevada, Las Vegas Libraries Message-ID: Dear ArchivesSpace Users, The next webinar in the Integrations with ArchivesSpace series will be tomorrow, July 15, at 2pm ET. Each webinar in this series highlights an integration with another application used in archives that ArchivesSpace members have worked on or requested. Our ninth webinar in this series will discuss integration with Drupal 8 and Islandora at the University of Nevada, Las Vegas. When: July 15, 2020 Time: 2:00 p.m. ? 3:00 p.m. ET (11:00 a.m. ? noon PT) Where: Zoom Registration: https://lyrasis.zoom.us/webinar/register/WN_9yfEhfHqR5exk5YUazX1hA In order to provide a secure webinar experience and ensure adequate space in our Zoom environment, registration is now required for our webinars. Our webinars continue to be free and open to anyone using or interested in ArchivesSpace. Webinar description: This webinar will be recorded and made available on the ArchivesSpace YouTube channel. Seth Shaw will present an ArchivesSpace integration with Drupal 8. Drupal is a popular Content Management System widely used for building websites and is the foundational component of the popular Islandora 8 repository software. The ArchivesSpace Drupal module (https://www.drupal.org/project/archivesspace) allows Drupal and Islandora-based websites to present archival descriptions harvested from the ArchivesSpace API. This integration allows special collections and archives to build a single integrated interface combining both archival description from ArchivesSpace and digital objects in an Islandora 8 repository. This webinar will demonstrate how the integration works and how it can be used with Islandora 8. It will also demonstrate how it is being used at the UNLV Special Collections and Archives in their forthcoming repository site. Webinar Presenter: Seth Shaw is an Application Developer for UNLV Libraries dedicated to Special Collections and Archives. Previously, he was the Electronic Records Archivist for Duke University and an Assistant Professor of Archival Studies at Clayton State University. He has been developing IT solutions for special collections and archives, off and on, since his days as an undergraduate student. Who should attend: Anyone interested in learning more about using ArchivesSpace with both Drupal and Islandora, integrating Drupal and ArchivesSpace or who has already developed an integration for working with Islandora and ArchivesSpace. Questions? Contact Jessica at jessica.crouch at lyrasis.org if you have questions about this webinar or the Integrations with ArchivesSpace webinar series. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29062 bytes Desc: image001.jpg URL: From scheirw at newschool.edu Tue Jul 14 13:30:22 2020 From: scheirw at newschool.edu (Wendy Scheir) Date: Tue, 14 Jul 2020 13:30:22 -0400 Subject: [Archivesspace_Users_Group] version 2.8 release date? Message-ID: Hi, We are intending to migrate to ASpace from AT in the very near future. We're aware of v2.8-RC, but Is there an anticipated release date for v.2.8? Many thanks, Wendy ____________________________________ WENDY SCHEIR *DIRECTOR* 66 5TH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212.229.5942 x2888 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Tue Jul 14 13:44:17 2020 From: mark.custer at yale.edu (Custer, Mark) Date: Tue, 14 Jul 2020 17:44:17 +0000 Subject: [Archivesspace_Users_Group] version 2.8 release date? In-Reply-To: References: Message-ID: Wendy, I'll let others weigh in about 2.8, but I expect it should be released soon. That said, if you are planning on using the AT to ASpace migration tool (i.e. https://github.com/archivesspace/at-migration), then it looks like you would need to start off with ArchivesSpace 2.6. Once the migration from the AT is complete (which has a lot of little gotchas, but in general does all of the heavy lifting), then you could go directly from 2.6 to 2.8 (or any newer version, without having to upgrade to each release in between). Starting with ArchivesSpace 2.7, though, there were changes with how languages and scripts of materials are recorded in ArchivesSpace, so that post-2.6 upgrade will also likely require some additional updates to your data depending on how everything is recorded in the AT now. We are about to upgrade to version 2.7.1 from 2.4.1, so we haven't gone through that particular process yet, but we will be doing it soon. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Wendy Scheir Sent: Tuesday, July 14, 2020 1:30 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] version 2.8 release date? Hi, We are intending to migrate to ASpace from AT in the very near future. We're aware of v2.8-RC, but Is there an anticipated release date for v.2.8? Many thanks, Wendy ____________________________________ WENDY SCHEIR DIRECTOR [https://docs.google.com/uc?export=download&id=16Nic6T4ZK1k1BhLOUToez7KP5Tzv8f9o&revid=0B4enrSUaFYtfdnV0R3E3bEkvek9LUVdsbkRIVUNJaXh1MU9VPQ] 66 5TH AVENUE, NEW YORK, NY 10011 scheirw at newschool.edu T 212.229.5942 x2888 Explore the Archives | Digital Collections from the Archives | New School Histories | @tnsarchives -------------- next part -------------- An HTML attachment was scrubbed... URL: From scheirw at newschool.edu Thu Jul 16 13:39:23 2020 From: scheirw at newschool.edu (Wendy Scheir) Date: Thu, 16 Jul 2020 13:39:23 -0400 Subject: [Archivesspace_Users_Group] version 2.8 release date? In-Reply-To: References: Message-ID: Thanks so much, Mark--that's really useful information. No one has weighed in on the v2.8 release date, as of yet. Thanks, Wendy On Tue, Jul 14, 2020 at 1:44 PM Custer, Mark wrote: > Wendy, > > I'll let others weigh in about 2.8, but I expect it should be released > soon. That said, if you are planning on using the AT to ASpace migration > tool (i.e. https://github.com/archivesspace/at-migration), then it looks > like you would need to start off with ArchivesSpace 2.6. Once the > migration from the AT is complete (which has a lot of little gotchas, but > in general does all of the heavy lifting), then you could go directly > from 2.6 to 2.8 (or any newer version, without having to upgrade to each > release in between). > > Starting with ArchivesSpace 2.7, though, there were changes with how > languages and scripts of materials are recorded in ArchivesSpace, so that > post-2.6 upgrade will also likely require some additional updates to your > data depending on how everything is recorded in the AT now. We are about > to upgrade to version 2.7.1 from 2.4.1, so we haven't gone through that > particular process yet, but we will be doing it soon. > > Mark > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Wendy Scheir > *Sent:* Tuesday, July 14, 2020 1:30 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] version 2.8 release date? > > Hi, > > We are intending to migrate to ASpace from AT in the very near future. > We're aware of v2.8-RC, but Is there an anticipated release date for v.2.8? > > Many thanks, > Wendy > > ____________________________________ > > WENDY SCHEIR > *DIRECTOR* > > 66 5TH AVENUE, NEW YORK, NY 10011 > scheirw at newschool.edu > > T 212.229.5942 x2888 > > Explore the Archives > > | Digital Collections from the Archives > > | New School Histories > > | @tnsarchives > > > _______________________________________________ > 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 Thu Jul 16 14:15:59 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 16 Jul 2020 18:15:59 +0000 Subject: [Archivesspace_Users_Group] Take a break with ArchivesSpace on Fridays In-Reply-To: <69AD5D49-2C12-450D-9763-D88A59297611@lyrasis.org> References: <4C151ED1-3A98-4217-908A-55C7BA8ED233@lyrasis.org> <939F1E31-3ECB-44AD-93A6-6634E8BFF8F7@lyrasis.org> <512F3C3D-C506-4E11-B5FB-4B9EBF4775B0@lyrasis.org> <614B918C-6F58-4D55-89F5-18680C71701B@lyrasis.org> <69AD5D49-2C12-450D-9763-D88A59297611@lyrasis.org> Message-ID: <24DA2EB0-8EA2-42E8-9EC1-2377BAE51368@lyrasis.org> Dear ArchivesSpace Users, We?ll be hosting another casual open call via zoom at 12pm ET tomorrow. With no set agenda or presentation for these calls, this forum is an opportunity to connect, chat and recharge. Use this as a time to get help or talk about ArchivesSpace (or anything else) in an informal setting or just have a beverage with other ArchivesSpace users during this stressful time. Most of us are doing our jobs under much different conditions than usual. As a browser based system you can access from anywhere, the ArchivesSpace application may offer a sense of archival normalcy as we each adjust. And with a welcoming and robust member community all over the world, ArchivesSpace can also offer camaraderie when many of us may feel isolated from our colleagues or the professional communities we interact with regularly. Thank you to everyone who joined us last week for a great chat. We hope to see you all tomorrow. When: Fridays Time: 12:00 p.m. ? 1:00 p.m. ET (9:00 a.m. ? 10:00 a.m. PT) Where: Zoom Join the call via the information below: Join Zoom Meeting https://lyrasis.zoom.us/j/281962467 Meeting ID: 281 962 467 One tap mobile +19292056099,,281962467# US (New York) +13126266799,,281962467# US (Chicago) Dial by your location +1 929 205 6099 US (New York) +1 312 626 6799 US (Chicago) +1 301 715 8592 US +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 253 215 8782 US 888 475 4499 US Toll-free 877 853 5257 US Toll-free Meeting ID: 281 962 467 Find your local number: https://lyrasis.zoom.us/u/awkFNWPxh We seek to provide a welcoming, fun, and safe community experience for everyone and adhere to Code4Lib?s CodeofConduct4Lib. The full text of the code of conduct is available at: http://bit.ly/coc4lib. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29072 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Thu Jul 16 15:52:22 2020 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 16 Jul 2020 19:52:22 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v2.8.0 now available Message-ID: ArchivesSpace is announcing the availability of v2.8.0. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.8.0. This release contains program-led and community pull requests that provide feature enhancements, bug fixes, infrastructure improvements, and documentation updates. Some items of note include the ability to merge top containers, new browse, search, and sort preferences in the staff interface, some improvements to search and display in the public interface, additional display and faceting options in the background jobs area, bug fixes and accessibility improvements. Developers at Harvard University contributed several new features related to containers and locations from the specification they circulated in the community last year. Fans of the popular Harvard import plugin will be pleased to see that its functionality is now included in ArchivesSpace, courtesy of our work with the plugin's original developer, Bobbi Fox. Please note that if you used the plugin previously you will need to disable it before starting up ArchivesSpace post-upgrade. Thanks very much to community members Andrew Morrison, Austin Schaffer, Dave Mayo, David P. Steelman, Douglas Simon, Katie Amaral, Mark Custer, Mark Triggs, Matt Patterson, Michael Vandermillen, and Peter Heiner for their code contributions to this release. Program team members Lora Woodford and Mark Cooper wrote extensive code and supervised the work of the contractors we worked with us on this release: Bobbi Fox, Brian Zelip, Sarah Morrissey, and Manny Rodriguez. As always this release would not have been possible without the substantial efforts of our Development Prioritization sub-team, Testing sub-team, Technical Documentation sub-team, User Documentation sub-team, and Core Committers Group. Information on upgrading to a new version of ArchivesSpace is available at https://archivesspace.github.io/tech-docs/administration/upgrading.html. Please let us know if you have any questions or need help upgrading. This is the last release where our primary technical documentation will live at https://archivesspace.github.io/archivesspace/. If you'd like to get a jump on things, please change your bookmarks to https://archivesspace.github.io/tech-docs/ for all updates going forward. Lastly, I want to acknowledge that these are incredibly tough times for so many of us. Even more than usual, I've really appreciated all our team and community members have done to continue making ArchivesSpace better in the face of many challenges. Thanks for all your help and for letting us know how important the ArchivesSpace application and community have been to you in these times. 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: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From na207 at cam.ac.uk Wed Jul 22 10:20:16 2020 From: na207 at cam.ac.uk (Natalie Adams) Date: Wed, 22 Jul 2020 14:20:16 +0000 Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Message-ID: Dear all, Are there any repositories on the list using ArchivesSpace for agent records who would be willing to share any guidance they have prepared for users/cataloguers about creating agent records? I'm specifically interested in conventions for entering compound and hyphenated surnames or last names. Any advice would be really helpful. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library Natalie Adams Systems Archivist Cambridge University Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From VivianLea.Solek at Kofc.Org Wed Jul 22 11:12:01 2020 From: VivianLea.Solek at Kofc.Org (Solek, VivianLea) Date: Wed, 22 Jul 2020 15:12:01 +0000 Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames In-Reply-To: References: Message-ID: Please share to the list. I would be interested in this as well. Many thanks! VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Natalie Adams Sent: Wednesday, July 22, 2020 10:20 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Dear all, Are there any repositories on the list using ArchivesSpace for agent records who would be willing to share any guidance they have prepared for users/cataloguers about creating agent records? I'm specifically interested in conventions for entering compound and hyphenated surnames or last names. Any advice would be really helpful. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library Natalie Adams Systems Archivist Cambridge University Library CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmichelson at smith.edu Wed Jul 22 11:17:38 2020 From: dmichelson at smith.edu (Daniel Michelson) Date: Wed, 22 Jul 2020 11:17:38 -0400 Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames In-Reply-To: References: Message-ID: Hi Natalie, Could you say more about why compound or hyphenated surnames would require special treatment? Can't they be entered as is? I may not have understood your question. All the best, Dan On Wed, Jul 22, 2020 at 10:20 AM Natalie Adams wrote: > Dear all, > > Are there any repositories on the list using ArchivesSpace for agent > records who would be willing to share any guidance they have prepared for > users/cataloguers about creating agent records? I'm specifically interested > in conventions for entering compound and hyphenated surnames or last names. > > Any advice would be really helpful. > > Best wishes, > > Natalie > > > Natalie Adams > Systems Archivist > Cambridge University Library > > > Natalie Adams > Systems Archivist > Cambridge University Library > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Dan Michelson Project Manager Archivist Smith College Special Collections The Special Collections reading room is closed. As of March 18th, all Special Collections staff will be working remotely. Smith course support is our primary responsibility at this time. Minimal reference services will be managed remotely by staff. Reference inquiries that require access to physical materials will be held in order of when they were received and responded to once the campus is reopened. Expect a four to six week delay, minimum. There is a moratorium on digitization services. For information about Smith College?s response to Covid-19, please visit the college?s official website . For information about library services during this time, information is available on our website . -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.neely at bodleian.ox.ac.uk Wed Jul 22 11:24:09 2020 From: matthew.neely at bodleian.ox.ac.uk (Matthew Neely) Date: Wed, 22 Jul 2020 15:24:09 +0000 Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames In-Reply-To: References: Message-ID: Hi Natalie, We've followed the UK's NCA Rules for Names in our implementation (a practice we have used historically at the Bodleian). For example, Violet Bonham Carter is Carter | Lady | Helen Violet | Bonham | 1887-1969 | n?e Asquith | Baroness Asquith of Yarnbury | Liberal political figure in the Primary Part of Name field in the Agent record. Best wishes, Matthew ---------------------------------- Matthew Neely Senior Archivist Special Collections Bodleian Libraries Tel: 01865 287158 Post: The Weston Library, Broad Street, Oxford, OX1 3BG Email: matthew.neely at bodleian.ox.ac.uk Web: http://www.bodleian.ox.ac.uk/weston From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Natalie Adams Sent: 22 July 2020 15:20 To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Dear all, Are there any repositories on the list using ArchivesSpace for agent records who would be willing to share any guidance they have prepared for users/cataloguers about creating agent records? I'm specifically interested in conventions for entering compound and hyphenated surnames or last names. Any advice would be really helpful. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library Natalie Adams Systems Archivist Cambridge University Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corey.Schmidt at uga.edu Wed Jul 22 11:54:56 2020 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Wed, 22 Jul 2020 15:54:56 +0000 Subject: [Archivesspace_Users_Group] Update a Resource via the API Message-ID: Dear all, Hello, this is Corey Schmidt, ArchivesSpace Project Manager at the University of Georgia. I hope you all are doing well and staying cool! I'm trying to update records via the API using the Update a Resource endpoint (https://archivesspace.github.io/archivesspace/api/#update-a-resource). I found Duke made a script (https://github.com/duke-libraries/archivesspace-duke-scripts/blob/master/python/asnake_update_all_resources_and_aos.py) to do this very thing and I modeled my request on that example. I also found what I think is the code for the endpoint, found in backend/app/controllers/resource.rb file, line 114 (https://github.com/archivesspace/archivesspace/blob/0c4cb2dd263bbeacdbce70567ccbb86634cde769/backend/app/controllers/resource.rb#L114). However, no matter the combinations I try for the request, I'm getting a error with the following message: "error":"Had some trouble parsing your request: unexpected token at The following is the code I'm running in python: get_resource = client.get('/repositories/5/resources/1814') print(get_resource.text) resource = json.loads(get_resource.text) resource["restrictions"] = True print(json.dumps(resource)) update_resource = client.post('/repositories/5/resources/1814', json=json.dumps(resource)) # update_resource = client.post('/repositories/5/resources/1814', params={"id": 1814, "resource": json.dumps(resource), "repo_id": 5}) # the last line produces this error: {"error":"Had some trouble parsing your request: A JSON text must at least contain two octets!"} print(update_resource, update_resource.text) I've attached the json file to this email. Any help would be greatly appreciated. Thanks! Sincerely, Corey Schmidt ArchivesSpace Project Manager University of Georgia Special Collections Libraries Email: Corey.Schmidt at uga.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: resource.json Type: application/json Size: 15416 bytes Desc: resource.json URL: From na207 at cam.ac.uk Wed Jul 22 12:06:07 2020 From: na207 at cam.ac.uk (Natalie Adams) Date: Wed, 22 Jul 2020 16:06:07 +0000 Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames In-Reply-To: References: , Message-ID: Dear Matthew and Daniel, Many thanks for replying so quickly. Matthew- could you share details of how Violet Bonham Carter's agent record is constructed in your staff interface? Daniel- the issue with the UK's NCA Rules is that the primary part of the name is the final element of a compound or hyphenated surname (Carter in Matthew's example). I wanted to check we'd be right to construct an agent record like this:- Primary part of name: Carter Rest of name: Helen Violet Bonham Not Primary part of name: Bonham Carter Rest of name: Helen Violet A sanity check with the listserv would be reassuring! Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Matthew Neely Sent: 22 July 2020 16:24 To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Hi Natalie, We?ve followed the UK?s NCA Rules for Names in our implementation (a practice we have used historically at the Bodleian). For example, Violet Bonham Carter is Carter | Lady | Helen Violet | Bonham | 1887-1969 | n?e Asquith | Baroness Asquith of Yarnbury | Liberal political figure in the Primary Part of Name field in the Agent record. Best wishes, Matthew ---------------------------------- Matthew Neely Senior Archivist Special Collections Bodleian Libraries Tel: 01865 287158 Post: The Weston Library, Broad Street, Oxford, OX1 3BG Email: matthew.neely at bodleian.ox.ac.uk Web: http://www.bodleian.ox.ac.uk/weston From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Natalie Adams Sent: 22 July 2020 15:20 To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Dear all, Are there any repositories on the list using ArchivesSpace for agent records who would be willing to share any guidance they have prepared for users/cataloguers about creating agent records? I'm specifically interested in conventions for entering compound and hyphenated surnames or last names. Any advice would be really helpful. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library Natalie Adams Systems Archivist Cambridge University Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From KennedyN at si.edu Wed Jul 22 12:25:18 2020 From: KennedyN at si.edu (Kennedy, Nancy) Date: Wed, 22 Jul 2020 16:25:18 +0000 Subject: [Archivesspace_Users_Group] Update a Resource via the API In-Reply-To: References: Message-ID: Hi Corey - When you post your changes back, try this: client.post('/repositories/5/resources/1814', json=resource) Nancy Kennedy Smithsonian Institution ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Corey Schmidt Sent: Wednesday, July 22, 2020 11:54 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Update a Resource via the API External Email - Exercise Caution Dear all, Hello, this is Corey Schmidt, ArchivesSpace Project Manager at the University of Georgia. I hope you all are doing well and staying cool! I'm trying to update records via the API using the Update a Resource endpoint (https://archivesspace.github.io/archivesspace/api/#update-a-resource). I found Duke made a script (https://github.com/duke-libraries/archivesspace-duke-scripts/blob/master/python/asnake_update_all_resources_and_aos.py) to do this very thing and I modeled my request on that example. I also found what I think is the code for the endpoint, found in backend/app/controllers/resource.rb file, line 114 (https://github.com/archivesspace/archivesspace/blob/0c4cb2dd263bbeacdbce70567ccbb86634cde769/backend/app/controllers/resource.rb#L114). However, no matter the combinations I try for the request, I'm getting a error with the following message: "error":"Had some trouble parsing your request: unexpected token at The following is the code I'm running in python: get_resource = client.get('/repositories/5/resources/1814') print(get_resource.text) resource = json.loads(get_resource.text) resource["restrictions"] = True print(json.dumps(resource)) update_resource = client.post('/repositories/5/resources/1814', json=json.dumps(resource)) # update_resource = client.post('/repositories/5/resources/1814', params={"id": 1814, "resource": json.dumps(resource), "repo_id": 5}) # the last line produces this error: {"error":"Had some trouble parsing your request: A JSON text must at least contain two octets!"} print(update_resource, update_resource.text) I've attached the json file to this email. Any help would be greatly appreciated. Thanks! Sincerely, Corey Schmidt ArchivesSpace Project Manager University of Georgia Special Collections Libraries Email: Corey.Schmidt at uga.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From ldfs at umn.edu Wed Jul 22 12:40:56 2020 From: ldfs at umn.edu (Lara Friedman-Shedlov) Date: Wed, 22 Jul 2020 11:40:56 -0500 Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames In-Reply-To: References: Message-ID: I don't know anything about the UK rules for this, so I'm curious, especially as a person with a hyphenated last name. I consider that the primary part of my name is "Friedman-Shedlov," NOT "Shedlov," and if I were creating an agent record for my name, my understanding is that the primary part would indeed by "Friedman-Shedlov," going by the rules we use here in the U.S. However, it is definitely more ambiguous with compound names that are not hyphenated. / Lara Friedman-Shedlov On Wed, Jul 22, 2020 at 11:06 AM Natalie Adams wrote: > Dear Matthew and Daniel, > > Many thanks for replying so quickly. > > Matthew- could you share details of how Violet Bonham Carter's agent > record is constructed in your staff interface? > > Daniel- the issue with the UK's NCA Rules is that the primary part of the > name is the final element of a compound or hyphenated surname (Carter in > Matthew's example). I wanted to check we'd be right to construct an agent > record like this:- > > Primary part of name: Carter > Rest of name: Helen Violet Bonham > > Not > Primary part of name: Bonham Carter > Rest of name: Helen Violet > > A sanity check with the listserv would be reassuring! > > Best wishes, > > Natalie > > > > > Natalie Adams > Systems Archivist > Cambridge University Library > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Matthew Neely > *Sent:* 22 July 2020 16:24 > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Agent records in ArchivesSpace > and compound or hyphenated surnames > > > Hi Natalie, > > > > We?ve followed the UK?s NCA Rules for Names in our implementation (a > practice we have used historically at the Bodleian). For example, Violet > Bonham Carter is Carter | Lady | Helen Violet | Bonham | 1887-1969 | n?e > Asquith | Baroness Asquith of Yarnbury | Liberal political figure > in the Primary > Part of Name field in the Agent record. > > > > Best wishes, > > Matthew > > ---------------------------------- > > Matthew Neely > > Senior Archivist > > Special Collections > > Bodleian Libraries > > > > Tel: 01865 287158 > > Post: The Weston Library, Broad Street, Oxford, OX1 3BG > > Email: matthew.neely at bodleian.ox.ac.uk > > Web: http://www.bodleian.ox.ac.uk/weston > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Natalie > Adams > *Sent:* 22 July 2020 15:20 > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Agent records in ArchivesSpace and > compound or hyphenated surnames > > > > Dear all, > > > > Are there any repositories on the list using ArchivesSpace for agent > records who would be willing to share any guidance they have prepared for > users/cataloguers about creating agent records? I'm specifically interested > in conventions for entering compound and hyphenated surnames or last names. > > > > Any advice would be really helpful. > > > > Best wishes, > > > > Natalie > > > > > > Natalie Adams > > Systems Archivist > > Cambridge University Library > > > > > > Natalie Adams > > Systems Archivist > > Cambridge University Library > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Lara D. Friedman-Shedlov (she / they) Description and Access Archivist | Kautz Family YMCA Archives | www.lib.umn.edu/ymca Digital Records Archivist | Archives & Special Collections | www.lib.umn.edu/special University of Minnesota Libraries | lib.umn.edu | 612.626.7972 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corey.Schmidt at uga.edu Wed Jul 22 12:47:06 2020 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Wed, 22 Jul 2020 16:47:06 +0000 Subject: [Archivesspace_Users_Group] Update a Resource via the API In-Reply-To: References: , Message-ID: That did it. Thanks! ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kennedy, Nancy Sent: Wednesday, July 22, 2020 12:25 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Update a Resource via the API [EXTERNAL SENDER - PROCEED CAUTIOUSLY] Hi Corey - When you post your changes back, try this: client.post('/repositories/5/resources/1814', json=resource) Nancy Kennedy Smithsonian Institution ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Corey Schmidt Sent: Wednesday, July 22, 2020 11:54 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Update a Resource via the API External Email - Exercise Caution Dear all, Hello, this is Corey Schmidt, ArchivesSpace Project Manager at the University of Georgia. I hope you all are doing well and staying cool! I'm trying to update records via the API using the Update a Resource endpoint (https://archivesspace.github.io/archivesspace/api/#update-a-resource). I found Duke made a script (https://github.com/duke-libraries/archivesspace-duke-scripts/blob/master/python/asnake_update_all_resources_and_aos.py) to do this very thing and I modeled my request on that example. I also found what I think is the code for the endpoint, found in backend/app/controllers/resource.rb file, line 114 (https://github.com/archivesspace/archivesspace/blob/0c4cb2dd263bbeacdbce70567ccbb86634cde769/backend/app/controllers/resource.rb#L114). However, no matter the combinations I try for the request, I'm getting a error with the following message: "error":"Had some trouble parsing your request: unexpected token at The following is the code I'm running in python: get_resource = client.get('/repositories/5/resources/1814') print(get_resource.text) resource = json.loads(get_resource.text) resource["restrictions"] = True print(json.dumps(resource)) update_resource = client.post('/repositories/5/resources/1814', json=json.dumps(resource)) # update_resource = client.post('/repositories/5/resources/1814', params={"id": 1814, "resource": json.dumps(resource), "repo_id": 5}) # the last line produces this error: {"error":"Had some trouble parsing your request: A JSON text must at least contain two octets!"} print(update_resource, update_resource.text) I've attached the json file to this email. Any help would be greatly appreciated. Thanks! Sincerely, Corey Schmidt ArchivesSpace Project Manager University of Georgia Special Collections Libraries Email: Corey.Schmidt at uga.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From scheirw at newschool.edu Wed Jul 22 15:12:16 2020 From: scheirw at newschool.edu (Wendy Scheir) Date: Wed, 22 Jul 2020 15:12:16 -0400 Subject: [Archivesspace_Users_Group] batch publishing resources using Staff User Interface? Message-ID: Hi, Unable to find documentation about this: is it possible to create a results list of resource records and trigger all of them to publish at once? Many thanks, Wendy -------------- next part -------------- An HTML attachment was scrubbed... URL: From matthew.neely at bodleian.ox.ac.uk Thu Jul 23 04:44:31 2020 From: matthew.neely at bodleian.ox.ac.uk (Matthew Neely) Date: Thu, 23 Jul 2020 08:44:31 +0000 Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames In-Reply-To: References: , Message-ID: Hi Natalie, The full name record is placed in the Primary Sort Name field in the Agent Record and we also use the Source and Rules fields. We don't use the other fields. I personally don't think that the NCA guidance on compound surnames is particularly helpful. Best wishes, Matthew ---------------------------------- Matthew Neely Senior Archivist Special Collections Bodleian Libraries Tel: 01865 287158 Post: The Weston Library, Broad Street, Oxford, OX1 3BG Email: matthew.neely at bodleian.ox.ac.uk Web: http://www.bodleian.ox.ac.uk/weston From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Natalie Adams Sent: 22 July 2020 17:06 To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Dear Matthew and Daniel, Many thanks for replying so quickly. Matthew- could you share details of how Violet Bonham Carter's agent record is constructed in your staff interface? Daniel- the issue with the UK's NCA Rules is that the primary part of the name is the final element of a compound or hyphenated surname (Carter in Matthew's example). I wanted to check we'd be right to construct an agent record like this:- Primary part of name: Carter Rest of name: Helen Violet Bonham Not Primary part of name: Bonham Carter Rest of name: Helen Violet A sanity check with the listserv would be reassuring! Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Matthew Neely > Sent: 22 July 2020 16:24 To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Hi Natalie, We've followed the UK's NCA Rules for Names in our implementation (a practice we have used historically at the Bodleian). For example, Violet Bonham Carter is Carter | Lady | Helen Violet | Bonham | 1887-1969 | n?e Asquith | Baroness Asquith of Yarnbury | Liberal political figure in the Primary Part of Name field in the Agent record. Best wishes, Matthew ---------------------------------- Matthew Neely Senior Archivist Special Collections Bodleian Libraries Tel: 01865 287158 Post: The Weston Library, Broad Street, Oxford, OX1 3BG Email: matthew.neely at bodleian.ox.ac.uk Web: http://www.bodleian.ox.ac.uk/weston From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Natalie Adams Sent: 22 July 2020 15:20 To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Dear all, Are there any repositories on the list using ArchivesSpace for agent records who would be willing to share any guidance they have prepared for users/cataloguers about creating agent records? I'm specifically interested in conventions for entering compound and hyphenated surnames or last names. Any advice would be really helpful. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library Natalie Adams Systems Archivist Cambridge University Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From na207 at cam.ac.uk Thu Jul 23 06:28:11 2020 From: na207 at cam.ac.uk (Natalie Adams) Date: Thu, 23 Jul 2020 10:28:11 +0000 Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames In-Reply-To: References: , , Message-ID: Dear Matthew, Many thanks for getting back to me- that's really useful to know. I completely agree about the NCA Rules- definitely not intuitive for the end user. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Matthew Neely Sent: 23 July 2020 09:44 To: 'Archivesspace Users Group' Subject: Re: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Hi Natalie, The full name record is placed in the Primary Sort Name field in the Agent Record and we also use the Source and Rules fields. We don?t use the other fields. I personally don?t think that the NCA guidance on compound surnames is particularly helpful. Best wishes, Matthew ---------------------------------- Matthew Neely Senior Archivist Special Collections Bodleian Libraries Tel: 01865 287158 Post: The Weston Library, Broad Street, Oxford, OX1 3BG Email: matthew.neely at bodleian.ox.ac.uk Web: http://www.bodleian.ox.ac.uk/weston From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Natalie Adams Sent: 22 July 2020 17:06 To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Dear Matthew and Daniel, Many thanks for replying so quickly. Matthew- could you share details of how Violet Bonham Carter's agent record is constructed in your staff interface? Daniel- the issue with the UK's NCA Rules is that the primary part of the name is the final element of a compound or hyphenated surname (Carter in Matthew's example). I wanted to check we'd be right to construct an agent record like this:- Primary part of name: Carter Rest of name: Helen Violet Bonham Not Primary part of name: Bonham Carter Rest of name: Helen Violet A sanity check with the listserv would be reassuring! Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Matthew Neely > Sent: 22 July 2020 16:24 To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Hi Natalie, We?ve followed the UK?s NCA Rules for Names in our implementation (a practice we have used historically at the Bodleian). For example, Violet Bonham Carter is Carter | Lady | Helen Violet | Bonham | 1887-1969 | n?e Asquith | Baroness Asquith of Yarnbury | Liberal political figure in the Primary Part of Name field in the Agent record. Best wishes, Matthew ---------------------------------- Matthew Neely Senior Archivist Special Collections Bodleian Libraries Tel: 01865 287158 Post: The Weston Library, Broad Street, Oxford, OX1 3BG Email: matthew.neely at bodleian.ox.ac.uk Web: http://www.bodleian.ox.ac.uk/weston From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Natalie Adams Sent: 22 July 2020 15:20 To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Dear all, Are there any repositories on the list using ArchivesSpace for agent records who would be willing to share any guidance they have prepared for users/cataloguers about creating agent records? I'm specifically interested in conventions for entering compound and hyphenated surnames or last names. Any advice would be really helpful. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library Natalie Adams Systems Archivist Cambridge University Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Thu Jul 23 10:03:16 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 23 Jul 2020 14:03:16 +0000 Subject: [Archivesspace_Users_Group] Take a break with ArchivesSpace on Fridays In-Reply-To: <24DA2EB0-8EA2-42E8-9EC1-2377BAE51368@lyrasis.org> References: <4C151ED1-3A98-4217-908A-55C7BA8ED233@lyrasis.org> <939F1E31-3ECB-44AD-93A6-6634E8BFF8F7@lyrasis.org> <512F3C3D-C506-4E11-B5FB-4B9EBF4775B0@lyrasis.org> <614B918C-6F58-4D55-89F5-18680C71701B@lyrasis.org> <69AD5D49-2C12-450D-9763-D88A59297611@lyrasis.org> <24DA2EB0-8EA2-42E8-9EC1-2377BAE51368@lyrasis.org> Message-ID: Dear ArchivesSpace Users, We?ll be hosting another casual open call via zoom at 12pm ET tomorrow. With no set agenda or presentation for these calls, this forum is an opportunity to connect, chat and recharge. Use this as a time to get help or talk about ArchivesSpace (or anything else) in an informal setting or just have a beverage with other ArchivesSpace users during this stressful time. Most of us are doing our jobs under much different conditions than usual. As a browser based system you can access from anywhere, the ArchivesSpace application may offer a sense of archival normalcy as we each adjust. And with a welcoming and robust member community all over the world, ArchivesSpace can also offer camaraderie when many of us may feel isolated from our colleagues or the professional communities we interact with regularly. Thank you to everyone who joined us last week for a great chat. We hope to see you all tomorrow. When: Fridays Time: 12:00 p.m. ? 1:00 p.m. ET (9:00 a.m. ? 10:00 a.m. PT) Where: Zoom Join the call via the information below: Join Zoom Meeting https://lyrasis.zoom.us/j/281962467 Meeting ID: 281 962 467 One tap mobile +19292056099,,281962467# US (New York) +13126266799,,281962467# US (Chicago) Dial by your location +1 929 205 6099 US (New York) +1 312 626 6799 US (Chicago) +1 301 715 8592 US +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 253 215 8782 US 888 475 4499 US Toll-free 877 853 5257 US Toll-free Meeting ID: 281 962 467 Find your local number: https://lyrasis.zoom.us/u/awkFNWPxh We seek to provide a welcoming, fun, and safe community experience for everyone and adhere to Code4Lib?s CodeofConduct4Lib. The full text of the code of conduct is available at: http://bit.ly/coc4lib. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29073 bytes Desc: image001.jpg URL: From mkottman at ku.edu Thu Jul 23 14:26:18 2020 From: mkottman at ku.edu (Kottman, Miloche) Date: Thu, 23 Jul 2020 18:26:18 +0000 Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Message-ID: Since the agent template is built to be compatible with LC's Name Authority File and we heavily use the LC NAF plugin, we follow the guidelines from RDA and MARC Authority Format to fill it in. This will hopefully prevent double files in the future. Catalogers set up and/or review the agent records and they are all experienced in setting up headings as MARC records either for NACO or in our local file. We determine what the last name is based on the guidelines in RDA which usually says that hyphenated names are treated as the last name and compound names are set up based on the preference of the agents country of origin. The guidelines for most countries can be found in the IFLA names of persons document at: https://www.ifla.org/node/4953 So this means that everything to the left of the comma in a MARC authority record goes in the primary name field. If no comma (i.e. surname) then put the name in the primary name field, e.g. Margaret, $c Sister => put Margaret in primary name field. $q's go in the Fuller Form field $c's are tricky and you'll have to use judgment for where the information goes, e.g. Prefix, Suffix, Title or Qualifier. $b's go in the Number field $d's go in the Dates field --Miloche ****************************** Miloche Kottman Head of Cataloging & Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Natalie Adams Sent: Wednesday, July 22, 2020 9:20 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Dear all, Are there any repositories on the list using ArchivesSpace for agent records who would be willing to share any guidance they have prepared for users/cataloguers about creating agent records? I'm specifically interested in conventions for entering compound and hyphenated surnames or last names. Any advice would be really helpful. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library Natalie Adams Systems Archivist Cambridge University Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From Corey.Schmidt at uga.edu Fri Jul 24 16:30:39 2020 From: Corey.Schmidt at uga.edu (Corey Schmidt) Date: Fri, 24 Jul 2020 20:30:39 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Batch Export App is Live! Message-ID: Dear ArchivesSpace Users, Hello again, this is Corey Schmidt, ArchivesSpace PM at the University of Georgia. I'm excited to announce the full release of a little app we made to batch export ArchivesSpace records. This app can batch export EAD and MARCXML files, Container Labels, and PDFs. It can also run XML cleanup on EAD.xml files and upload XML or PDF files to XTF-based finding aid websites. It's made with a simple GUI, so no terminal inputs are necessary. Also, for Windows users, it comes with an easy installer. For Mac users, you can still run it with a few extra steps, but we are working on getting a Mac .app version that is just as easy to install. If you would like to check it out, here is the link to the GitHub repo: https://github.com/uga-libraries/ASpace_Batch_Export-Cleanup-Upload. To download the latest release for Windows, go to this link and click on asbatch-v100.exe to download and install: https://github.com/uga-libraries/ASpace_Batch_Export-Cleanup-Upload/releases/tag/1.0.0 I will be giving a demo/presentation of the app at the ArchivesSpace Member Forum on August 3, 1:10PM (EST) and at the Metadata and Digital Object Section at the SAA Annual Meeting on July 27, 1:00PM (EST). Special thanks to everyone on the listserv and elsewhere who helped make this possible. Thank you for you valuable and amazing insight. Sincerely, Corey Corey Schmidt ArchivesSpace Project Manager University of Georgia Special Collections Libraries Email: Corey.Schmidt at uga.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From na207 at cam.ac.uk Mon Jul 27 04:15:46 2020 From: na207 at cam.ac.uk (Natalie Adams) Date: Mon, 27 Jul 2020 08:15:46 +0000 Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames In-Reply-To: References: Message-ID: Dear Miloche, Many thanks for sharing this information, Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kottman, Miloche Sent: 23 July 2020 19:26 To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Since the agent template is built to be compatible with LC?s Name Authority File and we heavily use the LC NAF plugin, we follow the guidelines from RDA and MARC Authority Format to fill it in. This will hopefully prevent double files in the future. Catalogers set up and/or review the agent records and they are all experienced in setting up headings as MARC records either for NACO or in our local file. We determine what the last name is based on the guidelines in RDA which usually says that hyphenated names are treated as the last name and compound names are set up based on the preference of the agents country of origin. The guidelines for most countries can be found in the IFLA names of persons document at: https://www.ifla.org/node/4953 So this means that everything to the left of the comma in a MARC authority record goes in the primary name field. If no comma (i.e. surname) then put the name in the primary name field, e.g. Margaret, $c Sister => put Margaret in primary name field. $q?s go in the Fuller Form field $c?s are tricky and you?ll have to use judgment for where the information goes, e.g. Prefix, Suffix, Title or Qualifier. $b?s go in the Number field $d?s go in the Dates field --Miloche ?????????????????????????????? Miloche Kottman Head of Cataloging & Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Natalie Adams Sent: Wednesday, July 22, 2020 9:20 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Agent records in ArchivesSpace and compound or hyphenated surnames Dear all, Are there any repositories on the list using ArchivesSpace for agent records who would be willing to share any guidance they have prepared for users/cataloguers about creating agent records? I'm specifically interested in conventions for entering compound and hyphenated surnames or last names. Any advice would be really helpful. Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library Natalie Adams Systems Archivist Cambridge University Library -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdysonsm at utk.edu Mon Jul 27 09:30:41 2020 From: bdysonsm at utk.edu (Dyson-Smith, Bridger) Date: Mon, 27 Jul 2020 13:30:41 +0000 Subject: [Archivesspace_Users_Group] Odd permissions problem with resources Message-ID: Hi all - We're experiencing a strange issue with at least two of our resources: they are available in the staff UI for some admin-level users (me), but not others. They're unavailable in the public UI for everyone (except very briefly during a reindex - once the reindex is finished, they're not longer available in the public UI). Any suggestions for where to start trying to determine a solution? Both resources are published. Thanks in advance for your time. And apologies if you're seeing this twice - I had emailed the Google Group last week. Best, Bridger -- University of Tennessee Libraries Digital Initiatives Get Outlook for Android -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Mon Jul 27 09:48:53 2020 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 27 Jul 2020 13:48:53 +0000 Subject: [Archivesspace_Users_Group] Odd permissions problem with resources In-Reply-To: References: Message-ID: Bridger, Regarding the first issue, are those two resources "suppressed" by any chance? A suppressed record cannot be seen in the staff interface by most users unless they also have the ability to view suppressed records. Since you mentioned that you could see it as an admin user, that's my first guess. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dyson-Smith, Bridger Sent: Monday, July 27, 2020 9:30 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Odd permissions problem with resources Hi all - We're experiencing a strange issue with at least two of our resources: they are available in the staff UI for some admin-level users (me), but not others. They're unavailable in the public UI for everyone (except very briefly during a reindex - once the reindex is finished, they're not longer available in the public UI). Any suggestions for where to start trying to determine a solution? Both resources are published. Thanks in advance for your time. And apologies if you're seeing this twice - I had emailed the Google Group last week. Best, Bridger -- University of Tennessee Libraries Digital Initiatives Get Outlook for Android -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at jhu.edu Mon Jul 27 10:54:57 2020 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Mon, 27 Jul 2020 10:54:57 -0400 Subject: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed" Message-ID: <3c7d5a3e-c840-dac9-886f-40c769ff304e@jhu.edu> All, I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a Vagrant box before upgrading for real. I was having problems running the /scripts/database-setup.sh migration script via my Vagrant file, and, as with Vagrant, Ansible, etc. found myself spending lots of time troubleshooting the script I've written to install the software, when I could have just installed the software! So now I have my Vagrant box up and running, I SSH in and run /scripts/database-setup.sh without any problem. BUT now that I've kicked this can down the road, the next issue is: When I go to boot up ASpace, I end up with the following error: INFO: DEBUG: resetting rack response due exception E, [2020-07-25T15:57:06.898049 #38438] ERROR -- : Thread-2004: Connection to backend failed ( I read that if the schema in the DB does not match the schema in the ASpace codebase, the backend will not start. And yet, the setup-database.sh migration script ran without error, so at this point the schemas should be in sync. Any advice on how to get the backend up and running greatly appreciated, Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lora.Woodford at lyrasis.org Mon Jul 27 11:22:22 2020 From: Lora.Woodford at lyrasis.org (Lora Woodford) Date: Mon, 27 Jul 2020 15:22:22 +0000 Subject: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed" In-Reply-To: <3c7d5a3e-c840-dac9-886f-40c769ff304e@jhu.edu> References: <3c7d5a3e-c840-dac9-886f-40c769ff304e@jhu.edu> Message-ID: <50AE0EE7-34D7-4FD5-B476-6B39CCBA739C@lyrasis.org> Hiya Mark! So, if the issue were a db schema mismatch, you?d likely get an error message explaining that. Something like ?Schema Info Mismatch. Expected #{expected schema version}, received #{your schema version} for ASPACE version #{version you?re trying to run}.? What version of mysql (if mysql?) are you using? I?ve seen similar issues with folks attempting to run against MySql 8. Can you try 5.7? Lora From: on behalf of Mark Cyzyk Reply-To: "mcyzyk at jhu.edu" , Archivesspace Users Group Date: Monday, July 27, 2020 at 10:55 AM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed" All, I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a Vagrant box before upgrading for real. I was having problems running the /scripts/database-setup.sh migration script via my Vagrant file, and, as with Vagrant, Ansible, etc. found myself spending lots of time troubleshooting the script I've written to install the software, when I could have just installed the software! So now I have my Vagrant box up and running, I SSH in and run /scripts/database-setup.sh without any problem. BUT now that I've kicked this can down the road, the next issue is: When I go to boot up ASpace, I end up with the following error: INFO: DEBUG: resetting rack response due exception E, [2020-07-25T15:57:06.898049 #38438] ERROR -- : Thread-2004: Connection to backend failed (> I read that if the schema in the DB does not match the schema in the ASpace codebase, the backend will not start. And yet, the setup-database.sh migration script ran without error, so at this point the schemas should be in sync. Any advice on how to get the backend up and running greatly appreciated, Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at jhu.edu Mon Jul 27 11:35:49 2020 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Mon, 27 Jul 2020 11:35:49 -0400 Subject: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed" In-Reply-To: <50AE0EE7-34D7-4FD5-B476-6B39CCBA739C@lyrasis.org> References: <3c7d5a3e-c840-dac9-886f-40c769ff304e@jhu.edu> <50AE0EE7-34D7-4FD5-B476-6B39CCBA739C@lyrasis.org> Message-ID: <776606c3-5eba-eb6f-c64c-ae67fa3c3d9b@jhu.edu> Hi Lora! Sorry, I should have mentioned this, I'm running against MariaDB: MariaDB from Ubuntu 20.04 repository, version 10.3 (We're running against MariaDB here in Prod and Dev on CentOS 7.) Thanks! Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/27/20 11:22 AM, Lora Woodford wrote: > > Hiya Mark! > > So, if the issue were a db schema mismatch, you?d likely get an error > message explaining that.? Something like ?Schema Info Mismatch. > Expected #{expected schema version}, received #{your schema version} > for ASPACE version #{version you?re trying to run}.? > > > What version of mysql (if mysql?) are you using?? I?ve seen similar > issues with folks attempting to run against MySql 8. Can you try 5.7? > > Lora > > *From: * on > behalf of Mark Cyzyk > *Reply-To: *"mcyzyk at jhu.edu" , Archivesspace Users > Group > *Date: *Monday, July 27, 2020 at 10:55 AM > *To: *"archivesspace_users_group at lyralists.lyrasis.org" > > *Subject: *[Archivesspace_Users_Group] ASpace upgrade: "Connection to > backend failed" > > > All, > > I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a Vagrant > box before upgrading for real. > > I was having problems running the /scripts/database-setup.sh migration > script via my Vagrant file, and, as with Vagrant, Ansible, etc. found > myself spending lots of time troubleshooting the script I've written > to install the software, when I could have just installed the software! > > So now I have my Vagrant box up and running, I SSH in and run > /scripts/database-setup.sh without any problem. > > BUT now that I've kicked this can down the road, the next issue is: > > When I go to boot up ASpace, I end up with the following error: > > INFO: DEBUG: resetting rack response due exception > E, [2020-07-25T15:57:06.898049 #38438] ERROR -- : Thread-2004: > Connection to backend failed ( HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd" > > > > > I read that if the schema in the DB does not match the schema in the > ASpace codebase, the backend will not start. > > And yet, the setup-database.sh migration script ran without error, so > at this point the schemas should be in sync. > > Any advice on how to get the backend up and running greatly appreciated, > > Mark > > -- > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bdysonsm at utk.edu Mon Jul 27 12:25:41 2020 From: bdysonsm at utk.edu (Dyson-Smith, Bridger) Date: Mon, 27 Jul 2020 16:25:41 +0000 Subject: [Archivesspace_Users_Group] Odd permissions problem with resources In-Reply-To: References: Message-ID: Mark - Thanks for the response! That was a good thought, but unfortunately I checked and the resources are not suppressed. I really appreciate the suggestion. Best, Bridger On Mon, 2020-07-27 at 13:48 +0000, Custer, Mark wrote: > Bridger, > > Regarding the first issue, are those two resources "suppressed" by > any chance? A suppressed record cannot be seen in the staff > interface by most users unless they also have the ability to view > suppressed records. Since you mentioned that you could see it as an > admin user, that's my first guess. > > Mark > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Dyson-Smith, Bridger > Sent: Monday, July 27, 2020 9:30 AM > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] Odd permissions problem with > resources > > Hi all - > > We're experiencing a strange issue with at least two of our > resources: they are available in the staff UI for some admin-level > users (me), but not others. They're unavailable in the public UI > for everyone (except very briefly during a reindex - once the reindex > is finished, they're not longer available in the public UI). > > Any suggestions for where to start trying to determine a solution? > Both resources are published. > > Thanks in advance for your time. And apologies if you're seeing this > twice - I had emailed the Google Group last week. > > Best, > Bridger > -- > University of Tennessee Libraries > Digital Initiatives > > > > Get Outlook for Android > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From KennedyN at si.edu Mon Jul 27 12:53:40 2020 From: KennedyN at si.edu (Kennedy, Nancy) Date: Mon, 27 Jul 2020 16:53:40 +0000 Subject: [Archivesspace_Users_Group] Odd permissions problem with resources In-Reply-To: References: , Message-ID: Hi Bridger - Just wanted to say that when we were on 2.5, we had an issue like this pop up. For the same search, we would see different results for some users. Admin and repo managers were able to search for the specific record, but not others. This was in the staff interface (we don't use the pui). We were working on moving up to 2.6 at the time, and our problem did go away after moving into 2.6. Here are details from my notes, in case it helps you -- That error message points to an issue that was resolved for v2.6.0. So, you may not be on v2.6.0 OR your plugin that overrides the listing view is not up to date with v2.6.0: I, [2019-09-19T11:41:48.479388 #921] INFO -- : Rendered /opt/archivesspace/plugins/local/frontend/views/search/_listing.html.erb (1844.8ms) I'd recommend a) be on v2.6.0 (if not) and b) update plugins/local/frontend/views/search/_listing.html.erb to be up to date with v2.6.0 with your edits. Nancy Kennedy Smithsonian Institution kennedyn at si.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dyson-Smith, Bridger Sent: Monday, July 27, 2020 12:25 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Odd permissions problem with resources External Email - Exercise Caution Mark - Thanks for the response! That was a good thought, but unfortunately I checked and the resources are not suppressed. I really appreciate the suggestion. Best, Bridger On Mon, 2020-07-27 at 13:48 +0000, Custer, Mark wrote: > Bridger, > > Regarding the first issue, are those two resources "suppressed" by > any chance? A suppressed record cannot be seen in the staff > interface by most users unless they also have the ability to view > suppressed records. Since you mentioned that you could see it as an > admin user, that's my first guess. > > Mark > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Dyson-Smith, Bridger > Sent: Monday, July 27, 2020 9:30 AM > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] Odd permissions problem with > resources > > Hi all - > > We're experiencing a strange issue with at least two of our > resources: they are available in the staff UI for some admin-level > users (me), but not others. They're unavailable in the public UI > for everyone (except very briefly during a reindex - once the reindex > is finished, they're not longer available in the public UI). > > Any suggestions for where to start trying to determine a solution? > Both resources are published. > > Thanks in advance for your time. And apologies if you're seeing this > twice - I had emailed the Google Group last week. > > Best, > Bridger > -- > University of Tennessee Libraries > Digital Initiatives > > > > Get Outlook for Android > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7CKennedyN%40si.edu%7Cd1cd5b8bcba0455b5a6408d83249b87c%7C989b5e2a14e44efe93b78cdd5fc5d11c%7C0%7C0%7C637314639503226572&sdata=M7m7klG4edzOwumsObFJCiol15IOc8FxkvuQA3%2Bk5EU%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7CKennedyN%40si.edu%7Cd1cd5b8bcba0455b5a6408d83249b87c%7C989b5e2a14e44efe93b78cdd5fc5d11c%7C0%7C0%7C637314639503236569&sdata=WZHRNz0OIga2D%2BggMKTklBUaC%2F4urwCOeY10tSxs1Fc%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Jul 27 12:54:09 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 27 Jul 2020 16:54:09 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 6th Annual Member Forum is one week away! Message-ID: <233FB9AB-6430-4E11-894B-8FD159522436@lyrasis.org> [A picture containing woman, holding, standing Description automatically generated] There is still time to register for next week?s 6th Annual ArchivesSpace Member Forum! Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. Unlike previous years, ArchivesSpace will be holding its sixth Annual Member Forum virtually, on August 3-7, 2020, from 12pm-3pm ET each day via Zoom. This free event is a chance for ArchivesSpace members to come together to highlight the work they are doing in ArchivesSpace, show off new plugins or tools they?ve developed, and attend workshops and trainings on a variety of topics. As with our previous Annual Member Forums, it is being held in conjunction with the Society of American Archivists annual meeting, but it is not part of SAA and does not require registration for the SAA Annual Meeting. When: Presentations and breakout discussions will be held on August 3-4, 2020 from 12pm-3pm ET, and all individuals from ArchivesSpace member institutions are welcome to attend some or all of the sessions on these days. Small workshops covering specific elements of the ArchivesSpace application will be offered August 5-7, 2020 from 12pm-3pm ET. These workshops will be limited in capacity. Registrations for each day are separate and you must register for individually for all days you are interested in attending. Where: All online via Zoom, with opportunities to join via computer or phone. Who Can Attend: The ArchivesSpace Member Forum is open to individuals from ArchivesSpace member institutions only. To register, you must use an institutional email address associated with an ArchivesSpace member institution. Registrations using personal email addresses and addresses associated with non-member institutions will not be accepted. This means that events with limited capacity may fill before you are able to correct your registration. Online registration: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1422819333/ArchivesSpace+Member+Forum+2020 Registrations for each day of the Forum are separate. You will need to register for each day you are interested in attending to guarantee your spot. Registration for each activity is linked above the session in the agenda. Workshop attendance is limited. Discussion sessions on Tuesday, August 4, will occur in two separate zoom rooms. You must register for both Zoom Room A and B if you want to attend discussions in both rooms. The number of registrations available for the workshops on August 5-7 is limited. The total number of attendees is noted next to the registration. To give as many people as possible a chance to attend, you may register for only one workshop. We will be recording the sessions on August 3, 2020 but will not be recording discussions or workshops. We encourage you to dip in and out of the live programs on August 3-4, 2020 as much as you can. Please feel free to contact ArchivesSpace Community Engagement Coordinator Jessica Crouch (jessica.crouch at lyrasis.org) with questions. We look forward to seeing many of you there! Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 66179 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 8536 bytes Desc: image002.jpg URL: From bdysonsm at utk.edu Mon Jul 27 15:47:51 2020 From: bdysonsm at utk.edu (Dyson-Smith, Bridger) Date: Mon, 27 Jul 2020 19:47:51 +0000 Subject: [Archivesspace_Users_Group] Odd permissions problem with resources In-Reply-To: References: , , Message-ID: Hi Nancy, Thanks for the response. I'll take a closer look at our logs and see if we're experiencing those errors. I don't know if an upgrade to v2.6 is in the immediate cards for us, but we'll have to consider it if we can't fix this problem. Best wishes, Bridger Get Outlook for Android ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kennedy, Nancy Sent: Monday, July 27, 2020 12:53:40 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Odd permissions problem with resources [External Email] Hi Bridger - Just wanted to say that when we were on 2.5, we had an issue like this pop up. For the same search, we would see different results for some users. Admin and repo managers were able to search for the specific record, but not others. This was in the staff interface (we don't use the pui). We were working on moving up to 2.6 at the time, and our problem did go away after moving into 2.6. Here are details from my notes, in case it helps you -- That error message points to an issue that was resolved for v2.6.0. So, you may not be on v2.6.0 OR your plugin that overrides the listing view is not up to date with v2.6.0: I, [2019-09-19T11:41:48.479388 #921] INFO -- : Rendered /opt/archivesspace/plugins/local/frontend/views/search/_listing.html.erb (1844.8ms) I'd recommend a) be on v2.6.0 (if not) and b) update plugins/local/frontend/views/search/_listing.html.erb to be up to date with v2.6.0 with your edits. Nancy Kennedy Smithsonian Institution kennedyn at si.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dyson-Smith, Bridger Sent: Monday, July 27, 2020 12:25 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Odd permissions problem with resources External Email - Exercise Caution Mark - Thanks for the response! That was a good thought, but unfortunately I checked and the resources are not suppressed. I really appreciate the suggestion. Best, Bridger On Mon, 2020-07-27 at 13:48 +0000, Custer, Mark wrote: > Bridger, > > Regarding the first issue, are those two resources "suppressed" by > any chance? A suppressed record cannot be seen in the staff > interface by most users unless they also have the ability to view > suppressed records. Since you mentioned that you could see it as an > admin user, that's my first guess. > > Mark > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Dyson-Smith, Bridger > Sent: Monday, July 27, 2020 9:30 AM > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] Odd permissions problem with > resources > > Hi all - > > We're experiencing a strange issue with at least two of our > resources: they are available in the staff UI for some admin-level > users (me), but not others. They're unavailable in the public UI > for everyone (except very briefly during a reindex - once the reindex > is finished, they're not longer available in the public UI). > > Any suggestions for where to start trying to determine a solution? > Both resources are published. > > Thanks in advance for your time. And apologies if you're seeing this > twice - I had emailed the Google Group last week. > > Best, > Bridger > -- > University of Tennessee Libraries > Digital Initiatives > > > > Get Outlook for Android > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7CKennedyN%40si.edu%7Cd1cd5b8bcba0455b5a6408d83249b87c%7C989b5e2a14e44efe93b78cdd5fc5d11c%7C0%7C0%7C637314639503226572&sdata=M7m7klG4edzOwumsObFJCiol15IOc8FxkvuQA3%2Bk5EU%3D&reserved=0 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7CKennedyN%40si.edu%7Cd1cd5b8bcba0455b5a6408d83249b87c%7C989b5e2a14e44efe93b78cdd5fc5d11c%7C0%7C0%7C637314639503236569&sdata=WZHRNz0OIga2D%2BggMKTklBUaC%2F4urwCOeY10tSxs1Fc%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at jhu.edu Tue Jul 28 11:18:44 2020 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Tue, 28 Jul 2020 11:18:44 -0400 Subject: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed" In-Reply-To: <776606c3-5eba-eb6f-c64c-ae67fa3c3d9b@jhu.edu> References: <3c7d5a3e-c840-dac9-886f-40c769ff304e@jhu.edu> <50AE0EE7-34D7-4FD5-B476-6B39CCBA739C@lyrasis.org> <776606c3-5eba-eb6f-c64c-ae67fa3c3d9b@jhu.edu> Message-ID: Update on this: Upgraded to latest MySQL Connector (8.0.21).??? Still no joy, Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/27/20 11:35 AM, Mark Cyzyk wrote: > > Hi Lora! > > Sorry, I should have mentioned this, I'm running against MariaDB: > > MariaDB from Ubuntu 20.04 repository, version 10.3 > > (We're running against MariaDB here in Prod and Dev on CentOS 7.) > > Thanks! > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. > On 7/27/20 11:22 AM, Lora Woodford wrote: >> >> Hiya Mark! >> >> So, if the issue were a db schema mismatch, you?d likely get an error >> message explaining that.? Something like ?Schema Info Mismatch. >> Expected #{expected schema version}, received #{your schema version} >> for ASPACE version #{version you?re trying to run}.? >> >> >> What version of mysql (if mysql?) are you using?? I?ve seen similar >> issues with folks attempting to run against MySql 8.? Can you try 5.7? >> >> Lora >> >> *From: * on >> behalf of Mark Cyzyk >> *Reply-To: *"mcyzyk at jhu.edu" , Archivesspace Users >> Group >> *Date: *Monday, July 27, 2020 at 10:55 AM >> *To: *"archivesspace_users_group at lyralists.lyrasis.org" >> >> *Subject: *[Archivesspace_Users_Group] ASpace upgrade: "Connection to >> backend failed" >> >> >> All, >> >> I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a >> Vagrant box before upgrading for real. >> >> I was having problems running the /scripts/database-setup.sh >> migration script via my Vagrant file, and, as with Vagrant, Ansible, >> etc. found myself spending lots of time troubleshooting the script >> I've written to install the software, when I could have just >> installed the software! >> >> So now I have my Vagrant box up and running, I SSH in and run >> /scripts/database-setup.sh without any problem. >> >> BUT now that I've kicked this can down the road, the next issue is: >> >> When I go to boot up ASpace, I end up with the following error: >> >> INFO: DEBUG: resetting rack response due exception >> E, [2020-07-25T15:57:06.898049 #38438] ERROR -- : Thread-2004: >> Connection to backend failed (> HTML 4.01 Transitional//EN" >> "http://www.w3.org/TR/html4/loose.dtd" >> > >> >> >> I read that if the schema in the DB does not match the schema in the >> ASpace codebase, the backend will not start. >> >> And yet, the setup-database.sh migration script ran without error, so >> at this point the schemas should be in sync. >> >> Any advice on how to get the backend up and running greatly appreciated, >> >> Mark >> >> -- >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> Mark Cyzyk, M.A., M.L.S. >> Library Applications Group >> The Sheridan Libraries >> The Johns Hopkins University >> mcyzyk at jhu.edu >> Verba volant, scripta manent. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Tue Jul 28 11:24:12 2020 From: blake.carver at lyrasis.org (Blake Carver) Date: Tue, 28 Jul 2020 15:24:12 +0000 Subject: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed" In-Reply-To: References: <3c7d5a3e-c840-dac9-886f-40c769ff304e@jhu.edu> <50AE0EE7-34D7-4FD5-B476-6B39CCBA739C@lyrasis.org> <776606c3-5eba-eb6f-c64c-ae67fa3c3d9b@jhu.edu>, Message-ID: "Connection to backend failed " can mean a bunch of things. What's around that error, are there any other details? Those usually show up before that line. There's should be something more specific in the logs about that error. Could be as simple as user/pass isn't correct. Can you connect to mysql from the command line successfully? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mark Cyzyk Sent: Tuesday, July 28, 2020 11:18 AM To: Lora Woodford ; Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed" Update on this: Upgraded to latest MySQL Connector (8.0.21). Still no joy, Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/27/20 11:35 AM, Mark Cyzyk wrote: Hi Lora! Sorry, I should have mentioned this, I'm running against MariaDB: MariaDB from Ubuntu 20.04 repository, version 10.3 (We're running against MariaDB here in Prod and Dev on CentOS 7.) Thanks! Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/27/20 11:22 AM, Lora Woodford wrote: Hiya Mark! So, if the issue were a db schema mismatch, you?d likely get an error message explaining that. Something like ?Schema Info Mismatch. Expected #{expected schema version}, received #{your schema version} for ASPACE version #{version you?re trying to run}.? What version of mysql (if mysql?) are you using? I?ve seen similar issues with folks attempting to run against MySql 8. Can you try 5.7? Lora From: on behalf of Mark Cyzyk Reply-To: "mcyzyk at jhu.edu" , Archivesspace Users Group Date: Monday, July 27, 2020 at 10:55 AM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed" All, I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a Vagrant box before upgrading for real. I was having problems running the /scripts/database-setup.sh migration script via my Vagrant file, and, as with Vagrant, Ansible, etc. found myself spending lots of time troubleshooting the script I've written to install the software, when I could have just installed the software! So now I have my Vagrant box up and running, I SSH in and run /scripts/database-setup.sh without any problem. BUT now that I've kicked this can down the road, the next issue is: When I go to boot up ASpace, I end up with the following error: INFO: DEBUG: resetting rack response due exception E, [2020-07-25T15:57:06.898049 #38438] ERROR -- : Thread-2004: Connection to backend failed (> I read that if the schema in the DB does not match the schema in the ASpace codebase, the backend will not start. And yet, the setup-database.sh migration script ran without error, so at this point the schemas should be in sync. Any advice on how to get the backend up and running greatly appreciated, Mark -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ccauste1 at swarthmore.edu Tue Jul 28 12:13:46 2020 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Tue, 28 Jul 2020 12:13:46 -0400 Subject: [Archivesspace_Users_Group] ArchivesSpace Export Service - filenaming for EAD Message-ID: Hi folks, We're testing out Hudson Molonglo's ArchivesSpace Export Service and would like the EAD-XML filenames exported through the service to utilize a more meaningful filenaming convention (eadid and/or collection identifier) versus the ASpace database number. Has anyone done this, or have advice as to what we might try? Thanks! Celia -- Celia Caust-Ellenbogen (she/her/hers ) Friends Historical Library of Swarthmore College ccauste1 at swarthmore.edu Please be aware that Swarthmore College is currently closed to visitors and all but essential staff due to coronavirus precautions. I am working from home and email is the best way to reach me. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at jhu.edu Wed Jul 29 17:38:55 2020 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Wed, 29 Jul 2020 17:38:55 -0400 Subject: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed" In-Reply-To: References: <3c7d5a3e-c840-dac9-886f-40c769ff304e@jhu.edu> <50AE0EE7-34D7-4FD5-B476-6B39CCBA739C@lyrasis.org> <776606c3-5eba-eb6f-c64c-ae67fa3c3d9b@jhu.edu> Message-ID: More: The nice thing about Vagrant is that you can pretty quickly run things on a totally different OS.? So this I just did.? I'm now on CentOS-7 (which is what we are running in Dev and Prod anyway). Again, no issues whatsoever in running the setup-database script and, presumably, getting schemas in sync. But I boot up archivesspace.sh, and this: > INFO -- : Thread-2000: All tables checked and confirmed set to UTF-8.? > Nice job! > ======================================================================== > ????? A trace file has been written to the following location: > /usr/share/archivesspace/data/tmp/aspace_diagnostic_1596058212.txt > > ????? This file contains information that will assist developers in > diagnosing > ????? problems with your ArchivesSpace installation.? Please review > the file's > ????? contents for sensitive information (such as passwords) that you > might not > ????? want to share. > ======================================================================== > Jul 29, 2020 9:30:12 PM > org.eclipse.jetty.server.handler.ContextHandler$Context log > INFO: An exception happened during JRuby-Rack startup > undefined method `[]' for nil:NilClass > --- System > jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 OpenJDK 64-Bit Server VM > 25.252-b09 on 1.8.0_252-b09 +jit [linux-x86_64] > Time: 2020-07-29 21:30:12 UTC > Server: jetty/8.1.5.v20120716 > jruby.home: uri:classloader://META-INF/jruby.home > > --- Context Init Parameters: > jruby.compat.version = 1.9 > jruby.max.runtimes = 1 > jruby.min.runtimes = 1 > public.root = / > rack.env = production > > --- Backtrace > NoMethodError: undefined method `[]' for nil:NilClass > ?????? block in prepare_schemas at > uri:classloader:/record_inheritance.rb:31 > ?????????????????????????? each at org/jruby/RubyArray.java:1735 > ?????? block in prepare_schemas at > uri:classloader:/record_inheritance.rb:16 > ?????????????????????????? each at org/jruby/RubyHash.java:1350 > ??????????????? prepare_schemas at > uri:classloader:/record_inheritance.rb:15 > ? block in ArchivesSpaceService at > /usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:108 > ????????????????????? configure at > /usr/share/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411 > ?? at > /usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:79 > ????????????????????????
at > /usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:39 > ??????????????????????? require at org/jruby/RubyKernel.java:956 > ???????????????????????? (root) at > uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1 > ?????????????? block in require at > uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55 > ????????????????? instance_eval at org/jruby/RubyBasicObject.java:1691 > ???????????????????????? (root) at > /usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4 > ????????????????????????
at > uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55 > ?????????????????? start_server at launcher/launcher.rb:92 > ?????????????????????????? main at launcher/launcher.rb:157 > ????????????????????????
at launcher/launcher.rb:261 This is on a fully updated CentOS-7 box.? Something just after the UTF-8 check. Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/28/20 11:18 AM, Mark Cyzyk wrote: > > Update on this: > > Upgraded to latest MySQL Connector (8.0.21).??? Still no joy, > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. > On 7/27/20 11:35 AM, Mark Cyzyk wrote: >> >> Hi Lora! >> >> Sorry, I should have mentioned this, I'm running against MariaDB: >> >> MariaDB from Ubuntu 20.04 repository, version 10.3 >> >> (We're running against MariaDB here in Prod and Dev on CentOS 7.) >> >> Thanks! >> >> Mark >> >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> Mark Cyzyk, M.A., M.L.S. >> Library Applications Group >> The Sheridan Libraries >> The Johns Hopkins University >> mcyzyk at jhu.edu >> >> Verba volant, scripta manent. >> On 7/27/20 11:22 AM, Lora Woodford wrote: >>> >>> Hiya Mark! >>> >>> So, if the issue were a db schema mismatch, you?d likely get an >>> error message explaining that.? Something like ?Schema Info >>> Mismatch. Expected #{expected schema version}, received #{your >>> schema version} for ASPACE version #{version you?re trying to run}.? >>> >>> >>> What version of mysql (if mysql?) are you using?? I?ve seen similar >>> issues with folks attempting to run against MySql 8.? Can you try 5.7? >>> >>> Lora >>> >>> *From: * on >>> behalf of Mark Cyzyk >>> *Reply-To: *"mcyzyk at jhu.edu" , Archivesspace Users >>> Group >>> *Date: *Monday, July 27, 2020 at 10:55 AM >>> *To: *"archivesspace_users_group at lyralists.lyrasis.org" >>> >>> *Subject: *[Archivesspace_Users_Group] ASpace upgrade: "Connection >>> to backend failed" >>> >>> >>> All, >>> >>> I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a >>> Vagrant box before upgrading for real. >>> >>> I was having problems running the /scripts/database-setup.sh >>> migration script via my Vagrant file, and, as with Vagrant, Ansible, >>> etc. found myself spending lots of time troubleshooting the script >>> I've written to install the software, when I could have just >>> installed the software! >>> >>> So now I have my Vagrant box up and running, I SSH in and run >>> /scripts/database-setup.sh without any problem. >>> >>> BUT now that I've kicked this can down the road, the next issue is: >>> >>> When I go to boot up ASpace, I end up with the following error: >>> >>> INFO: DEBUG: resetting rack response due exception >>> E, [2020-07-25T15:57:06.898049 #38438] ERROR -- : Thread-2004: >>> Connection to backend failed (>> HTML 4.01 Transitional//EN" >>> "http://www.w3.org/TR/html4/loose.dtd" >>> > >>> >>> >>> I read that if the schema in the DB does not match the schema in the >>> ASpace codebase, the backend will not start. >>> >>> And yet, the setup-database.sh migration script ran without error, >>> so at this point the schemas should be in sync. >>> >>> Any advice on how to get the backend up and running greatly appreciated, >>> >>> Mark >>> >>> -- >>> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >>> Mark Cyzyk, M.A., M.L.S. >>> Library Applications Group >>> The Sheridan Libraries >>> The Johns Hopkins University >>> mcyzyk at jhu.edu >>> Verba volant, scripta manent. >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcyzyk at jhu.edu Thu Jul 30 09:49:24 2020 From: mcyzyk at jhu.edu (Mark Cyzyk) Date: Thu, 30 Jul 2020 09:49:24 -0400 Subject: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed" In-Reply-To: References: <3c7d5a3e-c840-dac9-886f-40c769ff304e@jhu.edu> <50AE0EE7-34D7-4FD5-B476-6B39CCBA739C@lyrasis.org> <776606c3-5eba-eb6f-c64c-ae67fa3c3d9b@jhu.edu> Message-ID: Even more: Just ran through the whole thing, but this time with fresh MariaDB 10.5 direct from their repository. Same error. :( Mark <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcyzyk at jhu.edu Verba volant, scripta manent. On 7/29/20 5:38 PM, Mark Cyzyk wrote: > > More: > > The nice thing about Vagrant is that you can pretty quickly run things > on a totally different OS.? So this I just did.? I'm now on CentOS-7 > (which is what we are running in Dev and Prod anyway). > > Again, no issues whatsoever in running the setup-database script and, > presumably, getting schemas in sync. > > But I boot up archivesspace.sh, and this: > >> INFO -- : Thread-2000: All tables checked and confirmed set to >> UTF-8.? Nice job! >> ======================================================================== >> ????? A trace file has been written to the following location: >> /usr/share/archivesspace/data/tmp/aspace_diagnostic_1596058212.txt >> >> ????? This file contains information that will assist developers in >> diagnosing >> ????? problems with your ArchivesSpace installation.? Please review >> the file's >> ????? contents for sensitive information (such as passwords) that you >> might not >> ????? want to share. >> ======================================================================== >> Jul 29, 2020 9:30:12 PM >> org.eclipse.jetty.server.handler.ContextHandler$Context log >> INFO: An exception happened during JRuby-Rack startup >> undefined method `[]' for nil:NilClass >> --- System >> jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 OpenJDK 64-Bit Server VM >> 25.252-b09 on 1.8.0_252-b09 +jit [linux-x86_64] >> Time: 2020-07-29 21:30:12 UTC >> Server: jetty/8.1.5.v20120716 >> jruby.home: uri:classloader://META-INF/jruby.home >> >> --- Context Init Parameters: >> jruby.compat.version = 1.9 >> jruby.max.runtimes = 1 >> jruby.min.runtimes = 1 >> public.root = / >> rack.env = production >> >> --- Backtrace >> NoMethodError: undefined method `[]' for nil:NilClass >> ?????? block in prepare_schemas at >> uri:classloader:/record_inheritance.rb:31 >> ?????????????????????????? each at org/jruby/RubyArray.java:1735 >> ?????? block in prepare_schemas at >> uri:classloader:/record_inheritance.rb:16 >> ?????????????????????????? each at org/jruby/RubyHash.java:1350 >> ??????????????? prepare_schemas at >> uri:classloader:/record_inheritance.rb:15 >> ? block in ArchivesSpaceService at >> /usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:108 >> ????????????????????? configure at >> /usr/share/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411 >> ?? at >> /usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:79 >> ????????????????????????
at >> /usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:39 >> ??????????????????????? require at org/jruby/RubyKernel.java:956 >> ???????????????????????? (root) at >> uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1 >> ?????????????? block in require at >> uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55 >> ????????????????? instance_eval at org/jruby/RubyBasicObject.java:1691 >> ???????????????????????? (root) at >> /usr/share/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4 >> ????????????????????????
at >> uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55 >> ?????????????????? start_server at launcher/launcher.rb:92 >> ?????????????????????????? main at launcher/launcher.rb:157 >> ????????????????????????
at launcher/launcher.rb:261 > > This is on a fully updated CentOS-7 box.? Something just after the > UTF-8 check. > > Mark > > <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> > Mark Cyzyk, M.A., M.L.S. > Library Applications Group > The Sheridan Libraries > The Johns Hopkins University > mcyzyk at jhu.edu > > Verba volant, scripta manent. > On 7/28/20 11:18 AM, Mark Cyzyk wrote: >> >> Update on this: >> >> Upgraded to latest MySQL Connector (8.0.21).??? Still no joy, >> >> Mark >> >> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >> Mark Cyzyk, M.A., M.L.S. >> Library Applications Group >> The Sheridan Libraries >> The Johns Hopkins University >> mcyzyk at jhu.edu >> >> Verba volant, scripta manent. >> On 7/27/20 11:35 AM, Mark Cyzyk wrote: >>> >>> Hi Lora! >>> >>> Sorry, I should have mentioned this, I'm running against MariaDB: >>> >>> MariaDB from Ubuntu 20.04 repository, version 10.3 >>> >>> (We're running against MariaDB here in Prod and Dev on CentOS 7.) >>> >>> Thanks! >>> >>> Mark >>> >>> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >>> Mark Cyzyk, M.A., M.L.S. >>> Library Applications Group >>> The Sheridan Libraries >>> The Johns Hopkins University >>> mcyzyk at jhu.edu >>> >>> Verba volant, scripta manent. >>> On 7/27/20 11:22 AM, Lora Woodford wrote: >>>> >>>> Hiya Mark! >>>> >>>> So, if the issue were a db schema mismatch, you?d likely get an >>>> error message explaining that.? Something like ?Schema Info >>>> Mismatch. Expected #{expected schema version}, received #{your >>>> schema version} for ASPACE version #{version you?re trying to run}.? >>>> >>>> >>>> What version of mysql (if mysql?) are you using?? I?ve seen similar >>>> issues with folks attempting to run against MySql 8.? Can you try 5.7? >>>> >>>> Lora >>>> >>>> *From: * >>>> on behalf of Mark Cyzyk >>>> *Reply-To: *"mcyzyk at jhu.edu" , Archivesspace Users >>>> Group >>>> *Date: *Monday, July 27, 2020 at 10:55 AM >>>> *To: *"archivesspace_users_group at lyralists.lyrasis.org" >>>> >>>> *Subject: *[Archivesspace_Users_Group] ASpace upgrade: "Connection >>>> to backend failed" >>>> >>>> >>>> All, >>>> >>>> I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a >>>> Vagrant box before upgrading for real. >>>> >>>> I was having problems running the /scripts/database-setup.sh >>>> migration script via my Vagrant file, and, as with Vagrant, >>>> Ansible, etc. found myself spending lots of time troubleshooting >>>> the script I've written to install the software, when I could have >>>> just installed the software! >>>> >>>> So now I have my Vagrant box up and running, I SSH in and run >>>> /scripts/database-setup.sh without any problem. >>>> >>>> BUT now that I've kicked this can down the road, the next issue is: >>>> >>>> When I go to boot up ASpace, I end up with the following error: >>>> >>>> INFO: DEBUG: resetting rack response due exception >>>> E, [2020-07-25T15:57:06.898049 #38438] ERROR -- : Thread-2004: >>>> Connection to backend failed (>>> "-//W3C//DTD HTML 4.01 Transitional//EN" >>>> "http://www.w3.org/TR/html4/loose.dtd" >>>> > >>>> >>>> >>>> I read that if the schema in the DB does not match the schema in >>>> the ASpace codebase, the backend will not start. >>>> >>>> And yet, the setup-database.sh migration script ran without error, >>>> so at this point the schemas should be in sync. >>>> >>>> Any advice on how to get the backend up and running greatly >>>> appreciated, >>>> >>>> Mark >>>> >>>> -- >>>> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> >>>> Mark Cyzyk, M.A., M.L.S. >>>> Library Applications Group >>>> The Sheridan Libraries >>>> The Johns Hopkins University >>>> mcyzyk at jhu.edu >>>> Verba volant, scripta manent. >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Thu Jul 30 12:18:01 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Thu, 30 Jul 2020 16:18:01 +0000 Subject: [Archivesspace_Users_Group] Take a break with ArchivesSpace on Fridays In-Reply-To: References: <4C151ED1-3A98-4217-908A-55C7BA8ED233@lyrasis.org> <939F1E31-3ECB-44AD-93A6-6634E8BFF8F7@lyrasis.org> <512F3C3D-C506-4E11-B5FB-4B9EBF4775B0@lyrasis.org> <614B918C-6F58-4D55-89F5-18680C71701B@lyrasis.org> <69AD5D49-2C12-450D-9763-D88A59297611@lyrasis.org> <24DA2EB0-8EA2-42E8-9EC1-2377BAE51368@lyrasis.org> Message-ID: <46CE10A0-3DD9-4139-BF15-B9D19408EC16@lyrasis.org> Dear ArchivesSpace Users, We?ll be hosting another casual open call via zoom at 12pm ET tomorrow. With no set agenda or presentation for these calls, this forum is an opportunity to connect, chat and recharge. Use this as a time to get help or talk about ArchivesSpace (or anything else) in an informal setting or just have a beverage with other ArchivesSpace users during this stressful time. Most of us are doing our jobs under much different conditions than usual. As a browser based system you can access from anywhere, the ArchivesSpace application may offer a sense of archival normalcy as we each adjust. And with a welcoming and robust member community all over the world, ArchivesSpace can also offer camaraderie when many of us may feel isolated from our colleagues or the professional communities we interact with regularly. Thank you to everyone who joined us last week for a great chat. We hope to see you all tomorrow. When: Fridays Time: 12:00 p.m. ? 1:00 p.m. ET (9:00 a.m. ? 10:00 a.m. PT) Where: Zoom Join the call via the information below: Join Zoom Meeting https://lyrasis.zoom.us/j/281962467 Meeting ID: 281 962 467 One tap mobile +19292056099,,281962467# US (New York) +13126266799,,281962467# US (Chicago) Dial by your location +1 929 205 6099 US (New York) +1 312 626 6799 US (Chicago) +1 301 715 8592 US +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 253 215 8782 US 888 475 4499 US Toll-free 877 853 5257 US Toll-free Meeting ID: 281 962 467 Find your local number: https://lyrasis.zoom.us/u/awkFNWPxh We seek to provide a welcoming, fun, and safe community experience for everyone and adhere to Code4Lib?s CodeofConduct4Lib. The full text of the code of conduct is available at: http://bit.ly/coc4lib. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29074 bytes Desc: image001.jpg URL: From adrien_hilton at harvard.edu Thu Jul 30 13:58:13 2020 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Thu, 30 Jul 2020 17:58:13 +0000 Subject: [Archivesspace_Users_Group] Survey on API usage Message-ID: Dear Colleagues, At Harvard Library, our Library Technology Services unit is exploring how to support usage of the ArchivesSpace API. We've compiled a brief survey that we're hoping you can fill out. It will take about 20-30 minutes to complete. Your responses will be incredibly useful in helping us to establish sustainable models for maintenance and support. https://docs.google.com/forms/d/e/1FAIpQLSd_-Tx8xllx-vvVrTgBHKGhQ3XvgxZriZ_dni_bbJugHBoX1A/viewform?usp=sf_link You can find background information about the project here: https://wiki.harvard.edu/confluence/pages/viewpage.action?pageId=254280364 Responses by August 14th would be wonderful! Thanks in advance, Adrien -------------- next part -------------- An HTML attachment was scrubbed... URL: From adrien_hilton at harvard.edu Thu Jul 30 15:30:24 2020 From: adrien_hilton at harvard.edu (Hilton, Adrien) Date: Thu, 30 Jul 2020 19:30:24 +0000 Subject: [Archivesspace_Users_Group] Survey on API usage In-Reply-To: References: Message-ID: Apologies, the wiki page for background info is restricted, and permissions are at a much higher level. If folks are interested, feel free to reach out and I can share the text with you individually. Best wishes, Adrien From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Hilton, Adrien Sent: Thursday, July 30, 2020 1:58 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Survey on API usage Dear Colleagues, At Harvard Library, our Library Technology Services unit is exploring how to support usage of the ArchivesSpace API. We've compiled a brief survey that we're hoping you can fill out. It will take about 20-30 minutes to complete. Your responses will be incredibly useful in helping us to establish sustainable models for maintenance and support. https://docs.google.com/forms/d/e/1FAIpQLSd_-Tx8xllx-vvVrTgBHKGhQ3XvgxZriZ_dni_bbJugHBoX1A/viewform?usp=sf_link You can find background information about the project here: https://wiki.harvard.edu/confluence/pages/viewpage.action?pageId=254280364 Responses by August 14th would be wonderful! Thanks in advance, Adrien -------------- next part -------------- An HTML attachment was scrubbed... URL: From pshowell at anderson.edu Thu Jul 30 21:24:25 2020 From: pshowell at anderson.edu (Preston Howell) Date: Thu, 30 Jul 2020 21:24:25 -0400 Subject: [Archivesspace_Users_Group] Multi Tenant Instance Message-ID: Good evening user group! I'm working to set up a multi-tenant instance. We are using AWS for our hosting, but I have not worked with AWS before. Has anyone had success with this and want to pass along some tips? I've been reading through the docs , but I'm beginning to think my trouble is coming for a lack of experience of AWS. -- Preston Howell | Library Technology Specialist | Nicholson Library Anderson University | 1100 E Fifth St, Anderson, IN 46012-3495 765-641-4270 | pshowell at anderson.edu www.anderson.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From ndroark at anderson.edu Fri Jul 31 10:19:13 2020 From: ndroark at anderson.edu (Nic Stanton-Roark) Date: Fri, 31 Jul 2020 10:19:13 -0400 Subject: [Archivesspace_Users_Group] Tutorial videos Message-ID: Hi all, I'm looking for some relatively up-to-date (1.5 or later) tutorial videos for new users to ArchivesSpace. Any leads? *Nicholas Stanton-Roark* | Archivist | Robert A. Nicholson University Library Anderson University | 1100 E. Fifth St, Anderson, IN 46012 (765) 641-4285 <%28765%29%20641%204285> | ndroark at anderson.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Fri Jul 31 11:20:48 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Fri, 31 Jul 2020 15:20:48 +0000 Subject: [Archivesspace_Users_Group] Tutorial videos In-Reply-To: References: Message-ID: <8FCB18ED-2552-4A9F-B738-AD16B2EF2599@lyrasis.org> Hi Nick, I recommend checking out the user tutorial videos in the ArchivesSpace Help Center. In the Help Center, you can access the user manual and training videos for ArchivesSpace. The current user tutorial videos were all recorded using v2.6 or later. If you already have a Help Center account, you can navigate directly to the user tutorials at https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/910032919/ArchivesSpace+User+Tutorial+Videos. If you don?t currently have an account, you will need a Confluence account to access the Help Center. You can create an account by following the steps at https://bit.ly/3fgpt2M. You will need to use your institutional email address to create your account. We will receive notification of the new account and will add access to the Help Center. You can find more information about managing your Confluence account at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/918945793/Confluence+Account+Management and information about the ArchivesSpace Help Center and how to access it at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/917045261/ArchivesSpace+Help+Center. If you have colleagues that would also like access, please ask them to sign up for their own accounts using the information above. Best, Jessica Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] From: on behalf of Nic Stanton-Roark Reply-To: Archivesspace Users Group Date: Friday, July 31, 2020 at 10:19 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Tutorial videos Hi all, I'm looking for some relatively up-to-date (1.5 or later) tutorial videos for new users to ArchivesSpace. Any leads? [Image removed by sender.] Nicholas Stanton-Roark | Archivist | Robert A. Nicholson University Library Anderson University | 1100 E. Fifth St, Anderson, IN 46012 (765) 641-4285 | ndroark at anderson.edu -------------- 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 Jessica.Crouch at lyrasis.org Fri Jul 31 11:26:58 2020 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Fri, 31 Jul 2020 15:26:58 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - July 2020 In-Reply-To: <6BB0F9FA-794B-49E5-A481-AF8EEFED82D5@lyrasis.org> References: <6BB0F9FA-794B-49E5-A481-AF8EEFED82D5@lyrasis.org> Message-ID: [cid:image001.jpg at 01D6672D.806C9FC0] July 2020 Update Development ArchivesSpace is announcing the availability of v2.8.0. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.8.0. This release contains program-led and community pull requests that provide feature enhancements, bug fixes, infrastructure improvements, and documentation updates. Some items of note include the ability to merge top containers, new browse, search, and sort preferences in the staff interface, some improvements to search and display in the public interface, additional display and faceting options in the background jobs area, bug fixes and accessibility improvements. Developers at Harvard University contributed several new features related to containers and locations from the specification they circulated in the community last year. Fans of the popular Harvard import plugin will be pleased to see that its functionality is now included in ArchivesSpace, courtesy of our work with the plugin?s original developer, Bobbi Fox. Please note that if you used the plugin previously you will need to disable it before starting up ArchivesSpace post-upgrade. Thanks very much to community members Andrew Morrison, Austin Schaffer, Dave Mayo, David P. Steelman, Douglas Simon, Katie Amaral, Mark Custer, Mark Triggs, Matt Patterson, Michael Vandermillen, and Peter Heiner for their code contributions to this release. Program team members Lora Woodford and Mark Cooper wrote extensive code and supervised the work of the contractors we worked with us on this release: Bobbi Fox, Brian Zelip, Sarah Morrissey, and Manny Rodriguez. As always this release would not have been possible without the substantial efforts of our Development Prioritization sub-team, Testing sub-team, Technical Documentation sub-team, User Documentation sub-team, and Core Committers Group. Information on upgrading to a new version of ArchivesSpace is available at https://archivesspace.github.io/tech-docs/administration/upgrading.html. Please let us know if you have any questions or need help upgrading. This is the last release where our primary technical documentation will live at https://archivesspace.github.io/archivesspace/. If you?d like to get a jump on things, please change your bookmarks to https://archivesspace.github.io/tech-docs/ for all updates going forward. We want to acknowledge that these are incredibly tough times for so many of us. Even more than usual, we?ve really appreciated all that our team and community members have done to continue making ArchivesSpace better in the face of many challenges. Thanks for all your help and for letting us know how important the ArchivesSpace application and community have been to you in these times. Register now for the 6th Annual ArchivesSpace Member Forum There is still time to register for next week?s 6th Annual ArchivesSpace Member Forum! Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. Unlike previous years, ArchivesSpace will be holding its sixth Annual Member Forum virtually, on August 3-7, 2020, from 12pm-3pm ET each day via Zoom. This free event is a chance for ArchivesSpace members to come together to highlight the work they are doing in ArchivesSpace, show off new plugins or tools they?ve developed, and attend workshops and trainings on a variety of topics. As with our previous Annual Member Forums, it is being held in conjunction with the Society of American Archivists annual meeting, but it is not part of SAA and does not require registration for the SAA Annual Meeting. When: Presentations and breakout discussions will be held on August 3-4, 2020 from 12pm-3pm ET, and all individuals from ArchivesSpace member institutions are welcome to attend some or all of the sessions on these days. Small workshops covering specific elements of the ArchivesSpace application will be offered August 5-7, 2020 from 12pm-3pm ET. These workshops will be limited in capacity. Registrations for each day are separate and you must register individually for all days you are interested in attending. Where: All online via Zoom, with opportunities to join via computer or phone. Who Can Attend: The ArchivesSpace Member Forum is open to individuals from ArchivesSpace member institutions only. To register, you must use an institutional email address associated with an ArchivesSpace member institution. Registrations using personal email addresses and addresses associated with non-member institutions will not be accepted. This means that events with limited capacity may fill before you are able to correct your registration. Online registration: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1422819333/ArchivesSpace+Member+Forum+2020 Registrations for each day of the Forum are separate. You will need to register for each day you are interested in attending to guarantee your spot. Registration for each activity is linked above the session in the agenda. Workshop attendance is limited. Discussion sessions on Tuesday, August 4, will occur in two separate zoom rooms. You must register for both Zoom Room A and B if you want to attend discussions in both rooms. The number of registrations available for the workshops on August 5-7 is limited. The total number of attendees is noted next to the registration. To give as many people as possible a chance to attend, you may register for only one workshop. We will be recording the sessions on August 3, 2020 but will not be recording discussions or workshops. We encourage you to dip in and out of the live programs on August 3-4, 2020 as much as you can. Please feel free to contact ArchivesSpace Community Engagement Coordinator Jessica Crouch (jessica.crouch at lyrasis.org) with questions. We look forward to seeing many of you there! Membership Update As of July 31, we have 412 General members, 21 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. ________________________________ ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA?s Collection Management Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 22470 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 29062 bytes Desc: image002.jpg URL: