From laney.mcglohon at lyrasis.org Thu Jun 1 09:36:58 2017 From: laney.mcglohon at lyrasis.org (Laney McGlohon) Date: Thu, 1 Jun 2017 13:36:58 +0000 Subject: [Archivesspace_Users_Group] Inaugural ArchivesSpace Core Committers Group Message-ID: The ArchivesSpace Program Team is pleased to announce the inaugural ArchivesSpace Core Committers Group. Code goes into the ArchivesSpace application from a variety of sources, and the core committers will be responsible for helping people with the process of contributing code to ArchivesSpace Github, reviewing and committing individual code contributions, and ensuring code contributions are properly licensed and follow best-practice guidelines. The core committers will also stay active in the community by welcoming new contributors and helping them get involved, monitoring and responding to issues on the ArchivesSpace mailing lists, and monitoring and analyzing relevant tickets on ArchivesSpace JIRA. We thank the following individuals who have agreed to take on this important charge as part of this group: * Dave Mayo ? Harvard University * Esha Datta ? New York University * Lora B Davis ? Johns Hopkins University * Mark Cooper ? LYRASIS * Steve Majewski ? University of Virginia * Laney McGlohon ? ArchivesSpace Technical Lead Next steps for the group are: 1. Decide on communication pathways 2. Decide on dates, times, and frequency of the core committer?s calls. 3. Get contributor licensing agreements filled out and signed 4. Review the Core Contributors? Guidelines Please feel free to contact me if you have any questions about contributing code to the ArchivesSpace application or you would like to get involved. Best, Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 800.999.8558 x2927 laneymcglohon Skype [cid:image001.jpg at 01D2DABA.9CE3E940] Save the Date for the 2017 ArchivesSpace Member Forum: July 25 Save the Date for the 2017 LYRASIS Member Summit: October 11-12 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6689 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Thu Jun 1 13:33:14 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 1 Jun 2017 17:33:14 +0000 Subject: [Archivesspace_Users_Group] registration now open for ArchivesSpace Member Forum 2017 Message-ID: Hello ArchivesSpace Members, The planning group for the 2017 ArchivesSpace Member Forum is pleased to announce that online registration is now open. The Forum will be held on Tuesday, July 25, at the Smith Memorial Student Union on the campus of Portland State University from 9:00 a.m. to 5:30 p.m. The Member Forum is a chance for all interested staff of ArchivesSpace member institutions to share and learn about experiences implementing, using, and developing for ArchivesSpace. The preliminary schedule is available on our wiki, with more details to come. This is a free event. You may attend the full day, or just part. We kindly request that all who plan to be there complete the online registration in order for us to plan appropriately. Due to limited space and the need to prepare materials for the two afternoon workshops, you must preregister if you'd like to attend one of these. Ways you can participate: * Register to attend the Member Forum at https://www.eventbrite.com/e/archivesspace-member-forum-2017-registration-34624388478 * Volunteer to speak in the concluding lightning round on ArchivesSpace Tips, Tricks and Ideas or share your insights in the ArchivesSpace Community/Ask an Expert session (just email me to volunteer) * Suggest topics you'd like addressed in the Program update by emailing me, starting a discussion on the Users Group listserv, or commenting on the wiki page. We look forward to seeing many of you there in person! We also hope to livestream (and/or record) a portion of the program for those who can't be in Portland, and will have more information about that available at a later date. Christine On behalf of the planning group for the ArchivesSpace Member Forum 2017 Lisa Calahan, University of Minnesota Johanna Carll, Harvard University Celia Caust-Ellenbogen, Swarthmore College Maggie Hughes, UCLA Sue Luftschein, University of Southern California Jaime Margalotti, University of Delaware Jenny Mitchell, Louisiana State University Elizabeth Russell, University of Maine Linda Sellars, North Carolina State University Mariella Soprano, Caltech Kelly Spring, UC Irvine 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: 4144 bytes Desc: image002.jpg URL: From eckardm at umich.edu Fri Jun 2 16:59:54 2017 From: eckardm at umich.edu (Max Eckard) Date: Fri, 2 Jun 2017 16:59:54 -0400 Subject: [Archivesspace_Users_Group] ASpace and bepress In-Reply-To: References: Message-ID: Hi Johna, This thread from September of last year may be useful or at least give you a potential point of contact: http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2016-September/004053.html What you want to do can probably be done via the ArchivesSpace API, and I think a number of people have done some similar metadata export/ArchivesSpace updating tasks in this way. We have a similar use case--not between ArchivesSpace and Digital Commons, but ArchivesSpace and DSpace, a system that does some of the same things. We get the collection-level information from ArchivesSpace Resources to DSpace Collections with a little command line program we wrote: https://github.com/bentley-historical-library/resource-to-collection. Basically, you point it at an ArchivesSpace Resource and it makes use of the ArchivesSpace API and the DSpace API to take data from the former and add it to the latter. It's definitely a homegrown thing for the very particular way we do things here, but it sounds similar to what you need to do and you could certainly make use of any or all of it. For getting the information about individual ArchivesSpace Digital Objects to DSpace, this essentially happens for us as part of an integration between ArchivesSpace, Archivematica and DSpace, where scripts in Archivematica handle getting information from ArchivesSpace Archival Objects to ArchivesSpace Digital Objects and DSpace Items, and then URLs from those DSpace Items back to ArchivesSpace. There's little bits and pieces that seem relevant to your use case: - agentarchives, which interacts with the ArchivesSpace API (with various functions around getting info from resources and components in ArchivesSpace or posting to or updating those things in ArchivesSpace): https://github.com/artefactual-labs/agentarchives - DSpace URLs (handles) back to ArchivesSpace, which I'm not sure you'd be able to do *without* using the API: https://github.com/artefactual/archivematica/blob/stable/1.6.x-bentley/src/MCPClient/lib/clientScripts/post_store_aip_hook.py#L47-L84 Again, different system, but similar principles and similar interaction with ArchivesSpace via the API. It looks like bepress is thinking about building out an API , which you could look into as well--maybe that could help? Hope any of that helps! Thanks, Max On Wed, May 31, 2017 at 1:53 PM, Johna Von Behrens < johnavonbehrens at gmail.com> wrote: > I am looking for some information or advice on using AS and Digital > Commons (DC) together. > > In AS there would be the regular finding aids and digital objects created. > Create and run a report that would provide all the needed info to crosswalk > the collection level info and digital materials to DC. Then possibly run a > report in DC to get the URLs to throw back into the digital object record > in AS. > > Is anyone doing or tried this? > > Thanks > -- > Johna Von Behrens > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- *Max Eckard* *Assistant Archivist for Digital Curation* Bentley Historical Library 1150 Beal Ave. Ann Arbor, MI 48109-2113 (734) 763-7518 http://bentley.umich.edu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Jun 6 09:20:16 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 6 Jun 2017 13:20:16 +0000 Subject: [Archivesspace_Users_Group] request for comments: specification for ArchivesSpace agents module expansion Message-ID: Hello ArchivesSpace members, I wanted to pass along information on the valuable work being done to write a specification for an expansion of the Agents module in ArchivesSpace. Thanks very much to Cory, Sue, and Brad for their efforts on this very complex undertaking. The details are below and also linked from the JIRA issue: https://archivesspace.atlassian.net/browse/AR-1779. The specification team requests feedback from institutions and individual archivists. Comments can be posted directly to the User's Group listserv and you can also make comments on many of the individual specification documents. We ask as much as possible for initial comments to be submitted by Friday, June 30. There will also be an opportunity to discuss these enhancements in person at the ArchivesSpace Member Forum in Portland in July, with more details to come. Christine Agent Module Expansion Specification In an effort begun over two years ago, an ad-hoc team from the Technical Advisory Committee has been working to develop specifications to expand the ArchivesSpace Agent module to more fully support EAC-CPF and the MARC Authority format, and to assist with integration with the Social Networks and Archival Context (SNAC) Cooperative. This group has included representatives from the ArchivesSpace program team, Brigham Young University, and the University of Southern California. The current draft of the specification is now available for comment and includes these components: * Data Model: https://docs.google.com/spreadsheets/d/1HFBCQ6hnsr92gaSqs2cWSkRRtwySstHQv_B74XnYxKw/edit?usp=sharing * Software Requirements Specification: https://docs.google.com/document/d/1aFz4hzFWYVFo8TLkUpZS97cr1QfRgO4-st_G7wU8z2I/edit?usp=sharing * Wireframes: https://drive.google.com/drive/folders/0B1AAa_XOzd58OGFxVWdzNDM3d0k?usp=sharing * Migration Maps: https://drive.google.com/drive/folders/0B1AAa_XOzd58a3dVNkpYdXVTWlk?usp=sharing The current version of the specification aims to provide augmented functionality in the following areas: * Record input Introduces a range of new elements for the description of archival creators and authority record management. This includes a revised model for dates based on the EAC-CPF standard. * Record ingest Includes expanded functionality for the implementation of EAC-CPF and MARC. Documentation of updated mappings for these ingest routines is provided. * Record merging Expands on existing merging functionality, allowing for element-by-element selection from individual records during merge. * Record export Introduces revised export routines to provide greater compatibility with EAC-CPF and MARC. Documentation of updated mappings is provided. * Record transmission Provides for submission of locally-created Agent records to the SNAC Cooperative using a JSON response. * Record synchronization Introduces functionality to allow institutions to maintain synchronization of local Agent record content with the Library of Congress Name Authority File (LCNAF) and SNAC. The specification team requests feedback from institutions and individual archivists. Member comments can be posted directly to the User's Group listserv (archivesspace_users_group at lyralists.lyrasis.org). You can also make comments on many of the individual specification documents. Sincerely, Specification Team: Sue Luftschein Cory Nimer Bradley Westbrook 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: 4144 bytes Desc: image002.jpg URL: From christine.dibella at lyrasis.org Tue Jun 6 14:36:09 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 6 Jun 2017 18:36:09 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - June 2017 Message-ID: [ASpaceOrgHome.jpg] June 2017 Update Development Together with our development partner Hudson Molonglo, we're hard at work on the 2.1.0 release. This release will include major additions and improvements to functionality, including the production-ready version of the new public user interface, an OAI-PMH responder, and an enhanced rights management module. It will also include various bug fixes, improvements to the backend and performance, and minor report enhancements. We expect to freeze the code in mid-June, and make the new features available for testing very soon afterwards. Once testing is complete to a satisfactory degree, we'll release 2.1.0, a very exciting milestone in ArchivesSpace development. Stay tuned - more information will be available later this month. Updated Technology and Development Roadmap We have shared an updated ArchivesSpace Technology and Development Roadmap on the ArchivesSpace wiki at: https://archivesspace.atlassian.net/wiki/display/ADC/Road+Map The roadmap is a planning and communication tool to help the community know what to expect in terms of future development work and aid in planning for upcoming releases and upgrades. This updated version includes: * tying activities to JIRA tickets * including the requirements portion of the process (we need close-to-finalized requirements before development can be scheduled) * outlining the responsible party as a way to highlight and encourage community involvement * a detailed overview for several releases on the first tab, then separate tabs to highlight features of individual releases The timelines and priorities reflect: * Major feature priorities were based on a combination of the results of the 2016 prioritization member survey, the availability of finalized specifications, and community input including discussion on the Users Group listserv * Refactoring prioritization was based on HM's analysis of the code * Bug fixes and feature enhancements prioritized by the Development Prioritization Subteam We have heard from a number of people who want their institutions to get more involved in developing for ArchivesSpace. We have indicated in the roadmap features for which we are actively seeking developers from the community willing to take responsibility for implementing them in the code. These are noted with "Seeking community developer/s" in the Responsibility column. We believe that these pieces are small and bounded enough to make them reasonable to implement this way and that they provide an excellent opportunity for those who are interested to improve the ArchivesSpace application for the community overall. Please get in touch with us if you'd like to discuss this kind of involvement with development, or if you'd like to share feedback, at ArchivesSpaceHome at lyrasis.org. Announcing the Inaugural Core Committers Group The ArchivesSpace Program Team is pleased to announce the inaugural ArchivesSpace Core Committers Group. Code goes into the ArchivesSpace application from a variety of sources, and the core committers will be responsible for helping people with the process of contributing code to ArchivesSpace Github, reviewing and committing individual code contributions, and ensuring code contributions are properly licensed and follow best-practice guidelines. The core committers will also stay active in the community by welcoming new contributors and helping them get involved, monitoring and responding to issues on the ArchivesSpace mailing lists, and monitoring and analyzing relevant tickets on ArchivesSpace JIRA. We thank the following individuals who have agreed to take on this important charge as part of this group: * Dave Mayo - Harvard University * Esha Datta - New York University * Lora Davis - Johns Hopkins University * Mark Cooper - LYRASIS * Steve Majewski - University of Virginia * Laney McGlohon - ArchivesSpace Technical Lead If you'd like more information about the Core Committers, or if you'd like to get involved in contributing code to ArchivesSpace, please contact Laney at laney.mcglohon at lyrasis.org. Request for Comments: Agents Module Expansion Specification On behalf of the Specification Team: Sue Luftschein, Cory Nimer, and Bradley Westbrook In an effort begun over two years ago, an ad-hoc team from the Technical Advisory Council has been working to develop specifications to expand the ArchivesSpace Agent module to more fully support EAC-CPF and the MARC Authority format, and to assist with integration with the Social Networks and Archival Context (SNAC) Cooperative. This group has included representatives from the ArchivesSpace program team, Brigham Young University, and the University of Southern California. The current draft of the specification is now available for comment and includes these components: * Data Model: https://docs.google.com/spreadsheets/d/1HFBCQ6hnsr92gaSqs2cWSkRRtwySstHQv_B74XnYxKw/edit?usp=sharing * Software Requirements Specification: https://docs.google.com/document/d/1aFz4hzFWYVFo8TLkUpZS97cr1QfRgO4-st_G7wU8z2I/edit?usp=sharing * Wireframes: https://drive.google.com/drive/folders/0B1AAa_XOzd58OGFxVWdzNDM3d0k?usp=sharing * Migration Maps: https://drive.google.com/drive/folders/0B1AAa_XOzd58a3dVNkpYdXVTWlk?usp=sharing The current version of the specification aims to provide augmented functionality in the following areas: * Record input Introduces a range of new elements for the description of archival creators and authority record management. This includes a revised model for dates based on the EAC-CPF standard. * Record ingest Includes expanded functionality for the implementation of EAC-CPF and MARC. Documentation of updated mappings for these ingest routines is provided. * Record merging Expands on existing merging functionality, allowing for element-by-element selection from individual records during merge. * Record export Introduces revised export routines to provide greater compatibility with EAC-CPF and MARC. Documentation of updated mappings is provided. * Record transmission Provides for submission of locally-created Agent records to the SNAC Cooperative using a JSON response. * Record synchronization Introduces functionality to allow institutions to maintain synchronization of local Agent record content with the Library of Congress Name Authority File (LCNAF) and SNAC. The specification team requests feedback from institutions and individual archivists. Member comments can be posted directly to the User's Group listserv (archivesspace_users_group at lyralists.lyrasis.org). You can also make comments on many of the individual specification documents. Please get in touch at ArchivesSpaceHome at lyrasis.org if you have further questions or comments. ArchivesSpace Integrations On behalf of the Integrations sub-team of the Technical Advisory Council The Integrations sub-team of the ArchivesSpace Technical Advisory Council is pleased to announce a number of new resources designed to make it easier for community members to undertake a project to integrate ArchivesSpace with another system. * A new Integrations with ArchivesSpace page on the main ArchivesSpace site. We hope this helps to draw even more attention to the excellent work being done by community members that are already integrating ArchivesSpace with various other systems including: Archivematica, CollectionSpace, Drupal, DSpace, Jekyll and Preservica. * Two new resources: Why to Integrate with ArchivesSpace and How to Integrate with ArchivesSpace. The former details why you might want to couple ArchivesSpace together with various disparate systems to create efficient archival workflows, as well as various in-progress and planned integration scenarios. The latter details how you might go about integrating with ArchivesSpace and the various ways in which the architecture of ArchivesSpace is integration-friendly. Neither resource is exhaustive; if you have other ideas, please let us know! The Integrations sub-team will also be highlighting these resources at a session entitled "Integrations with Other Applications" at the ArchivesSpace Member Forum later this summer. We hope to see you there! As always, we're eager to hear about the work you're doing. Please get in touch with us by filling out the ArchivesSpace Integration Information form so we can help spread the word. Member Forum Registration Now Open The 2017 ArchivesSpace Member Forum will be held on Tuesday, July 25, at the Smith Memorial Student Union on the campus of Portland State University from 9:00 a.m. to 5:30 p.m. The Member Forum is a chance for all interested staff of ArchivesSpace member institutions to share and learn about experiences implementing, using, and developing for ArchivesSpace. The preliminary schedule is available on our wiki, with more details to come. Online registration for this free event is now open at https://www.eventbrite.com/e/archivesspace-member-forum-2017-registration-34624388478. You may attend the full day, or just part. We look forward to seeing many ArchivesSpace members there. Membership Update Our new members since May 10 include: * Rochester Institute of Technology * Wesleyan University Queens College Graduate School of Library and Information Studies and the Department of Library & Information Science at Catholic University of America are our new Educational Program members. As of June 6, we have 333 General members, 14 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. Membership renewals for the 2017-2018 membership term are being prepared this month and all current members who have not already requested an advance renewal will receive an invoice for next year. Invoices will be sent to the billing contact we have on file, with a copy to Member Representatives as well. 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 roundtable listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 11964 bytes Desc: image003.jpg URL: From CurbowJ at bvu.edu Fri Jun 9 15:52:05 2017 From: CurbowJ at bvu.edu (Joan Curbow) Date: Fri, 9 Jun 2017 19:52:05 +0000 Subject: [Archivesspace_Users_Group] Testing Message-ID: I haven?t had any emails in this listserv all week. Is something wrong on my end? 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 www.library.bvu.edu?? -------------- next part -------------- An HTML attachment was scrubbed... URL: From sspires at atlas-sys.com Mon Jun 12 10:33:31 2017 From: sspires at atlas-sys.com (Stephanie Spires) Date: Mon, 12 Jun 2017 14:33:31 +0000 Subject: [Archivesspace_Users_Group] FREE Class: Introduction to ArchivesSpace (hands-on, online) Message-ID: FREE Class: Introduction to ArchivesSpace (hands-on,online) Have you been thinking about using ArchivesSpace? Are you wondering about how your institution's finding aids and archival data would look in ArchivesSpace? During the formal hands-on workshop hours, which will be July 11-13, 1:30 PM-3:30 PM Eastern time, you will learn how to create accession and resource (finding aid) records in ArchivesSpace. Outside of the formal online workshop hours, attendees will be able to practice on an ArchivesSpace server at any time, beginning at the start of the workshop on Tuesday, July 11th through 5PM Eastern Time on Friday, July 14th. There will be some examples to practice with during the workshop, but you can also practice with your own finding aids. As an added bonus, attendees will also receive a free month of access to the Atlas Systems Video Training Library of ArchivesSpace videos. This course is limited to 20 participants. Atlas Systems, Inc. is an ArchivesSpace Registered Service Provider. Registration: Email Anne Marie Lyons at amlyons at atlas-sys.com by Wednesday, July 5th, to register for the course. Thank you, Stephanie _________________________________________________________ Stephanie Spires Chief Service Officer Atlas Systems - Library excellence through efficiency phone: 757-467-7872 x223 fax: 757-467-7875 sspires at atlas-sys.com http://www.atlas-sys.com/ Now Get Social with Atlas Support and Development! Big changes are happening as Atlas rolls out a new web based service platform to replace our previous service system. With the new system you can submit and track service requests, dialog with other members of the community, and provide your input on product enhancements. It's simple and easy at our new support portal https://support.atlas-sys.com. And while you are there make sure to check out our quick video summary of the new features! Notice: This e-mail message, including any attachments, is intended only for the named recipient(s) above and may contain confidential information. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message from your computer without making any copies or distributing it to any other person. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cspeterson at email.gwu.edu Tue Jun 13 12:06:54 2017 From: cspeterson at email.gwu.edu (Peterson, Christie) Date: Tue, 13 Jun 2017 12:06:54 -0400 Subject: [Archivesspace_Users_Group] Question about behavior of 1.5 conversion Message-ID: Hello, We're working our way bravely through errors being output by the 1.5 conversion process, and we've come to one that I'm hoping someone can shed some light on. In our latest attempt, we've gotten a bunch of Indicator_1 mismatch errors related to Accessions. However, I'm not at all clear what the converter is attempting to do with Accessions, so I'm not sure what the error is. For example, I'm looking at an error that refers to an accession with only one container instance. It's linked to a Related Resource, though. Is something happening there? What? For reference, here is the full line from the error log: error message url uri parent resource instances instance_ids preconversion_locations postconversion_locations conversion_context JSONModel::ValidationException indicator_1 -- Mismatch when mapping between indicator and indicator_1 http://localhost:8080/resolve/ readonly?uri=/repositories/2/accessions/183 /repositories/2/accessions/183 {"lock_version"=>0, "created_by"=>"admin", "last_modified_by"=>"admin", "create_time"=>"2016-07-05T15:14:01Z", "system_mtime"=>"2016-07-05T15:14:01Z", "user_mtime"=>"2016-07-05T15:14:01Z", "instance_type"=>"accession", "jsonmodel_type"=>"instance", "is_representative"=>false, "container"=>{"lock_version"=>0, "indicator_1"=>"2007.009", "barcode_1"=>"1", "created_by"=>"admin", "last_modified_by"=>"admin", "create_time"=>"2016-07-05T15:14:01Z", "system_mtime"=>"2016-07-05T15:14:01Z", "user_mtime"=>"2016-07-05T15:14:01Z", "type_1"=>"item", "jsonmodel_type"=>"container", "container_locations"=>[{"status"=>"current", "start_date"=>"2016-07-05", "system_mtime"=>2016-07-05 15:14:01 UTC, "user_mtime"=>2016-07-05 15:14:01 UTC, "ref"=>"/locations/1989"}], "type_id"=>1346}} 3 {:top_container=>#1, :repo_id=>2, :lock_version=>1, :json_schema_version=>1, :barcode=>"1", :ils_holding_id=>nil, :ils_item_id=>nil, :exported_to_ils=>nil, :indicator=>"2007.007", :created_by=>"admin", :last_modified_by=>"admin", :create_time=>2017-06-12 13:57:33 UTC, :system_mtime=>2017-06-12 13:57:33 UTC, :user_mtime=>2017-06-12 13:57:33 UTC, :type_id=>1346}>, :aspace_container=>{"lock_version"=>0, "indicator_1"=>"2007.009", "barcode_1"=>"1", "created_by"=>"admin", "last_modified_by"=>"admin", "create_time"=>"2016-07-05T15:14:01Z", "system_mtime"=>"2016-07-05T15:14:01Z", "user_mtime"=>"2016-07-05T15:14:01Z", "type_1"=>"item", "jsonmodel_type"=>"container", "container_locations"=>[{"status"=>"current", "start_date"=>"2016-07-05", "system_mtime"=>2016-07-05 15:14:01 UTC, "user_mtime"=>2016-07-05 15:14:01 UTC, "ref"=>"/locations/1989"}], "type_id"=>1346}} Thanks in advance, Christie -- Christie S. Peterson University Archivist George Washington University Libraries 704H Gelman Library cspeterson at gwu.edu 202.994.3925 <(202)%20994-3925> -------------- next part -------------- An HTML attachment was scrubbed... URL: From cspeterson at email.gwu.edu Tue Jun 13 12:45:17 2017 From: cspeterson at email.gwu.edu (Peterson, Christie) Date: Tue, 13 Jun 2017 12:45:17 -0400 Subject: [Archivesspace_Users_Group] Question about behavior of 1.5 conversion In-Reply-To: References: Message-ID: A further clue or possibly muddling: neither of the instances identified in the final column output (indicator_1 = 2007.007 or 2007.009) have any barcode assigned in ASpace, despite the "barcode_1"=>"1" part in the error report On Tue, Jun 13, 2017 at 12:06 PM, Peterson, Christie < cspeterson at email.gwu.edu> wrote: > Hello, > > We're working our way bravely through errors being output by the 1.5 > conversion process, and we've come to one that I'm hoping someone can shed > some light on. > > In our latest attempt, we've gotten a bunch of Indicator_1 mismatch errors > related to Accessions. However, I'm not at all clear what the converter is > attempting to do with Accessions, so I'm not sure what the error is. > > For example, I'm looking at an error that refers to an accession with only > one container instance. It's linked to a Related Resource, though. Is > something happening there? What? > > For reference, here is the full line from the error log: > > error message url uri parent resource instances instance_ids > preconversion_locations postconversion_locations conversion_context > JSONModel::ValidationException indicator_1 -- Mismatch when mapping > between indicator and indicator_1 http://localhost:8080/resolve/ > readonly?uri=/repositories/2/accessions/183 /repositories/2/accessions/183 {"lock_version"=>0, > "created_by"=>"admin", "last_modified_by"=>"admin", > "create_time"=>"2016-07-05T15:14:01Z", "system_mtime"=>"2016-07-05T15:14:01Z", > "user_mtime"=>"2016-07-05T15:14:01Z", "instance_type"=>"accession", > "jsonmodel_type"=>"instance", "is_representative"=>false, > "container"=>{"lock_version"=>0, "indicator_1"=>"2007.009", > "barcode_1"=>"1", "created_by"=>"admin", "last_modified_by"=>"admin", > "create_time"=>"2016-07-05T15:14:01Z", "system_mtime"=>"2016-07-05T15:14:01Z", > "user_mtime"=>"2016-07-05T15:14:01Z", "type_1"=>"item", > "jsonmodel_type"=>"container", "container_locations"=>[{"status"=>"current", > "start_date"=>"2016-07-05", "system_mtime"=>2016-07-05 15:14:01 UTC, > "user_mtime"=>2016-07-05 15:14:01 UTC, "ref"=>"/locations/1989"}], > "type_id"=>1346}} 3 {:top_container=>#1, > :repo_id=>2, :lock_version=>1, :json_schema_version=>1, :barcode=>"1", > :ils_holding_id=>nil, :ils_item_id=>nil, :exported_to_ils=>nil, > :indicator=>"2007.007", :created_by=>"admin", :last_modified_by=>"admin", > :create_time=>2017-06-12 13:57:33 UTC, :system_mtime=>2017-06-12 13:57:33 > UTC, :user_mtime=>2017-06-12 13:57:33 UTC, :type_id=>1346}>, > :aspace_container=>{"lock_version"=>0, "indicator_1"=>"2007.009", > "barcode_1"=>"1", "created_by"=>"admin", "last_modified_by"=>"admin", > "create_time"=>"2016-07-05T15:14:01Z", "system_mtime"=>"2016-07-05T15:14:01Z", > "user_mtime"=>"2016-07-05T15:14:01Z", "type_1"=>"item", > "jsonmodel_type"=>"container", "container_locations"=>[{"status"=>"current", > "start_date"=>"2016-07-05", "system_mtime"=>2016-07-05 15:14:01 UTC, > "user_mtime"=>2016-07-05 15:14:01 UTC, "ref"=>"/locations/1989"}], > "type_id"=>1346}} > > Thanks in advance, > > Christie > > -- > Christie S. Peterson > > University Archivist > George Washington University Libraries > 704H Gelman Library > cspeterson at gwu.edu > 202.994.3925 <(202)%20994-3925> > -- Christie S. Peterson University Archivist George Washington University Libraries 704H Gelman Library cspeterson at gwu.edu 202.994.3925 -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Jun 14 10:10:30 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 14 Jun 2017 14:10:30 +0000 Subject: [Archivesspace_Users_Group] call for participants in ArchivesSpace staff interface enhancement working group Message-ID: Hello ArchivesSpace Members, With the new version of the public user interface nearly complete, we are pleased to announce a member-led project to enhance, streamline, and make the staff interface of the ArchivesSpace software application more accessible. As part of this effort, we are calling for member volunteers to participate in a working group to examine the current staff interface and identify improvements. A fuller description of what we are asking this working group to take on is included below. The Staff Interface Enhancement Working Group will: * Review, in order to de-dupe and enhance where necessary, outstanding JIRA issues submitted by the community over the years regarding the staff interface. * Identify areas of interest not covered by existing JIRA issues. * Identify accessibility gaps in the current staff interface. * Based on the group's research and member feedback, develop organized recommendations for staff interface improvements. * Once finalized, work with the ArchivesSpace Program team and others to use the recommendations as the basis for a comprehensive specification for the look and feel of the next version of the staff interface. Lydia Tang of Michigan State University has graciously agreed to chair the working group. If you are interested in participating as a member of the group, please let me know through a direct reply to this message, by Friday, June 30. We are looking for broad participation across the different sizes and types of organizations that use ArchivesSpace. In addition to the working group itself, there will be calls for feedback and participation at regular intervals. The first of these will be an in person focus group held in conjunction with the ArchivesSpace Member Forum in Portland on July 25. This will by no means be the last opportunity to give feedback, but we anticipate that it will help us get things off to a great start. Let us know if you have any questions or would like to participate. I look forward to working with Lydia and all of you on this important endeavor! Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: From cmaurice at tulane.edu Thu Jun 15 12:07:50 2017 From: cmaurice at tulane.edu (Maurice, Candace A) Date: Thu, 15 Jun 2017 16:07:50 +0000 Subject: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 Message-ID: Hello All, We are on version 1.4.2 and we have had a user report that the subject heading plugin is not returning results for either LCNAF or LCSH (OCLC works, however). The user doesn?t receive any error messages when using the plugin, but tried typing in known subject headings for the Library Of Congress and it?s still not returning results. I checked the Background jobs and logs and there are not error messages. I also went to the LOC website and all appears to be fine when searching subject headings on their site. Has anyone else experienced a similar issue? Can you point me in the right direction for resolving this issue? Thanks, Candace ------------------------- Candace Maurice Web Developer Howard-Tiltion Memorial Library Tulane University 504.314.7784 cmaurice at tulane.edu [Description: Description: cid:image001.jpg at 01C9F346.FB284370] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 512DA1AA-B52D-4559-9B7E-FB77BCC5BB86.png Type: image/png Size: 4171 bytes Desc: 512DA1AA-B52D-4559-9B7E-FB77BCC5BB86.png URL: From gpgaidmore at wm.edu Thu Jun 15 12:55:10 2017 From: gpgaidmore at wm.edu (Gaidmore, Gerald) Date: Thu, 15 Jun 2017 16:55:10 +0000 Subject: [Archivesspace_Users_Group] 2017 ArchivesSpace Governance Board Election - candidate statements Message-ID: The 2017 ArchivesSpace Nominating Committee is pleased to present the following slate of candidates for election to fill vacancies on the ArchivesSpace Governance Board: Very Small Member Representative * Thomas Adams, Manager, Library Systems & Digital Project Developer, Cold Spring Harbor Laboratory * Nicholas Zmijewski, Archivist, Industrial Archives & Library Medium Member Representative * Peter Carini, College Archivist, Dartmouth College * Ann Hodges, Head of Special Collections and Archives, Texas A&M University-Corpus Christi Large Member Representative * Gordon Daines, Supervisor of Reference Services and Department Chair, L. Tom Perry Special Collections, Brigham Young University * Christian Dupont, Burns Librarian and Associate University Librarian for Special Collections, Boston College Statements for each candidate are included in the attached PDF. The official voting members for Large, Medium, and Very Small member institutions will receive a separate message with a ballot link for their respective slates. Only official voting members may vote, and only in their member categories. If you are unsure about who the voting member is for your institution, please get in touch with Christine Di Bella (christine.dibella at lyrasis.org). Election results will be announced in early July. Elected candidates will serve a two-year term beginning July 1, 2017 concluding June 30, 2019. Respectfully submitted, Jay Gaidmore, College of William and Mary Chair, 2017 Nominating Committee 2017 Nominating Committee members Jay Gaidmore, Chair, College of William and Mary, Governance Board member Gordon Daines, BYU, Chair of User Advisory Council Sally Vermaaten, Gates Archive, Chair of Technical Advisory Council Johna Von Behrens, University of Louisiana Lafayette, representing Very Large membership level Cyndi Shein, UNLV, representing Large membership level Mary Saffell, Texas Christian University, representing Medium membership level Julia Novakovic, The Strong National Museum of Play, representing Small membership level Annie Tummino, SUNY Maritime, representing Very Small membership level Christine Di Bella, ArchivesSpace Program Manager, ex officio -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ASpaceCandidateStatementsPacket2017.pdf Type: application/pdf Size: 276072 bytes Desc: ASpaceCandidateStatementsPacket2017.pdf URL: From sdm7g at eservices.virginia.edu Thu Jun 15 13:26:53 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 15 Jun 2017 17:26:53 +0000 Subject: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 In-Reply-To: References: Message-ID: It appears to be no longer working in any version. I believe loc has changed the API for the service slightly. Need to investigate further. But trying to reverse engineer the parameters from inspecting the difference in the params used in the web page search vs. what?s embedded in LCNAF plugin, I tried this change, which appears to work for me: diff --git a/plugins/lcnaf/frontend/models/opensearcher.rb b/plugins/lcnaf/frontend/models/opensearcher.rb index 9391ab5..37e2813 100644 --- a/plugins/lcnaf/frontend/models/opensearcher.rb +++ b/plugins/lcnaf/frontend/models/opensearcher.rb @@ -14,7 +14,7 @@ class OpenSearcher def initialize(base_url, scheme ) @base_url = base_url - @scheme = scheme + @scheme = "cs:" + scheme end @@ -71,7 +71,7 @@ class OpenSearcher 'start' => start_record) uri.query = URI.encode_www_form(params) - + p uri results = HTTPRequest.new.get(uri) do |response| if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") ( The other OCLC search has always been unreliable ? it?s a test site and not a supported service. ) ? Steve Majewski On Jun 15, 2017, at 12:07 PM, Maurice, Candace A > wrote: Hello All, We are on version 1.4.2 and we have had a user report that the subject heading plugin is not returning results for either LCNAF or LCSH (OCLC works, however). The user doesn?t receive any error messages when using the plugin, but tried typing in known subject headings for the Library Of Congress and it?s still not returning results. I checked the Background jobs and logs and there are not error messages. I also went to the LOC website and all appears to be fine when searching subject headings on their site. Has anyone else experienced a similar issue? Can you point me in the right direction for resolving this issue? Thanks, Candace ------------------------- Candace Maurice Web Developer Howard-Tiltion Memorial Library Tulane University 504.314.7784 cmaurice at tulane.edu <512DA1AA-B52D-4559-9B7E-FB77BCC5BB86.png> _______________________________________________ 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 sdm7g at eservices.virginia.edu Thu Jun 15 15:35:42 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Thu, 15 Jun 2017 19:35:42 +0000 Subject: [Archivesspace_Users_Group] invalid EAD exported Message-ID: FYI: I?ve been finding a number of cases of ArchivesSpace ( 2.x ) producing invalid EAD on export. In these cases, and element with a but no other content is produced. In a couple of cases, the cause was that a note was marked as published, but someone missed clicking publish on the sub note with the text. In another case, the ArchivesSpace resource was created by importing EAD which had nested elements: Bibliography Print Sources ? Electronic Sources ? On import, ArchivesSpace created 3 separate bibliographic notes, one of them empty. On export, this serialized as 3 un-nested elements, one of them empty, which cause the validation error. It might be simple to make the exporter skip serializing content-less notes, however that would make the first case of inadvertently not publishing all of the sub notes harder to notice. And not sure if you can always safely assume that published notes should imply publish all sub-notes. Can you think of any counter instances ? Another possible way to handle this might be to incorporate validation as a last step in export, and if there are errors, display them on the redirected download page. Then you will know upfront to review your resource again and where to look for issues. ? Steve Majewski From cmaurice at tulane.edu Thu Jun 15 17:02:55 2017 From: cmaurice at tulane.edu (Maurice, Candace A) Date: Thu, 15 Jun 2017 21:02:55 +0000 Subject: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 In-Reply-To: References: Message-ID: Thanks for the fast response, Steve! I?ll try your fix to see if it works for us as well. Thanks! From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Thursday, June 15, 2017 at 12:26 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 It appears to be no longer working in any version. I believe loc has changed the API for the service slightly. Need to investigate further. But trying to reverse engineer the parameters from inspecting the difference in the params used in the web page search vs. what?s embedded in LCNAF plugin, I tried this change, which appears to work for me: diff --git a/plugins/lcnaf/frontend/models/opensearcher.rb b/plugins/lcnaf/frontend/models/opensearcher.rb index 9391ab5..37e2813 100644 --- a/plugins/lcnaf/frontend/models/opensearcher.rb +++ b/plugins/lcnaf/frontend/models/opensearcher.rb @@ -14,7 +14,7 @@ class OpenSearcher def initialize(base_url, scheme ) @base_url = base_url - @scheme = scheme + @scheme = "cs:" + scheme end @@ -71,7 +71,7 @@ class OpenSearcher 'start' => start_record) uri.query = URI.encode_www_form(params) - + p uri results = HTTPRequest.new.get(uri) do |response| if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") ( The other OCLC search has always been unreliable ? it?s a test site and not a supported service. ) ? Steve Majewski On Jun 15, 2017, at 12:07 PM, Maurice, Candace A > wrote: Hello All, We are on version 1.4.2 and we have had a user report that the subject heading plugin is not returning results for either LCNAF or LCSH (OCLC works, however). The user doesn?t receive any error messages when using the plugin, but tried typing in known subject headings for the Library Of Congress and it?s still not returning results. I checked the Background jobs and logs and there are not error messages. I also went to the LOC website and all appears to be fine when searching subject headings on their site. Has anyone else experienced a similar issue? Can you point me in the right direction for resolving this issue? Thanks, Candace ------------------------- Candace Maurice Web Developer Howard-Tiltion Memorial Library Tulane University 504.314.7784 cmaurice at tulane.edu <512DA1AA-B52D-4559-9B7E-FB77BCC5BB86.png> _______________________________________________ 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 cmaurice at tulane.edu Fri Jun 16 14:38:45 2017 From: cmaurice at tulane.edu (Maurice, Candace A) Date: Fri, 16 Jun 2017 18:38:45 +0000 Subject: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 In-Reply-To: References: Message-ID: Hi Steve, I tried to implement the patch, but still no luck. My file on line 71 is different than in the patch you provided (see function below). def search(query, page, records_per_page) uri = URI(@base_url) start_record = calculate_start_record(page, records_per_page) params = default_params.merge('q' => [query.to_s, @scheme], 'count' => records_per_page, 'start' => start_record) uri.query = URI.encode_www_form(params) response = Net::HTTP.get_response(uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end results = OpenSearchResultSet.new(response.body, query) results.entries.each do |entry| marc_uri = URI("#{entry['uri']}.marcxml.xml") response = Net::HTTP.get_response(marc_uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end entry['xml'] = response.body.force_encoding("iso-8859-1").encode('utf-8') end results End -candace From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Thursday, June 15, 2017 at 12:26 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 It appears to be no longer working in any version. I believe loc has changed the API for the service slightly. Need to investigate further. But trying to reverse engineer the parameters from inspecting the difference in the params used in the web page search vs. what?s embedded in LCNAF plugin, I tried this change, which appears to work for me: diff --git a/plugins/lcnaf/frontend/models/opensearcher.rb b/plugins/lcnaf/frontend/models/opensearcher.rb index 9391ab5..37e2813 100644 --- a/plugins/lcnaf/frontend/models/opensearcher.rb +++ b/plugins/lcnaf/frontend/models/opensearcher.rb @@ -14,7 +14,7 @@ class OpenSearcher def initialize(base_url, scheme ) @base_url = base_url - @scheme = scheme + @scheme = "cs:" + scheme end @@ -71,7 +71,7 @@ class OpenSearcher 'start' => start_record) uri.query = URI.encode_www_form(params) - + p uri results = HTTPRequest.new.get(uri) do |response| if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") ( The other OCLC search has always been unreliable ? it?s a test site and not a supported service. ) ? Steve Majewski On Jun 15, 2017, at 12:07 PM, Maurice, Candace A > wrote: Hello All, We are on version 1.4.2 and we have had a user report that the subject heading plugin is not returning results for either LCNAF or LCSH (OCLC works, however). The user doesn?t receive any error messages when using the plugin, but tried typing in known subject headings for the Library Of Congress and it?s still not returning results. I checked the Background jobs and logs and there are not error messages. I also went to the LOC website and all appears to be fine when searching subject headings on their site. Has anyone else experienced a similar issue? Can you point me in the right direction for resolving this issue? Thanks, Candace ------------------------- Candace Maurice Web Developer Howard-Tiltion Memorial Library Tulane University 504.314.7784 cmaurice at tulane.edu <512DA1AA-B52D-4559-9B7E-FB77BCC5BB86.png> _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From k-miller3 at northwestern.edu Fri Jun 16 14:57:04 2017 From: k-miller3 at northwestern.edu (Karen Miller) Date: Fri, 16 Jun 2017 18:57:04 +0000 Subject: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 In-Reply-To: References: Message-ID: <28ee5b17d88142f08614152640c7eee6@evcspmbx05.ads.northwestern.edu> Hi, Candace. I can't help on the plugin operational issue, but I can offer a caveat about using the plugin for LCSH. This plugin has (until very recently) worked well for us at NUL for importing Agent records from LCNAF, but we have never used it to import Subject records. And, as Steve pointed out, the import from OCLC is unreliable. When a Subject is imported using this plug-in, individual Subject records are created for the preferred term (the MARC 150 field in the authority record) as well as for each of the non-preferred terms (the MARC 450 fields in the authority record, i.e., references). For example, an LCSH record with 4 non-preferred terms will be imported as 5 Subject records, one for the preferred term and one for each of the non-preferred terms, with no indication in the records for the non-preferred terms that they are references and should not be assigned, as well as no indication of the preferred term with which they are associated. This is almost certainly not what your archivists or catalogers want. While the import of Name Authority File (LCNAF) records correctly places non-preferred names in the Agent record for the preferred name designated as references, the import of LCSH records operates differently and would wreak havoc on the use of Subject records. I understand that Yale is undertaking a project to update the plug-in and hopes to change the functionality so that only the preferred Subject term is imported, but until then, I can't recommend using it. Best, Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maurice, Candace A Sent: Friday, June 16, 2017 1:39 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 Hi Steve, I tried to implement the patch, but still no luck. My file on line 71 is different than in the patch you provided (see function below). def search(query, page, records_per_page) uri = URI(@base_url) start_record = calculate_start_record(page, records_per_page) params = default_params.merge('q' => [query.to_s, @scheme], 'count' => records_per_page, 'start' => start_record) uri.query = URI.encode_www_form(params) response = Net::HTTP.get_response(uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end results = OpenSearchResultSet.new(response.body, query) results.entries.each do |entry| marc_uri = URI("#{entry['uri']}.marcxml.xml") response = Net::HTTP.get_response(marc_uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end entry['xml'] = response.body.force_encoding("iso-8859-1").encode('utf-8') end results End -candace From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Thursday, June 15, 2017 at 12:26 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 It appears to be no longer working in any version. I believe loc has changed the API for the service slightly. Need to investigate further. But trying to reverse engineer the parameters from inspecting the difference in the params used in the web page search vs. what's embedded in LCNAF plugin, I tried this change, which appears to work for me: diff --git a/plugins/lcnaf/frontend/models/opensearcher.rb b/plugins/lcnaf/frontend/models/opensearcher.rb index 9391ab5..37e2813 100644 --- a/plugins/lcnaf/frontend/models/opensearcher.rb +++ b/plugins/lcnaf/frontend/models/opensearcher.rb @@ -14,7 +14,7 @@ class OpenSearcher def initialize(base_url, scheme ) @base_url = base_url - @scheme = scheme + @scheme = "cs:" + scheme end @@ -71,7 +71,7 @@ class OpenSearcher 'start' => start_record) uri.query = URI.encode_www_form(params) - + p uri results = HTTPRequest.new.get(uri) do |response| if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") ( The other OCLC search has always been unreliable - it's a test site and not a supported service. ) - Steve Majewski On Jun 15, 2017, at 12:07 PM, Maurice, Candace A > wrote: Hello All, We are on version 1.4.2 and we have had a user report that the subject heading plugin is not returning results for either LCNAF or LCSH (OCLC works, however). The user doesn't receive any error messages when using the plugin, but tried typing in known subject headings for the Library Of Congress and it's still not returning results. I checked the Background jobs and logs and there are not error messages. I also went to the LOC website and all appears to be fine when searching subject headings on their site. Has anyone else experienced a similar issue? Can you point me in the right direction for resolving this issue? Thanks, Candace ------------------------- Candace Maurice Web Developer Howard-Tiltion Memorial Library Tulane University 504.314.7784 cmaurice at tulane.edu <512DA1AA-B52D-4559-9B7E-FB77BCC5BB86.png> _______________________________________________ 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 sdm7g at eservices.virginia.edu Fri Jun 16 15:12:30 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 16 Jun 2017 19:12:30 +0000 Subject: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 In-Reply-To: References: Message-ID: My tests and patch were on current master branch, and so it looks like there were further changes to lcnaf between 1.4.2 and 2.0.1 . But the significant changes in my patch were: [1] prefixing the @scheme parameter with (what I assume is) a field specifier: @scheme = ?cs:? + @scheme ( prefix could either be added to @scheme in initialized method, or else added to the search params in search method. ) You can just manually edit that change if the patch doesn?t work. [2] the ?p uri? prints out the final doc.gov URI and query string. This was part of the debugging and reverse engineering: to compare the URI & query in id.loc.gov search page with what LCNAF plugin was using. Since I?m not sure if API changes to id.loc.gov are documented anywhere, I left it there in case of future changes or problems. You can always grab the URL out of the log file and paste it into curl or your browser to see if it?s working as expected. So the line 71 change is not required. ? Steve. On Jun 16, 2017, at 2:38 PM, Maurice, Candace A > wrote: Hi Steve, I tried to implement the patch, but still no luck. My file on line 71 is different than in the patch you provided (see function below). def search(query, page, records_per_page) uri = URI(@base_url) start_record = calculate_start_record(page, records_per_page) params = default_params.merge('q' => [query.to_s, @scheme], 'count' => records_per_page, 'start' => start_record) uri.query = URI.encode_www_form(params) response = Net::HTTP.get_response(uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end results = OpenSearchResultSet.new(response.body, query) results.entries.each do |entry| marc_uri = URI("#{entry['uri']}.marcxml.xml") response = Net::HTTP.get_response(marc_uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end entry['xml'] = response.body.force_encoding("iso-8859-1").encode('utf-8') end results End -candace From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Thursday, June 15, 2017 at 12:26 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 It appears to be no longer working in any version. I believe loc has changed the API for the service slightly. Need to investigate further. But trying to reverse engineer the parameters from inspecting the difference in the params used in the web page search vs. what?s embedded in LCNAF plugin, I tried this change, which appears to work for me: diff --git a/plugins/lcnaf/frontend/models/opensearcher.rb b/plugins/lcnaf/frontend/models/opensearcher.rb index 9391ab5..37e2813 100644 --- a/plugins/lcnaf/frontend/models/opensearcher.rb +++ b/plugins/lcnaf/frontend/models/opensearcher.rb @@ -14,7 +14,7 @@ class OpenSearcher def initialize(base_url, scheme ) @base_url = base_url - @scheme = scheme + @scheme = "cs:" + scheme end @@ -71,7 +71,7 @@ class OpenSearcher 'start' => start_record) uri.query = URI.encode_www_form(params) - + p uri results = HTTPRequest.new.get(uri) do |response| if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") ( The other OCLC search has always been unreliable ? it?s a test site and not a supported service. ) ? Steve Majewski On Jun 15, 2017, at 12:07 PM, Maurice, Candace A > wrote: Hello All, We are on version 1.4.2 and we have had a user report that the subject heading plugin is not returning results for either LCNAF or LCSH (OCLC works, however). The user doesn?t receive any error messages when using the plugin, but tried typing in known subject headings for the Library Of Congress and it?s still not returning results. I checked the Background jobs and logs and there are not error messages. I also went to the LOC website and all appears to be fine when searching subject headings on their site. Has anyone else experienced a similar issue? Can you point me in the right direction for resolving this issue? Thanks, Candace ------------------------- Candace Maurice Web Developer Howard-Tiltion Memorial Library Tulane University 504.314.7784 cmaurice at tulane.edu <512DA1AA-B52D-4559-9B7E-FB77BCC5BB86.png> _______________________________________________ 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 cmaurice at tulane.edu Fri Jun 16 15:50:20 2017 From: cmaurice at tulane.edu (Maurice, Candace A) Date: Fri, 16 Jun 2017 19:50:20 +0000 Subject: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 In-Reply-To: <28ee5b17d88142f08614152640c7eee6@evcspmbx05.ads.northwestern.edu> References: <28ee5b17d88142f08614152640c7eee6@evcspmbx05.ads.northwestern.edu> Message-ID: Thank you for your response Karen. I will discuss this with our archivist. From: > on behalf of Karen Miller > Reply-To: Archivesspace Users Group > Date: Friday, June 16, 2017 at 1:57 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 Hi, Candace. I can?t help on the plugin operational issue, but I can offer a caveat about using the plugin for LCSH. This plugin has (until very recently) worked well for us at NUL for importing Agent records from LCNAF, but we have never used it to import Subject records. And, as Steve pointed out, the import from OCLC is unreliable. When a Subject is imported using this plug-in, individual Subject records are created for the preferred term (the MARC 150 field in the authority record) as well as for each of the non-preferred terms (the MARC 450 fields in the authority record, i.e., references). For example, an LCSH record with 4 non-preferred terms will be imported as 5 Subject records, one for the preferred term and one for each of the non-preferred terms, with no indication in the records for the non-preferred terms that they are references and should not be assigned, as well as no indication of the preferred term with which they are associated. This is almost certainly not what your archivists or catalogers want. While the import of Name Authority File (LCNAF) records correctly places non-preferred names in the Agent record for the preferred name designated as references, the import of LCSH records operates differently and would wreak havoc on the use of Subject records. I understand that Yale is undertaking a project to update the plug-in and hopes to change the functionality so that only the preferred Subject term is imported, but until then, I can?t recommend using it. Best, Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maurice, Candace A Sent: Friday, June 16, 2017 1:39 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 Hi Steve, I tried to implement the patch, but still no luck. My file on line 71 is different than in the patch you provided (see function below). def search(query, page, records_per_page) uri = URI(@base_url) start_record = calculate_start_record(page, records_per_page) params = default_params.merge('q' => [query.to_s, @scheme], 'count' => records_per_page, 'start' => start_record) uri.query = URI.encode_www_form(params) response = Net::HTTP.get_response(uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end results = OpenSearchResultSet.new(response.body, query) results.entries.each do |entry| marc_uri = URI("#{entry['uri']}.marcxml.xml") response = Net::HTTP.get_response(marc_uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end entry['xml'] = response.body.force_encoding("iso-8859-1").encode('utf-8') end results End -candace From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Thursday, June 15, 2017 at 12:26 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 It appears to be no longer working in any version. I believe loc has changed the API for the service slightly. Need to investigate further. But trying to reverse engineer the parameters from inspecting the difference in the params used in the web page search vs. what?s embedded in LCNAF plugin, I tried this change, which appears to work for me: diff --git a/plugins/lcnaf/frontend/models/opensearcher.rb b/plugins/lcnaf/frontend/models/opensearcher.rb index 9391ab5..37e2813 100644 --- a/plugins/lcnaf/frontend/models/opensearcher.rb +++ b/plugins/lcnaf/frontend/models/opensearcher.rb @@ -14,7 +14,7 @@ class OpenSearcher def initialize(base_url, scheme ) @base_url = base_url - @scheme = scheme + @scheme = "cs:" + scheme end @@ -71,7 +71,7 @@ class OpenSearcher 'start' => start_record) uri.query = URI.encode_www_form(params) - + p uri results = HTTPRequest.new.get(uri) do |response| if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") ( The other OCLC search has always been unreliable ? it?s a test site and not a supported service. ) ? Steve Majewski On Jun 15, 2017, at 12:07 PM, Maurice, Candace A > wrote: Hello All, We are on version 1.4.2 and we have had a user report that the subject heading plugin is not returning results for either LCNAF or LCSH (OCLC works, however). The user doesn?t receive any error messages when using the plugin, but tried typing in known subject headings for the Library Of Congress and it?s still not returning results. I checked the Background jobs and logs and there are not error messages. I also went to the LOC website and all appears to be fine when searching subject headings on their site. Has anyone else experienced a similar issue? Can you point me in the right direction for resolving this issue? Thanks, Candace ------------------------- Candace Maurice Web Developer Howard-Tiltion Memorial Library Tulane University 504.314.7784 cmaurice at tulane.edu <512DA1AA-B52D-4559-9B7E-FB77BCC5BB86.png> _______________________________________________ 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 sdm7g at eservices.virginia.edu Fri Jun 16 16:03:12 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 16 Jun 2017 20:03:12 +0000 Subject: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 In-Reply-To: References: Message-ID: Although those changes seem to fix the search, when I actually try importing either subject or agent records, I get an internal server error. This need more investigation. On Jun 16, 2017, at 3:12 PM, Majewski, Steven Dennis (sdm7g) > wrote: My tests and patch were on current master branch, and so it looks like there were further changes to lcnaf between 1.4.2 and 2.0.1 . But the significant changes in my patch were: [1] prefixing the @scheme parameter with (what I assume is) a field specifier: @scheme = ?cs:? + @scheme ( prefix could either be added to @scheme in initialized method, or else added to the search params in search method. ) You can just manually edit that change if the patch doesn?t work. [2] the ?p uri? prints out the final doc.gov URI and query string. This was part of the debugging and reverse engineering: to compare the URI & query in id.loc.gov search page with what LCNAF plugin was using. Since I?m not sure if API changes to id.loc.gov are documented anywhere, I left it there in case of future changes or problems. You can always grab the URL out of the log file and paste it into curl or your browser to see if it?s working as expected. So the line 71 change is not required. ? Steve. On Jun 16, 2017, at 2:38 PM, Maurice, Candace A > wrote: Hi Steve, I tried to implement the patch, but still no luck. My file on line 71 is different than in the patch you provided (see function below). def search(query, page, records_per_page) uri = URI(@base_url) start_record = calculate_start_record(page, records_per_page) params = default_params.merge('q' => [query.to_s, @scheme], 'count' => records_per_page, 'start' => start_record) uri.query = URI.encode_www_form(params) response = Net::HTTP.get_response(uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end results = OpenSearchResultSet.new(response.body, query) results.entries.each do |entry| marc_uri = URI("#{entry['uri']}.marcxml.xml") response = Net::HTTP.get_response(marc_uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end entry['xml'] = response.body.force_encoding("iso-8859-1").encode('utf-8') end results End -candace From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Thursday, June 15, 2017 at 12:26 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 It appears to be no longer working in any version. I believe loc has changed the API for the service slightly. Need to investigate further. But trying to reverse engineer the parameters from inspecting the difference in the params used in the web page search vs. what?s embedded in LCNAF plugin, I tried this change, which appears to work for me: diff --git a/plugins/lcnaf/frontend/models/opensearcher.rb b/plugins/lcnaf/frontend/models/opensearcher.rb index 9391ab5..37e2813 100644 --- a/plugins/lcnaf/frontend/models/opensearcher.rb +++ b/plugins/lcnaf/frontend/models/opensearcher.rb @@ -14,7 +14,7 @@ class OpenSearcher def initialize(base_url, scheme ) @base_url = base_url - @scheme = scheme + @scheme = "cs:" + scheme end @@ -71,7 +71,7 @@ class OpenSearcher 'start' => start_record) uri.query = URI.encode_www_form(params) - + p uri results = HTTPRequest.new.get(uri) do |response| if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") ( The other OCLC search has always been unreliable ? it?s a test site and not a supported service. ) ? Steve Majewski On Jun 15, 2017, at 12:07 PM, Maurice, Candace A > wrote: Hello All, We are on version 1.4.2 and we have had a user report that the subject heading plugin is not returning results for either LCNAF or LCSH (OCLC works, however). The user doesn?t receive any error messages when using the plugin, but tried typing in known subject headings for the Library Of Congress and it?s still not returning results. I checked the Background jobs and logs and there are not error messages. I also went to the LOC website and all appears to be fine when searching subject headings on their site. Has anyone else experienced a similar issue? Can you point me in the right direction for resolving this issue? Thanks, Candace ------------------------- Candace Maurice Web Developer Howard-Tiltion Memorial Library Tulane University 504.314.7784 cmaurice at tulane.edu <512DA1AA-B52D-4559-9B7E-FB77BCC5BB86.png> _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at eservices.virginia.edu Fri Jun 16 16:50:44 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 16 Jun 2017 20:50:44 +0000 Subject: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 In-Reply-To: References: Message-ID: @scheme is re-used later in the importer to construct the URI for the marc.xml, as well as in the search, so instead of adding the prefix to @scheme, it should just be prefixed in the search parameters: - params = default_params.merge('q' => [query.to_s, @scheme], + params = default_params.merge('q' => [query.to_s, 'cs:' + @scheme], Sorry for the quick & wrong first answer! ? Steve. On Jun 16, 2017, at 4:03 PM, Majewski, Steven Dennis (sdm7g) > wrote: Although those changes seem to fix the search, when I actually try importing either subject or agent records, I get an internal server error. This need more investigation. On Jun 16, 2017, at 3:12 PM, Majewski, Steven Dennis (sdm7g) > wrote: My tests and patch were on current master branch, and so it looks like there were further changes to lcnaf between 1.4.2 and 2.0.1 . But the significant changes in my patch were: [1] prefixing the @scheme parameter with (what I assume is) a field specifier: @scheme = ?cs:? + @scheme ( prefix could either be added to @scheme in initialized method, or else added to the search params in search method. ) You can just manually edit that change if the patch doesn?t work. [2] the ?p uri? prints out the final doc.gov URI and query string. This was part of the debugging and reverse engineering: to compare the URI & query in id.loc.gov search page with what LCNAF plugin was using. Since I?m not sure if API changes to id.loc.gov are documented anywhere, I left it there in case of future changes or problems. You can always grab the URL out of the log file and paste it into curl or your browser to see if it?s working as expected. So the line 71 change is not required. ? Steve. On Jun 16, 2017, at 2:38 PM, Maurice, Candace A > wrote: Hi Steve, I tried to implement the patch, but still no luck. My file on line 71 is different than in the patch you provided (see function below). def search(query, page, records_per_page) uri = URI(@base_url) start_record = calculate_start_record(page, records_per_page) params = default_params.merge('q' => [query.to_s, @scheme], 'count' => records_per_page, 'start' => start_record) uri.query = URI.encode_www_form(params) response = Net::HTTP.get_response(uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end results = OpenSearchResultSet.new(response.body, query) results.entries.each do |entry| marc_uri = URI("#{entry['uri']}.marcxml.xml") response = Net::HTTP.get_response(marc_uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end entry['xml'] = response.body.force_encoding("iso-8859-1").encode('utf-8') end results End -candace From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Thursday, June 15, 2017 at 12:26 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 It appears to be no longer working in any version. I believe loc has changed the API for the service slightly. Need to investigate further. But trying to reverse engineer the parameters from inspecting the difference in the params used in the web page search vs. what?s embedded in LCNAF plugin, I tried this change, which appears to work for me: diff --git a/plugins/lcnaf/frontend/models/opensearcher.rb b/plugins/lcnaf/frontend/models/opensearcher.rb index 9391ab5..37e2813 100644 --- a/plugins/lcnaf/frontend/models/opensearcher.rb +++ b/plugins/lcnaf/frontend/models/opensearcher.rb @@ -14,7 +14,7 @@ class OpenSearcher def initialize(base_url, scheme ) @base_url = base_url - @scheme = scheme + @scheme = "cs:" + scheme end @@ -71,7 +71,7 @@ class OpenSearcher 'start' => start_record) uri.query = URI.encode_www_form(params) - + p uri results = HTTPRequest.new.get(uri) do |response| if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") ( The other OCLC search has always been unreliable ? it?s a test site and not a supported service. ) ? Steve Majewski On Jun 15, 2017, at 12:07 PM, Maurice, Candace A > wrote: Hello All, We are on version 1.4.2 and we have had a user report that the subject heading plugin is not returning results for either LCNAF or LCSH (OCLC works, however). The user doesn?t receive any error messages when using the plugin, but tried typing in known subject headings for the Library Of Congress and it?s still not returning results. I checked the Background jobs and logs and there are not error messages. I also went to the LOC website and all appears to be fine when searching subject headings on their site. Has anyone else experienced a similar issue? Can you point me in the right direction for resolving this issue? Thanks, Candace ------------------------- Candace Maurice Web Developer Howard-Tiltion Memorial Library Tulane University 504.314.7784 cmaurice at tulane.edu <512DA1AA-B52D-4559-9B7E-FB77BCC5BB86.png> _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ 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 sdm7g at eservices.virginia.edu Sat Jun 17 18:15:38 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Sat, 17 Jun 2017 22:15:38 +0000 Subject: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 In-Reply-To: <28ee5b17d88142f08614152640c7eee6@evcspmbx05.ads.northwestern.edu> References: <28ee5b17d88142f08614152640c7eee6@evcspmbx05.ads.northwestern.edu> Message-ID: <76D40E2B-3EC5-4492-9803-6A8B548EA130@eservices.virginia.edu> I don?t believe that behavior is specific to the LCNAF plugin. It?s inherited from the MarcXML base mappings. So if you don?t use the plugin and manually import a MARC XML authority record, I believe that you?ll get the same result. https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/lib/marcxml_base_map.rb#L970-L1043 So perhaps the "or @tag=?450?? should be removed from the base mappings, along with ?451? and ?455? [?] Are there any counter cases where you would want those mappings to create a term ? Does it need to check if there is a previous 15x tag first to determine whether to skip 45x ? ? Steve. On Jun 16, 2017, at 2:57 PM, Karen Miller > wrote: Hi, Candace. I can?t help on the plugin operational issue, but I can offer a caveat about using the plugin for LCSH. This plugin has (until very recently) worked well for us at NUL for importing Agent records from LCNAF, but we have never used it to import Subject records. And, as Steve pointed out, the import from OCLC is unreliable. When a Subject is imported using this plug-in, individual Subject records are created for the preferred term (the MARC 150 field in the authority record) as well as for each of the non-preferred terms (the MARC 450 fields in the authority record, i.e., references). For example, an LCSH record with 4 non-preferred terms will be imported as 5 Subject records, one for the preferred term and one for each of the non-preferred terms, with no indication in the records for the non-preferred terms that they are references and should not be assigned, as well as no indication of the preferred term with which they are associated. This is almost certainly not what your archivists or catalogers want. While the import of Name Authority File (LCNAF) records correctly places non-preferred names in the Agent record for the preferred name designated as references, the import of LCSH records operates differently and would wreak havoc on the use of Subject records. I understand that Yale is undertaking a project to update the plug-in and hopes to change the functionality so that only the preferred Subject term is imported, but until then, I can?t recommend using it. Best, Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maurice, Candace A Sent: Friday, June 16, 2017 1:39 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 Hi Steve, I tried to implement the patch, but still no luck. My file on line 71 is different than in the patch you provided (see function below). def search(query, page, records_per_page) uri = URI(@base_url) start_record = calculate_start_record(page, records_per_page) params = default_params.merge('q' => [query.to_s, @scheme], 'count' => records_per_page, 'start' => start_record) uri.query = URI.encode_www_form(params) response = Net::HTTP.get_response(uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end results = OpenSearchResultSet.new(response.body, query) results.entries.each do |entry| marc_uri = URI("#{entry['uri']}.marcxml.xml") response = Net::HTTP.get_response(marc_uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end entry['xml'] = response.body.force_encoding("iso-8859-1").encode('utf-8') end results End -candace From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Thursday, June 15, 2017 at 12:26 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 It appears to be no longer working in any version. I believe loc has changed the API for the service slightly. Need to investigate further. But trying to reverse engineer the parameters from inspecting the difference in the params used in the web page search vs. what?s embedded in LCNAF plugin, I tried this change, which appears to work for me: diff --git a/plugins/lcnaf/frontend/models/opensearcher.rb b/plugins/lcnaf/frontend/models/opensearcher.rb index 9391ab5..37e2813 100644 --- a/plugins/lcnaf/frontend/models/opensearcher.rb +++ b/plugins/lcnaf/frontend/models/opensearcher.rb @@ -14,7 +14,7 @@ class OpenSearcher def initialize(base_url, scheme ) @base_url = base_url - @scheme = scheme + @scheme = "cs:" + scheme end @@ -71,7 +71,7 @@ class OpenSearcher 'start' => start_record) uri.query = URI.encode_www_form(params) - + p uri results = HTTPRequest.new.get(uri) do |response| if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") ( The other OCLC search has always been unreliable ? it?s a test site and not a supported service. ) ? Steve Majewski On Jun 15, 2017, at 12:07 PM, Maurice, Candace A > wrote: Hello All, We are on version 1.4.2 and we have had a user report that the subject heading plugin is not returning results for either LCNAF or LCSH (OCLC works, however). The user doesn?t receive any error messages when using the plugin, but tried typing in known subject headings for the Library Of Congress and it?s still not returning results. I checked the Background jobs and logs and there are not error messages. I also went to the LOC website and all appears to be fine when searching subject headings on their site. Has anyone else experienced a similar issue? Can you point me in the right direction for resolving this issue? Thanks, Candace ------------------------- Candace Maurice Web Developer Howard-Tiltion Memorial Library Tulane University 504.314.7784 cmaurice at tulane.edu <512DA1AA-B52D-4559-9B7E-FB77BCC5BB86.png> _______________________________________________ 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 mblair1 at stedwards.edu Mon Jun 19 09:35:36 2017 From: mblair1 at stedwards.edu (Megan Blair) Date: Mon, 19 Jun 2017 08:35:36 -0500 Subject: [Archivesspace_Users_Group] Resources not updating Message-ID: Hello, We are currently entering items into ArchivesSpace v.2.0.1 and I have noticed that our resources last modified by and date in the resources overview is not updating. I have attached a screenshot. The changes are there and when you click on the individual items within a resource its shows that modifications have been made [screenshot included]. We can also see the changes reflected in the public view. Any suggestions for how to correct this issue will be greatly appreciated. Best, Megan -- Megan M. Blair Archivist and Public Services Librarian Munday Library St. Edward's University 3001 S. Congress Ave. Austin, TX 78704 512.428.1047 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-06-19 at 8.30.33 AM.png Type: image/png Size: 95208 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-06-19 at 8.29.39 AM.png Type: image/png Size: 60678 bytes Desc: not available URL: From Carolyn-Runyon at utc.edu Mon Jun 19 09:42:49 2017 From: Carolyn-Runyon at utc.edu (Runyon, Carolyn) Date: Mon, 19 Jun 2017 13:42:49 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Reports Update Message-ID: <10113269-BCE3-494D-B416-72444C97B3D5@utc.edu> Colleagues, We know reports are an important consideration for many ArchivesSpace users and wanted to provide an update on current and future plans. The User Advisory Council Reports sub-team, comprised of Carolyn Runyon, Nancy Enneking, Alston Cobourn, Lydia Tang, Nikki Thomas, Brenda Burk, Jasmine Jones, and Laney McGlohon, ArchivesSpace Technical Lead, have been working together particularly over the last couple of months to review the current state of the ArchivesSpace reports, including where they need to be enhanced, and, in some cases, fixed or removed. For the 2.1.0 release, some unnecessary reports, identified by the sub-team as no longer needed because they are duplications of other reports, will be removed. For the 2.1.0 release, we have also put temporary measures into place to ensure that there is consistent, correct, and complete data in all formats of the other built-in reports. To make sure the community better understands how the reports work, we?re also working on adding to both the documentation and error messaging. This will help users understand how to get reports to run and what to do when they encounter problems. An overhaul of the code is needed to undertake the other enhancements to the reporting functionality that the sub-team and Laney have been discussing, such as being able to preview a report and the ability for users to dynamically create their own reports. This will be on the roadmap for the fall. The JIRA tickets associated with reports can be found here: https://archivesspace.atlassian.net/issues/?filter=13200. Thanks for your patience with this process and let us know if you have any questions. Laney and Nancy will be presenting a session on Reports and Report Workarounds at the ArchivesSpace Member Forum next month and we look forward to sharing and hearing more ideas in this area there and in other ways very soon. All the best, Carolyn Carolyn Runyon Assistant Head of Collection Services and Director of Special Collections University of Tennessee at Chattanooga Library 615 McCallie Ave., Chattanooga, TN 37403 Carolyn-Runyon at utc.edu, (423) 425-4503 Dept. 6456, LIB 439D From k-miller3 at northwestern.edu Mon Jun 19 10:46:13 2017 From: k-miller3 at northwestern.edu (Karen Miller) Date: Mon, 19 Jun 2017 14:46:13 +0000 Subject: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 In-Reply-To: <76D40E2B-3EC5-4492-9803-6A8B548EA130@eservices.virginia.edu> References: <28ee5b17d88142f08614152640c7eee6@evcspmbx05.ads.northwestern.edu> <76D40E2B-3EC5-4492-9803-6A8B548EA130@eservices.virginia.edu> Message-ID: Interesting! In any event, a caveat is still deserved. I would recommend removing not just the 450 or 455, but any 550 terms as well. In fact, I?d just keep the 150. There is no place for variant forms of the heading in the AS Subject record the way there is in the Agent record. It would be desirable to keep those terms as variants to facilitate searching, in exactly the same way we use variant forms of names in the Agent records. That would require a change to the data model for Subject records. Karen From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g) Sent: Saturday, June 17, 2017 5:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 I don?t believe that behavior is specific to the LCNAF plugin. It?s inherited from the MarcXML base mappings. So if you don?t use the plugin and manually import a MARC XML authority record, I believe that you?ll get the same result. https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/lib/marcxml_base_map.rb#L970-L1043 So perhaps the "or @tag=?450?? should be removed from the base mappings, along with ?451? and ?455? [?] Are there any counter cases where you would want those mappings to create a term ? Does it need to check if there is a previous 15x tag first to determine whether to skip 45x ? ? Steve. On Jun 16, 2017, at 2:57 PM, Karen Miller > wrote: Hi, Candace. I can?t help on the plugin operational issue, but I can offer a caveat about using the plugin for LCSH. This plugin has (until very recently) worked well for us at NUL for importing Agent records from LCNAF, but we have never used it to import Subject records. And, as Steve pointed out, the import from OCLC is unreliable. When a Subject is imported using this plug-in, individual Subject records are created for the preferred term (the MARC 150 field in the authority record) as well as for each of the non-preferred terms (the MARC 450 fields in the authority record, i.e., references). For example, an LCSH record with 4 non-preferred terms will be imported as 5 Subject records, one for the preferred term and one for each of the non-preferred terms, with no indication in the records for the non-preferred terms that they are references and should not be assigned, as well as no indication of the preferred term with which they are associated. This is almost certainly not what your archivists or catalogers want. While the import of Name Authority File (LCNAF) records correctly places non-preferred names in the Agent record for the preferred name designated as references, the import of LCSH records operates differently and would wreak havoc on the use of Subject records. I understand that Yale is undertaking a project to update the plug-in and hopes to change the functionality so that only the preferred Subject term is imported, but until then, I can?t recommend using it. Best, Karen Karen D. Miller Monographic Cataloger/Metadata Specialist Northwestern University Libraries Northwestern University 1970 Campus Drive Evanston, IL 60208 www.library.northwestern.edu k-miller3 at northwestern.edu 874.467.3462 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maurice, Candace A Sent: Friday, June 16, 2017 1:39 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 Hi Steve, I tried to implement the patch, but still no luck. My file on line 71 is different than in the patch you provided (see function below). def search(query, page, records_per_page) uri = URI(@base_url) start_record = calculate_start_record(page, records_per_page) params = default_params.merge('q' => [query.to_s, @scheme], 'count' => records_per_page, 'start' => start_record) uri.query = URI.encode_www_form(params) response = Net::HTTP.get_response(uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end results = OpenSearchResultSet.new(response.body, query) results.entries.each do |entry| marc_uri = URI("#{entry['uri']}.marcxml.xml") response = Net::HTTP.get_response(marc_uri) if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") end entry['xml'] = response.body.force_encoding("iso-8859-1").encode('utf-8') end results End -candace From: > on behalf of "Majewski, Steven Dennis (sdm7g)" > Reply-To: Archivesspace Users Group > Date: Thursday, June 15, 2017 at 12:26 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Subject Heading Plugin not working properly 1.4.2 It appears to be no longer working in any version. I believe loc has changed the API for the service slightly. Need to investigate further. But trying to reverse engineer the parameters from inspecting the difference in the params used in the web page search vs. what?s embedded in LCNAF plugin, I tried this change, which appears to work for me: diff --git a/plugins/lcnaf/frontend/models/opensearcher.rb b/plugins/lcnaf/frontend/models/opensearcher.rb index 9391ab5..37e2813 100644 --- a/plugins/lcnaf/frontend/models/opensearcher.rb +++ b/plugins/lcnaf/frontend/models/opensearcher.rb @@ -14,7 +14,7 @@ class OpenSearcher def initialize(base_url, scheme ) @base_url = base_url - @scheme = scheme + @scheme = "cs:" + scheme end @@ -71,7 +71,7 @@ class OpenSearcher 'start' => start_record) uri.query = URI.encode_www_form(params) - + p uri results = HTTPRequest.new.get(uri) do |response| if response.code != '200' raise OpenSearchException.new("Error during OpenSearch search: #{response.body}") ( The other OCLC search has always been unreliable ? it?s a test site and not a supported service. ) ? Steve Majewski On Jun 15, 2017, at 12:07 PM, Maurice, Candace A > wrote: Hello All, We are on version 1.4.2 and we have had a user report that the subject heading plugin is not returning results for either LCNAF or LCSH (OCLC works, however). The user doesn?t receive any error messages when using the plugin, but tried typing in known subject headings for the Library Of Congress and it?s still not returning results. I checked the Background jobs and logs and there are not error messages. I also went to the LOC website and all appears to be fine when searching subject headings on their site. Has anyone else experienced a similar issue? Can you point me in the right direction for resolving this issue? Thanks, Candace ------------------------- Candace Maurice Web Developer Howard-Tiltion Memorial Library Tulane University 504.314.7784 cmaurice at tulane.edu <512DA1AA-B52D-4559-9B7E-FB77BCC5BB86.png> _______________________________________________ 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 ltang5 at mail.lib.msu.edu Mon Jun 19 11:01:31 2017 From: ltang5 at mail.lib.msu.edu (Tang, Lydia) Date: Mon, 19 Jun 2017 15:01:31 +0000 Subject: [Archivesspace_Users_Group] Resources not updating In-Reply-To: References: Message-ID: <0BE8D80E-9326-4315-B11D-5029E6F85061@mail.lib.msu.edu> Hi Megan, Currently the ?Last Modified? section is only for edits of on the collection level. There has been a lot of talk and debates about whether to have this reflect edits on any part of the record. I think the JIRA for this issue is here: https://archivesspace.atlassian.net/browse/AR-1580 Please comment and vote on it! ? Lydia From: on behalf of Megan Blair Reply-To: Archivesspace Users Group Date: Monday, June 19, 2017 at 9:35 AM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Resources not updating Hello, We are currently entering items into ArchivesSpace v.2.0.1 and I have noticed that our resources last modified by and date in the resources overview is not updating. I have attached a screenshot. The changes are there and when you click on the individual items within a resource its shows that modifications have been made [screenshot included]. We can also see the changes reflected in the public view. Any suggestions for how to correct this issue will be greatly appreciated. Best, Megan -- Megan M. Blair Archivist and Public Services Librarian Munday Library St. Edward's University 3001 S. Congress Ave. Austin, TX 78704 512.428.1047 From library at princeofpeaceabbey.org Tue Jun 20 09:40:53 2017 From: library at princeofpeaceabbey.org (library at princeofpeaceabbey.org) Date: Tue, 20 Jun 2017 08:40:53 -0500 Subject: [Archivesspace_Users_Group] ArchivesSpace Reports Update In-Reply-To: <10113269-BCE3-494D-B416-72444C97B3D5@utc.edu> Message-ID: <20170620084053.Horde.FAsGVuPPygOON7abbAn8XRj@gator3088.hostgator.com> I am Br Raphael from Prince of Peace Abbey and I have a problem with the resource location report. Could you look at the attachment and tell me if I have done something wrong. Quoting "Runyon, Carolyn" : > Colleagues, > > We know reports are an important consideration for many > ArchivesSpace users and wanted to provide an update on current and > future plans. The User Advisory Council Reports sub-team, comprised > of Carolyn Runyon, Nancy Enneking, Alston Cobourn, Lydia Tang, Nikki > Thomas, Brenda Burk, Jasmine Jones, and Laney McGlohon, > ArchivesSpace Technical Lead, have been working together > particularly over the last couple of months to review the current > state of the ArchivesSpace reports, including where they need to be > enhanced, and, in some cases, fixed or removed. For the 2.1.0 > release, some unnecessary reports, identified by the sub-team as no > longer needed because they are duplications of other reports, will > be removed. For the 2.1.0 release, we have also put temporary > measures into place to ensure that there is consistent, correct, and > complete data in all formats of the other built-in reports. > > To make sure the community better understands how the reports work, > we?re also working on adding to both the documentation and error > messaging. This will help users understand how to get reports to run > and what to do when they encounter problems. > > An overhaul of the code is needed to undertake the other > enhancements to the reporting functionality that the sub-team and > Laney have been discussing, such as being able to preview a report > and the ability for users to dynamically create their own reports. > This will be on the roadmap for the fall. The JIRA tickets > associated with reports can be found here: > https://archivesspace.atlassian.net/issues/?filter=13200. > > Thanks for your patience with this process and let us know if you > have any questions. Laney and Nancy will be presenting a session on > Reports and Report Workarounds at the ArchivesSpace Member Forum > next month and we look forward to sharing and hearing more ideas in > this area there and in other ways very soon. > > All the best, > Carolyn > > Carolyn Runyon > Assistant Head of Collection Services and Director of Special Collections > University of Tennessee at Chattanooga Library > 615 McCallie Ave., Chattanooga, TN 37403 > Carolyn-Runyon at utc.edu, (423) 425-4503 > Dept. 6456, LIB 439D > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- A non-text attachment was scrubbed... Name: job_47_file_105.pdf Type: application/pdf Size: 402625 bytes Desc: not available URL: From Henry.Steele at tufts.edu Tue Jun 20 09:49:21 2017 From: Henry.Steele at tufts.edu (Steele, Henry) Date: Tue, 20 Jun 2017 13:49:21 +0000 Subject: [Archivesspace_Users_Group] expanding fields available to create digital objects - API Message-ID: Good morning, I assist Digital Collections & Archives at Tufts University with ArchivesSpace administration. I have recently been working on a modification to the Digital Object Manager plugin developed by Kevin Clair at Duke University. Digital Collections & Archives uses the DOM to update digital objects, but they asked me for a way to create digital objects from a larger input CSV with more fields. Using the API, I modified a local version of DOM so that it would create a digital object with the following fields, using the post method for digital objects: - Title - digital object identifier - file_uri - restrictions Using another method, I was able to set the digital object to publish, including the subrecords. However, there are a few fields we would like to add to the new digital object that appear they may not be supported in the create digital object method in the API. The API documentation doesn't list these fields in the JSON under the Create Digital Object method. The most important field we want to include is "Checksum" but also would like to add: - checksum (mentioned above) - user_defined_string_1 (we're using this for location) - digital_object_level - checksum method More broadly, is it possible to expand the number of fields available in digital object creation, or in a subsequent update of the new digital object? -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob.green at uni.edu Tue Jun 20 10:39:04 2017 From: rob.green at uni.edu (Rob Green) Date: Tue, 20 Jun 2017 09:39:04 -0500 Subject: [Archivesspace_Users_Group] Cracking into an Archon Login Account for migrating to ArchiveSpace Message-ID: Hi! A stab in the dark, but but any of you know of a way to force entry into an Archon admin account? Like a secret "always works" password? Or is that just a thing in the movies? I'm a web developer for the University of Northern Iowa who has the task of migrating our old Archon data to our spiffy new ArchivesSpace account. Sadly, the person who set up the account is no longer with us, and none of our usual passwords seem to work. I can get into the actual MySQL database just fine (to see everything)....I just can't view it as an admin on the website, which as I understand it, I need to be able to do in order to migrate. Any thoughts would be greatly appreciated; success may mean a shipped gift of bratwursts from the nearby Amana Colonies. :) Thanks in advance! Rob *Rob Green *rob.green at uni.edu *Web Developer III* *Chair, Library Organizational Development Committee* *UNI P&S Council: At-Large Rep & Employee Relations Chair *Rod Library, University of Northern Iowa (Room 231) Cedar Falls, Iowa 50613-3675 | (319) 273-6273 about.me/robgreeniowa | "Campaigner" (ENFP) -------------- next part -------------- An HTML attachment was scrubbed... URL: From lwoodford at jhu.edu Tue Jun 20 10:45:26 2017 From: lwoodford at jhu.edu (Lora Davis) Date: Tue, 20 Jun 2017 14:45:26 +0000 Subject: [Archivesspace_Users_Group] expanding fields available to create digital objects - API In-Reply-To: References: Message-ID: <09b4c474046b45dc85f106196f7519e0@ESGEBEX8.win.ad.jhu.edu> Hi Henry, I'm not familiar with that plugin, but, in general, posting in that information through the API should not be a problem (I have several scripts that do this). As long as you construct JSON that generally looks like this, you should be golden. { "digital_object_id": "Your digital object identifier", "title": "Your title", "jsonmodel_type": "digital_object", "file_versions": [ { "file_uri": "Your file uri", "publish": false, "checksum": "Your checksum", "checksum_method": "sha-256", "jsonmodel_type": "file_version" } ], "user_defined": { "string_1": "Your string 1", "jsonmodel_type": "user_defined" } } For what it's worth, I've found that it is best not to take the existing API documentation as a hard and fast rule for what can/cannot be done via the API. The documentation is more an overview map, than it is a list of turn-by-turn directions. I keep a local instance of ASpace running that I can throw things at using scripts and/or GUI API clients like Postman (https://www.getpostman.com/) or any number of browser add-ons/extensions. Starting by trying to do the thing I want to do on a small scale before ramping up has routinely paid me dividends and shown me possible solutions I would have never thought of were I just going off of existing documentation. Best, Lora Lora J. (Davis) Woodford Digital Archivist The Sheridan Libraries Johns Hopkins University 3400 North Charles Street Baltimore, MD 21228 (410) 516-5898 lwoodford at jhu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Steele, Henry Sent: Tuesday, June 20, 2017 9:49 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] expanding fields available to create digital objects - API Good morning, I assist Digital Collections & Archives at Tufts University with ArchivesSpace administration. I have recently been working on a modification to the Digital Object Manager plugin developed by Kevin Clair at Duke University. Digital Collections & Archives uses the DOM to update digital objects, but they asked me for a way to create digital objects from a larger input CSV with more fields. Using the API, I modified a local version of DOM so that it would create a digital object with the following fields, using the post method for digital objects: - Title - digital object identifier - file_uri - restrictions Using another method, I was able to set the digital object to publish, including the subrecords. However, there are a few fields we would like to add to the new digital object that appear they may not be supported in the create digital object method in the API. The API documentation doesn't list these fields in the JSON under the Create Digital Object method. The most important field we want to include is "Checksum" but also would like to add: - checksum (mentioned above) - user_defined_string_1 (we're using this for location) - digital_object_level - checksum method More broadly, is it possible to expand the number of fields available in digital object creation, or in a subsequent update of the new digital object? -------------- next part -------------- An HTML attachment was scrubbed... URL: From prom at illinois.edu Tue Jun 20 10:51:43 2017 From: prom at illinois.edu (Prom, Christopher John) Date: Tue, 20 Jun 2017 14:51:43 +0000 Subject: [Archivesspace_Users_Group] Cracking into an Archon Login Account for migrating to ArchiveSpace In-Reply-To: References: Message-ID: You will need to force a new hash value into the password field of the user table for one of the existing users. If you contact me off list I can help since I had to do this in one other instance and am familiar with the process. Thanks, Chris Christopher J. Prom, PhD Andrew S. G. Turyn Professor Assistant University Archivist 146 Library 1408 W. Gregory Drive Urbana, IL 61801 prom at illinois.edu 217 244 2052 http://archivalconnections.org On Jun 20, 2017, at 9:39 AM, Rob Green > wrote: Hi! A stab in the dark, but but any of you know of a way to force entry into an Archon admin account? Like a secret "always works" password? Or is that just a thing in the movies? I'm a web developer for the University of Northern Iowa who has the task of migrating our old Archon data to our spiffy new ArchivesSpace account. Sadly, the person who set up the account is no longer with us, and none of our usual passwords seem to work. I can get into the actual MySQL database just fine (to see everything)....I just can't view it as an admin on the website, which as I understand it, I need to be able to do in order to migrate. Any thoughts would be greatly appreciated; success may mean a shipped gift of bratwursts from the nearby Amana Colonies. :) Thanks in advance! Rob Rob Green rob.green at uni.edu Web Developer III Chair, Library Organizational Development Committee UNI P&S Council: At-Large Rep & Employee Relations Chair Rod Library, University of Northern Iowa (Room 231) Cedar Falls, Iowa 50613-3675 | (319) 273-6273 about.me/robgreeniowa | "Campaigner" (ENFP) _______________________________________________ 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 Kate.F.Herbert at maine.gov Tue Jun 20 14:09:37 2017 From: Kate.F.Herbert at maine.gov (Herbert, Kate F) Date: Tue, 20 Jun 2017 18:09:37 +0000 Subject: [Archivesspace_Users_Group] Error when entering RDE Message-ID: We have two interns entering folder and item level data via the RDE one of them has been unable to use RDE at all because every time they try to save the data they have entered they get this error "0 row(s) with an error- click a row field to view the errors for that row" The second intern who is logged on to the same account was able to enter via RDE until today and now they are also getting this error. We have tried switching computers and logins but the error persists. Any idea as to what could be causing it? -------------- next part -------------- An HTML attachment was scrubbed... URL: From apacy at cambridgema.gov Tue Jun 20 14:35:03 2017 From: apacy at cambridgema.gov (Pacy, Alyssa) Date: Tue, 20 Jun 2017 18:35:03 +0000 Subject: [Archivesspace_Users_Group] (no subject) Message-ID: We recently upgraded to the newest version of ArchivesSpace and we're now having a problem with resources, subjects, agents, etc. not showing up in the public interface until after they've been edited in the admin interface. Anyone else have this problem? Thank you! Alyssa Alyssa Pacy Archivist|Cambridge Public Library 449 Broadway|Cambridge, MA 02138 617-349-7757|http://thecambridgeroom.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Henry.Steele at tufts.edu Tue Jun 20 15:55:19 2017 From: Henry.Steele at tufts.edu (Steele, Henry) Date: Tue, 20 Jun 2017 19:55:19 +0000 Subject: [Archivesspace_Users_Group] expanding fields available to create digital objects - API In-Reply-To: <09b4c474046b45dc85f106196f7519e0@ESGEBEX8.win.ad.jhu.edu> References: <09b4c474046b45dc85f106196f7519e0@ESGEBEX8.win.ad.jhu.edu> Message-ID: Thank you very much for your response. I see the error I made was mistakenly trying to include user-defined fields in an array, when they are only in a hash. But your response let me know that these fields are available for update, and not to take the API documentation too literally. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lora Davis Sent: Tuesday, June 20, 2017 10:45 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] expanding fields available to create digital objects - API Hi Henry, I'm not familiar with that plugin, but, in general, posting in that information through the API should not be a problem (I have several scripts that do this). As long as you construct JSON that generally looks like this, you should be golden. { "digital_object_id": "Your digital object identifier", "title": "Your title", "jsonmodel_type": "digital_object", "file_versions": [ { "file_uri": "Your file uri", "publish": false, "checksum": "Your checksum", "checksum_method": "sha-256", "jsonmodel_type": "file_version" } ], "user_defined": { "string_1": "Your string 1", "jsonmodel_type": "user_defined" } } For what it's worth, I've found that it is best not to take the existing API documentation as a hard and fast rule for what can/cannot be done via the API. The documentation is more an overview map, than it is a list of turn-by-turn directions. I keep a local instance of ASpace running that I can throw things at using scripts and/or GUI API clients like Postman (https://www.getpostman.com/) or any number of browser add-ons/extensions. Starting by trying to do the thing I want to do on a small scale before ramping up has routinely paid me dividends and shown me possible solutions I would have never thought of were I just going off of existing documentation. Best, Lora Lora J. (Davis) Woodford Digital Archivist The Sheridan Libraries Johns Hopkins University 3400 North Charles Street Baltimore, MD 21228 (410) 516-5898 lwoodford at jhu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Steele, Henry Sent: Tuesday, June 20, 2017 9:49 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] expanding fields available to create digital objects - API Good morning, I assist Digital Collections & Archives at Tufts University with ArchivesSpace administration. I have recently been working on a modification to the Digital Object Manager plugin developed by Kevin Clair at Duke University. Digital Collections & Archives uses the DOM to update digital objects, but they asked me for a way to create digital objects from a larger input CSV with more fields. Using the API, I modified a local version of DOM so that it would create a digital object with the following fields, using the post method for digital objects: - Title - digital object identifier - file_uri - restrictions Using another method, I was able to set the digital object to publish, including the subrecords. However, there are a few fields we would like to add to the new digital object that appear they may not be supported in the create digital object method in the API. The API documentation doesn't list these fields in the JSON under the Create Digital Object method. The most important field we want to include is "Checksum" but also would like to add: - checksum (mentioned above) - user_defined_string_1 (we're using this for location) - digital_object_level - checksum method More broadly, is it possible to expand the number of fields available in digital object creation, or in a subsequent update of the new digital object? -------------- next part -------------- An HTML attachment was scrubbed... URL: From apacy at cambridgema.gov Wed Jun 21 13:56:04 2017 From: apacy at cambridgema.gov (Pacy, Alyssa) Date: Wed, 21 Jun 2017 17:56:04 +0000 Subject: [Archivesspace_Users_Group] Resources, subjects, agents not showing up in public interface after upgrade Message-ID: We recently upgraded to the newest version of ArchivesSpace and we're now having a problem with resources, subjects, agents, etc. not showing up in the public interface until after they've been edited in the admin interface. Anyone else have this problem? Is there an easy fix? Thank you! Alyssa Alyssa Pacy Archivist|Cambridge Public Library 449 Broadway|Cambridge, MA 02138 617-349-7757|http://thecambridgeroom.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From edgar-garcia at northwestern.edu Wed Jun 21 16:23:18 2017 From: edgar-garcia at northwestern.edu (Edgar Garcia) Date: Wed, 21 Jun 2017 20:23:18 +0000 Subject: [Archivesspace_Users_Group] Resources, subjects, agents not showing up in public interface after upgrade Message-ID: Reindexing after an upgrade takes a while but something should be showing up within the hour? Unless someone else can correct me, I believe we had similar issues in the past where some SOLR index files might have been corrupted. We had to delete the index and have ArchivesSpace reindex everything. Within the scripts directory you can run the checkindex script against the solr_index/index directory to see if there are any issues. Here is the linux command: scripts/checkindex.sh data/solr_index/index Here are the index files to delete: /path/to/archivespace/data/solr_index/index/ Also delete: /path/to/archivesspace/data/indexer_state /path/to/archivesspace/data/indexer_pui_state This process might take some time to index/complete depending on how large your database is, but it should start doing it once the above is deleted. If this does not fix the issue, there could also be a problem with memory being allocated: http://archivesspace.github.io/archivesspace/user/tuning-archivesspace/ a server/service restart COULD fix it temporarily in this case but it will eventually happen again. You will have to reindex things again to fix any of the records that were not updated. Edgar ---------- Edgar Garcia Senior Software Developer Discovery Platform Services Metadata & Discovery Services Digital Strategies Northwestern University Libraries Northwestern University Evanston, IL 60208 From: on behalf of "Pacy, Alyssa" Reply-To: "archivesspace_users_group at lyralists.lyrasis.org" Date: Wednesday, June 21, 2017 at 12:56 PM To: "archivesspace_users_group at lyralists.lyrasis.org" Subject: [Archivesspace_Users_Group] Resources, subjects, agents not showing up in public interface after upgrade We recently upgraded to the newest version of ArchivesSpace and we?re now having a problem with resources, subjects, agents, etc. not showing up in the public interface until after they?ve been edited in the admin interface. Anyone else have this problem? Is there an easy fix? Thank you! Alyssa Alyssa Pacy Archivist|Cambridge Public Library 449 Broadway|Cambridge, MA 02138 617-349-7757|http://thecambridgeroom.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Thu Jun 22 08:08:10 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 22 Jun 2017 12:08:10 +0000 Subject: [Archivesspace_Users_Group] EAD3 export for ArchivesSpace being developed through a partnership of NC State and Duke Message-ID: Hello ArchivesSpace members, I'm pleased to announce that community members Trevor Thornton of North Carolina State University and Noah Huffman of Duke University are taking the lead this summer on building an exporter that will provide a first level of EAD3 support in the ArchivesSpace application. Trevor will be doing the development and Noah will be providing leadership and guidance from the functional side of things. Their work will be based on the mapping for EAD3 that the Migrations sub-team of our Technical Advisory Council circulated in the community earlier this year. The initial focus is on ArchivesSpace being able to export valid EAD3. Building on this work, the program will continue to consider how to provide additional levels of support - with help in this area always much appreciated. As work proceeds, you will be able to comment on and track progress in the JIRA issue: https://archivesspace.atlassian.net/browse/AR-923. The guiding principles and mapping being used for the project are linked from the comments on the issue. We'll post more links, including to the Github repository for the developing code, as work progresses. For questions about the EAD3 exporter project, please contact Noah (noah.huffman at duke.edu) or Trevor (trthorn2 at ncsu.edu). For questions or ideas about EAD3 support overall, feel free to post to the JIRA issue or get in touch with me. Thanks to Trevor and Noah and their institutions for their generosity in taking on this project. If you or your institution are interested in getting more involved in development for ArchivesSpace, and either have projects in mind or want to know about projects already prioritized by the community, please get in touch with Laney or me. We'd love to hear from you! Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: From bthomas at tsl.texas.gov Thu Jun 22 10:36:02 2017 From: bthomas at tsl.texas.gov (Brian Thomas) Date: Thu, 22 Jun 2017 14:36:02 +0000 Subject: [Archivesspace_Users_Group] Appraisal plug-in Message-ID: We are considering appraisal reports for our implementation of AS and were wondering if anyone is using a plug-in to handle this type of thing? I didn't see anything in the plug-ins on the wiki. The User Defined fields will work, but if someone has something better... Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From christine.dibella at lyrasis.org Thu Jun 22 15:09:16 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 22 Jun 2017 19:09:16 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace release candidate available - v2.1.0-RC1 Message-ID: Dear ArchivesSpace members, We are pleased to announce that a release candidate - v2.1.0-RC1 (https://github.com/archivesspace/archivesspace/releases/tag/v2.1.0-RC1) - is now available for download and testing purposes. Among other new functionality, ArchivesSpace 2.1.0 includes the production-ready version of the new public interface. More details on the specifics are in the notes included with the release candidate. This release candidate features substantial work from our development partner, Hudson Molonglo (HM), as well as contributions from community members. User documentation is in the works for the new features. In the interim, if you have questions about how anything is intended to work, please get in touch. Testing and Feedback Please try out this release candidate and let us know if you experience any problems. If you use this release candidate with your own data, please note that a full index is required. (If you currently use rights statements, you'll want to pay particular attention to how your rights data migrates to the new model.) Also, please note that running reports requires a MySQL database backend. You will not be able to run reports with the embedded database. If you don't wish to download anything at this time, you can still test drive the release candidate on our test site, http://test.archivesspace.org, using the standard administrative login (admin/admin). This is another time where many of the changes are larger than single issues in JIRA. As such, we're asking people to provide feedback by emailing me directly. We encourage you to run through the areas of the application you use regularly and let us know if anything that was working previously appears not to be, or if anything described about the new functionality is not working as intended. We'd like to get as much feedback as possible by Friday, June 30. We will determine the exact release date for 2.1.0 when we are confident in the testing results. Thanks Thanks to HM for all their work on this release candidate, to our community members who contributed code, to those on the Prioritization, Reports, and Testing sub-teams who identified and tested specific changes in recent months, to our specification writers for the new rights statements and OAI-PMH functionality, and especially to Mark Custer and the Public Interface Enhancement Project participants for their extensive efforts in bringing a new public interface to fruition. Even more than most of our releases, ArchivesSpace will 2.1.0 represent a major community effort and we are very appreciative of all of the different types of contributions that make this application better. Thank you all! If you have any questions, or if you notice any issues while testing, 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: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: From livsolis at utexas.edu Fri Jun 23 09:15:59 2017 From: livsolis at utexas.edu (Olivia S Solis) Date: Fri, 23 Jun 2017 08:15:59 -0500 Subject: [Archivesspace_Users_Group] Appraisal plug-in In-Reply-To: References: Message-ID: Hi Brian, For clarification, do you mean a monetary appraisal or an archival appraisal? We are interested in representing monetary appraisals in ASpace. For now we decided to document the info in the "Appraisal" event. It would be nice to be able to document monetary value in an easily searchable way, though. Thanks, Olivia On Thu, Jun 22, 2017 at 9:36 AM, Brian Thomas wrote: > We are considering appraisal reports for our implementation of AS and were > wondering if anyone is using a plug-in to handle this type of thing? I > didn?t see anything in the plug-ins on the wiki. The User Defined fields > will work, but if someone has something better? > > > > Brian Thomas > > Electronic Records Specialist > > Texas State Library and Archives Commission > > 1201 Brazos Street > > Austin, TX 78701 > > PH: (512) 475-3374 > > e-mail: bthomas at tsl.texas.gov > > tsl.texas.gov > > [image: cid:image001.jpg at 01D029A2.37194C70] > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: not available URL: From bthomas at tsl.texas.gov Fri Jun 23 09:54:19 2017 From: bthomas at tsl.texas.gov (Brian Thomas) Date: Fri, 23 Jun 2017 13:54:19 +0000 Subject: [Archivesspace_Users_Group] Appraisal plug-in In-Reply-To: References: Message-ID: I was referring to an archival appraisal plug-in. We are not worried at the moment about valuation, and unfortunately the appraisal/de-accession events do not allow the level of detail we are seeking. Thanks for the reply Brian From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Olivia S Solis Sent: Friday, June 23, 2017 8:16 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Appraisal plug-in Hi Brian, For clarification, do you mean a monetary appraisal or an archival appraisal? We are interested in representing monetary appraisals in ASpace. For now we decided to document the info in the "Appraisal" event. It would be nice to be able to document monetary value in an easily searchable way, though. Thanks, Olivia On Thu, Jun 22, 2017 at 9:36 AM, Brian Thomas > wrote: We are considering appraisal reports for our implementation of AS and were wondering if anyone is using a plug-in to handle this type of thing? I didn?t see anything in the plug-ins on the wiki. The User Defined fields will work, but if someone has something better? Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 5314 bytes Desc: image001.png URL: From trthorn2 at ncsu.edu Fri Jun 23 10:21:26 2017 From: trthorn2 at ncsu.edu (Trevor Thornton) Date: Fri, 23 Jun 2017 10:21:26 -0400 Subject: [Archivesspace_Users_Group] Trouble transferring resource Message-ID: Hi- We're trying to transfer a relatively large resource to a different repository and the transfer keeps failing with a CookieOverflow exception (the most delicious exception of all). The exception response HTML is attached. We're on v. 1.5.1. Anybody every experience this? Is there a cure? Thanks, Trevor Thornton -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Jun 23 15:38:20 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 23 Jun 2017 19:38:20 +0000 Subject: [Archivesspace_Users_Group] Appraisal plug-in In-Reply-To: References: Message-ID: Yale University has worked with HM to develop a number of plugins to extend the accessions module for its purposes. See http://guides.library.yale.edu/archivesspace/ArchivesSpaceAccessioning for at least some of them. There may be something you can use or adapt for monetary appraisals. If you?re just needing a single field of information, a user-defined field might be a good choice. (In fact, this is an example we use in our trainings of something someone might use a user-defined field for.) The assessment module that Tufts is subsidizing and that is projected to be available for release in the fall will provide some support for the archival appraisal function. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brian Thomas Sent: Friday, June 23, 2017 9:54 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Appraisal plug-in I was referring to an archival appraisal plug-in. We are not worried at the moment about valuation, and unfortunately the appraisal/de-accession events do not allow the level of detail we are seeking. Thanks for the reply Brian From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Olivia S Solis Sent: Friday, June 23, 2017 8:16 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Appraisal plug-in Hi Brian, For clarification, do you mean a monetary appraisal or an archival appraisal? We are interested in representing monetary appraisals in ASpace. For now we decided to document the info in the "Appraisal" event. It would be nice to be able to document monetary value in an easily searchable way, though. Thanks, Olivia On Thu, Jun 22, 2017 at 9:36 AM, Brian Thomas > wrote: We are considering appraisal reports for our implementation of AS and were wondering if anyone is using a plug-in to handle this type of thing? I didn?t see anything in the plug-ins on the wiki. The User Defined fields will work, but if someone has something better? Brian Thomas Electronic Records Specialist Texas State Library and Archives Commission 1201 Brazos Street Austin, TX 78701 PH: (512) 475-3374 e-mail: bthomas at tsl.texas.gov tsl.texas.gov [cid:image001.jpg at 01D029A2.37194C70] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 13904 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 2994 bytes Desc: image003.jpg URL: From laney.mcglohon at lyrasis.org Mon Jun 26 09:23:12 2017 From: laney.mcglohon at lyrasis.org (Laney McGlohon) Date: Mon, 26 Jun 2017 13:23:12 +0000 Subject: [Archivesspace_Users_Group] Trouble transferring resource In-Reply-To: References: Message-ID: <15600B98-E1FF-4796-ADBC-87EDCCDC8779@lyrasis.org> Hey Trevor, We need to change and use sessions instead of cookies for transferring large resources. I have added comment from StackOverflow (my favorite source) to the JIRA ticket, Here it is again: Rails cookies are limited to 4KB. Note that the sessions is also stored in the cookie in the default configuration. See: http://guides.rubyonrails.org/security.html#session-storage The only thing you can do about that: Do not store big objects in the cookie. Store them in the database and then only store the object's id in the cookie. This answer might also be interesting to you: https://stackoverflow.com/a/4604212/2483313 Laney Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org 800.999.8558 x2927 laneymcglohon Skype From: on behalf of Trevor Thornton Reply-To: Archivesspace Users Group Date: Friday, June 23, 2017 at 10:21 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Trouble transferring resource Hi- We're trying to transfer a relatively large resource to a different repository and the transfer keeps failing with a CookieOverflow exception (the most delicious exception of all). The exception response HTML is attached. We're on v. 1.5.1. Anybody every experience this? Is there a cure? Thanks, Trevor Thornton -- Trevor Thornton Applications Developer, Digital Library Initiatives North Carolina State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From livsolis at utexas.edu Mon Jun 26 12:05:33 2017 From: livsolis at utexas.edu (Olivia S Solis) Date: Mon, 26 Jun 2017 11:05:33 -0500 Subject: [Archivesspace_Users_Group] Appraisal plug-in In-Reply-To: References: Message-ID: Hi Christina, Thanks for sharing, and yes, we have already incorporated Yale's purchases plugin, as well as the material types one, in our implementation but have not really considered the possibility of adapting it for the purposes of monetary appraisals. It is certainly worth considering. Thanks for the suggestion! And Brian, I would definitely be interested in what kind of archival appraisal plugin could be developed/is being developed for ASpace, so I would love to hear about any traction you get on this post. Thanks! Olivia On Fri, Jun 23, 2017 at 2:38 PM, Christine Di Bella < christine.dibella at lyrasis.org> wrote: > Yale University has worked with HM to develop a number of plugins to > extend the accessions module for its purposes. See > http://guides.library.yale.edu/archivesspace/ArchivesSpaceAccessioning > for at least some of them. There may be something you can use or adapt for > monetary appraisals. > > > > If you?re just needing a single field of information, a user-defined field > might be a good choice. (In fact, this is an example we use in our > trainings of something someone might use a user-defined field for.) > > > > The assessment module that Tufts is subsidizing and that is projected to > be available for release in the fall will provide some support for the > archival appraisal function. > > > > Christine > > > > Christine Di Bella > > ArchivesSpace Program Manager > > christine.dibella at lyrasis.org > > 800.999.8558 x2905 <(800)%20999-8558> > > 678-235-2905 <(678)%20235-2905> > > cdibella13 (Skype) > > > > [image: ASpaceOrgHomeMedium] > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Brian > Thomas > *Sent:* Friday, June 23, 2017 9:54 AM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > > *Subject:* Re: [Archivesspace_Users_Group] Appraisal plug-in > > > > I was referring to an archival appraisal plug-in. We are not worried at > the moment about valuation, and unfortunately the appraisal/de-accession > events do not allow the level of detail we are seeking. > > Thanks for the reply > > Brian > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Olivia > S Solis > *Sent:* Friday, June 23, 2017 8:16 AM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Appraisal plug-in > > > > Hi Brian, > > For clarification, do you mean a monetary appraisal or an archival > appraisal? We are interested in representing monetary appraisals in ASpace. > For now we decided to document the info in the "Appraisal" event. It would > be nice to be able to document monetary value in an easily searchable way, > though. > > Thanks, > Olivia > > > > On Thu, Jun 22, 2017 at 9:36 AM, Brian Thomas > wrote: > > We are considering appraisal reports for our implementation of AS and were > wondering if anyone is using a plug-in to handle this type of thing? I > didn?t see anything in the plug-ins on the wiki. The User Defined fields > will work, but if someone has something better? > > > > Brian Thomas > > Electronic Records Specialist > > Texas State Library and Archives Commission > > 1201 Brazos Street > > Austin, TX 78701 > > PH: (512) 475-3374 > > e-mail: bthomas at tsl.texas.gov > > tsl.texas.gov > > [image: cid:image001.jpg at 01D029A2.37194C70] > > > > > _______________________________________________ > 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 <(512)%20232-8013> > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 13904 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 2994 bytes Desc: not available URL: From laurie.arp at lyrasis.org Tue Jun 27 09:59:53 2017 From: laurie.arp at lyrasis.org (Laurie Arp) Date: Tue, 27 Jun 2017 13:59:53 +0000 Subject: [Archivesspace_Users_Group] New ArchivesSpace Community Engagement Coordinator: Christine Kim Message-ID: LYRASIS, the organizational home for ArchivesSpace, is pleased to announce that Christine Kim will be joining us as our Community Engagement Coordinator. Christine has been working in a variety of roles in Special Collections & Archives at ArchivesSpace charter member institution University of California Irvine (UCI) since 2010. With ArchivesSpace, she was first involved in helping to ensure UCI's smooth transition from Archivists' Toolkit, and now uses the ArchivesSpace application and supervises others in their use of it on a daily basis. Her ArchivesSpace-specific activities at UCI include testing migrations and features, developing and implementing workflows, creating user documentation, training, and working closely with staff, students, and IT support to make the application work for all. Her most recent position at UCI combines technical services, public services, and outreach activities, giving her a broad view of archives and the needs of different kinds of users of archives. She has taken a lead role in developing dynamic campus and community programming to highlight materials in Special Collections & Archives, including a now annual ZineFest that promotes UCI's rich collections of handmade, community-centric zines and gives participants chances to engage with and produce their own content. She received her MLIS from San Jose State University and has an undergraduate degree from UCI with a dual major in Film & Media Studies and History. As Community Engagement Coordinator, Christine Kim will be responsible for user support, training, outreach, and communications across the ArchivesSpace community and will work especially closely with the User Documentation and Testing sub-teams of our Advisory Councils. One of her first priorities will be working with Christine Di Bella and the rest of the ArchivesSpace team to develop engaging programming and other opportunities for ArchivesSpace users to share their expertise with each other in person and online. LYRASIS serves as the organizational home for ArchivesSpace, providing resources and services to help grow, support and amplify the community contributions. These include staff, technology, financial services and logistics support. The ArchivesSpace team, consisting of Christine Di Bella, Program Manager, Laney McGlohon, our Technical Lead, and now Christine Kim, our Community Engagement Coordinator, reports to Laurie Arp, LYRASIS's Director of Collections Services & Community Supported Software. To distinguish who's who on the ArchivesSpace team, Christine Kim will go by "Kim." Kim's first day will be July 10 and we're especially pleased that she'll be part of our Member Forum and other activities in conjunction with SAA in Portland at the end of July. She will continue to be based in Southern California, but is sure to become a lively presence on our listservs and a familiar face as she represents ArchivesSpace at conferences and in other venues. Please join us in welcoming Christine Kim to the ArchivesSpace team! Laurie Gemmill Arp Director, Collections Services & Community Supported Software laurie.arp at lyrasis.org 800.999.8558 x 2908 Fax: 404.592.4804 laurie.gemmill1 Skype [cid:D9C43C04-DF4E-467C-B0BC-358EF417F998] Save the Date for the 2017 Member Summit: October 11-12 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 4483 bytes Desc: image001.png URL: From apacy at cambridgema.gov Tue Jun 27 12:46:09 2017 From: apacy at cambridgema.gov (Pacy, Alyssa) Date: Tue, 27 Jun 2017 16:46:09 +0000 Subject: [Archivesspace_Users_Group] Resources, subjects, agents not showing up in public interface after upgrade In-Reply-To: References: Message-ID: Thank you! It worked perfectly. Alyssa From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Edgar Garcia Sent: Wednesday, June 21, 2017 4:23 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Resources, subjects, agents not showing up in public interface after upgrade Reindexing after an upgrade takes a while but something should be showing up within the hour? Unless someone else can correct me, I believe we had similar issues in the past where some SOLR index files might have been corrupted. We had to delete the index and have ArchivesSpace reindex everything. Within the scripts directory you can run the checkindex script against the solr_index/index directory to see if there are any issues. Here is the linux command: scripts/checkindex.sh data/solr_index/index Here are the index files to delete: /path/to/archivespace/data/solr_index/index/ Also delete: /path/to/archivesspace/data/indexer_state /path/to/archivesspace/data/indexer_pui_state This process might take some time to index/complete depending on how large your database is, but it should start doing it once the above is deleted. If this does not fix the issue, there could also be a problem with memory being allocated: http://archivesspace.github.io/archivesspace/user/tuning-archivesspace/ a server/service restart COULD fix it temporarily in this case but it will eventually happen again. You will have to reindex things again to fix any of the records that were not updated. Edgar ---------- Edgar Garcia Senior Software Developer Discovery Platform Services Metadata & Discovery Services Digital Strategies Northwestern University Libraries Northwestern University Evanston, IL 60208 From: > on behalf of "Pacy, Alyssa" > Reply-To: "archivesspace_users_group at lyralists.lyrasis.org" > Date: Wednesday, June 21, 2017 at 12:56 PM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Resources, subjects, agents not showing up in public interface after upgrade We recently upgraded to the newest version of ArchivesSpace and we?re now having a problem with resources, subjects, agents, etc. not showing up in the public interface until after they?ve been edited in the admin interface. Anyone else have this problem? Is there an easy fix? Thank you! Alyssa Alyssa Pacy Archivist|Cambridge Public Library 449 Broadway|Cambridge, MA 02138 617-349-7757|http://thecambridgeroom.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Jun 27 14:28:20 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 27 Jun 2017 18:28:20 +0000 Subject: [Archivesspace_Users_Group] registration continues for the ArchivesSpace Member Forum 2017 Message-ID: Hello ArchivesSpace Members, Thanks to all who have registered so far for the Member Forum taking place at Portland State University on July 25. We look forward to seeing many of you there! As a reminder, the Forum will be held on Tuesday, July 25, at the Smith Memorial Student Union on the campus of Portland State University from 9:00 a.m. to 5:30 p.m. The Member Forum is a chance for all interested staff of ArchivesSpace member institutions to share and learn about experiences implementing, using, and developing for ArchivesSpace. The preliminary schedule is available on our wiki, with more details to come. This is a free event. You may attend the full day, or just part. While registration will continue to be open through the day before the event, we kindly request that all who plan to be there complete the online registration once you know you're coming in order for us to plan appropriately. Due to limited space and the need to prepare materials for the two afternoon workshops, you must preregister if you'd like to attend one of these. Ways you can participate: * Register to attend the Member Forum at https://www.eventbrite.com/e/archivesspace-member-forum-2017-registration-34624388478 * Volunteer to speak in the concluding lightning round on ArchivesSpace Tips, Tricks and Ideas or share your insights in the ArchivesSpace Community/Ask an Expert session (just email me to volunteer) * Suggest topics you'd like addressed in the Program update by emailing me, starting a discussion on the Users Group listserv, or commenting on the wiki page. We look forward to seeing many of you there in person! We also hope to livestream and record some portions of the program for those who can't be in Portland, and will have more information about that available soon. Christine On behalf of the planning group for the ArchivesSpace Member Forum 2017 Lisa Calahan, University of Minnesota Johanna Carll, Harvard University Celia Caust-Ellenbogen, Swarthmore College Maggie Hughes, UCLA Sue Luftschein, University of Southern California Jaime Margalotti, University of Delaware Jenny Mitchell, Louisiana State University Elizabeth Russell, University of Maine Linda Sellars, North Carolina State University Mariella Soprano, Caltech Kelly Spring, UC Irvine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 5872 bytes Desc: image001.jpg URL: From ldfs at umn.edu Tue Jun 27 16:28:56 2017 From: ldfs at umn.edu (Lara Friedman-Shedlov) Date: Tue, 27 Jun 2017 15:28:56 -0500 Subject: [Archivesspace_Users_Group] Display of punctuation in PUI Message-ID: I was sure I had seen a JIRA issue for this a while back, but now I can't find it. We have thousands of finding aids imported from EAD that have punctuation (commas and periods) at the end of the unittitle and/or unitdate fields. Since ArchivesSpace automatically inserts commas between unittitles and unitdates, you end up with double punctuation. Rather than edit thousands and thousands of records to remove this superfluous punctuation, is there a way for ASpace to just ignore it? Please say yes! :-) / Lara Friedman-Shedlov -- _________________________________ Lara D. Friedman-Shedlov Kautz Family YMCA Archives | University of Minnesota Libraries ldfs at umn.edu | 612.626.7972 | [image: www.facebook.com/IHRCA] [image: https://twitter.com/yarchives] -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at eservices.virginia.edu Tue Jun 27 17:31:10 2017 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 27 Jun 2017 21:31:10 +0000 Subject: [Archivesspace_Users_Group] Display of punctuation in PUI In-Reply-To: References: Message-ID: <4F834578-FE3D-481F-9CF4-01366328D127@eservices.virginia.edu> May be able to be fixed in EAD import. Or, perhaps added to pre-flight schematrons and fixed in XSLT before import, since there are already a number of required fixes. But that would be too late to fix resources you?ve already imported. Those, you can fix it in MySQL with something like: select count(*) from archivesspace.archival_object WHERE title LIKE '%,,%'; SET SQL_SAFE_UPDATES=0; UPDATE archivesspace.archival_object SET title = REPLACE(title, ',,', ',') WHERE title LIKE '%,,%'; select count(*) from archivesspace.archival_object WHERE title LIKE '%,,%'; except repeat the archival_object.title update for archival_object.display_string, resource.title, accession.title, and accession.display_string as needed. ( I think that's all of them. ) May require triggering a reindex afterwards. Note: I find too many false positives using regex search rlike: display_string rlike "[.,;],? i.e. strings with an abbrev., : ?? U.S. Commissioners, et.al., 1931-56;? or "Photographs, India, Thomas Gampper, M.D., undated? . And searching for double periods ( like ?%..%? ) mostly brings up intended ellipses in my sample, so if you want to try any other patterns, you should inspect the search results first. The above is all assuming that the problem is in the database and not just some display string constructed on the fly. I?ve found some matching ?,,? instances in my sample, so that?s my guess at the source of the problem. However, I have no way to search display only instances other than by eyeball. ( Reminds me of the joke about the drunk looking for his keys under the streetlight! ;-) ? Steve Majewski On Jun 27, 2017, at 4:28 PM, Lara Friedman-Shedlov > wrote: I was sure I had seen a JIRA issue for this a while back, but now I can't find it. We have thousands of finding aids imported from EAD that have punctuation (commas and periods) at the end of the unittitle and/or unitdate fields. Since ArchivesSpace automatically inserts commas between unittitles and unitdates, you end up with double punctuation. Rather than edit thousands and thousands of records to remove this superfluous punctuation, is there a way for ASpace to just ignore it? Please say yes! :-) / Lara Friedman-Shedlov -- _________________________________ Lara D. Friedman-Shedlov Kautz Family YMCA Archives | University of Minnesota Libraries ldfs at umn.edu | 612.626.7972 | [www.facebook.com/IHRCA] [https://twitter.com/yarchives] _______________________________________________ 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 jrowe at sebts.edu Wed Jun 28 09:32:50 2017 From: jrowe at sebts.edu (Rowe, Jayson) Date: Wed, 28 Jun 2017 13:32:50 +0000 Subject: [Archivesspace_Users_Group] LDAP Configuration Woes Message-ID: Hi, I'm new to setting up ArchivesSpace, and I'm having trouble getting it to bind to my LDAP. I'm getting two errors, one is a code 49 saying Invalid Credentials (which I know are correct) and then it says failed to bind to LDAP directory. Here is what my LDAP config block looks like (scrubbed a bit for privacy): AppConfig[:authentication_sources] = [{ :model => 'LDAPAuth', :hostname => 'dc.example.com', :port => 389, :base_dn => 'dc=blah,dc=example',dc=blahblah' :username_attribute => 'SAMAccountName', :attribute_map => {:cn => :name}, :bind_dn => 'sAMAccountName=ldapuser,ou=users,dc=blah,dc=example,dc=blahblah', :bind_password => 'secretpassword', }] This is a configuration similar to what other apps use. The only line that was really unfamiliar to us was the ':attribute_map=>' line. I'm grateful for any help the community might be able to provide. Thank you, Jayson Rowe Southeastern Baptist Theological Seminary Jayson Rowe Software Developer, Information Technology Editor, Between The Times Southeastern Baptist Theological Seminary 919.761.2267 | www.sebts.edu | map | social [http://mailer.sebts.edu/admin/images/SEBTS-logo-email.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Wed Jun 28 11:00:28 2017 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 28 Jun 2017 15:00:28 +0000 Subject: [Archivesspace_Users_Group] LDAP Configuration Woes In-Reply-To: References: Message-ID: Hi Jason, I've found the settings that seem to be hard to dial in are the bind_dn / base_dn and sometimes port / encryption. I just checked ours here (we have just a few that are using LDAP) and we've not had to change up attribute_map for anyone. Usually base_dn was something like '"dc=example,dc=edu"' for something like example.edu bind_dn seems to vary widely, from a simple bind at example.edu to something like '"CN=Aspace Bind,OU=Misc,DC=example,DC=edu"' Blake Carver Systems Administrator, LYRASIS ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Rowe, Jayson Sent: Wednesday, June 28, 2017 9:32:50 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] LDAP Configuration Woes Hi, I?m new to setting up ArchivesSpace, and I?m having trouble getting it to bind to my LDAP. I?m getting two errors, one is a code 49 saying Invalid Credentials (which I know are correct) and then it says failed to bind to LDAP directory. Here is what my LDAP config block looks like (scrubbed a bit for privacy): AppConfig[:authentication_sources] = [{ :model => 'LDAPAuth', :hostname => 'dc.example.com', :port => 389, :base_dn => 'dc=blah,dc=example',dc=blahblah? :username_attribute => 'SAMAccountName', :attribute_map => {:cn => :name}, :bind_dn => 'sAMAccountName=ldapuser,ou=users,dc=blah,dc=example,dc=blahblah', :bind_password => 'secretpassword', }] This is a configuration similar to what other apps use. The only line that was really unfamiliar to us was the ?:attribute_map=>? line. I?m grateful for any help the community might be able to provide. Thank you, Jayson Rowe Southeastern Baptist Theological Seminary Jayson Rowe Software Developer, Information Technology Editor, Between The Times Southeastern Baptist Theological Seminary 919.761.2267 | www.sebts.edu | map | social [http://mailer.sebts.edu/admin/images/SEBTS-logo-email.png] From christine.dibella at lyrasis.org Wed Jun 28 11:37:11 2017 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 28 Jun 2017 15:37:11 +0000 Subject: [Archivesspace_Users_Group] seeking volunteers from Very Small and Small institutions for ArchivesSpace staff interface enhancement working group Message-ID: Hello ArchivesSpace members, Thanks to all who have volunteered so far to participate in the member working group for enhancing the staff interface of ArchivesSpace. Lydia and I are gratified that the response to the call for participants has been so strong. We're especially encouraged because this means that the work of this big effort can be structured in a way that allows people with varying availability or different levels of experience to work on activities that are particularly meaningful to them. More details will be forthcoming in July. Before the overall call closes on Friday, I wanted to put in a particular plea for people who work in Very Small and Small member institutions to join. If you work in a smaller institution and are at all interested in this effort for the staff interface, please get in touch. If you have concerns about the time commitment or level of experience needed, I'd be very happy to discuss them. Given the significance of the staff interface to people's experience using ArchivesSpace, it's very important to us that reexamining it be a representative effort. Thanks for your consideration! Christine From: archivesspace_tac_uac-bounces at lyralists.lyrasis.org [mailto:archivesspace_tac_uac-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Wednesday, June 14, 2017 10:11 AM To: Archivesspace Users Group ; Archivesspace Member Reps ; archivesspace_tac_uac at lyralists.lyrasis.org Cc: ArchivesSpace Board of Trustees mail list Subject: [Archivesspace_tac_uac] call for participants in ArchivesSpace staff interface enhancement working group Hello ArchivesSpace Members, With the new version of the public user interface nearly complete, we are pleased to announce a member-led project to enhance, streamline, and make the staff interface of the ArchivesSpace software application more accessible. As part of this effort, we are calling for member volunteers to participate in a working group to examine the current staff interface and identify improvements. A fuller description of what we are asking this working group to take on is included below. The Staff Interface Enhancement Working Group will: * Review, in order to de-dupe and enhance where necessary, outstanding JIRA issues submitted by the community over the years regarding the staff interface. * Identify areas of interest not covered by existing JIRA issues. * Identify accessibility gaps in the current staff interface. * Based on the group's research and member feedback, develop organized recommendations for staff interface improvements. * Once finalized, work with the ArchivesSpace Program team and others to use the recommendations as the basis for a comprehensive specification for the look and feel of the next version of the staff interface. Lydia Tang of Michigan State University has graciously agreed to chair the working group. If you are interested in participating as a member of the group, please let me know through a direct reply to this message, by Friday, June 30. We are looking for broad participation across the different sizes and types of organizations that use ArchivesSpace. In addition to the working group itself, there will be calls for feedback and participation at regular intervals. The first of these will be an in person focus group held in conjunction with the ArchivesSpace Member Forum in Portland on July 25. This will by no means be the last opportunity to give feedback, but we anticipate that it will help us get things off to a great start. Let us know if you have any questions or would like to participate. I look forward to working with Lydia and all of you on this important endeavor! Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13904 bytes Desc: image001.jpg URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From bmg17 at psu.edu Wed Jun 28 13:52:00 2017 From: bmg17 at psu.edu (Ben Goldman) Date: Wed, 28 Jun 2017 13:52:00 -0400 (EDT) Subject: [Archivesspace_Users_Group] merging/fixing duplicate top containers Message-ID: <825811075.4403712.1498672320466.JavaMail.zimbra@psu.edu> Hello, Without realizing it, we migrated a considerable number of poorly encoded instances into ASpace 1.5 and its new container model. We're trying to figure out how best to deal cases like the one in the screenshot below, where historical practice has found us encoding box and folder numbers in a single instance, with values separated by a slash. Until a merge feature is implemented, it looks like we may have to do this through the API, and I'm wondering if anyone has tackled something similar and can possibly share a solution. Thanks much, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-06-28 at 1.48.32 PM.png Type: image/png Size: 104679 bytes Desc: not available URL: From PGalligan at rockarch.org Wed Jun 28 15:03:00 2017 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Wed, 28 Jun 2017 19:03:00 +0000 Subject: [Archivesspace_Users_Group] merging/fixing duplicate top containers In-Reply-To: <825811075.4403712.1498672320466.JavaMail.zimbra@psu.edu> References: <825811075.4403712.1498672320466.JavaMail.zimbra@psu.edu> Message-ID: <045bf7b7c5df4f3f92265c68c18e5159@RACEX13.ad.rockarchive.org> Ben, So, uh, we had some of the same issue. We generally identified that you need at least one barcode to realistically do it in our case. We have two scripts. 1. This one is for resources where the Box numbers don't restart at 1 every series. It won't work if you have two separate box 1s. We know the script is a little messy, but we haven't had the chance to test a refactor. It basically matches based on logic around our barcodes. You could change this to match around other logic as necessary. Like you might be able to split your indicators and match based off of those. We did barcodes because we had faux codes after migration and it was the easiest way to identify the "real" container. https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asAutoReplaceContainers.py 2. This you can use on resources that restart numbers. It's pretty manual, and you have to create a Csv first, but it gets the job done. https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asReplaceContainers.py There should be documentation in the repo, but let me know if you get stuck. -Patrick Galligan Sent with BlackBerry Work (www.blackberry.com) From: Ben Goldman > Date: Thursday, Jun 29, 2017, 3:52 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] merging/fixing duplicate top containers Hello, Without realizing it, we migrated a considerable number of poorly encoded instances into ASpace 1.5 and its new container model. We're trying to figure out how best to deal cases like the one in the screenshot below, where historical practice has found us encoding box and folder numbers in a single instance, with values separated by a slash. Until a merge feature is implemented, it looks like we may have to do this through the API, and I'm wondering if anyone has tackled something similar and can possibly share a solution. [cid:0adb6e00e3d922e8cd87529d47fe6d5a6e97f6b0 at zimbra] Thanks much, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-06-28 at 1.48.32 PM.png Type: image/png Size: 104679 bytes Desc: Screen Shot 2017-06-28 at 1.48.32 PM.png URL: From bmg17 at psu.edu Thu Jun 29 10:29:54 2017 From: bmg17 at psu.edu (Ben Goldman) Date: Thu, 29 Jun 2017 10:29:54 -0400 (EDT) Subject: [Archivesspace_Users_Group] merging/fixing duplicate top containers In-Reply-To: <045bf7b7c5df4f3f92265c68c18e5159@RACEX13.ad.rockarchive.org> References: <825811075.4403712.1498672320466.JavaMail.zimbra@psu.edu> <045bf7b7c5df4f3f92265c68c18e5159@RACEX13.ad.rockarchive.org> Message-ID: <1298696531.5464714.1498746594478.JavaMail.zimbra@psu.edu> Thanks, Patrick. asReplaceContainers.py looks especially useful in our case. Can you tell me whether it retains Child Type and Child Indicator when it replaces a Top Container? Thanks, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries From: "Galligan, Patrick" To: "Archivesspace Users Group" Sent: Wednesday, June 28, 2017 3:03:00 PM Subject: Re: [Archivesspace_Users_Group] merging/fixing duplicate top containers Ben, So, uh, we had some of the same issue. We generally identified that you need at least one barcode to realistically do it in our case. We have two scripts. 1. This one is for resources where the Box numbers don't restart at 1 every series. It won't work if you have two separate box 1s. We know the script is a little messy, but we haven't had the chance to test a refactor. It basically matches based on logic around our barcodes. You could change this to match around other logic as necessary. Like you might be able to split your indicators and match based off of those. We did barcodes because we had faux codes after migration and it was the easiest way to identify the "real" container. [ https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asAutoReplaceContainers.py | https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asAutoReplaceContainers.py ] 2. This you can use on resources that restart numbers. It's pretty manual, and you have to create a Csv first, but it gets the job done. [ https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asReplaceContainers.py | https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asReplaceContainers.py ] There should be documentation in the repo, but let me know if you get stuck. -Patrick Galligan Sent with BlackBerry Work (www.blackberry.com) From: Ben Goldman < [ mailto:bmg17 at psu.edu | bmg17 at psu.edu ] > Date: Thursday, Jun 29, 2017, 3:52 AM To: Archivesspace Users Group < [ mailto:archivesspace_users_group at lyralists.lyrasis.org | archivesspace_users_group at lyralists.lyrasis.org ] > Subject: [Archivesspace_Users_Group] merging/fixing duplicate top containers Hello, Without realizing it, we migrated a considerable number of poorly encoded instances into ASpace 1.5 and its new container model. We're trying to figure out how best to deal cases like the one in the screenshot below, where historical practice has found us encoding box and folder numbers in a single instance, with values separated by a slash. Until a merge feature is implemented, it looks like we may have to do this through the API, and I'm wondering if anyone has tackled something similar and can possibly share a solution. Thanks much, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries _______________________________________________ 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: Screen Shot 2017-06-28 at 1.48.32 PM.png Type: image/png Size: 104679 bytes Desc: Screen Shot 2017-06-28 at 1.48.32 PM.png URL: From craig.savino at nyu.edu Thu Jun 29 11:00:48 2017 From: craig.savino at nyu.edu (Craig P Savino) Date: Thu, 29 Jun 2017 11:00:48 -0400 Subject: [Archivesspace_Users_Group] Error when deleting location despite no linked records Message-ID: Hello, We have not been able to replicate the following problem in the ASpace test instance, but were wondering if anyone else has run across this problem or may have recommendations in how to resolve it. After merging three separate repositories from Toolkit into ASpace we are left with many legacy locations that we would like to delete. However, in some cases we have run across locations that the system will not let us delete, giving the following error instead: Text of the error is the following: translation missing: en.validation_errors.record_deletion_failed__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__cannot_delete_or_update_a_parent_row__a_foreign_key_constraint_fails_(`asdb`.`housed_at_rlshp`__constraint_`housed_at_rlshp_ibfk_2`_foreign_key_(`location_id`)_references_`location`_(`id`)) I have checked across all three repositories and cannot find any top container records linked to this location (or others which refuse to delete) so I am not sure why we are getting this error. Thanks, *Craig Savino* *Senior Processing Archivist* *Archival Collections Management, NYU* -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cannot delete error.png Type: image/png Size: 72917 bytes Desc: not available URL: From mark.cooper at lyrasis.org Thu Jun 29 11:42:01 2017 From: mark.cooper at lyrasis.org (Mark Cooper) Date: Thu, 29 Jun 2017 15:42:01 +0000 Subject: [Archivesspace_Users_Group] Error when deleting location despite no linked records In-Reply-To: References: Message-ID: Hi Craig, That error appears related to some leftover cruft from the container conversion upgrade. The housed_at_rlshp table is a legacy table related to the legacy container table (not top containers) and location. The v2.1.0 release is under active testing, looking good for July, and removes all of the legacy data so it should resolve things for you (the release candidate is available if you want to test with a copy of your database: https://github.com/archivesspace/archivesspace/releases/download/v2.1.0-RC1/archivesspace-v2.1.0-RC1.zip). Best, Mark Mark Cooper Technical Lead, Hosting and Support LYRASIS email: mark.cooper at lyrasis.org skype: mark_c_cooper ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Craig P Savino Sent: Thursday, June 29, 2017 8:00:48 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Error when deleting location despite no linked records Hello, We have not been able to replicate the following problem in the ASpace test instance, but were wondering if anyone else has run across this problem or may have recommendations in how to resolve it. After merging three separate repositories from Toolkit into ASpace we are left with many legacy locations that we would like to delete. However, in some cases we have run across locations that the system will not let us delete, giving the following error instead: [cid:ii_j4ijtsjx0_15cf4567eaf2f66f] Text of the error is the following: translation missing: en.validation_errors.record_deletion_failed__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__cannot_delete_or_update_a_parent_row__a_foreign_key_constraint_fails_(`asdb`.`housed_at_rlshp`__constraint_`housed_at_rlshp_ibfk_2`_foreign_key_(`location_id`)_references_`location`_(`id`)) I have checked across all three repositories and cannot find any top container records linked to this location (or others which refuse to delete) so I am not sure why we are getting this error. Thanks, Craig Savino Senior Processing Archivist Archival Collections Management, NYU -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cannot delete error.png Type: image/png Size: 72917 bytes Desc: cannot delete error.png URL: From craig.savino at nyu.edu Thu Jun 29 11:46:05 2017 From: craig.savino at nyu.edu (Craig P Savino) Date: Thu, 29 Jun 2017 11:46:05 -0400 Subject: [Archivesspace_Users_Group] Error when deleting location despite no linked records In-Reply-To: References: Message-ID: Mark, Thank you! I had my suspicions that this was something that would get resolved in one of the new updates. - Craig On Thu, Jun 29, 2017 at 11:42 AM, Mark Cooper wrote: > Hi Craig, > > > That error appears related to some leftover cruft from the container > conversion upgrade. The housed_at_rlshp table is a legacy table related > to the legacy container table (not top containers) and location. The v2.1.0 > release is under active testing, looking good for July, and removes all > of the legacy data so it should resolve things for you (the release > candidate is available if you want to test with a copy of your database: > https://github.com/archivesspace/archivesspace/ > releases/download/v2.1.0-RC1/archivesspace-v2.1.0-RC1.zip). > > > Best, > > Mark > > > Mark Cooper > Technical Lead, Hosting and Support > LYRASIS > email: mark.cooper at lyrasis.org > skype: mark_c_cooper > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Craig P Savino > *Sent:* Thursday, June 29, 2017 8:00:48 AM > *To:* Archivesspace Users Group > *Subject:* [Archivesspace_Users_Group] Error when deleting location > despite no linked records > > Hello, > > We have not been able to replicate the following problem in the ASpace > test instance, but were wondering if anyone else has run across this > problem or may have recommendations in how to resolve it. > > After merging three separate repositories from Toolkit into ASpace we are > left with many legacy locations that we would like to delete. However, in > some cases we have run across locations that the system will not let us > delete, giving the following error instead: > > > > Text of the error is the following: > > translation missing: en.validation_errors.record_deletion_failed__java__ > commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolat > ionexception__cannot_delete_or_update_a_parent_row__a_ > foreign_key_constraint_fails_(`asdb`.`housed_at_rlshp`__ > constraint_`housed_at_rlshp_ibfk_2`_foreign_key_(` > location_id`)_references_`location`_(`id`)) > > I have checked across all three repositories and cannot find any top > container records linked to this location (or others which refuse to > delete) so I am not sure why we are getting this error. > > Thanks, > > *Craig Savino* > *Senior Processing Archivist* > *Archival Collections Management, NYU* > > > -- *Craig Savino* *Senior Processing Archivist* *Archival Collections Management* -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cannot delete error.png Type: image/png Size: 72917 bytes Desc: not available URL: From Gregory.Farr at AustenRiggs.net Thu Jun 29 16:01:08 2017 From: Gregory.Farr at AustenRiggs.net (Gregory.Farr at AustenRiggs.net) Date: Thu, 29 Jun 2017 16:01:08 -0400 Subject: [Archivesspace_Users_Group] AUTO: Gregory Farr is out of the office (returning 07/11/2017) Message-ID: I am out of the office until 07/11/2017. Note: This is an automated response to your message "Re: [Archivesspace_Users_Group] merging/fixing duplicate top containers" sent on 6/29/2017 10:29:54 AM. This is the only notification you will receive while this person is away. From PGalligan at rockarch.org Thu Jun 29 19:02:15 2017 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Thu, 29 Jun 2017 23:02:15 +0000 Subject: [Archivesspace_Users_Group] merging/fixing duplicate top containers Message-ID: Ben, Unfortunately it?s a full replacement. It literally takes one top container and replaces it with another, so you?d lose any information from the container being replaced. Unfortunately, this might not be too useful to you if you?re really looking to keep top container information. Sorry ? -Patrick From: on behalf of Ben Goldman Reply-To: Archivesspace Users Group Date: Friday, June 30, 2017 at 12:29 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] merging/fixing duplicate top containers Thanks, Patrick. asReplaceContainers.py looks especially useful in our case. Can you tell me whether it retains Child Type and Child Indicator when it replaces a Top Container? Thanks, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries ________________________________ From: "Galligan, Patrick" To: "Archivesspace Users Group" Sent: Wednesday, June 28, 2017 3:03:00 PM Subject: Re: [Archivesspace_Users_Group] merging/fixing duplicate top containers Ben, So, uh, we had some of the same issue. We generally identified that you need at least one barcode to realistically do it in our case. We have two scripts. 1. This one is for resources where the Box numbers don't restart at 1 every series. It won't work if you have two separate box 1s. We know the script is a little messy, but we haven't had the chance to test a refactor. It basically matches based on logic around our barcodes. You could change this to match around other logic as necessary. Like you might be able to split your indicators and match based off of those. We did barcodes because we had faux codes after migration and it was the easiest way to identify the "real" container. https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asAutoReplaceContainers.py 2. This you can use on resources that restart numbers. It's pretty manual, and you have to create a Csv first, but it gets the job done. https://github.com/RockefellerArchiveCenter/scripts/blob/master/archivesspace/asReplaceContainers.py There should be documentation in the repo, but let me know if you get stuck. -Patrick Galligan Sent with BlackBerry Work (www.blackberry.com) From: Ben Goldman > Date: Thursday, Jun 29, 2017, 3:52 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] merging/fixing duplicate top containers Hello, Without realizing it, we migrated a considerable number of poorly encoded instances into ASpace 1.5 and its new container model. We're trying to figure out how best to deal cases like the one in the screenshot below, where historical practice has found us encoding box and folder numbers in a single instance, with values separated by a slash. Until a merge feature is implemented, it looks like we may have to do this through the API, and I'm wondering if anyone has tackled something similar and can possibly share a solution. [cid:image001.png at 01D2F17F.6A8509D0] Thanks much, Ben Ben Goldman Digital Records Archivist & Sally W. Kalin Early Career Librarian for Technological Innovations Penn State University Libraries _______________________________________________ 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.png Type: image/png Size: 104680 bytes Desc: image001.png URL: From KelliSalmon at rmc.edu Fri Jun 30 10:05:34 2017 From: KelliSalmon at rmc.edu (Salmon, Kelli) Date: Fri, 30 Jun 2017 14:05:34 +0000 Subject: [Archivesspace_Users_Group] Third Party Hosting, Support and Implementation Message-ID: Hi, all. Are there any other third part hosting/support/implementation options other than the 3 listed on the ASpace site? Kelli Salmon Library Systems Administrator & Interlibrary Loan Coordinator McGraw-Page Library, Randolph-Macon College 305 Henry Street Ashland, VA 23005 P (804) 752-3219 C (804) 678-9850 kellisalmon at rmc.edu [RMC-logo-email] Building Extraordinary Futures -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1089 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 8280 bytes Desc: image002.gif URL: From ldfs at umn.edu Fri Jun 30 10:19:18 2017 From: ldfs at umn.edu (Lara Friedman-Shedlov) Date: Fri, 30 Jun 2017 09:19:18 -0500 Subject: [Archivesspace_Users_Group] Display of punctuation in PUI In-Reply-To: <4F834578-FE3D-481F-9CF4-01366328D127@eservices.virginia.edu> References: <4F834578-FE3D-481F-9CF4-01366328D127@eservices.virginia.edu> Message-ID: Thanks, Steve. As you correctly surmised, the EAD files are already imported, so it is too late to use XSLT or otherwise manipulate the files to strip out the punctuation. Our instance of ArchivesSpace is hosted, so I don't think we can try the MySQL approach on our own. Lyrasis would have to help us with that. As I mentioned, I really thought I had seen this (some way for the interface to have a display rule of some kind) in a JIRA as an requested feature. Double periods might be harder to address because of the occasional use of ellipses, but double commas should be easy to screen out and are our biggest issue anyway. On Tue, Jun 27, 2017 at 4:31 PM, Majewski, Steven Dennis (sdm7g) < sdm7g at eservices.virginia.edu> wrote: > > May be able to be fixed in EAD import. > Or, perhaps added to pre-flight schematrons and fixed in XSLT before > import, since there are already a number of required fixes. > > But that would be too late to fix resources you?ve already imported. > > Those, you can fix it in MySQL with something like: > > select count(*) from archivesspace.archival_object WHERE title LIKE '%,,%'; > SET SQL_SAFE_UPDATES=0; > UPDATE archivesspace.archival_object > SET > title = REPLACE(title, ',,', ',') > WHERE > title LIKE '%,,%'; > select count(*) from archivesspace.archival_object WHERE title LIKE '%,,%'; > > > except repeat the archival_object.title update for archival_object.display_string, > resource.title, accession.title, and accession.display_string as needed. ( > I think that's all of them. ) > > May require triggering a reindex afterwards. > > > Note: I find too many false positives using regex search rlike: > display_string rlike "[.,;],? > i.e. strings with an abbrev., : ?? U.S. Commissioners, et.al., 1931-56;? > or "Photographs, India, Thomas Gampper, M.D., undated? . And searching > for double periods ( like ?%..%? ) mostly brings up intended ellipses in my > sample, so if you want to try any other patterns, you should inspect the > search results first. > > > The above is all assuming that the problem is in the database and not just > some display string constructed on the fly. I?ve found some matching ?,,? > instances in my sample, so that?s my guess at the source of the problem. > However, I have no way to search display only instances other than by > eyeball. ( Reminds me of the joke about the drunk looking for his keys > under the streetlight! ;-) > > > > > ? Steve Majewski > > > > > On Jun 27, 2017, at 4:28 PM, Lara Friedman-Shedlov wrote: > > I was sure I had seen a JIRA issue for this a while back, but now I can't > find it. We have thousands of finding aids imported from EAD that have > punctuation (commas and periods) at the end of the unittitle and/or > unitdate fields. Since ArchivesSpace automatically inserts commas between > unittitles and unitdates, you end up with double punctuation. Rather than > edit thousands and thousands of records to remove this superfluous > punctuation, is there a way for ASpace to just ignore it? Please say yes! > :-) > > / Lara Friedman-Shedlov > > -- > _________________________________ > > Lara D. Friedman-Shedlov > Kautz Family YMCA Archives | University of > Minnesota Libraries > ldfs at umn.edu | 612.626.7972 <(612)%20626-7972> | > > [image: www.facebook.com/IHRCA] [image: > https://twitter.com/yarchives] > > _______________________________________________ > 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 > > -- _________________________________ Lara D. Friedman-Shedlov Kautz Family YMCA Archives | University of Minnesota Libraries ldfs at umn.edu | 612.626.7972 | [image: www.facebook.com/IHRCA] [image: https://twitter.com/yarchives] -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at mail.lib.msu.edu Fri Jun 30 16:10:41 2017 From: ltang5 at mail.lib.msu.edu (Tang, Lydia) Date: Fri, 30 Jun 2017 20:10:41 +0000 Subject: [Archivesspace_Users_Group] events question Message-ID: Hi all, In general, I?ve been kind of confused by the Events feature, which I understand was brought over from AT (I used Archon earlier). I see that events automatically are created when migrating Resources between Repositories. I also see that Events can be used for tracking processing, accessions, and a miriade of other functions. I can definitely see the value of keeping track of all of the steps for the collections? care, but I was wondering if it has ever been problematic or unneeded to have so many event records? Is it ever problematic when the event tasks over lap the Collection Management processing information or Accessions? Or to avoid overlapping, should those section within CM or Acessions be broken into connected event records? I just am curious and would love to hear your thoughts! Thanks, Lydia From livsolis at utexas.edu Fri Jun 30 16:43:20 2017 From: livsolis at utexas.edu (Olivia S Solis) Date: Fri, 30 Jun 2017 15:43:20 -0500 Subject: [Archivesspace_Users_Group] "Source" definitions Message-ID: Hello all, We at the Briscoe are in the budding but soon to be live ASpace implementation point. Yay and at last! Documentation and staff training are big priorities for us right now. One thing that I think might be a bit confusing for staff still getting used to the term "Agent" or "Archival Object" is what we mean by "Source". I've noted at least 3 different senses of "source" in ASpace: - Resource/Accession records: Linked agent role ("Source", "Creator", "Subject") - Event record: Record links/role: ("Source", "Transfer", "Outcome") - Names/Subjects: the external authority for the controlled vocab term It actually took a bit of time for me to understand the logic behind the first and last second bullet points above (and I may not fully still, but we've got a system in place). Have any of you struggled with explaining the idea of "source" to staff? Ideally I like to provide definitions for terms, but there are different use cases here. For us, agent link sources will only pop up in accessions, where the agent is a "Source", with a relator of seller (for purchases), former owner (for transfers), or donor (most common). All of our events presume the resource/accession is the source of the event (we're using a number of human-initiated events but our digital repository lies outside of ASpace and so we won't use a lot of the default events). And of course, I'm using "Source" to specify external authorities when entering names and subject terms pulled from VIAF, GeoNames, FAST etc. So far, I've not found definitions for "source" in some other institutions' documentation I've looked at. Has anyone else struggled with this? Has the notion of "source" confused staff? We could provide rote instructions for processors/ etc. to follow that bypass any definition of "source", and perhaps that's all we need.. Has just giving processors steps 1, 2, and 3 been sufficient for your ASpace needs? Thanks! Olivia -- Olivia Solis, MSIS Metadata Coordinator Dolph Briscoe Center for American History The University of Texas at Austin 2300 Red River St. Stop D1100 Austin TX, 78712-1426 (512) 232-8013 <(512)%20232-8013> -------------- next part -------------- An HTML attachment was scrubbed... URL: