From Christine.Kim at lyrasis.org Fri Jun 1 09:56:32 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Fri, 1 Jun 2018 13:56:32 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - May 2018 In-Reply-To: References: Message-ID: Correction: The webinar "Transforming XSL to EAD: Importing Component Hierarchies" will be on June 27 at 1-2:30pm ET (10-11:30am PT). Thank you! Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_uac-bounces at lyralists.lyrasis.org [mailto:archivesspace_uac-bounces at lyralists.lyrasis.org] On Behalf Of Christine Kim Sent: Thursday, May 31, 2018 3:35 PM To: Archivesspace Users Group ; Archivesspace Member Reps ; Archivesspace_tac at lyralists.lyrasis.org; Archivesspace_uac at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org Subject: [Archivesspace_uac] ArchivesSpace Update - May 2018 [ASpaceOrgHome.jpg] May 2018 Update We are excited to share exciting community updates, including updates on regional forums and the upcoming 4th annual Member Forum. New stories are up on the blog, and we have another great webinar coming up in June! Read on for more news! Development The ArchivesSpace team is pleased to announce a release candidate for our next version. It is available at https://github.com/archivesspace/archivesspace/releases/tag/v2.4.0-RC1. This release candidate includes improvements to the search results screen in the staff interface (including new columns for the identifier and the result context), updates to the mapping and a new option for our built-in MARCXML exporter for resources, a new option to search subjects in the PUI, and updates to the French translations. There are also fixes to some bugs with permissions, the OAI-PMH responder, an erroneous error message in the PUI when using the back button with some browsers, and orphaned instance records being created when digital objects were deleted. Please try this release candidate out and let us know by June 6 at ArchivesSpaceHome at lyrasis.org if you notice any problems with the specific areas that are addressed in this release, or if anything that was working before no longer is. Barring major issues, we expect to release 2.4.0 next week. We expect to put out a PUI search improvement-specific release later in June pending further internal testing. Annual Member Forum: August 14, 2018, in Washington D.C. ArchivesSpace will be holding its fourth annual Member Forum on August 14, 2018 at the Josephine Butler Parks Center in Washington, DC. Washington Parks & People is the capital's hub for activating public lands & waters for broad community revitalization, with a mission to grow city-wide park-based community health & vitality by nurturing innovation & partnerships. We are thrilled to have our annual forum held at this location. Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. More information on the developing program is on the ArchivesSpace wiki at https://archivesspace.atlassian.net/wiki/display/ADC/ArchivesSpace+Member+Forum+2018. The planning group is looking for speakers to cover a range of topics. There is a short Google submission form available at https://goo.gl/forms/6L9UsylUz5u2Ws5n1; you can submit ideas or volunteer yourself to speak. Proposals, ideas, and suggestions received by June 26 will receive priority consideration so that we can get the program squared away as soon as possible. You will receive a response by July 13. If you have any questions or other suggestions at this point, please feel free to email Kim at christine.kim at lyrasis.org. Registration for the Member Forum will open early July. Thanks in advance for your help in making this a great event! Webinar: Transforming XSL to EAD: Importing Component Hierarchies: June 27 at 1-2:30pm ET (10-11:30am PT) Do you list out your components on a spreadsheet before committing the item records into ArchivesSpace? If this is your preferred processing workflow, you're not alone. In this webinar, we will look at three distinct methods to get your spreadsheet lists into your ArchivesSpace resource record to populate components. Elizabeth Perkes (Utah State Archives) will demonstrate a workflow that uses built-in Microsoft Office tools to convert Microsoft Excel spreadsheets to EAD via mail merge. Jason Ronallo (North Carolina State University) will provide a demo of the STEAD schema and STEADY tool. And Ben Johnson (Harvard Business School) uses a spreadsheet importer plugin developed by Bobbi Fox (Harvard University) in a variety of ways. However, he will provide an overview of one simple use of the tool: How to easily and quickly add bulk data from new accessions to existing resources. Ben will walk through our workflow for that and show some limitations and pitfalls to avoid. But perhaps you would like to see more than just workflows. Kelly Spring (East Carolina University) will provide insight into some of the common troubleshooting and other tasks that will help you successfully upload the EAD to ArchivesSpace. Please join us on June 27, 2018 at 1-2:30pm ET (10-11:30am PT) as Elizabeth, Jason, Ben, and Kelly share a variety of practices to import your spreadsheet contents into ArchivesSpace. Please feel free to bring any questions you have. The webinar will be available through: http://lyrasis.adobeconnect.com/ruio9pyqjot4/ and the recording will be available at a later date on the ArchivesSpace YouTube channel: https://www.youtube.com/channel/UCxR6D-UlSx6N6UWTeqHTjzA. 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. We look forward to seeing you at the webinar! Regional Forum Updates ArchivesSpace regional forums are opportunities for our diverse ArchivesSpace members to meet up more locally to share and learn from each other through program content shaped by the community. Upcoming: SoCal Regional Forum: June 28, 2018 at University of California, Irvine * Registration is open until June 27th. But register by June 5th to cast your vote for the afternoon activity: https://www.eventbrite.com/e/archivesspace-regional-forum-southern-california-2018-tickets-44930947674 * Call for lightning round speakers: The SoCal Regional Forum Working Group is seeking proposals for a lightning round session. Presentations will be capped at 5 minutes and topics can be on anything related to your work using, developing, implementing, or actively contributing to the ArchivesSpace application and community. Submit a short proposal at https://goo.gl/forms/zowXsJvLWBPa0Bts1 by Thursday, May 31, 2018. * The program is taking shape! Keep up to date: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/533168147/SoCal+Regional+Forum Past: Boston Regional Forum: May 3, 2018 at Tufts University Thanks to all who attended and made the Boston Regional Forum such a lively event! Do you have photos to share? Please feel free to add them to this google drive folder: https://goo.gl/LKUeWv * Notes: Links to the notes are up on the wiki. Do you have notes you'd like to share? Please add them to this google drive folder: https://goo.gl/yHq7dQ * Slides: All presentation slides are also up on the wiki, including slides from the plug-ins overview workshop: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/455213059/Boston+Regional+Forum+-+May+2018 If you have any questions or ideas about regional forums, feel free to email Kim at christine.kim at lyrasis.org. New Stories on the Blog In All About Community (http://archivesspace.org/category/all-about-community/), Scott Hanrath (Assistant Dean for Digital Initiatives and Discovery Services, University of Kansas Libraries) provides insight into the Technical Documentation sub-team. This is a continuation of a series looking into the various sub-teams of the Technical Advisory Council and User Advisory Council to provide insight into the variety of activities and initiatives undertaken by these groups. In User Insights (http://archivesspace.org/category/user-insights/), Adrienne Harling (Archivist, San Francisco Symphony) shares on her experience successfully organizing an ArchivesSpace workshop for smaller institutions in her region. We would love to include your ArchivesSpace stories on the blog! If you would like to contribute, please email Kim at christine.kim at lyrasis.org. Change in Membership Level Criteria for Free-Standing and Non-Academic Archives The ArchivesSpace Governance Board recently approved a change in our membership level criteria for free-standing and non-academic archives. Beginning with the 2018/2019 membership term, which starts July 1, the membership level criteria for these types of archives will be as follows: Free-Standing or Non-Academic Archives: JSTOR or Artstor Classification Total FTE Staff (only for those without a JSTOR or Artstor Classification) ArchivesSpace Level Annual Fee Very Large 401+ Very Large $7500 Large 301-400 Large $5000 Medium 151-300 Medium $3000 Small 51-150 Small $1000 Very Small 0-50 Very Small $300 This represents higher FTE thresholds across the board for free-standing and non-academic institutions, which may mean that some institutions that were previously classified at a higher level will now be classified at a lower level. This change does not affect academic institutions, anyone with a JSTOR or Artstor classification, or those that were already classified at the Very Small level. Our membership benefits continue to be the same at every level. ArchivesSpace membership provides for the long-term development and sustainability of the application, and our intent is to give institutions of all sizes and types the ability to contribute toward its future and participate in our community. We very much hope this policy change will encourage certain types of institutions that found it difficult to participate under the previous classification system for free-standing and non-academic archives to join us. Membership Update We are excited to welcome our newest members to our community! Our new members since April 30 include: * California State University, Sacramento * Indiana University of Pennsylvania * Newman University (Wichita, Kansas) * Saint Mary's College of California (Moraga, California) As of May 31, we have 362 General members, 19 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. ________________________________ ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA's Collection Management Tools Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 19952 bytes Desc: image001.jpg URL: From matt.lawson at uni.edu Mon Jun 4 11:08:50 2018 From: matt.lawson at uni.edu (Matthew Lawson) Date: Mon, 4 Jun 2018 10:08:50 -0500 Subject: [Archivesspace_Users_Group] Staff login page problems Message-ID: We just migrated to 2.2.2 but the staff logon page has problems. It displays some mixed messages: Login attempt failed Login Successful. Redirecting.... but more importantly, the login button seems to do nothing. -Matt Lawson University of Northern Iowa -------------- next part -------------- An HTML attachment was scrubbed... URL: From mhughes at library.ucla.edu Mon Jun 4 15:49:46 2018 From: mhughes at library.ucla.edu (Hughes, Margaret) Date: Mon, 4 Jun 2018 19:49:46 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List In-Reply-To: References: Message-ID: Thanks so much for your response, Seth, and for including an example of the functionality you?d like to see in a CONTENTdm/ASpace integration. I?ve added it to our list! I?ve heard from others off-list, and so far our ?integrations wish list? includes: ? CONTENTdm x2 ? Trello ? ILS x2 Please reach out (on- or off-list) if you have an ASpace integration you?d like to see! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Seth Shaw Sent: Tuesday, May 29, 2018 10:08 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Something that came up in the recent community call is the ability to connect ArchivesSpace to digital asset management systems (e.g. CONTENTdm). For example, we use a script[1] to find all of the objects in CONTENTdm that match the title, date, and collection identifier fields to create ArchivesSpace digital objects + instances so that the AS EAD and PDF exports will link to our objects in CONTENTdm. Granted, this title/date matching wasn't perfect, but 97% was close enough that the remaining 14 could be easily reviewed manually. This sure beats making a few thousand, or even a few hundred manual digital object records. Of course, I'm running this script on my own computer which isn't an ideal workflow. It would be better if this were a plugin with a drop-down menu button and configuration screen so that ArchivesSpace users can initiate the matching and import on their own. If someone wants to port the code to Ruby, make the necessary configuration pages, and/or generally improve it; I think there are plenty of people who would appreciate it. 1: https://github.com/seth-shaw-unlv/small-stuff/blob/master/cdm-update-as/cdm_link_as.py On Tue, May 29, 2018 at 9:47 AM, Hughes, Margaret > wrote: Hi all, The Integrations sub-team of TAC (Technical Advisory Council) is interested in hearing about your most desired ArchivesSpace integrations. What other systems and software do you wish ASpace could talk to? This could be anything ? large or small, common or uncommon. Trello, your ILS, Slack, etc etc ? whatever comes to mind! Send your replies on- or off-list. Any input is much appreciated! Thank you, Maggie, on behalf of the TAC Integrations sub-team ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 _______________________________________________ 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 buschedw at msu.edu Tue Jun 5 10:28:03 2018 From: buschedw at msu.edu (Busch, Ed) Date: Tue, 5 Jun 2018 14:28:03 +0000 Subject: [Archivesspace_Users_Group] implementing lcnaf plugin Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164A839A7@CAD-EX01.campusad.msu.edu> What's required to implement the LCNAF Plugin? I see the line in config.rb but what' "3rd party services" are required? Is implementing this plugin described somewhere? Thanks! Ed Busch Electronic Records Archivist MSU Archives Conrad Hall, Room 101 888 Wilson Road East Lansing, MI 48824 517-884-6438 From PGalligan at rockarch.org Tue Jun 5 10:32:09 2018 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Tue, 5 Jun 2018 14:32:09 +0000 Subject: [Archivesspace_Users_Group] Tell us about your integrations Message-ID: All, Besides gathering information about desired integrations, the TAC integrations subteam is interested in hearing you talk about an integration you?re currently working on. Doing integrations work currently? Planning to start an integration? We want to hear about it. Integrations would love to have you on one of our monthly calls to talk about how we can help you with your work. Shoot me an email off list (pgalligan at rockarch.org) if you?re interested! We tried this with Litchfield Historical Society and thought it?d be great to get more people involved. Thanks, Patrick Galligan Integrations Chair -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Tue Jun 5 10:44:45 2018 From: livsolis at utexas.edu (Olivia S Solis) Date: Tue, 5 Jun 2018 09:44:45 -0500 Subject: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List In-Reply-To: References: Message-ID: Hi all, So this is probably hyperspecific to our needs, but 1) Islandora integration that can deal with a very detailed MODS form. We are aware that there is an existing module, but it uses the ASpace fields to populate Islandora (at least when we tested it), and our Islandora XML form is way more complex than ASpace. 2) I manage taxonomy lists with both local and external controlled vocabularies outside ASpace, as they apply to both ASpace and Islandora. I'm not sure how unique we are. Eventually, I will want to publish to iQVoc or some taxonomy management system. integration with that system would be great so that I could post new subject/agent terms to ASpace with the click of a button. (This may be too nebulous) 3) In the mean time, I'm managing them in Google Sheets, temporarily assigning local terms a local identifier (until we can get them URIs). It would be great to have some kind of CSV uploader for new subject/agent records, one that would spit back the ASpace ID so I could easily add them to the existing Google Sheets lists. Thanks, Olivia On Mon, Jun 4, 2018 at 2:49 PM, Hughes, Margaret wrote: > Thanks so much for your response, Seth, and for including an example of > the functionality you?d like to see in a CONTENTdm/ASpace integration. I?ve > added it to our list! > > > > I?ve heard from others off-list, and so far our ?integrations wish list? > includes: > > ? CONTENTdm x2 > > ? Trello > > ? ILS x2 > > > > Please reach out (on- or off-list) if you have an ASpace integration you?d > like to see! > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Seth > Shaw > *Sent:* Tuesday, May 29, 2018 10:08 AM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace Integrations > Wish List > > > > Something that came up in the recent community call is the ability to > connect ArchivesSpace to digital asset management systems (e.g. CONTENTdm). > > > > For example, we use a script[1] to find all of the objects in CONTENTdm > that match the title, date, and collection identifier fields to create > ArchivesSpace digital objects + instances so that the AS EAD and PDF > exports will link to our objects in CONTENTdm. Granted, this title/date > matching wasn't perfect, but 97% was close enough that the remaining 14 > could be easily reviewed manually. This sure beats making a few thousand, > or even a few hundred manual digital object records. > > > > Of course, I'm running this script on my own computer which isn't an ideal > workflow. It would be better if this were a plugin with a drop-down menu > button and configuration screen so that ArchivesSpace users can initiate > the matching and import on their own. If someone wants to port the code to > Ruby, make the necessary configuration pages, and/or generally improve it; > I think there are plenty of people who would appreciate it. > > > > 1: https://github.com/seth-shaw-unlv/small-stuff/blob/ > master/cdm-update-as/cdm_link_as.py > > > > On Tue, May 29, 2018 at 9:47 AM, Hughes, Margaret < > mhughes at library.ucla.edu> wrote: > > Hi all, > > > > The Integrations sub-team of TAC (Technical Advisory Council) is > interested in hearing about your most desired ArchivesSpace integrations. > What other systems and software do you wish ASpace could talk to? This > could be anything ? large or small, common or uncommon. Trello, your ILS, > Slack, etc etc ? whatever comes to mind! > > > > Send your replies on- or off-list. Any input is much appreciated! > > > > Thank you, > > > > Maggie, on behalf of the TAC Integrations sub-team > > > > > > ---------------------------------- > > Margaret Hughes > > Collections Data Archivist > > 310.206.6203 > > > > UCLA Library Special Collections > > A1713 Charles E. Young Research Library > > Los Angeles, CA 90095-1575 > > > > > _______________________________________________ > 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 > > -- 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 Kevin.Clair at du.edu Tue Jun 5 13:37:45 2018 From: Kevin.Clair at du.edu (Kevin Clair) Date: Tue, 5 Jun 2018 17:37:45 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List In-Reply-To: References: Message-ID: <8277C5A9-9BBD-4AD8-A6AA-1A24B1E497DA@du.edu> I can?t remember if I?ve mentioned this on-list, but on the topic of the ILS, we?ve started on some rudimentary Alma integrations for ArchivesSpace: https://github.com/duspeccoll/alma_integrations The way we have it implemented is: we?ve assigned a user-defined field to Alma MMS IDs for each Resource we have. The Alma Integrations plugin takes as input a linked resource and checks that field to see if an MMS ID exists. If it finds one you have the option to push new bibliographic metadata (using the MARC exporter) to Alma, or to add new holdings (using a controlled list of DU holdings codes). If it doesn?t find one, you have the option to create a new BIB and assign whatever MMS ID Alma creates to the user-defined field automatically. It doesn?t do anything to link AS Top Containers with Alma items yet, but that?s the next step. Happy to talk about this more and get more use cases for it in whatever medium people like! -k From: on behalf of "Hughes, Margaret" Reply-To: Archivesspace Group Date: Monday, June 4, 2018 at 1:49 PM To: Archivesspace Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Thanks so much for your response, Seth, and for including an example of the functionality you?d like to see in a CONTENTdm/ASpace integration. I?ve added it to our list! I?ve heard from others off-list, and so far our ?integrations wish list? includes: * CONTENTdm x2 * Trello * ILS x2 Please reach out (on- or off-list) if you have an ASpace integration you?d like to see! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Seth Shaw Sent: Tuesday, May 29, 2018 10:08 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Something that came up in the recent community call is the ability to connect ArchivesSpace to digital asset management systems (e.g. CONTENTdm). For example, we use a script[1] to find all of the objects in CONTENTdm that match the title, date, and collection identifier fields to create ArchivesSpace digital objects + instances so that the AS EAD and PDF exports will link to our objects in CONTENTdm. Granted, this title/date matching wasn't perfect, but 97% was close enough that the remaining 14 could be easily reviewed manually. This sure beats making a few thousand, or even a few hundred manual digital object records. Of course, I'm running this script on my own computer which isn't an ideal workflow. It would be better if this were a plugin with a drop-down menu button and configuration screen so that ArchivesSpace users can initiate the matching and import on their own. If someone wants to port the code to Ruby, make the necessary configuration pages, and/or generally improve it; I think there are plenty of people who would appreciate it. 1: https://github.com/seth-shaw-unlv/small-stuff/blob/master/cdm-update-as/cdm_link_as.py On Tue, May 29, 2018 at 9:47 AM, Hughes, Margaret > wrote: Hi all, The Integrations sub-team of TAC (Technical Advisory Council) is interested in hearing about your most desired ArchivesSpace integrations. What other systems and software do you wish ASpace could talk to? This could be anything ? large or small, common or uncommon. Trello, your ILS, Slack, etc etc ? whatever comes to mind! Send your replies on- or off-list. Any input is much appreciated! Thank you, Maggie, on behalf of the TAC Integrations sub-team ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 _______________________________________________ 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 benn.joseph at northwestern.edu Tue Jun 5 14:43:36 2018 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Tue, 5 Jun 2018 18:43:36 +0000 Subject: [Archivesspace_Users_Group] implementing lcnaf plugin In-Reply-To: <35E2A8E8997F6C48A5D5FC21602BDEB60164A839A7@CAD-EX01.campusad.msu.edu> References: <35E2A8E8997F6C48A5D5FC21602BDEB60164A839A7@CAD-EX01.campusad.msu.edu> Message-ID: <5366a857261749b791bdafd7e40fd5d5@evcspmbx04.ads.northwestern.edu> I'm curious about this too--here's the ticket, which is marked as resolved: https://archivesspace.atlassian.net/browse/ANW-148 There's a note from Christine on April 20 about it working now, but it still isn't working for us. Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Busch, Ed Sent: Tuesday, June 05, 2018 9:28 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] implementing lcnaf plugin What's required to implement the LCNAF Plugin? I see the line in config.rb but what' "3rd party services" are required? Is implementing this plugin described somewhere? Thanks! Ed Busch Electronic Records Archivist MSU Archives Conrad Hall, Room 101 888 Wilson Road East Lansing, MI 48824 517-884-6438 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=Kxgh0ADDfnY3Gohe40JeSLmDPMe9KpP-JaK84583qyg&s=3QIPpcYGL6RAtLdx0YoFCTCKmbhvV7pj6OloOp0G47s&e= From buschedw at msu.edu Tue Jun 5 14:51:29 2018 From: buschedw at msu.edu (Busch, Ed) Date: Tue, 5 Jun 2018 18:51:29 +0000 Subject: [Archivesspace_Users_Group] implementing lcnaf plugin In-Reply-To: <5366a857261749b791bdafd7e40fd5d5@evcspmbx04.ads.northwestern.edu> References: <35E2A8E8997F6C48A5D5FC21602BDEB60164A839A7@CAD-EX01.campusad.msu.edu> <5366a857261749b791bdafd7e40fd5d5@evcspmbx04.ads.northwestern.edu> Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164A83CFF@CAD-EX01.campusad.msu.edu> Dallas Pillen pointed out to me that the LC site http://id.loc.gov/authorities/names is actually not working. I wrongly assumed there was more to making the plugin work. The OCLC site appears to be completely gone. Ed Busch Electronic Records Archivist MSU Archives -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Benn Joseph Sent: Tuesday, June 5, 2018 2:44 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] implementing lcnaf plugin I'm curious about this too--here's the ticket, which is marked as resolved: https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D148&d=DwICAg&c=nE__W8dFE-shTxStwXtp0A&r=nzQRpzss_AwHOHAKVWRsNQ&m=omUHlg6rxeBbKLuejb_iZYP3maZJbyTgK05X3cBPGIw&s=rijIbSKUm2fx1RwzcP3Deoccyoel7a7Gwl2lMm1qf-c&e= There's a note from Christine on April 20 about it working now, but it still isn't working for us. Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Busch, Ed Sent: Tuesday, June 05, 2018 9:28 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] implementing lcnaf plugin What's required to implement the LCNAF Plugin? I see the line in config.rb but what' "3rd party services" are required? Is implementing this plugin described somewhere? Thanks! Ed Busch Electronic Records Archivist MSU Archives Conrad Hall, Room 101 888 Wilson Road East Lansing, MI 48824 517-884-6438 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=Kxgh0ADDfnY3Gohe40JeSLmDPMe9KpP-JaK84583qyg&s=3QIPpcYGL6RAtLdx0YoFCTCKmbhvV7pj6OloOp0G47s&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=nE__W8dFE-shTxStwXtp0A&r=nzQRpzss_AwHOHAKVWRsNQ&m=omUHlg6rxeBbKLuejb_iZYP3maZJbyTgK05X3cBPGIw&s=n4knAZ35DkfZPBajWZy3FytlVgLNSgV1iY7I4iVRqOc&e= From buschedw at msu.edu Tue Jun 5 14:54:20 2018 From: buschedw at msu.edu (Busch, Ed) Date: Tue, 5 Jun 2018 18:54:20 +0000 Subject: [Archivesspace_Users_Group] implementing lcnaf plugin In-Reply-To: <5366a857261749b791bdafd7e40fd5d5@evcspmbx04.ads.northwestern.edu> References: <35E2A8E8997F6C48A5D5FC21602BDEB60164A839A7@CAD-EX01.campusad.msu.edu> <5366a857261749b791bdafd7e40fd5d5@evcspmbx04.ads.northwestern.edu> Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164A83D0F@CAD-EX01.campusad.msu.edu> Follow up- ASPace shouldn't of closed the ticket https://archivesspace.atlassian.net/browse/ANW-148 . The plugin should have the OCLC part removed since they reported it was no longer supported. Ed Busch Electronic Records Archivist MSU Archives -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Benn Joseph Sent: Tuesday, June 5, 2018 2:44 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] implementing lcnaf plugin I'm curious about this too--here's the ticket, which is marked as resolved: https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D148&d=DwICAg&c=nE__W8dFE-shTxStwXtp0A&r=nzQRpzss_AwHOHAKVWRsNQ&m=omUHlg6rxeBbKLuejb_iZYP3maZJbyTgK05X3cBPGIw&s=rijIbSKUm2fx1RwzcP3Deoccyoel7a7Gwl2lMm1qf-c&e= There's a note from Christine on April 20 about it working now, but it still isn't working for us. Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Busch, Ed Sent: Tuesday, June 05, 2018 9:28 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] implementing lcnaf plugin What's required to implement the LCNAF Plugin? I see the line in config.rb but what' "3rd party services" are required? Is implementing this plugin described somewhere? Thanks! Ed Busch Electronic Records Archivist MSU Archives Conrad Hall, Room 101 888 Wilson Road East Lansing, MI 48824 517-884-6438 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=Kxgh0ADDfnY3Gohe40JeSLmDPMe9KpP-JaK84583qyg&s=3QIPpcYGL6RAtLdx0YoFCTCKmbhvV7pj6OloOp0G47s&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=nE__W8dFE-shTxStwXtp0A&r=nzQRpzss_AwHOHAKVWRsNQ&m=omUHlg6rxeBbKLuejb_iZYP3maZJbyTgK05X3cBPGIw&s=n4knAZ35DkfZPBajWZy3FytlVgLNSgV1iY7I4iVRqOc&e= From robin_mcelheny at harvard.edu Tue Jun 5 16:14:04 2018 From: robin_mcelheny at harvard.edu (McElheny, Robin G.) Date: Tue, 5 Jun 2018 20:14:04 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List In-Reply-To: <8277C5A9-9BBD-4AD8-A6AA-1A24B1E497DA@du.edu> References: <8277C5A9-9BBD-4AD8-A6AA-1A24B1E497DA@du.edu> Message-ID: Here at Harvard we are moving to Alma so integrations for ArchivesSpace are of great interest. Not sure we?re ready to concentrate on use cases just yet but we?d love to hear more about what folks at Duke are doing. Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Kevin Clair Sent: Tuesday, June 05, 2018 1:38 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List I can?t remember if I?ve mentioned this on-list, but on the topic of the ILS, we?ve started on some rudimentary Alma integrations for ArchivesSpace: https://github.com/duspeccoll/alma_integrations The way we have it implemented is: we?ve assigned a user-defined field to Alma MMS IDs for each Resource we have. The Alma Integrations plugin takes as input a linked resource and checks that field to see if an MMS ID exists. If it finds one you have the option to push new bibliographic metadata (using the MARC exporter) to Alma, or to add new holdings (using a controlled list of DU holdings codes). If it doesn?t find one, you have the option to create a new BIB and assign whatever MMS ID Alma creates to the user-defined field automatically. It doesn?t do anything to link AS Top Containers with Alma items yet, but that?s the next step. Happy to talk about this more and get more use cases for it in whatever medium people like! -k From: > on behalf of "Hughes, Margaret" > Reply-To: Archivesspace Group > Date: Monday, June 4, 2018 at 1:49 PM To: Archivesspace Group > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Thanks so much for your response, Seth, and for including an example of the functionality you?d like to see in a CONTENTdm/ASpace integration. I?ve added it to our list! I?ve heard from others off-list, and so far our ?integrations wish list? includes: * CONTENTdm x2 * Trello * ILS x2 Please reach out (on- or off-list) if you have an ASpace integration you?d like to see! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Seth Shaw Sent: Tuesday, May 29, 2018 10:08 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Something that came up in the recent community call is the ability to connect ArchivesSpace to digital asset management systems (e.g. CONTENTdm). For example, we use a script[1] to find all of the objects in CONTENTdm that match the title, date, and collection identifier fields to create ArchivesSpace digital objects + instances so that the AS EAD and PDF exports will link to our objects in CONTENTdm. Granted, this title/date matching wasn't perfect, but 97% was close enough that the remaining 14 could be easily reviewed manually. This sure beats making a few thousand, or even a few hundred manual digital object records. Of course, I'm running this script on my own computer which isn't an ideal workflow. It would be better if this were a plugin with a drop-down menu button and configuration screen so that ArchivesSpace users can initiate the matching and import on their own. If someone wants to port the code to Ruby, make the necessary configuration pages, and/or generally improve it; I think there are plenty of people who would appreciate it. 1: https://github.com/seth-shaw-unlv/small-stuff/blob/master/cdm-update-as/cdm_link_as.py On Tue, May 29, 2018 at 9:47 AM, Hughes, Margaret > wrote: Hi all, The Integrations sub-team of TAC (Technical Advisory Council) is interested in hearing about your most desired ArchivesSpace integrations. What other systems and software do you wish ASpace could talk to? This could be anything ? large or small, common or uncommon. Trello, your ILS, Slack, etc etc ? whatever comes to mind! Send your replies on- or off-list. Any input is much appreciated! Thank you, Maggie, on behalf of the TAC Integrations sub-team ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 _______________________________________________ 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 lsaegert at tsl.texas.gov Tue Jun 5 16:42:02 2018 From: lsaegert at tsl.texas.gov (Laura Saegert) Date: Tue, 5 Jun 2018 20:42:02 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List In-Reply-To: References: <8277C5A9-9BBD-4AD8-A6AA-1A24B1E497DA@du.edu> Message-ID: Has anyone done or is planning to do integrations with Preservica? From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of McElheny, Robin G. Sent: Tuesday, June 5, 2018 3:14 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Here at Harvard we are moving to Alma so integrations for ArchivesSpace are of great interest. Not sure we?re ready to concentrate on use cases just yet but we?d love to hear more about what folks at Duke are doing. Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Kevin Clair Sent: Tuesday, June 05, 2018 1:38 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List I can?t remember if I?ve mentioned this on-list, but on the topic of the ILS, we?ve started on some rudimentary Alma integrations for ArchivesSpace: https://github.com/duspeccoll/alma_integrations The way we have it implemented is: we?ve assigned a user-defined field to Alma MMS IDs for each Resource we have. The Alma Integrations plugin takes as input a linked resource and checks that field to see if an MMS ID exists. If it finds one you have the option to push new bibliographic metadata (using the MARC exporter) to Alma, or to add new holdings (using a controlled list of DU holdings codes). If it doesn?t find one, you have the option to create a new BIB and assign whatever MMS ID Alma creates to the user-defined field automatically. It doesn?t do anything to link AS Top Containers with Alma items yet, but that?s the next step. Happy to talk about this more and get more use cases for it in whatever medium people like! -k From: > on behalf of "Hughes, Margaret" > Reply-To: Archivesspace Group > Date: Monday, June 4, 2018 at 1:49 PM To: Archivesspace Group > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Thanks so much for your response, Seth, and for including an example of the functionality you?d like to see in a CONTENTdm/ASpace integration. I?ve added it to our list! I?ve heard from others off-list, and so far our ?integrations wish list? includes: * CONTENTdm x2 * Trello * ILS x2 Please reach out (on- or off-list) if you have an ASpace integration you?d like to see! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Seth Shaw Sent: Tuesday, May 29, 2018 10:08 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Something that came up in the recent community call is the ability to connect ArchivesSpace to digital asset management systems (e.g. CONTENTdm). For example, we use a script[1] to find all of the objects in CONTENTdm that match the title, date, and collection identifier fields to create ArchivesSpace digital objects + instances so that the AS EAD and PDF exports will link to our objects in CONTENTdm. Granted, this title/date matching wasn't perfect, but 97% was close enough that the remaining 14 could be easily reviewed manually. This sure beats making a few thousand, or even a few hundred manual digital object records. Of course, I'm running this script on my own computer which isn't an ideal workflow. It would be better if this were a plugin with a drop-down menu button and configuration screen so that ArchivesSpace users can initiate the matching and import on their own. If someone wants to port the code to Ruby, make the necessary configuration pages, and/or generally improve it; I think there are plenty of people who would appreciate it. 1: https://github.com/seth-shaw-unlv/small-stuff/blob/master/cdm-update-as/cdm_link_as.py On Tue, May 29, 2018 at 9:47 AM, Hughes, Margaret > wrote: Hi all, The Integrations sub-team of TAC (Technical Advisory Council) is interested in hearing about your most desired ArchivesSpace integrations. What other systems and software do you wish ASpace could talk to? This could be anything ? large or small, common or uncommon. Trello, your ILS, Slack, etc etc ? whatever comes to mind! Send your replies on- or off-list. Any input is much appreciated! Thank you, Maggie, on behalf of the TAC Integrations sub-team ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 _______________________________________________ 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 buschedw at msu.edu Wed Jun 6 08:07:46 2018 From: buschedw at msu.edu (Busch, Ed) Date: Wed, 6 Jun 2018 12:07:46 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List In-Reply-To: References: <8277C5A9-9BBD-4AD8-A6AA-1A24B1E497DA@du.edu> Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164A84683@CAD-EX01.campusad.msu.edu> Preservica has been integrated with ArchivesSpace. https://preservica.com/digital-archive-software/automated-content-acquisition . I haven?t tried it yet so can?t speak to how well. Ed Busch Electronic Records Archivist MSU Archives From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Laura Saegert Sent: Tuesday, June 5, 2018 4:42 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Has anyone done or is planning to do integrations with Preservica? From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of McElheny, Robin G. Sent: Tuesday, June 5, 2018 3:14 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Here at Harvard we are moving to Alma so integrations for ArchivesSpace are of great interest. Not sure we?re ready to concentrate on use cases just yet but we?d love to hear more about what folks at Duke are doing. Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Kevin Clair Sent: Tuesday, June 05, 2018 1:38 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List I can?t remember if I?ve mentioned this on-list, but on the topic of the ILS, we?ve started on some rudimentary Alma integrations for ArchivesSpace: https://github.com/duspeccoll/alma_integrations The way we have it implemented is: we?ve assigned a user-defined field to Alma MMS IDs for each Resource we have. The Alma Integrations plugin takes as input a linked resource and checks that field to see if an MMS ID exists. If it finds one you have the option to push new bibliographic metadata (using the MARC exporter) to Alma, or to add new holdings (using a controlled list of DU holdings codes). If it doesn?t find one, you have the option to create a new BIB and assign whatever MMS ID Alma creates to the user-defined field automatically. It doesn?t do anything to link AS Top Containers with Alma items yet, but that?s the next step. Happy to talk about this more and get more use cases for it in whatever medium people like! -k From: > on behalf of "Hughes, Margaret" > Reply-To: Archivesspace Group > Date: Monday, June 4, 2018 at 1:49 PM To: Archivesspace Group > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Thanks so much for your response, Seth, and for including an example of the functionality you?d like to see in a CONTENTdm/ASpace integration. I?ve added it to our list! I?ve heard from others off-list, and so far our ?integrations wish list? includes: * CONTENTdm x2 * Trello * ILS x2 Please reach out (on- or off-list) if you have an ASpace integration you?d like to see! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Seth Shaw Sent: Tuesday, May 29, 2018 10:08 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List Something that came up in the recent community call is the ability to connect ArchivesSpace to digital asset management systems (e.g. CONTENTdm). For example, we use a script[1] to find all of the objects in CONTENTdm that match the title, date, and collection identifier fields to create ArchivesSpace digital objects + instances so that the AS EAD and PDF exports will link to our objects in CONTENTdm. Granted, this title/date matching wasn't perfect, but 97% was close enough that the remaining 14 could be easily reviewed manually. This sure beats making a few thousand, or even a few hundred manual digital object records. Of course, I'm running this script on my own computer which isn't an ideal workflow. It would be better if this were a plugin with a drop-down menu button and configuration screen so that ArchivesSpace users can initiate the matching and import on their own. If someone wants to port the code to Ruby, make the necessary configuration pages, and/or generally improve it; I think there are plenty of people who would appreciate it. 1: https://github.com/seth-shaw-unlv/small-stuff/blob/master/cdm-update-as/cdm_link_as.py On Tue, May 29, 2018 at 9:47 AM, Hughes, Margaret > wrote: Hi all, The Integrations sub-team of TAC (Technical Advisory Council) is interested in hearing about your most desired ArchivesSpace integrations. What other systems and software do you wish ASpace could talk to? This could be anything ? large or small, common or uncommon. Trello, your ILS, Slack, etc etc ? whatever comes to mind! Send your replies on- or off-list. Any input is much appreciated! Thank you, Maggie, on behalf of the TAC Integrations sub-team ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 _______________________________________________ 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 mcallahan at smith.edu Wed Jun 6 08:41:31 2018 From: mcallahan at smith.edu (Maureen Callahan) Date: Wed, 6 Jun 2018 08:41:31 -0400 Subject: [Archivesspace_Users_Group] ArchivesSpace Integrations Wish List In-Reply-To: <35E2A8E8997F6C48A5D5FC21602BDEB60164A84683@CAD-EX01.campusad.msu.edu> References: <8277C5A9-9BBD-4AD8-A6AA-1A24B1E497DA@du.edu> <35E2A8E8997F6C48A5D5FC21602BDEB60164A84683@CAD-EX01.campusad.msu.edu> Message-ID: Something that I think would be useful from this group might be a set of principles and best practices for integrations. I know that both the RAC and the Bentley have done a lot of intellectual legwork to really think through which system should be the system of record for various types of information and how it should communicate, and I wonder if this could be generalizable to future integration work. For instance, when I worked with Mark Custer, Mary Caldera and Euan Cochrane on the Preservica integrations at Yale, we had splendid fights about where description should be authored and how granularly it should be represented in each system (I'm not 100% thrilled with how this worked out in Preservica, by the way -- URLs are stored in archival object records rather than the way I would like to see them as digital object records, and connecting aggregations of electronic records from Preservica to ArchivesSpace AOs isn't as sophisticated as I would like). I wonder if this group, after it has looked at all of these wished-for integrations, could provide feedback and guidance about how integrations should and shouldn't behave in accordance with archival description best practices. Thanks all, Maureen On Wed, Jun 6, 2018 at 8:07 AM, Busch, Ed wrote: > Preservica has been integrated with ArchivesSpace. https://preservica.com/ > digital-archive-software/automated-content-acquisition . I haven?t tried > it yet so can?t speak to how well. > > > > Ed Busch > > Electronic Records Archivist > > MSU Archives > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Laura > Saegert > *Sent:* Tuesday, June 5, 2018 4:42 PM > > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace Integrations > Wish List > > > > Has anyone done or is planning to do integrations with Preservica? > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *McElheny, > Robin G. > *Sent:* Tuesday, June 5, 2018 3:14 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace Integrations > Wish List > > > > Here at Harvard we are moving to Alma so integrations for ArchivesSpace > are of great interest. Not sure we?re ready to concentrate on use cases > just yet but we?d love to hear more about what folks at Duke are doing. > > > > Robin McElheny > > Associate University Archivist for Collections and Public Services > > Harvard University Archives > > Pusey Library > > Cambridge, MA 02138 > > Email: robin_mcelheny at harvard.edu > > Phone: 617-495-2461 > > Fax: 617-495-8011 > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Kevin > Clair > *Sent:* Tuesday, June 05, 2018 1:38 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace Integrations > Wish List > > > > I can?t remember if I?ve mentioned this on-list, but on the topic of the > ILS, we?ve started on some rudimentary Alma integrations for ArchivesSpace: > https://github.com/duspeccoll/alma_integrations > > > > > The way we have it implemented is: we?ve assigned a user-defined field to > Alma MMS IDs for each Resource we have. The Alma Integrations plugin takes > as input a linked resource and checks that field to see if an MMS ID > exists. If it finds one you have the option to push new bibliographic > metadata (using the MARC exporter) to Alma, or to add new holdings (using a > controlled list of DU holdings codes). If it doesn?t find one, you have the > option to create a new BIB and assign whatever MMS ID Alma creates to the > user-defined field automatically. > > > > It doesn?t do anything to link AS Top Containers with Alma items yet, but > that?s the next step. > > > > Happy to talk about this more and get more use cases for it in whatever > medium people like! -k > > > > *From: * on > behalf of "Hughes, Margaret" > *Reply-To: *Archivesspace Group lyralists.lyrasis.org> > *Date: *Monday, June 4, 2018 at 1:49 PM > *To: *Archivesspace Group > > *Subject: *Re: [Archivesspace_Users_Group] ArchivesSpace Integrations > Wish List > > > > Thanks so much for your response, Seth, and for including an example of > the functionality you?d like to see in a CONTENTdm/ASpace integration. I?ve > added it to our list! > > > > I?ve heard from others off-list, and so far our ?integrations wish list? > includes: > > - CONTENTdm x2 > - Trello > - ILS x2 > > > > Please reach out (on- or off-list) if you have an ASpace integration you?d > like to see! > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Seth > Shaw > *Sent:* Tuesday, May 29, 2018 10:08 AM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace Integrations > Wish List > > > > Something that came up in the recent community call is the ability to > connect ArchivesSpace to digital asset management systems (e.g. CONTENTdm). > > > > For example, we use a script[1] to find all of the objects in CONTENTdm > that match the title, date, and collection identifier fields to create > ArchivesSpace digital objects + instances so that the AS EAD and PDF > exports will link to our objects in CONTENTdm. Granted, this title/date > matching wasn't perfect, but 97% was close enough that the remaining 14 > could be easily reviewed manually. This sure beats making a few thousand, > or even a few hundred manual digital object records. > > > > Of course, I'm running this script on my own computer which isn't an ideal > workflow. It would be better if this were a plugin with a drop-down menu > button and configuration screen so that ArchivesSpace users can initiate > the matching and import on their own. If someone wants to port the code to > Ruby, make the necessary configuration pages, and/or generally improve it; > I think there are plenty of people who would appreciate it. > > > > 1: https://github.com/seth-shaw-unlv/small-stuff/blob/ > master/cdm-update-as/cdm_link_as.py > > > > > On Tue, May 29, 2018 at 9:47 AM, Hughes, Margaret < > mhughes at library.ucla.edu> wrote: > > Hi all, > > > > The Integrations sub-team of TAC (Technical Advisory Council) is > interested in hearing about your most desired ArchivesSpace integrations. > What other systems and software do you wish ASpace could talk to? This > could be anything ? large or small, common or uncommon. Trello, your ILS, > Slack, etc etc ? whatever comes to mind! > > > > Send your replies on- or off-list. Any input is much appreciated! > > > > Thank you, > > > > Maggie, on behalf of the TAC Integrations sub-team > > > > > > ---------------------------------- > > Margaret Hughes > > Collections Data Archivist > > 310.206.6203 > > > > UCLA Library Special Collections > > A1713 Charles E. Young Research Library > > Los Angeles, CA 90095-1575 > > > > > _______________________________________________ > 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 > > -- Maureen Callahan Sophia Smith Collection Archivist Smith College Special Collections Northampton, Massachusetts 01063 T. 413 585 2981 C. 215.863.1860 mcallahan at smith.edu Pronouns: she/her/hers Facebook: https://www.facebook.com/SophiaSmithCollection/ Instagram: https://www.instagram.com/smithlibraries/ Twitter: https://twitter.com/archivalagents *Please note*. Smith College Special Collections is now housed at Young Library . Learn more about renovations to Neilson Library here . -------------- next part -------------- An HTML attachment was scrubbed... URL: From kws2126 at columbia.edu Thu Jun 7 09:23:53 2018 From: kws2126 at columbia.edu (Kevin W. Schlottmann) Date: Thu, 7 Jun 2018 09:23:53 -0400 Subject: [Archivesspace_Users_Group] Syntax for merge_requests API call Message-ID: Hi all, I'm trying to use the API to POST a merge request[1]. The documentation is missing an example of what is actually posted. Before I dig too much deeper, does anyone know the syntax for the POST? Is it the entire JSON objects of the target and victim, in an array? Just the URIs? Something else? Best, Kevin [1] https://archivesspace.github.io/archivesspace/api/#post-merge_requests-agent -- Kevin Schlottmann Head of Archives Processing Rare Book & Manuscript Library Butler Library, Room 801 Columbia University 535 W. 114th St., New York, NY 10027 (212) 854-8483 From harnold at rockarch.org Thu Jun 7 11:43:53 2018 From: harnold at rockarch.org (Arnold, Hillel) Date: Thu, 7 Jun 2018 15:43:53 +0000 Subject: [Archivesspace_Users_Group] Syntax for merge_requests API call In-Reply-To: References: Message-ID: <5FBE7EE1-C38F-43C9-94F3-3A7CA736CB17@rockarch.org> Hi Kevin, It looks like you need to post a target URI plus an array of victims URIs to that endpoint, so something like: { "target" : {"ref": "/agents/corporate_entities/40"}, "victims": [ { "ref": "/agents/corporate_entities/38" }, { "ref": "/agents/corporate_entities/39" } ] } FWIW, I've found the JSONmodel schemas to be pretty useful in reverse-engineering API calls: https://github.com/archivesspace/archivesspace/tree/master/common/schemas Hillel ?On 6/7/18, 9:24 AM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kevin W. Schlottmann" wrote: Hi all, I'm trying to use the API to POST a merge request[1]. The documentation is missing an example of what is actually posted. Before I dig too much deeper, does anyone know the syntax for the POST? Is it the entire JSON objects of the target and victim, in an array? Just the URIs? Something else? Best, Kevin [1] https://archivesspace.github.io/archivesspace/api/#post-merge_requests-agent -- Kevin Schlottmann Head of Archives Processing Rare Book & Manuscript Library Butler Library, Room 801 Columbia University 535 W. 114th St., New York, NY 10027 (212) 854-8483 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From kws2126 at columbia.edu Thu Jun 7 12:13:27 2018 From: kws2126 at columbia.edu (Kevin W Schlottmann) Date: Thu, 7 Jun 2018 12:13:27 -0400 Subject: [Archivesspace_Users_Group] Syntax for merge_requests API call In-Reply-To: <5FBE7EE1-C38F-43C9-94F3-3A7CA736CB17@rockarch.org> References: <5FBE7EE1-C38F-43C9-94F3-3A7CA736CB17@rockarch.org> Message-ID: Perfect; thank you Hillel! > On Jun 7, 2018, at 11:43 AM, Arnold, Hillel wrote: > > Hi Kevin, > It looks like you need to post a target URI plus an array of victims URIs to that endpoint, so something like: > > { > "target" : {"ref": "/agents/corporate_entities/40"}, > "victims": [ > { "ref": "/agents/corporate_entities/38" }, > { "ref": "/agents/corporate_entities/39" } > ] > } > > FWIW, I've found the JSONmodel schemas to be pretty useful in reverse-engineering API calls: https://github.com/archivesspace/archivesspace/tree/master/common/schemas > > Hillel > > ?On 6/7/18, 9:24 AM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kevin W. Schlottmann" wrote: > > Hi all, > > I'm trying to use the API to POST a merge request[1]. The > documentation is missing an example of what is actually posted. > Before I dig too much deeper, does anyone know the syntax for the > POST? Is it the entire JSON objects of the target and victim, in an > array? Just the URIs? Something else? > > Best, > > Kevin > > [1] https://archivesspace.github.io/archivesspace/api/#post-merge_requests-agent > > -- > Kevin Schlottmann > Head of Archives Processing > Rare Book & Manuscript Library > Butler Library, Room 801 > Columbia University > 535 W. 114th St., New York, NY 10027 > (212) 854-8483 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > 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 christine.dibella at lyrasis.org Thu Jun 7 16:49:38 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 7 Jun 2018 20:49:38 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v2.4.0 released Message-ID: Hello ArchivesSpace members, The ArchivesSpace team is pleased to announce the availability of v2.4.0. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.4.0. This release contains many program-led and community pull requests that provide feature enhancements, bug fixes, infrastructure improvements, and documentation updates. Some items of note include improvements to the search results screen in the staff interface (including new columns for identifier and result context for archival objects), updates to the mapping and new options for our built-in MARCXML exporter for resources, a new option to search subjects in the PUI, and updates to the French translations. There are also fixes to some bugs with the OAI-PMH responder, an erroneous error message in the PUI when using the back button with some browsers, orphaned instance records being created when digital objects were deleted, and more. The full list of bug fixes and improvements is included in the release notes. Thanks to community members Blake Carver, Mark Cooper, Mark Custer, Chris Fitzpatrick, Noah Huffman, Matt Patterson, Dallas Pillen, Austin Schaffer, Chris Tanguay, Mark Triggs, Lora Woodford, Brother Paul, and our wonderful contractor via LibraryHost, Manny Rodriguez, for their contributions. We are also very appreciative of all the work our Development Prioritization sub-team, Testing sub-team, and Core Committers Group do in helping prioritize, test, and do code review for issues for this and all of our releases. Thanks also to Nancy Kennedy and the Smithsonian team for their feedback on the release candidate, which helped us both improve it and aid in planning for future releases. 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 a 2.3.x version, we recommend going directly to 2.4.0, 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. 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 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From ltang5 at lib.msu.edu Fri Jun 8 08:41:26 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Fri, 8 Jun 2018 12:41:26 +0000 Subject: [Archivesspace_Users_Group] implementing lcnaf plugin Message-ID: <8278BB5F-2493-4A8B-8280-0634545742E0@lib.msu.edu> Hi all, Thanks for bringing this up. The ticket has been opened again - it sounded like it was working for a while but went down again. The latest comment on the ticket now points to an API for VIAF - https://platform.worldcat.org/api-explorer/apis/VIAF and the ticket is back in the Development Prioritization queue. If anyone has additional comments or insights on the issue, please feel free to comment/vote on the ticket! https://archivesspace.atlassian.net/browse/ANW-148 Thanks! Lydia - on behalf of the Development Prioritization subteam ?On 6/5/18, 2:54 PM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Busch, Ed" wrote: Follow up- ASPace shouldn't of closed the ticket https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D148&d=DwICAg&c=nE__W8dFE-shTxStwXtp0A&r=lG1-HSCEGsZJf-_mV6BDLh4PvkC3fOv47rKbM_dbh1g&m=tw6M2lPZUIRvrA_H61Q4C2EWawjxjFKBKa1mUXFvdRA&s=1qT3ABLw6E1P2Vbs_XefSMEFWozC9SRMrDy2EFoLqmo&e= . The plugin should have the OCLC part removed since they reported it was no longer supported. Ed Busch Electronic Records Archivist MSU Archives -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Benn Joseph Sent: Tuesday, June 5, 2018 2:44 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] implementing lcnaf plugin I'm curious about this too--here's the ticket, which is marked as resolved: https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D148&d=DwICAg&c=nE__W8dFE-shTxStwXtp0A&r=nzQRpzss_AwHOHAKVWRsNQ&m=omUHlg6rxeBbKLuejb_iZYP3maZJbyTgK05X3cBPGIw&s=rijIbSKUm2fx1RwzcP3Deoccyoel7a7Gwl2lMm1qf-c&e= There's a note from Christine on April 20 about it working now, but it still isn't working for us. Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Busch, Ed Sent: Tuesday, June 05, 2018 9:28 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] implementing lcnaf plugin What's required to implement the LCNAF Plugin? I see the line in config.rb but what' "3rd party services" are required? Is implementing this plugin described somewhere? Thanks! Ed Busch Electronic Records Archivist MSU Archives Conrad Hall, Room 101 888 Wilson Road East Lansing, MI 48824 517-884-6438 From matt.lawson at uni.edu Fri Jun 8 11:46:28 2018 From: matt.lawson at uni.edu (Matthew Lawson) Date: Fri, 8 Jun 2018 10:46:28 -0500 Subject: [Archivesspace_Users_Group] migration question: Message-ID: I am trying to migrate from Archon v3.21 rev3 to ArchivesSpace 2.3.2 using the 11-2017 Archon Data Migrator Jar I think the error log indicates a wrong URL, but I tried to enter the URL where I log on and later tried it without the staff portion: https://archivesspace.library.uni.edu/staff RECORD CONVERSION ERRORS/WARNINGS ( 0 ) :: RECORD SAVE ERRORS ( 0 ) :: Endpoint: https://archivesspace.library.uni.edu/staff/users/admin/login AR Identifier:N/A Status code: 404 Status text: Not Found The page you were looking for doesn't exist (404)

