From Christine.Kim at lyrasis.org Fri Dec 1 13:40:29 2017 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Fri, 1 Dec 2017 18:40:29 +0000 Subject: [Archivesspace_Users_Group] [Archivesspace_tac_uac] ArchivesSpace Open Call - Nov 29 at 2pm EST / 11am PST In-Reply-To: References: Message-ID: Dear ArchivesSpace community, Thank you all for participating in the open discussion call this week! Notes have been posted on the wiki: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/312442910/2017-11-29+Meeting+notes And thanks to your feedback, we will make these open calls a regular part of our community conversations on a quarterly basis. Please save the date for Wednesday, February 21, 2-3pm ET / 11-12 PT. A formal announcement will follow. If you have additional feedback you?d like to share, please email Kim at christine.kim at lyrasis.org. Thanks so much! Best wishes, Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: Christine Kim Sent: Monday, November 27, 2017 10:18 AM To: Christine Kim ; archivesspace_users_group at lyralists.lyrasis.org; archivesspace_member_reps at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org; archivesspace_tac_uac at lyralists.lyrasis.org Subject: RE: [Archivesspace_tac_uac] ArchivesSpace Open Call - Nov 29 at 2pm EST / 11am PST Hi everyone, This is just a friendly reminder about the upcoming open Zoom call this Wednesday! This is an informal online get together and has no set agenda or presentations. Please feel free to come with anything ArchivesSpace that is on your mind on November 29 at 2pm EST / 11am PST. Potential topics open for discussion include: * ASpace training - ideas or requests for advanced topics? * Staff Interface Enhancement Working Group recommendations - thoughts or feedback? * Regional Forums - help us name this! * Cool plugins you are working on? * Fun collection arrangement projects? * The conversation is open! We?ll start here and see where we end up. Anything you?d like to share - ideas, news, questions - is welcome! Information about joining this call is available on this page: http://archivesspace.org/open-zoom-nov/. We look forward to seeing you on Wednesday! Best wishes, Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_tac_uac-bounces at lyralists.lyrasis.org [mailto:archivesspace_tac_uac-bounces at lyralists.lyrasis.org] On Behalf Of Christine Kim Sent: Friday, November 3, 2017 12:15 PM To: archivesspace_users_group at lyralists.lyrasis.org; archivesspace_member_reps at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org; archivesspace_tac_uac at lyralists.lyrasis.org Subject: [Archivesspace_tac_uac] ArchivesSpace Open Call - Nov 29 at 2pm EST / 11am PST Dear ArchivesSpace members, It?s been an exciting and busy year for all of us! As we approach the end of the calendar year, we would love to get a better sense of your ArchivesSpace experience, as well as give you a chance to ask the program team and each other questions. We are hosting an informal Zoom call on November 29 at 2-3pm EST (11am-12pm PST) so we can hear updates from each other and encourage group discussion. You will be able to join by either computer or phone. Our hope is to provide a space to surface news, ideas, and challenges. This might be an especially good chance to talk about non-technical questions or ideas that you weren?t quite sure about posting on the Users Group listserv but really would like help with from us or your peers. Here are the details of joining the call: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/804518729 Or iPhone one-tap : US: +16468769923,,804518729# or +16699006833,,804518729# Or Telephone? Dial(for higher quality, dial a number based on your current location)? US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968 Meeting ID: 804 518 729 International numbers available: https://zoom.us/zoomconference?m=-CnZdNUzB4VhAipYXVQs3X1IOX8LOfFC If you have any questions about this call, please email Kim at christine.kim at lyrasis.org. We look forward to ?seeing? you there! -------------- next part -------------- An HTML attachment was scrubbed... URL: From DUPREL at mailbox.sc.edu Mon Dec 4 09:48:26 2017 From: DUPREL at mailbox.sc.edu (DUPRE, LANCE) Date: Mon, 4 Dec 2017 14:48:26 +0000 Subject: [Archivesspace_Users_Group] Problems with merging extent types In-Reply-To: References: Message-ID: <661CD015-0D44-4B7B-8717-3CDA9C6B35E4@mailbox.sc.edu> Hello all, I am having an issue with creating new extent types and then merging old extent types into the new. After the merge, on the Controlled Value List: Extent Extent Type (extent_extent_type) page the new type shows that it is not used. If I go to and actual record that contained the merged extent type, the new extent type is there correctly merged. This is the process I am using. Am I doing something wrong? Create a new value on the Controlled Value List: Extent Extent Type (extent_extent_type) page. Select the merge option for the old extent type. Select the new extent type for the old to be merged into. Click merge value. From bthomas at tsl.texas.gov Mon Dec 4 10:22:51 2017 From: bthomas at tsl.texas.gov (Brian Thomas) Date: Mon, 4 Dec 2017 15:22:51 +0000 Subject: [Archivesspace_Users_Group] Problems with merging extent types In-Reply-To: <661CD015-0D44-4B7B-8717-3CDA9C6B35E4@mailbox.sc.edu> References: <661CD015-0D44-4B7B-8717-3CDA9C6B35E4@mailbox.sc.edu> Message-ID: How long did you wait before checking? I had a similar problem with a different controlled value and the next day the right value showed up, which I would assume it the index waiting to catch up to reality. Also, did you refresh the webpage? -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of DUPRE, LANCE Sent: Monday, December 04, 2017 8:48 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Problems with merging extent types Hello all, I am having an issue with creating new extent types and then merging old extent types into the new. After the merge, on the Controlled Value List: Extent Extent Type (extent_extent_type) page the new type shows that it is not used. If I go to and actual record that contained the merged extent type, the new extent type is there correctly merged. This is the process I am using. Am I doing something wrong? Create a new value on the Controlled Value List: Extent Extent Type (extent_extent_type) page. Select the merge option for the old extent type. Select the new extent type for the old to be merged into. Click merge value. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cbthomas%40tsl.texas.gov%7C4061d9e4d4a548fa9b9a08d53b26286b%7Ca4597bff9f384145a0334a2168399a5e%7C0%7C0%7C636479957432387389&sdata=mfJnAILcvmOunqMYkMnb1WrQPPlNsvOt0n0VDApkdaY%3D&reserved=0 From DUPREL at mailbox.sc.edu Mon Dec 4 10:45:17 2017 From: DUPREL at mailbox.sc.edu (DUPRE, LANCE) Date: Mon, 4 Dec 2017 15:45:17 +0000 Subject: [Archivesspace_Users_Group] Problems with merging extent types In-Reply-To: References: <661CD015-0D44-4B7B-8717-3CDA9C6B35E4@mailbox.sc.edu> Message-ID: <90684755-7E87-4507-921A-FE486ED71CCB@mailbox.sc.edu> I did the merge Friday afternoon and checked it this morning. I did refresh the webpage and also checked it on a different computer with the same results. I?ll check on the indexing to see if it is stuck somewhere. Thanks. On Dec 4, 2017, at 10:22 AM, Brian Thomas > wrote: How long did you wait before checking? I had a similar problem with a different controlled value and the next day the right value showed up, which I would assume it the index waiting to catch up to reality. Also, did you refresh the webpage? -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of DUPRE, LANCE Sent: Monday, December 04, 2017 8:48 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Problems with merging extent types Hello all, I am having an issue with creating new extent types and then merging old extent types into the new. After the merge, on the Controlled Value List: Extent Extent Type (extent_extent_type) page the new type shows that it is not used. If I go to and actual record that contained the merged extent type, the new extent type is there correctly merged. This is the process I am using. Am I doing something wrong? Create a new value on the Controlled Value List: Extent Extent Type (extent_extent_type) page. Select the merge option for the old extent type. Select the new extent type for the old to be merged into. Click merge value. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cbthomas%40tsl.texas.gov%7C4061d9e4d4a548fa9b9a08d53b26286b%7Ca4597bff9f384145a0334a2168399a5e%7C0%7C0%7C636479957432387389&sdata=mfJnAILcvmOunqMYkMnb1WrQPPlNsvOt0n0VDApkdaY%3D&reserved=0 _______________________________________________ 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 DUPREL at mailbox.sc.edu Mon Dec 4 11:02:48 2017 From: DUPREL at mailbox.sc.edu (DUPRE, LANCE) Date: Mon, 4 Dec 2017 16:02:48 +0000 Subject: [Archivesspace_Users_Group] Problems with merging extent types In-Reply-To: <90684755-7E87-4507-921A-FE486ED71CCB@mailbox.sc.edu> References: <661CD015-0D44-4B7B-8717-3CDA9C6B35E4@mailbox.sc.edu> <90684755-7E87-4507-921A-FE486ED71CCB@mailbox.sc.edu> Message-ID: I forced a reindex by deleting the indexer_state directory and that seemed to work. Thanks for the help! On Dec 4, 2017, at 10:45 AM, DUPRE, LANCE > wrote: I did the merge Friday afternoon and checked it this morning. I did refresh the webpage and also checked it on a different computer with the same results. I?ll check on the indexing to see if it is stuck somewhere. Thanks. On Dec 4, 2017, at 10:22 AM, Brian Thomas > wrote: How long did you wait before checking? I had a similar problem with a different controlled value and the next day the right value showed up, which I would assume it the index waiting to catch up to reality. Also, did you refresh the webpage? -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of DUPRE, LANCE Sent: Monday, December 04, 2017 8:48 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Problems with merging extent types Hello all, I am having an issue with creating new extent types and then merging old extent types into the new. After the merge, on the Controlled Value List: Extent Extent Type (extent_extent_type) page the new type shows that it is not used. If I go to and actual record that contained the merged extent type, the new extent type is there correctly merged. This is the process I am using. Am I doing something wrong? Create a new value on the Controlled Value List: Extent Extent Type (extent_extent_type) page. Select the merge option for the old extent type. Select the new extent type for the old to be merged into. Click merge value. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=02%7C01%7Cbthomas%40tsl.texas.gov%7C4061d9e4d4a548fa9b9a08d53b26286b%7Ca4597bff9f384145a0334a2168399a5e%7C0%7C0%7C636479957432387389&sdata=mfJnAILcvmOunqMYkMnb1WrQPPlNsvOt0n0VDApkdaY%3D&reserved=0 _______________________________________________ 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 livsolis at utexas.edu Mon Dec 4 11:55:18 2017 From: livsolis at utexas.edu (Olivia S Solis) Date: Mon, 4 Dec 2017 10:55:18 -0600 Subject: [Archivesspace_Users_Group] Moving archival objects --> Inventory display issues Message-ID: Hi all, So, we are using the API to migrate all of our legacy data into ASpace. I accidentally assigned a number of archival objects to the wrong parent. (oops!) We figured out how to interpret all the parameters here: https://archivesspace.github.io/archivesspace/api/#post-repositories-repo_id-archival_objects-id-accept_children to reassign to the children to the correct parents. Everything worked great except there now seem to be some display issues in the inventory tree in the staff interface. The level for the moved archival objects are misaligned with the rest of the archival objects in the collection. I've not yet linked all of our containers to their associated archival objects, but I made a fake container and associated it to one of the moved children to see what would happen. The level appears in the same cell as the fake container indicator. See screen shot. I looked at the JSON, and everything looks good there. Before adding the container: {"lock_version":1,"position":0,"publish":true,"ref_id":"6f79ba7ad742e13a3a01dba335e443c4","title":"American Civil Liberties Union (ACLU) in San Antonio","display_string":"American Civil Liberties Union (ACLU) in San Antonio","other_level":"unspecified","restrictions_apply":false,"created_by":"osolis","last_modified_by":"osolis","create_time":"2017-08-03T17:46:31Z","system_mtime":"2017-12-04T16:17:28Z","user_mtime":"2017-10-12T20:28:28Z","suppressed":false,"level":"otherlevel","jsonmodel_type":"archival_object","external_ids":[],"subjects":[],"linked_events":[],"extents":[],"dates":[],"external_documents":[],"rights_statements":[],"linked_agents":[],"instances":[],"notes":[],"uri":"/repositories/2/archival_objects/591562","repository":{"ref":"/repositories/2"},"resource":{"ref":"/repositories/2/resources/567"},"parent":{"ref":"/repositories/2/archival_objects/594393"},"has_unpublished_ancestor":false} After adding the container: {"lock_version":2,"position":0,"publish":true,"ref_id":"6f79ba7ad742e13a3a01dba335e443c4","title":"American Civil Liberties Union (ACLU) in San Antonio","display_string":"American Civil Liberties Union (ACLU) in San Antonio","other_level":"unspecified","restrictions_apply":false,"created_by":"osolis","last_modified_by":"osolis","create_time":"2017-08-03T17:46:31Z","system_mtime":"2017-12-04T16:36:05Z","user_mtime":"2017-12-04T16:36:05Z","suppressed":false,"level":"otherlevel","jsonmodel_type":"archival_object","external_ids":[],"subjects":[],"linked_events":[],"extents":[],"dates":[],"external_documents":[],"rights_statements":[],"linked_agents":[],"instances":[{"lock_version":0,"created_by":"osolis","last_modified_by":"osolis","create_time":"2017-12-04T16:36:05Z","system_mtime":"2017-12-04T16:36:05Z","user_mtime":"2017-12-04T16:36:05Z","instance_type":"mixed_materials","jsonmodel_type":"instance","is_representative":false,"sub_container":{"lock_version":0,"created_by":"osolis","last_modified_by":"osolis","create_time":"2017-12-04T16:36:05Z","system_mtime":"2017-12-04T16:36:05Z","user_mtime":"2017-12-04T16:36:05Z","jsonmodel_type":"sub_container","top_container":{"ref":"/repositories/2/top_containers/28804"}},"container":{"type_1":"box","indicator_1":"fake container","container_locations":[],"lock_version":1}}],"notes":[],"uri":"/repositories/2/archival_objects/591562","repository":{"ref":"/repositories/2"},"resource":{"ref":"/repositories/2/resources/567"},"parent":{"ref":"/repositories/2/archival_objects/594393"},"has_unpublished_ancestor":false} ...so I think our data is good. Has anyone else experienced this kink when using the API to move archival objects? Any suggestions? Reindexing? Thanks! Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-12-04 at 10.36.19 AM.png Type: image/png Size: 375660 bytes Desc: not available URL: From livsolis at utexas.edu Mon Dec 4 12:36:47 2017 From: livsolis at utexas.edu (Olivia S Solis) Date: Mon, 4 Dec 2017 11:36:47 -0600 Subject: [Archivesspace_Users_Group] Multi-factor authentication and ASpace Message-ID: Hello all, So we are setting up our web-hosted instance of ASpace. Thus far we have been utilizing a secure VM that we have to tunnel into while we migrate all of our legacy data into the system. We want to set up a two-factor authentication system in our web-hosted version of the staff interface as we have a lot of sensitive donor data in the system. Our the service provider for our web-hosted version is inquiring as to the technologies ASpace uses to support authentication... LDAP, OAuth, or PAM. From our provider, "if it supports PAM then I?m pretty confident we have an easy path to supporting two-factor authentication, if not we have to get into the OAuth realm which I don?t think is straightforward yet, but we have folks around here with more expertise." This is foreign territory for me so I'm directly quoting our contact. We've looked a bit at the documentation, but haven't found the information we are looking for. Does anyone have experience with multi-factor authentication and ASpace? If so, what mechanism did you use (technology and MFA provider)? Thanks! Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From benn.joseph at northwestern.edu Mon Dec 4 14:53:45 2017 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Mon, 4 Dec 2017 19:53:45 +0000 Subject: [Archivesspace_Users_Group] problem with collection-level Digital Object links Message-ID: Hi all, Strange problem here, but perhaps there's an easy solution. For some of our Resource records we're trying to create a collection-level Digital Object that will contain a link to the area on our repository that contains digitized content from those collections. For a collection of glass slides, for instance, will create a collection-level Digital Object with this link as the File URI: http://images.northwestern.edu/catalog?f[institutional_collection_title_facet][]=George%20Silas%20Duntley%20%281879-1957%29%20Photographs%2C%20circa%201899-1918 What we've discovered, though, is that even though the whole link is in there, ArchivesSpace somehow drops everything after the question mark and leaves you with: http://images.northwestern.edu/catalog? ...which is just a link to the main Images Repository intro page (not very helpful). So, we decided to get around this by creating an ARK for each publicly available image collection in our Images Repository and using that as the File URI in ArchivesSpace. This works great! But only in Firefox and Internet Explorer. Chrome and Safari take the ARK (http://n2t.net/ark:/81985/n2t19k, for example) and add a question mark ("?") to the end of the url, which results in a page displaying an error message relating to our ARK setup. It appears that ArchivesSpace is adding this question mark, but whereas Firefox just ignores it (and makes it go away), Chrome gets tripped up. We tried using a bit.ly link in desperation, and it works just fine in all browsers...but we'd prefer not to actually start using bit.ly links in finding aids on our production server. Does anyone know how we can go about creating collection-level Digital Object links to our digitized materials in a stable manner? Seems like ArchivesSpace can link to an image file no problem, but it gets confused with other types of urls. Best, --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -------------- next part -------------- An HTML attachment was scrubbed... URL: From edgar-garcia at northwestern.edu Mon Dec 4 15:07:30 2017 From: edgar-garcia at northwestern.edu (Edgar Garcia) Date: Mon, 4 Dec 2017 20:07:30 +0000 Subject: [Archivesspace_Users_Group] problem with collection-level Digital Object links In-Reply-To: References: Message-ID: <555B6575-929F-4236-B988-419E7D34BCB7@northwestern.edu> Benn, There is a pull request that I believe touches on this: https://github.com/archivesspace/archivesspace/pull/1047 I think this is why it happens. I?ve been trying to look over this code because this pull request I think will break because our digital repository doesn?t accept POST requests for our object pages and it was requiring us to refresh the page for it to load. I *think* when a thumbnail is missing, the page uses a form as a link instead of an anchor tag and that is where GET/POST. I haven?t been able to figure out why this was the decision. Does anyone else know the answer to this? I?d rather some generic icon/img be used with an anchor tag to avoid this form/POST issue. Edgar ---------- Edgar Garcia Senior Software Developer Discovery Platform Services Metadata & Discovery Services Digital Strategies Northwestern University Libraries Northwestern University Evanston, IL 60208 From: on behalf of Benn Joseph Reply-To: Archivesspace Users Group Date: Monday, December 4, 2017 at 1:53 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] problem with collection-level Digital Object links Hi all, Strange problem here, but perhaps there?s an easy solution. For some of our Resource records we?re trying to create a collection-level Digital Object that will contain a link to the area on our repository that contains digitized content from those collections. For a collection of glass slides, for instance, will create a collection-level Digital Object with this link as the File URI: http://images.northwestern.edu/catalog?f[institutional_collection_title_facet][]=George%20Silas%20Duntley%20%281879-1957%29%20Photographs%2C%20circa%201899-1918 What we?ve discovered, though, is that even though the whole link is in there, ArchivesSpace somehow drops everything after the question mark and leaves you with: http://images.northwestern.edu/catalog? ?which is just a link to the main Images Repository intro page (not very helpful). So, we decided to get around this by creating an ARK for each publicly available image collection in our Images Repository and using that as the File URI in ArchivesSpace. This works great! But only in Firefox and Internet Explorer. Chrome and Safari take the ARK (http://n2t.net/ark:/81985/n2t19k, for example) and add a question mark (???) to the end of the url, which results in a page displaying an error message relating to our ARK setup. It appears that ArchivesSpace is adding this question mark, but whereas Firefox just ignores it (and makes it go away), Chrome gets tripped up. We tried using a bit.ly link in desperation, and it works just fine in all browsers?but we?d prefer not to actually start using bit.ly links in finding aids on our production server. Does anyone know how we can go about creating collection-level Digital Object links to our digitized materials in a stable manner? Seems like ArchivesSpace can link to an image file no problem, but it gets confused with other types of urls. Best, --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Mon Dec 4 15:43:14 2017 From: livsolis at utexas.edu (Olivia S Solis) Date: Mon, 4 Dec 2017 14:43:14 -0600 Subject: [Archivesspace_Users_Group] Moving archival objects --> Inventory display issues In-Reply-To: References: Message-ID: For anybody riveted by this post, reindexing didn't help the problem. :) On Mon, Dec 4, 2017 at 10:55 AM, Olivia S Solis wrote: > Hi all, > > So, we are using the API to migrate all of our legacy data into ASpace. I > accidentally assigned a number of archival objects to the wrong parent. > (oops!) We figured out how to interpret all the parameters here: > https://archivesspace.github.io/archivesspace/api/#post- > repositories-repo_id-archival_objects-id-accept_children > to reassign to the children to the correct parents. Everything worked > great except there now seem to be some display issues in the inventory tree > in the staff interface. The level for the moved archival objects are > misaligned with the rest of the archival objects in the collection. I've > not yet linked all of our containers to their associated archival objects, > but I made a fake container and associated it to one of the moved children > to see what would happen. The level appears in the same cell as the fake > container indicator. See screen shot. > > I looked at the JSON, and everything looks good there. Before adding the > container: > > {"lock_version":1,"position":0,"publish":true,"ref_id":" > 6f79ba7ad742e13a3a01dba335e443c4","title":"American Civil Liberties Union > (ACLU) in San Antonio","display_string":"American Civil Liberties Union > (ACLU) in San Antonio","other_level":"unspecified","restrictions_ > apply":false,"created_by":"osolis","last_modified_by":" > osolis","create_time":"2017-08-03T17:46:31Z","system_ > mtime":"2017-12-04T16:17:28Z","user_mtime":"2017-10-12T20: > 28:28Z","suppressed":false,"level":"otherlevel"," > jsonmodel_type":"archival_object","external_ids":[]," > subjects":[],"linked_events":[],"extents":[],"dates":[]," > external_documents":[],"rights_statements":[],"linked_ > agents":[],"instances":[],"notes":[],"uri":"/repositories/2/archival_ > objects/591562","repository":{"ref":"/repositories/2"}," > resource":{"ref":"/repositories/2/resources/567"},"parent":{"ref":"/ > repositories/2/archival_objects/594393"},"has_unpublished_ancestor":false} > > After adding the container: > {"lock_version":2,"position":0,"publish":true,"ref_id":" > 6f79ba7ad742e13a3a01dba335e443c4","title":"American Civil Liberties Union > (ACLU) in San Antonio","display_string":"American Civil Liberties Union > (ACLU) in San Antonio","other_level":"unspecified","restrictions_ > apply":false,"created_by":"osolis","last_modified_by":" > osolis","create_time":"2017-08-03T17:46:31Z","system_ > mtime":"2017-12-04T16:36:05Z","user_mtime":"2017-12-04T16: > 36:05Z","suppressed":false,"level":"otherlevel"," > jsonmodel_type":"archival_object","external_ids":[]," > subjects":[],"linked_events":[],"extents":[],"dates":[]," > external_documents":[],"rights_statements":[],"linked_ > agents":[],"instances":[{"lock_version":0,"created_by":" > osolis","last_modified_by":"osolis","create_time":"2017- > 12-04T16:36:05Z","system_mtime":"2017-12-04T16:36:05Z", > "user_mtime":"2017-12-04T16:36:05Z","instance_type":" > mixed_materials","jsonmodel_type":"instance","is_ > representative":false,"sub_container":{"lock_version":0," > created_by":"osolis","last_modified_by":"osolis","create_ > time":"2017-12-04T16:36:05Z","system_mtime":"2017-12-04T16: > 36:05Z","user_mtime":"2017-12-04T16:36:05Z","jsonmodel_type" > :"sub_container","top_container":{"ref":"/repositories/2/top_containers/ > 28804"}},"container":{"type_1":"box","indicator_1":"fake > container","container_locations":[],"lock_version": > 1}}],"notes":[],"uri":"/repositories/2/archival_ > objects/591562","repository":{"ref":"/repositories/2"}," > resource":{"ref":"/repositories/2/resources/567"},"parent":{"ref":"/ > repositories/2/archival_objects/594393"},"has_unpublished_ancestor":false} > > ...so I think our data is good. > > Has anyone else experienced this kink when using the API to move archival > objects? Any suggestions? Reindexing? > > Thanks! > Olivia > -- > Olivia Solis, MSIS > Metadata Coordinator > Dolph Briscoe Center for American History > The University of Texas at Austin > 2300 Red River St. Stop D1100 > Austin TX, 78712-1426 > (512) 232-8013 <(512)%20232-8013> > -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Mon Dec 4 15:57:45 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Mon, 4 Dec 2017 20:57:45 +0000 Subject: [Archivesspace_Users_Group] problem with collection-level Digital Object links In-Reply-To: <555B6575-929F-4236-B988-419E7D34BCB7@northwestern.edu> References: <555B6575-929F-4236-B988-419E7D34BCB7@northwestern.edu> Message-ID: <2CC7EA9E-7239-4935-A375-624D9840F4FE@virginia.edu> Originally the code had method=?POST? on the form action. None of my links worked with POST, and after asking about the logic of why view was coded this way and getting no response, I submitted request to change that to method=?GET?, being unaware that form processing strips parameters off of URLs for GETs. So that change fixed some links but broke or didn?t fix others. That current pull request just proposes to change method=?GET? back to original method=?POST? , which still will not work for some links. I was just looking at this history and the code again when your email arrived: still trying to figure out the original logic ? is the a reason it?s coded as a form action instead of just an anchor link ? It could be fixed up in local plugin javascript, but it may still require some other context being included to figure out what needs to be done. ( Not all of the digital_object or file_version attributes are exposed in the public view as they are in the staff view. May need to include more context in a hidden form object. ) ? Steve Majewski > On Dec 4, 2017, at 3:07 PM, Edgar Garcia wrote: > > Benn, > > There is a pull request that I believe touches on this: https://github.com/archivesspace/archivesspace/pull/1047 > > I think this is why it happens. > > I?ve been trying to look over this code because this pull request I think will break because our digital repository doesn?t accept POST requests for our object pages and it was requiring us to refresh the page for it to load. > > I *think* when a thumbnail is missing, the page uses a form as a link instead of an anchor tag and that is where GET/POST. I haven?t been able to figure out why this was the decision. > > Does anyone else know the answer to this? I?d rather some generic icon/img be used with an anchor tag to avoid this form/POST issue. > > Edgar > ---------- > Edgar Garcia > Senior Software Developer > Discovery Platform Services > Metadata & Discovery Services > Digital Strategies > Northwestern University Libraries > Northwestern University > Evanston, IL 60208 > > From: on behalf of Benn Joseph > Reply-To: Archivesspace Users Group > Date: Monday, December 4, 2017 at 1:53 PM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] problem with collection-level Digital Object links > > Hi all, > Strange problem here, but perhaps there?s an easy solution. For some of our Resource records we?re trying to create a collection-level Digital Object that will contain a link to the area on our repository that contains digitized content from those collections. For a collection of glass slides, for instance, will create a collection-level Digital Object with this link as the File URI: > > http://images.northwestern.edu/catalog?f[institutional_collection_title_facet][]=George%20Silas%20Duntley%20%281879-1957%29%20Photographs%2C%20circa%201899-1918 > > What we?ve discovered, though, is that even though the whole link is in there, ArchivesSpace somehow drops everything after the question mark and leaves you with: > > http://images.northwestern.edu/catalog ? > > ?which is just a link to the main Images Repository intro page (not very helpful). > > So, we decided to get around this by creating an ARK for each publicly available image collection in our Images Repository and using that as the File URI in ArchivesSpace. This works great! But only in Firefox and Internet Explorer. Chrome and Safari take the ARK (http://n2t.net/ark:/81985/n2t19k , for example) and add a question mark (???) to the end of the url, which results in a page displaying an error message relating to our ARK setup. It appears that ArchivesSpace is adding this question mark, but whereas Firefox just ignores it (and makes it go away), Chrome gets tripped up. > > We tried using a bit.ly link in desperation, and it works just fine in all browsers?but we?d prefer not to actually start using bit.ly links in finding aids on our production server. Does anyone know how we can go about creating collection-level Digital Object links to our digitized materials in a stable manner? Seems like ArchivesSpace can link to an image file no problem, but it gets confused with other types of urls. > > Best, > --Benn > > Benn Joseph > Head of Archival Processing > Northwestern University Libraries > Northwestern University > www.library.northwestern.edu > benn.joseph at northwestern.edu > 847.467.6581 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: From Kate.F.Herbert at maine.gov Mon Dec 4 16:02:59 2017 From: Kate.F.Herbert at maine.gov (Herbert, Kate F) Date: Mon, 4 Dec 2017 21:02:59 +0000 Subject: [Archivesspace_Users_Group] Digital Object Component Agents Message-ID: Hello All, We are just starting to add Digital Object with Components to our system. I was testing uploading then via the Digital Objects CSV, but have found that if the components have different agents then the parent the agents do not come through on the upload. Dates and file version information was not affected, we are not using subjects or notes. Thanks, Kate Herbert Cultural Heritage Data Specialist Shared position between the Maine State Archives, Maine State Library, & Maine State Museum (207) 712-9494 kate.f.herbert at maine.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From randy.kuehn at louisville.edu Mon Dec 4 18:18:14 2017 From: randy.kuehn at louisville.edu (Kuehn,Randy) Date: Mon, 4 Dec 2017 23:18:14 +0000 Subject: [Archivesspace_Users_Group] Disable Display of Classification Identifiers in PUI Message-ID: Hello, I'm currently in the process of configuring v.2.2.0 and I've run into a bit of a problem. Has anyone found or figured out a way to disable the identifier from prepending itself to classification titles throughout the PUI? Thanks, Randy Randy Kuehn Digital Technologies Systems Librarian Office of Libraries Technology Ekstrom Library University of Louisville Louisville, KY 40292 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyndi.shein at unlv.edu Wed Dec 6 14:33:14 2017 From: cyndi.shein at unlv.edu (Cyndi Shein) Date: Wed, 6 Dec 2017 11:33:14 -0800 Subject: [Archivesspace_Users_Group] ILS and AS In-Reply-To: References: Message-ID: Hi All, I'm not sure exactly what functions or edits you're looking for, but you may be able to adapt an existing plugin while you work on a long-term solution for integrating ASpace with your LSP or ILS. UNLV Libraries uses a plugin with check-boxes that allows us to customize the MARCXML fields that ASpace exports. We use it to prepare records for import into OCLC Connexion, reducing the manual editing we have to do. The plugin is on GitHub: https://github.com/l3mus/ArchivesSpace-authority-project/tree/master/unlv_marc_exporter How we use the plugin and a screenshot of the staff interface is here: http://elischolar.library.yale.edu/jcas/vol4/iss1/2/ (page 7-8 has the explanation, page 16 has a screenshot). Cyndi Shein UNLV Libraries Special Collections and Archives Technical Services On Mon, Nov 27, 2017 at 11:47 AM, Caitlin Wells wrote: > I definitely support this! We're currently trying to figure out a way to > translate the exported MARCXML from v. 1.5.4 for import into Aleph, and I'd > love to hear what everyone else is doing. > > Caitlin > -- > Caitlin R. Wells > Collection Services Librarian, Special Collections Library > University of Michigan, Ann Arbor 48109 > P: (734) 763-7901 > > On Mon, Nov 27, 2017 at 2:34 PM, Pyzynski, Susan C. < > pyzynski at fas.harvard.edu> wrote: > >> Hi Jason, >> >> >> >> I also heartily second this idea. We are just at the beginning stages of >> thinking about these exact questions here. At Houghton we need a record in >> Aleph (soon to be Alma) for invoice paying and managing offsite >> collections, to get a record in ASpace for accessioning/access, and have a >> record in OCLC/Worldcat so our holdings are represented accurately. We are >> trying to determine the most streamlined workflow(s) to achieve this, and >> also figure out the maintenance these records in 3 different places. >> >> >> >> While repositories needs differ somewhat, it sounds like we are all >> dealing with a fundamental issue, moving our metadata around in as >> streamlined and efficient a way possible. >> >> >> >> All the best, >> >> Susan >> >> >> >> >> >> Susan C. Pyzynski >> >> Associate Librarian of Houghton Library for Technical Services >> >> Harvard Library >> >> Harvard University >> >> Cambridge MA 02138 >> >> pyzynski at fas.harvard.edu >> >> >> >> >> >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: >> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Shelley >> M. Hayreh >> *Sent:* Monday, November 27, 2017 2:34 PM >> *To:* Archivesspace Users Group > alists.lyrasis.org> >> *Subject:* Re: [Archivesspace_Users_Group] ILS and AS >> >> >> >> Yes, I strongly second that! Thank you Jason and all. >> >> >> >> On Mon, Nov 27, 2017 at 2:12 PM, Jason Loeffler >> wrote: >> >> Great to hear so much interest and support in ILS integration. Unless >> anyone has any other ideas, I propose putting out an open call to the >> community to garner interest in forming a working group to: >> >> - share information >> - flesh out use cases >> - define workflows >> - and, possibly, contribute to a specification for a plugin or core >> enhancements, should the need arise. >> >> Does anyone want to second this approach? >> >> >> >> Jason Loeffler >> >> Technology Consultant | The American Academy in Rome >> >> Minor Science | Application Development & Metadata Strategy >> >> Brooklyn, New York >> >> jason at minorscience.com >> >> (347) 405-0826 >> >> minorscience (Skype) >> >> >> >> On Mon, Nov 27, 2017 at 1:49 PM, Christie Peterson >> wrote: >> >> Hello, >> >> >> >> My medium-range plan is that once we turn on the ASpace PUI, we'll >> include it in our library's main discovery layer as another area of the >> "bento" results layout. >> >> >> >> However, I've been told that we need to keep producing MARC records >> because otherwise our collections won't get into OCLC/WorldCat. If someone >> has or dreams of a method that achieves this goal without the overhead of >> MARC record creation and maintenance, I would love to hear more. >> >> >> >> Thanks, >> >> >> >> Christie Peterson >> >> >> >> On Mon, Nov 27, 2017 at 1:07 PM Sarah Horowitz >> wrote: >> >> Hello, >> >> >> >> We are currently in the planning phases of a project to get all our >> ASpace records into our ILS; implementation will begin this winter. There >> has been a lot of data clean-up to make this possible; we're still trying >> to come up with a work-around for the fact that beyond the first author, >> the exporter throws everything into one 7xx field rather than separating >> each of them out. >> >> >> >> This is a very important project for us, as many people are more likely >> to discover our collections through our ILS/discovery layer than through >> the ASpace site itself. I would love to see some support from the >> Integrations team for projects like this. >> >> >> >> All the best, >> >> Sarah >> >> >> >> On Mon, Nov 27, 2017 at 12:57 PM, Jason Loeffler >> wrote: >> >> Hi Shelley, >> >> >> >> This topic has been discussed recently in Integrations >> meetings, >> though, given team members current commitments, we temporarily dropped the >> discussion. >> >> >> >> At the Academy's New York office, we're currently using a few custom >> tools to map ArchivesSpace resource component JSON to MARC bibliographic >> records. The latest version of ArchivesSpace has an OAI-PMH MARC responder. >> If your ILS has an OAI-PMH client that may be worth exploring. Reconciling >> subject and named authorities between the two systems is particularly >> tricky. Happy to discuss this in more detail should the occasion arise. >> >> >> >> I'm curious to know whether other institutions are grappling with this >> use case. If there's a critical mass of support, perhaps the Integrations >> team should take this matter up in the future. >> >> >> >> Regards, Jason >> >> >> Jason Loeffler >> >> Technology Consultant | The American Academy in Rome >> >> Minor Science | Application Development & Metadata Strategy >> >> Brooklyn, New York >> >> jason at minorscience.com >> >> (347) 405-0826 >> >> minorscience (Skype) >> >> >> >> On Mon, Nov 27, 2017 at 12:08 PM, Shelley M. Hayreh >> wrote: >> >> Hello AS community, >> >> I'm serving on an implementation task-force reviewing how the adoption of >> ArchivesSpace might change various workflows currently in place. A couple >> of questions have arisen that I'm hoping the AS community can speak to: >> >> >> >> -Is anyone in the community using ArchivesSpace to populate their >> catalog/ILS? >> >> >> >> -Can AS contribute directly to OCLC or ArchivesGrid, therefore bypassing >> the ILS? >> >> >> >> Thank you! >> >> >> >> Shelley >> >> -- >> >> Shelley Hayreh >> >> Avery Archivist >> >> Avery Architectural and Fine Arts Library >> >> 1172 Amsterdam Avenue MC0301 >> >> New York, NY 10027 >> >> 212-854-0760 <(212)%20854-0760> >> >> Web:http://library.columbia.edu/indiv/avery/da.html >> >> >> >> >> >> >> >> _______________________________________________ >> 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 >> >> >> >> >> -- >> >> Sarah Horowitz >> >> Curator of Rare Books and Manuscripts >> Head of Quaker & Special Collections >> >> Haverford College Libraries >> Haverford College >> >> 370 Lancaster Ave. >> >> Haverford, PA 19041 >> (610) 896-2948 >> >> shorowitz at haverford.edu >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> -- >> >> ? >> >> Christie S. Peterson >> >> >> >> Head of Technical Services for Special Collections >> >> Smith College >> >> Northampton, Mass. >> >> 413-585-2996 <(413)%20585-2996> >> >> cpeterson at smith.edu >> >> >> >> pronouns: she/her/hers >> >> >> _______________________________________________ >> 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 >> >> >> >> >> >> -- >> >> Shelley Hayreh >> >> Avery Archivist >> >> Avery Architectural and Fine Arts Library >> >> 1172 Amsterdam Avenue MC0301 >> >> New York, NY 10027 >> >> 212-854-0760 <(212)%20854-0760> >> >> Web:http://library.columbia.edu/indiv/avery/da.html >> >> >> >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Caitlin R. Wells > Collection Services Librarian, Special Collections Library > University of Michigan, Ann Arbor 48109 > P: (734) 763-7901 > > _______________________________________________ > 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 msf252 at cornell.edu Wed Dec 6 15:46:38 2017 From: msf252 at cornell.edu (Marcie Suzanne Farwell) Date: Wed, 6 Dec 2017 20:46:38 +0000 Subject: [Archivesspace_Users_Group] Importing containers from EAD Message-ID: Hello all, We're in ASpace testing phase and I am attempting to import an EAD file. For our current system all I need for containers are: 1 2 1938 Abraham Lincoln Lives Again Allan, Anne New York, New York We know that for ASpace every box needs and id and in the past we encoded this as 1 for everything in Box 1 and that worked for the previous version of ASpace. Now it seems that the id number needs to be unique because I am getting this error: instances/0/sub_container/type_2 : container 2 requires both a type and indicator When I manually create a unique id, it imports just fine. We don't currently create unique ids for our boxes. Is there a way around this? How are other people creating unique ids for their containers? I don't see any questions on the list related to this so perhaps there is something simple I am overlooking. Thanks, Marcie Technical Services Archivist Division of Rare and Manuscript Collections 2B Kroch Library Cornell University Library Ithaca, NY 14853 607-255-3530 -------------- next part -------------- An HTML attachment was scrubbed... URL: From j at minorscience.com Wed Dec 6 16:30:38 2017 From: j at minorscience.com (Jason Loeffler) Date: Wed, 6 Dec 2017 16:30:38 -0500 Subject: [Archivesspace_Users_Group] ILS and AS In-Reply-To: References: Message-ID: Hi Cyndi, I just took a peek at the code. It looks the UNLV extends the ArchivesSpace MARC exporter. As such, your local use case is to only export MARC for ArchivesSpace resources (i.e. collection-level) records, correct? JL On Wed, Dec 6, 2017 at 2:33 PM, Cyndi Shein wrote: > Hi All, > > I'm not sure exactly what functions or edits you're looking for, but you > may be able to adapt an existing plugin while you work on a long-term > solution for integrating ASpace with your LSP or ILS. UNLV Libraries uses > a plugin with check-boxes that allows us to customize the MARCXML fields > that ASpace exports. We use it to prepare records for import into OCLC > Connexion, reducing the manual editing we have to do. > > The plugin is on GitHub: https://github.com/l3mus/ArchivesSpace-authority- > project/tree/master/unlv_marc_exporter > > How we use the plugin and a screenshot of the staff interface is here: > http://elischolar.library.yale.edu/jcas/vol4/iss1/2/ (page 7-8 has the > explanation, page 16 has a screenshot). > > Cyndi Shein > UNLV Libraries Special Collections and Archives Technical Services > > > On Mon, Nov 27, 2017 at 11:47 AM, Caitlin Wells wrote: > >> I definitely support this! We're currently trying to figure out a way to >> translate the exported MARCXML from v. 1.5.4 for import into Aleph, and I'd >> love to hear what everyone else is doing. >> >> Caitlin >> -- >> Caitlin R. Wells >> Collection Services Librarian, Special Collections Library >> University of Michigan, Ann Arbor 48109 >> P: (734) 763-7901 >> >> On Mon, Nov 27, 2017 at 2:34 PM, Pyzynski, Susan C. < >> pyzynski at fas.harvard.edu> wrote: >> >>> Hi Jason, >>> >>> >>> >>> I also heartily second this idea. We are just at the beginning stages >>> of thinking about these exact questions here. At Houghton we need a record >>> in Aleph (soon to be Alma) for invoice paying and managing offsite >>> collections, to get a record in ASpace for accessioning/access, and have a >>> record in OCLC/Worldcat so our holdings are represented accurately. We are >>> trying to determine the most streamlined workflow(s) to achieve this, and >>> also figure out the maintenance these records in 3 different places. >>> >>> >>> >>> While repositories needs differ somewhat, it sounds like we are all >>> dealing with a fundamental issue, moving our metadata around in as >>> streamlined and efficient a way possible. >>> >>> >>> >>> All the best, >>> >>> Susan >>> >>> >>> >>> >>> >>> Susan C. Pyzynski >>> >>> Associate Librarian of Houghton Library for Technical Services >>> >>> Harvard Library >>> >>> Harvard University >>> >>> Cambridge MA 02138 >>> >>> pyzynski at fas.harvard.edu >>> >>> >>> >>> >>> >>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: >>> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Shelley >>> M. Hayreh >>> *Sent:* Monday, November 27, 2017 2:34 PM >>> *To:* Archivesspace Users Group >> alists.lyrasis.org> >>> *Subject:* Re: [Archivesspace_Users_Group] ILS and AS >>> >>> >>> >>> Yes, I strongly second that! Thank you Jason and all. >>> >>> >>> >>> On Mon, Nov 27, 2017 at 2:12 PM, Jason Loeffler >>> wrote: >>> >>> Great to hear so much interest and support in ILS integration. Unless >>> anyone has any other ideas, I propose putting out an open call to the >>> community to garner interest in forming a working group to: >>> >>> - share information >>> - flesh out use cases >>> - define workflows >>> - and, possibly, contribute to a specification for a plugin or core >>> enhancements, should the need arise. >>> >>> Does anyone want to second this approach? >>> >>> >>> >>> Jason Loeffler >>> >>> Technology Consultant | The American Academy in Rome >>> >>> Minor Science | Application Development & Metadata Strategy >>> >>> Brooklyn, New York >>> >>> jason at minorscience.com >>> >>> (347) 405-0826 >>> >>> minorscience (Skype) >>> >>> >>> >>> On Mon, Nov 27, 2017 at 1:49 PM, Christie Peterson >>> wrote: >>> >>> Hello, >>> >>> >>> >>> My medium-range plan is that once we turn on the ASpace PUI, we'll >>> include it in our library's main discovery layer as another area of the >>> "bento" results layout. >>> >>> >>> >>> However, I've been told that we need to keep producing MARC records >>> because otherwise our collections won't get into OCLC/WorldCat. If someone >>> has or dreams of a method that achieves this goal without the overhead of >>> MARC record creation and maintenance, I would love to hear more. >>> >>> >>> >>> Thanks, >>> >>> >>> >>> Christie Peterson >>> >>> >>> >>> On Mon, Nov 27, 2017 at 1:07 PM Sarah Horowitz >>> wrote: >>> >>> Hello, >>> >>> >>> >>> We are currently in the planning phases of a project to get all our >>> ASpace records into our ILS; implementation will begin this winter. There >>> has been a lot of data clean-up to make this possible; we're still trying >>> to come up with a work-around for the fact that beyond the first author, >>> the exporter throws everything into one 7xx field rather than separating >>> each of them out. >>> >>> >>> >>> This is a very important project for us, as many people are more likely >>> to discover our collections through our ILS/discovery layer than through >>> the ASpace site itself. I would love to see some support from the >>> Integrations team for projects like this. >>> >>> >>> >>> All the best, >>> >>> Sarah >>> >>> >>> >>> On Mon, Nov 27, 2017 at 12:57 PM, Jason Loeffler >>> wrote: >>> >>> Hi Shelley, >>> >>> >>> >>> This topic has been discussed recently in Integrations >>> meetings, >>> though, given team members current commitments, we temporarily dropped the >>> discussion. >>> >>> >>> >>> At the Academy's New York office, we're currently using a few custom >>> tools to map ArchivesSpace resource component JSON to MARC bibliographic >>> records. The latest version of ArchivesSpace has an OAI-PMH MARC responder. >>> If your ILS has an OAI-PMH client that may be worth exploring. Reconciling >>> subject and named authorities between the two systems is particularly >>> tricky. Happy to discuss this in more detail should the occasion arise. >>> >>> >>> >>> I'm curious to know whether other institutions are grappling with this >>> use case. If there's a critical mass of support, perhaps the Integrations >>> team should take this matter up in the future. >>> >>> >>> >>> Regards, Jason >>> >>> >>> Jason Loeffler >>> >>> Technology Consultant | The American Academy in Rome >>> >>> Minor Science | Application Development & Metadata Strategy >>> >>> Brooklyn, New York >>> >>> jason at minorscience.com >>> >>> (347) 405-0826 >>> >>> minorscience (Skype) >>> >>> >>> >>> On Mon, Nov 27, 2017 at 12:08 PM, Shelley M. Hayreh >>> wrote: >>> >>> Hello AS community, >>> >>> I'm serving on an implementation task-force reviewing how the adoption >>> of ArchivesSpace might change various workflows currently in place. A >>> couple of questions have arisen that I'm hoping the AS community can speak >>> to: >>> >>> >>> >>> -Is anyone in the community using ArchivesSpace to populate their >>> catalog/ILS? >>> >>> >>> >>> -Can AS contribute directly to OCLC or ArchivesGrid, therefore bypassing >>> the ILS? >>> >>> >>> >>> Thank you! >>> >>> >>> >>> Shelley >>> >>> -- >>> >>> Shelley Hayreh >>> >>> Avery Archivist >>> >>> Avery Architectural and Fine Arts Library >>> >>> 1172 Amsterdam Avenue MC0301 >>> >>> New York, NY 10027 >>> >>> 212-854-0760 <(212)%20854-0760> >>> >>> Web:http://library.columbia.edu/indiv/avery/da.html >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >>> >>> >>> >>> >>> -- >>> >>> Sarah Horowitz >>> >>> Curator of Rare Books and Manuscripts >>> Head of Quaker & Special Collections >>> >>> Haverford College Libraries >>> Haverford College >>> >>> 370 Lancaster Ave. >>> >>> Haverford, PA 19041 >>> (610) 896-2948 >>> >>> shorowitz at haverford.edu >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> -- >>> >>> ? >>> >>> Christie S. Peterson >>> >>> >>> >>> Head of Technical Services for Special Collections >>> >>> Smith College >>> >>> Northampton, Mass. >>> >>> 413-585-2996 <(413)%20585-2996> >>> >>> cpeterson at smith.edu >>> >>> >>> >>> pronouns: she/her/hers >>> >>> >>> _______________________________________________ >>> 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 >>> >>> >>> >>> >>> >>> -- >>> >>> Shelley Hayreh >>> >>> Avery Archivist >>> >>> Avery Architectural and Fine Arts Library >>> >>> 1172 Amsterdam Avenue MC0301 >>> >>> New York, NY 10027 >>> >>> 212-854-0760 <(212)%20854-0760> >>> >>> Web:http://library.columbia.edu/indiv/avery/da.html >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >> >> >> -- >> Caitlin R. Wells >> Collection Services Librarian, Special Collections Library >> University of Michigan, Ann Arbor 48109 >> P: (734) 763-7901 >> >> _______________________________________________ >> 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 cyndi.shein at unlv.edu Wed Dec 6 19:05:39 2017 From: cyndi.shein at unlv.edu (Cyndi Shein) Date: Wed, 6 Dec 2017 16:05:39 -0800 Subject: [Archivesspace_Users_Group] ILS and AS In-Reply-To: References: Message-ID: Hi Jason, Correct. We export MARCXML only for resource records at this time. Cyndi On Wed, Dec 6, 2017 at 1:30 PM, Jason Loeffler wrote: > Hi Cyndi, > > I just took a peek at the code. It looks the UNLV extends the > ArchivesSpace MARC exporter. As such, your local use case is to only export > MARC for ArchivesSpace resources (i.e. collection-level) records, correct? > > JL > > On Wed, Dec 6, 2017 at 2:33 PM, Cyndi Shein wrote: > >> Hi All, >> >> I'm not sure exactly what functions or edits you're looking for, but you >> may be able to adapt an existing plugin while you work on a long-term >> solution for integrating ASpace with your LSP or ILS. UNLV Libraries uses >> a plugin with check-boxes that allows us to customize the MARCXML fields >> that ASpace exports. We use it to prepare records for import into OCLC >> Connexion, reducing the manual editing we have to do. >> >> The plugin is on GitHub: https://github.com/l3mus/Archi >> vesSpace-authority-project/tree/master/unlv_marc_exporter >> >> How we use the plugin and a screenshot of the staff interface is here: >> http://elischolar.library.yale.edu/jcas/vol4/iss1/2/ (page 7-8 has the >> explanation, page 16 has a screenshot). >> >> Cyndi Shein >> UNLV Libraries Special Collections and Archives Technical Services >> >> >> On Mon, Nov 27, 2017 at 11:47 AM, Caitlin Wells wrote: >> >>> I definitely support this! We're currently trying to figure out a way to >>> translate the exported MARCXML from v. 1.5.4 for import into Aleph, and I'd >>> love to hear what everyone else is doing. >>> >>> Caitlin >>> -- >>> Caitlin R. Wells >>> Collection Services Librarian, Special Collections Library >>> University of Michigan, Ann Arbor 48109 >>> P: (734) 763-7901 >>> >>> On Mon, Nov 27, 2017 at 2:34 PM, Pyzynski, Susan C. < >>> pyzynski at fas.harvard.edu> wrote: >>> >>>> Hi Jason, >>>> >>>> >>>> >>>> I also heartily second this idea. We are just at the beginning stages >>>> of thinking about these exact questions here. At Houghton we need a record >>>> in Aleph (soon to be Alma) for invoice paying and managing offsite >>>> collections, to get a record in ASpace for accessioning/access, and have a >>>> record in OCLC/Worldcat so our holdings are represented accurately. We are >>>> trying to determine the most streamlined workflow(s) to achieve this, and >>>> also figure out the maintenance these records in 3 different places. >>>> >>>> >>>> >>>> While repositories needs differ somewhat, it sounds like we are all >>>> dealing with a fundamental issue, moving our metadata around in as >>>> streamlined and efficient a way possible. >>>> >>>> >>>> >>>> All the best, >>>> >>>> Susan >>>> >>>> >>>> >>>> >>>> >>>> Susan C. Pyzynski >>>> >>>> Associate Librarian of Houghton Library for Technical Services >>>> >>>> Harvard Library >>>> >>>> Harvard University >>>> >>>> Cambridge MA 02138 >>>> >>>> pyzynski at fas.harvard.edu >>>> >>>> >>>> >>>> >>>> >>>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org >>>> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] *On >>>> Behalf Of *Shelley M. Hayreh >>>> *Sent:* Monday, November 27, 2017 2:34 PM >>>> *To:* Archivesspace Users Group >>> alists.lyrasis.org> >>>> *Subject:* Re: [Archivesspace_Users_Group] ILS and AS >>>> >>>> >>>> >>>> Yes, I strongly second that! Thank you Jason and all. >>>> >>>> >>>> >>>> On Mon, Nov 27, 2017 at 2:12 PM, Jason Loeffler >>>> wrote: >>>> >>>> Great to hear so much interest and support in ILS integration. Unless >>>> anyone has any other ideas, I propose putting out an open call to the >>>> community to garner interest in forming a working group to: >>>> >>>> - share information >>>> - flesh out use cases >>>> - define workflows >>>> - and, possibly, contribute to a specification for a plugin or core >>>> enhancements, should the need arise. >>>> >>>> Does anyone want to second this approach? >>>> >>>> >>>> >>>> Jason Loeffler >>>> >>>> Technology Consultant | The American Academy in Rome >>>> >>>> Minor Science | Application Development & Metadata Strategy >>>> >>>> Brooklyn, New York >>>> >>>> jason at minorscience.com >>>> >>>> (347) 405-0826 >>>> >>>> minorscience (Skype) >>>> >>>> >>>> >>>> On Mon, Nov 27, 2017 at 1:49 PM, Christie Peterson >>>> wrote: >>>> >>>> Hello, >>>> >>>> >>>> >>>> My medium-range plan is that once we turn on the ASpace PUI, we'll >>>> include it in our library's main discovery layer as another area of the >>>> "bento" results layout. >>>> >>>> >>>> >>>> However, I've been told that we need to keep producing MARC records >>>> because otherwise our collections won't get into OCLC/WorldCat. If someone >>>> has or dreams of a method that achieves this goal without the overhead of >>>> MARC record creation and maintenance, I would love to hear more. >>>> >>>> >>>> >>>> Thanks, >>>> >>>> >>>> >>>> Christie Peterson >>>> >>>> >>>> >>>> On Mon, Nov 27, 2017 at 1:07 PM Sarah Horowitz >>>> wrote: >>>> >>>> Hello, >>>> >>>> >>>> >>>> We are currently in the planning phases of a project to get all our >>>> ASpace records into our ILS; implementation will begin this winter. There >>>> has been a lot of data clean-up to make this possible; we're still trying >>>> to come up with a work-around for the fact that beyond the first author, >>>> the exporter throws everything into one 7xx field rather than separating >>>> each of them out. >>>> >>>> >>>> >>>> This is a very important project for us, as many people are more likely >>>> to discover our collections through our ILS/discovery layer than through >>>> the ASpace site itself. I would love to see some support from the >>>> Integrations team for projects like this. >>>> >>>> >>>> >>>> All the best, >>>> >>>> Sarah >>>> >>>> >>>> >>>> On Mon, Nov 27, 2017 at 12:57 PM, Jason Loeffler >>>> wrote: >>>> >>>> Hi Shelley, >>>> >>>> >>>> >>>> This topic has been discussed recently in Integrations >>>> meetings, >>>> though, given team members current commitments, we temporarily dropped the >>>> discussion. >>>> >>>> >>>> >>>> At the Academy's New York office, we're currently using a few custom >>>> tools to map ArchivesSpace resource component JSON to MARC bibliographic >>>> records. The latest version of ArchivesSpace has an OAI-PMH MARC responder. >>>> If your ILS has an OAI-PMH client that may be worth exploring. Reconciling >>>> subject and named authorities between the two systems is particularly >>>> tricky. Happy to discuss this in more detail should the occasion arise. >>>> >>>> >>>> >>>> I'm curious to know whether other institutions are grappling with this >>>> use case. If there's a critical mass of support, perhaps the Integrations >>>> team should take this matter up in the future. >>>> >>>> >>>> >>>> Regards, Jason >>>> >>>> >>>> Jason Loeffler >>>> >>>> Technology Consultant | The American Academy in Rome >>>> >>>> Minor Science | Application Development & Metadata Strategy >>>> >>>> Brooklyn, New York >>>> >>>> jason at minorscience.com >>>> >>>> (347) 405-0826 >>>> >>>> minorscience (Skype) >>>> >>>> >>>> >>>> On Mon, Nov 27, 2017 at 12:08 PM, Shelley M. Hayreh < >>>> sh2309 at columbia.edu> wrote: >>>> >>>> Hello AS community, >>>> >>>> I'm serving on an implementation task-force reviewing how the adoption >>>> of ArchivesSpace might change various workflows currently in place. A >>>> couple of questions have arisen that I'm hoping the AS community can speak >>>> to: >>>> >>>> >>>> >>>> -Is anyone in the community using ArchivesSpace to populate their >>>> catalog/ILS? >>>> >>>> >>>> >>>> -Can AS contribute directly to OCLC or ArchivesGrid, therefore >>>> bypassing the ILS? >>>> >>>> >>>> >>>> Thank you! >>>> >>>> >>>> >>>> Shelley >>>> >>>> -- >>>> >>>> Shelley Hayreh >>>> >>>> Avery Archivist >>>> >>>> Avery Architectural and Fine Arts Library >>>> >>>> 1172 Amsterdam Avenue MC0301 >>>> >>>> New York, NY 10027 >>>> >>>> 212-854-0760 <(212)%20854-0760> >>>> >>>> Web:http://library.columbia.edu/indiv/avery/da.html >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Sarah Horowitz >>>> >>>> Curator of Rare Books and Manuscripts >>>> Head of Quaker & Special Collections >>>> >>>> Haverford College Libraries >>>> Haverford College >>>> >>>> 370 Lancaster Ave. >>>> >>>> Haverford, PA 19041 >>>> (610) 896-2948 >>>> >>>> shorowitz at haverford.edu >>>> >>>> _______________________________________________ >>>> Archivesspace_Users_Group mailing list >>>> Archivesspace_Users_Group at lyralists.lyrasis.org >>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>>> >>>> >>>> -- >>>> >>>> ? >>>> >>>> Christie S. Peterson >>>> >>>> >>>> >>>> Head of Technical Services for Special Collections >>>> >>>> Smith College >>>> >>>> Northampton, Mass. >>>> >>>> 413-585-2996 <(413)%20585-2996> >>>> >>>> cpeterson at smith.edu >>>> >>>> >>>> >>>> pronouns: she/her/hers >>>> >>>> >>>> _______________________________________________ >>>> 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 >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Shelley Hayreh >>>> >>>> Avery Archivist >>>> >>>> Avery Architectural and Fine Arts Library >>>> >>>> 1172 Amsterdam Avenue MC0301 >>>> >>>> New York, NY 10027 >>>> >>>> 212-854-0760 <(212)%20854-0760> >>>> >>>> Web:http://library.columbia.edu/indiv/avery/da.html >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Archivesspace_Users_Group mailing list >>>> Archivesspace_Users_Group at lyralists.lyrasis.org >>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>>> >>>> >>> >>> >>> -- >>> Caitlin R. Wells >>> Collection Services Librarian, Special Collections Library >>> University of Michigan, Ann Arbor 48109 >>> P: (734) 763-7901 >>> >>> _______________________________________________ >>> 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 >> >> > > _______________________________________________ > 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 than at guggenheim.org Thu Dec 7 12:00:16 2017 From: than at guggenheim.org (Tali Han) Date: Thu, 7 Dec 2017 17:00:16 +0000 Subject: [Archivesspace_Users_Group] DAO Notes in EAD Message-ID: Hello everyone, I'm having trouble with note tags in DAO records when downloading EAD finding aids. During our migration to ArchivesSpace a few years ago, the copyright notes in were mapped as "General Notes" in ArchivesSpace DAO records. However, I noticed that "General Notes" or any other note fields in the DAO record do not export as part of the EAD from ArchivesSpace. I saw the following ticket but I believe this is about the PUI not the EAD export: https://archivesspace.atlassian.net/browse/AR-1807 It is crucial that the "General Note" (or any other appropriate field you can recommend) show up in our EAD XML document-we do not use the PUI but instead download the EAD and map it directly onto our online finding aid on the museum website. We are using ArchivesSpace version 2.2.0 in Google Chrome browser. Also, in the future, can I map DAO fields to export as in EAD3? Is this a setting we can tweak in the backend? I would really appreciate it if I can get any input or suggestions! Thank you! Best, Tali Tali (Chiyong) Han Archivist and Manager, Library and Archives Solomon R. Guggenheim Museum One Liberty Plaza, 24th Floor New York, NY 10006 Phone 212 360 4232 than at guggenheim.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From laney.mcglohon at lyrasis.org Thu Dec 7 12:27:57 2017 From: laney.mcglohon at lyrasis.org (Laney McGlohon) Date: Thu, 7 Dec 2017 17:27:57 +0000 Subject: [Archivesspace_Users_Group] =?utf-8?q?Call_for_Testers_=E2=80=93_?= =?utf-8?q?Archon_to_ArchivesSpace_Migration?= Message-ID: <97FFF7AC-9E1D-437D-A01B-6D2782722C27@lyrasis.org> Call for Testers ? Archon to ArchivesSpace Migration The ArchivesSpace Program Team is looking for people who haven't yet migrated from Archon to ArchivesSpace to test updates to the Archon migration tool. We have developed a pre-release version of the Archon migration tool that migrates directly into ArchivesSpace version 2.x. If you?re interested, please email Laney at laney.mcglohon at lyrasis.org. Thanks, Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 818-442-7161 laneymcglohon Skype [ignature_584307941] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6693 bytes Desc: image001.jpg URL: From PGalligan at rockarch.org Thu Dec 7 14:13:13 2017 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Thu, 7 Dec 2017 19:13:13 +0000 Subject: [Archivesspace_Users_Group] ArchivesSnake Needs Your Help! Message-ID: <1D6EEB51-7D91-45DB-BD1E-4A894DBFB318@rockarch.org> Hi all, I?m heading up a collaborative project that we?re calling ArchivesSnake. ArchivesSnake is attempting to create a Python Library of scripts for working with the ArchivesSpace API. We?ve got a great team going, and we?re currently in the information gathering stage. If you?ve written a Python script to work with the AS API, we want to hear about it! We have a Github page: https://github.com/archivesspace-labs/ArchivesSnake, but you?ll need access to write to it. We?re currently taking the approach of adding links to scripts in github repos, and you can use the RAC (https://github.com/archivesspace-labs/ArchivesSnake/blob/master/RAC_links.md) or U of Albany (https://github.com/archivesspace-labs/ArchivesSnake/blob/master/ualbanyExample.md) links for examples. If your code is not in Github yet, but you?re willing to share it, we?ll put it up on ArchivesSnake. If you want to add links yourself, please email me and I?ll add you as a Github collaborator. If you lack the time to add links yourself, or you?re just baffled by Github, email me links to your code, and I can put them up myself. We?re closing the information-gathering stage on January 31st, 2018. Please contact us before then. After we?ve gathered sufficient examples, we?ll start grouping like functions and try to find the best way to do everything. After which point we?ll start work on creating the open Python library for all your needs. Let me know if you have any questions! Best, Patrick Galligan Rockefeller Archive Center Digital Archivist pgalligan at rockarch.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Thu Dec 7 15:39:26 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 7 Dec 2017 20:39:26 +0000 Subject: [Archivesspace_Users_Group] Importing containers from EAD In-Reply-To: References: Message-ID: Hi Marcie, What version of ArchivesSpace are you trying to import these EADs into? We found a bug beginning with 2.1.0 - when the older container code had been removed - where uniqueness of top containers was being enforced unnecessarily in EAD imports (see https://archivesspace.atlassian.net/browse/AR-1903). (The original issue was reported related to barcode uniqueness, but we found it went further than that.) This was corrected 2.2.1. If you try to import one of those EADs into the ArchivesSpace sandbox (http://sandbox.archivesspace.org), which is on 2.2.1, do you get the same issue? I do note that the error below suggests that you don't have both a type and indicator for your child container, but your example has those. (You don't have to have a child container in ArchivesSpace, but if you have one you have to have both of those data points.) If by some chance you have something where you don't have both the type and the indicator for a second-level container, correcting that should get rid of that kind of error. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Marcie Suzanne Farwell Sent: Wednesday, December 6, 2017 3:47 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Importing containers from EAD Hello all, We're in ASpace testing phase and I am attempting to import an EAD file. For our current system all I need for containers are: 1 2 1938 Abraham Lincoln Lives Again Allan, Anne New York, New York We know that for ASpace every box needs and id and in the past we encoded this as 1 for everything in Box 1 and that worked for the previous version of ASpace. Now it seems that the id number needs to be unique because I am getting this error: instances/0/sub_container/type_2 : container 2 requires both a type and indicator When I manually create a unique id, it imports just fine. We don't currently create unique ids for our boxes. Is there a way around this? How are other people creating unique ids for their containers? I don't see any questions on the list related to this so perhaps there is something simple I am overlooking. Thanks, Marcie Technical Services Archivist Division of Rare and Manuscript Collections 2B Kroch Library Cornell University Library Ithaca, NY 14853 607-255-3530 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From christine.dibella at lyrasis.org Thu Dec 7 15:46:09 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 7 Dec 2017 20:46:09 +0000 Subject: [Archivesspace_Users_Group] Digital Object Component Agents In-Reply-To: References: Message-ID: Hi Kate, Could you send me an example file for this issue (you can send it directly to christine.dibella at lyrasis.org)? It sounds like it's probably a bug, but there are limitations on CSV imports, so I'm just trying to get a better sense of what's going on here. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Herbert, Kate F Sent: Monday, December 4, 2017 4:03 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Digital Object Component Agents Hello All, We are just starting to add Digital Object with Components to our system. I was testing uploading then via the Digital Objects CSV, but have found that if the components have different agents then the parent the agents do not come through on the upload. Dates and file version information was not affected, we are not using subjects or notes. Thanks, Kate Herbert Cultural Heritage Data Specialist Shared position between the Maine State Archives, Maine State Library, & Maine State Museum (207) 712-9494 kate.f.herbert at maine.gov -------------- 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 christine.dibella at lyrasis.org Thu Dec 7 15:52:30 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 7 Dec 2017 20:52:30 +0000 Subject: [Archivesspace_Users_Group] Multi-factor authentication and ASpace In-Reply-To: References: Message-ID: Dear Olivia, ArchivesSpace supports LDAP (see http://archivesspace.github.io/archivesspace/user/configuring-ldap-authentication/) and recently Mark Cooper of LYRASIS developed a plugin for people interested in supporting some other kinds of authentication, which is available at https://github.com/lyrasis/aspace-oauth. We can help your tech people with either of those through a support ticket if you email us at ArchivesSpaceHome at lyrasis.org when you get to that point. We?ve also heard of institutions using or wanting to use things like Shibboleth (Mark Cooper?s plugin will also facilitate that) who have created their own plugins or custom deployments. People on the list would know more about those kinds of solutions if they?ve been implemented at their own institutions. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Olivia S Solis Sent: Monday, December 4, 2017 12:37 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Multi-factor authentication and ASpace Hello all, So we are setting up our web-hosted instance of ASpace. Thus far we have been utilizing a secure VM that we have to tunnel into while we migrate all of our legacy data into the system. We want to set up a two-factor authentication system in our web-hosted version of the staff interface as we have a lot of sensitive donor data in the system. Our the service provider for our web-hosted version is inquiring as to the technologies ASpace uses to support authentication... LDAP, OAuth, or PAM. From our provider, "if it supports PAM then I?m pretty confident we have an easy path to supporting two-factor authentication, if not we have to get into the OAuth realm which I don?t think is straightforward yet, but we have folks around here with more expertise." This is foreign territory for me so I'm directly quoting our contact. We've looked a bit at the documentation, but haven't found the information we are looking for. Does anyone have experience with multi-factor authentication and ASpace? If so, what mechanism did you use (technology and MFA provider)? Thanks! Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From harmeyna at purdue.edu Thu Dec 7 17:45:10 2017 From: harmeyna at purdue.edu (Harmeyer, Neal A) Date: Thu, 7 Dec 2017 22:45:10 +0000 Subject: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 Message-ID: <335e01911d5e406694be521877594c72@wppexc09.purdue.lcl> Hello all, I wonder if anyone else has experienced this issue? When selecting the Collections browse (/repositories/resources) from the header in the public interface, version 2.2.1, the system throws an error message that reads 'Your request could not be completed due to an unexpected error'. This only occurs for Collections browse; all other areas continue to load without issue-so our systems administrator isn't sure this could be cause by any web server configurations. I've been able to cause the failure on our dev site by repeatedly selecting the Collections browse over a short period of time. We didn't experience this in any past versions. A restart of the server removes the issue for a period of time but then it re-appears; there is nothing in our logs to point to a cause of the problem. Any suggestions would be helpful! Thank you, Neal -- Neal Harmeyer Digital Archivist Purdue Univesity Archives and Special Collections Purdue University Libraries harmeyna at purdue.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Thu Dec 7 18:03:40 2017 From: livsolis at utexas.edu (Olivia S Solis) Date: Thu, 7 Dec 2017 17:03:40 -0600 Subject: [Archivesspace_Users_Group] Multi-factor authentication and ASpace In-Reply-To: References: Message-ID: Thank you for the info! This is quite useful. I know that we would like to use Shibboleth, so this is good news. On Thu, Dec 7, 2017 at 2:52 PM, Christine Di Bella < christine.dibella at lyrasis.org> wrote: > Dear Olivia, > > > > ArchivesSpace supports LDAP (see http://archivesspace.github. > io/archivesspace/user/configuring-ldap-authentication/) and recently Mark > Cooper of LYRASIS developed a plugin for people interested in supporting > some other kinds of authentication, which is available at > https://github.com/lyrasis/aspace-oauth. We can help your tech people > with either of those through a support ticket if you email us at > ArchivesSpaceHome at lyrasis.org when you get to that point. > > > > We?ve also heard of institutions using or wanting to use things like > Shibboleth (Mark Cooper?s plugin will also facilitate that) who have > created their own plugins or custom deployments. People on the list would > know more about those kinds of solutions if they?ve been implemented at > their own institutions. > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 <(800)%20999-8558> > > 678-235-2905 <(678)%20235-2905> > > cdibella13 (Skype) > > > > [image: ASpaceOrgHomeMedium] > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Olivia > S Solis > *Sent:* Monday, December 4, 2017 12:37 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Multi-factor authentication and > ASpace > > > > Hello all, > > > > So we are setting up our web-hosted instance of ASpace. Thus far we have > been utilizing a secure VM that we have to tunnel into while we migrate all > of our legacy data into the system. We want to set up a two-factor > authentication system in our web-hosted version of the staff interface as > we have a lot of sensitive donor data in the system. Our the service > provider for our web-hosted version is inquiring as to the technologies > ASpace uses to support authentication... LDAP, OAuth, or PAM. From our > provider, "if it supports PAM then I?m pretty confident we have an easy > path to supporting two-factor authentication, if not we have to get into > the OAuth realm which I don?t think is straightforward yet, but we have > folks around here with more expertise." > > > > This is foreign territory for me so I'm directly quoting our contact. > We've looked a bit at the documentation, but haven't found the information > we are looking for. Does anyone have experience with multi-factor > authentication and ASpace? If so, what mechanism did you use (technology > and MFA provider)? > > > > Thanks! > > Olivia > > > > -- > > Olivia Solis, MSIS > > Metadata Coordinator > > Dolph Briscoe Center for American History > > The University of Texas at Austin > > 2300 Red River St. Stop D1100 > > Austin TX, 78712-1426 > > (512) 232-8013 <(512)%20232-8013> > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: not available URL: From christine.dibella at lyrasis.org Fri Dec 8 08:28:53 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 8 Dec 2017 13:28:53 +0000 Subject: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 Message-ID: Hi Neal, Do you by chance have a collection that has the circumstance described in this JIRA ticket: https://archivesspace.atlassian.net/browse/AR-1938 (A diacritic wrapped in a tag.) Most likely it would be in the scope and contents note or abstract field if the error is happening from the collection browse. If so, and that record appears on the first page of your all collection browse, that may be what's causing the issue. You would also get a "We're sorry something went wrong" when trying to view that particular record or on a search that includes that particular record. If you have multiple repositories, that would also explain why a collection browse that's scoped to another repository would not yield that issue. This is a reported issue for all 2.1 and 2.2 versions. The workaround for now would be to remove either the tagging or the diacritic, but we hope to fix this issue for a future release. If you don't have that circumstance, we'll need to delve into this more deeply. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Thursday, December 7, 2017 5:45 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 Hello all, I wonder if anyone else has experienced this issue? When selecting the Collections browse (/repositories/resources) from the header in the public interface, version 2.2.1, the system throws an error message that reads 'Your request could not be completed due to an unexpected error'. This only occurs for Collections browse; all other areas continue to load without issue-so our systems administrator isn't sure this could be cause by any web server configurations. I've been able to cause the failure on our dev site by repeatedly selecting the Collections browse over a short period of time. We didn't experience this in any past versions. A restart of the server removes the issue for a period of time but then it re-appears; there is nothing in our logs to point to a cause of the problem. Any suggestions would be helpful! Thank you, Neal -- Neal Harmeyer Digital Archivist Purdue Univesity Archives and Special Collections Purdue University Libraries harmeyna at purdue.edu -------------- 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 lc7 at williams.edu Fri Dec 8 08:42:13 2017 From: lc7 at williams.edu (Conathan, Lisa) Date: Fri, 8 Dec 2017 08:42:13 -0500 Subject: [Archivesspace_Users_Group] Components not displaying in one of our repositories In-Reply-To: References: Message-ID: Hi everyone, I wanted to update the list to let people know that we solved this issue using the HM data checker plugin at https://github.com/hudmol/asck. It identified an object that had an error, that apparently was causing the indexing to get hung up. We were able to delete the object directly from the database (since the error prevented us from doing so in the staff UI). The error occurred when a staff member attempted to transfer the object from one collection to another (in another repository) using the staff UI. We don't plan on trying to replicate the error, but this was a very informative process to go through. Thanks to everyone on the list who so generously helped us troubleshoot this issue! Lisa +++++++++++++++++++++ Lisa Conathan Head of Special Collections Williams College Libraries 413-597-2930 On Mon, Nov 6, 2017 at 1:32 PM, Custer, Mark wrote: > Hi Lisa, > > > > I?ve no clue what could be causing this, but others have reported the > issue as well. Hopefully the root cause of the issue can be identified > with enough eyes on the problem. So far, I haven?t seen this happen in > Yale?s TEST PUI instance (on 2.1.2) or on our DEV instance (on version > 20171105-1021). > > > > Chris Fitzpatrick started a thread on the Apace Google Groups about this, > though, which might be helpful: https://groups.google.com/ > forum/#!topic/archivesspace/PhgUjukaNzQ > > > > My first inclination would be that things are stuck in an indexing loop > (e.g. https://groups.google.com/d/msg/archivesspace/mRH_eCDHpwE/ > 2fjb5EAfAgAJ), but that could be completely wrong. In any event, can you > ask someone who has database access to run this query: > > > > *select* * *from* archival_object *where* root_record_id *is* *null*; > > > > If they get any results that way, that would cause an issue. > > > > As for whey it would happen in just one repository, I believe that once > the indexer gets stuck (and it goes through the record types one repository > at a time, I think) then it just won?t ever get to the rest of the record > types in that particular repository. Some of the archival objects in this > repository are indeed being indexed (e.g. http://archivesspace.williams. > edu:8081/repositories/4/archival_objects/10484), but not completely, > since this archival object doesn?t even know which collection it?s supposed > to be part of. > > > > Mark > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Conathan, > Lisa > *Sent:* Monday, 06 November, 2017 1:12 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Components not displaying in one > of our repositories > > > > Hi everyone, > > > > Williams College is running 2.2.0 and we have two repositories publishing > to the PUI > . > One repository is displaying resource records correctly, and the other > > is displaying only collection-level information (no collection > organization, no container list on the right side of the screen). > Components also do not display in the container inventory. We've double > checked that everything is published, reindexed, and rebooted. We > experienced this previously, and then the problem resolved with one of the > patches, and now has re-appeared. Anyone know why we might be having this > problem with just one of our repositories and what we might try to address > it? > > > > Lisa > > > +++++++++++++++++++++ > Lisa Conathan > Head of Special Collections > Williams College Libraries > 413-597-2930 <(413)%20597-2930> > > _______________________________________________ > 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 ltdawson at hawaii.edu Fri Dec 8 13:13:06 2017 From: ltdawson at hawaii.edu (Leilani Dawson) Date: Fri, 8 Dec 2017 08:13:06 -1000 Subject: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 In-Reply-To: References: Message-ID: Hi Christine, I see this is listed in JIRA as a minor issue, but is there any guess for when it might be addressed? Certain Hawaiian-language diacritics "break" screen readers, so in order to satisfy both accessibility requirements and UH's mandate to be a Hawaiian place of learning, the Library has started wrapping these diacritics in tags with aria-label attributes. (E.g.: Hawaiʻi) ArchivesSpace 2.1 and 2.2 not being able to handle wrapped diacritics might preclude us from going forward with using the public user interface and/or upgrading to 2.x. until the fix is in. -Leilani. - - Leilani Dawson Manuscript Collections Archivist University Archives & Manuscripts Department University of Hawaii at Manoa Library 2550 McCarthy Mall, Honolulu, HI 96822 ltdawson at hawaii.edu On Fri, Dec 8, 2017 at 3:28 AM, Christine Di Bella < christine.dibella at lyrasis.org> wrote: > Hi Neal, > > > > Do you by chance have a collection that has the circumstance described in > this JIRA ticket: https://archivesspace.atlassian.net/browse/AR-1938 (A > diacritic wrapped in a tag.) Most likely it would be in the scope and > contents note or abstract field if the error is happening from the > collection browse. > > > > If so, and that record appears on the first page of your all collection > browse, that may be what?s causing the issue. You would also get a ?We?re > sorry something went wrong? when trying to view that particular record or > on a search that includes that particular record. If you have multiple > repositories, that would also explain why a collection browse that?s scoped > to another repository would not yield that issue. > > > > This is a reported issue for all 2.1 and 2.2 versions. The workaround for > now would be to remove either the tagging or the diacritic, but we hope to > fix this issue for a future release. > > > > If you don?t have that circumstance, we?ll need to delve into this more > deeply. > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 <(800)%20999-8558> > > 678-235-2905 <(678)%20235-2905> > > cdibella13 (Skype) > > > > [image: ASpaceOrgHomeMedium] > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Harmeyer, > Neal A > *Sent:* Thursday, December 7, 2017 5:45 PM > *To:* Archivesspace Users Group alists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Collections Browse Error in Public > Interface, v2.2.1 > > > > Hello all, > > > > I wonder if anyone else has experienced this issue? > > > > When selecting the Collections browse (/repositories/resources) from the > header in the public interface, version 2.2.1, the system throws an error > message that reads 'Your request could not be completed due to an > unexpected error'. This only occurs for Collections browse; all other areas > continue to load without issue?so our systems administrator isn?t sure this > could be cause by any web server configurations. I?ve been able to cause > the failure on our dev site by repeatedly selecting the Collections browse > over a short period of time. > > > > We didn?t experience this in any past versions. A restart of the server > removes the issue for a period of time but then it re-appears; there is > nothing in our logs to point to a cause of the problem. > > > > Any suggestions would be helpful! > > > > Thank you, > > Neal > > > > -- > > Neal Harmeyer > > Digital Archivist > > Purdue Univesity Archives and Special Collections > > Purdue University Libraries > > harmeyna at purdue.edu > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: not available URL: From christine.dibella at lyrasis.org Fri Dec 8 14:12:12 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 8 Dec 2017 19:12:12 +0000 Subject: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 In-Reply-To: References: Message-ID: Hi Leilani, Thanks for making me dig into this a bit more and for explaining one of the reasons tagging around a diacritic may be especially necessary. For your use case, is your tagging always like your example? If so, there?s sanitizer for HTML in the PUI that allows this kind of tagging to sail through just fine. It is XML tags like that we?re seeing this bug on. There was some accessibility work that went into the development of the new PUI, but it would be good to know that what makes this kind of tagging work in the PUI doesn?t also cause the same issue for screen readers that is the reason for you wrapping the text originally. Can you test this out locally or upload a finding aid to http://test.archivesspace.org and try it out? Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Leilani Dawson Sent: Friday, December 8, 2017 1:13 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 Hi Christine, I see this is listed in JIRA as a minor issue, but is there any guess for when it might be addressed? Certain Hawaiian-language diacritics "break" screen readers, so in order to satisfy both accessibility requirements and UH's mandate to be a Hawaiian place of learning, the Library has started wrapping these diacritics in tags with aria-label attributes. (E.g.: Hawaiʻi) ArchivesSpace 2.1 and 2.2 not being able to handle wrapped diacritics might preclude us from going forward with using the public user interface and/or upgrading to 2.x. until the fix is in. -Leilani. - - Leilani Dawson Manuscript Collections Archivist University Archives & Manuscripts Department University of Hawaii at Manoa Library 2550 McCarthy Mall, Honolulu, HI 96822 ltdawson at hawaii.edu On Fri, Dec 8, 2017 at 3:28 AM, Christine Di Bella > wrote: Hi Neal, Do you by chance have a collection that has the circumstance described in this JIRA ticket: https://archivesspace.atlassian.net/browse/AR-1938 (A diacritic wrapped in a tag.) Most likely it would be in the scope and contents note or abstract field if the error is happening from the collection browse. If so, and that record appears on the first page of your all collection browse, that may be what?s causing the issue. You would also get a ?We?re sorry something went wrong? when trying to view that particular record or on a search that includes that particular record. If you have multiple repositories, that would also explain why a collection browse that?s scoped to another repository would not yield that issue. This is a reported issue for all 2.1 and 2.2 versions. The workaround for now would be to remove either the tagging or the diacritic, but we hope to fix this issue for a future release. If you don?t have that circumstance, we?ll need to delve into this more deeply. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A Sent: Thursday, December 7, 2017 5:45 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 Hello all, I wonder if anyone else has experienced this issue? When selecting the Collections browse (/repositories/resources) from the header in the public interface, version 2.2.1, the system throws an error message that reads 'Your request could not be completed due to an unexpected error'. This only occurs for Collections browse; all other areas continue to load without issue?so our systems administrator isn?t sure this could be cause by any web server configurations. I?ve been able to cause the failure on our dev site by repeatedly selecting the Collections browse over a short period of time. We didn?t experience this in any past versions. A restart of the server removes the issue for a period of time but then it re-appears; there is nothing in our logs to point to a cause of the problem. Any suggestions would be helpful! Thank you, Neal -- Neal Harmeyer Digital Archivist Purdue Univesity Archives and Special Collections Purdue University Libraries harmeyna at purdue.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 6608 bytes Desc: image005.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.jpg Type: image/jpeg Size: 6608 bytes Desc: image006.jpg URL: From ltdawson at hawaii.edu Fri Dec 8 15:45:37 2017 From: ltdawson at hawaii.edu (Leilani Dawson) Date: Fri, 8 Dec 2017 10:45:37 -1000 Subject: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 In-Reply-To: References: Message-ID: Yes, all of our accessibility-wrapped diacritics are in html tags. (Occasionally we have notes where words labeled with alternate text are nested within EAD elements such as or <persname> or the like, but those EAD elements are not as critical for us as the <span> with aria-label attribute.) I'll ask our IT folks to put together a 2.2 test instance so I can upload a finding aid with diacritics and see whether the new PUI handles it in a screen-reader-friendly manner. Thanks, -Leilani On Fri, Dec 8, 2017 at 9:12 AM, Christine Di Bella < christine.dibella at lyrasis.org> wrote: > Hi Leilani, > > > > Thanks for making me dig into this a bit more and for explaining one of > the reasons tagging around a diacritic may be especially necessary. For > your use case, is your tagging always like your example? If so, there?s > sanitizer for HTML in the PUI that allows this kind of tagging to sail > through just fine. It is XML tags like <emph> that we?re seeing this bug > on. > > > > There was some accessibility work that went into the development of the > new PUI, but it would be good to know that what makes this kind of tagging > work in the PUI doesn?t also cause the same issue for screen readers that > is the reason for you wrapping the text originally. Can you test this out > locally or upload a finding aid to http://test.archivesspace.org and try > it out? > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 <(800)%20999-8558> > > 678-235-2905 <(678)%20235-2905> > > cdibella13 (Skype) > > > > [image: ASpaceOrgHomeMedium] > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Leilani > Dawson > *Sent:* Friday, December 8, 2017 1:13 PM > *To:* Archivesspace Users Group <archivesspace_users_group@ > lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Collections Browse Error in > Public Interface, v2.2.1 > > > > Hi Christine, > > I see this is listed in JIRA as a minor issue, but is there any guess for > when it might be addressed? > > Certain Hawaiian-language diacritics "break" screen readers, so in order > to satisfy both accessibility requirements and UH's mandate to be a > Hawaiian place of learning, the Library has started wrapping these > diacritics in <span> tags with aria-label attributes. (E.g.: <span > aria-label="Hawaii">Hawaiʻi</span>) ArchivesSpace 2.1 and 2.2 not > being able to handle wrapped diacritics might preclude us from going > forward with using the public user interface and/or upgrading to 2.x. until > the fix is in. > > > -Leilani. > > - - > > Leilani Dawson > > Manuscript Collections Archivist > > University Archives & Manuscripts Department > > University of Hawaii at Manoa Library > > 2550 McCarthy Mall, Honolulu, HI 96822 > > ltdawson at hawaii.edu > > > > On Fri, Dec 8, 2017 at 3:28 AM, Christine Di Bella < > christine.dibella at lyrasis.org> wrote: > > Hi Neal, > > > > Do you by chance have a collection that has the circumstance described in > this JIRA ticket: https://archivesspace.atlassian.net/browse/AR-1938 (A > diacritic wrapped in a tag.) Most likely it would be in the scope and > contents note or abstract field if the error is happening from the > collection browse. > > > > If so, and that record appears on the first page of your all collection > browse, that may be what?s causing the issue. You would also get a ?We?re > sorry something went wrong? when trying to view that particular record or > on a search that includes that particular record. If you have multiple > repositories, that would also explain why a collection browse that?s scoped > to another repository would not yield that issue. > > > > This is a reported issue for all 2.1 and 2.2 versions. The workaround for > now would be to remove either the tagging or the diacritic, but we hope to > fix this issue for a future release. > > > > If you don?t have that circumstance, we?ll need to delve into this more > deeply. > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 <(800)%20999-8558> > > 678-235-2905 <(678)%20235-2905> > > cdibella13 (Skype) > > > > [image: ASpaceOrgHomeMedium] > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Harmeyer, > Neal A > *Sent:* Thursday, December 7, 2017 5:45 PM > *To:* Archivesspace Users Group <archivesspace_users_group@ > lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Collections Browse Error in Public > Interface, v2.2.1 > > > > Hello all, > > > > I wonder if anyone else has experienced this issue? > > > > When selecting the Collections browse (/repositories/resources) from the > header in the public interface, version 2.2.1, the system throws an error > message that reads 'Your request could not be completed due to an > unexpected error'. This only occurs for Collections browse; all other areas > continue to load without issue?so our systems administrator isn?t sure this > could be cause by any web server configurations. I?ve been able to cause > the failure on our dev site by repeatedly selecting the Collections browse > over a short period of time. > > > > We didn?t experience this in any past versions. A restart of the server > removes the issue for a period of time but then it re-appears; there is > nothing in our logs to point to a cause of the problem. > > > > Any suggestions would be helpful! > > > > Thank you, > > Neal > > > > -- > > Neal Harmeyer > > Digital Archivist > > Purdue Univesity Archives and Special Collections > > Purdue University Libraries > > harmeyna at purdue.edu > > > > > _______________________________________________ > 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: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171208/ef2d47dc/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 6608 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171208/ef2d47dc/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.jpg Type: image/jpeg Size: 6608 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171208/ef2d47dc/attachment-0001.jpg> From Christine.Kim at lyrasis.org Fri Dec 8 18:44:39 2017 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Fri, 8 Dec 2017 23:44:39 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: Varying Approaches to Testing ASpace Pre-Releases - Dec 14 Message-ID: <MWHPR08MB249557CCB19C0A315A816DF5F5300@MWHPR08MB2495.namprd08.prod.outlook.com> Unit Testing and the Testing Sub-Team: Varying Approaches to Testing ArchivesSpace Pre-Releases When: Thursday, December 14, 2017 Time: 1:00 p.m. - 2:00 p.m. EST (10:00 a.m. - 11:00 a.m. PST) Where: Webinar at http://lyrasis.adobeconnect.com/rai0bzfc3h54/ Dial-in only option: 888-354-0094 - Access code is 731627 No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. The webinar will be recorded and available for viewing at a later date. Webinar description: Before we make any release or update widely available, we perform tests in every nook and cranny in ArchivesSpace. Testing applications plays an essential role in our workflow to ensure the application is growing in the right direction, and not breaking already functional working components. Join us on December 14 as we explore why testing is vital to our growth and process, as well as the testing methods our community implements to ensure new features and fixes are improvements. Alex and Miloche will share their experiences and insights on testing pre-release versions of ArchivesSpace. Please feel free to bring any questions you have. Presenters: Alexander Duryee (Metadata Archivist, New York Public Library) has been a major contributor in the ArchivesSpace Core Committers Group. He has taken a lead role to delve into test automation for ArchivesSpace releases. Alex will share how he runs unit testing so certain components of each release can be tested through automated commands. Miloche Kottman (Head of Cataloging & Archival Processing, University of Kansas) is leading the Testing sub-team for ArchivesSpace. Once a pre-release version is available, Miloche and the Testing sub-team implement a workflow to run through basic functions inside ArchivesSpace, employing the diverse perspectives of archivists. Miloche will share insight into how testing is carried out by the team before each release finally becomes available. Who should attend: Everyone interested in going behind the scenes of the application and learning how ArchivesSpace tests new features before releasing new versions. Questions? Please contact Kim at christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171208/80d0037d/attachment.html> From jjones at smith.edu Mon Dec 11 10:06:38 2017 From: jjones at smith.edu (Jasmine Jones) Date: Mon, 11 Dec 2017 10:06:38 -0500 Subject: [Archivesspace_Users_Group] ArchivesSpace user manual error page Message-ID: <CADExw5=TOdDKBXtfbT62MhfJrAXWMBkbasiJFG3UEi37pdSV3Q@mail.gmail.com> Hi all: I'm having trouble with the ArchivesSpace user manual this morning and get directed to an error page (http://docs.archivesspace.org/Default.htm and screenshot attached). Has anyone else had issues? Thank you, Jasmine Jones [image: Inline image 1] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/f69ca727/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: aspace-user-manual-error-page-screenshot.png Type: image/png Size: 409680 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/f69ca727/attachment.png> From dave_mayo at harvard.edu Mon Dec 11 10:14:44 2017 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Mon, 11 Dec 2017 15:14:44 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace user manual error page In-Reply-To: <CADExw5=TOdDKBXtfbT62MhfJrAXWMBkbasiJFG3UEi37pdSV3Q@mail.gmail.com> References: <CADExw5=TOdDKBXtfbT62MhfJrAXWMBkbasiJFG3UEi37pdSV3Q@mail.gmail.com> Message-ID: <995C0A49-F5B4-4134-8E36-7EA6B4078C21@harvard.edu> I can confirm that I?m getting the same thing. - Dave Mayo From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jasmine Jones <jjones at smith.edu> Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> Date: Monday, December 11, 2017 at 10:07 AM To: "archivesspace_users_group at lyralists.lyrasis.org" <archivesspace_users_group at lyralists.lyrasis.org> Subject: [Archivesspace_Users_Group] ArchivesSpace user manual error page Hi all: I'm having trouble with the ArchivesSpace user manual this morning and get directed to an error page (http://docs.archivesspace.org/Default.htm<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.archivesspace.org_Default.htm&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=Uwkulyf5Wv3_OV4RVr9ZeAak82IKUfn4c2nGpZ6RRy4&s=DmQELUqxVlsaOSW0SYFX6TjQFAgffB6bXn_YmXU29m0&e=> and screenshot attached). Has anyone else had issues? Thank you, Jasmine Jones [nline image 1] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/87191788/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 278340 bytes Desc: image002.png URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/87191788/attachment-0001.png> From Christine.Kim at lyrasis.org Mon Dec 11 10:18:11 2017 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Mon, 11 Dec 2017 15:18:11 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace user manual error page In-Reply-To: <995C0A49-F5B4-4134-8E36-7EA6B4078C21@harvard.edu> References: <CADExw5=TOdDKBXtfbT62MhfJrAXWMBkbasiJFG3UEi37pdSV3Q@mail.gmail.com> <995C0A49-F5B4-4134-8E36-7EA6B4078C21@harvard.edu> Message-ID: <MWHPR08MB24959E52E7B20C1D47239E65F5370@MWHPR08MB2495.namprd08.prod.outlook.com> I?m receiving the same. I will submit a support ticket for this. Thanks for reporting! Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org> 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mayo, Dave Sent: Monday, December 11, 2017 7:15 AM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> Subject: Re: [Archivesspace_Users_Group] ArchivesSpace user manual error page I can confirm that I?m getting the same thing. - Dave Mayo From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Jasmine Jones <jjones at smith.edu<mailto:jjones at smith.edu>> Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>> Date: Monday, December 11, 2017 at 10:07 AM To: "archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>" <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>> Subject: [Archivesspace_Users_Group] ArchivesSpace user manual error page Hi all: I'm having trouble with the ArchivesSpace user manual this morning and get directed to an error page (http://docs.archivesspace.org/Default.htm<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.archivesspace.org_Default.htm&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=Uwkulyf5Wv3_OV4RVr9ZeAak82IKUfn4c2nGpZ6RRy4&s=DmQELUqxVlsaOSW0SYFX6TjQFAgffB6bXn_YmXU29m0&e=> and screenshot attached). Has anyone else had issues? Thank you, Jasmine Jones [nline image 1] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/37c61133/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 278340 bytes Desc: image001.png URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/37c61133/attachment.png> From Christine.Kim at lyrasis.org Mon Dec 11 10:35:33 2017 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Mon, 11 Dec 2017 15:35:33 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace user manual error page In-Reply-To: <MWHPR08MB24959E52E7B20C1D47239E65F5370@MWHPR08MB2495.namprd08.prod.outlook.com> References: <CADExw5=TOdDKBXtfbT62MhfJrAXWMBkbasiJFG3UEi37pdSV3Q@mail.gmail.com> <995C0A49-F5B4-4134-8E36-7EA6B4078C21@harvard.edu> <MWHPR08MB24959E52E7B20C1D47239E65F5370@MWHPR08MB2495.namprd08.prod.outlook.com> Message-ID: <MWHPR08MB249578F47CA23D152809C1A3F5370@MWHPR08MB2495.namprd08.prod.outlook.com> Hi all, The problem has been resolved. For the info curious ? it seems there was a problem with bad bots or something hitting it this morning. Thanks so much for reporting, and have a great Monday! Best wishes, Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org> 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Kim Sent: Monday, December 11, 2017 7:18 AM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> Subject: Re: [Archivesspace_Users_Group] ArchivesSpace user manual error page I?m receiving the same. I will submit a support ticket for this. Thanks for reporting! Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org> 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mayo, Dave Sent: Monday, December 11, 2017 7:15 AM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>> Subject: Re: [Archivesspace_Users_Group] ArchivesSpace user manual error page I can confirm that I?m getting the same thing. - Dave Mayo From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Jasmine Jones <jjones at smith.edu<mailto:jjones at smith.edu>> Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>> Date: Monday, December 11, 2017 at 10:07 AM To: "archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>" <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>> Subject: [Archivesspace_Users_Group] ArchivesSpace user manual error page Hi all: I'm having trouble with the ArchivesSpace user manual this morning and get directed to an error page (http://docs.archivesspace.org/Default.htm<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.archivesspace.org_Default.htm&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=Uwkulyf5Wv3_OV4RVr9ZeAak82IKUfn4c2nGpZ6RRy4&s=DmQELUqxVlsaOSW0SYFX6TjQFAgffB6bXn_YmXU29m0&e=> and screenshot attached). Has anyone else had issues? Thank you, Jasmine Jones [nline image 1] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/9ccc17bf/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 278340 bytes Desc: image001.png URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/9ccc17bf/attachment.png> From mark.custer at yale.edu Mon Dec 11 10:58:06 2017 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 11 Dec 2017 15:58:06 +0000 Subject: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 In-Reply-To: <CADGuORFhbO1HYR1beZzHie2WJYAK5h_qqwMo7uegTATJ9F997g@mail.gmail.com> References: <CY1PR08MB119726445B4DB7BBEB4456DCF1300@CY1PR08MB1197.namprd08.prod.outlook.com> <CADGuORFSLn4749anfxVQmAkjrgt94Kf06RhLQvBBGPxi2FdXrw@mail.gmail.com> <CY1PR08MB11971CF15949B3C0CF7A10DDF1300@CY1PR08MB1197.namprd08.prod.outlook.com>, <CADGuORFhbO1HYR1beZzHie2WJYAK5h_qqwMo7uegTATJ9F997g@mail.gmail.com> Message-ID: <BN3PR08MB1303914D77E761964B6D5E538C370@BN3PR08MB1303.namprd08.prod.outlook.com> Leilani, Could you attach an example EAD file? I'm curious what happens when Unicode characters are used in place of the character entities. I'm wondering if the issue might simply be that the font used doesn't include italic characters for the character entities that are tagged as italic (as an aside, what fonts do you use outside of ArchivesSpace?). Either way, it would be nice to add these examples to some test scripts for ArchivesSpace. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Leilani Dawson <ltdawson at hawaii.edu> Sent: Friday, December 8, 2017 3:45 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 Yes, all of our accessibility-wrapped diacritics are in html tags. (Occasionally we have notes where words labeled with alternate text are nested within EAD elements such as <title> or <persname> or the like, but those EAD elements are not as critical for us as the <span> with aria-label attribute.) I'll ask our IT folks to put together a 2.2 test instance so I can upload a finding aid with diacritics and see whether the new PUI handles it in a screen-reader-friendly manner. Thanks, -Leilani On Fri, Dec 8, 2017 at 9:12 AM, Christine Di Bella <christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>> wrote: Hi Leilani, Thanks for making me dig into this a bit more and for explaining one of the reasons tagging around a diacritic may be especially necessary. For your use case, is your tagging always like your example? If so, there?s sanitizer for HTML in the PUI that allows this kind of tagging to sail through just fine. It is XML tags like <emph> that we?re seeing this bug on. There was some accessibility work that went into the development of the new PUI, but it would be good to know that what makes this kind of tagging work in the PUI doesn?t also cause the same issue for screen readers that is the reason for you wrapping the text originally. Can you test this out locally or upload a finding aid to http://test.archivesspace.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=ojcyFCMoM3zS9hpwYf4E7AnqB96za3sLtX6PZ20VkFM&e=> and try it out? Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org> 800.999.8558 x2905<tel:(800)%20999-8558> 678-235-2905<tel:(678)%20235-2905> cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Leilani Dawson Sent: Friday, December 8, 2017 1:13 PM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>> Subject: Re: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 Hi Christine, I see this is listed in JIRA as a minor issue, but is there any guess for when it might be addressed? Certain Hawaiian-language diacritics "break" screen readers, so in order to satisfy both accessibility requirements and UH's mandate to be a Hawaiian place of learning, the Library has started wrapping these diacritics in <span> tags with aria-label attributes. (E.g.: <span aria-label="Hawaii">Hawaiʻi</span>) ArchivesSpace 2.1 and 2.2 not being able to handle wrapped diacritics might preclude us from going forward with using the public user interface and/or upgrading to 2.x. until the fix is in. -Leilani. - - Leilani Dawson Manuscript Collections Archivist University Archives & Manuscripts Department University of Hawaii at Manoa Library 2550 McCarthy Mall, Honolulu, HI 96822 ltdawson at hawaii.edu<mailto:ltdawson at hawaii.edu> On Fri, Dec 8, 2017 at 3:28 AM, Christine Di Bella <christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>> wrote: Hi Neal, Do you by chance have a collection that has the circumstance described in this JIRA ticket: https://archivesspace.atlassian.net/browse/AR-1938<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1938&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=VMpZ3HzcFod2VlOa_Q5TAqIkbX5K9NFmJ-9RGxTgJRI&e=> (A diacritic wrapped in a tag.) Most likely it would be in the scope and contents note or abstract field if the error is happening from the collection browse. If so, and that record appears on the first page of your all collection browse, that may be what?s causing the issue. You would also get a ?We?re sorry something went wrong? when trying to view that particular record or on a search that includes that particular record. If you have multiple repositories, that would also explain why a collection browse that?s scoped to another repository would not yield that issue. This is a reported issue for all 2.1 and 2.2 versions. The workaround for now would be to remove either the tagging or the diacritic, but we hope to fix this issue for a future release. If you don?t have that circumstance, we?ll need to delve into this more deeply. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org> 800.999.8558 x2905<tel:(800)%20999-8558> 678-235-2905<tel:(678)%20235-2905> cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Harmeyer, Neal A Sent: Thursday, December 7, 2017 5:45 PM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>> Subject: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 Hello all, I wonder if anyone else has experienced this issue? When selecting the Collections browse (/repositories/resources) from the header in the public interface, version 2.2.1, the system throws an error message that reads 'Your request could not be completed due to an unexpected error'. This only occurs for Collections browse; all other areas continue to load without issue?so our systems administrator isn?t sure this could be cause by any web server configurations. I?ve been able to cause the failure on our dev site by repeatedly selecting the Collections browse over a short period of time. We didn?t experience this in any past versions. A restart of the server removes the issue for a period of time but then it re-appears; there is nothing in our logs to point to a cause of the problem. Any suggestions would be helpful! Thank you, Neal -- Neal Harmeyer Digital Archivist Purdue Univesity Archives and Special Collections Purdue University Libraries harmeyna at purdue.edu<mailto:harmeyna at purdue.edu> _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=mcku_27mMAV6rVbPS8IwL0Tx_W-qI7NJvab5eSZgQuU&e=> _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=mcku_27mMAV6rVbPS8IwL0Tx_W-qI7NJvab5eSZgQuU&e=> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/375fb341/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 6608 bytes Desc: image005.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/375fb341/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.jpg Type: image/jpeg Size: 6608 bytes Desc: image006.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/375fb341/attachment-0001.jpg> From ltdawson at hawaii.edu Mon Dec 11 14:02:37 2017 From: ltdawson at hawaii.edu (Leilani Dawson) Date: Mon, 11 Dec 2017 09:02:37 -1000 Subject: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1 In-Reply-To: <BN3PR08MB1303914D77E761964B6D5E538C370@BN3PR08MB1303.namprd08.prod.outlook.com> References: <CY1PR08MB119726445B4DB7BBEB4456DCF1300@CY1PR08MB1197.namprd08.prod.outlook.com> <CADGuORFSLn4749anfxVQmAkjrgt94Kf06RhLQvBBGPxi2FdXrw@mail.gmail.com> <CY1PR08MB11971CF15949B3C0CF7A10DDF1300@CY1PR08MB1197.namprd08.prod.outlook.com> <CADGuORFhbO1HYR1beZzHie2WJYAK5h_qqwMo7uegTATJ9F997g@mail.gmail.com> <BN3PR08MB1303914D77E761964B6D5E538C370@BN3PR08MB1303.namprd08.prod.outlook.com> Message-ID: <CADGuORE3ZJ84itYeHSmf-zduRHE-PPzPo545zj3T2F-3UiajCA@mail.gmail.com> Sure, here's an export of a tiny collection showing a couple of wrapped diacritics in the custodial history. We haven't yet done any testing of the PUI--or the staff interface, for that matter--with screen readers; what we know of how the ?okina (the glottal stop marker, ʻ) interacts with them comes mostly from Library-wide testing of WordPress and LibGuides. (And from that testing we know that vowels with macrons don't normally confuse screen readers, so we haven't been coding words containing them, e.g. M?noa, with aria-label attributes.) I'm not sure what fonts we're using in WordPress and LibGuides. I'd assume they're pretty standard, but I'll ask. -Leilani. On Mon, Dec 11, 2017 at 5:58 AM, Custer, Mark <mark.custer at yale.edu> wrote: > Leilani, > > > Could you attach an example EAD file? I'm curious what happens when > Unicode characters are used in place of the character entities. I'm > wondering if the issue might simply be that the font used doesn't include > italic characters for the character entities that are tagged as italic (as > an aside, what fonts do you use outside of ArchivesSpace?). Either way, > it would be nice to add these examples to some test scripts for > ArchivesSpace. > > > Mark > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Leilani Dawson <ltdawson at hawaii.edu> > *Sent:* Friday, December 8, 2017 3:45 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Collections Browse Error in > Public Interface, v2.2.1 > > Yes, all of our accessibility-wrapped diacritics are in html tags. > > (Occasionally we have notes where words labeled with alternate text are > nested within EAD elements such as <title> or <persname> or the like, but > those EAD elements are not as critical for us as the <span> with aria-label > attribute.) > > I'll ask our IT folks to put together a 2.2 test instance so I can upload > a finding aid with diacritics and see whether the new PUI handles it in a > screen-reader-friendly manner. > > Thanks, > -Leilani > > On Fri, Dec 8, 2017 at 9:12 AM, Christine Di Bella < > christine.dibella at lyrasis.org> wrote: > > Hi Leilani, > > > > Thanks for making me dig into this a bit more and for explaining one of > the reasons tagging around a diacritic may be especially necessary. For > your use case, is your tagging always like your example? If so, there?s > sanitizer for HTML in the PUI that allows this kind of tagging to sail > through just fine. It is XML tags like <emph> that we?re seeing this bug > on. > > > > There was some accessibility work that went into the development of the > new PUI, but it would be good to know that what makes this kind of tagging > work in the PUI doesn?t also cause the same issue for screen readers that > is the reason for you wrapping the text originally. Can you test this out > locally or upload a finding aid to http://test.archivesspace.org > <https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=ojcyFCMoM3zS9hpwYf4E7AnqB96za3sLtX6PZ20VkFM&e=> > and try it out? > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 <(800)%20999-8558> > > 678-235-2905 <(678)%20235-2905> > > cdibella13 (Skype) > > > > [image: ASpaceOrgHomeMedium] > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Leilani > Dawson > *Sent:* Friday, December 8, 2017 1:13 PM > *To:* Archivesspace Users Group <archivesspace_users_group at lyr > alists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Collections Browse Error in > Public Interface, v2.2.1 > > > > Hi Christine, > > I see this is listed in JIRA as a minor issue, but is there any guess for > when it might be addressed? > > Certain Hawaiian-language diacritics "break" screen readers, so in order > to satisfy both accessibility requirements and UH's mandate to be a > Hawaiian place of learning, the Library has started wrapping these > diacritics in <span> tags with aria-label attributes. (E.g.: <span > aria-label="Hawaii">Hawaiʻi</span>) ArchivesSpace 2.1 and 2.2 not > being able to handle wrapped diacritics might preclude us from going > forward with using the public user interface and/or upgrading to 2.x. until > the fix is in. > > > -Leilani. > > - - > > Leilani Dawson > > Manuscript Collections Archivist > > University Archives & Manuscripts Department > > University of Hawaii at Manoa Library > > 2550 McCarthy Mall, Honolulu, HI 96822 > > ltdawson at hawaii.edu > > > > On Fri, Dec 8, 2017 at 3:28 AM, Christine Di Bella < > christine.dibella at lyrasis.org> wrote: > > Hi Neal, > > > > Do you by chance have a collection that has the circumstance described in > this JIRA ticket: https://archivesspace.atlassian.net/browse/AR-1938 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1938&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=VMpZ3HzcFod2VlOa_Q5TAqIkbX5K9NFmJ-9RGxTgJRI&e=> > (A diacritic wrapped in a tag.) Most likely it would be in the scope and > contents note or abstract field if the error is happening from the > collection browse. > > > > If so, and that record appears on the first page of your all collection > browse, that may be what?s causing the issue. You would also get a ?We?re > sorry something went wrong? when trying to view that particular record or > on a search that includes that particular record. If you have multiple > repositories, that would also explain why a collection browse that?s scoped > to another repository would not yield that issue. > > > > This is a reported issue for all 2.1 and 2.2 versions. The workaround for > now would be to remove either the tagging or the diacritic, but we hope to > fix this issue for a future release. > > > > If you don?t have that circumstance, we?ll need to delve into this more > deeply. > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 <(800)%20999-8558> > > 678-235-2905 <(678)%20235-2905> > > cdibella13 (Skype) > > > > [image: ASpaceOrgHomeMedium] > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Harmeyer, > Neal A > *Sent:* Thursday, December 7, 2017 5:45 PM > *To:* Archivesspace Users Group <archivesspace_users_group at lyr > alists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] Collections Browse Error in Public > Interface, v2.2.1 > > > > Hello all, > > > > I wonder if anyone else has experienced this issue? > > > > When selecting the Collections browse (/repositories/resources) from the > header in the public interface, version 2.2.1, the system throws an error > message that reads 'Your request could not be completed due to an > unexpected error'. This only occurs for Collections browse; all other areas > continue to load without issue?so our systems administrator isn?t sure this > could be cause by any web server configurations. I?ve been able to cause > the failure on our dev site by repeatedly selecting the Collections browse > over a short period of time. > > > > We didn?t experience this in any past versions. A restart of the server > removes the issue for a period of time but then it re-appears; there is > nothing in our logs to point to a cause of the problem. > > > > Any suggestions would be helpful! > > > > Thank you, > > Neal > > > > -- > > Neal Harmeyer > > Digital Archivist > > Purdue Univesity Archives and Special Collections > > Purdue University Libraries > > harmeyna at purdue.edu > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > <https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=mcku_27mMAV6rVbPS8IwL0Tx_W-qI7NJvab5eSZgQuU&e=> > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > <https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=mcku_27mMAV6rVbPS8IwL0Tx_W-qI7NJvab5eSZgQuU&e=> > > > > _______________________________________________ > 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: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/2418fb0d/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 6608 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/2418fb0d/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.jpg Type: image/jpeg Size: 6608 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/2418fb0d/attachment-0001.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: MANUSCRIPT.M00060_20171211_184828_UTC__ead.xml Type: text/xml Size: 3409 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/2418fb0d/attachment.xml> From maderikra at vmi.edu Mon Dec 11 15:02:37 2017 From: maderikra at vmi.edu (Maderik, Rachel A) Date: Mon, 11 Dec 2017 20:02:37 +0000 Subject: [Archivesspace_Users_Group] truncation in PUI 2.2.1 Message-ID: <be6834aa52ef42b38fa0691dd7e77eca@vmi.edu> Has anyone else had problems with search term truncation not working in the PUI in v2.2.1? I can replicate the problem on the public sandbox: I created a record entitled "Test Record Morrill": http://public.archivesspace.org/repositories/3/resources/105, but searching for "morril*" brings back 0 results (it also inserts a backslash before the truncation character, which may be related to the problem): [cid:image003.jpg at 01D37291.14C1DCB0] Rachel Maderik Systems and Technology Librarian 501D Preston Library Virginia Military Institute Lexington, VA 24450 540-464-7572 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/79470ac7/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 31259 bytes Desc: image003.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/79470ac7/attachment.jpg> From christine.dibella at lyrasis.org Mon Dec 11 15:23:28 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 11 Dec 2017 20:23:28 +0000 Subject: [Archivesspace_Users_Group] truncation in PUI 2.2.1 In-Reply-To: <be6834aa52ef42b38fa0691dd7e77eca@vmi.edu> References: <be6834aa52ef42b38fa0691dd7e77eca@vmi.edu> Message-ID: <CY1PR08MB119796FBE72BA32B04E2B9ACF1370@CY1PR08MB1197.namprd08.prod.outlook.com> Dear Rachel, This was a bug inadvertently introduced in 2.2.1 that will be resolved in 2.2.2, which we anticipate putting out before the holiday break. We overcorrected when we put in a fix to allow searching for another character that was previously causing errors. Apologies, Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org> 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maderik, Rachel A Sent: Monday, December 11, 2017 3:03 PM To: 'Archivesspace_Users_Group at lyralists.lyrasis.org' <Archivesspace_Users_Group at lyralists.lyrasis.org> Subject: [Archivesspace_Users_Group] truncation in PUI 2.2.1 Has anyone else had problems with search term truncation not working in the PUI in v2.2.1? I can replicate the problem on the public sandbox: I created a record entitled "Test Record Morrill": http://public.archivesspace.org/repositories/3/resources/105, but searching for "morril*" brings back 0 results (it also inserts a backslash before the truncation character, which may be related to the problem): [cid:image002.jpg at 01D37293.FA1F2360] Rachel Maderik Systems and Technology Librarian 501D Preston Library Virginia Military Institute Lexington, VA 24450 540-464-7572 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/61d7e45a/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6608 bytes Desc: image001.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/61d7e45a/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 31259 bytes Desc: image002.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/61d7e45a/attachment-0001.jpg> From sustasiula at pa.gov Tue Dec 12 14:57:42 2017 From: sustasiula at pa.gov (Stasiulatis, Suzanne) Date: Tue, 12 Dec 2017 19:57:42 +0000 Subject: [Archivesspace_Users_Group] Merging Controlled Values Message-ID: <103c127cd54443c7b8e301e93f2fbb4c@ENCTCEXCH008.PA.LCL> I remember a while back that people were having trouble merging controlled values. Is this a safe feature to use yet? Has anyone used it successfully in 2.2.x? Thanks, Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 Phone: 717-787-5953 http://www.PAStateArchives.com sustasiula at pa.gov<mailto:sustasiula at pa.gov> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171212/91be7f7a/attachment.html> From slenkb at hope.edu Tue Dec 12 15:57:33 2017 From: slenkb at hope.edu (Brian Slenk) Date: Tue, 12 Dec 2017 15:57:33 -0500 Subject: [Archivesspace_Users_Group] installing wildcard SSL cert, redirect http to https Message-ID: <CAAK7xVSGJZF==PkKyY8E_2xkoqHLQYqaBZ0EC0=tERviJ+qs4A@mail.gmail.com> Hello, I have a new installation of an archives space server. Is there a way with the Apache Solr web server to add an SSL wildcard certificate, and then redirect http to https for the the public interface ? I am not finding documentation if this is possible. Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171212/efeb656c/attachment.html> From afocke at rice.edu Tue Dec 12 16:14:01 2017 From: afocke at rice.edu (Amanda Focke) Date: Tue, 12 Dec 2017 15:14:01 -0600 Subject: [Archivesspace_Users_Group] digital object mapping to EAD in v.2.2.1 Message-ID: <5A304699.8030907@rice.edu> Hello all - We have "nearline" digital objects which do not have a public URL, and we describe them in ArchivesSpace. They have a Title and an Identifier, but we don't use the File Version field for them because there is no File URI. This is an example of what ArchivesSpace exports as EAD for a digital object which has an Identifier of "ms0599aip_001" but has no "File version / file URI". <dao xlink:actuate="onRequest" *xlink:href="ms0599aip_001"* xlink:show="new" xlink:title="Louis Albach Buffalo Bayou research materials" xlink:type="simple"> So it is mapping the Identifier to an xlink:href attribute, and therefore makes a dead link in the EAD. Has anyone successfully edited the mapping to make this stop? I would want the Identifier to simply show as "Identifier" and not try to be a link. Thanks, Amanda -- Amanda Focke, CA, DAS Asst. Head of Woodson Research Center Fondren Library Rice University 6100 Main St. MS-44 Houston, TX 77005 afocke at rice.edu | 713-348-2124 http://library.rice.edu/woodson -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171212/e5ea4566/attachment.html> From ccauste1 at swarthmore.edu Wed Dec 13 11:27:05 2017 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Wed, 13 Dec 2017 11:27:05 -0500 Subject: [Archivesspace_Users_Group] Splitting off one repository into a new database Message-ID: <CAFvko3vcNZyrjb-A+Li8GJMWwmjPhv8F6esvowNf5nxP7QX0Qw@mail.gmail.com> Hi all, Just curious if anyone has themselves, or know of anyone who has, taken a single ArchivesSpace database and split off one of the repositories into a new ArchivesSpace database? Can anyone advise on how difficult a process this would be? I don't need to do it right now, but I'm curious for planning purposes. Thanks! Celia -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College <http://swarthmore.edu/friends-historical-library> 610-328-8498 ccauste1 at swarthmore.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171213/4673ea43/attachment.html> From cpeterson at smith.edu Wed Dec 13 11:28:51 2017 From: cpeterson at smith.edu (Christie Peterson) Date: Wed, 13 Dec 2017 16:28:51 +0000 Subject: [Archivesspace_Users_Group] Position statement on multitenancy Message-ID: <CAFy-AYKbbxo4iUvNPCLdxcEzn1kPVg0-dSEarOYQfEZCB6pS8A@mail.gmail.com> Hello, Google and listserv archives brought me to the 2011 ASpace position statement on multitenancy <https://archivesspace.org/wp-content/uploads/2016/05/Position-Statement-on-Multitenancy-20111111-1.pdf> (watermarked as a draft), which states, in part: "Within the context of the ArchivesSpace project ... tenants within the application should be viewed as what would be otherwise freestanding instances of the application, and information should not be shared across tenants. If an institution should need to share data between clients within the application, implementers should use the approach where the application hosts more than one repository within one tenant." I couldn't find anything more recent addressing this question (but please point me to it if I missed it). So my question is, is this still the official or defacto position of ArchivesSpace's community, core developers, and governing bodies? Thanks, Christie Peterson -- ?? ?? ?? ?? ?? ?? ?? ?? Christie S. Peterson Head of Technical Services for Special Collections Smith College Northampton, Mass. 413-585-2996 cpeterson at smith.edu pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171213/a0d46f7f/attachment.html> From michelsd at union.edu Wed Dec 13 11:33:50 2017 From: michelsd at union.edu (Michelson, Daniel) Date: Wed, 13 Dec 2017 11:33:50 -0500 Subject: [Archivesspace_Users_Group] Merging Controlled Values In-Reply-To: <103c127cd54443c7b8e301e93f2fbb4c@ENCTCEXCH008.PA.LCL> References: <103c127cd54443c7b8e301e93f2fbb4c@ENCTCEXCH008.PA.LCL> Message-ID: <CAG_gFtzvMEVJBz+5uP4wAD+QujY2UbWqWsLUwcC6mNDwnY9OOA@mail.gmail.com> Hi Suzanne, I merged numerous controlled values some months ago and have continued to do so intermittently up to the present. The only problem I encountered was when I attempted to merge the default value into another value. That bug came up some time ago, so it may have been fixed. I've had no other problems. Regards, Dan Michelson On Tue, Dec 12, 2017 at 2:57 PM, Stasiulatis, Suzanne <sustasiula at pa.gov> wrote: > I remember a while back that people were having trouble merging controlled > values. Is this a safe feature to use yet? Has anyone used it successfully > in 2.2.x? > > > > Thanks, > > > > Suzanne > > > > *Suzanne Stasiulatis *| Archivist II > Pennsylvania Historical and Museum Commission | Pennsylvania State > Archives > 350 North Street | Harrisburg, PA 17120-0090 > > Phone: 717-787-5953 <(717)%20787-5953> > > http://www.PAStateArchives.com > > sustasiula at pa.gov > > > > _______________________________________________ > 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: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171213/9bc1b0ea/attachment.html> From sdm7g at virginia.edu Wed Dec 13 12:01:53 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 13 Dec 2017 17:01:53 +0000 Subject: [Archivesspace_Users_Group] Splitting off one repository into a new database In-Reply-To: <CAFvko3vcNZyrjb-A+Li8GJMWwmjPhv8F6esvowNf5nxP7QX0Qw@mail.gmail.com> References: <CAFvko3vcNZyrjb-A+Li8GJMWwmjPhv8F6esvowNf5nxP7QX0Qw@mail.gmail.com> Message-ID: <8B3B9972-9D1C-4756-83DE-502D97F76612@virginia.edu> I?ve never tried it, but I expect it would not be simple. If I had to do it, I would probably attempt to clone the existing database to a new instance, and then delete the other repositories and attached resources from the new instance staff interface. Alternatively, you could migrate to a new instance using the backend APIs to copy resources and just copy the global resources and those attached to the repository being migrated. Theoretically, you could do this sort of migration in SQL, but it would require mapping out all of the dependencies pretty well and I?m not sure how well that is documented. ? Steve Majewski > On Dec 13, 2017, at 11:27 AM, Celia Caust-Ellenbogen <ccauste1 at swarthmore.edu> wrote: > > Hi all, > > Just curious if anyone has themselves, or know of anyone who has, taken a single ArchivesSpace database and split off one of the repositories into a new ArchivesSpace database? Can anyone advise on how difficult a process this would be? I don't need to do it right now, but I'm curious for planning purposes. > > Thanks! > Celia > > -- > Celia Caust-Ellenbogen > Friends Historical Library of Swarthmore College <http://swarthmore.edu/friends-historical-library> > 610-328-8498 > ccauste1 at swarthmore.edu <mailto:ccauste1 at swarthmore.edu> > she/her/hers > > > _______________________________________________ > 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: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171213/08cff8a7/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171213/08cff8a7/attachment.bin> From Christine.Kim at lyrasis.org Wed Dec 13 12:42:51 2017 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Wed, 13 Dec 2017 17:42:51 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: Varying Approaches to Testing ASpace Pre-Releases - Dec 14 In-Reply-To: <MWHPR08MB249557CCB19C0A315A816DF5F5300@MWHPR08MB2495.namprd08.prod.outlook.com> References: <MWHPR08MB249557CCB19C0A315A816DF5F5300@MWHPR08MB2495.namprd08.prod.outlook.com> Message-ID: <MWHPR08MB249538681BED52F8CC82A89CF5350@MWHPR08MB2495.namprd08.prod.outlook.com> Reminder - Join us for the Unit Testing and the Testing Sub-Team: Varying Approaches to Testing ArchivesSpace Pre-Releases webinar tomorrow, December 14! Details: http://archivesspace.org/webinar-testing/ Sent: Friday, December 8, 2017 3:45 PM Subject: [Archivesspace_uac] Webinar Announcement: Varying Approaches to Testing ASpace Pre-Releases - Dec 14 Unit Testing and the Testing Sub-Team: Varying Approaches to Testing ArchivesSpace Pre-Releases When: Thursday, December 14, 2017 Time: 1:00 p.m. - 2:00 p.m. EST (10:00 a.m. - 11:00 a.m. PST) Where: Webinar at http://lyrasis.adobeconnect.com/rai0bzfc3h54/ Dial-in only option: 888-354-0094 - Access code is 731627 No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. The webinar will be recorded and available for viewing at a later date. Webinar description: Before we make any release or update widely available, we perform tests in every nook and cranny in ArchivesSpace. Testing applications plays an essential role in our workflow to ensure the application is growing in the right direction, and not breaking already functional working components. Join us on December 14 as we explore why testing is vital to our growth and process, as well as the testing methods our community implements to ensure new features and fixes are improvements. Alex and Miloche will share their experiences and insights on testing pre-release versions of ArchivesSpace. Please feel free to bring any questions you have. Presenters: Alexander Duryee (Metadata Archivist, New York Public Library) has been a major contributor in the ArchivesSpace Core Committers Group. He has taken a lead role to delve into test automation for ArchivesSpace releases. Alex will share how he runs unit testing so certain components of each release can be tested through automated commands. Miloche Kottman (Head of Cataloging & Archival Processing, University of Kansas) is leading the Testing sub-team for ArchivesSpace. Once a pre-release version is available, Miloche and the Testing sub-team implement a workflow to run through basic functions inside ArchivesSpace, employing the diverse perspectives of archivists. Miloche will share insight into how testing is carried out by the team before each release finally becomes available. Who should attend: Everyone interested in going behind the scenes of the application and learning how ArchivesSpace tests new features before releasing new versions. Questions? Please contact Kim at christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171213/8b6e1d59/attachment.html> From j at minorscience.com Wed Dec 13 15:37:36 2017 From: j at minorscience.com (Jason Loeffler) Date: Wed, 13 Dec 2017 15:37:36 -0500 Subject: [Archivesspace_Users_Group] installing wildcard SSL cert, redirect http to https In-Reply-To: <CAAK7xVSGJZF==PkKyY8E_2xkoqHLQYqaBZ0EC0=tERviJ+qs4A@mail.gmail.com> References: <CAAK7xVSGJZF==PkKyY8E_2xkoqHLQYqaBZ0EC0=tERviJ+qs4A@mail.gmail.com> Message-ID: <CAP4gJsVn+PVA4EHvjOPrAFUD3cBPwNPWY7uG1_nJECSXJrnTvQ@mail.gmail.com> Brian, There is limited documentation in the README_HTTPS.md file. <goog_1397951669> https://github.com/archivesspace/archivesspace/blob/bf7849472b0fcb91961c91764f757681670dc204/README_HTTPS.md The technical documentation team has plans for enhancing this documentation in 2018. You might reach out to one of its members if you're having trouble with the configuration. https://archivesspace.atlassian.net/wiki/spaces/AC/pages/141197319/Tech+Docs+Workplan+for+2017-2018 Regards, Jason Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) On Tue, Dec 12, 2017 at 3:57 PM, Brian Slenk <slenkb at hope.edu> wrote: > Hello, > > I have a new installation of an archives space server. Is there a way > with the Apache Solr web server to add an SSL wildcard certificate, and > then redirect http to https for the the public interface ? I am not > finding documentation if this is possible. > > Brian > > > _______________________________________________ > 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: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171213/d5d5e10c/attachment.html> From Christine.Kim at lyrasis.org Wed Dec 13 16:25:44 2017 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Wed, 13 Dec 2017 21:25:44 +0000 Subject: [Archivesspace_Users_Group] Ideas for advanced training topics? Message-ID: <MWHPR08MB24951F4B270AFCAB9B802AD2F5350@MWHPR08MB2495.namprd08.prod.outlook.com> Dear ArchivesSpace community, We're currently looking to expand on training topics. One major focus on our radar is to get an "Advanced Skills" workshop together. However, we'd love to get your input on what skills or customizations help you get the most out of ASpace. Are there any particular tools or workflows you have discovered that really makes using ASpace easier? Or are there any features or practices you would like to receive more in depth training? Some potential ideas include: preparing EAD for import, customizing the PUI, working with plugins, etc. Our current workshop topics are included on this page on the website: http://archivesspace.org/using-archivesspace/training-and-consultations/ We would really appreciate your ideas and feedback. Please email me or respond to this thread if you'd like to share your ideas. Thanks! Best wishes, Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org> 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171213/9882ec95/attachment.html> From rocook at seattleschools.org Wed Dec 13 16:30:30 2017 From: rocook at seattleschools.org (Cook, Robert) Date: Wed, 13 Dec 2017 21:30:30 +0000 Subject: [Archivesspace_Users_Group] installing wildcard SSL cert, redirect http to https In-Reply-To: <CAP4gJsVn+PVA4EHvjOPrAFUD3cBPwNPWY7uG1_nJECSXJrnTvQ@mail.gmail.com> References: <CAAK7xVSGJZF==PkKyY8E_2xkoqHLQYqaBZ0EC0=tERviJ+qs4A@mail.gmail.com> <CAP4gJsVn+PVA4EHvjOPrAFUD3cBPwNPWY7uG1_nJECSXJrnTvQ@mail.gmail.com> Message-ID: <MWHPR04MB1182F749DCFCCCE5CE2941A0A2350@MWHPR04MB1182.namprd04.prod.outlook.com> Brain, For our deployment, we have F5 load-balancers. I configured an F5 virtual server object, that listens on port 443 (SSL/HTTPS) for the public interface and additional virtual servers for each respective port for each interface Staff, Backend, Solr. I elected to use 443 for the public interface for ease of use for customers using AS. https://<AS_URL>/ vs http:// <AS_URL>:8081/ The F5 NATs the ?Client? connection to the ?AS server?, with the connection between the ?F5? and the ?AS server? still being unencrypted (F5 acting as a HTTPS proxy). I modified the config.rb to configure the application to use a different set of ports for the F5 connections to the server, while the client connections to the F5 use AS default ports (with the exception of 443 for the public interface), then I wrote a HTTP URI rewrite rule (called an iRule in F5 land) to re-write HTTP requests as HTTPS while maintaining the original requested URI string. The path is: Client <-- HTTPS --> F5 <-- HTTP --> AS Server For the traffic between the F5 and the AS Server, the server is postured on our network in a way that we aren?t concerned about unencrypted traffic on the wire. Referring back to AS documentation; if you use the Apache or some other method, you can install the proxy application on the same host as the AS server, and unencrypted traffic is never put onto the wire or leaves the server hosting the AS application, which is always preferred. Thanks, -Robbie Robert Cook Systems Engineer Dept. of Technology Services Seattle Public Schools E: rocook at seattleschools.org<mailto:rocook at seattleschools.org> P: 206-252-0352 (Forwards to my cellphone) From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler Sent: Wednesday, December 13, 2017 12:38 PM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> Subject: Re: [Archivesspace_Users_Group] installing wildcard SSL cert, redirect http to https WARNING: The sender of this email could not be validated and may not match the person in the "From" field. This might be a fake e-mail Brian, There is limited documentation in the README_HTTPS.md file. <goog_1397951669> https://github.com/archivesspace/archivesspace/blob/bf7849472b0fcb91961c91764f757681670dc204/README_HTTPS.md The technical documentation team has plans for enhancing this documentation in 2018. You might reach out to one of its members if you're having trouble with the configuration. https://archivesspace.atlassian.net/wiki/spaces/AC/pages/141197319/Tech+Docs+Workplan+for+2017-2018 Regards, Jason Jason Loeffler Technology Consultant | The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com<mailto:jason at minorscience.com> (347) 405-0826 minorscience (Skype) On Tue, Dec 12, 2017 at 3:57 PM, Brian Slenk <slenkb at hope.edu<mailto:slenkb at hope.edu>> wrote: Hello, I have a new installation of an archives space server. Is there a way with the Apache Solr web server to add an SSL wildcard certificate, and then redirect http to https for the the public interface ? I am not finding documentation if this is possible. Brian _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group CAUTION: This email originated from outside of the organization. Please don't click links, open attachments, or reply with confidential details unless you are certain you know the sender and are expecting the content. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171213/d7742c9b/attachment.html> From christine.dibella at lyrasis.org Thu Dec 14 11:08:51 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 14 Dec 2017 16:08:51 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 2.2.2 now available Message-ID: <CY1PR08MB11974DC10C013FF35361E787F10A0@CY1PR08MB1197.namprd08.prod.outlook.com> Hello ArchivesSpace members, The ArchivesSpace program team is pleased to announce the availability of v2.2.2. While we are still finishing up some larger development work that is now due in January, including the first phases of the expanded agents module specification, we wanted to close out this busy development year by putting out one last small release. This release contains a number of community pull requests and several bug fixes, most notably one that restores the ability to do truncation searches in the public user interface. A big thanks to all the community members who have provided development and submitted pull requests in 2017, including the work from Mark Cooper, Chris Fitzpatrick, Tim DiLauro, and Steve Majewski that is included in this release. You can download this release at https://github.com/archivesspace/archivesspace/releases/tag/v2.2.2. The full list of bug fixes and improvements is included in the release notes. Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not already upgraded to 2.2.0 or 2.2.1, we recommend going directly to 2.2.2, though, depending on the version you are coming from, you should read the special considerations for upgrading from/to different versions that are linked to from the upgrading document first. Thanks to all who have participated in the ArchivesSpace development process this year, from identifying and prioritizing issues, to writing and reviewing code for the application, to testing changes and writing documentation. We on the ArchivesSpace team are very appreciative of all the work so many have done to make the ArchivesSpace application what it is today and look forward to working with you towards many more improvements in 2018. If you have any questions or need help upgrading, please let us know. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org> 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171214/d03e3c28/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171214/d03e3c28/attachment.jpg> From cpeterson at smith.edu Thu Dec 14 12:25:24 2017 From: cpeterson at smith.edu (Christie Peterson) Date: Thu, 14 Dec 2017 17:25:24 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 2.2.2 now available In-Reply-To: <CY1PR08MB11974DC10C013FF35361E787F10A0@CY1PR08MB1197.namprd08.prod.outlook.com> References: <CY1PR08MB11974DC10C013FF35361E787F10A0@CY1PR08MB1197.namprd08.prod.outlook.com> Message-ID: <CAFy-AY+Sx_WahtttOio63SsoHpM6+eaXZGRJHzq5VSjvuhy+3g@mail.gmail.com> Thanks so much for this, Christine and everyone who has been contributing. Is there any way to get an idea of what's on the map for the agents module work? Is there a tag in Jira or somewhere else we can see what issues are being addressed or considered under this umbrella? Cheers, Christie Peterson On Thu, Dec 14, 2017 at 11:09 AM Christine Di Bella < christine.dibella at lyrasis.org> wrote: > Hello ArchivesSpace members, > > > > The ArchivesSpace program team is pleased to announce the availability of > v2.2.2. While we are still finishing up some larger development work that > is now due in January, including the first phases of the expanded agents > module specification, we wanted to close out this busy development year by > putting out one last small release. This release contains a number of > community pull requests and several bug fixes, most notably one that > restores the ability to do truncation searches in the public user > interface. A big thanks to all the community members who have provided > development and submitted pull requests in 2017, including the work from > Mark Cooper, Chris Fitzpatrick, Tim DiLauro, and Steve Majewski that is > included in this release. > > > > You can download this release at > https://github.com/archivesspace/archivesspace/releases/tag/v2.2.2. The > full list of bug fixes and improvements is included in the release notes. > > > > Information on upgrading to a new version of ArchivesSpace is available at > http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. > If you have not already upgraded to 2.2.0 or 2.2.1, we recommend going > directly to 2.2.2, though, depending on the version you are coming from, > you should read the special considerations for upgrading from/to different > versions that are linked to from the upgrading document first. > > > > Thanks to all who have participated in the ArchivesSpace development > process this year, from identifying and prioritizing issues, to writing and > reviewing code for the application, to testing changes and writing > documentation. We on the ArchivesSpace team are very appreciative of all > the work so many have done to make the ArchivesSpace application what it is > today and look forward to working with you towards many more improvements > in 2018. If you have any questions or need help upgrading, please let us > know. > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 <(800)%20999-8558> > > 678-235-2905 <(678)%20235-2905> > > cdibella13 (Skype) > > > > [image: ASpaceOrgHomeMedium] > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- ?? ?? ?? ?? ?? ?? ?? ?? Christie S. Peterson Head of Technical Services for Special Collections Smith College Northampton, Mass. 413-585-2996 cpeterson at smith.edu pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171214/f8268361/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171214/f8268361/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171214/f8268361/attachment-0001.jpg> From christine.dibella at lyrasis.org Thu Dec 14 12:37:30 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 14 Dec 2017 17:37:30 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 2.2.2 now available In-Reply-To: <CAFy-AY+Sx_WahtttOio63SsoHpM6+eaXZGRJHzq5VSjvuhy+3g@mail.gmail.com> References: <CY1PR08MB11974DC10C013FF35361E787F10A0@CY1PR08MB1197.namprd08.prod.outlook.com> <CAFy-AY+Sx_WahtttOio63SsoHpM6+eaXZGRJHzq5VSjvuhy+3g@mail.gmail.com> Message-ID: <CY1PR08MB1197754B4343B449194DE262F10A0@CY1PR08MB1197.namprd08.prod.outlook.com> Hi Christie, We?re putting the finishing touches on an improved and expanded format for our roadmap, complete with updated content, but here?s some information about the agents work specifically. There will be more details on the development for the pieces due in March and June when we get a little closer, but work will proceed according to the overall specification linked from AR-1779. Pending Work JIRA Target release Agents module expansion - multiple projects as follows AR-1779<https://archivesspace.atlassian.net/browse/AR-1779> more control over merging of agents ANW-183<https://archivesspace.atlassian.net/browse/ANW-183> January 2018 allow admins to set additional required fields for agents ANW-182<https://archivesspace.atlassian.net/browse/ANW-182> January 2018 add agent fields and update views part of AR-1779<https://archivesspace.atlassian.net/browse/AR-1779> March 2018 update agents importers/exporters part of AR-1779<https://archivesspace.atlassian.net/browse/AR-1779> March 2018 agent synchronization/integration with SNAC and LCNAF part of AR-1779<https://archivesspace.atlassian.net/browse/AR-1779> June 2018 Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christie Peterson Sent: Thursday, December 14, 2017 12:25 PM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> Cc: Archivesspace Member Reps <archivesspace_member_reps at lyralists.lyrasis.org>; archivesspace_tac at lyralists.lyrasis.org; ArchivesSpace Board of Trustees mail list <archivesspace_bot_members at lyralists.lyrasis.org>; archivesspace_uac at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] ArchivesSpace 2.2.2 now available Thanks so much for this, Christine and everyone who has been contributing. Is there any way to get an idea of what's on the map for the agents module work? Is there a tag in Jira or somewhere else we can see what issues are being addressed or considered under this umbrella? Cheers, Christie Peterson On Thu, Dec 14, 2017 at 11:09 AM Christine Di Bella <christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>> wrote: Hello ArchivesSpace members, The ArchivesSpace program team is pleased to announce the availability of v2.2.2. While we are still finishing up some larger development work that is now due in January, including the first phases of the expanded agents module specification, we wanted to close out this busy development year by putting out one last small release. This release contains a number of community pull requests and several bug fixes, most notably one that restores the ability to do truncation searches in the public user interface. A big thanks to all the community members who have provided development and submitted pull requests in 2017, including the work from Mark Cooper, Chris Fitzpatrick, Tim DiLauro, and Steve Majewski that is included in this release. You can download this release at https://github.com/archivesspace/archivesspace/releases/tag/v2.2.2. The full list of bug fixes and improvements is included in the release notes. Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not already upgraded to 2.2.0 or 2.2.1, we recommend going directly to 2.2.2, though, depending on the version you are coming from, you should read the special considerations for upgrading from/to different versions that are linked to from the upgrading document first. Thanks to all who have participated in the ArchivesSpace development process this year, from identifying and prioritizing issues, to writing and reviewing code for the application, to testing changes and writing documentation. We on the ArchivesSpace team are very appreciative of all the work so many have done to make the ArchivesSpace application what it is today and look forward to working with you towards many more improvements in 2018. If you have any questions or need help upgrading, please let us know. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org> 800.999.8558 x2905<tel:(800)%20999-8558> 678-235-2905<tel:(678)%20235-2905> cdibella13 (Skype) [ASpaceOrgHomeMedium] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- ?? ?? ?? ?? ?? ?? ?? ?? Christie S. Peterson Head of Technical Services for Special Collections Smith College Northampton, Mass. 413-585-2996 cpeterson at smith.edu<mailto:cpeterson at smith.edu> pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171214/da4bc13d/attachment.html> From knoxa at uncw.edu Thu Dec 14 14:14:43 2017 From: knoxa at uncw.edu (Knox, Ashley M.) Date: Thu, 14 Dec 2017 19:14:43 +0000 Subject: [Archivesspace_Users_Group] ASpace 2.1.2 issue with digital object links Message-ID: <BN6PR06MB251575619FF1D328D5AF416ADC0A0@BN6PR06MB2515.namprd06.prod.outlook.com> Hi. We are having issues with our digital objects in 2.1.2. This is a message from our server administrator: We recently upgraded to a new Linux server running RHEL 7.4, Apache 2.4.6 and ArchivesSpace 2.1.2. Everything is working normally except for some links to an existing webserver running on Windows 2012r2/IIS 8.5. Clicking on a digital object in the public user interface returns a 405 error for a bad http verb. I have checked the IIS configuration and the normal http verbs are allowed. To test, I have moved the resource to an Apache server and tested and the link resolves correctly. I am not seeing any errors in archivesspace.out, any of the Apache error logs on the aspace server or any of the logs on the IIS server. Can anyone offer any insight or suggestions as to how to fix the issue? Ashley Knox Digital Initiatives Librarian William M. Randall Library University of North Carolina Wilmington 601 South College Road Wilmington, NC 28403-5616 910-962-7996 knoxa at uncw.edu<mailto:knoxa at uncw.edu> http://library.uncw.edu<http://library.uncw.edu/> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171214/0cd5fc3b/attachment.html> From ltang5 at lib.msu.edu Fri Dec 15 10:22:39 2017 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Fri, 15 Dec 2017 15:22:39 +0000 Subject: [Archivesspace_Users_Group] Creating staff entities for Assessments module? Message-ID: <441B7155-4614-48EF-8402-90C6DDC070EE@lib.msu.edu> Hi all, We just upgraded our test instance to 2.2.2 and I?m looking forward to experimenting with the Assessments module. It looks like staff are being treated similar to Agents to populate the ?Surveyed by? and ?Reviewed by? fields. In looking at the existing documentation, it looks like Assessments hasn?t been documented yet (unless I overlooked it). I just wanted to hear from other repositories to confirm ? how are you creating staff entities, because I noticed that it doesn?t (and rightly so) pull up just any Agent records kicking around the repository? Thanks for your help! Lydia From scott.walker at Vanderbilt.Edu Fri Dec 15 10:48:49 2017 From: scott.walker at Vanderbilt.Edu (Walker, Scott) Date: Fri, 15 Dec 2017 15:48:49 +0000 Subject: [Archivesspace_Users_Group] Trouble changing localhost:9081 to new URL Message-ID: <26B0E63164FAD9448D3E02C6F69DA1B866A1B327@ITS-HCWNEM104.ds.vanderbilt.edu> Hi! I am new to ArchivesSpace and have an issue I hope you can help me with. I am having trouble figuring out how to change the default public URL from http://localhost:9081 so that our URL in the citation link and the links back to the home page use our URL. I have tried changing public_url, public_proxy_url, and frontend_proxy_url in config.rb, but none of them worked. I get a 503 error each time. Any ideas? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171215/e6438a95/attachment.html> From bobbi_fox at harvard.edu Fri Dec 15 11:01:40 2017 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Fri, 15 Dec 2017 16:01:40 +0000 Subject: [Archivesspace_Users_Group] New version of aspace-import-excel, a plugin to support bulk loading of Archival Objects Message-ID: <BN6PR07MB34921A74007C44FBB2B1CE52900B0@BN6PR07MB3492.namprd07.prod.outlook.com> Good morning, This message is for those using, or thinking of using, Harvard's aspace-import-excel, that adds and/or inserts a set of Archival Objects from an Excel Spreadsheet. I'm announcing Version v1.7.1 (Downloadable as a zip at https://github.com/harvard-library/aspace-import-excel/archive/v1.7.1.zip ), which addresses two issues: - Incorrect support of "Other Level" for the "Level of Description" column (https://github.com/harvard-library/aspace-import-excel/issues/16) o "Other Level" has been added to the template dropdown, and another column "Other Level" has been added for entering the free-text value of that level. If this new column is empty, the plugin will use the default of "unspecified" - Ruby gem clashes with the latest version of ArchivesSpace (https://github.com/harvard-library/aspace-import-excel/issues/17) Note that there is an updated template available with this version; however, if you never use "Other Level", you may safely continue using spreadsheets based on the old template. Cheers, Bobbi Fox, Maintainer Library Technology Services Harvard University -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171215/82afe08f/attachment.html> From sdm7g at virginia.edu Fri Dec 15 11:20:36 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 15 Dec 2017 16:20:36 +0000 Subject: [Archivesspace_Users_Group] New version of aspace-import-excel, a plugin to support bulk loading of Archival Objects In-Reply-To: <BN6PR07MB34921A74007C44FBB2B1CE52900B0@BN6PR07MB3492.namprd07.prod.outlook.com> References: <BN6PR07MB34921A74007C44FBB2B1CE52900B0@BN6PR07MB3492.namprd07.prod.outlook.com> Message-ID: <8AD97E49-753D-4439-A492-24D713113D20@virginia.edu> Great news! Thanks. I just tried upgrading to 2.2.2 on our test server the other day, and server wouldn?t start until I edited the rubyzip version in the Gemfile. Will upgrade to the current version of the plugin ? will make it easier to deploy. ? Steve. > On Dec 15, 2017, at 11:01 AM, Fox, Bobbi <bobbi_fox at harvard.edu> wrote: > > Good morning, > > This message is for those using, or thinking of using, Harvard?s aspace-import-excel, that adds and/or inserts a set of Archival Objects from an Excel Spreadsheet. > > I?m announcing Version v1.7.1 (Downloadable as a zip at https://github.com/harvard-library/aspace-import-excel/archive/v1.7.1.zip <https://github.com/harvard-library/aspace-import-excel/archive/v1.7.1.zip> ), which addresses two issues: > - Incorrect support of ?Other Level? for the ?Level of Description? column (https://github.com/harvard-library/aspace-import-excel/issues/16 <https://github.com/harvard-library/aspace-import-excel/issues/16>) > o ?Other Level? has been added to the template dropdown, and another column ?Other Level? has been added for entering the free-text value of that level. If this new column is empty, the plugin will use the default of ?unspecified? > - Ruby gem clashes with the latest version of ArchivesSpace (https://github.com/harvard-library/aspace-import-excel/issues/17 <https://github.com/harvard-library/aspace-import-excel/issues/17>) > > > Note that there is an updated template available with this version; however, if you never use ?Other Level?, you may safely continue using spreadsheets based on the old template. > > Cheers, > Bobbi Fox, Maintainer > Library Technology Services > Harvard University > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org <mailto:Archivesspace_Users_Group at lyralists.lyrasis.org> > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171215/1cbf7f5a/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171215/1cbf7f5a/attachment.bin> From steve.majewski at gmail.com Fri Dec 15 12:22:34 2017 From: steve.majewski at gmail.com (Steve Majewski) Date: Fri, 15 Dec 2017 12:22:34 -0500 Subject: [Archivesspace_Users_Group] reports Message-ID: <4EAD15C5-5A88-4197-8190-517D200361C0@virginia.edu> We have noticed that most of the reports in the current versions are global reports, not repository based. Is this intentional ? Both might be useful at times, but mostly, repository manages want reports for their repository only. ? Steve Majewski -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171215/061db07e/attachment.bin> From Christine.Kim at lyrasis.org Fri Dec 15 16:11:52 2017 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Fri, 15 Dec 2017 21:11:52 +0000 Subject: [Archivesspace_Users_Group] DAO Notes in EAD In-Reply-To: <BF7377CBEE38FD468371B36C139A68CB020FFC06@NY345EX10.na.GUGGENHEIM.ORG> References: <BF7377CBEE38FD468371B36C139A68CB020FFC06@NY345EX10.na.GUGGENHEIM.ORG> Message-ID: <MWHPR08MB2495AC892971D1A5BAF52C90F50B0@MWHPR08MB2495.namprd08.prod.outlook.com> Hi Tali, The EAD for the finding aid exports the DAO info that's in the resource record, but doesn't pull additional notes from the actual digital object record. The digital object record itself would need to be exported. Has anyone found a workaround for this? Is this something that should be submitted to JIRA? Best wishes, Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org> 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tali Han Sent: Thursday, December 7, 2017 9:00 AM To: 'Archivesspace_Users_Group at lyralists.lyrasis.org' <Archivesspace_Users_Group at lyralists.lyrasis.org> Subject: [Archivesspace_Users_Group] DAO Notes in EAD Hello everyone, I'm having trouble with note tags in DAO records when downloading EAD finding aids. During our migration to ArchivesSpace a few years ago, the copyright notes in <daodesc> were mapped as "General Notes" in ArchivesSpace DAO records. However, I noticed that "General Notes" or any other note fields in the DAO record do not export as part of the EAD from ArchivesSpace. I saw the following ticket but I believe this is about the PUI not the EAD export: https://archivesspace.atlassian.net/browse/AR-1807 It is crucial that the "General Note" (or any other appropriate field you can recommend) show up in our EAD XML document-we do not use the PUI but instead download the EAD and map it directly onto our online finding aid on the museum website<http://www.guggenheim.org/library-archives/archives-collections>. We are using ArchivesSpace version 2.2.0 in Google Chrome browser. Also, in the future, can I map DAO fields to export as <descriptivenote> in EAD3? Is this a setting we can tweak in the backend? I would really appreciate it if I can get any input or suggestions! Thank you! Best, Tali Tali (Chiyong) Han Archivist and Manager, Library and Archives Solomon R. Guggenheim Museum One Liberty Plaza, 24th Floor New York, NY 10006 Phone 212 360 4232 than at guggenheim.org<mailto:than at guggenheim.org> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171215/c9ee2142/attachment.html> From Adrienne.Pruitt at tufts.edu Fri Dec 15 16:41:12 2017 From: Adrienne.Pruitt at tufts.edu (Pruitt, Adrienne) Date: Fri, 15 Dec 2017 21:41:12 +0000 Subject: [Archivesspace_Users_Group] Creating staff entities for Assessments module? In-Reply-To: <441B7155-4614-48EF-8402-90C6DDC070EE@lib.msu.edu> References: <441B7155-4614-48EF-8402-90C6DDC070EE@lib.msu.edu> Message-ID: <A237987C6D42E74989F45439551E5213017319D3@SSVMEXDAG01MB06.tufts.ad.tufts.edu> Hi, Lydia, Staff entities in the assessment module pull from those who have a user account in the system. (If that makes sense - they have to be a user in ASpace in order to populate that field.) Documentation was produced for the Assessment module and hopefully will be available to you soon! Please let me know if you have questions, Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Friday, December 15, 2017 10:23 AM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> Subject: [Archivesspace_Users_Group] Creating staff entities for Assessments module? Hi all, We just upgraded our test instance to 2.2.2 and I?m looking forward to experimenting with the Assessments module. It looks like staff are being treated similar to Agents to populate the ?Surveyed by? and ?Reviewed by? fields. In looking at the existing documentation, it looks like Assessments hasn?t been documented yet (unless I overlooked it). I just wanted to hear from other repositories to confirm ? how are you creating staff entities, because I noticed that it doesn?t (and rightly so) pull up just any Agent records kicking around the repository? Thanks for your help! Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From ltang5 at lib.msu.edu Fri Dec 15 16:50:19 2017 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Fri, 15 Dec 2017 21:50:19 +0000 Subject: [Archivesspace_Users_Group] Creating staff entities for Assessments module? In-Reply-To: <A237987C6D42E74989F45439551E5213017319D3@SSVMEXDAG01MB06.tufts.ad.tufts.edu> References: <441B7155-4614-48EF-8402-90C6DDC070EE@lib.msu.edu> <A237987C6D42E74989F45439551E5213017319D3@SSVMEXDAG01MB06.tufts.ad.tufts.edu> Message-ID: <DF60CDD8-6390-4B7D-A2E3-2E55BD8104BC@lib.msu.edu> Hi Adrienne, Thanks for getting back to me! Now it works, and thank you for the clarification! It turned out that we needed to put new solr config xml files on the solr server and restart the index. Earlier, it wasn?t showing any of the staff accounts in Browse or type ahead, and we also were/are still tackling a strange issue with our test instance PUI. Earlier, our Container Inventory also wasn?t loading and now that has cleared up but we still can?t get the Collection Organization tab to load. If anyone has any ideas about that, please be in touch too! Have a great weekend, everyone! Lydia On 12/15/17, 4:41 PM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Pruitt, Adrienne" <archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Adrienne.Pruitt at tufts.edu> wrote: Hi, Lydia, Staff entities in the assessment module pull from those who have a user account in the system. (If that makes sense - they have to be a user in ASpace in order to populate that field.) Documentation was produced for the Assessment module and hopefully will be available to you soon! Please let me know if you have questions, Adrienne Pruitt | Collections Management Archivist Digital Collections and Archives Tufts University adrienne.pruitt at tufts.edu |617-627-0957 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Friday, December 15, 2017 10:23 AM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> Subject: [Archivesspace_Users_Group] Creating staff entities for Assessments module? Hi all, We just upgraded our test instance to 2.2.2 and I?m looking forward to experimenting with the Assessments module. It looks like staff are being treated similar to Agents to populate the ?Surveyed by? and ?Reviewed by? fields. In looking at the existing documentation, it looks like Assessments hasn?t been documented yet (unless I overlooked it). I just wanted to hear from other repositories to confirm ? how are you creating staff entities, because I noticed that it doesn?t (and rightly so) pull up just any Agent records kicking around the repository? Thanks for your help! Lydia _______________________________________________ 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 From sdm7g at virginia.edu Tue Dec 19 14:01:07 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 19 Dec 2017 19:01:07 +0000 Subject: [Archivesspace_Users_Group] reports Message-ID: <1685B3FF-9FBD-42F4-9D8A-2B29750F34EE@virginia.edu> Most of the reports in 2.x appear to be global. Is this intentional ? A lot of them, certainly for repository based resources like accessions, would be more useful for us if they were repository based. Agree/disagree ? ? Steve Majewski -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171219/33de33d8/attachment.bin> From christine.dibella at lyrasis.org Tue Dec 19 14:05:43 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 19 Dec 2017 19:05:43 +0000 Subject: [Archivesspace_Users_Group] release of updated Archivists' Toolkit to ArchivesSpace migration tool Message-ID: <CY1PR08MB119776F932519C8B32AE40D5F10F0@CY1PR08MB1197.namprd08.prod.outlook.com> The ArchivesSpace team is very pleased to announce the release of an updated Archivists' Toolkit to ArchivesSpace migration tool. The updated tool will enable people with Archivists' Toolkit databases who have not yet moved to ArchivesSpace to migrate directly to the latest versions of ArchivesSpace. Since ArchivesSpace has an assessment module as of v2.2.0, unlike previous versions of the migration tool, the updated tool also includes migration of assessment data. The updated tool is available at https://github.com/archivesspace/at-migration/releases/tag/v2.2.2. Thanks very much to those who provided sample AT datasets and testing feedback. A very special thanks to Ed Busch of Michigan State University for his tireless efforts in testing and re-testing the tool while we were working on it and helping us greatly improve it as a result. A note for Archon users: we are finishing up work on the updated Archon to ArchivesSpace migration tool and hope to have it available later this week. Look for another announcement soon. The updates to these migration tools reflect the very significant work of Sarah Morrissey, our Georgia Tech co-op student, under the supervision of and in collaboration with Tech Lead Laney McGlohon. We are so appreciative of Sarah's efforts and look forward to her rejoining us for her next assignment in summer 2018. We hope this updated tool will be helpful to those who have not yet made the move from Archivists' Toolkit. If you have any questions or difficulties using the updated Archivists' Toolkit migration tool, please get in touch. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org> 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171219/b6531822/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171219/b6531822/attachment.jpg> From cpeterson at smith.edu Tue Dec 19 15:12:54 2017 From: cpeterson at smith.edu (Christie Peterson) Date: Tue, 19 Dec 2017 20:12:54 +0000 Subject: [Archivesspace_Users_Group] reports In-Reply-To: <1685B3FF-9FBD-42F4-9D8A-2B29750F34EE@virginia.edu> References: <1685B3FF-9FBD-42F4-9D8A-2B29750F34EE@virginia.edu> Message-ID: <CAFy-AYJS+T=GGTN8Tb3-4r304vheP-tnP+gZ1GHt_R2TBbSonQ@mail.gmail.com> I have a broader question about reports, which perhaps someone can answer along with Steven's specific one: is all pending work of the reports subcomittee complete? If so, are there plans to update the user guide to reflect if and how reports can be customized? Thanks, Christie On Tue, Dec 19, 2017 at 2:01 PM Majewski, Steven Dennis (sdm7g) < sdm7g at virginia.edu> wrote: > > Most of the reports in 2.x appear to be global. > Is this intentional ? > A lot of them, certainly for repository based resources like accessions, > would be more useful for us if they were repository based. > > Agree/disagree ? > > > ? Steve Majewski > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- ?? ?? ?? ?? ?? ?? ?? ?? Christie S. Peterson Head of Technical Services for Special Collections Smith College Northampton, Mass. 413-585-2996 cpeterson at smith.edu pronouns: she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171219/4a627dbf/attachment.html> From Christine.Kim at lyrasis.org Tue Dec 19 16:08:06 2017 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Tue, 19 Dec 2017 21:08:06 +0000 Subject: [Archivesspace_Users_Group] Happy Holidays from ArchivesSpace! Message-ID: <MWHPR08MB2495F4C42F9753F5FC24BEC7F50F0@MWHPR08MB2495.namprd08.prod.outlook.com> [cid:image001.jpg at 01D37589.3923C050] Thank you for your continued support of ArchivesSpace! We really appreciate all you do to shape ArchivesSpace so that we are always growing and learning, both as an application as well as a community. This has been a wonderful year of exciting developments, and we look forward to accomplishing even more together in the next. We wish you all a warm and happy holidays! Sincerely, Your ArchivesSpace Program Team (Christine Di Bella, Christine Kim, Laney McGlohon, and Laurie Gemmill Arp) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171219/7861cfb8/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 35951 bytes Desc: image003.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171219/7861cfb8/attachment.jpg> From sdm7g at virginia.edu Tue Dec 19 17:30:41 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 19 Dec 2017 22:30:41 +0000 Subject: [Archivesspace_Users_Group] reports In-Reply-To: <CAFy-AYJS+T=GGTN8Tb3-4r304vheP-tnP+gZ1GHt_R2TBbSonQ@mail.gmail.com> References: <1685B3FF-9FBD-42F4-9D8A-2B29750F34EE@virginia.edu> <CAFy-AYJS+T=GGTN8Tb3-4r304vheP-tnP+gZ1GHt_R2TBbSonQ@mail.gmail.com> Message-ID: <B163AF0C-9F44-41CE-9CD2-372755965D73@virginia.edu> I have found that reports can be added to ( and probably customized ) by adding to the archivesspace/reports/ directory. I assumed this was the way to do it since the reports directory is a top level directory and not part of the frontend or backend .war files. I haven?t yet tested ( or searched ) to see if it looks in the plugins/local/ directory as well. ( I?m adding a users + permission groups report, and looking at modifying some of the existing accession reports to be repository based. ) ? Steve. > On Dec 19, 2017, at 3:12 PM, Christie Peterson <cpeterson at smith.edu> wrote: > > I have a broader question about reports, which perhaps someone can answer along with Steven's specific one: is all pending work of the reports subcomittee complete? If so, are there plans to update the user guide to reflect if and how reports can be customized? > > Thanks, > > Christie > > On Tue, Dec 19, 2017 at 2:01 PM Majewski, Steven Dennis (sdm7g) <sdm7g at virginia.edu <mailto:sdm7g at virginia.edu>> wrote: > > Most of the reports in 2.x appear to be global. > Is this intentional ? > A lot of them, certainly for repository based resources like accessions, would be more useful for us if they were repository based. > > Agree/disagree ? > > > ? Steve Majewski > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org <mailto:Archivesspace_Users_Group at lyralists.lyrasis.org> > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group> > -- > ?? ?? ?? ?? ?? ?? ?? ?? > Christie S. Peterson > Head of Technical Services for Special Collections > Smith College > Northampton, Mass. > 413-585-2996 > cpeterson at smith.edu <mailto:cpeterson at smith.edu> > > pronouns: she/her/hers > _______________________________________________ > 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: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171219/616fecfa/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171219/616fecfa/attachment.bin> From laney.mcglohon at lyrasis.org Wed Dec 20 08:41:37 2017 From: laney.mcglohon at lyrasis.org (Laney McGlohon) Date: Wed, 20 Dec 2017 13:41:37 +0000 Subject: [Archivesspace_Users_Group] Update on reports Message-ID: <B48F514D-3993-4FE1-8994-9C7BCE0C28CD@lyrasis.org> Hey Everyone, In response to the questions about reports, I would like to share the future plans on improving them. The reports sub-team and I are working on a data dictionary which will help with determining which fields to include in the reports. I have been working on a reports refactoring project that will improve the reports that are in the ArchivesSpace distribution. We are expecting to roll out the changes in the major releases in 2018, and hope to begin that rollout process with the January release. Thanks to the efforts of Steve Majewski, those modifications will probably be included in earlier releases than currently planned, so stay tuned for future announcements. Best, Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org<mailto:laney.mcglohon at lyrasis.org> 818-442-7161 laneymcglohon Skype [cid:image001.jpg at 01D3796E.57EB7AD0] [id:image002.png at 01D36F5B.0E7349E0] Become a Reviewer<http://lyrasisnow.org/become-a-reviewer-for-the-2018-catalyst-fund/> for the 2018 Catalyst Fund! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171220/d7fbdb4a/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6695 bytes Desc: image001.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171220/d7fbdb4a/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 21697 bytes Desc: image002.png URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171220/d7fbdb4a/attachment.png> From jsteele at jhu.edu Wed Dec 20 10:54:53 2017 From: jsteele at jhu.edu (Jordon Steele) Date: Wed, 20 Dec 2017 15:54:53 +0000 Subject: [Archivesspace_Users_Group] Update on reports In-Reply-To: <B48F514D-3993-4FE1-8994-9C7BCE0C28CD@lyrasis.org> References: <B48F514D-3993-4FE1-8994-9C7BCE0C28CD@lyrasis.org> Message-ID: <963d45a14eab4433b8fddec8d59a30c2@esgmtwex18.win.ad.jhu.edu> Thanks for the update, Laney. We?ve toyed with the idea of using another application to generate reports because of ASpace?s challenges to produce even basic reports (not meant to be a judgment, just the reality), but if improving reports is on the roadmap we?ll hold tight for now. Thank you to those in the community actively working on this. Best, Jordon Jordon Steele Hodson Curator of the University Archives Special Collections The Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 410-516-5493 jsteele at jhu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Laney McGlohon Sent: Wednesday, December 20, 2017 8:42 AM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> Subject: [Archivesspace_Users_Group] Update on reports Hey Everyone, In response to the questions about reports, I would like to share the future plans on improving them. The reports sub-team and I are working on a data dictionary which will help with determining which fields to include in the reports. I have been working on a reports refactoring project that will improve the reports that are in the ArchivesSpace distribution. We are expecting to roll out the changes in the major releases in 2018, and hope to begin that rollout process with the January release. Thanks to the efforts of Steve Majewski, those modifications will probably be included in earlier releases than currently planned, so stay tuned for future announcements. Best, Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org<mailto:laney.mcglohon at lyrasis.org> 818-442-7161 laneymcglohon Skype [cid:image001.jpg at 01D37980.F74B7A50] [id:image002.png at 01D36F5B.0E7349E0] Become a Reviewer<http://lyrasisnow.org/become-a-reviewer-for-the-2018-catalyst-fund/> for the 2018 Catalyst Fund! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171220/2fe215c1/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6695 bytes Desc: image001.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171220/2fe215c1/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 21697 bytes Desc: image002.png URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171220/2fe215c1/attachment.png> From christine.dibella at lyrasis.org Thu Dec 21 14:49:22 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 21 Dec 2017 19:49:22 +0000 Subject: [Archivesspace_Users_Group] release of updated Archon to ArchivesSpace migration tool Message-ID: <CY1PR08MB11971529E6F2DFC4495E84D2F10D0@CY1PR08MB1197.namprd08.prod.outlook.com> The ArchivesSpace team is very pleased to announce the release of an updated Archon to ArchivesSpace migration tool. The updated tool will enable people with Archon databases who have not yet moved to ArchivesSpace to migrate directly to the latest versions of ArchivesSpace. The updated tool is available at https://github.com/archivesspace/archon-migration/releases/latest. Thanks very much to those who provided sample Archon datasets and testing feedback. Particular thanks to Jeff Sheldon and Cliff Hight at Kansas State University for helping us improve the tool in a number of areas after our first update efforts. Once again, this update reflects the very significant work of Sarah Morrissey, our Georgia Tech co-op student, under the supervision of and in collaboration with Tech Lead Laney McGlohon. We look forward to more great work that will benefit many in the ArchivesSpace community when Sarah rejoins us for her next assignment in summer 2018. We hope this updated tool will be helpful to those who have not yet made the move from Archon and are planning to do so in the near future. If you have any questions or difficulties using the updated Archon migration tool, please get in touch. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org> 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171221/96c1c094/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171221/96c1c094/attachment.jpg> From PJFlanagan at ship.edu Thu Dec 21 15:27:10 2017 From: PJFlanagan at ship.edu (Flanagan, Patrick) Date: Thu, 21 Dec 2017 20:27:10 +0000 Subject: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 Message-ID: <1cd6941edab84b1d9c97ac7527543366@ship.edu> Hello, I'm attempting to write a plugin that will modify the way the breadcrumb trail (shown in the new public UI) is generated to include more detail. I decided to try and override one of the files in the controller part of the architecture: resources_controller.rb, since I can see the :crumb being defined there. However, either my path is wrong, or the new UI isn't utilizing it. Following the instructions here: http://archivesspace.github.io/archivesspace/user/archivesspace-plug-ins-readme/ I've placed the file in the following directory: as220/plugins/local/public/controllers/resources_controller.rb ( source location: /public/app/controllers/resources_controller.rb ) Plugin Config: AppConfig[:plugins] = ['local', 'lcnaf', 'aspace-public-formats'] If I'm not mistaken that document indicates that this is something that can be overridden, but I'm suspecting I can't actually override something in the controller from a plugin. The version is 2.2.0, running on Linux x64, openjdk version "1.8.0_151". Any advice would be appreciated! Thank you, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171221/1af624c2/attachment.html> From bobbi_fox at harvard.edu Thu Dec 21 15:47:18 2017 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Thu, 21 Dec 2017 20:47:18 +0000 Subject: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 In-Reply-To: <1cd6941edab84b1d9c97ac7527543366@ship.edu> References: <1cd6941edab84b1d9c97ac7527543366@ship.edu> Message-ID: <BN6PR07MB3492B4BA65ACAB6FED8BD8DF900D0@BN6PR07MB3492.namprd07.prod.outlook.com> Hi, Patrick, I'm having to do a lot of extending/overriding of controllers & methods in our new public interface. You are correct; you can't just override by placing your modified controller in the path location; instead, what *I'm* doing (and I know there's a more elegant way of doing it); is put the changes in the plugin/plugin_init.rb ,using the [class|module]_eval method on something. For instance, I'm changing what gets faceted in the Searchable concern this way in plugin_init.rb: Searchable.module_eval do def set_up_and_run_search(default_types = [],default_facets=[],default_search_opts={}, params={}) ~ my stuff here ~~ end end I'm adding methods to controllers in a somewhat similar way, for instance, in plugin_init.rb, I've got: # add a digital only action to the resources controller class ResourcesController def digital_only uri = "/repositories/#{params[:rid]}/resources/#{params[:id]}" begin ~ etc. ~ end end Hope this helps, Bobbi From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Flanagan, Patrick Sent: Thursday, December 21, 2017 3:27 PM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> Subject: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 Hello, I'm attempting to write a plugin that will modify the way the breadcrumb trail (shown in the new public UI) is generated to include more detail. I decided to try and override one of the files in the controller part of the architecture: resources_controller.rb, since I can see the :crumb being defined there. However, either my path is wrong, or the new UI isn't utilizing it. Following the instructions here: http://archivesspace.github.io/archivesspace/user/archivesspace-plug-ins-readme/<https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.github.io_archivesspace_user_archivesspace-2Dplug-2Dins-2Dreadme_&d=DwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=5xWUzLrZrVLeTqs3CDoeRpPtLv1fRM04CCu4TDULrSY&m=3DmZ4KyjSuOHTC-7rfq8Dv2MTeEFEBci91sKzca-4YQ&s=is5OAKKChee55MtdTuQYDj2OwuvI8f0Y6lBLS8-ast8&e=> I've placed the file in the following directory: as220/plugins/local/public/controllers/resources_controller.rb ( source location: /public/app/controllers/resources_controller.rb ) Plugin Config: AppConfig[:plugins] = ['local', 'lcnaf', 'aspace-public-formats'] If I'm not mistaken that document indicates that this is something that can be overridden, but I'm suspecting I can't actually override something in the controller from a plugin. The version is 2.2.0, running on Linux x64, openjdk version "1.8.0_151". Any advice would be appreciated! Thank you, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171221/b34bd032/attachment.html> From PJFlanagan at ship.edu Thu Dec 21 16:18:32 2017 From: PJFlanagan at ship.edu (Flanagan, Patrick) Date: Thu, 21 Dec 2017 21:18:32 +0000 Subject: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 In-Reply-To: <BN6PR07MB3492B4BA65ACAB6FED8BD8DF900D0@BN6PR07MB3492.namprd07.prod.outlook.com> References: <1cd6941edab84b1d9c97ac7527543366@ship.edu>, <BN6PR07MB3492B4BA65ACAB6FED8BD8DF900D0@BN6PR07MB3492.namprd07.prod.outlook.com> Message-ID: <207241878cdb49c385b9351d3735c3f1@ship.edu> Hi Bobbi, Thank you for this! I'll give it a try this way and see if I can make some progress. ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Fox, Bobbi <bobbi_fox at harvard.edu> Sent: Thursday, December 21, 2017 3:47:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 Hi, Patrick, I?m having to do a lot of extending/overriding of controllers & methods in our new public interface. You are correct; you can?t just override by placing your modified controller in the path location; instead, what *I?m* doing (and I know there?s a more elegant way of doing it); is put the changes in the plugin/plugin_init.rb ,using the [class|module]_eval method on something. For instance, I?m changing what gets faceted in the Searchable concern this way in plugin_init.rb: Searchable.module_eval do def set_up_and_run_search(default_types = [],default_facets=[],default_search_opts={}, params={}) ~ my stuff here ~~ end end I?m adding methods to controllers in a somewhat similar way, for instance, in plugin_init.rb, I?ve got: # add a digital only action to the resources controller class ResourcesController def digital_only uri = "/repositories/#{params[:rid]}/resources/#{params[:id]}" begin ~ etc. ~ end end Hope this helps, Bobbi From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Flanagan, Patrick Sent: Thursday, December 21, 2017 3:27 PM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> Subject: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 Hello, I'm attempting to write a plugin that will modify the way the breadcrumb trail (shown in the new public UI) is generated to include more detail. I decided to try and override one of the files in the controller part of the architecture: resources_controller.rb, since I can see the :crumb being defined there. However, either my path is wrong, or the new UI isn't utilizing it. Following the instructions here: http://archivesspace.github.io/archivesspace/user/archivesspace-plug-ins-readme/<https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.github.io_archivesspace_user_archivesspace-2Dplug-2Dins-2Dreadme_&d=DwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=5xWUzLrZrVLeTqs3CDoeRpPtLv1fRM04CCu4TDULrSY&m=3DmZ4KyjSuOHTC-7rfq8Dv2MTeEFEBci91sKzca-4YQ&s=is5OAKKChee55MtdTuQYDj2OwuvI8f0Y6lBLS8-ast8&e=> I've placed the file in the following directory: as220/plugins/local/public/controllers/resources_controller.rb ( source location: /public/app/controllers/resources_controller.rb ) Plugin Config: AppConfig[:plugins] = ['local', 'lcnaf', 'aspace-public-formats'] If I'm not mistaken that document indicates that this is something that can be overridden, but I'm suspecting I can't actually override something in the controller from a plugin. The version is 2.2.0, running on Linux x64, openjdk version "1.8.0_151". Any advice would be appreciated! Thank you, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171221/03751fb2/attachment.html> From sdm7g at virginia.edu Thu Dec 21 16:40:29 2017 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 21 Dec 2017 21:40:29 +0000 Subject: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 In-Reply-To: <207241878cdb49c385b9351d3735c3f1@ship.edu> References: <1cd6941edab84b1d9c97ac7527543366@ship.edu> <BN6PR07MB3492B4BA65ACAB6FED8BD8DF900D0@BN6PR07MB3492.namprd07.prod.outlook.com> <207241878cdb49c385b9351d3735c3f1@ship.edu> Message-ID: <FDFEB843-68A5-4CD2-B29B-EA5C65C56A78@virginia.edu> I remember running into something like this where the problem was Rails lazy loading of classes. The base classes were not actually defined when the plugins were loaded, so what was supposed to be additional methods extending an existing class became the entire replacement class definition. I had to add a reference to the class to force lazy loading before trying to extend the class. This might be what you are running into. I will look and see if I still have any notes with more details from that experiment. ? Steve. > On Dec 21, 2017, at 4:18 PM, Flanagan, Patrick <PJFlanagan at ship.edu> wrote: > > Hi Bobbi, > > Thank you for this! I'll give it a try this way and see if I can make some progress. > > ~Patrick Flanagan > KLN Applications Administrator > Keystone Library Network Hub > From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Fox, Bobbi <bobbi_fox at harvard.edu> > Sent: Thursday, December 21, 2017 3:47:18 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 > > Hi, Patrick, > > I?m having to do a lot of extending/overriding of controllers & methods in our new public interface. > > You are correct; you can?t just override by placing your modified controller in the path location; instead, what *I?m* doing (and I know there?s a more elegant way of doing it); is put the changes in the plugin/plugin_init.rb ,using the [class|module]_eval method on something. > > For instance, I?m changing what gets faceted in the Searchable concern this way in plugin_init.rb: > Searchable.module_eval do > def set_up_and_run_search(default_types = [],default_facets=[],default_search_opts={}, params={}) > ~ my stuff here ~~ > end > end > > > I?m adding methods to controllers in a somewhat similar way, for instance, in plugin_init.rb, I?ve got: > > # add a digital only action to the resources controller > class ResourcesController > def digital_only > uri = "/repositories/#{params[:rid]}/resources/#{params[:id]}" > begin > ~ etc. ~ > end > end > > Hope this helps, > Bobbi > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Flanagan, Patrick > Sent: Thursday, December 21, 2017 3:27 PM > To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 > > Hello, > > I'm attempting to write a plugin that will modify the way the breadcrumb trail (shown in the new public UI) is generated to include more detail. I decided to try and override one of the files in the controller part of the architecture: resources_controller.rb, since I can see the :crumb being defined there. However, either my path is wrong, or the new UI isn't utilizing it. Following the instructions here:http://archivesspace.github.io/archivesspace/user/archivesspace-plug-ins-readme/ <https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.github.io_archivesspace_user_archivesspace-2Dplug-2Dins-2Dreadme_&d=DwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=5xWUzLrZrVLeTqs3CDoeRpPtLv1fRM04CCu4TDULrSY&m=3DmZ4KyjSuOHTC-7rfq8Dv2MTeEFEBci91sKzca-4YQ&s=is5OAKKChee55MtdTuQYDj2OwuvI8f0Y6lBLS8-ast8&e=> I've placed the file in the following directory: > > as220/plugins/local/public/controllers/resources_controller.rb > ( source location: /public/app/controllers/resources_controller.rb ) > Plugin Config: AppConfig[:plugins] = ['local', 'lcnaf', 'aspace-public-formats'] > > > If I'm not mistaken that document indicates that this is something that can be overridden, but I'm suspecting I can't actually override something in the controller from a plugin. > > The version is 2.2.0, running on Linux x64, openjdk version "1.8.0_151". Any advice would be appreciated! > > Thank you, > > ~Patrick Flanagan > KLN Applications Administrator > Keystone Library Network Hub > _______________________________________________ > 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: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171221/4ba76ff0/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171221/4ba76ff0/attachment.bin> From Christine.Kim at lyrasis.org Thu Dec 21 17:44:54 2017 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Thu, 21 Dec 2017 22:44:54 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - December 2017 Message-ID: <MWHPR08MB2495CBA386919B8DE5C142B5F50D0@MWHPR08MB2495.namprd08.prod.outlook.com> [ASpaceOrgHome.jpg] December 2017 Update We're happy to round out the year with some exciting news. We have new migration tool that will help you migrate from either Archivists' Toolkit or Archon directly into the latest ArchivesSpace version. We also just had a smaller release come out that addresses some bug fixes. The Staff Interface Enhancement Working Group has submitted their final recommendations! And we have a variety of webinars all queued up for the new year. Read on for more news! Development The ArchivesSpace program team is pleased to announce the availability of v2.2.2. While we are still finishing up some larger development work that is now due in January, including the first phases of the expanded agents module specification, we wanted to close out this busy development year by putting out one last small release. This release contains a number of community pull requests and several bug fixes, most notably one that restores the ability to do truncation searches in the public user interface. A big thanks to all the community members who have provided development and submitted pull requests in 2017, including the work from Mark Cooper, Chris Fitzpatrick, Tim DiLauro, and Steve Majewski that is included in this release. You can download this release at https://github.com/archivesspace/archivesspace/releases/tag/v2.2.2. The full list of bug fixes and improvements is included in the release notes. Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not already upgraded to 2.2.0 or 2.2.1, we recommend going directly to 2.2.2, though, depending on the version you are coming from, you should read the special considerations for upgrading from/to different versions that are linked to from the upgrading document first. Thanks to all who have participated in the ArchivesSpace development process this year, from identifying and prioritizing issues, to writing and reviewing code for the application, to testing changes and writing documentation. We on the ArchivesSpace team are very appreciative of all the work so many have done to make the ArchivesSpace application what it is today and look forward to working with you towards many more improvements in 2018. If you have any questions or need help upgrading, please let us know. Release of Updated Migration Tools The ArchivesSpace team is very pleased to announce the release of two updated migration tools: an Archivists' Toolkit to ArchivesSpace migration tool, as well as an Archon to ArchivesSpace migration tool. Both updated tools will enable people with Archivists' Toolkit or Archon databases who have not yet moved to ArchivesSpace to migrate directly to the latest versions of ArchivesSpace. Since ArchivesSpace has an assessment module as of v2.2.0, unlike previous versions of the migration tool, the updated tool also includes migration of assessment data. The updated Archivists' Toolkit to ArchivesSpace tool is available at https://github.com/archivesspace/at-migration/releases/tag/v2.2.2. The updated Archon to ArchivesSpace tool is available at https://github.com/archivesspace/archon-migration/releases/latest. Thanks very much to those who provided sample AT and Archon datasets and testing feedback. A very special thanks to Ed Busch of Michigan State University for his tireless efforts in testing and re-testing the Archivists' Toolkit migration tool while we were working on it and helping us greatly improve it as a result. And particular thanks to Jeff Sheldon and Cliff Hight at Kansas State University for helping us improve the Archon migration tool in a number of areas after our first update efforts. This update reflects the very significant work of Sarah Morrissey, our Georgia Tech co-op student, under the supervision of and in collaboration with Tech Lead Laney McGlohon. We look forward to more great work that will benefit many in the ArchivesSpace community when Sarah rejoins us for her next assignment in summer 2018. We hope these updated tools will be helpful to those who have not yet made the move from either Archivists' Toolkit or Archon and are planning to do so in the near future. If you have any questions or difficulties using the updated Archon migration tool, please get in touch. Staff Interface Enhancement Working Group - Final Recommendations Following an open commentary period from November 7 to December 12th, SIEWG submitted their final recommendations on December 21st. These recommendations are available: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/369557505/SIEWG+final+recommendations. Please feel free to add additional comments on the final recommendations page. There will also be opportunities for additional comments and feedback throughout the implementation process into 2018. A very special thank you to SIEWG for their incredible work to identify areas for improvement, proposing and refining recommendations, and incorporating feedback from the community to create a vision of an improved staff interface. Particular thanks goes to Lydia Tang for fearlessly spearheading this group. We look forward to continuing this work into the new year as we investigate how to incorporate these recommendations into the application and partner with developers to give life to this vision. Webinar on the ArchivesSpace Technology & Development Roadmap: January 17 at 2-2:30pm ET (11-11:30am PT) The ArchivesSpace Technology and Development roadmap is a planning and communication tool to help our community know what to expect in terms of future development work and aid in planning for upcoming releases. To be distributed at the end of 2017, the latest version of our roadmap has many content and format updates, and now provides a series of views targeted at the needs of different kinds of ArchivesSpace stakeholders. In this webinar, Program Manager Christine Di Bella will walk through the new roadmap format and also take questions and comments on the development planning process. Please join us on January 17, 2018 at 2-2:30pm EST (11-11:30am PST) as Christine shares an overview of the new ArchivesSpace Technology and Development roadmap. Please feel free to bring any questions you have. The webinar will be available through Adobe Connect. The URL to the webinar will be posted soon. No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. If you have any questions about this webinar, please contact Kim at christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org>. We look forward to seeing you at the webinar! Save the date for upcoming web events! Formal announcements to follow. * Webinar: ArchivesSpace Technology & Development Roadmap [January 17, 2-2:30pm ET / 11-11:30am PT] * Open Members Call on Zoom! [February 21, 2-3pm ET / 11-noon PT] * Webinar: Assessments Module Overview & Implementation [March 2, 1-2pm ET / 10-11am PT] * Webinar: A Bug's Life: From JIRA to Fix [April 11, 1-2pm ET / 10-11am PT] Webinar on Testing: Recording Available Thanks to all who joined our webinar on testing ArchivesSpace pre-release candidates. For those who were unable to make it, the webinar has been recorded and is available here: https://youtu.be/5jY8rAmGqP8 Special thanks to our presenters, Alexander Duryee (Metadata Archivist, New York Public Library) and Miloche Kottman (Head of Cataloging & Archival Processing, University of Kansas). New Blog Series: User Insights User Insights<http://archivesspace.org/category/user-insights/> is a blog series that highlights diverse perspectives and experiences of ArchivesSpace users to enrich our entire community through shared stories, strategies, and lessons learned. This series aims to provide insight to the archivists, librarians, information technologists, developers, and so many other contributors using ArchivesSpace to preserve permanently valuable records and provide access to our researchers. If you would like to share your ArchivesSpace stories, please email Kim at christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org>. Regional Forums: Announcement & Request for Help We have been looking forward to offering regional forums for the ArchivesSpace community. We envision these forums as opportunities for our diverse ArchivesSpace members to meet up more locally to share and learn from each other through workshops, focused discussion sessions, and presentations. We are happy to announce the first regional forum will be coming to the Boston area on May 3, 2018 at Tufts University. We would love for the content to be shaped by the community. This working group will focus on identifying program content, connecting with presenters, and suggesting local arrangements. Additionally, other potential tasks will include hands-on assistance during the forum such as running the registration table and taking notes. The program team will take care of any details concerning cost and logistics. If you (or you know someone interested) would like to join the working group to plan the ArchivesSpace Regional Forum in Boston, feel free to email me at christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org>. Please let me know if you have any questions, and thank you for considering. Happy Holidays! Thank you for your continued support of ArchivesSpace! We really appreciate all you do to shape ArchivesSpace so that we are always growing and learning, both as an application as well as a community. This has been a wonderful year of exciting developments, and we look forward to accomplishing even more together in the next. Our office will be closed during the holidays, from December 25 to January 1. Normal office hours will resume on January 2nd. Hope you all have a warm and happy holidays! Membership Update Our new members since November 17 include: * McDaniel College * University of Wisconsin-Madison * University of Amsterdam * Oklahoma State University * Front Range Community College * ADVN | archives for national movements New educational member: * University of North Carolina at Greensboro Department of Library and Information Studies * University of Missouri iSchool As of December 21, we have 345 General members, 19 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org> for more information. ________________________________ ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA's Collection Management Tools roundtable 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171221/9f6da938/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 20006 bytes Desc: image003.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171221/9f6da938/attachment.jpg> From christine.dibella at lyrasis.org Fri Dec 22 09:04:41 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 22 Dec 2017 14:04:41 +0000 Subject: [Archivesspace_Users_Group] latest version and format for the ArchivesSpace roadmap Message-ID: <CY1PR08MB11976D58EACB55D26D12C516F1020@CY1PR08MB1197.namprd08.prod.outlook.com> Hello ArchivesSpace members, In recent months we've been working to update both the content and the format of our technology and development roadmap. The results are now available as a series of PDFs linked from our wiki at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/18710568/Roadmap. Our roadmap now consists of a series of views targeted at the needs of different kinds of ArchivesSpace stakeholders. Whether you're looking for everything related to the plans for particular functionality or want to volunteer to take on a development project (All Details<https://archivesspace.atlassian.net/wiki/download/attachments/18710568/ASpaceRoadMap-December%202017%20-%20full%20details.pdf?version=1&modificationDate=1513879897969&cacheVersion=1&api=v2>), want an overview of the plans for the year (Annual Overview<https://archivesspace.atlassian.net/wiki/download/attachments/18710568/ASpaceRoadMap-December%202017%20-%20annual%20overview.pdf?version=1&modificationDate=1513879905567&cacheVersion=1&api=v2>), need to know what's in a particular release (Release-Specific views, such as this one for the our just released 2.2.2<https://archivesspace.atlassian.net/wiki/download/attachments/18710568/ASpaceRoadMap-December%202017%20release%20details.pdf?version=1&modificationDate=1513879899717&cacheVersion=1&api=v2>) or just want to convey to your administration how much is happening with the ArchivesSpace application (Impact of Enhancements<https://archivesspace.atlassian.net/wiki/download/attachments/18710568/ASpaceRoadMap-December%202017%20-%20impact.pdf?version=1&modificationDate=1513879898892&cacheVersion=1&api=v2>), we've got a view for you. By its nature, the roadmap includes more detail in the near term, but more tentative information about improvements planned further out. In 2018, we'll aim to update it after every release. Thanks to all who gave feedback on previous versions of the roadmap and helped us conceive of this new format. And many kudos to Christine Kim for applying her impressive design and Excel skills to the challenge of making a roadmap that both meets the needs of our many audiences and is easier for the program team to maintain. Please feel free to get in touch with any questions. As mentioned in yesterday's monthly update, I'll also be presenting a webinar on the new roadmap on January 17 at 2:00 ET for those who want to dive into it with us a bit more deeply. I look forward to connecting with many of you there and in many other ways in the new year. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org> 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171222/b4679193/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171222/b4679193/attachment.jpg> From PJFlanagan at ship.edu Fri Dec 22 15:07:18 2017 From: PJFlanagan at ship.edu (Flanagan, Patrick) Date: Fri, 22 Dec 2017 20:07:18 +0000 Subject: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 In-Reply-To: <FDFEB843-68A5-4CD2-B29B-EA5C65C56A78@virginia.edu> References: <1cd6941edab84b1d9c97ac7527543366@ship.edu> <BN6PR07MB3492B4BA65ACAB6FED8BD8DF900D0@BN6PR07MB3492.namprd07.prod.outlook.com> <207241878cdb49c385b9351d3735c3f1@ship.edu>, <FDFEB843-68A5-4CD2-B29B-EA5C65C56A78@virginia.edu> Message-ID: <c8e3e306a42a4bc08227c241b677fa6d@ship.edu> I think I just encountered that sort of issue. From public/plugin_init.rb both ResourcesController and ApplicationController don't appear to be in scope; so I can't even replace it let alone extend it. That, or I'm supposed to use require to get at the specific classes - but I haven't been able to do so. I think it's one of the intricacies of Rails that is escaping me. Ideally, for an identifier of A/B/C/D on a given resource, I wanted the breadcrumb to link back to A - B - C - D - This Resource, a behavior that's more similar to Archon, and more useful than the default behavior of simply linking to the repository top itself, I think. ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Majewski, Steven Dennis (sdm7g) <sdm7g at virginia.edu> Sent: Thursday, December 21, 2017 4:40:29 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 I remember running into something like this where the problem was Rails lazy loading of classes. The base classes were not actually defined when the plugins were loaded, so what was supposed to be additional methods extending an existing class became the entire replacement class definition. I had to add a reference to the class to force lazy loading before trying to extend the class. This might be what you are running into. I will look and see if I still have any notes with more details from that experiment. ? Steve. On Dec 21, 2017, at 4:18 PM, Flanagan, Patrick <PJFlanagan at ship.edu<mailto:PJFlanagan at ship.edu>> wrote: Hi Bobbi, Thank you for this! I'll give it a try this way and see if I can make some progress. ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Fox, Bobbi <bobbi_fox at harvard.edu<mailto:bobbi_fox at harvard.edu>> Sent: Thursday, December 21, 2017 3:47:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 Hi, Patrick, I?m having to do a lot of extending/overriding of controllers & methods in our new public interface. You are correct; you can?t just override by placing your modified controller in the path location; instead, what *I?m* doing (and I know there?s a more elegant way of doing it); is put the changes in the plugin/plugin_init.rb ,using the [class|module]_eval method on something. For instance, I?m changing what gets faceted in the Searchable concern this way in plugin_init.rb: Searchable.module_eval do def set_up_and_run_search(default_types = [],default_facets=[],default_search_opts={}, params={}) ~ my stuff here ~~ end end I?m adding methods to controllers in a somewhat similar way, for instance, in plugin_init.rb, I?ve got: # add a digital only action to the resources controller class ResourcesController def digital_only uri = "/repositories/#{params[:rid]}/resources/#{params[:id]}" begin ~ etc. ~ end end Hope this helps, Bobbi From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Flanagan, Patrick Sent: Thursday, December 21, 2017 3:27 PM To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>> Subject: [Archivesspace_Users_Group] Overriding/Extending the new public interface in 2.2.0 Hello, I'm attempting to write a plugin that will modify the way the breadcrumb trail (shown in the new public UI) is generated to include more detail. I decided to try and override one of the files in the controller part of the architecture: resources_controller.rb, since I can see the :crumb being defined there. However, either my path is wrong, or the new UI isn't utilizing it. Following the instructions here:http://archivesspace.github.io/archivesspace/user/archivesspace-plug-ins-readme/<https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.github.io_archivesspace_user_archivesspace-2Dplug-2Dins-2Dreadme_&d=DwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=5xWUzLrZrVLeTqs3CDoeRpPtLv1fRM04CCu4TDULrSY&m=3DmZ4KyjSuOHTC-7rfq8Dv2MTeEFEBci91sKzca-4YQ&s=is5OAKKChee55MtdTuQYDj2OwuvI8f0Y6lBLS8-ast8&e=> I've placed the file in the following directory: as220/plugins/local/public/controllers/resources_controller.rb ( source location: /public/app/controllers/resources_controller.rb ) Plugin Config: AppConfig[:plugins] = ['local', 'lcnaf', 'aspace-public-formats'] If I'm not mistaken that document indicates that this is something that can be overridden, but I'm suspecting I can't actually override something in the controller from a plugin. The version is 2.2.0, running on Linux x64, openjdk version "1.8.0_151". Any advice would be appreciated! Thank you, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171222/4d906438/attachment.html>