The page you were looking for doesn't exist.

You may have mistyped the address or the page may have moved.

Running for: 2 min 25.79 sec Current # of Records Copied: -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.harrington at lyrasis.org Fri Jun 8 12:06:02 2018 From: brian.harrington at lyrasis.org (Brian Harrington) Date: Fri, 8 Jun 2018 16:06:02 +0000 Subject: [Archivesspace_Users_Group] migration question: In-Reply-To: References: Message-ID: <064D7F15-E95A-4D75-B975-7F3AF005AC65@lyrasis.org> Hi Matthew, The URL the Archon Migrator requires is for the ArchivesSpace backend. Try https://archivesspace.library.uni.edu:8089 Brian ? Brian Harrington Migration Specialist LYRASIS brian.harrington at lyrasis.org Skype: abbistani > On Jun 8, 2018, at 11:46 AM, Matthew Lawson wrote: > > I am trying to migrate from Archon v3.21 rev3 to ArchivesSpace 2.3.2 using the 11-2017 Archon Data Migrator Jar > > I think the error log indicates a wrong URL, but I tried to enter the URL where I log on and later tried it without the staff portion: https://archivesspace.library.uni.edu/staff > > > RECORD CONVERSION ERRORS/WARNINGS ( 0 ) :: > > > > > RECORD SAVE ERRORS ( 0 ) :: > > Endpoint: https://archivesspace.library.uni.edu/staff/users/admin/login > AR Identifier:N/A > Status code: 404 > Status text: Not Found > > > > The page you were looking for doesn't exist (404) > > > > > >
>

The page you were looking for doesn't exist.

>

You may have mistyped the address or the page may have moved.

>
> > > > > > > Running for: 2 min 25.79 sec > > Current # of Records Copied: > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From matt.lawson at uni.edu Fri Jun 8 13:44:38 2018 From: matt.lawson at uni.edu (Matthew Lawson) Date: Fri, 8 Jun 2018 12:44:38 -0500 Subject: [Archivesspace_Users_Group] migration question: In-Reply-To: <064D7F15-E95A-4D75-B975-7F3AF005AC65@lyrasis.org> References: <064D7F15-E95A-4D75-B975-7F3AF005AC65@lyrasis.org> Message-ID: OK I tried that next. The output console says "done" there are no errors, error log says: RECORD CONVERSION ERRORS/WARNINGS ( 0 ) :: RECORD SAVE ERRORS ( 0 ) :: Running for: 9 min 13.68 sec Current # of Records Copied: On Fri, Jun 8, 2018 at 11:06 AM, Brian Harrington < brian.harrington at lyrasis.org> wrote: > Hi Matthew, > > The URL the Archon Migrator requires is for the ArchivesSpace backend. > Try https://archivesspace.library.uni.edu:8089 > > Brian > > ? > Brian Harrington > Migration Specialist > LYRASIS > brian.harrington at lyrasis.org > Skype: abbistani > > > > On Jun 8, 2018, at 11:46 AM, Matthew Lawson wrote: > > > > I am trying to migrate from Archon v3.21 rev3 to ArchivesSpace 2.3.2 > using the 11-2017 Archon Data Migrator Jar > > > > I think the error log indicates a wrong URL, but I tried to enter the > URL where I log on and later tried it without the staff portion: > https://archivesspace.library.uni.edu/staff > > > > > > RECORD CONVERSION ERRORS/WARNINGS ( 0 ) :: > > > > > > > > > > RECORD SAVE ERRORS ( 0 ) :: > > > > Endpoint: https://archivesspace.library.uni.edu/staff/users/admin/login > > AR Identifier:N/A > > Status code: 404 > > Status text: Not Found > > > > > > > > The page you were looking for doesn't exist (404) > > > > > > > > > > > >
> >

The page you were looking for doesn't exist.

> >

You may have mistyped the address or the page may have moved.

> >
> > > > > > > > > > > > > > Running for: 2 min 25.79 sec > > > > Current # of Records Copied: > > > > _______________________________________________ > > 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 matt.lawson at uni.edu Fri Jun 8 17:01:38 2018 From: matt.lawson at uni.edu (Matthew Lawson) Date: Fri, 8 Jun 2018 16:01:38 -0500 Subject: [Archivesspace_Users_Group] migration question: In-Reply-To: References: <064D7F15-E95A-4D75-B975-7F3AF005AC65@lyrasis.org> Message-ID: But no data transfers....it says "done" after about 90 seconds of run time. In Archon there were thousands of records and I spot checked today. -Matt On Fri, Jun 8, 2018 at 12:44 PM, Matthew Lawson wrote: > OK I tried that next. The output console says "done" there are no > errors, error log says: > > > RECORD CONVERSION ERRORS/WARNINGS ( 0 ) :: > > > > > RECORD SAVE ERRORS ( 0 ) :: > > > > Running for: 9 min 13.68 sec > > Current # of Records Copied: > > > On Fri, Jun 8, 2018 at 11:06 AM, Brian Harrington < > brian.harrington at lyrasis.org> wrote: > >> Hi Matthew, >> >> The URL the Archon Migrator requires is for the ArchivesSpace backend. >> Try https://archivesspace.library.uni.edu:8089 >> >> Brian >> >> ? >> Brian Harrington >> Migration Specialist >> LYRASIS >> brian.harrington at lyrasis.org >> Skype: abbistani >> >> >> > On Jun 8, 2018, at 11:46 AM, Matthew Lawson >> wrote: >> > >> > I am trying to migrate from Archon v3.21 rev3 to ArchivesSpace 2.3.2 >> using the 11-2017 Archon Data Migrator Jar >> > >> > I think the error log indicates a wrong URL, but I tried to enter the >> URL where I log on and later tried it without the staff portion: >> https://archivesspace.library.uni.edu/staff >> > >> > >> > RECORD CONVERSION ERRORS/WARNINGS ( 0 ) :: >> > >> > >> > >> > >> > RECORD SAVE ERRORS ( 0 ) :: >> > >> > Endpoint: https://archivesspace.library.uni.edu/staff/users/admin/login >> > AR Identifier:N/A >> > Status code: 404 >> > Status text: Not Found >> > >> > >> > >> > The page you were looking for doesn't exist (404) >> > >> > >> > >> > >> > >> >
>> >

The page you were looking for doesn't exist.

>> >

You may have mistyped the address or the page may have moved.

>> >
>> > >> > >> > >> > >> > >> > >> > Running for: 2 min 25.79 sec >> > >> > Current # of Records Copied: >> > >> > _______________________________________________ >> > 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 christine.dibella at lyrasis.org Fri Jun 8 17:18:07 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 8 Jun 2018 21:18:07 +0000 Subject: [Archivesspace_Users_Group] migration question: In-Reply-To: References: <064D7F15-E95A-4D75-B975-7F3AF005AC65@lyrasis.org> Message-ID: Hi Matt, We can put a support ticket in for you on this. (You?ll see another message about that directly to you in a minute.) At this point it sounds like something not quite right in the connection and the tech folks can troubleshoot this with you. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Matthew Lawson Sent: Friday, June 8, 2018 5:02 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] migration question: But no data transfers....it says "done" after about 90 seconds of run time. In Archon there were thousands of records and I spot checked today. -Matt On Fri, Jun 8, 2018 at 12:44 PM, Matthew Lawson > wrote: OK I tried that next. The output console says "done" there are no errors, error log says: RECORD CONVERSION ERRORS/WARNINGS ( 0 ) :: RECORD SAVE ERRORS ( 0 ) :: Running for: 9 min 13.68 sec Current # of Records Copied: On Fri, Jun 8, 2018 at 11:06 AM, Brian Harrington > wrote: Hi Matthew, The URL the Archon Migrator requires is for the ArchivesSpace backend. Try https://archivesspace.library.uni.edu:8089 Brian ? Brian Harrington Migration Specialist LYRASIS brian.harrington at lyrasis.org Skype: abbistani > On Jun 8, 2018, at 11:46 AM, Matthew Lawson > wrote: > > I am trying to migrate from Archon v3.21 rev3 to ArchivesSpace 2.3.2 using the 11-2017 Archon Data Migrator Jar > > I think the error log indicates a wrong URL, but I tried to enter the URL where I log on and later tried it without the staff portion: https://archivesspace.library.uni.edu/staff > > > RECORD CONVERSION ERRORS/WARNINGS ( 0 ) :: > > > > > RECORD SAVE ERRORS ( 0 ) :: > > Endpoint: https://archivesspace.library.uni.edu/staff/users/admin/login > AR Identifier:N/A > Status code: 404 > Status text: Not Found > > > > The page you were looking for doesn't exist (404) > > > > > >
>

The page you were looking for doesn't exist.

>

You may have mistyped the address or the page may have moved.

>
> > > > > > > Running for: 2 min 25.79 sec > > Current # of Records Copied: > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6608 bytes Desc: image001.jpg URL: From buschedw at msu.edu Mon Jun 11 15:12:16 2018 From: buschedw at msu.edu (Busch, Ed) Date: Mon, 11 Jun 2018 19:12:16 +0000 Subject: [Archivesspace_Users_Group] External Documents Link in Accessions not working correctly? Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164A8C374@CAD-EX01.campusad.msu.edu> In Accessions, there's a section for entering External Document titles and locations which creates a link. I have had success creating document links to http pages but not to file pages. The help specifies the form file:///C:\Users\buschedw\Desktop\ERST_faq.docx but when the document link is clicked, nothing happens. I can take the document link and paste into a browser and the document opens successfully. In summary, the link works for http: but not for file: I don't see an open ticket for this. Or maybe this is a local setup thing that I don't know about. :) Ed Busch Electronic Records Archivist MSU Archives Conrad Hall, Room 101 888 Wilson Road East Lansing, MI 48824 517-884-6438 From mhughes at library.ucla.edu Tue Jun 12 10:14:27 2018 From: mhughes at library.ucla.edu (Hughes, Margaret) Date: Tue, 12 Jun 2018 14:14:27 +0000 Subject: [Archivesspace_Users_Group] Announcing: Awesome ArchivesSpace! Message-ID: Dear colleagues, We're excited to announce a new resource for the ASpace community: Awesome ArchivesSpace https://github.com/archivesspace/awesome-archivesspace. Awesome ArchivesSpace is an awesome list. It points to resources (code, blog posts, anything with a URL, really) regarding ArchivesSpace created by the community that are dispersed around the web. We hope this will function as a sort of "resource guide," by providing a single access point to many of the amazing resources you've all created. Resources in the list are loosely categorized by broad topic. Awesome ArchivesSpace was initially populated with three categories of resources: Migrations, Plug-ins, and Integrations. Through that work, additional categories of interest were identified: Implementation, Scripts and APIs, and Trainings and Documentation. We encourage the ArchivesSpace community to add links to existing categories as well as welcome new category suggestions. The ArchivesSpace community has ownership over Awesome ArchivesSpace -- please help us continue to collect and add relevant resources to Awesome ArchivesSpace! See the Contributing Guidelines for information on how to update the list via pull requests. We hope you find Awesome ArchivesSpace to be useful. Please reach out if you have any comments or questions -- we welcome your feedback! Best, Awesome ArchivesSpace Ad Hoc Working Group - Justin Dalton, Christina Luers, Anne Marie Lyons, and Maggie Hughes. ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bobbi_fox at harvard.edu Tue Jun 12 14:04:53 2018 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Tue, 12 Jun 2018 18:04:53 +0000 Subject: [Archivesspace_Users_Group] Bug fixes for aspace-import-excel Message-ID: Library Technology Services, which supports the Harvard Library, is releasing a new version ( v2.1.9 ) of the aspace-import-excel plugin, available on GitHub at https://github.com/harvard-library/aspace-import-excel . This version is only supported for v2.2.2 and higher of ArchivesSpace. The two major bugs fixed: * Removal of the use 'pry', including removing it from the Gemfile; * Better handling of empty cells in the spreadsheet Pull requests welcome. If you encounter problems, please create an issue in the GitHub repository. Cheers, Bobbi Fox, Maintainer -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory_nimer at byu.edu Thu Jun 14 14:49:29 2018 From: cory_nimer at byu.edu (Cory Nimer) Date: Thu, 14 Jun 2018 18:49:29 +0000 Subject: [Archivesspace_Users_Group] Request for community input: ANW-380 Message-ID: <1890dd3fb1034773996d9f434c1c5e7c@MB7.byu.local> Colleagues, The Development Prioritization Team is seeking community input on a feature request for revisions to the Date subrecord in ArchivesSpace (ANW-380; https://archivesspace.atlassian.net/browse/ANW-380). The Date subrecord is used in multiple ArchivesSpace modules, including those for Accession, Resource, and Digital Object records. Changes to the Date subrecord to support the EAC-CPF model were previously included in the Agents revision project specifications (ANW-429; https://archivesspace.atlassian.net/browse/ANW-429), and the new model would support either EAD2002/EAD3 or EAD3 exports. The primary change planned is the separation of begin and end date expressions in the application. For example, currently a single date expression is used with separate normalized begin and end date entries for date spans: Date subrecord Date Expression: circa 1950-1960 ... Begin: 1950 End: 1960 Certainty: Approximate The revised model would include a separate date expression field entry for each part of the date span: Date subrecord Begin Date Expression: circa 1950 ... Begin Date Standardized: 1950 End Date Expression: 1960 ... End Date Standardized: 1960 ... Certainty: Approximate The concern has been raised that institutions may not have sufficiently consistent data entry practices to allow a single migration script to parse existing Date Expression values into separate Begin and End date expression fields. One proposed path has been to move the entire existing Date Expression value to the new Begin Date Expression, while moving the normalized dates to their appropriate standardized value fields. This would appear as: Date subrecord Begin Date Expression: circa 1950-1960 ... Begin Date Standardized: 1950 End Date Expression: ... End Date Standardized: 1960 ... Certainty: Approximate The Development Prioritization Team would like to obtain feedback from the community regarding preferences for migrating existing Date subrecord content, or other concerns. Comments may be submitted through JIRA on the ticket for ANW-380 (https://archivesspace.atlassian.net/browse/ANW-380). Sincerely, Cory Nimer University Archivist Brigham Young University 801-422-6091 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkottman at ku.edu Thu Jun 14 16:18:55 2018 From: mkottman at ku.edu (Kottman, Miloche) Date: Thu, 14 Jun 2018 20:18:55 +0000 Subject: [Archivesspace_Users_Group] Request for community input: ANW-380 In-Reply-To: <1890dd3fb1034773996d9f434c1c5e7c@MB7.byu.local> References: <1890dd3fb1034773996d9f434c1c5e7c@MB7.byu.local> Message-ID: <57502edc68a74ec985f914e57a1912c3@ex13-ell-cr-15.home.ku.edu> Cory, Am I correct in assuming that the display in the Public Interface will look the same regardless of if the data is in just in the Begin Date Expression or in both begin and end date expression? In other words: Date subrecord Begin Date Expression: circa 1950 Begin Date Standardized: 1950 End Date Expression: 1960 End Date Standardized: 1960 Certainty: Approximate PUBLIC INTERFACE: circa 1950-1960 and Date subrecord Begin Date Expression: circa 1950-1960 Begin Date Standardized: 1950 End Date Expression: End Date Standardized: 1960 Certainty: Approximate PUBLIC INTERFACE: circa 1950-1960 --Miloche ****************************** Miloche Kottman Head of Cataloging and Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Cory Nimer Sent: Thursday, June 14, 2018 1:49 PM To: Archivesspace Users Group ; ArchivesSpace Subject: [Archivesspace_Users_Group] Request for community input: ANW-380 Colleagues, The Development Prioritization Team is seeking community input on a feature request for revisions to the Date subrecord in ArchivesSpace (ANW-380; https://archivesspace.atlassian.net/browse/ANW-380). The Date subrecord is used in multiple ArchivesSpace modules, including those for Accession, Resource, and Digital Object records. Changes to the Date subrecord to support the EAC-CPF model were previously included in the Agents revision project specifications (ANW-429; https://archivesspace.atlassian.net/browse/ANW-429), and the new model would support either EAD2002/EAD3 or EAD3 exports. The primary change planned is the separation of begin and end date expressions in the application. For example, currently a single date expression is used with separate normalized begin and end date entries for date spans: Date subrecord Date Expression: circa 1950-1960 ... Begin: 1950 End: 1960 Certainty: Approximate The revised model would include a separate date expression field entry for each part of the date span: Date subrecord Begin Date Expression: circa 1950 ... Begin Date Standardized: 1950 End Date Expression: 1960 ... End Date Standardized: 1960 ... Certainty: Approximate The concern has been raised that institutions may not have sufficiently consistent data entry practices to allow a single migration script to parse existing Date Expression values into separate Begin and End date expression fields. One proposed path has been to move the entire existing Date Expression value to the new Begin Date Expression, while moving the normalized dates to their appropriate standardized value fields. This would appear as: Date subrecord Begin Date Expression: circa 1950-1960 ... Begin Date Standardized: 1950 End Date Expression: ... End Date Standardized: 1960 ... Certainty: Approximate The Development Prioritization Team would like to obtain feedback from the community regarding preferences for migrating existing Date subrecord content, or other concerns. Comments may be submitted through JIRA on the ticket for ANW-380 (https://archivesspace.atlassian.net/browse/ANW-380). Sincerely, Cory Nimer University Archivist Brigham Young University 801-422-6091 -------------- next part -------------- An HTML attachment was scrubbed... URL: From trthorn2 at ncsu.edu Thu Jun 14 16:56:31 2018 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Thu, 14 Jun 2018 16:56:31 -0400 Subject: [Archivesspace_Users_Group] Request for community input: ANW-380 In-Reply-To: <1890dd3fb1034773996d9f434c1c5e7c@MB7.byu.local> References: <1890dd3fb1034773996d9f434c1c5e7c@MB7.byu.local> Message-ID: I think the new model makes sense, but the migration will be onerous for a lot of people depending on the state of their existing data. Alex Duryee at NYPL (I think he's still there) published some Ruby code (which I also contributed to during my time there) that could be useful in the migration process: https://github.com/alexduryee/timetwister He also ported it into an AS plugin: https://github.com/alexduryee/timewalk It parses date expressions into one or more normalized dates based on regex patterns and corresponding rules for parsing each pattern. I ran an earlier version of it over a fairly large corpus for dates from NYPL archival collections with very good results, and it's been improved upon since then. On Thu, Jun 14, 2018 at 2:49 PM, Cory Nimer wrote: > Colleagues, > > > > The Development Prioritization Team is seeking community input on a > feature request for revisions to the Date subrecord in ArchivesSpace > (ANW-380; https://archivesspace.atlassian.net/browse/ANW-380). The Date > subrecord is used in multiple ArchivesSpace modules, including those for > Accession, Resource, and Digital Object records. Changes to the Date > subrecord to support the EAC-CPF model were previously included > in the Agents revision project specifications (ANW-429; > https://archivesspace.atlassian.net/browse/ANW-429), and the new model > would support either EAD2002/EAD3 or EAD3 > exports. > > > > The primary change planned is the separation of begin and end date > expressions in the application. For example, currently a single date > expression is used with separate normalized begin and end date entries for > date spans: > > > > *Date subrecord* > > Date Expression: circa 1950-1960 > > ? > > Begin: 1950 > > End: 1960 > > Certainty: Approximate > > > > The revised model would include a separate date expression field entry for > each part of the date span: > > > > *Date subrecord* > > Begin Date Expression: circa 1950 > > ? > > Begin Date Standardized: 1950 > > > > End Date Expression: 1960 > > ? > > End Date Standardized: 1960 > > ? > > Certainty: Approximate > > > > The concern has been raised that institutions may not have sufficiently > consistent data entry practices to allow a single migration script to parse > existing Date Expression values into separate Begin and End date expression > fields. One proposed path has been to move the entire existing Date > Expression value to the new Begin Date Expression, while moving the > normalized dates to their appropriate standardized value fields. This would > appear as: > > > > *Date subrecord* > > Begin Date Expression: circa 1950-1960 > > ? > > Begin Date Standardized: 1950 > > > > End Date Expression: > > ? > > End Date Standardized: 1960 > > ? > > Certainty: Approximate > > > > The Development Prioritization Team would like to obtain feedback from the > community regarding preferences for migrating existing Date subrecord > content, or other concerns. Comments may be submitted through JIRA on the > ticket for ANW-380 (https://archivesspace.atlassian.net/browse/ANW-380). > > > > Sincerely, > > > > Cory Nimer > > University Archivist > > Brigham Young University > > 801-422-6091 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmduffin at upenn.edu Thu Jun 14 17:45:19 2018 From: jmduffin at upenn.edu (J.M. Duffin) Date: Thu, 14 Jun 2018 17:45:19 -0400 Subject: [Archivesspace_Users_Group] Table relationships in database Message-ID: <00e501d40428$feddf8f0$fc99ead0$@upenn.edu> Does anyone have or know where I can find some documentation on the different tables and their function and, more importantly, the relationships of the different tables (i.e. which fields are the linking fields between tables) in the backend MySql database for ASpace? I want to review our test import of several thousand records from AT into ASpace to see that there are no major problems. From experience, I've found that reviewing the data through an interface like Access allows me a quick and easy way to locate anomalies as well as isolate problems. I would greatly appreciate any thoughts or suggestions people can offer. Thanks, Jim Duffin J.M. Duffin Senior Archives and Office Manager University Archives and Records Center University of Pennsylvania 3401 Market Street, Suite 210 Philadelphia, PA 19104 T: 215.898.2002 -------------- next part -------------- An HTML attachment was scrubbed... URL: From laurie.arp at lyrasis.org Fri Jun 15 08:54:44 2018 From: laurie.arp at lyrasis.org (Laurie Arp) Date: Fri, 15 Jun 2018 12:54:44 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 4th Quarter Board update Message-ID: Distributing for Carol Mandel... Dear ArchivesSpace members, I am writing to report on the ArchivesSpace Governance Board 4th Quarter meeting, a 2 hour virtual meeting which was conducted June 1st. The board approved the nominations for the election slate for the Governance board, and appointments to the Technical Advisory Council and User Advisory Council. We thanked the Nominating Committee, chaired by Gordon Daines, for their careful and hard work. Gordon will send out an announcement of the election and appointment results once the process is complete. We approved procedures for electing the ArchivesSpace Governance Board Chair and Vice-Chair. John Wilkin, Dean of Libraries and University Librarian at the University of Illinois at Urbana-Champaign, will be the Governance Board Chair for the 2018/2019 term. Gordon Daines, Special Collections Department Chair at Brigham Young University, will be the Vice-Chair for the 2018/19 term; the Vice-Chair is the chair-elect. We also approved a FY18-19 budget focused on further growth and development. We reviewed: * the continued excellent work of TAC and UAC and thank the members for their dedicated participation * updates on the founding partner and organizational home agreements * a financial report that confirms we are on budget and in a strong financial position We welcomed Dr. Erik Mitchell to the Governance Board. Erik became the Audrey Geisel University Librarian at UC San Diego (UCSD) in April 2018 and he will represent that ArchivesSpace founding partner. Erik was previously the Associate University Librarian of Digital Initiatives and Collaborative Services at UC Berkeley. The board members thanked departing board members Heather Heckman, Audra Eagle Yun, and Gregor Trinkaus-Randall for their active and substantial service on the board. Heather has served one term representing the "small" membership category. Heather's contributions include participating in the Organizational Home Agreement subteam and working to ensure ArchivesSpace meets the needs of the small and very small membership categories. Audra has served one term representing the "very large" membership category. Audra's contributions include participating in the Bylaws review subteam and the Mission Statement and Guiding Principles subteam. Gregor Trinkaus-Randall has been an ex-officio member representing the LYRASIS board since 2016. He was active in the Bylaws review and exploring ways to grow use of ArchivesSpace. The Board very much appreciates their commitment to furthering the ArchivesSpace community. As we look ahead to a new membership term, we continue to see this community that we have all built together grow and develop in exciting ways. Members are essential to its success, and your participation in all of its facets is both encouraged and vital. The Board welcomes your communications and comments on anything mentioned here, or anything else related to ArchivesSpace that is of concern or interest to you. On a personal note, June's meeting was my final one on the ArchivesSpace Governance Board as I am stepping down as dean of the Division of Libraries at New York University effective June 30. Participating in the growth of ArchivesSpace from an idea to a brilliantly successful open source model has been incredibly gratifying. The success of ArchivesSpace is the vibrant, active, engaged community that you have all created. Your willingness to give your time, expertise and ideas has had an enormous collaborative impact. Thank you for all we have done together, and thank you for all you will do in the years to come. Respectfully, Carol A. Mandel Chair, ArchivesSpace Governance Board Dean, Division of Libraries, New York University -------------- next part -------------- An HTML attachment was scrubbed... URL: From ccauste1 at swarthmore.edu Fri Jun 15 09:53:53 2018 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Fri, 15 Jun 2018 09:53:53 -0400 Subject: [Archivesspace_Users_Group] Announcing: Awesome ArchivesSpace! In-Reply-To: References: Message-ID: Thanks for this - a lot of really great resources! I am confused, however. There seems to be a lot of redundancy with the ArchivesSpace wiki ( https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/16449557/Community+Resources). Does this replace the wiki? On Tue, Jun 12, 2018 at 10:14 AM, Hughes, Margaret wrote: > Dear colleagues, > > > > We?re excited to announce a new resource for the ASpace community: Awesome > ArchivesSpace https://github.com/archivesspace/awesome-archivesspace. > > > > Awesome ArchivesSpace is an awesome list > . It points to resources (code, > blog posts, anything with a URL, really) regarding ArchivesSpace created by > the community that are dispersed around the web. We hope this will function > as a sort of ?resource guide,? by providing a single access point to many > of the amazing resources you?ve all created. > > > > Resources in the list are loosely categorized by broad topic. Awesome > ArchivesSpace was initially populated with three categories of resources: > Migrations, Plug-ins, and Integrations. Through that work, additional > categories of interest were identified: Implementation, Scripts and APIs, > and Trainings and Documentation. We encourage the ArchivesSpace community > to add links to existing categories as well as welcome new category > suggestions. > > > > The ArchivesSpace community has ownership over Awesome ArchivesSpace -- > please help us continue to collect and add relevant resources to Awesome > ArchivesSpace! See the Contributing Guidelines > > for information on how to update the list via pull requests. > > > > We hope you find Awesome ArchivesSpace to be useful. Please reach out if > you have any comments or questions -- we welcome your feedback! > > > > Best, > > > > Awesome ArchivesSpace Ad Hoc Working Group > > - Justin Dalton, Christina Luers, Anne Marie Lyons, and Maggie Hughes. > > > > > > ---------------------------------- > > Margaret Hughes > > Collections Data Archivist > > 310.206.6203 > > > > UCLA Library Special Collections > > A1713 Charles E. Young Research Library > > Los Angeles, CA 90095-1575 > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8496 ccauste1 at swarthmore.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexanderduryee at nypl.org Fri Jun 15 10:28:37 2018 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Fri, 15 Jun 2018 10:28:37 -0400 Subject: [Archivesspace_Users_Group] [archivesspace] Request for community input: ANW-380 In-Reply-To: References: <1890dd3fb1034773996d9f434c1c5e7c@MB7.byu.local> Message-ID: I'm a bit wary of making major changes to the date model, as it'll require prescriptive policy changes for data entry. Providing only one date expression field allows for a degree of flexibility with semantically meaningful dates; for example, "1950s" is a perfectly valid date expression that wouldn't separate well into begin/end expressions. It's also not immediately clear how range dates like "Spring 1950" or "Early 1950" will work in this format - archives would either need to develop rules for data entry around these date forms, or forbid them entirely. When developing timetwister/timewalk, my goal was to be as permissive as possible regarding date forms, and not to make assumptions/prescriptions about metadata rules. This results in occasional ambiguity (e.g. "circa 1950-1960" isn't clear which dates are approximated) and minor inaccuracy (e.g. "Spring 1950" parses to 1950-03-20/1950-06-21, which is overly broad), but there will always be a degree of that in archival description. My concern with the proposed date model is that it takes the opposite approach by strictly defining date forms, even when appropriate archival practice may not call for that level of precision. Regarding migration - our date metadata is about as sterling as one can reasonably expect (thanks Trevor), with ~99.99% of our dates machine-readable and parsed, and even then I anticipate migration issues when moving to the new date model. One possible compromise solution would be implementing EDTF in the Begin/End Date Standardized field, as per Seth Shaw's suggestion. This would allow for very precise dates when necessary (e.g. "1950~/1960", "18xx/1920~") but without prescribing descriptive policy on archives that don't want/need that level of accuracy. Exporters could pull from this field to generate structured dates and bypass the expression when appropriate (or just don't use an expression for highly precise dates). This would require replacing the date picker with a validated text field, and changes to exporters / maybe the PUI, but it would be much less disruptive than a data model modification. Thanks, --Alex On Fri, Jun 15, 2018 at 4:40 AM, Chris Fitzpatrick wrote: > > Hi, > > I think these make sense, but I also think there's a lot of "migration and > cleanup fatigue" around archivesspace. The database schema changes quite > frequently, which often adds a lot of work to folks doing the metadata > management. > > In addition, these kinds of changes require a lot of work on the > development side, much of which isn't really anticipated before the > database changes roll out. . Modifications to the database schema require > changes to the staff UI views and forms and javascript, and ditto for the > public UI, then the indexer and the solr schema, the backend models and > api, the exporters, importers, the converters..oh and we usually forget > about things like the RDE, reports, AT/Archon migration apps, various > background jobs, and all the changes to the test suite...and then there's > everyone's plugins, themes, and integrations that have to be updated. > > It sounds like this is a concern for EAD exports, so should this just be > handled in the EAD exporter? Either the standard exporter could have logic > added to handle the use case, or a specialized exporter could be developed > to format the data the way that's required ( if there's too much variance > across everyone's data to correctly map it to the desired output ). > It might be too complicated, but it might be worth exploring that option > before making more database changes. > > best,chris. > > > > > > On Thu, Jun 14, 2018 at 8:49 PM, Cory Nimer wrote: > >> Colleagues, >> >> >> >> The Development Prioritization Team is seeking community input on a >> feature request for revisions to the Date subrecord in ArchivesSpace >> (ANW-380; https://archivesspace.atlassian.net/browse/ANW-380). The Date >> subrecord is used in multiple ArchivesSpace modules, including those for >> Accession, Resource, and Digital Object records. Changes to the Date >> subrecord to support the EAC-CPF model were previously included >> in the Agents revision project specifications (ANW-429; >> https://archivesspace.atlassian.net/browse/ANW-429), and the new model >> would support either EAD2002/EAD3 or EAD3 >> exports. >> >> >> >> The primary change planned is the separation of begin and end date >> expressions in the application. For example, currently a single date >> expression is used with separate normalized begin and end date entries for >> date spans: >> >> >> >> *Date subrecord* >> >> Date Expression: circa 1950-1960 >> >> ? >> >> Begin: 1950 >> >> End: 1960 >> >> Certainty: Approximate >> >> >> >> The revised model would include a separate date expression field entry >> for each part of the date span: >> >> >> >> *Date subrecord* >> >> Begin Date Expression: circa 1950 >> >> ? >> >> Begin Date Standardized: 1950 >> >> >> >> End Date Expression: 1960 >> >> ? >> >> End Date Standardized: 1960 >> >> ? >> >> Certainty: Approximate >> >> >> >> The concern has been raised that institutions may not have sufficiently >> consistent data entry practices to allow a single migration script to parse >> existing Date Expression values into separate Begin and End date expression >> fields. One proposed path has been to move the entire existing Date >> Expression value to the new Begin Date Expression, while moving the >> normalized dates to their appropriate standardized value fields. This would >> appear as: >> >> >> >> *Date subrecord* >> >> Begin Date Expression: circa 1950-1960 >> >> ? >> >> Begin Date Standardized: 1950 >> >> >> >> End Date Expression: >> >> ? >> >> End Date Standardized: 1960 >> >> ? >> >> Certainty: Approximate >> >> >> >> The Development Prioritization Team would like to obtain feedback from >> the community regarding preferences for migrating existing Date subrecord >> content, or other concerns. Comments may be submitted through JIRA on the >> ticket for ANW-380 (https://archivesspace.atlassian.net/browse/ANW-380). >> >> >> >> Sincerely, >> >> >> >> Cory Nimer >> >> University Archivist >> >> Brigham Young University >> >> 801-422-6091 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "ArchivesSpace" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to archivesspace+unsubscribe at googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > chris fitzpatrick > http://cfitz.github.io/ > > -- > You received this message because you are subscribed to the Google Groups > "ArchivesSpace" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to archivesspace+unsubscribe at googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From library at princeofpeaceabbey.org Fri Jun 15 11:30:31 2018 From: library at princeofpeaceabbey.org (library at princeofpeaceabbey.org) Date: Fri, 15 Jun 2018 10:30:31 -0500 Subject: [Archivesspace_Users_Group] [archivesspace] Request for community input: ANW-380 In-Reply-To: References: <1890dd3fb1034773996d9f434c1c5e7c@MB7.byu.local> Message-ID: <20180615103031.Horde.hllXMVnBJaj2qrzsl5n9e_f@gator3088.hostgator.com> If I may chime in. It would help if AS would allow something like February 30, any year as the unknown date. I found that the ladies of old would place this date on their tombstones. Br Raphael Quoting Alexander Duryee : > I'm a bit wary of making major changes to the date model, as it'll require > prescriptive policy changes for data entry. Providing only one date > expression field allows for a degree of flexibility with semantically > meaningful dates; for example, "1950s" is a perfectly valid date expression > that wouldn't separate well into begin/end expressions. It's also not > immediately clear how range dates like "Spring 1950" or "Early 1950" will > work in this format - archives would either need to develop rules for data > entry around these date forms, or forbid them entirely. > > When developing timetwister/timewalk, my goal was to be as permissive as > possible regarding date forms, and not to make assumptions/prescriptions > about metadata rules. This results in occasional ambiguity (e.g. "circa > 1950-1960" isn't clear which dates are approximated) and minor inaccuracy > (e.g. "Spring 1950" parses to 1950-03-20/1950-06-21, which is overly > broad), but there will always be a degree of that in archival description. > My concern with the proposed date model is that it takes the opposite > approach by strictly defining date forms, even when appropriate archival > practice may not call for that level of precision. > > Regarding migration - our date metadata is about as sterling as one can > reasonably expect (thanks Trevor), with ~99.99% of our dates > machine-readable and parsed, and even then I anticipate migration issues > when moving to the new date model. > > One possible compromise solution would be implementing EDTF in the > Begin/End Date Standardized field, as per Seth Shaw's suggestion. This > would allow for very precise dates when necessary (e.g. "1950~/1960", > "18xx/1920~") but without prescribing descriptive policy on archives that > don't want/need that level of accuracy. Exporters could pull from this > field to generate structured dates and bypass the expression when > appropriate (or just don't use an expression for highly precise dates). > This would require replacing the date picker with a validated text field, > and changes to exporters / maybe the PUI, but it would be much less > disruptive than a data model modification. > > Thanks, > --Alex > > On Fri, Jun 15, 2018 at 4:40 AM, Chris Fitzpatrick > wrote: > >> >> Hi, >> >> I think these make sense, but I also think there's a lot of "migration and >> cleanup fatigue" around archivesspace. The database schema changes quite >> frequently, which often adds a lot of work to folks doing the metadata >> management. >> >> In addition, these kinds of changes require a lot of work on the >> development side, much of which isn't really anticipated before the >> database changes roll out. . Modifications to the database schema require >> changes to the staff UI views and forms and javascript, and ditto for the >> public UI, then the indexer and the solr schema, the backend models and >> api, the exporters, importers, the converters..oh and we usually forget >> about things like the RDE, reports, AT/Archon migration apps, various >> background jobs, and all the changes to the test suite...and then there's >> everyone's plugins, themes, and integrations that have to be updated. >> >> It sounds like this is a concern for EAD exports, so should this just be >> handled in the EAD exporter? Either the standard exporter could have logic >> added to handle the use case, or a specialized exporter could be developed >> to format the data the way that's required ( if there's too much variance >> across everyone's data to correctly map it to the desired output ). >> It might be too complicated, but it might be worth exploring that option >> before making more database changes. >> >> best,chris. >> >> >> >> >> >> On Thu, Jun 14, 2018 at 8:49 PM, Cory Nimer wrote: >> >>> Colleagues, >>> >>> >>> >>> The Development Prioritization Team is seeking community input on a >>> feature request for revisions to the Date subrecord in ArchivesSpace >>> (ANW-380; https://archivesspace.atlassian.net/browse/ANW-380). The Date >>> subrecord is used in multiple ArchivesSpace modules, including those for >>> Accession, Resource, and Digital Object records. Changes to the Date >>> subrecord to support the EAC-CPF model were previously included >>> in the Agents revision project specifications (ANW-429; >>> https://archivesspace.atlassian.net/browse/ANW-429), and the new model >>> would support either EAD2002/EAD3 or EAD3 >>> exports. >>> >>> >>> >>> The primary change planned is the separation of begin and end date >>> expressions in the application. For example, currently a single date >>> expression is used with separate normalized begin and end date entries for >>> date spans: >>> >>> >>> >>> *Date subrecord* >>> >>> Date Expression: circa 1950-1960 >>> >>> ? >>> >>> Begin: 1950 >>> >>> End: 1960 >>> >>> Certainty: Approximate >>> >>> >>> >>> The revised model would include a separate date expression field entry >>> for each part of the date span: >>> >>> >>> >>> *Date subrecord* >>> >>> Begin Date Expression: circa 1950 >>> >>> ? >>> >>> Begin Date Standardized: 1950 >>> >>> >>> >>> End Date Expression: 1960 >>> >>> ? >>> >>> End Date Standardized: 1960 >>> >>> ? >>> >>> Certainty: Approximate >>> >>> >>> >>> The concern has been raised that institutions may not have sufficiently >>> consistent data entry practices to allow a single migration script to parse >>> existing Date Expression values into separate Begin and End date expression >>> fields. One proposed path has been to move the entire existing Date >>> Expression value to the new Begin Date Expression, while moving the >>> normalized dates to their appropriate standardized value fields. This would >>> appear as: >>> >>> >>> >>> *Date subrecord* >>> >>> Begin Date Expression: circa 1950-1960 >>> >>> ? >>> >>> Begin Date Standardized: 1950 >>> >>> >>> >>> End Date Expression: >>> >>> ? >>> >>> End Date Standardized: 1960 >>> >>> ? >>> >>> Certainty: Approximate >>> >>> >>> >>> The Development Prioritization Team would like to obtain feedback from >>> the community regarding preferences for migrating existing Date subrecord >>> content, or other concerns. Comments may be submitted through JIRA on the >>> ticket for ANW-380 (https://archivesspace.atlassian.net/browse/ANW-380). >>> >>> >>> >>> Sincerely, >>> >>> >>> >>> Cory Nimer >>> >>> University Archivist >>> >>> Brigham Young University >>> >>> 801-422-6091 >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "ArchivesSpace" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to archivesspace+unsubscribe at googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> chris fitzpatrick >> http://cfitz.github.io/ >> >> -- >> You received this message because you are subscribed to the Google Groups >> "ArchivesSpace" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to archivesspace+unsubscribe at googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Alexander Duryee > Metadata Archivist > New York Public Library > (917)-229-9590 > alexanderduryee at nypl.org From seth.shaw at unlv.edu Fri Jun 15 11:37:43 2018 From: seth.shaw at unlv.edu (Seth Shaw) Date: Fri, 15 Jun 2018 08:37:43 -0700 Subject: [Archivesspace_Users_Group] [archivesspace] Request for community input: ANW-380 In-Reply-To: <20180615103031.Horde.hllXMVnBJaj2qrzsl5n9e_f@gator3088.hostgator.com> References: <1890dd3fb1034773996d9f434c1c5e7c@MB7.byu.local> <20180615103031.Horde.hllXMVnBJaj2qrzsl5n9e_f@gator3088.hostgator.com> Message-ID: Making date validation a configuration option is a good idea; so those who want it can keep it but those who need to turn it off, can. On Fri, Jun 15, 2018 at 8:30 AM, wrote: > If I may chime in. It would help if AS would allow something like > February 30, any year as the unknown date. I found that the ladies of old > would place this date on their tombstones. > > Br Raphael > -------------- next part -------------- An HTML attachment was scrubbed... URL: From akroeger at unomaha.edu Mon Jun 18 12:18:16 2018 From: akroeger at unomaha.edu (Angela Kroeger) Date: Mon, 18 Jun 2018 16:18:16 +0000 Subject: [Archivesspace_Users_Group] [archivesspace] Request for community input: ANW-380 In-Reply-To: <20180615103031.Horde.hllXMVnBJaj2qrzsl5n9e_f@gator3088.hostgator.com> References: <1890dd3fb1034773996d9f434c1c5e7c@MB7.byu.local> <20180615103031.Horde.hllXMVnBJaj2qrzsl5n9e_f@gator3088.hostgator.com> Message-ID: I agree with what Alexander Duryee said about a single date expression field providing "a degree of flexibility with semantically meaningful dates." Adding to Alex's excellent examples, a date expression I've used is "Not earlier than 1972 and not later than 1985," which also would be difficult for an algorithm to separate into separate begin and end date expression fields. As one of the institutions which likely "may not have sufficiently consistent data entry practices to allow a single migration script to parse existing Date Expression values into separate Begin and End date expression fields," we support the proposed idea of "[moving] the entire existing Date Expression value to the new Begin Date Expression, while moving the normalized dates to their appropriate standardized value fields." Will it be possible for each institution to choose whether they want their Date Expression values moved one-to-one into the Begin Date Expression field or algorithmically split into the new Begin and End Date Expression fields? So that institutions which think their dates are sufficiently consistent to be split into the new fields could choose the latter option, while institutions which may have more unusual date expressions could choose the former? Will it be possible, post-migration, for an institution to choose to continue to use a single free-text field for the date expression? (Of course, normalized dates would still be separately recorded in the standardized fields, for machine searchability. The date expression is for human readability.) That is, would it be possible for an institution to choose to not utilize the new fields, or to choose to use the Begin Date Expression field like a single expression field post-migration? Better still, I like Mark Carlson's suggestion on ANW-380 (https://archivesspace.atlassian.net/browse/ANW-380), that the existing model be retained and available alongside the new model, rather than being replaced by the new model, and allowing the institution to choose whether date expression should be one field or split. Date expression is useful as a free-text, human-readable field, and it already pairs nicely with the existing machine-readable normalized begin/end dates. I would like for institutions to continue to have the option of using a single field for date expression if they so choose. Angela Kroeger Archives and Special Collections Associate UNO Libraries | Criss Library 107 University of Nebraska at Omaha | unomaha.edu 402.554.4159 akroeger at unomaha.edu From mhughes at library.ucla.edu Mon Jun 18 12:56:35 2018 From: mhughes at library.ucla.edu (Hughes, Margaret) Date: Mon, 18 Jun 2018 16:56:35 +0000 Subject: [Archivesspace_Users_Group] Announcing: Awesome ArchivesSpace! In-Reply-To: References: Message-ID: Hi Celia, As of now, Awesome ArchivesSpace doesn?t replace the wiki. However, portions of the wiki (particularly the plugins and integrations pages) did inform the contents of the awesome list (and the awesome list links back to the wiki pages). We saw the awesome list as a different type of community resource -- topically it is more expansive than the wiki (with migrations, trainings, APIs -- and we hope this will grow further) as well as content-wise (blog posts, slide decks, journal articles). It?s a good question to think about, though, the overlap between the two resources to ensure that the community isn?t further confused. Perhaps we could link out to the awesome list from the Community Resources wiki page. Maggie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Celia Caust-Ellenbogen Sent: Friday, June 15, 2018 6:54 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Announcing: Awesome ArchivesSpace! Thanks for this - a lot of really great resources! I am confused, however. There seems to be a lot of redundancy with the ArchivesSpace wiki (https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/16449557/Community+Resources). Does this replace the wiki? On Tue, Jun 12, 2018 at 10:14 AM, Hughes, Margaret > wrote: Dear colleagues, We?re excited to announce a new resource for the ASpace community: Awesome ArchivesSpace https://github.com/archivesspace/awesome-archivesspace. Awesome ArchivesSpace is an awesome list. It points to resources (code, blog posts, anything with a URL, really) regarding ArchivesSpace created by the community that are dispersed around the web. We hope this will function as a sort of ?resource guide,? by providing a single access point to many of the amazing resources you?ve all created. Resources in the list are loosely categorized by broad topic. Awesome ArchivesSpace was initially populated with three categories of resources: Migrations, Plug-ins, and Integrations. Through that work, additional categories of interest were identified: Implementation, Scripts and APIs, and Trainings and Documentation. We encourage the ArchivesSpace community to add links to existing categories as well as welcome new category suggestions. The ArchivesSpace community has ownership over Awesome ArchivesSpace -- please help us continue to collect and add relevant resources to Awesome ArchivesSpace! See the Contributing Guidelines for information on how to update the list via pull requests. We hope you find Awesome ArchivesSpace to be useful. Please reach out if you have any comments or questions -- we welcome your feedback! Best, Awesome ArchivesSpace Ad Hoc Working Group - Justin Dalton, Christina Luers, Anne Marie Lyons, and Maggie Hughes. ---------------------------------- Margaret Hughes Collections Data Archivist 310.206.6203 UCLA Library Special Collections A1713 Charles E. Young Research Library Los Angeles, CA 90095-1575 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8496 ccauste1 at swarthmore.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Tue Jun 19 13:36:22 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Tue, 19 Jun 2018 17:36:22 +0000 Subject: [Archivesspace_Users_Group] Webinar Announcement: Transforming XLS to EAD -- June 27 Message-ID: Transforming XLS to EAD: Importing Component Hierarchies When: Wednesday, June 27, 2018 Time: 1:00 p.m. - 2:30 p.m. ET (10:00 a.m. - 11:30 a.m. PT) Where: Webinar at http://lyrasis.adobeconnect.com/ruio9pyqjot4/ 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 on the ArchivesSpace YouTube channel. Webinar description: Do you list out your components on a spreadsheet before committing the item records into ArchivesSpace? If this is your preferred processing workflow, you're not alone. In this webinar, we will look at three distinct methods to get your spreadsheet rows and columns into your ArchivesSpace resource record to populate components. First, Elizabeth Perkes (Utah State Archives) will demonstrate a workflow that uses built-in Microsoft Office tools to convert Microsoft Excel spreadsheets to EAD via mail merge. Jason Ronallo (North Carolina State University) will provide a demo of the Stead schema and Steady tool he developed, which is a command line tool and web application that uses Ruby to transform data in spreadsheets into EAD component levels. And Ben Johnson (Harvard Business School) uses a spreadsheet importer plugin developed by Bobbi Fox (Harvard University) in a variety of ways. However, he will provide an overview of one simple use of the tool: How to easily and quickly add bulk data from new accessions to existing resources. Ben will walk through our workflow for that and show some limitations and pitfalls to avoid. But perhaps you would like to see more than just workflows. Kelly Spring (East Carolina University) will provide insight into some of the common troubleshooting and other tasks that will help you successfully upload the EAD to ArchivesSpace. Presenters: Elizabeth Perkes has worked for the Utah State Archives for almost 28 years. In that capacity she has primarily managed our database systems, websites, and electronic records. In 2000, she converted all of their finding aids to EAD. The general methodology used in that project became a small how-to video in 2008, which is being updated and described today. Jason Ronallo is the Department Head of Digital Library Initiatives at NCSU Libraries. Current interests include IIIF and researcher support. You can learn more about his work at https://ronallo.com/ Ben Johnson is the Senior Processing Archivist at Baker Library, Harvard Business School, where he is perpetually processing the Polaroid Corporation records. Ben helps develop and implement procedures and workflows to better streamline the processing of collections. He also frequently finds himself working with audiovisual materials. Kelly Spring is the Access Archivist at East Carolina University where, currently, she aspires to AS migration wizardry with a team of talented colleagues. Who should attend: Everyone interested in seeing a demonstration of a variety of practices to import your spreadsheet contents into ArchivesSpace. Please feel free to bring any questions you have. Questions? Please contact Kim at christine.kim at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Tue Jun 19 19:02:03 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Tue, 19 Jun 2018 23:02:03 +0000 Subject: [Archivesspace_Users_Group] Finalized program for the SoCal Regional Forum - June 27 Message-ID: Hi everyone, We are one week away from the SoCal Regional Forum! The finalized program for the SoCal Regional Forum is now available and includes information on presentations, workshops, the post-forum mixer, and parking information. * Program: A finalized program is now available: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/533168147/SoCal+Regional+Forum * Afternoon activities: Selected by the community vote through registration, the afternoon will provide a variety of overviews in different formats. We will have an Introduction to ArchivesSpace workshop for those who choose to attend, with a group discussion on a variety of topics running in parallel. Following, we will have an overview of plug-ins. Last, we will have demonstration and discussion of the Digital Objects module. A laptop is not required to follow along, but is welcome if you'd like to try anything out. * Lunch: A catered lunch will be provided. * Post-event mixer: After the program's conclusion, we will move out to the Anthill Pub & Grille for an optional (and fun!) opportunity to continue our conversations in a more casual and personal way * On-site volunteers: If you plan to attend the forum, please consider volunteering for special tasks throughout the day. This will not be a full day commitment, but rather for specific assigned segments throughout the day, such as notetaking or photography. Please feel free to view the opportunities and sign up directly on this sheet: https://goo.gl/Hc662B Registration is still open! https://www.eventbrite.com/e/archivesspace-regional-forum-southern-california-2018-tickets-44930947674 Special thanks to working group members Elvia Arroyo-Ramirez (UCI Libraries), Krystal Tribbett (UCI Libraries), and Margaret Hughes (UCLA) for putting together an incredible program. Best wishes, Christine Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Wed Jun 20 15:41:49 2018 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Wed, 20 Jun 2018 19:41:49 +0000 Subject: [Archivesspace_Users_Group] SOLR Snapshot concurrency issue - anyone? Message-ID: Throwing this out to the group..... We're testing the 2.3.2 release and are seeing some solr snapshot failure errors in the logs on our dev server (running in a docker container). I did not see anything like this running locally (not in a docker container) and am wondering what might be a potential cause and what sorts of things I could/should be tweaking. The error looks like the below snippet (five attempts in all) and seems to occur on the hour (I think?) The indexer seems to have completed for both the staff and PUI. Any thoughts from the group? Thanks! Joshua E, [2018-06-20T18:00:24.451481 #72] ERROR -- : Thread-7344: Solr snapshot failed (Solr snapshot failed: Concurrent snapshot detected. Bailing out!: ["uri:classloader:/solr_snapshotter.rb:78:in `wait_for_snapshot_to_finish'", "uri:classloader:/solr_snapshotter.rb:123:in `do_snapshot'", "uri:classloader:/solr_snapshotter.rb:63:in `block in snapshot'", "org/jruby/RubyFixnum.java:305:in `times'", "uri:classloader:/solr_snapshotter.rb:61:in `snapshot'", "/opt/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:186:in `block in ArchivesSpaceService'", "/opt/archivesspace/gems/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:229:in `trigger_block'", "/opt/archivesspace/gems/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:204:in `block in trigger'", "/opt/archivesspace/gems/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in `block in trigger_job'"]) - attempt 4 ================================================================================ scheduler caught exception: Solr snapshot failed after 5 retries: Solr snapshot failed: Concurrent snapshot detected. Bailing out!: ["uri:classloader:/solr_snapshotter.rb:78:in `wait_for_snapshot_to_finish'", "uri:classloader:/solr_snapshotter.rb:123:in `do_snapshot'", "uri:classloader:/solr_snapshotter.rb:63:in `block in snapshot'", "org/jruby/RubyFixnum.java:305:in `times'", "uri:classloader:/solr_snapshotter.rb:61:in `snapshot'", "/opt/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:186:in `block in ArchivesSpaceService'", "/opt/archivesspace/gems/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:229:in `trigger_block'", "/opt/archivesspace/gems/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:204:in `block in trigger'", "/opt/archivesspace/gems/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in `block in trigger_job'"] uri:classloader:/solr_snapshotter.rb:69:in `block in snapshot' org/jruby/RubyFixnum.java:305:in `times' uri:classloader:/solr_snapshotter.rb:61:in `snapshot' /opt/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:186:in `block in ArchivesSpaceService' /opt/archivesspace/gems/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:229:in `trigger_block' /opt/archivesspace/gems/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:204:in `block in trigger' /opt/archivesspace/gems/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in `block in trigger_job' ================================================================================ -------------- next part -------------- An HTML attachment was scrubbed... URL: From buschedw at msu.edu Wed Jun 20 16:50:05 2018 From: buschedw at msu.edu (Busch, Ed) Date: Wed, 20 Jun 2018 20:50:05 +0000 Subject: [Archivesspace_Users_Group] Extent Calculation Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164A93C41@CAD-EX01.campusad.msu.edu> Does the ASpace Extent Calculation only do linear feet or can it do cubic feet? I've tried changing the Extent Dimension but that doesn't seem to effect the units. Ed Busch Electronic Records Archivist MSU Archives From james at hudmol.com Wed Jun 20 19:26:50 2018 From: james at hudmol.com (James Bullen) Date: Thu, 21 Jun 2018 09:26:50 +1000 Subject: [Archivesspace_Users_Group] Extent Calculation In-Reply-To: <35E2A8E8997F6C48A5D5FC21602BDEB60164A93C41@CAD-EX01.campusad.msu.edu> References: <35E2A8E8997F6C48A5D5FC21602BDEB60164A93C41@CAD-EX01.campusad.msu.edu> Message-ID: Hi Ed, Here are the config options. # :report_volume if true the report will show the cubic volume, # otherwise linear based on extent dimension # :unit values = :inches, :feet, :centimeters, :meters # defaults to the first unit it finds when calculating extent # :decimal_places = the number of decimal places to show in the extent value # defaults to 2 AppConfig[:container_management_extent_calculator] = { :report_volume => false, :unit => :feet, :decimal_places => 3 } So, just set :report_volume to true and you should be good. Cheers, James > On Jun 21, 2018, at 6:50 AM, Busch, Ed wrote: > > Does the ASpace Extent Calculation only do linear feet or can it do cubic feet? I've tried changing the Extent Dimension but that doesn't seem to effect the units. > > Ed Busch > Electronic Records Archivist > MSU Archives > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > !DSPAM:5b2abe8f522559955512038! -------------- next part -------------- An HTML attachment was scrubbed... URL: From buschedw at msu.edu Thu Jun 21 08:18:51 2018 From: buschedw at msu.edu (Busch, Ed) Date: Thu, 21 Jun 2018 12:18:51 +0000 Subject: [Archivesspace_Users_Group] Extent Calculation In-Reply-To: References: <35E2A8E8997F6C48A5D5FC21602BDEB60164A93C41@CAD-EX01.campusad.msu.edu> Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB60164A94304@CAD-EX01.campusad.msu.edu> Oh, duh. I should of known to look there. :) Thanks! Ed Busch Electronic Records Archivist MSU Archives From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of James Bullen Sent: Wednesday, June 20, 2018 7:27 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Extent Calculation Hi Ed, Here are the config options. # :report_volume if true the report will show the cubic volume, # otherwise linear based on extent dimension # :unit values = :inches, :feet, :centimeters, :meters # defaults to the first unit it finds when calculating extent # :decimal_places = the number of decimal places to show in the extent value # defaults to 2 AppConfig[:container_management_extent_calculator] = { :report_volume => false, :unit => :feet, :decimal_places => 3 } So, just set :report_volume to true and you should be good. Cheers, James On Jun 21, 2018, at 6:50 AM, Busch, Ed > wrote: Does the ASpace Extent Calculation only do linear feet or can it do cubic feet? I've tried changing the Extent Dimension but that doesn't seem to effect the units. Ed Busch Electronic Records Archivist MSU Archives _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group !DSPAM:5b2abe8f522559955512038! -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Thu Jun 21 11:54:19 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Thu, 21 Jun 2018 15:54:19 +0000 Subject: [Archivesspace_Users_Group] Annual Member Forum - reception announcement! Message-ID: Hi everyone, We are thrilled to share an update on our upcoming Annual Member Forum! This year we're excited to join forces with our friends at Archive-It to co-host a reception that will bring our partner communities together. Join us at the Conservation Pavilion at the National Zoo from 5-7 PM for drinks, hors d'oeuvres, and good times! [logos connected by bridge] The Conservation Pavilion is a new building at the National Zoo - so new that it's yet to have made a print on Google Maps. It is close to the Mane Grill, and represented as #11 on the map here: https://nationalzoo.si.edu/visit/zoo-map. The reception is located central to the conference hotel as well as the member forum site, approximately 1.0 miles between each location. [cid:image003.jpg at 01D4093D.6FD40D10] [cid:image007.png at 01D4093B.6A15EFD0] indicates DC Circulator route. Detailed directions will be provided on the program wiki page. The ArchivesSpace 4th Annual Member Forum will take place on August 14 at the Josephine Butler Parks Center in Washington DC. The planning group continues to accept submissions and topic suggestions! There is a short Google submission form available at https://goo.gl/forms/6L9UsylUz5u2Ws5n1.Proposals, ideas, and suggestions received by June 26 will receive priority consideration. Please let me know if you have any questions. We look forward to seeing you in a couple of months! Best wishes, Christine Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 22358 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 2244 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 70328 bytes Desc: image003.jpg URL: From roliveir at conncoll.edu Thu Jun 21 14:36:06 2018 From: roliveir at conncoll.edu (Rose Oliveira) Date: Thu, 21 Jun 2018 14:36:06 -0400 Subject: [Archivesspace_Users_Group] Rapid Data Entry errors In-Reply-To: References: <7DE35B3E-7528-4DB0-8F8F-8FDF75B2E091@lib.msu.edu> Message-ID: I have a similar problem. I recreated our templates to try and fix this problem. However, when I try to save I get a property missing error. All the required information is in the correct field. Has anyone else experienced this? On Fri, May 18, 2018 at 8:33 AM Lisa Calahan wrote: > We also had this problem. I ended up deleting the 20+ templates we had > saved and creating new ones. > > > > On Wed, May 16, 2018 at 8:13 PM, Tang, Lydia wrote: > >> Hi Chris, >> I just wanted to chime in and say that we experienced this as well. We >> ended up replacing our templates after the 2.x upgrade. Luckily, we didn?t >> have many specialized templates to update. >> Lydia >> >> From: on >> behalf of Christina Barber >> Reply-To: Archivesspace Users Group < >> archivesspace_users_group at lyralists.lyrasis.org> >> Date: Wednesday, May 16, 2018 at 12:36 PM >> To: "archivesspace_users_group at lyralists.lyrasis.org" < >> archivesspace_users_group at lyralists.lyrasis.org> >> Subject: [Archivesspace_Users_Group] Rapid Data Entry errors >> >> Hi all, >> >> Since upgrading to ArchivesSpace v. 2.3.2 from v. 1.5.3, we have >> encountered an error with Rapid Data Entry. Rapid Data Entry templates, >> both templates created in the new version and templates carried over from >> the previous version, are appearing ? for lack of a better word ? broken. >> Here are two screen shots of how our templates can appear in the Rapid Data >> Entry screen: occasionally with fields falling under incorrect elements >> (i.e. Label fields appearing under Date) or with a whole slew of other >> elements jumbled together without fields to edit, as in the first screen >> shot. These cause errors and an inability to save because some of the >> fields that are not appearing are required fields. Has anyone encountered >> a similar problem or have ideas about what?s gone wrong? Our ArchivesSpace >> is hosted locally and managed by the College?s IT department. >> >> Thanks, all, for any help, >> Chris Barber >> >> Christina E. Barber >> Deputy Archivist >> Amherst College >> cbarber at amherst.edu >> >> [cid:image001.jpg at 01D3ED12.4FCA0430] >> >> [cid:image002.png at 01D3ED12.4FCA0430] >> >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Pronouns: She/her/hers > Head of Archival Processing > University of Minnesota Libraries > Archives and Special Collections > Elmer L. Andersen Library, Suite 315 > 222-21st Ave. S. > Minneapolis MN 55455 > > Phone: 612.626.2531 > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Rose Oliveira Linda Lear Special Collections Librarian Linda Lear Center for Special Collections and Archives Connecticut College Charles E. Shain Library 270 Mohegan Ave. New London, CT 06320 Preferred pronouns: she/her/hers Phone: 860-439-5053 Web: http://learcenter.conncoll.edu Tumblr: lindalearcenter.tumblr.com Twitter: https://twitter.com/ConnCollLibTech -------------- next part -------------- An HTML attachment was scrubbed... URL: From reesj at mail.nlm.nih.gov Thu Jun 21 15:42:59 2018 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Thu, 21 Jun 2018 19:42:59 +0000 Subject: [Archivesspace_Users_Group] EAD import extents mapping Message-ID: Using the background job importer, I'm trying to import extent data from EAD 2002 schema XML, specifically the other extent data we record in parenthesis like 15.0 linear feet (36 boxes + oversize folder) I'd like these parenthetical statements to map to the Container Summary field. According to the EAD import mapper http://archivesspace.org/wp-content/uploads/2016/05/EAD-Import-Export-Mapping-20171030.xlsx anything after a number and space that can't be parsed should import into Container Summary. Is there a syntax for making this string unparsable and force this behavior? Currently "linear feet (36 boxes + oversize folder)" from the above imports to Extent @Type as a new unique value and I don't want all that data pollution. Thanks, John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 -------------- next part -------------- An HTML attachment was scrubbed... URL: From susan.thomas at bodleian.ox.ac.uk Fri Jun 22 08:31:19 2018 From: susan.thomas at bodleian.ox.ac.uk (Susan Thomas) Date: Fri, 22 Jun 2018 12:31:19 +0000 Subject: [Archivesspace_Users_Group] Consultancy opportunity: options assessment for circulation of archives and manuscripts at the Bodleian Libraries Message-ID: Dear colleagues, The Bodleian Libraries is seeking a consultant to conduct an options assessment for implementing a system of circulation for its archives and manuscripts. It is anticipated that this work will take place during July-Oct 2018, with the final version of the options assessment report due before 31 Oct 2018. If this work is of interest, please email me to obtain the 'Request for Quotations' document, which provides full background and details. The deadline for quotations is 9 July 2018 at 12.00 GMT. Best wishes, Susan Susan Thomas Head of Archives & Modern Manuscripts Bodleian Library Web: http://www.bodleian.ox.ac.uk/special-collections Tel: +44 (0) 1865 283821 Post: Weston Library, Broad Street, Oxford, OX1 3BG -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Fri Jun 22 08:50:10 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Fri, 22 Jun 2018 12:50:10 +0000 Subject: [Archivesspace_Users_Group] EAD import extents mapping In-Reply-To: References: Message-ID: John, What I think that you'd want to do in this case is to modify the EAD so that it looks like the following: 15.0 linear_feet (36 boxes + oversize folder) Two important points about this: 1. The ASpace EAD importer uses the database values for controlled value fields, which is why I've changed linear feet to "linear_feet" ("linear_feet" is one of the database values available in ASpace by default, but if that's not the value that matches your YML translation, you might want to use another one). The ASpace EAD exporter, on the other hand, will use the YML translation when exporting the EAD, so you'd wind up with "linear feet" in the export, or whatever else is specified in the YML file that's being employed by your application. 2. Whatever you put into a second extent statement will be mapped to the Container Summary field in ArchivesSpace. This is essentially following the AT model for importing EAD physdesc elements. I wish, instead, that ASpace would only add extent values based on the availability of the extent/@unit attribute in EAD 2002. That would make things a lot less dicey than trying to parse the text field of an extent element during import time, but it would require more EAD manipulation for a lot of folks before importing that data since the @unit attribute isn't heavily used. Mark p.s. the physdesc/@label attribute, however, does NOT get mapped at all by ASpace. Instead, it's dropped silently during the import process. That used to be the case, at least. I haven't checked in a while to see if that behavior has been changed, but in general label attributes and head elements will usually map to the ASpace label field. p.p.s. I've never tested to see what happens if you have a third sibling extent statement (to see if those get dropped or appended to container summary). But I have tested using dimensions and/or physfacet within the same grouping, and those are imported as expected. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Rees, John (NIH/NLM) [E] Sent: Thursday, 21 June, 2018 3:43 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] EAD import extents mapping Using the background job importer, I'm trying to import extent data from EAD 2002 schema XML, specifically the other extent data we record in parenthesis like 15.0 linear feet (36 boxes + oversize folder) I'd like these parenthetical statements to map to the Container Summary field. According to the EAD import mapper http://archivesspace.org/wp-content/uploads/2016/05/EAD-Import-Export-Mapping-20171030.xlsx anything after a number and space that can't be parsed should import into Container Summary. Is there a syntax for making this string unparsable and force this behavior? Currently "linear feet (36 boxes + oversize folder)" from the above imports to Extent @Type as a new unique value and I don't want all that data pollution. Thanks, John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Fri Jun 22 08:59:22 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Fri, 22 Jun 2018 12:59:22 +0000 Subject: [Archivesspace_Users_Group] EAD import extents mapping In-Reply-To: References: Message-ID: John, And it case it helps, here's the admittedly hacky way that I've handled this in the past, only focusing on splitting out those linear footage statements since that's what we had to deal with: I should note, though, that our incoming EAD files would only have a single extent statement to begin with, so I wouldn't use this without inspecting another EAD corpus before running it there. But for the example that you originally provided, it should do the trick. Just be careful if those statements aren't uniform in your corpus, since the above template really only expects physdesc elements with a single extent child. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Friday, 22 June, 2018 8:50 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] EAD import extents mapping John, What I think that you'd want to do in this case is to modify the EAD so that it looks like the following: 15.0 linear_feet (36 boxes + oversize folder) Two important points about this: 1. The ASpace EAD importer uses the database values for controlled value fields, which is why I've changed linear feet to "linear_feet" ("linear_feet" is one of the database values available in ASpace by default, but if that's not the value that matches your YML translation, you might want to use another one). The ASpace EAD exporter, on the other hand, will use the YML translation when exporting the EAD, so you'd wind up with "linear feet" in the export, or whatever else is specified in the YML file that's being employed by your application. 2. Whatever you put into a second extent statement will be mapped to the Container Summary field in ArchivesSpace. This is essentially following the AT model for importing EAD physdesc elements. I wish, instead, that ASpace would only add extent values based on the availability of the extent/@unit attribute in EAD 2002. That would make things a lot less dicey than trying to parse the text field of an extent element during import time, but it would require more EAD manipulation for a lot of folks before importing that data since the @unit attribute isn't heavily used. Mark p.s. the physdesc/@label attribute, however, does NOT get mapped at all by ASpace. Instead, it's dropped silently during the import process. That used to be the case, at least. I haven't checked in a while to see if that behavior has been changed, but in general label attributes and head elements will usually map to the ASpace label field. p.p.s. I've never tested to see what happens if you have a third sibling extent statement (to see if those get dropped or appended to container summary). But I have tested using dimensions and/or physfacet within the same grouping, and those are imported as expected. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Rees, John (NIH/NLM) [E] Sent: Thursday, 21 June, 2018 3:43 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] EAD import extents mapping Using the background job importer, I'm trying to import extent data from EAD 2002 schema XML, specifically the other extent data we record in parenthesis like 15.0 linear feet (36 boxes + oversize folder) I'd like these parenthetical statements to map to the Container Summary field. According to the EAD import mapper http://archivesspace.org/wp-content/uploads/2016/05/EAD-Import-Export-Mapping-20171030.xlsx anything after a number and space that can't be parsed should import into Container Summary. Is there a syntax for making this string unparsable and force this behavior? Currently "linear feet (36 boxes + oversize folder)" from the above imports to Extent @Type as a new unique value and I don't want all that data pollution. Thanks, John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Jun 22 09:24:26 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 22 Jun 2018 13:24:26 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v2.4.1 now available Message-ID: ArchivesSpace is announcing the availability of v2.4.1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.4.1. This minor release fixes a bug introduced in 2.4.0 that affected searching by date in the public user interface. Thank you to Mark Custer for identifying the issue so that our developers could quickly address it. The release also contains two community contributions related to the backend, for which we thank James Bullen and Chris Fitzpatrick. Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not yet upgraded to 2.4.0, we recommend going directly to 2.4.1. Also, if you are not currently using the public user interface, you may want to skip this release and wait for our next, larger release, which we expect to come in late July. The fixes in this release will also be included in that one. If you have any questions or need help upgrading - or deciding whether to upgrade - please let us know. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From matt.lawson at uni.edu Fri Jun 22 09:36:42 2018 From: matt.lawson at uni.edu (Matthew Lawson) Date: Fri, 22 Jun 2018 08:36:42 -0500 Subject: [Archivesspace_Users_Group] Finding aids missing after migration Message-ID: We recently migrated to ArchivesSpace 2.3.2 from Archon. Our collection organization and container inventory tabs do not lead to any URL and the Folders link to empty folders. Has anyone seen this before? Might a plausible way of addressing the situation be to re-import this data as EAD? -Matt Lawson University of Iowa -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Fri Jun 22 11:41:01 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Fri, 22 Jun 2018 15:41:01 +0000 Subject: [Archivesspace_Users_Group] Finalized program for the SoCal Regional Forum - June 28 Message-ID: Hi everyone, I would like to offer a correction and clarification on the SoCal Regional Forum. The date of the forum is Thursday, June 28. Registration is still open! https://www.eventbrite.com/e/archivesspace-regional-forum-southern-california-2018-tickets-44930947674 Best wishes, Christine Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_member_reps-bounces at lyralists.lyrasis.org [mailto:archivesspace_member_reps-bounces at lyralists.lyrasis.org] On Behalf Of Christine Kim Sent: Tuesday, June 19, 2018 4:02 PM Subject: [Archivesspace_member_reps] Finalized program for the SoCal Regional Forum - June 28 Hi everyone, We are one week away from the SoCal Regional Forum! The finalized program for the SoCal Regional Forum is now available and includes information on presentations, workshops, the post-forum mixer, and parking information. * Program: A finalized program is now available: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/533168147/SoCal+Regional+Forum * Afternoon activities: Selected by the community vote through registration, the afternoon will provide a variety of overviews in different formats. We will have an Introduction to ArchivesSpace workshop for those who choose to attend, with a group discussion on a variety of topics running in parallel. Following, we will have an overview of plug-ins. Last, we will have demonstration and discussion of the Digital Objects module. A laptop is not required to follow along, but is welcome if you'd like to try anything out. * Lunch: A catered lunch will be provided. * Post-event mixer: After the program's conclusion, we will move out to the Anthill Pub & Grille for an optional (and fun!) opportunity to continue our conversations in a more casual and personal way * On-site volunteers: If you plan to attend the forum, please consider volunteering for special tasks throughout the day. This will not be a full day commitment, but rather for specific assigned segments throughout the day, such as notetaking or photography. Please feel free to view the opportunities and sign up directly on this sheet: https://goo.gl/Hc662B Registration is still open! https://www.eventbrite.com/e/archivesspace-regional-forum-southern-california-2018-tickets-44930947674 Special thanks to working group members Elvia Arroyo-Ramirez (UCI Libraries), Krystal Tribbett (UCI Libraries), and Margaret Hughes (UCLA) for putting together an incredible program. Best wishes, Christine Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: From Daniel.Thacker at tamuk.edu Fri Jun 22 12:01:48 2018 From: Daniel.Thacker at tamuk.edu (Daniel L Thacker) Date: Fri, 22 Jun 2018 16:01:48 +0000 Subject: [Archivesspace_Users_Group] That ID is already in use problem and not being able to delete Message-ID: Hello, We imported a collection on Monday and it went through fine. Then we had an error where we could not merge collections (it was an "db_error" {"Database integrity constraint conflict: Java: ComMysqlJdbcExceptionsJdbc4::MySQLTransactionRollbackException: Lock wait timeout exceeded: try restarting transaction"). We tired to back up the database straight from MySQL and took 30 minutes instead of the usual 10 seconds. Then we decided to roll back to a previous back-up, which worked. The collection I put in on Monday was gone. Since we went to the back-up I had to re-import the collection I put in on Monday. The collection did not go through this time and got an "id_0 : That ID is already in use" error. We cleared the indexes in the data folder and restored the backup again but the problem continues to exist. I have attached the part of the error log that corresponds with our problem. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: archivesspace errors.txt URL: From psutherland at amphilsoc.org Fri Jun 22 13:53:08 2018 From: psutherland at amphilsoc.org (Paul Sutherland) Date: Fri, 22 Jun 2018 13:53:08 -0400 Subject: [Archivesspace_Users_Group] Re-ordering plugins Message-ID: Hi all, I have checked Awesome ArchivesSpace and can't see anything that looks like this. Please let me know if I'm missing it. I am wondering if anyone has created plugins for: - bulk re-ordering records at the same level and with the same parent (e.g. children of a series, either alphabetically or chronologically by begin date); - inserting new records as adjacent siblings of a currently selected record (a functionality that Archivists' Toolkit had) Since moving from Archivists' Toolkit, it has become difficult to deal with very large series that are not already arranged before entry, as all new records go to the end of their level. Plugins for these operations would help greatly with daily entry. Thank you for any assistance, Paul -- *Paul Sutherland* (he/his) Archivist Center for Native American and Indigenous Research American Philosophical Society 105 S. 5th Street, 2nd Floor Philadelphia, PA 19406 215-440-3408 amphilsoc.org/library/CNAIR Browse our new Indigenous Subject Guide and read our latest blog posts Twitter: @paulssutherland -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Jun 22 14:48:08 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 22 Jun 2018 18:48:08 +0000 Subject: [Archivesspace_Users_Group] That ID is already in use problem and not being able to delete In-Reply-To: References: Message-ID: Hi Daniel, I'm going to put a support ticket in for you on this. (You'll see another message about that directly to you in a minute.) It'd be great if you posted the answer back to the list when it's resolved. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Daniel L Thacker Sent: Friday, June 22, 2018 12:02 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] That ID is already in use problem and not being able to delete Hello, We imported a collection on Monday and it went through fine. Then we had an error where we could not merge collections (it was an "db_error" {"Database integrity constraint conflict: Java: ComMysqlJdbcExceptionsJdbc4::MySQLTransactionRollbackException: Lock wait timeout exceeded: try restarting transaction"). We tired to back up the database straight from MySQL and took 30 minutes instead of the usual 10 seconds. Then we decided to roll back to a previous back-up, which worked. The collection I put in on Monday was gone. Since we went to the back-up I had to re-import the collection I put in on Monday. The collection did not go through this time and got an "id_0 : That ID is already in use" error. We cleared the indexes in the data folder and restored the backup again but the problem continues to exist. I have attached the part of the error log that corresponds with our problem. Thanks, Daniel Thacker Digital Archivist James C. Jernigan Library Texas A&M University-Kingsville MSC 197 700 University Blvd Kingsville, TX 78363-8202 361-593-4154 -------------- 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 reesj at mail.nlm.nih.gov Fri Jun 22 15:08:52 2018 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Fri, 22 Jun 2018 19:08:52 +0000 Subject: [Archivesspace_Users_Group] EAD import extents mapping In-Reply-To: References: Message-ID: Thanks Mark. Luckily we only use one statement and the syntax is pretty uniform across our corpus. Today I discovered a 2nd sans will also import nicely into a Physical Description Note. This note exports as a vanilla but your approach produces more specific and parsable EAD for down the road. And yes, I've been tracking the silent label drops esp. since our external public access application often depends on them. John From: Custer, Mark [mailto:mark.custer at yale.edu] Sent: Friday, June 22, 2018 8:59 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] EAD import extents mapping John, And it case it helps, here's the admittedly hacky way that I've handled this in the past, only focusing on splitting out those linear footage statements since that's what we had to deal with: I should note, though, that our incoming EAD files would only have a single extent statement to begin with, so I wouldn't use this without inspecting another EAD corpus before running it there. But for the example that you originally provided, it should do the trick. Just be careful if those statements aren't uniform in your corpus, since the above template really only expects physdesc elements with a single extent child. Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Friday, 22 June, 2018 8:50 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] EAD import extents mapping John, What I think that you'd want to do in this case is to modify the EAD so that it looks like the following: 15.0 linear_feet (36 boxes + oversize folder) Two important points about this: 1. The ASpace EAD importer uses the database values for controlled value fields, which is why I've changed linear feet to "linear_feet" ("linear_feet" is one of the database values available in ASpace by default, but if that's not the value that matches your YML translation, you might want to use another one). The ASpace EAD exporter, on the other hand, will use the YML translation when exporting the EAD, so you'd wind up with "linear feet" in the export, or whatever else is specified in the YML file that's being employed by your application. 2. Whatever you put into a second extent statement will be mapped to the Container Summary field in ArchivesSpace. This is essentially following the AT model for importing EAD physdesc elements. I wish, instead, that ASpace would only add extent values based on the availability of the extent/@unit attribute in EAD 2002. That would make things a lot less dicey than trying to parse the text field of an extent element during import time, but it would require more EAD manipulation for a lot of folks before importing that data since the @unit attribute isn't heavily used. Mark p.s. the physdesc/@label attribute, however, does NOT get mapped at all by ASpace. Instead, it's dropped silently during the import process. That used to be the case, at least. I haven't checked in a while to see if that behavior has been changed, but in general label attributes and head elements will usually map to the ASpace label field. p.p.s. I've never tested to see what happens if you have a third sibling extent statement (to see if those get dropped or appended to container summary). But I have tested using dimensions and/or physfacet within the same grouping, and those are imported as expected. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Rees, John (NIH/NLM) [E] Sent: Thursday, 21 June, 2018 3:43 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] EAD import extents mapping Using the background job importer, I'm trying to import extent data from EAD 2002 schema XML, specifically the other extent data we record in parenthesis like 15.0 linear feet (36 boxes + oversize folder) I'd like these parenthetical statements to map to the Container Summary field. According to the EAD import mapper http://archivesspace.org/wp-content/uploads/2016/05/EAD-Import-Export-Mapping-20171030.xlsx anything after a number and space that can't be parsed should import into Container Summary. Is there a syntax for making this string unparsable and force this behavior? Currently "linear feet (36 boxes + oversize folder)" from the above imports to Extent @Type as a new unique value and I don't want all that data pollution. Thanks, John John P. Rees Archivist and Digital Resources Manager History of Medicine Division National Library of Medicine 301-827-4510 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsprouse at tsl.texas.gov Mon Jun 25 11:34:28 2018 From: dsprouse at tsl.texas.gov (Daniel Sprouse) Date: Mon, 25 Jun 2018 15:34:28 +0000 Subject: [Archivesspace_Users_Group] version string Message-ID: what is the quickest way to pull a version.major-release.minor-release string from archivesspace at the command line? Any chance that the version could be added as on option in archivesspace.sh, like having archivesspace.sh [start|status|version|stop|restart] ? Daniel Sprouse, Linux Administrator Texas State Library & Archives Commission G 19.01 tel: 512-463-5482 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Mon Jun 25 11:52:14 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Mon, 25 Jun 2018 15:52:14 +0000 Subject: [Archivesspace_Users_Group] version string In-Reply-To: References: Message-ID: <0455A14B-181D-410E-9797-2B0C1AD6600D@virginia.edu> curl to the root of the backend server ( port 8089 by default ) ( No authentication necessary for ?/? , so you don?t need login credentials. ) curl http://localhost:8089/ { "databaseProductName": "MySQL", "databaseProductVersion": "5.1.73", "ruby_version": "2.3.0", "host_os": "linux", "host_cpu": "x86_64", "build": "java1.7", "archivesSpaceVersion": "v2.4.1" } > On Jun 25, 2018, at 11:34 AM, Daniel Sprouse wrote: > > what is the quickest way to pull a version.major-release.minor-release string from archivesspace at the command line? > Any chance that the version could be added as on option in archivesspace.sh, like having archivesspace.sh[start|status|version|stop|restart] ? > > Daniel Sprouse, Linux Administrator > Texas State Library & Archives Commission > G 19.01 tel: 512-463-5482 > > _______________________________________________ > 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: 6091 bytes Desc: not available URL: From dsprouse at tsl.texas.gov Mon Jun 25 13:24:36 2018 From: dsprouse at tsl.texas.gov (Daniel Sprouse) Date: Mon, 25 Jun 2018 17:24:36 +0000 Subject: [Archivesspace_Users_Group] mysqlconnector 5.1.46 Message-ID: currently using mysql-connector-java-5.1.45 have any been seen moving to mysql-connector-java-5.1.46 (GA release)? Daniel Sprouse, Linux Administrator Texas State Library & Archives Commission G 19.01 tel: 512-463-5482 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Mon Jun 25 17:11:32 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Mon, 25 Jun 2018 21:11:32 +0000 Subject: [Archivesspace_Users_Group] [Archivesspace_tac] Webinar Announcement: Transforming XLS to EAD -- June 27 In-Reply-To: References: Message-ID: Reminder - Join us for the Transforming XLS to EAD: Importing Component Hierarchies webinar on Wednesday, June 27! Details: http://archivesspace.org/archives/3016 Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis From: archivesspace_tac-bounces at lyralists.lyrasis.org [mailto:archivesspace_tac-bounces at lyralists.lyrasis.org] On Behalf Of Christine Kim Sent: Tuesday, June 19, 2018 10:36 AM To: Archivesspace Users Group ; Archivesspace Member Reps ; Archivesspace_tac at lyralists.lyrasis.org; Archivesspace_uac at lyralists.lyrasis.org; archivesspace_bot_members at lyralists.lyrasis.org Subject: [Archivesspace_tac] Webinar Announcement: Transforming XLS to EAD -- June 27 Transforming XLS to EAD: Importing Component Hierarchies When: Wednesday, June 27, 2018 Time: 1:00 p.m. - 2:30 p.m. ET (10:00 a.m. - 11:30 a.m. PT) Where: Webinar at http://lyrasis.adobeconnect.com/ruio9pyqjot4/ 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 on the ArchivesSpace YouTube channel. Webinar description: Do you list out your components on a spreadsheet before committing the item records into ArchivesSpace? If this is your preferred processing workflow, you're not alone. In this webinar, we will look at three distinct methods to get your spreadsheet rows and columns into your ArchivesSpace resource record to populate components. First, Elizabeth Perkes (Utah State Archives) will demonstrate a workflow that uses built-in Microsoft Office tools to convert Microsoft Excel spreadsheets to EAD via mail merge. Jason Ronallo (North Carolina State University) will provide a demo of the Stead schema and Steady tool he developed, which is a command line tool and web application that uses Ruby to transform data in spreadsheets into EAD component levels. And Ben Johnson (Harvard Business School) uses a spreadsheet importer plugin developed by Bobbi Fox (Harvard University) in a variety of ways. However, he will provide an overview of one simple use of the tool: How to easily and quickly add bulk data from new accessions to existing resources. Ben will walk through our workflow for that and show some limitations and pitfalls to avoid. But perhaps you would like to see more than just workflows. Kelly Spring (East Carolina University) will provide insight into some of the common troubleshooting and other tasks that will help you successfully upload the EAD to ArchivesSpace. Presenters: Elizabeth Perkes has worked for the Utah State Archives for almost 28 years. In that capacity she has primarily managed our database systems, websites, and electronic records. In 2000, she converted all of their finding aids to EAD. The general methodology used in that project became a small how-to video in 2008, which is being updated and described today. Jason Ronallo is the Department Head of Digital Library Initiatives at NCSU Libraries. Current interests include IIIF and researcher support. You can learn more about his work at https://ronallo.com/ Ben Johnson is the Senior Processing Archivist at Baker Library, Harvard Business School, where he is perpetually processing the Polaroid Corporation records. Ben helps develop and implement procedures and workflows to better streamline the processing of collections. He also frequently finds himself working with audiovisual materials. Kelly Spring is the Access Archivist at East Carolina University where, currently, she aspires to AS migration wizardry with a team of talented colleagues. Who should attend: Everyone interested in seeing a demonstration of a variety of practices to import your spreadsheet contents into ArchivesSpace. Please feel free to bring any questions you have. Questions? Please contact Kim at christine.kim at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From tadams at cshl.edu Mon Jun 25 18:14:09 2018 From: tadams at cshl.edu (Adams, Thomas) Date: Mon, 25 Jun 2018 22:14:09 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace failing to export resource to PDF Message-ID: <9924A3758AEDEC48B06A918F5A0175FE9C124563@EX-HS-MBX02.cshl.edu> >From the staff interface in ArchivesSpace 2.3.2, I am attempting to "Export | Print resource to PDF". The batch submission get things started fine, but the job ends up with a failure status when it completes. I see the following error message: # more /home/archivesspace/archivesspace-v2.3.2/archivesspace/data/shared/job_files/print_to_pdf_job_236/output.log Generating PDF for Oral History org.apache.fop.fo.ValidationException: "fo:list-block" is missing child elements. Required content model: marker* (list-item)+ (See position 1794:68) org.apache.xalan.transformer.TransformerIdentityImpl.transform(org/apache/xalan/transformer/TransformerIdentityImpl.java:502) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) .... Trevor Thornton gave the following suggestion to the ASpace mailing list (back in 2017-03-21) to a similar error message: Looks like there is a list in a note somewhere that has no list items - that what this seems to be saying: org.apache.fop.fo.ValidationException: "fo:list-block" is missing child elements. Required content model: marker* (list-item)+ (See position 508:68) I would try to export the resource as an EAD, and if that works you might more easily search through the XML to find the problem. I was able to "Export | Download EAD", that resource as suggested, but there were only three tags in the EAD and all of them had and as children. I also looked on the ArchivesSpace server and was not able to find a temporary file created at that time, that might have position 1794:68 (line#:char). Any suggestions on what to try next? Thanks -Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Tue Jun 26 09:58:07 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Tue, 26 Jun 2018 13:58:07 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace failing to export resource to PDF In-Reply-To: <9924A3758AEDEC48B06A918F5A0175FE9C124563@EX-HS-MBX02.cshl.edu> References: <9924A3758AEDEC48B06A918F5A0175FE9C124563@EX-HS-MBX02.cshl.edu> Message-ID: Thomas, If you could send me a copy of the EAD file, I can take a look this afternoon (I'm working on a new process to create PDF files in ASpace using the new EAD3 export option, but I have the current ASpace PDF files handy for testing). The issue is definitely that the current EAD to PDF process is creating an invalid XSL-FO file, which Apache FOP cannot then render properly as a PDF file, as Trevor mentioned. Without seeing the EAD file, though, it's impossible to tell if there's an issue in the EAD or the XSL file that's being used to create the temporary XSL-FO file. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Adams, Thomas Sent: Monday, June 25, 2018 6:14:09 PM To: Archivesspace Users Group (Archivesspace_Users_Group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] ArchivesSpace failing to export resource to PDF >From the staff interface in ArchivesSpace 2.3.2, I am attempting to ?Export | Print resource to PDF?. The batch submission get things started fine, but the job ends up with a failure status when it completes. I see the following error message: # more /home/archivesspace/archivesspace-v2.3.2/archivesspace/data/shared/job_files/print_to_pdf_job_236/output.log Generating PDF for Oral History org.apache.fop.fo.ValidationException: "fo:list-block" is missing child elements. Required content model: marker* (list-item)+ (See position 1794:68) org.apache.xalan.transformer.TransformerIdentityImpl.transform(org/apache/xalan/transformer/TransformerIdentityImpl.java:502) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) ?. Trevor Thornton gave the following suggestion to the ASpace mailing list (back in 2017-03-21) to a similar error message: Looks like there is a list in a note somewhere that has no list items - that what this seems to be saying: org.apache.fop.fo.ValidationException: "fo:list-block" is missing child elements. Required content model: marker* (list-item)+ (See position 508:68) I would try to export the resource as an EAD, and if that works you might more easily search through the XML to find the problem. I was able to ?Export | Download EAD?, that resource as suggested, but there were only three tags in the EAD and all of them had and as children. I also looked on the ArchivesSpace server and was not able to find a temporary file created at that time, that might have position 1794:68 (line#:char). Any suggestions on what to try next? Thanks -Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From CurbowJ at bvu.edu Tue Jun 26 10:15:27 2018 From: CurbowJ at bvu.edu (Joan Curbow) Date: Tue, 26 Jun 2018 14:15:27 +0000 Subject: [Archivesspace_Users_Group] Rapid Data Entry errors In-Reply-To: References: <7DE35B3E-7528-4DB0-8F8F-8FDF75B2E091@lib.msu.edu> Message-ID: Yes, I have this problem all the time. I?ve stopped trying to save any templates; it?s a pain not to be able to use a template, but it?s also a pain when they don?t work as they should. Sincerely, Joan Curbow Reference Librarian and Archivist Buena Vista University Library Buena Vista University 610 West Fourth Street Storm Lake, Iowa 50588 712-749-2094 curbowj at bvu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Rose Oliveira Sent: Thursday, June 21, 2018 1:36 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Rapid Data Entry errors I have a similar problem. I recreated our templates to try and fix this problem. However, when I try to save I get a property missing error. All the required information is in the correct field. Has anyone else experienced this? On Fri, May 18, 2018 at 8:33 AM Lisa Calahan > wrote: We also had this problem. I ended up deleting the 20+ templates we had saved and creating new ones. On Wed, May 16, 2018 at 8:13 PM, Tang, Lydia > wrote: Hi Chris, I just wanted to chime in and say that we experienced this as well. We ended up replacing our templates after the 2.x upgrade. Luckily, we didn?t have many specialized templates to update. Lydia From: > on behalf of Christina Barber > Reply-To: Archivesspace Users Group > Date: Wednesday, May 16, 2018 at 12:36 PM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Rapid Data Entry errors Hi all, Since upgrading to ArchivesSpace v. 2.3.2 from v. 1.5.3, we have encountered an error with Rapid Data Entry. Rapid Data Entry templates, both templates created in the new version and templates carried over from the previous version, are appearing ? for lack of a better word ? broken. Here are two screen shots of how our templates can appear in the Rapid Data Entry screen: occasionally with fields falling under incorrect elements (i.e. Label fields appearing under Date) or with a whole slew of other elements jumbled together without fields to edit, as in the first screen shot. These cause errors and an inability to save because some of the fields that are not appearing are required fields. Has anyone encountered a similar problem or have ideas about what?s gone wrong? Our ArchivesSpace is hosted locally and managed by the College?s IT department. Thanks, all, for any help, Chris Barber Christina E. Barber Deputy Archivist Amherst College cbarber at amherst.edu> [cid:image001.jpg at 01D3ED12.4FCA0430] [cid:image002.png at 01D3ED12.4FCA0430] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Pronouns: She/her/hers Head of Archival Processing University of Minnesota Libraries Archives and Special Collections Elmer L. Andersen Library, Suite 315 222-21st Ave. S. Minneapolis MN 55455 Phone: 612.626.2531 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Rose Oliveira Linda Lear Special Collections Librarian Linda Lear Center for Special Collections and Archives Connecticut College Charles E. Shain Library 270 Mohegan Ave. New London, CT 06320 Preferred pronouns: she/her/hers Phone: 860-439-5053 Web: http://learcenter.conncoll.edu Tumblr: lindalearcenter.tumblr.com Twitter: https://twitter.com/ConnCollLibTech -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Tue Jun 26 12:16:16 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Tue, 26 Jun 2018 16:16:16 +0000 Subject: [Archivesspace_Users_Group] =?windows-1252?q?Annual_Member_Forum_?= =?windows-1252?q?=96_presentation_ideas?= Message-ID: Hi everyone, Would you like to present at the ASpace Annual Member Forum on August 14? Are you still brainstorming ideas? Here are some suggestions that were submitted through our ideas form: * OAI: I?d like to hear how institutions are using the new OAI functionality. Harvesting into discovery layers? * Wikidata and Archival Description: How might ArchivesSpace (both the community and the software) encourage more participation from archivists in their day-to-day work? * Basic start up, installation: Where do I begin from scratch? * Legacy metadata: I?d be interested in a discussion of getting legacy metadata in various formats into ArchivesSpace (as in, not AT or Archon migrations). I can speak specifically about getting from .csv files, access database into ArchivesSpace, and using/modifying Stead for local use ; bulk date normalized (a la Bentley?s process), dummy top containers, and just general quandaries. We could talk tools, developing a toolkit of resources broken out by skill level and tech support availability, or something? I?d also be interested in a discussion of bulk metadata work against the API, whether through ArchivesSnake or just generally. * Agents and Subjects: I would like it if there was a discussion on Agents and Subjects, particularly in regards to how to properly form Agents and Subjects within ArchivesSpace or how others are defining how they create them within ArchivesSpace. These are just a handful of ideas! You can turn any of these suggestions into a presentation, workshop, or discussion topic. Or, feel free to submit on something new altogether! Send your ideas through this submission/suggestion form by June 26 for priority consideration. We would also love to encourage our friends and colleagues from the smaller institutions to present or lead discussions. Please email me at christine.kim at lyrasis.org if you have any questions. Thanks! Best wishes, Kim Christine Kim ArchivesSpace Community Engagement Coordinator christine.kim at lyrasis.org 800.999.8558 x4820 404.592.4820 Skype: ckim.lyrasis -------------- next part -------------- An HTML attachment was scrubbed... URL: From tadams at cshl.edu Tue Jun 26 13:04:22 2018 From: tadams at cshl.edu (Adams, Thomas) Date: Tue, 26 Jun 2018 17:04:22 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace failing to export resource to PDF Message-ID: <9924A3758AEDEC48B06A918F5A0175FE9C124B95@EX-HS-MBX02.cshl.edu> Mark, Thanks for your offer to look over my EAD, with regards to my inability to generate a PDF from a resource. I will directly forward you the EAD file (and a copy of the same file formatted for better viewing.) The "Oral History" collection is the resource I was attempting to generate a PDF from. You are able to view it at: http://archivesspace.cshl.edu/repositories/2/resources/39 BTW - Is it possible to capture the temporary XSL-FO file on my end, before it is removed by the termination of the PDF generation? That might give me a hint to which archival object might be a problem. Celia, With regards to your question: Are you using the pdf_per_repository plugin from UNLV? No. I am using the built in ASpace staff interface. Thanks -Tom Adams From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Tuesday, June 26, 2018 9:58 AM To: Archivesspace Users Group (Archivesspace_Users_Group at lyralists.lyrasis.org) Subject: Re: [Archivesspace_Users_Group] ArchivesSpace failing to export resource to PDF Thomas, If you could send me a copy of the EAD file, I can take a look this afternoon (I'm working on a new process to create PDF files in ASpace using the new EAD3 export option, but I have the current ASpace PDF files handy for testing). The issue is definitely that the current EAD to PDF process is creating an invalid XSL-FO file, which Apache FOP cannot then render properly as a PDF file, as Trevor mentioned. Without seeing the EAD file, though, it's impossible to tell if there's an issue in the EAD or the XSL file that's being used to create the temporary XSL-FO file. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Adams, Thomas Sent: Monday, June 25, 2018 6:14:09 PM To: Archivesspace Users Group (Archivesspace_Users_Group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] ArchivesSpace failing to export resource to PDF >From the staff interface in ArchivesSpace 2.3.2, I am attempting to "Export | Print resource to PDF". The batch submission get things started fine, but the job ends up with a failure status when it completes. I see the following error message: # more /home/archivesspace/archivesspace-v2.3.2/archivesspace/data/shared/job_files/print_to_pdf_job_236/output.log Generating PDF for Oral History org.apache.fop.fo.ValidationException: "fo:list-block" is missing child elements. Required content model: marker* (list-item)+ (See position 1794:68) org.apache.xalan.transformer.TransformerIdentityImpl.transform(org/apache/xalan/transformer/TransformerIdentityImpl.java:502) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) .... Trevor Thornton gave the following suggestion to the ASpace mailing list (back in 2017-03-21) to a similar error message: Looks like there is a list in a note somewhere that has no list items - that what this seems to be saying: org.apache.fop.fo.ValidationException: "fo:list-block" is missing child elements. Required content model: marker* (list-item)+ (See position 508:68) I would try to export the resource as an EAD, and if that works you might more easily search through the XML to find the problem. I was able to "Export | Download EAD", that resource as suggested, but there were only three tags in the EAD and all of them had and as children. I also looked on the ArchivesSpace server and was not able to find a temporary file created at that time, that might have position 1794:68 (line#:char). Any suggestions on what to try next? Thanks -Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Tue Jun 26 17:25:54 2018 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Tue, 26 Jun 2018 21:25:54 +0000 Subject: [Archivesspace_Users_Group] Indexing repository details in all records skews results set Message-ID: Hi All- I think this has been the behavior of AS from the beginning, but during some recent testing, I finally realized that AS is indexing the repository details with every record in the repository. Since part of our address is "6065 Webster Hall" and we have a *lot* of Daniel Webster related material (he's a Dartmouth alum), searching for "webster" is a bad thing since every record in the repo is listed. In a vanilla install, you can see the repository details in the json package in the results (result['json']), so that sort of made sense.... I've done some cooking of the indexer to remove the resolved repository details (result['json']['repository']['_resolved'] (and fiddle some other things), but even though the json representation of the search results contains no instance of the search string, I *still* get results based on the repository details. Example: Repository Name is "rauner" and the long name is "Rauner Special Collections Library" Search: "rauner" Example results in json for a top container and an archival object below. Note that these *do not* contain the string "rauner" I must be missing something in how the indexer is actually storing and searching data. I'd love to know if someone has a method to remove the repository details (and anything else global) from the results to prevent this sort of thing and to cut down on erroneous results. Thanks! Joshua TC: { "id": "/repositories/2/top_containers/53", "uri": "/repositories/2/top_containers/53", "title": "MS-1371b, Box 53", "primary_type": "top_container", "types": [ "top_container" ], "json": "{\"lock_version\":38,\"indicator\":\"53\",\"created_by\":\"admin\",\"last_modified_by\":\"admin\",\"create_time\":\"2018-06-26T20:28:33Z\",\"system_mtime\":\"2018-06-26T21:11:11Z\",\"user_mtime\":\"2018-06-26T20:28:33Z\",\"type\":\"box\",\"jsonmodel_type\":\"top_container\",\"active_restrictions\":[],\"container_locations\":[],\"series\":[],\"collection\":[{\"ref\":\"/repositories/2/resources/1\",\"identifier\":\"MS-1371b\",\"display_string\":\"Mario Puzo papers\"}],\"uri\":\"/repositories/2/top_containers/53\",\"repository\":{\"ref\":\"/repositories/2\",\"_resolved\":\"\"},\"restricted\":false,\"is_linked_to_published_record\":false,\"display_string\":\"Box 53\",\"long_display_string\":\"MS-1371b, Box 53\"}", "suppressed": false, "publish": false, "system_generated": false, "repository": "/repositories/2", "type_enum_s": [ "box" ], "created_by": "admin", "last_modified_by": "admin", "user_mtime": "2018-06-26T20:28:33Z", "system_mtime": "2018-06-26T21:11:11Z", "create_time": "2018-06-26T20:28:33Z", "display_string": "Box 53", "collection_uri_u_sstr": [ "/repositories/2/resources/1" ], "collection_display_string_u_sstr": [ "Mario Puzo papers" ], "collection_identifier_stored_u_sstr": [ "MS-1371b" ], "collection_identifier_u_stext": [ "MS-1371b", "MS 1371b", "MS1371b", "MS- 1371 b" ], "exported_u_sbool": [ false ], "empty_u_sbool": [ false ], "indicator_u_stext": [ "53" ], "jsonmodel_type": "top_container" } AO: { "id": "/repositories/2/archival_objects/3", "uri": "/repositories/2/archival_objects/3", "title": "The Fortunate Pilgrim", "primary_type": "archival_object", "types": [ "archival_object" ], "json": "{\"lock_version\":0,\"position\":2,\"publish\":true,\"ref_id\":\"a97bf46cbc2cd85e9789c76098a3ee1b\",\"title\":\"The Fortunate Pilgrim\",\"display_string\":\"The Fortunate Pilgrim\",\"restrictions_apply\":false,\"created_by\":\"admin\",\"last_modified_by\":\"admin\",\"create_time\":\"2018-06-26T20:28:33Z\",\"system_mtime\":\"2018-06-26T21:11:11Z\",\"user_mtime\":\"2018-06-26T20:28:33Z\",\"suppressed\":false,\"level\":\"series\",\"jsonmodel_type\":\"archival_object\",\"external_ids\":[],\"subjects\":[],\"linked_events\":[],\"extents\":[],\"dates\":[],\"external_documents\":[],\"rights_statements\":[],\"linked_agents\":[],\"onbase_documents\":[],\"ancestors\":[{\"ref\":\"/repositories/2/resources/1\",\"level\":\"collection\"}],\"instances\":[],\"notes\":[],\"uri\":\"/repositories/2/archival_objects/3\",\"repository\":{\"ref\":\"/repositories/2\",\"_resolved\":\"\"},\"resource\":{\"ref\":\"/repositories/2/resources/1\"},\"has_unpublished_ancestor\":false,\"resource_identifier_u_sstr\":\"MS-1371b\",\"resource_type_u_sstr\":null,\"resource_title\":\"Mario Puzo papers\"}", "suppressed": false, "publish": false, "system_generated": false, "repository": "/repositories/2", "level_enum_s": [ "series", "collection" ], "resource": "/repositories/2/resources/1", "ref_id": "a97bf46cbc2cd85e9789c76098a3ee1b", "created_by": "admin", "last_modified_by": "admin", "user_mtime": "2018-06-26T20:28:33Z", "system_mtime": "2018-06-26T21:11:11Z", "create_time": "2018-06-26T20:28:33Z", "notes": "", "level": "series", "ancestors": [ "/repositories/2/resources/1" ], "total_restrictions_u_sstr": [ "false" ], "resource_identifier_u_sstr": [ "MS-1371b" ], "resource_title_u_sstr": [ "Mario Puzo papers" ], "resource_identifier_w_title_u_sstr": [ "MS-1371b: Mario Puzo papers" ], "jsonmodel_type": "archival_object" } -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Wed Jun 27 10:31:12 2018 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Wed, 27 Jun 2018 14:31:12 +0000 Subject: [Archivesspace_Users_Group] Indexing repository details in all records skews results set In-Reply-To: References: Message-ID: I did a little more digging and to answer my own question, the "fullrecord" field holds everything (well almost) in the SOLR doc. I think that the steps to build this field, specifically the "extract_string_values" method in IndexerCommon is probably a bit greedy and probably should skip the repository in addition to the update times, etc. I'm testing that locally. My own issue was also complicated by some custom indexer stuff I'm doing that was initially adding the resource as a fully resolved attribute to the AO docs (I'm doing it differently now).....which doubled the fullrecord issue and added its own headaches for searching relevancy. Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Joshua D. Shaw Sent: Tuesday, June 26, 2018 5:25 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Indexing repository details in all records skews results set Hi All- I think this has been the behavior of AS from the beginning, but during some recent testing, I finally realized that AS is indexing the repository details with every record in the repository. Since part of our address is "6065 Webster Hall" and we have a *lot* of Daniel Webster related material (he's a Dartmouth alum), searching for "webster" is a bad thing since every record in the repo is listed. In a vanilla install, you can see the repository details in the json package in the results (result['json']), so that sort of made sense.... I've done some cooking of the indexer to remove the resolved repository details (result['json']['repository']['_resolved'] (and fiddle some other things), but even though the json representation of the search results contains no instance of the search string, I *still* get results based on the repository details. Example: Repository Name is "rauner" and the long name is "Rauner Special Collections Library" Search: "rauner" Example results in json for a top container and an archival object below. Note that these *do not* contain the string "rauner" I must be missing something in how the indexer is actually storing and searching data. I'd love to know if someone has a method to remove the repository details (and anything else global) from the results to prevent this sort of thing and to cut down on erroneous results. Thanks! Joshua TC: { "id": "/repositories/2/top_containers/53", "uri": "/repositories/2/top_containers/53", "title": "MS-1371b, Box 53", "primary_type": "top_container", "types": [ "top_container" ], "json": "{\"lock_version\":38,\"indicator\":\"53\",\"created_by\":\"admin\",\"last_modified_by\":\"admin\",\"create_time\":\"2018-06-26T20:28:33Z\",\"system_mtime\":\"2018-06-26T21:11:11Z\",\"user_mtime\":\"2018-06-26T20:28:33Z\",\"type\":\"box\",\"jsonmodel_type\":\"top_container\",\"active_restrictions\":[],\"container_locations\":[],\"series\":[],\"collection\":[{\"ref\":\"/repositories/2/resources/1\",\"identifier\":\"MS-1371b\",\"display_string\":\"Mario Puzo papers\"}],\"uri\":\"/repositories/2/top_containers/53\",\"repository\":{\"ref\":\"/repositories/2\",\"_resolved\":\"\"},\"restricted\":false,\"is_linked_to_published_record\":false,\"display_string\":\"Box 53\",\"long_display_string\":\"MS-1371b, Box 53\"}", "suppressed": false, "publish": false, "system_generated": false, "repository": "/repositories/2", "type_enum_s": [ "box" ], "created_by": "admin", "last_modified_by": "admin", "user_mtime": "2018-06-26T20:28:33Z", "system_mtime": "2018-06-26T21:11:11Z", "create_time": "2018-06-26T20:28:33Z", "display_string": "Box 53", "collection_uri_u_sstr": [ "/repositories/2/resources/1" ], "collection_display_string_u_sstr": [ "Mario Puzo papers" ], "collection_identifier_stored_u_sstr": [ "MS-1371b" ], "collection_identifier_u_stext": [ "MS-1371b", "MS 1371b", "MS1371b", "MS- 1371 b" ], "exported_u_sbool": [ false ], "empty_u_sbool": [ false ], "indicator_u_stext": [ "53" ], "jsonmodel_type": "top_container" } AO: { "id": "/repositories/2/archival_objects/3", "uri": "/repositories/2/archival_objects/3", "title": "The Fortunate Pilgrim", "primary_type": "archival_object", "types": [ "archival_object" ], "json": "{\"lock_version\":0,\"position\":2,\"publish\":true,\"ref_id\":\"a97bf46cbc2cd85e9789c76098a3ee1b\",\"title\":\"The Fortunate Pilgrim\",\"display_string\":\"The Fortunate Pilgrim\",\"restrictions_apply\":false,\"created_by\":\"admin\",\"last_modified_by\":\"admin\",\"create_time\":\"2018-06-26T20:28:33Z\",\"system_mtime\":\"2018-06-26T21:11:11Z\",\"user_mtime\":\"2018-06-26T20:28:33Z\",\"suppressed\":false,\"level\":\"series\",\"jsonmodel_type\":\"archival_object\",\"external_ids\":[],\"subjects\":[],\"linked_events\":[],\"extents\":[],\"dates\":[],\"external_documents\":[],\"rights_statements\":[],\"linked_agents\":[],\"onbase_documents\":[],\"ancestors\":[{\"ref\":\"/repositories/2/resources/1\",\"level\":\"collection\"}],\"instances\":[],\"notes\":[],\"uri\":\"/repositories/2/archival_objects/3\",\"repository\":{\"ref\":\"/repositories/2\",\"_resolved\":\"\"},\"resource\":{\"ref\":\"/repositories/2/resources/1\"},\"has_unpublished_ancestor\":false,\"resource_identifier_u_sstr\":\"MS-1371b\",\"resource_type_u_sstr\":null,\"resource_title\":\"Mario Puzo papers\"}", "suppressed": false, "publish": false, "system_generated": false, "repository": "/repositories/2", "level_enum_s": [ "series", "collection" ], "resource": "/repositories/2/resources/1", "ref_id": "a97bf46cbc2cd85e9789c76098a3ee1b", "created_by": "admin", "last_modified_by": "admin", "user_mtime": "2018-06-26T20:28:33Z", "system_mtime": "2018-06-26T21:11:11Z", "create_time": "2018-06-26T20:28:33Z", "notes": "", "level": "series", "ancestors": [ "/repositories/2/resources/1" ], "total_restrictions_u_sstr": [ "false" ], "resource_identifier_u_sstr": [ "MS-1371b" ], "resource_title_u_sstr": [ "Mario Puzo papers" ], "resource_identifier_w_title_u_sstr": [ "MS-1371b: Mario Puzo papers" ], "jsonmodel_type": "archival_object" } -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Jun 27 10:36:33 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 27 Jun 2018 14:36:33 +0000 Subject: [Archivesspace_Users_Group] Indexing repository details in all records skews results set In-Reply-To: References: Message-ID: Hi Joshua, Thanks for posting about this. Just to clarify, are you referring to search behavior in the staff interface or the public interface (or both)? If it's the public interface, you've hit the nail on the head - the full record field is a big issue there. We've been working on specific improvements to search behavior that we believe will address situations like this. We'd love to have you test what we've been doing and can point you to it, if you'd like. (If it's the staff interface, full record exhibits the same behavior, but it seems to be an issue for fewer people.) We'd also love your help with this indexer work if you're like to talk with Laney and some others who been looking into this. Sounds like your perspective and investigations could be really helpful to everyone, especially while we're all knee deep in it! Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Joshua D. Shaw Sent: Wednesday, June 27, 2018 10:31 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Indexing repository details in all records skews results set I did a little more digging and to answer my own question, the "fullrecord" field holds everything (well almost) in the SOLR doc. I think that the steps to build this field, specifically the "extract_string_values" method in IndexerCommon is probably a bit greedy and probably should skip the repository in addition to the update times, etc. I'm testing that locally. My own issue was also complicated by some custom indexer stuff I'm doing that was initially adding the resource as a fully resolved attribute to the AO docs (I'm doing it differently now).....which doubled the fullrecord issue and added its own headaches for searching relevancy. Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Joshua D. Shaw > Sent: Tuesday, June 26, 2018 5:25 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Indexing repository details in all records skews results set Hi All- I think this has been the behavior of AS from the beginning, but during some recent testing, I finally realized that AS is indexing the repository details with every record in the repository. Since part of our address is "6065 Webster Hall" and we have a *lot* of Daniel Webster related material (he's a Dartmouth alum), searching for "webster" is a bad thing since every record in the repo is listed. In a vanilla install, you can see the repository details in the json package in the results (result['json']), so that sort of made sense.... I've done some cooking of the indexer to remove the resolved repository details (result['json']['repository']['_resolved'] (and fiddle some other things), but even though the json representation of the search results contains no instance of the search string, I *still* get results based on the repository details. Example: Repository Name is "rauner" and the long name is "Rauner Special Collections Library" Search: "rauner" Example results in json for a top container and an archival object below. Note that these *do not* contain the string "rauner" I must be missing something in how the indexer is actually storing and searching data. I'd love to know if someone has a method to remove the repository details (and anything else global) from the results to prevent this sort of thing and to cut down on erroneous results. Thanks! Joshua TC: { "id": "/repositories/2/top_containers/53", "uri": "/repositories/2/top_containers/53", "title": "MS-1371b, Box 53", "primary_type": "top_container", "types": [ "top_container" ], "json": "{\"lock_version\":38,\"indicator\":\"53\",\"created_by\":\"admin\",\"last_modified_by\":\"admin\",\"create_time\":\"2018-06-26T20:28:33Z\",\"system_mtime\":\"2018-06-26T21:11:11Z\",\"user_mtime\":\"2018-06-26T20:28:33Z\",\"type\":\"box\",\"jsonmodel_type\":\"top_container\",\"active_restrictions\":[],\"container_locations\":[],\"series\":[],\"collection\":[{\"ref\":\"/repositories/2/resources/1\",\"identifier\":\"MS-1371b\",\"display_string\":\"Mario Puzo papers\"}],\"uri\":\"/repositories/2/top_containers/53\",\"repository\":{\"ref\":\"/repositories/2\",\"_resolved\":\"\"},\"restricted\":false,\"is_linked_to_published_record\":false,\"display_string\":\"Box 53\",\"long_display_string\":\"MS-1371b, Box 53\"}", "suppressed": false, "publish": false, "system_generated": false, "repository": "/repositories/2", "type_enum_s": [ "box" ], "created_by": "admin", "last_modified_by": "admin", "user_mtime": "2018-06-26T20:28:33Z", "system_mtime": "2018-06-26T21:11:11Z", "create_time": "2018-06-26T20:28:33Z", "display_string": "Box 53", "collection_uri_u_sstr": [ "/repositories/2/resources/1" ], "collection_display_string_u_sstr": [ "Mario Puzo papers" ], "collection_identifier_stored_u_sstr": [ "MS-1371b" ], "collection_identifier_u_stext": [ "MS-1371b", "MS 1371b", "MS1371b", "MS- 1371 b" ], "exported_u_sbool": [ false ], "empty_u_sbool": [ false ], "indicator_u_stext": [ "53" ], "jsonmodel_type": "top_container" } AO: { "id": "/repositories/2/archival_objects/3", "uri": "/repositories/2/archival_objects/3", "title": "The Fortunate Pilgrim", "primary_type": "archival_object", "types": [ "archival_object" ], "json": "{\"lock_version\":0,\"position\":2,\"publish\":true,\"ref_id\":\"a97bf46cbc2cd85e9789c76098a3ee1b\",\"title\":\"The Fortunate Pilgrim\",\"display_string\":\"The Fortunate Pilgrim\",\"restrictions_apply\":false,\"created_by\":\"admin\",\"last_modified_by\":\"admin\",\"create_time\":\"2018-06-26T20:28:33Z\",\"system_mtime\":\"2018-06-26T21:11:11Z\",\"user_mtime\":\"2018-06-26T20:28:33Z\",\"suppressed\":false,\"level\":\"series\",\"jsonmodel_type\":\"archival_object\",\"external_ids\":[],\"subjects\":[],\"linked_events\":[],\"extents\":[],\"dates\":[],\"external_documents\":[],\"rights_statements\":[],\"linked_agents\":[],\"onbase_documents\":[],\"ancestors\":[{\"ref\":\"/repositories/2/resources/1\",\"level\":\"collection\"}],\"instances\":[],\"notes\":[],\"uri\":\"/repositories/2/archival_objects/3\",\"repository\":{\"ref\":\"/repositories/2\",\"_resolved\":\"\"},\"resource\":{\"ref\":\"/repositories/2/resources/1\"},\"has_unpublished_ancestor\":false,\"resource_identifier_u_sstr\":\"MS-1371b\",\"resource_type_u_sstr\":null,\"resource_title\":\"Mario Puzo papers\"}", "suppressed": false, "publish": false, "system_generated": false, "repository": "/repositories/2", "level_enum_s": [ "series", "collection" ], "resource": "/repositories/2/resources/1", "ref_id": "a97bf46cbc2cd85e9789c76098a3ee1b", "created_by": "admin", "last_modified_by": "admin", "user_mtime": "2018-06-26T20:28:33Z", "system_mtime": "2018-06-26T21:11:11Z", "create_time": "2018-06-26T20:28:33Z", "notes": "", "level": "series", "ancestors": [ "/repositories/2/resources/1" ], "total_restrictions_u_sstr": [ "false" ], "resource_identifier_u_sstr": [ "MS-1371b" ], "resource_title_u_sstr": [ "Mario Puzo papers" ], "resource_identifier_w_title_u_sstr": [ "MS-1371b: Mario Puzo papers" ], "jsonmodel_type": "archival_object" } -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Wed Jun 27 11:02:43 2018 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Wed, 27 Jun 2018 15:02:43 +0000 Subject: [Archivesspace_Users_Group] Indexing repository details in all records skews results set In-Reply-To: References: , Message-ID: Hi Christine- I found its in both the staff and public interfaces, though the public side does seem to be more problematic - since it seems to be even greedier about how much its adding to the index fields. I think we got "lucky" because of the whoel "webster" thing. I'd be happy to chat with Laney and anyone else about what I've been poking at! Best, Joshua PS. For the record - and in case anyone else is doing something similar - one of the issues I ran into initially had to do with adding data from ancestors. I was initially adding the resource as a fully resolved attribute to an AO using the "add_attribute_to_resolve" method and then fiddling with that data to get what I needed for faceting and display. But I had forgotten about the fullrecord field and all of the resource data was being pushed into the AO fullrecord as well. I've switched to fetching each resource, extracting the data from that, and pushing just what I need into the AO record. It adds a bunch of overhead to the indexer process, so I'd be happy to hear if anyone has a better idea! ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Christine Di Bella Sent: Wednesday, June 27, 2018 10:36 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Indexing repository details in all records skews results set Hi Joshua, Thanks for posting about this. Just to clarify, are you referring to search behavior in the staff interface or the public interface (or both)? If it?s the public interface, you?ve hit the nail on the head ? the full record field is a big issue there. We?ve been working on specific improvements to search behavior that we believe will address situations like this. We?d love to have you test what we?ve been doing and can point you to it, if you?d like. (If it?s the staff interface, full record exhibits the same behavior, but it seems to be an issue for fewer people.) We?d also love your help with this indexer work if you?re like to talk with Laney and some others who been looking into this. Sounds like your perspective and investigations could be really helpful to everyone, especially while we?re all knee deep in it! Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Joshua D. Shaw Sent: Wednesday, June 27, 2018 10:31 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Indexing repository details in all records skews results set I did a little more digging and to answer my own question, the "fullrecord" field holds everything (well almost) in the SOLR doc. I think that the steps to build this field, specifically the "extract_string_values" method in IndexerCommon is probably a bit greedy and probably should skip the repository in addition to the update times, etc. I'm testing that locally. My own issue was also complicated by some custom indexer stuff I'm doing that was initially adding the resource as a fully resolved attribute to the AO docs (I'm doing it differently now).....which doubled the fullrecord issue and added its own headaches for searching relevancy. Joshua ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Joshua D. Shaw > Sent: Tuesday, June 26, 2018 5:25 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Indexing repository details in all records skews results set Hi All- I think this has been the behavior of AS from the beginning, but during some recent testing, I finally realized that AS is indexing the repository details with every record in the repository. Since part of our address is "6065 Webster Hall" and we have a *lot* of Daniel Webster related material (he's a Dartmouth alum), searching for "webster" is a bad thing since every record in the repo is listed. In a vanilla install, you can see the repository details in the json package in the results (result['json']), so that sort of made sense.... I've done some cooking of the indexer to remove the resolved repository details (result['json']['repository']['_resolved'] (and fiddle some other things), but even though the json representation of the search results contains no instance of the search string, I *still* get results based on the repository details. Example: Repository Name is "rauner" and the long name is "Rauner Special Collections Library" Search: "rauner" Example results in json for a top container and an archival object below. Note that these *do not* contain the string "rauner" I must be missing something in how the indexer is actually storing and searching data. I'd love to know if someone has a method to remove the repository details (and anything else global) from the results to prevent this sort of thing and to cut down on erroneous results. Thanks! Joshua TC: { "id": "/repositories/2/top_containers/53", "uri": "/repositories/2/top_containers/53", "title": "MS-1371b, Box 53", "primary_type": "top_container", "types": [ "top_container" ], "json": "{\"lock_version\":38,\"indicator\":\"53\",\"created_by\":\"admin\",\"last_modified_by\":\"admin\",\"create_time\":\"2018-06-26T20:28:33Z\",\"system_mtime\":\"2018-06-26T21:11:11Z\",\"user_mtime\":\"2018-06-26T20:28:33Z\",\"type\":\"box\",\"jsonmodel_type\":\"top_container\",\"active_restrictions\":[],\"container_locations\":[],\"series\":[],\"collection\":[{\"ref\":\"/repositories/2/resources/1\",\"identifier\":\"MS-1371b\",\"display_string\":\"Mario Puzo papers\"}],\"uri\":\"/repositories/2/top_containers/53\",\"repository\":{\"ref\":\"/repositories/2\",\"_resolved\":\"\"},\"restricted\":false,\"is_linked_to_published_record\":false,\"display_string\":\"Box 53\",\"long_display_string\":\"MS-1371b, Box 53\"}", "suppressed": false, "publish": false, "system_generated": false, "repository": "/repositories/2", "type_enum_s": [ "box" ], "created_by": "admin", "last_modified_by": "admin", "user_mtime": "2018-06-26T20:28:33Z", "system_mtime": "2018-06-26T21:11:11Z", "create_time": "2018-06-26T20:28:33Z", "display_string": "Box 53", "collection_uri_u_sstr": [ "/repositories/2/resources/1" ], "collection_display_string_u_sstr": [ "Mario Puzo papers" ], "collection_identifier_stored_u_sstr": [ "MS-1371b" ], "collection_identifier_u_stext": [ "MS-1371b", "MS 1371b", "MS1371b", "MS- 1371 b" ], "exported_u_sbool": [ false ], "empty_u_sbool": [ false ], "indicator_u_stext": [ "53" ], "jsonmodel_type": "top_container" } AO: { "id": "/repositories/2/archival_objects/3", "uri": "/repositories/2/archival_objects/3", "title": "The Fortunate Pilgrim", "primary_type": "archival_object", "types": [ "archival_object" ], "json": "{\"lock_version\":0,\"position\":2,\"publish\":true,\"ref_id\":\"a97bf46cbc2cd85e9789c76098a3ee1b\",\"title\":\"The Fortunate Pilgrim\",\"display_string\":\"The Fortunate Pilgrim\",\"restrictions_apply\":false,\"created_by\":\"admin\",\"last_modified_by\":\"admin\",\"create_time\":\"2018-06-26T20:28:33Z\",\"system_mtime\":\"2018-06-26T21:11:11Z\",\"user_mtime\":\"2018-06-26T20:28:33Z\",\"suppressed\":false,\"level\":\"series\",\"jsonmodel_type\":\"archival_object\",\"external_ids\":[],\"subjects\":[],\"linked_events\":[],\"extents\":[],\"dates\":[],\"external_documents\":[],\"rights_statements\":[],\"linked_agents\":[],\"onbase_documents\":[],\"ancestors\":[{\"ref\":\"/repositories/2/resources/1\",\"level\":\"collection\"}],\"instances\":[],\"notes\":[],\"uri\":\"/repositories/2/archival_objects/3\",\"repository\":{\"ref\":\"/repositories/2\",\"_resolved\":\"\"},\"resource\":{\"ref\":\"/repositories/2/resources/1\"},\"has_unpublished_ancestor\":false,\"resource_identifier_u_sstr\":\"MS-1371b\",\"resource_type_u_sstr\":null,\"resource_title\":\"Mario Puzo papers\"}", "suppressed": false, "publish": false, "system_generated": false, "repository": "/repositories/2", "level_enum_s": [ "series", "collection" ], "resource": "/repositories/2/resources/1", "ref_id": "a97bf46cbc2cd85e9789c76098a3ee1b", "created_by": "admin", "last_modified_by": "admin", "user_mtime": "2018-06-26T20:28:33Z", "system_mtime": "2018-06-26T21:11:11Z", "create_time": "2018-06-26T20:28:33Z", "notes": "", "level": "series", "ancestors": [ "/repositories/2/resources/1" ], "total_restrictions_u_sstr": [ "false" ], "resource_identifier_u_sstr": [ "MS-1371b" ], "resource_title_u_sstr": [ "Mario Puzo papers" ], "resource_identifier_w_title_u_sstr": [ "MS-1371b: Mario Puzo papers" ], "jsonmodel_type": "archival_object" } -------------- next part -------------- An HTML attachment was scrubbed... URL: From VivianLea.Solek at Kofc.Org Wed Jun 27 14:56:32 2018 From: VivianLea.Solek at Kofc.Org (VivianLea.Solek at Kofc.Org) Date: Wed, 27 Jun 2018 14:56:32 -0400 Subject: [Archivesspace_Users_Group] Question for Small Repositories re: Cataloging Books in ASpace In-Reply-To: <01702D2A-1792-433E-8F48-1E9CEDE0CA65@lyrasis.org> References: <01702D2A-1792-433E-8F48-1E9CEDE0CA65@lyrasis.org> Message-ID: Good afternoon all, I am a lone arranger and am finalizing my data import for ArchivesSpace. I have a sizeable book collection and would like to include the books in ArchivesSpace to provide "one stop shopping" for researchers. For those in smaller repositories, are you doing something similar? Did you create a separate directory for your books? Did you include them with your record groups and collections? Thanks for any and all input. Best, VivianLea VivianLea Solek Archivist Knights of Columbus Supreme Council Archives Knights of Columbus Museum 1 State Street New Haven, CT 06511-6702 Phone 203 752-4578 Fax 203 865-0351 CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tadams at cshl.edu Wed Jun 27 14:58:30 2018 From: tadams at cshl.edu (Adams, Thomas) Date: Wed, 27 Jun 2018 18:58:30 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace failing to export resource to PDF In-Reply-To: <9924A3758AEDEC48B06A918F5A0175FE9C124B95@EX-HS-MBX02.cshl.edu> References: <9924A3758AEDEC48B06A918F5A0175FE9C124B95@EX-HS-MBX02.cshl.edu> Message-ID: <9924A3758AEDEC48B06A918F5A0175FE9C1264E5@EX-HS-MBX02.cshl.edu> Our problem exporting a PDF from an ArchivesSpace resource has been resolved. Big thanks to Mark Custer for identifying the problem. The method used to identify the problem was to export the resource as an EAD file. Then open the file in the oXygen XML editor and run validate. In this particular case, the editor flagged two tags which did not have any elements within. It also flagged a normalized date which only had a single digit in the day field. Once the errors were flagged in the XML editor, it was easy to determine which archive object needed to be adjusted. In my case just changed the Note type from "Index" to "Arrangement". There also exist the possibility that the EAD is valid, but the XSLT file might still be throwing an error. Since there does not appear to be an way to capture the temporary XSL-FO file on the ArchivesSpace server, the following was suggested by Mark: "For my testing, I always export the EAD and then run the same transformation process through oXygen XML Editor. If the PDF file fails, then oXygen keeps the temporary XSL-FO in the same location as the source EAD file, and it's easy enough to inspect things from that to see what's going on." So it appears that behind the scenes, the PDF creation process first generates a EAD XML file, which is then transformed into a PDF by a XLST file. Thanks -Tom From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Adams, Thomas Sent: Tuesday, June 26, 2018 1:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace failing to export resource to PDF Mark, Thanks for your offer to look over my EAD, with regards to my inability to generate a PDF from a resource. I will directly forward you the EAD file (and a copy of the same file formatted for better viewing.) The "Oral History" collection is the resource I was attempting to generate a PDF from. You are able to view it at: http://archivesspace.cshl.edu/repositories/2/resources/39 BTW - Is it possible to capture the temporary XSL-FO file on my end, before it is removed by the termination of the PDF generation? That might give me a hint to which archival object might be a problem. Celia, With regards to your question: Are you using the pdf_per_repository plugin from UNLV? No. I am using the built in ASpace staff interface. Thanks -Tom Adams From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Tuesday, June 26, 2018 9:58 AM To: Archivesspace Users Group (Archivesspace_Users_Group at lyralists.lyrasis.org) Subject: Re: [Archivesspace_Users_Group] ArchivesSpace failing to export resource to PDF Thomas, If you could send me a copy of the EAD file, I can take a look this afternoon (I'm working on a new process to create PDF files in ASpace using the new EAD3 export option, but I have the current ASpace PDF files handy for testing). The issue is definitely that the current EAD to PDF process is creating an invalid XSL-FO file, which Apache FOP cannot then render properly as a PDF file, as Trevor mentioned. Without seeing the EAD file, though, it's impossible to tell if there's an issue in the EAD or the XSL file that's being used to create the temporary XSL-FO file. Mark ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Adams, Thomas Sent: Monday, June 25, 2018 6:14:09 PM To: Archivesspace Users Group (Archivesspace_Users_Group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] ArchivesSpace failing to export resource to PDF >From the staff interface in ArchivesSpace 2.3.2, I am attempting to "Export | Print resource to PDF". The batch submission get things started fine, but the job ends up with a failure status when it completes. I see the following error message: # more /home/archivesspace/archivesspace-v2.3.2/archivesspace/data/shared/job_files/print_to_pdf_job_236/output.log Generating PDF for Oral History org.apache.fop.fo.ValidationException: "fo:list-block" is missing child elements. Required content model: marker* (list-item)+ (See position 1794:68) org.apache.xalan.transformer.TransformerIdentityImpl.transform(org/apache/xalan/transformer/TransformerIdentityImpl.java:502) java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498) .... Trevor Thornton gave the following suggestion to the ASpace mailing list (back in 2017-03-21) to a similar error message: Looks like there is a list in a note somewhere that has no list items - that what this seems to be saying: org.apache.fop.fo.ValidationException: "fo:list-block" is missing child elements. Required content model: marker* (list-item)+ (See position 508:68) I would try to export the resource as an EAD, and if that works you might more easily search through the XML to find the problem. I was able to "Export | Download EAD", that resource as suggested, but there were only three tags in the EAD and all of them had and as children. I also looked on the ArchivesSpace server and was not able to find a temporary file created at that time, that might have position 1794:68 (line#:char). Any suggestions on what to try next? Thanks -Tom -------------- next part -------------- An HTML attachment was scrubbed... URL: From psutherland at amphilsoc.org Thu Jun 28 13:13:43 2018 From: psutherland at amphilsoc.org (Paul Sutherland) Date: Thu, 28 Jun 2018 13:13:43 -0400 Subject: [Archivesspace_Users_Group] Fwd: Re-ordering plugins In-Reply-To: References: Message-ID: Hi all, I am forwarding this as I do not think it sent to the list last time (I did not see a message at all in my inbox, although I do see a copy on the listserv archive). Apologies it if actually sent. Best, Paul ---------- Forwarded message ---------- From: Paul Sutherland Date: Fri, Jun 22, 2018 at 1:53 PM Subject: Re-ordering plugins To: archivesspace_users_group at lyralists.lyrasis.org Hi all, I have checked Awesome ArchivesSpace and can't see anything that looks like this. Please let me know if I'm missing it. I am wondering if anyone has created plugins for: - bulk re-ordering records at the same level and with the same parent (e.g. children of a series, either alphabetically or chronologically by begin date); - inserting new records as adjacent siblings of a currently selected record (a functionality that Archivists' Toolkit had) Since moving from Archivists' Toolkit, it has become difficult to deal with very large series that are not already arranged before entry, as all new records go to the end of their level. Plugins for these operations would help greatly with daily entry. Thank you for any assistance, Paul -- *Paul Sutherland* (he/his) Archivist Center for Native American and Indigenous Research American Philosophical Society 105 S. 5th Street, 2nd Floor Philadelphia, PA 19406 215-440-3408 amphilsoc.org/library/CNAIR Browse our new Indigenous Subject Guide and read our latest blog posts Twitter: @paulssutherland -- *Paul Sutherland* (he/his) Archivist Center for Native American and Indigenous Research American Philosophical Society 105 S. 5th Street, 2nd Floor Philadelphia, PA 19406 215-440-3408 amphilsoc.org/library/CNAIR Browse our new Indigenous Subject Guide and read our latest blog posts Twitter: @paulssutherland -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Fri Jun 29 10:23:21 2018 From: gordon_daines at byu.edu (Gordon Daines) Date: Fri, 29 Jun 2018 14:23:21 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Election results and new appointments Message-ID: To members of the ArchivesSpace community, I am pleased to announce the results of the recent Governance Board election as well as new appointments to the User Advisory Council and the Technical Advisory Council. Governance Board * Cynthia Ghering, Director, University Archives, Michigan State University (Very Large member representative) * Kat Stefko, Associate Librarian for Discovery, Digitization and Special Collections and Director of the George J. Mitchell Department of Special Collections & Archives, Bowdoin College (Small member representative) Cynthia and Kat will begin their three year terms on July 1, 2018 and serve through June 30, 2021. We extend our renewed thanks to outgoing representatives Audra Eagle Yun (University of California, Irvine) and Heather Heckman (Pennsylvania State Archives). The following individuals were appointed to the User Advisory and Technical Advisory Councils and will begin their two year terms on July 1, 2018. User Advisory Council * Kevin Clair, University of Denver * Angela White, Indiana University - Purdue University Indianapolis * William Modrow, Miami University of Ohio * Kate Blalack, Woody Guthrie Center * Terra Gullings, University of Texas at Tyler * Julia Novakovic, The Strong * Adrienne Harling, San Francisco Symphony * Joshua Shaw, Dartmouth College Technical Advisory Council * Greg Wiedeman, University of Albany * Bria Parker, University of Maryland * Alicia Detelich, Yale University * Jared Campbell, University of California, Davis * Edgar Garcia, Northwestern University * Dave Mayo, Harvard University Best wishes to all as we welcome our representatives to their new roles and look ahead to the coming year. Respectfully submitted, J. Gordon Daines III Chair, 2018 Nominating Committee Brigham Young University _________________________ J. Gordon Daines III Supervisor of Reference Services Department Chair L. Tom Perry Special Collections Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Jun 29 13:31:37 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 29 Jun 2018 17:31:37 +0000 Subject: [Archivesspace_Users_Group] Fwd: Re-ordering plugins In-Reply-To: References: Message-ID: Hi Paul, I don?t know that anyone has done any plugins for either of these, but there is feature request for the application for the one about where new siblings get inserted: https://archivesspace.atlassian.net/browse/ANW-373. It has been assigned to a developer, so I?m hopeful that it can get addressed this summer for a future release. (Now if someone has created a plugin for this function (or bulk reordering), we?d love to hear about it and consider it for the core code. Please get in touch with Laney or me if that?s the case!) Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Paul Sutherland Sent: Thursday, June 28, 2018 1:14 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Fwd: Re-ordering plugins Hi all, I am forwarding this as I do not think it sent to the list last time (I did not see a message at all in my inbox, although I do see a copy on the listserv archive). Apologies it if actually sent. Best, Paul ---------- Forwarded message ---------- From: Paul Sutherland > Date: Fri, Jun 22, 2018 at 1:53 PM Subject: Re-ordering plugins To: archivesspace_users_group at lyralists.lyrasis.org Hi all, I have checked Awesome ArchivesSpace and can't see anything that looks like this. Please let me know if I'm missing it. I am wondering if anyone has created plugins for: * bulk re-ordering records at the same level and with the same parent (e.g. children of a series, either alphabetically or chronologically by begin date); * inserting new records as adjacent siblings of a currently selected record (a functionality that Archivists' Toolkit had) Since moving from Archivists' Toolkit, it has become difficult to deal with very large series that are not already arranged before entry, as all new records go to the end of their level. Plugins for these operations would help greatly with daily entry. Thank you for any assistance, Paul -- Paul Sutherland (he/his) Archivist Center for Native American and Indigenous Research American Philosophical Society 105 S. 5th Street, 2nd Floor Philadelphia, PA 19406 215-440-3408 amphilsoc.org/library/CNAIR [https://www.amphilsoc.org/sites/default/files/2018-04/attachments/APS_Franklin275_Seal_R1_020618-1.jpg] Browse our new Indigenous Subject Guide and read our latest blog posts Twitter: @paulssutherland -- Paul Sutherland (he/his) Archivist Center for Native American and Indigenous Research American Philosophical Society 105 S. 5th Street, 2nd Floor Philadelphia, PA 19406 215-440-3408 amphilsoc.org/library/CNAIR [https://www.amphilsoc.org/sites/default/files/2018-04/attachments/APS_Franklin275_Seal_R1_020618-1.jpg] Browse our new Indigenous Subject Guide and read our latest blog posts Twitter: @paulssutherland -------------- 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 psutherland at amphilsoc.org Fri Jun 29 13:59:14 2018 From: psutherland at amphilsoc.org (Paul Sutherland) Date: Fri, 29 Jun 2018 13:59:14 -0400 Subject: [Archivesspace_Users_Group] Fwd: Re-ordering plugins In-Reply-To: References: Message-ID: Dear Christine, Thank you for pointing me to that. I am glad that this is projected for development. Best, Paul On Fri, Jun 29, 2018 at 1:31 PM, Christine Di Bella < christine.dibella at lyrasis.org> wrote: > Hi Paul, > > > > I don?t know that anyone has done any plugins for either of these, but > there is feature request for the application for the one about where new > siblings get inserted: https://archivesspace.atlassian.net/browse/ANW-373. > It has been assigned to a developer, so I?m hopeful that it can get > addressed this summer for a future release. > > > > (Now if someone has created a plugin for this function (or bulk > reordering), we?d love to hear about it and consider it for the core code. > Please get in touch with Laney or me if that?s the case!) > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 > > 678-235-2905 > > cdibella13 (Skype) > > > > [image: ASpaceOrgHomeMedium] > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> *On Behalf Of *Paul > Sutherland > *Sent:* Thursday, June 28, 2018 1:14 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Fwd: Re-ordering plugins > > > > Hi all, > > > > I am forwarding this as I do not think it sent to the list last time (I > did not see a message at all in my inbox, although I do see a copy on the > listserv archive). Apologies it if actually sent. > > > > Best, > > Paul > > > > > > ---------- Forwarded message ---------- > From: *Paul Sutherland* > Date: Fri, Jun 22, 2018 at 1:53 PM > Subject: Re-ordering plugins > To: archivesspace_users_group at lyralists.lyrasis.org > > Hi all, > > > > I have checked Awesome ArchivesSpace and can't see anything that looks > like this. Please let me know if I'm missing it. > > > > I am wondering if anyone has created plugins for: > > - bulk re-ordering records at the same level and with the same parent > (e.g. children of a series, either alphabetically or chronologically by > begin date); > - inserting new records as adjacent siblings of a currently selected > record (a functionality that Archivists' Toolkit had) > > Since moving from Archivists' Toolkit, it has become difficult to deal > with very large series that are not already arranged before entry, as all > new records go to the end of their level. Plugins for these operations > would help greatly with daily entry. > > > > Thank you for any assistance, > > Paul > > > > -- > > *Paul Sutherland* (he/his) > > Archivist > > Center for Native American and Indigenous Research > > American Philosophical Society > > 105 S. 5th Street, 2nd Floor > > Philadelphia, PA 19406 > > 215-440-3408 > > amphilsoc.org/library/CNAIR > > Browse our new Indigenous Subject Guide > > > and read our latest blog posts > > > Twitter: @paulssutherland > > > > > > -- > > *Paul Sutherland* (he/his) > > Archivist > > Center for Native American and Indigenous Research > > American Philosophical Society > > 105 S. 5th Street, 2nd Floor > > Philadelphia, PA 19406 > > 215-440-3408 > > amphilsoc.org/library/CNAIR > > Browse our new Indigenous Subject Guide > > > and read our latest blog posts > > > Twitter: @paulssutherland > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- *Paul Sutherland* (he/his) Archivist Center for Native American and Indigenous Research American Philosophical Society 105 S. 5th Street, 2nd Floor Philadelphia, PA 19406 215-440-3408 amphilsoc.org/library/CNAIR Browse our new Indigenous Subject Guide and read our latest blog posts Twitter: @paulssutherland -------------- 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.Kim at lyrasis.org Fri Jun 29 20:00:33 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Sat, 30 Jun 2018 00:00:33 +0000 Subject: [Archivesspace_Users_Group] =?windows-1252?q?ArchivesSpace_Update?= =?windows-1252?q?_=96_June_2018?= Message-ID: [ASpaceOrgHome.jpg] June 2018 Update We are excited to share exciting community updates, including updates on the upcoming 4th annual Member Forum. We?re pleased to welcome new members to our three governance groups for terms that begin July 1. New stories are up on the blog, and we have another great webinar coming up next month! Read on for more news! Development ArchivesSpace is announcing the availability of v2.4.1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.4.1. This minor release fixes a bug introduced in 2.4.0 that affected searching by date in the public user interface. Thank you to Mark Custer for identifying the issue so that our developers could quickly address it. The release also contains two community contributions related to the backend, for which we thank James Bullen and Chris Fitzpatrick. Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace . If you have not yet upgraded to 2.4.0, we recommend going directly to 2.4.1. Also, if you are not currently using the public user interface, you may want to skip this release and wait for our next, larger release, which we expect to come in late July. The fixes in this release will also be included in that one. The deadline to submit community pull requests for consideration for the July 2018 release is July 20. Pull requests submitted after July 20 will be considered for a future release. Annual Member Forum: August 14, 2018, in Washington D.C. Thanks to all who shared presentation ideas, workshop topics, and discussion suggestions. The planning group is reviewing the submissions to ensure that the program covers the diverse spread of topics suggested by our community. We received a number of topic suggestions from the community. Please take a look at the list of suggested topics (http://archivesspace.org/archives/3038) these and let us know via the ideas form if you would like to help lead a session. We appreciate a submission by July 6 so that we can get the program squared away as soon as possible. You will receive a response from the working group by July 13. * Location: ArchivesSpace will be holding its fourth annual Member Forum on August 14, 2018 at the Josephine Butler Parks Center in Washington, DC. Washington Parks & People is the capital?s hub for activating public lands & waters for broad community revitalization, with a mission to grow city-wide park-based community health & vitality by nurturing innovation & partnerships. We are thrilled to have our annual forum held at this location. * Program: More information on the developing program is on the ArchivesSpace wiki at https://archivesspace.atlassian.net/wiki/display/ADC/ArchivesSpace+Member+Forum+2018. * Registration: Registration for the Member Forum will open in early July. * Reception: This year we?re excited to join forces with our friends at Archive-It to co-host a reception that will bring our partner communities together. Join us at the Conservation Pavilion at the National Zoo from 5-7 PM for drinks, hors d?oeuvres, and good times! More information is available here: http://archivesspace.org/archives/3025 Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. If you have any questions or other suggestions at this point, please feel free to email Kim at christine.kim at lyrasis.org. Webinars Past: Transforming XLS to EAD: Importing Component Hierarchies Thanks to all who joined us for the Transforming XLS to EAD: Importing Component Hierarchies webinar on June 27. Special thanks to our presenters Elizabeth Perkes (Utah State Archives), Jason Ronallo (North Carolina State University), Ben Johnson (Harvard Business School), and Kelly Spring (East Carolina University). Resources from the webinar are now available: http://archivesspace.org/archives/3045 Upcoming: Webinar: Reports Refactored, July 31, 1-1:30pm ET (10-10:30am PT) Please save the date for our next upcoming webinar. Sarah Morrissey, our Georgia Tech co-op student, has taken on the task of refactoring and improving reports in ArchivesSpace. Sarah took the lead on this project under the supervision of and in collaboration with Tech Lead Laney McGlohon, as well as the recommendations contributed by the Reports sub-team. Formal announcement, including webinar viewing link, to follow. If you have any questions, please contact Kim at christine.kim at lyrasis.org. We look forward to seeing you at the webinar! Open Members Call on Zoom, July 26, 2-3pm ET (11-noon PT) Please save the date for our next informal open call, coming up on July 26 at 2-3pm ET (11-noon PT). Open calls provide an opportunity to hear updates from each other and encourage group discussion. It?s a space to surface news, ideas, and challenges. You will be able to join by either computer or phone. An announcement with call in details will be sent out shortly, along with a pre-survey to generate discussion topics. Please email Kim at christine.kim at lyrasis.org if you have any questions. We look forward to ?seeing? you there! Regional Forum Updates ArchivesSpace regional forums are opportunities for our diverse ArchivesSpace members to meet up more locally to share and learn from each other through program content shaped by the community. Past: SoCal Regional Forum: June 28, 2018 at University of California, Irvine Thanks to all who attended and made the SoCal Regional Forum such a lively event! * Notes & presentation slides: Links to the notes and presentation slides are up on the wiki: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/533168147/SoCal+Regional+Forum * Sharing notes & photos: Do you have notes or photos to share? Please feel free to add them to this google drive folder: https://goo.gl/eunPRr A very special thank you to UCI Libraries for generously sponsoring this forum! Please watch for announcements of future regional forums starting in the fall. If you have any questions or ideas about regional forums, feel free to email Kim at christine.kim at lyrasis.org. New Stories on the Blog In All About Community (http://archivesspace.org/category/all-about-community/), Margaret Hughes (Collections Data Archivist, UCLA) introduces the Awesome ArchivesSpace, an awesome list compiled by the Awesome ArchivesSpace Working Group. This is a continuation of a series looking into the various sub-teams of the Technical Advisory Council and User Advisory Council to provide insight into the variety of activities and initiatives undertaken by these groups. We would love to include your ArchivesSpace stories on the blog! If you would like to contribute, please email Kim at christine.kim at lyrasis.org. Governance Updates We?re pleased to welcome new members to our three governance groups for terms that begin July 1. Governance Board * Cynthia Ghering, Director, University Archives, Michigan State University (Very Large member representative) * Kat Stefko, Associate Librarian for Discovery, Digitization and Special Collections and Director of the George J. Mitchell Department of Special Collections & Archives, Bowdoin College (Small member representative) User Advisory Council * Kevin Clair, University of Denver * Angela White, Indiana University ? Purdue University Indianapolis * William Modrow, Miami University of Ohio * Kate Blalack, Woody Guthrie Center * Terra Gullings, University of Texas at Tyler * Julia Novakovic, The Strong * Adrienne Harling, San Francisco Symphony * Joshua Shaw, Dartmouth College Technical Advisory Council * Greg Wiedeman, University of Albany * Bria Parker, University of Maryland * Alicia Detelich, Yale University * Jared Campbell, University of California, Davis * Edgar Garcia, Northwestern University * Dave Mayo, Harvard University Best wishes to all as we welcome our representatives to their new roles and look ahead to the coming year. More information about ArchivesSpace governance is on our website at http://archivesspace.org/governance-board-and-councils. Membership Update We are excited to welcome our newest members to our community! Our new members since May 31 include: * Federal Bank of Boston (Boston, MA) * National Archives at Riverside (Riverside, CA) * University of Notre Dame (Notre Dame, IN) As of June 29, we have 364 General members, 19 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. Renewals Update Membership renewals for the 2018-2019 membership term have been prepared this month and all current members should have received an invoice for next year. Invoices were sent to the billing contact we have on file, with a copy to Member Representatives as well. 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. If you have any questions about your membership, please let us know at ArchivesSpaceHome at lyrasis.org. ________________________________ ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA?s Collection Management Tools Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 20006 bytes Desc: image003.jpg URL: