From gordon_daines at byu.edu Thu Mar 1 13:06:48 2018 From: gordon_daines at byu.edu (Gordon Daines) Date: Thu, 1 Mar 2018 18:06:48 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace User Advisory Council Message-ID: The ArchivesSpace Governance Board is seeking nominations to fill 8 vacancies on the ArchivesSpace User Advisory Council (UAC). Nominees should be presently employed at an ArchivesSpace member institution in any member category (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). Nominations may be made only by ArchivesSpace member representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities projected for UAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Friday, April 15, 2018. The Nominations Committee will review all nominations and recommend appointments to the Governance Board for approval. UAC (http://www.archivesspace.org/usersadvisory) is a critical part of the ArchivesSpace community, serving as a communication conduit between ArchivesSpace governance groups and ArchivesSpace users. It is also the group that implements and contributes to ArchivesSpace user services. Some of the activities UAC is currently engaged in are: * liaising with national and regional archives organizations; * soliciting, suggesting, gathering requirements for, and prioritizing enhancements to the ArchivesSpace application; * maintaining and updating user documentation, as needed, of the ArchivesSpace application; * developing and providing training to users; and * advising the Governance Board and LYRASIS on the design and delivery of user services, including but not limited to help desk support, training, and presentation of documentation. Sub-groups will be established within UAC to address the areas identified above, as well as other activities identified subsequently. Nominees will be appointed to UAC according to their ability to participate in and lead some of the activities mentioned above. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service will be July 1, 2018-June 30, 2020. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2020-June 30, 2022. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please identify the person and her/his organization in the form below, indicate the areas of activity to which the nominee is prepared to contribute. Again, self nominations are welcome. Return the completed form via email to ArchivesSpace Program Manager (Christine Di Bella) at christine.dibella at lyrasis.org, who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Friday, April 15, 2018. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: J. Gordon Daines III, Brigham Young University Chair, and Governance Board member Suzanne Stasiulatis, Pennsylvania Historical and Museum Commission, Chair of User Advisory Council Max Eckard, University of Michigan, Chair of Technical Advisory Council Jordon Steele, Johns Hopkins University, representing very large membership level Amanda Focke, Rice University, representing large membership level Amanda Lanthorne, San Diego State Universtiy, representing medium membership level Rebekah Irwin, Middlebury College, representing small membership level Dylan McDonald, Center for Sacramento History, representing very small membership level Christine Di Bella, (ArchivesSpace Program Manager), ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___Documentation ___Liaising with archives organizations. Please indicate the organizations: _____________________ ___New features, functional or technical specifications ___Training, design ___Training, provision ___ Usability testing ___User/Help support -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Thu Mar 1 13:13:34 2018 From: gordon_daines at byu.edu (Gordon Daines) Date: Thu, 1 Mar 2018 18:13:34 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Technical Advisory Council Message-ID: <503b981ca5e34008b2a7c71129016ab8@MB7.byu.local> The ArchivesSpace Governance Board is seeking nominations to fill 7 vacancies on the ArchivesSpace Technical Advisory Council (TAC). Nominees should be presently employed at an ArchivesSpace member institution (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). They may also be employees of a current Registered Service Provider (see: http://archivesspace.org/registered-service-providers/current-rsps/). Nominations may be made only by ArchivesSpace member representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities assigned to TAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Friday, April 15, 2018. The Nominations Committee will review all nominations and recommend appointments to the Governance Board for approval. TAC (http://www.archivesspace.org/technicaladvisory) is a critical part of the ArchivesSpace community, having responsibility for providing technical guidance to individuals or organizations contributing to application development, to the User Advisory Council, and to the ArchivesSpace Governance Board. TAC's current activities include: * developing a community of code committers, including helping to establish guidelines for contributing code and reviewing contributions, * reviewing enhancements and priorities and testing in collaboration with the User Advisory Council, * providing support for migrating data to ArchivesSpace from other systems and support for importing and exporting data such as EAD, MARCXML, CSV * documenting and assisting with resolving bugs identified in the application, * identifying integration points for ArchivesSpace with other systems (e.g. digital asset management systems, patron and request management systems, etc.), creating resources to assist the community with integration work and, for specific integrations, developing technical requirements, and * updating technical documentation. Sub-teams will be established within TAC to address the areas identified above, as well other activity areas identified subsequently. Nominees must have sufficient knowledge of application development methods, architectures and coding practices to participate in and lead some of the identified activities. Nominees with experience in open source projects, developing web applications (particularly using Ruby on Rails and Sinatra), software testing, or interest in those areas, are especially welcome. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service will be July 1, 2018-June 30, 2020. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2020-June 30, 2022. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please identify the person and her/his organization in the form below, indicate the areas of activity to which the nominee is prepared to contribute. Again, self nominations are welcome. Return the completed form via email to ArchivesSpace Program Manager (Christine Di Bella) at christine.dibella at lyrasis.org, who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Friday, April 15, 2018. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: J. Gordon Daines III, Brigham Young University Chair, and Governance Board member Max Eckard, University of Michigan, Chair of Technical Advisory Council Suzanne Stasiulatis, Pennsylvania Historical and Museum Commission, Chair of User Advisory Council Jordon Steele, Johns Hopkins University, representing very large membership level Amanda Focke, Rice University, representing large membership level Amanda Lanthorne, San Diego State Universtiy, representing medium membership level Rebekah Irwin, Middlebury College, representing small membership level Dylan McDonald, Center for Sacramento History, representing very small membership level Christine Di Bella, (ArchivesSpace Program Manager), ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___Managing/endorsing/eliciting code contributions ___Bug fixes ___Technical documentation ___Program architecture and integrations with other software ___Migration issues, including import/exports and API design and implementation ___Application testing -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Thu Mar 1 13:23:31 2018 From: gordon_daines at byu.edu (Gordon Daines) Date: Thu, 1 Mar 2018 18:23:31 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Governance Board Message-ID: <63729c50c395404f8cc33c32be68fa80@MB7.byu.local> As chair of the ArchivesSpace Nominating Committee, I am writing to seek your nominations of candidates to stand for election for the ArchivesSpace Governance Board representing the Very Large and Small membership levels. Member engagement is critical to the success of ArchivesSpace, and the Board relies upon your recommendations for strong candidates. Even if you represent a different category of membership, please consider colleagues you know at other institutions. Only ArchivesSpace members representatives may submit nominations. All other staff of ArchivesSpace member organizations must submit nominations through their Member Representative. All Member Representatives are strongly encouraged to consult with all interested colleagues within their organization to solicit recommendations for nominees. Self-nominations are also welcome if you represent a Very Large or Small member institution. To submit nominations, send names and the institutional affiliation for each, indicating whether or not you have contacted the nominee, so that a member of the nominating committee can follow up with the nominee accordingly to confirm interest. Self-nominees can simply indicate their interest. Nominees who confirm their interest in standing for election will be requested to supply a formal candidate statement outlining their qualifications for serving on the ArchivesSpace Governance Board (see: http://archivesspace.org/about/governance-board-and-councils/). Nominations must be received by 9:00 p.m. EDT Friday, April 15, 2018. They should be sent to ArchivesSpace Program Manager ArchivesSpace Program Manager (Christine Di Bella) at christine.dibella at lyrasis.org, who will collect nominations on behalf of the Nominating Committee. The Nominating Committee will review all nominations and confirm a slate of nominees with the current Governance Board. An election ballot will be circulated to member institutions in mid-May. The current incumbents at the Very Large and Small membership levels are not standing re-election as representatives to the Governance Board. The terms for their successors will be July 1, 2018-June 30, 2021. Each newly elected member representative will be eligible to run for a second term, July 1, 2021-June 30, 2024. Nominees must be currently employed by an ArchivesSpace member organization in either the Very Large or Small member levels (see the member lists at: http://archivesspace.org/community/whos-using-archivesspace/). Nominees should have administrative and fiscal oversight experience, characteristics typical of director or associate director level staff. The Governance Board is charged with providing oversight for the ArchivesSpace application and community, including fiscal oversight, the approval of development priorities, and oversight of the Technical and User Advisory councils. To meet the needs of a broad and diverse membership in a balanced and equitable way, the Governance Board is composed of twelve members, including: 9 voting members: 5 elected members, one from each of the five membership categories; 3 standing members, one representing each of the three original project partners (New York University, UC San Diego, and the University of Illinois, Urbana-Champaign); and 1 member representing the LYRASIS management team. 3 ex officio members: ArchivesSpace Program Manager, LYRASIS Director of Collection Services and Community Supported Software, and 1 member of the LYRASIS Board of Directors. Please feel free to contact me or any member of our Nominating Committee with any questions. Again, nominations should be sent to ArchivesSpace Program Manager (Christine Di Bella) at christine.dibella at lyrasis.org. All nominations must be received by April 15, 2018. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: J. Gordon Daines III, Brigham Young University Chair, and Governance Board member Max Eckard, University of Michigan, Chair of Technical Advisory Council Suzanne Stasiulatis, Pennsylvania Historical and Museum Commission, Chair of User Advisory Council Jordon Steele, Johns Hopkins University, representing very large membership level Amanda Focke, Rice University, representing large membership level Amanda Lanthorne, San Diego State Universtiy, representing medium membership level Rebekah Irwin, Middlebury College, representing small membership level Dylan McDonald, Center for Sacramento History, representing very small membership level Christine Di Bella, (ArchivesSpace Program Manager), ex officio -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Thu Mar 1 14:14:32 2018 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 1 Mar 2018 19:14:32 +0000 Subject: [Archivesspace_Users_Group] memory issues with reports in v2.3.0 Message-ID: <5448BC5C-7F65-4352-93D5-216D18CC9334@du.edu> Hello, I was curious if anyone else on the list had noticed that reports (and possibly other background jobs) are consuming more memory in v2.3.0 than in previous versions of ArchivesSpace. We?ve noticed that reports that worked for us in 2.2.1 are throwing ?GC overhead limit exceeded? errors since we upgraded. We don?t use any of the default reports; every report we have in our instance is here: https://github.com/duspeccoll/archivesspace_reports. I?m sharing the link in case it?s a problem with our reports, and there are ways I could write them to be more efficient. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Thu Mar 1 14:19:35 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Thu, 1 Mar 2018 19:19:35 +0000 Subject: [Archivesspace_Users_Group] Announcement re: It Takes a Village guidebook Message-ID: Hello ArchivesSpace Members, ArchivesSpace is featured in a recent publication from the IMLS-funded "It Takes a Village" project about Open Source Software programs. Some information from the press release is below. LYRASIS is proud to announce the release of the Open Source Software Sustainability Guidebook as the culmination of the "It Takes a Village" project. The Guidebook is designed to serve as a practical reference source to help open source software programs serving cultural and scientific heritage organizations plan for long-term sustainability. This project was made possible in part by the Institute of Museum and Library Services - Grant LG-73-17-0005-17; LYRASIS appreciates their support. The full press release is available at: http://lyrasisnow.org/press-release-itav-guidebook/ and the guidebook is available at https://www.lyrasis.org/technology/Pages/IMLS-OSS.aspx. Laurie Gemmill Arp, Director, Collections Services & Community Supported Software at LYRASIS, was the co-director (along with CollectionSpace Program Manager Megan Forbes) for the project. Several people represented ArchivesSpace including Program Manager Christine Di Bella, Technical Lead Laney McGlohon and David Millman from NYU. Christine also contributed a case study for the guidebook about ArchivesSpace community engagement and its growth over the years. Being participants in an open source software program yourselves, we thought you may enjoy learning more about how these programs address common challenges and thinking about the opportunities for collaboration that our involvement in such a project may provide in the future. If you have any questions, feel free to direct them to Laurie or Christine. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bobbi_fox at harvard.edu Thu Mar 1 15:55:34 2018 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Thu, 1 Mar 2018 20:55:34 +0000 Subject: [Archivesspace_Users_Group] V2.3.1: Did we lose the resource boost on search relevancy? Message-ID: Hi, We just installed v2.3.1 (setting AppConfig[:solr_params] = { "q.op" => "AND" } It looks as though we no longer have the boost on search relevancy so that Resources get ranked higher than items on a search. Is anyone else experiencing this? Do we have to add more key/value pairs to AppConfig[:solr_params] ? Thanks, Bobbi -------------- next part -------------- An HTML attachment was scrubbed... URL: From maderikra at vmi.edu Fri Mar 2 08:15:08 2018 From: maderikra at vmi.edu (Maderik, Rachel A) Date: Fri, 2 Mar 2018 13:15:08 +0000 Subject: [Archivesspace_Users_Group] V2.3.1: Did we lose the resource boost on search relevancy? In-Reply-To: References: Message-ID: We are experiencing this too, Bobbi. This also happens when using the plugin (https://github.com/hudmol/and_search) on previous versions of the PUI (which is why we never implemented it). Rachel Maderik Systems and Technology Librarian 501D Preston Library Virginia Military Institute Lexington, VA 24450 540-464-7572 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Fox, Bobbi Sent: Thursday, March 01, 2018 3:56 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] V2.3.1: Did we lose the resource boost on search relevancy? Hi, We just installed v2.3.1 (setting AppConfig[:solr_params] = { "q.op" => "AND" } It looks as though we no longer have the boost on search relevancy so that Resources get ranked higher than items on a search. Is anyone else experiencing this? Do we have to add more key/value pairs to AppConfig[:solr_params] ? Thanks, Bobbi -------------- next part -------------- An HTML attachment was scrubbed... URL: From smithkr at mit.edu Fri Mar 2 09:22:07 2018 From: smithkr at mit.edu (Kari R Smith) Date: Fri, 2 Mar 2018 14:22:07 +0000 Subject: [Archivesspace_Users_Group] plugin for creating the Next avail Accession number In-Reply-To: <87803952-910E-4599-BAC7-C852FDF4E339@virginia.edu> References: <29F559819ACA9A4FBF208407D4B63ABB0148B3411B@OC11expo28.exchange.mit.edu> <87803952-910E-4599-BAC7-C852FDF4E339@virginia.edu> Message-ID: <29F559819ACA9A4FBF208407D4B63ABB0148B37571@OC11expo28.exchange.mit.edu> Thank you, Steve for your reply! -------------------------------------------------------------------------- Kari R. Smith Institute Archivist and Program Head, Digital Archives Institute Archives & Special Collections, MIT Libraries Massachusetts Institute of Technology, Cambridge, Massachusetts 02139 IASC office: 617.258.5568 http://libraries.mit.edu/archives/ she | her | hers @karirene69 [smithkr at mit.edu] 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: Wednesday, February 28, 2018 5:10 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] plugin for creating the Next avail Accession number I don?t know if it works for current version, but if it doesn?t load, it?s likely the only thing that needs to be changed is the frontend/plugin_init.rb file, to use the new method of loading the routes.rb file: ArchivesSpace::Application.extend_aspace_routes(File.join(File.dirname(__FILE__), "routes.rb")) I have a modified version at: https://github.com/uvalib/generate_accession_identifiers which works under 2.x, which was originally forked from an earlier Yale version, but has two primary differences: [1] It produced IDs of the form ORGCODE YYYY NNNN where ORGCODE is either the org_code from the repository, or it that is nil, the short repo code for the repository. It keeps a separate sequence counter in the DB for each ORGCODE and YEAR, for example: sequence_name: GENERATE_ACCESSION_IDENTIFIER_ViU_2018 [2] It tries to work with the user_pref[?default_values?] setting to enable or disable automatic generation. It has worked fine for us, with one occasional source of confusion. Because this setting can have 3 values ( true, false, nil ) but the checkbox in the UI can only represent 2 values ( false and nil both map to unchecked ), it can sometimes be unclear whether or not it is enabled. This is something that needs to be fixed in the staff UI. If you have other use of the ?Pre-populate Records? setting, you may have a conflict as you cannot enable or disable the different fields or use-cases separately. ( I just added a further note to the README to try to explain this issue: ) This plugin is engaged by the pre-populate-records preference setting. ( preferences/defaults/default_values = true ) If default_values is false or unset (nil), then plugin will not generate accession ids. In the staff UI, this is labeled as 'Pre-populate Records?' with a checkbox for boolean values. This can be set on a User,Repository or Global basis. Note that because the value can have 3 possible settings ( true, false, nil ), but the checkbox can represent only 2 values, there can be some confusion over whether a value is unset (nil), which cause it to fallthru to the next level of settings, or false, which causes it to return false. ? Steve Majewski On Feb 28, 2018, at 2:28 PM, Kari R Smith > wrote: Hi group, Can someone tell me if the plug-in for Accessions that automatically creates the next avail accession number (given local standards) has been updated for 2.3.x? I?d like to have that implemented for our installation but am not sure which plug-in version (where to get the code) is current. Thanks for pointers and help with this! Kari -------------------------------------------------------------------------- Kari R. Smith Institute Archivist and Program Head, Digital Archives Institute Archives & Special Collections, MIT Libraries Massachusetts Institute of Technology, Cambridge, Massachusetts 02139 IASC office: 617.258.5568 http://libraries.mit.edu/archives/ she | her | hers @karirene69 [smithkr at mit.edu] _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From blerette at harpercollege.edu Mon Mar 5 13:09:25 2018 From: blerette at harpercollege.edu (Bridget Lerette) Date: Mon, 5 Mar 2018 18:09:25 +0000 Subject: [Archivesspace_Users_Group] Digital Records Management In-Reply-To: <044947CE0BE7024EA984BC6AADBDE47811623AD6@admmbxs2.admdom.harpercollege.edu> References: <044947CE0BE7024EA984BC6AADBDE47811623AD6@admmbxs2.admdom.harpercollege.edu> Message-ID: <044947CE0BE7024EA984BC6AADBDE47811623E53@admmbxs2.admdom.harpercollege.edu> Dear colleagues, I am writing to find out what other institutions are using to handle their digital objects in conjunction with ArchivesSpace. I am interested in knowing what software is available for this type of work and how it may (or may not) be working for your institution. If you aren't using a software, do you have a dedicated server for the archives? What size? Any feedback would be greatly appreciated. Thank you, Bridget Lerette Archivist Harper College 1200 W. Algonquin Rd. Palatine, IL 60067 blerette at harpercollege.edu harpercollege.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory_nimer at byu.edu Tue Mar 6 12:33:56 2018 From: cory_nimer at byu.edu (Cory Nimer) Date: Tue, 6 Mar 2018 17:33:56 +0000 Subject: [Archivesspace_Users_Group] Problem with Classifications: searching/adding to records In-Reply-To: References: Message-ID: <30f7ef3edfa44a698230a93c5cf0ea00@MB7.byu.local> Carrie, We are currently looking at transitioning away from repositories in ArchivesSpace, and using classifications in a similar manner to what you described. In testing this, however, we are seeing similar delays in loading times in our 1.5.4 installation. I recently reported this as a bug in JIRA (https://archivesspace.atlassian.net/projects/ANW/issues/ANW-652), but wondered if you were ever able to get this addressed or resolved? Best, Cory Nimer University Archivist Brigham Young University 801-422-6091 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of carrie.daniels at louisville.edu Sent: Monday, July 17, 2017 7:27 AM To: Archivesspace_Users_Group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Problem with Classifications: searching/adding to records We have been having a problem with Classifications for quite some time - we are currently in version 1.5.2, but I think the issue actually predates our move to 1.5.2 and it's just finally gotten exasperating. And we did some testing on 2.1.0-RC1, and it persists. In our workflow, every Accession and Resource record is assigned a Classification. When adding a Classification to the Accession/Resource record, AS takes a long time to search/find Classifications, particularly the one with (by far) the most records associated with it (about 3300). Saving is also very slow (slow enough that the browser can tell us as the percentage uploaded increases). We've monitored the system while going through these processes, and Java is working overtime during the search process. Has anyone else seen this? And/or have ideas as to how we can fix it? Thanks! Carrie Carrie Daniels University Archivist and Director, Archives and Special Collections University of Louisville -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcallahan at smith.edu Thu Mar 8 09:39:11 2018 From: mcallahan at smith.edu (Maureen Callahan) Date: Thu, 8 Mar 2018 09:39:11 -0500 Subject: [Archivesspace_Users_Group] shared top containers Message-ID: Hi folks, Someone at another library reached out for advice about "sharing" top containers across different resource records. I have a feeling that this may be a common question, so I thought I would share my response. MC Thanks for reaching out -- I know that ArchivesSpace adoption can be complicated! Yes, one of the explicit requirements of the container management model was to allow for shared containers. More information about that work is here: https://guides.library.yale.edu/archivesspace/ASpaceCo ntainerManagement. Here's how I think about it, which is helpful to me. Each top container has its own record in the database, and can be linked to any resource, accession, or archival object in your repository. In the same way that your resource records can share subject headings, they can also share top containers -- and in the same way that if you create a subject heading once, you don't have to create it again, the same thing is true for when you tell ArchivesSpace about a particular box on your shelf. So let's say that you have decided that you're going to put all panoramic photos, regardless of collection, in the same oversize box. The first time you have a panoramic photo in a finding aid, you would create a top container to assign it to. You can give it a container indicator (like "1" or "Oversize 1" or whatever you want), a container profile (information about the dimensions of the box itself, if you want) and a barcode. I am a big fan of barcodes, because they help give every container a truly unique indicator that you can then search by and retrieve. I've created an example here: http://sandbox.archivesspace.org/resources/1# tree::archival_object_11 . The credentials for the sandbox are admin/admin. Now, you're working on a finding aid for another collection and you come across another panoramic photograph and it lives in the same box as the one you encountered before. This time, you create the archival object, and when it's time to add a top container you go to "browse" instead of "create". This gives you a search box. If your box has a barcode, you can just wand that in and it's the easiest thing in the world. Otherwise, you will have to do a search for other resource records that point to the shared box so that you can find it and link to it. I've created an example of the same top container in a second collection here: http://sandbox.archivesspace.org/resources/2#tree::archival_object_12 Here, you can see the ways that ArchivesSpace tells you that these two objects are in the same top container: http://sandbox.archivesspace.org/top_ containers/7 And I think that's it! -- Maureen Callahan Sophia Smith Collection Archivist Smith College Special Collections Northampton, Massachusetts 01063 T. 413 585 2981 C. 215.863.1860 mcallahan at smith.edu Pronouns: she/her/hers Facebook: https://www.facebook.com/SophiaSmithCollection/ Instagram: https://www.instagram.com/smithlibraries/ Twitter: https://twitter.com/archivalagents *Please note*. Smith College Special Collections is now housed at Young Library . Learn more about renovations to Neilson Library here . -------------- next part -------------- An HTML attachment was scrubbed... URL: From jazairi at bc.edu Thu Mar 8 11:05:03 2018 From: jazairi at bc.edu (Adam Jazairi) Date: Thu, 8 Mar 2018 11:05:03 -0500 Subject: [Archivesspace_Users_Group] Editing linked agent roles Message-ID: Hi all, I was going to create a new value for the Linked Agent Role controlled value list, but I saw that the database has disabled the editing of that list. Would it cause problems with the application if I temporarily made Linked Agent Role editable? Thanks, Adam -- Adam Jazairi Digital Library Applications Developer Boston College (617) 552-1404 adam.jazairi at bc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexanderduryee at nypl.org Thu Mar 8 13:33:30 2018 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Thu, 8 Mar 2018 13:33:30 -0500 Subject: [Archivesspace_Users_Group] Editing linked agent roles In-Reply-To: References: Message-ID: Adam, Last year, we temporarily made this list editable to add a new value, suppressed the Source entry, then reset it to being read-only. We haven't encountered any ill effects yet, although we also edited the MARCXML and EAD exporters to account for the new entries. Regards, --Alex On Thu, Mar 8, 2018 at 11:05 AM, Adam Jazairi wrote: > Hi all, > > I was going to create a new value for the Linked Agent Role controlled > value list, but I saw that the database has disabled the editing of that > list. Would it cause problems with the application if I temporarily made > Linked Agent Role editable? > > Thanks, > > Adam > > -- > Adam Jazairi > Digital Library Applications Developer > Boston College > (617) 552-1404 > adam.jazairi at bc.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From jazairi at bc.edu Thu Mar 8 13:43:11 2018 From: jazairi at bc.edu (Adam Jazairi) Date: Thu, 8 Mar 2018 13:43:11 -0500 Subject: [Archivesspace_Users_Group] Editing linked agent roles In-Reply-To: References: Message-ID: Hi Alex, That's good to know. Thanks! Best, Adam On Thu, Mar 8, 2018 at 1:33 PM, Alexander Duryee wrote: > Adam, > > Last year, we temporarily made this list editable to add a new value, > suppressed the Source entry, then reset it to being read-only. We haven't > encountered any ill effects yet, although we also edited the MARCXML and > EAD exporters to account for the new entries. > > Regards, > --Alex > > On Thu, Mar 8, 2018 at 11:05 AM, Adam Jazairi wrote: > >> Hi all, >> >> I was going to create a new value for the Linked Agent Role controlled >> value list, but I saw that the database has disabled the editing of that >> list. Would it cause problems with the application if I temporarily made >> Linked Agent Role editable? >> >> Thanks, >> >> Adam >> >> -- >> Adam Jazairi >> Digital Library Applications Developer >> Boston College >> (617) 552-1404 >> adam.jazairi at bc.edu >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Alexander Duryee > Metadata Archivist > New York Public Library > (917)-229-9590 <(917)%20229-9590> > alexanderduryee at nypl.org > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Adam Jazairi Digital Library Applications Developer Boston College (617) 552-1404 adam.jazairi at bc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From bobbi_fox at harvard.edu Thu Mar 8 13:52:19 2018 From: bobbi_fox at harvard.edu (Fox, Bobbi) Date: Thu, 8 Mar 2018 18:52:19 +0000 Subject: [Archivesspace_Users_Group] Enhanced version of aspace-import-excel: now supporting bulk ingest of Digital Objects Message-ID: Library Technology Services, which supports the Harvard Library, is pleased to announce the availability of new functionality in the aspace-import-excel plugin, available on GitHub at https://github.com/harvard-library/aspace-import-excel . The new functionality allows you to ingest a spreadsheet that will create Digital Objects (and associated Files), and associate each Digital Object with an already-created Archival Object. The user documentation for this new functionality is at https://github.com/harvard-library/aspace-import-excel/blob/master/user_documentation/USER_DOCUMENTATION.md . The additional functionality was created in response to the needs of the Harvard Library archival community, and therefore does not address all cases, and uses, of Digital Objects, but we hope that it may be useful to other archivists in the ArchivesSpace community. Note that this version, v2.1.2 (https://github.com/harvard-library/aspace-import-excel/releases/tag/v2.1.2 ), is only supported for v2.2.2 and higher of ArchivesSpace. Pull requests welcome. If you encounter problems, please create an issue on the GitHub repository. Cheers, Bobbi Fox, Maintainer -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Thu Mar 8 16:15:58 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Thu, 8 Mar 2018 21:15:58 +0000 Subject: [Archivesspace_Users_Group] ASpace Boston Regional Forum - Registration is now open! Message-ID: Join us for the ArchivesSpace Regional Forum in Boston! The regional forums are opportunities for our diverse ArchivesSpace members to meet up more locally to share and learn from each other through workshops, focused discussion sessions, and presentations. Registration is now open! [cid:image002.png at 01D3B6B7.3BD065A0] PROGRAM The specifics continue to be shaped by the working group. The most current information is available on the ArchivesSpace wiki. Morning Program: The morning session will highlight stories and experiences through presentations, discussions, and a lightning round. * Lightning round: Currently accepting submissions! More info here: http://archivesspace.org/boston-regional-forum-lightning-round-proposals/ Afternoon program: The afternoon session will feature a hands on, engaging activity or workshop selected by a community poll provided during registration. (The poll will appear during check-out, and is available until April 3rd. The activity will be selected soon after this date, and will be announced shortly after.) Happy Hour: The day concludes with an optional happy hour nearby. Details will be provided at a later time. REGISTRATION Registration, including the afternoon session poll, is now open: https://www.eventbrite.com/e/archivesspace-regional-forum-boston-2018-tickets-42955347601 QUESTIONS? If you have any questions (or ideas!) related to the regional forums, feel free to email Kim at christine.kim at lyrasis.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 779043 bytes Desc: image002.png URL: From christine.dibella at lyrasis.org Mon Mar 12 10:26:13 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 12 Mar 2018 14:26:13 +0000 Subject: [Archivesspace_Users_Group] Cherry Hill Company working with ArchivesSpace on project to improve visual layout of staff interface Message-ID: Dear ArchivesSpace members, In their recommendations delivered at the end of December, the Staff Interface Enhancement Working Group suggested retaining the services of a professional user experience or design firm to provide additional guidance on the visual layout of the staff interface. I'm pleased to announce that Cherry Hill Company, who worked on the design phase of the public interface project, will be working with us to provide a set of wireframes and a design guide for optimal usability and accessibility of the staff interface. They will be using the recommendations of the group to guide this process, and there will also be opportunities for members to provide feedback at several points along the way. We are aiming to have the final wireframes and design guide delivered by the end of June 2018. I should note that this project is focused on the layout and appearance of the interface, with usability and accessibility as the chief considerations. There are other projects that focus on adding and/or improving functionality in the interface, some of which we anticipate may commence before the visual layout project is complete. If you have any questions, or if you know now that you would like to participate in the feedback process, please get in touch. Thanks especially to the Staff Interface Enhancement Working Group for identifying this as a need, and to all of you that participated in that process. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From christine.dibella at lyrasis.org Mon Mar 12 10:54:41 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 12 Mar 2018 14:54:41 +0000 Subject: [Archivesspace_Users_Group] example finding aids/records for ArchivesSpace visual layout project Message-ID: Hello again, ArchivesSpace members, I'm assembling a test corpus of finding aids and other records for use in the visual layout project with Cherry Hill Company. This data will be useful in helping those we're working with understand the diversity of forms that archival collections and their descriptions and other metadata take and designing to suit a range of needs. Since time is of the essence, I'm focusing on files known to successfully import in any format that ArchivesSpace accepts - EAD finding aids, accessions in CSV format, digital objects in CSV format, or MARCXML records. You can either send me your source files known to import successfully or export records from your ArchivesSpace in EAD or MARCXML and send them my way for this purpose. No record is too small or too big - or too weird - as long as it's something you manage in ArchivesSpace. Since some types of records do not import/export with collection descriptions, examples of ways you use things like classifications, events, and collection management records with your example records, as well as what you include in your repository record, would also be useful. Please limit example records to no more than 5 per type per submitter, please. The intent is to use these records to populate the test instance for this staff interface project and nothing else, but if you're willing for them to be used for any testing purposes, please indicate that when you send them and we may reuse them when other circumstances inevitably come up. If you'd like your example records to be included, please send them to me by Friday, March 23. Thanks for your help! Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From laney.mcglohon at lyrasis.org Mon Mar 12 11:58:20 2018 From: laney.mcglohon at lyrasis.org (Laney McGlohon) Date: Mon, 12 Mar 2018 15:58:20 +0000 Subject: [Archivesspace_Users_Group] Deadline for community pull requests for next release: March 16 Message-ID: <4D07826F-9884-42B4-98C2-9CFB42DE78B2@lyrasis.org> Just a reminder that the deadline by which a pull request needs to be submitted for consideration for the March 2018 release is March 16. Please submit any pull requests no later than the end of your day on March 16. Pull requests submitted after March 16 will be considered for a future release. Please note that submitting a pull request by the deadline does not guarantee that it will go into the next release, but it will help ensure that we have adequate time to review and test it before potentially putting it into a release. In general, the pull request deadline is the third Friday of a month in which a release is scheduled, with occasional exceptions when a release is intended to come out earlier in the month. If you have any questions, please get in touch. Thanks so much for your contributions and your help in making ArchivesSpace better! Laney McGlohon ArchivesSpace Tech Lead laney.mcglohon at lyrasis.org laneymcglohon Skype [cid:image001.jpg at 01D39034.63178020] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6700 bytes Desc: image001.jpg URL: From lynn.moulton at bc.edu Mon Mar 12 13:35:03 2018 From: lynn.moulton at bc.edu (Lynn Moulton) Date: Mon, 12 Mar 2018 13:35:03 -0400 Subject: [Archivesspace_Users_Group] Linking Agents to Archival Objects Message-ID: Good afternoon, Our institution is trying to link some creator names at the level of the archival object for a special project, and we're finding that when there is an Agent attached at that level, it breaks the export-to-PDF function for the resource record. Does anyone have experience with this? Found a work-around? Best, Lynn Moulton Processing Archivist John J. Burns Library Boston College -------------- next part -------------- An HTML attachment was scrubbed... URL: From lynn.moulton at bc.edu Mon Mar 12 14:47:17 2018 From: lynn.moulton at bc.edu (Lynn Moulton) Date: Mon, 12 Mar 2018 14:47:17 -0400 Subject: [Archivesspace_Users_Group] Linking Agents to Archival Objects In-Reply-To: References: Message-ID: A correction: that query should have read "link some subject names" to the archival object. Agents with the role "creator" don't cause a problem, but Agents with the role set to "subject" do. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexanderduryee at nypl.org Tue Mar 13 10:09:20 2018 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Tue, 13 Mar 2018 10:09:20 -0400 Subject: [Archivesspace_Users_Group] Linking Agents to Archival Objects In-Reply-To: References: Message-ID: Lynn, Which version are you encountering this issue on? I tried reproducing this issue on the sandbox ( http://sandbox.archivesspace.org/resources/11/edit#tree::resource_11, username/password are admin/admin), but the PDF didn't cause any issues. Thanks! --Alex On Mon, Mar 12, 2018 at 2:47 PM, Lynn Moulton wrote: > A correction: that query should have read "link some subject names" to the > archival object. Agents with the role "creator" don't cause a problem, but > Agents with the role set to "subject" do. > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsteele at jhu.edu Tue Mar 13 11:52:16 2018 From: jsteele at jhu.edu (Jordon Steele) Date: Tue, 13 Mar 2018 15:52:16 +0000 Subject: [Archivesspace_Users_Group] Slow load time for records with lots of instances Message-ID: Hi, We have an accession record that has over 1300 containers assigned to it in the instance module. The record takes almost 3 minutes to load in the staff interface, the same amount of time if you enter data and save. Sometimes, heavy interaction with this record causes ASpace to crash. We've doubled our memory to mitigate this, but there appears to be a correlation between the amount of instances we have and the slow load time. I'm wondering if anyone else in the community has experienced this and/or if ASpace is aware of this. Thanks! Best, Jordon Jordon Steele Hodson Curator of the University Archives Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 jsteele at jhu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From don.mennerich at nyu.edu Tue Mar 13 12:19:26 2018 From: don.mennerich at nyu.edu (Donald Mennerich) Date: Tue, 13 Mar 2018 12:19:26 -0400 Subject: [Archivesspace_Users_Group] Slow load time for records with lots of instances In-Reply-To: References: Message-ID: Jordan: What version of Aspace are you running? Don Donald R. Mennerich, digital archivist New York University Libraries don.mennerich at nyu.edu (212) 992-6264 On Tue, Mar 13, 2018 at 11:52 AM, Jordon Steele wrote: > Hi, > > > > We have an accession record that has over 1300 containers assigned to it > in the instance module. The record takes almost 3 minutes to load in the > staff interface, the same amount of time if you enter data and save. > Sometimes, heavy interaction with this record causes ASpace to crash. We?ve > doubled our memory to mitigate this, but there appears to be a correlation > between the amount of instances we have and the slow load time. > > > > I?m wondering if anyone else in the community has experienced this and/or > if ASpace is aware of this. > > > Thanks! > > > > Best, > > > > Jordon > > > > Jordon Steele > > Hodson Curator of the University Archives > > Sheridan Libraries > > Johns Hopkins University > > 3400 N Charles St > > Baltimore, MD 21218 > > jsteele at jhu.edu > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From seth.shaw at unlv.edu Tue Mar 13 12:41:07 2018 From: seth.shaw at unlv.edu (Seth Shaw) Date: Tue, 13 Mar 2018 09:41:07 -0700 Subject: [Archivesspace_Users_Group] Index for Staff UI not updating (2.3.1) Message-ID: In our testing of 2.3.1 no new resources are appearing while searching or browsing (either from import or manually using the Staff UI). If a resource has an Agent added it doesn't appear in that Agent's list of related resources. However, all these additions and changes are reflected in the database and resources created before the upgrade still appear in searches Forcing a reindex by deleting "data/indexer_state/" doesn't have any effect. The logs only show one related error that appears during the startup sequence (see attached for the relevant section of the log). Any ideas? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: archivesspace.log.partial Type: application/octet-stream Size: 13857 bytes Desc: not available URL: From jsteele at jhu.edu Tue Mar 13 12:43:46 2018 From: jsteele at jhu.edu (Jordon Steele) Date: Tue, 13 Mar 2018 16:43:46 +0000 Subject: [Archivesspace_Users_Group] Slow load time for records with lots of instances In-Reply-To: References: Message-ID: Oh sorry, meant to mention this: 1.5.4. Best, Jordon Jordon Steele Hodson Curator of the University Archives Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 jsteele at jhu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Donald Mennerich Sent: Tuesday, March 13, 2018 12:19 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Slow load time for records with lots of instances Jordan: What version of Aspace are you running? Don Donald R. Mennerich, digital archivist New York University Libraries don.mennerich at nyu.edu (212) 992-6264 On Tue, Mar 13, 2018 at 11:52 AM, Jordon Steele > wrote: Hi, We have an accession record that has over 1300 containers assigned to it in the instance module. The record takes almost 3 minutes to load in the staff interface, the same amount of time if you enter data and save. Sometimes, heavy interaction with this record causes ASpace to crash. We?ve doubled our memory to mitigate this, but there appears to be a correlation between the amount of instances we have and the slow load time. I?m wondering if anyone else in the community has experienced this and/or if ASpace is aware of this. Thanks! Best, Jordon Jordon Steele Hodson Curator of the University Archives Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 jsteele at jhu.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From seth.shaw at unlv.edu Tue Mar 13 14:01:32 2018 From: seth.shaw at unlv.edu (Seth Shaw) Date: Tue, 13 Mar 2018 11:01:32 -0700 Subject: [Archivesspace_Users_Group] Index for Staff UI not updating (2.3.1) In-Reply-To: References: Message-ID: So, false alarm. This was actually a problem with a local plugin that doesn't work for this version (written for 1.5.4). Thanks to Noah Huffman for directing my attention to the problem's source! On Tue, Mar 13, 2018 at 9:41 AM, Seth Shaw wrote: > In our testing of 2.3.1 no new resources are appearing while searching or > browsing (either from import or manually using the Staff UI). If a resource > has an Agent added it doesn't appear in that Agent's list of related > resources. However, all these additions and changes are reflected in the > database and resources created before the upgrade still appear in searches > > Forcing a reindex by deleting "data/indexer_state/" doesn't have any > effect. > > The logs only show one related error that appears during the startup > sequence (see attached for the relevant section of the log). > > Any ideas? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at lib.msu.edu Tue Mar 13 14:54:39 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Tue, 13 Mar 2018 18:54:39 +0000 Subject: [Archivesspace_Users_Group] "lost" collections after transferring between repositories/upgrades? Message-ID: <70FC88BD-8977-4FD8-ADCA-F5F8676B6285@lib.msu.edu> I?ve noticed some disturbing behavior? I was using a separate Data Entry repository for volunteers and less-trained student workers to add data into ArchivesSpace and then would transfer them into the production server. It seems to me that at some point with our upgrades or somehow, these inventories have been lost(!). There were some times when I would transfer the collections between repositories that the system seemed to time out. I had assumed that the collection eventually made it from one repository to another, but I probably should have checked. Does it seem possible that collections do get lost like this? Additionally, we have some wonky scenarios where collections seem to be ?mostly lost?, but then if I can find a random Top Container, I can edit the record again to have it reindex and show up. It has happened a couple of times! During this time, we were on versions 1.5.3 ? 2.1.1 Anyone else notice this? Thanks! Lydia -- Dr. Lydia Tang, CA, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 From j at minorscience.com Tue Mar 13 15:11:23 2018 From: j at minorscience.com (Jason Loeffler) Date: Tue, 13 Mar 2018 15:11:23 -0400 Subject: [Archivesspace_Users_Group] "lost" collections after transferring between repositories/upgrades? In-Reply-To: <70FC88BD-8977-4FD8-ADCA-F5F8676B6285@lib.msu.edu> References: <70FC88BD-8977-4FD8-ADCA-F5F8676B6285@lib.msu.edu> Message-ID: In 1.5.1 there was a major issue with "losing" connections between repositories and digital objects when digital objects were transferred between repositories. https://archivesspace.atlassian.net/projects/AR/issues/AR-1405 But what you describe may be an indexing issue. Brute force approach, but have you rebuilt the index from scratch? Jason On Tue, Mar 13, 2018 at 2:54 PM, Tang, Lydia wrote: > I?ve noticed some disturbing behavior? I was using a separate Data Entry > repository for volunteers and less-trained student workers to add data into > ArchivesSpace and then would transfer them into the production server. It > seems to me that at some point with our upgrades or somehow, these > inventories have been lost(!). There were some times when I would transfer > the collections between repositories that the system seemed to time out. I > had assumed that the collection eventually made it from one repository to > another, but I probably should have checked. Does it seem possible that > collections do get lost like this? > Additionally, we have some wonky scenarios where collections seem to be > ?mostly lost?, but then if I can find a random Top Container, I can edit > the record again to have it reindex and show up. It has happened a couple > of times! During this time, we were on versions 1.5.3 ? 2.1.1 > Anyone else notice this? Thanks! > Lydia > -- > Dr. Lydia Tang, CA, DMA, MLIS > Special Collections Archivist-Librarian > Philosophy, Aesthetics, and Ethics Bibliographer > Michigan State University Libraries > 366 W. Circle Drive (DB 6) > East Lansing, MI 48824-1048 > Email: ltang5 at msu.edu > Phone: 517-884-8984 > _______________________________________________ > 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 lib.msu.edu Tue Mar 13 15:21:42 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Tue, 13 Mar 2018 19:21:42 +0000 Subject: [Archivesspace_Users_Group] "lost" collections after transferring between repositories/upgrades? In-Reply-To: References: <70FC88BD-8977-4FD8-ADCA-F5F8676B6285@lib.msu.edu> Message-ID: <5CBBF303-BE06-420D-B203-D442171A428E@lib.msu.edu> Thanks for the context, Jason. My IT person loaded a database backup from the summer and I was able to download the collection?s EAD and import it into our production database. Even then, a few random objects showed up and I had to edit and save the collection in order for the Resource record to show up. I think we lost our earlier attached Subjects and Agents but at least we have the inventory. Luckily with only 600 collections, I could check everything else (however tedious), but I would be worried if I had a much larger collection and wouldn?t be able to know what might have been lost! Crisis averted for now. ;) Lydia From: on behalf of Jason Loeffler Reply-To: Archivesspace Users Group Date: Tuesday, March 13, 2018 at 3:11 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] "lost" collections after transferring between repositories/upgrades? In 1.5.1 there was a major issue with "losing" connections between repositories and digital objects when digital objects were transferred between repositories. https://archivesspace.atlassian.net/projects/AR/issues/AR-1405 But what you describe may be an indexing issue. Brute force approach, but have you rebuilt the index from scratch? Jason On Tue, Mar 13, 2018 at 2:54 PM, Tang, Lydia > wrote: I?ve noticed some disturbing behavior? I was using a separate Data Entry repository for volunteers and less-trained student workers to add data into ArchivesSpace and then would transfer them into the production server. It seems to me that at some point with our upgrades or somehow, these inventories have been lost(!). There were some times when I would transfer the collections between repositories that the system seemed to time out. I had assumed that the collection eventually made it from one repository to another, but I probably should have checked. Does it seem possible that collections do get lost like this? Additionally, we have some wonky scenarios where collections seem to be ?mostly lost?, but then if I can find a random Top Container, I can edit the record again to have it reindex and show up. It has happened a couple of times! During this time, we were on versions 1.5.3 ? 2.1.1 Anyone else notice this? Thanks! Lydia -- Dr. Lydia Tang, CA, DMA, MLIS Special Collections Archivist-Librarian Philosophy, Aesthetics, and Ethics Bibliographer Michigan State University Libraries 366 W. Circle Drive (DB 6) East Lansing, MI 48824-1048 Email: ltang5 at msu.edu Phone: 517-884-8984 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From christine.dibella at lyrasis.org Wed Mar 14 09:38:19 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 14 Mar 2018 13:38:19 +0000 Subject: [Archivesspace_Users_Group] Slow load time for records with lots of instances In-Reply-To: References: Message-ID: Dear Jordon, There were changes made in version 2.0.0 to better accommodate resource hierarchies with many components at the same level as well as records with many linked records at the same level. I?d recommend doing a test upgrade to a more recent ArchivesSpace version to see if that improves performance with this type of record. There are still ways that performance could be improved in the application, but given that you?re running a version that is quite a few back at this point, that?s where I?d recommend starting. I think 1300 instances attached to a single accession record (or 1300 top containers attached to a single instance) is likely to be an edge case, no matter what, however. Please feel free to file a JIRA issue about it, though I will admit that accommodating quick loading of such a record may require major refactoring of the ArchivesSpace application and we?d have to weigh the pros and cons and determine the extent to which such a scenario is needed in the community. I?d certainly be interested to hear how common something like this is. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Jordon Steele Sent: Tuesday, March 13, 2018 12:44 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Slow load time for records with lots of instances Oh sorry, meant to mention this: 1.5.4. Best, Jordon Jordon Steele Hodson Curator of the University Archives Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 jsteele at jhu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Donald Mennerich Sent: Tuesday, March 13, 2018 12:19 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Slow load time for records with lots of instances Jordan: What version of Aspace are you running? Don Donald R. Mennerich, digital archivist New York University Libraries don.mennerich at nyu.edu (212) 992-6264 On Tue, Mar 13, 2018 at 11:52 AM, Jordon Steele > wrote: Hi, We have an accession record that has over 1300 containers assigned to it in the instance module. The record takes almost 3 minutes to load in the staff interface, the same amount of time if you enter data and save. Sometimes, heavy interaction with this record causes ASpace to crash. We?ve doubled our memory to mitigate this, but there appears to be a correlation between the amount of instances we have and the slow load time. I?m wondering if anyone else in the community has experienced this and/or if ASpace is aware of this. Thanks! Best, Jordon Jordon Steele Hodson Curator of the University Archives Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 jsteele at jhu.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From christine.dibella at lyrasis.org Wed Mar 14 09:46:30 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 14 Mar 2018 13:46:30 +0000 Subject: [Archivesspace_Users_Group] reminder about how to get member tech support for ArchivesSpace Message-ID: Hi ArchivesSpace members, Because a number of people are new or newly in production, and it never hurts to have a reminder in any case, I wanted to point out the process for obtaining tech support from ArchivesSpace, which is described at http://archivesspace.org/member-area/technical-support/. In short, we have an agreement with LYRASIS Digital Technology Services (DTS) to provide support for members in a range of technical areas, including installation, upgrades, migration troubleshooting, and general technical difficulties. When you need help, we encourage you to post to the Users Group first, both to determine if your problem is being encountered by others and in case your solution can be easily crowdsourced. If you find you need more individualized assistance, please email the program team at ArchivesSpaceHome at lyrasis.org - we'll determine if your issue needs technical help between what Kim, Laney, and I can easily provide in the course of our other activities. If it does, we'll set up a ticket for you and the LYRASIS DTS team will take over from there. We always encourage you to share solutions back with the community, especially if it's something you originally posted about on the listserv, so that everyone benefits. Please note that while there is no limit on the number of requests a member organization may make for assistance, support provided through membership is geared toward helping people learn how to help themselves and there are limits to the complexity of issues that can be addressed. For example, membership does not include hosting, customization, data migration, or intensive data repair. We can provide you with strong guidance in these areas, but we can't undertake the solutions themselves for you. If your issue requires assistance beyond what is possible through membership, we will alert you to this and suggest alternatives. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From jsteele at jhu.edu Wed Mar 14 10:46:13 2018 From: jsteele at jhu.edu (Jordon Steele) Date: Wed, 14 Mar 2018 14:46:13 +0000 Subject: [Archivesspace_Users_Group] Slow load time for records with lots of instances In-Reply-To: References: Message-ID: Christine, Thanks for your reply and suggestions. We?ve got a test of 2.x on a server at the moment, so we?ll see how it performs. Understood about the tradeoffs. Best, Jordon Jordon Steele Hodson Curator of the University Archives Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 jsteele at jhu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Wednesday, March 14, 2018 9:38 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Slow load time for records with lots of instances Dear Jordon, There were changes made in version 2.0.0 to better accommodate resource hierarchies with many components at the same level as well as records with many linked records at the same level. I?d recommend doing a test upgrade to a more recent ArchivesSpace version to see if that improves performance with this type of record. There are still ways that performance could be improved in the application, but given that you?re running a version that is quite a few back at this point, that?s where I?d recommend starting. I think 1300 instances attached to a single accession record (or 1300 top containers attached to a single instance) is likely to be an edge case, no matter what, however. Please feel free to file a JIRA issue about it, though I will admit that accommodating quick loading of such a record may require major refactoring of the ArchivesSpace application and we?d have to weigh the pros and cons and determine the extent to which such a scenario is needed in the community. I?d certainly be interested to hear how common something like this is. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Jordon Steele Sent: Tuesday, March 13, 2018 12:44 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Slow load time for records with lots of instances Oh sorry, meant to mention this: 1.5.4. Best, Jordon Jordon Steele Hodson Curator of the University Archives Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 jsteele at jhu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Donald Mennerich Sent: Tuesday, March 13, 2018 12:19 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Slow load time for records with lots of instances Jordan: What version of Aspace are you running? Don Donald R. Mennerich, digital archivist New York University Libraries don.mennerich at nyu.edu (212) 992-6264 On Tue, Mar 13, 2018 at 11:52 AM, Jordon Steele > wrote: Hi, We have an accession record that has over 1300 containers assigned to it in the instance module. The record takes almost 3 minutes to load in the staff interface, the same amount of time if you enter data and save. Sometimes, heavy interaction with this record causes ASpace to crash. We?ve doubled our memory to mitigate this, but there appears to be a correlation between the amount of instances we have and the slow load time. I?m wondering if anyone else in the community has experienced this and/or if ASpace is aware of this. Thanks! Best, Jordon Jordon Steele Hodson Curator of the University Archives Sheridan Libraries Johns Hopkins University 3400 N Charles St Baltimore, MD 21218 jsteele at jhu.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4074 bytes Desc: image001.jpg URL: From Kevin.Clair at du.edu Wed Mar 14 11:27:28 2018 From: Kevin.Clair at du.edu (Kevin Clair) Date: Wed, 14 Mar 2018 15:27:28 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace integrations with Alma Message-ID: <2EE306C8-7C72-4B08-A6F0-DF123D093127@du.edu> Hello, I wrote a plugin that performs some integrations between ArchivesSpace and our Alma instance: https://github.com/duspeccoll/alma_integrations It takes as input a Resource provided by the user; it looks in the user-defined field we?ve assigned for Alma MMS IDs to see if one exists, then queries the Alma API to determine if there?s a Bibliographic record with that ID, and if so, if there are any Holdings records attached to it. From there the user has the option to push metadata changes from ArchivesSpace out to Alma (via MARC export), and to create new Holdings based on a pre-defined list of location codes we use for Special Collections and Archives materials. If the plugin is creating a new bibliographic record in Alma, it grabs the MMS ID of the new record and adds it to user_defined.string_2 for us. This code is functional but it?s not very pretty; I have plans to eventually clean it up and make it less focused on DU?s specific integration use case (i.e. by allowing a user to configure what field the MMS ID is assigned to). If you?re an ArchivesSpace/Alma shop and don?t mind taking risks, or would like to test it against the Alma sandbox, comments and/or pull requests are welcome! cheers, -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From smithkr at mit.edu Wed Mar 14 11:41:16 2018 From: smithkr at mit.edu (Kari R Smith) Date: Wed, 14 Mar 2018 15:41:16 +0000 Subject: [Archivesspace_Users_Group] Is it possible to export just the Events records? Message-ID: <29F559819ACA9A4FBF208407D4B63ABB0148B4D8DE@OC11expo28.exchange.mit.edu> Hi, I'm interested in exporting the Events (and other non ArchivesSpace events) that can be PREMIS events. Has anyone worked on this yet, or is there a way already to do it? Kari -------------------------------------------------------------------------- Kari R. Smith Institute Archivist and Program Head, Digital Archives Institute Archives & Special Collections, MIT Libraries Massachusetts Institute of Technology, Cambridge, Massachusetts 02139 IASC office: 617.258.5568 http://libraries.mit.edu/archives/ she | her | hers @karirene69 [smithkr at mit.edu] -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Thu Mar 15 08:59:17 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 15 Mar 2018 12:59:17 +0000 Subject: [Archivesspace_Users_Group] FW: [Archivesspace_member_reps] Migrating Data from Eloquent Systems to ArchivesSpace In-Reply-To: References: Message-ID: Hi all, I?m forwarding this for Cheryl from the Member Representatives list in case anyone here has made a move from Eloquent and has suggestions or advice. The program team will also reach out with some ideas. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_member_reps-bounces at lyralists.lyrasis.org On Behalf Of Cheryl Ziegler Sent: Wednesday, March 14, 2018 8:58 PM To: archivesspace_member_reps at lyralists.lyrasis.org Subject: [Archivesspace_member_reps] Migrating Data from Eloquent Systems to ArchivesSpace Hello all, I am under significant time constraints to move my data from Eloquent Systems to ArchivesSpace as my contract with Eloquent is over effective April 30. I was led to believe that my data could be exported in EAD format. Unfortunately, that is not true. I can only export my data into ASCII delimited text format. I am flying blind here and I know there is not an easy "fix." If I need to manually input my records, then I need to start doing that right away. If there is a way to convert ASCII into a workable migration format, then I need advise on how to accomplish that conversion. Some background: earlier in the year, my IT Director told me he had figured out how to do this migration. He has resigned taking that information with him although I am not sure that he actually had figured it out. I am willing to do the work. I just need a process. Thank you, Cheryl Cheryl L. Ziegler, MLIS Director of Library & Archives Union League Club of Chicago 65 W. Jackson Blvd. Chicago, IL 60604 P: 312.435.4818 www.ulcc.org [http://eline.ulcc.org/images/ULC_logo_platinum_2014_email.jpg] Find out how the Union League Club of Chicago can help enrich your life and improve the world by contacting membership at ulcc.org or 312.435.4825. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From j at minorscience.com Thu Mar 15 09:14:55 2018 From: j at minorscience.com (Jason Loeffler) Date: Thu, 15 Mar 2018 09:14:55 -0400 Subject: [Archivesspace_Users_Group] FW: [Archivesspace_member_reps] Migrating Data from Eloquent Systems to ArchivesSpace In-Reply-To: References: Message-ID: Hi Cheryl, Eloquent is a little bit of a black box, unfortunately. Could you send over a couple of example records? With those in hand, I can better advise you on various migration tactics. Do you host Eloquent yourself? Do you have direct access to its database? Jason On Thu, Mar 15, 2018 at 8:59 AM, Christine Di Bella < christine.dibella at lyrasis.org> wrote: > Hi all, > > > > I?m forwarding this for Cheryl from the Member Representatives list in > case anyone here has made a move from Eloquent and has suggestions or > advice. The program team will also reach out with some ideas. > > > > 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_member_reps-bounces at lyralists.lyrasis.org < > archivesspace_member_reps-bounces at lyralists.lyrasis.org> *On Behalf Of *Cheryl > Ziegler > *Sent:* Wednesday, March 14, 2018 8:58 PM > *To:* archivesspace_member_reps at lyralists.lyrasis.org > *Subject:* [Archivesspace_member_reps] Migrating Data from Eloquent > Systems to ArchivesSpace > > > > Hello all, > > > > I am under significant time constraints to move my data from Eloquent > Systems to ArchivesSpace as my contract with Eloquent is over effective > April 30. I was led to believe that my data could be exported in EAD > format. Unfortunately, that is not true. I can only export my data into > ASCII delimited text format. > > > > I am flying blind here and I know there is not an easy "fix." If I need to > manually input my records, then I need to start doing that right away. If > there is a way to convert ASCII into a workable migration format, then I > need advise on how to accomplish that conversion. > > > > Some background: earlier in the year, my IT Director told me he had > figured out how to do this migration. He has resigned taking that > information with him although I am not sure that he actually *had* > figured it out. > > > > I am willing to do the work. I just need a process. > > > > Thank you, > > Cheryl > > > Cheryl L. Ziegler, MLIS > > Director of Library & Archives > Union League Club of Chicago > > 65 W. Jackson Blvd. > > Chicago, IL 60604 > > > P: 312.435.4818 <(312)%20435-4818> > > www.ulcc.org > > > > *Find out how the Union League Club of Chicago can help enrich your life > and improve the world by contacting membership at ulcc.org > or 312.435.4825 <312.435.4825>.* > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: not available URL: From dave_mayo at harvard.edu Thu Mar 15 09:24:15 2018 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Thu, 15 Mar 2018 13:24:15 +0000 Subject: [Archivesspace_Users_Group] FW: [Archivesspace_member_reps] Migrating Data from Eloquent Systems to ArchivesSpace Message-ID: <1617F976-48C8-4D44-A822-94B7F681D2B2@harvard.edu> Hi Cheryl, Oof, that?s rough. I have a few questions, if you don?t mind. 1. Can you provide more detail on why EAD export is impossible? I only ask because they claim EAD export on their website pretty prominently, and it would be, I think, much easier than doing a migration from proprietary text format. 2. Are you comfortable with programming in a scripting language (Python, Ruby, Perl, etc.) or do you have access to someone who is? 3. What does the ASCII format actually look like? An example record would be really helpful in giving advice. Assuming that EAD is entirely out of reach, I think this would take either, as you mentioned, manual transfer, or someone writing a script to take the ascii output, turn it into ASpace JSONModel objects, and import it via the API. The hardest part is probably the conversion step ? there?s a fair amount of code out there for doing imports of JSONModel objects (or you can just strip the EAD -> JSONModel part out of EAD import scripts), but I don?t know that there?s a way around significant programming effort. Even EAD migrations have in my experience involved a fair amount of programming, though size and scope of collection matters a lot for how important that is. - Dave Mayo ASpace Core Committers Group From: on behalf of Christine Di Bella Reply-To: Archivesspace Users Group Date: Thursday, March 15, 2018 at 8:59 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] FW: [Archivesspace_member_reps] Migrating Data from Eloquent Systems to ArchivesSpace Hi all, I?m forwarding this for Cheryl from the Member Representatives list in case anyone here has made a move from Eloquent and has suggestions or advice. The program team will also reach out with some ideas. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_member_reps-bounces at lyralists.lyrasis.org On Behalf Of Cheryl Ziegler Sent: Wednesday, March 14, 2018 8:58 PM To: archivesspace_member_reps at lyralists.lyrasis.org Subject: [Archivesspace_member_reps] Migrating Data from Eloquent Systems to ArchivesSpace Hello all, I am under significant time constraints to move my data from Eloquent Systems to ArchivesSpace as my contract with Eloquent is over effective April 30. I was led to believe that my data could be exported in EAD format. Unfortunately, that is not true. I can only export my data into ASCII delimited text format. I am flying blind here and I know there is not an easy "fix." If I need to manually input my records, then I need to start doing that right away. If there is a way to convert ASCII into a workable migration format, then I need advise on how to accomplish that conversion. Some background: earlier in the year, my IT Director told me he had figured out how to do this migration. He has resigned taking that information with him although I am not sure that he actually had figured it out. I am willing to do the work. I just need a process. Thank you, Cheryl Cheryl L. Ziegler, MLIS Director of Library & Archives Union League Club of Chicago 65 W. Jackson Blvd. Chicago, IL 60604 P: 312.435.4818 www.ulcc.org [http://eline.ulcc.org/images/ULC_logo_platinum_2014_email.jpg] Find out how the Union League Club of Chicago can help enrich your life and improve the world by contacting membership at ulcc.org or 312.435.4825. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6609 bytes Desc: image001.jpg URL: From blparker at umd.edu Thu Mar 15 09:42:16 2018 From: blparker at umd.edu (Bria Lynn Parker) Date: Thu, 15 Mar 2018 09:42:16 -0400 Subject: [Archivesspace_Users_Group] FW: [Archivesspace_member_reps] Migrating Data from Eloquent Systems to ArchivesSpace In-Reply-To: <1617F976-48C8-4D44-A822-94B7F681D2B2@harvard.edu> References: <1617F976-48C8-4D44-A822-94B7F681D2B2@harvard.edu> Message-ID: Hi Cheryl, I'll also chime in here - I just got (mostly) through converting a ton of data that were eloquent data exported to tab delimited text/spreadsheet. We had a LARGE collection we purchased, and that was what we got with it: a dump of their eloquent data. I made use of Stead: https://github.com/jronallo/stead to do the conversion to EAD, and some local scripts to do some stuff to the converted EAD prior to upload to ArchivesSpace. A colleague and I made some local modifications/enhancements Stead to get it to work with our data. I would be more than happy to talk with you offline about how I did this if this is something you're interested in. And I would of course share my code. -- Bria L. Parker Head, Discovery and Metadata Services 2200 McKeldin Library University of Maryland College Park, MD 20742-7011 (301) 405-9067 blparker at umd.edu On Thu, Mar 15, 2018 at 9:24 AM, Mayo, Dave wrote: > Hi Cheryl, > > Oof, that?s rough. I have a few questions, if you don?t mind. > > 1. Can you provide more detail on why EAD export is impossible? I only > ask because they claim EAD export on their website pretty prominently, and > it would be, I think, much easier than doing a migration from proprietary > text format. > 2. Are you comfortable with programming in a scripting language (Python, > Ruby, Perl, etc.) or do you have access to someone who is? > 3. What does the ASCII format actually look like? An example record would > be really helpful in giving advice. > > Assuming that EAD is entirely out of reach, I think this would take > either, as you mentioned, manual transfer, or someone writing a script to > take the ascii output, turn it into ASpace JSONModel objects, and import it > via the API. The hardest part is probably the conversion step ? there?s a > fair amount of code out there for doing imports of JSONModel objects (or > you can just strip the EAD -> JSONModel part out of EAD import scripts), > but I don?t know that there?s a way around significant programming effort. > Even EAD migrations have in my experience involved a fair amount of > programming, though size and scope of collection matters a lot for how > important that is. > > - Dave Mayo > ASpace Core Committers Group > > > > *From: * on > behalf of Christine Di Bella > *Reply-To: *Archivesspace Users Group lyralists.lyrasis.org> > *Date: *Thursday, March 15, 2018 at 8:59 AM > *To: *Archivesspace Users Group lyralists.lyrasis.org> > *Subject: *[Archivesspace_Users_Group] FW: [Archivesspace_member_reps] > Migrating Data from Eloquent Systems to ArchivesSpace > > > > Hi all, > > > > I?m forwarding this for Cheryl from the Member Representatives list in > case anyone here has made a move from Eloquent and has suggestions or > advice. The program team will also reach out with some ideas. > > > > 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_member_reps-bounces at lyralists.lyrasis.org < > archivesspace_member_reps-bounces at lyralists.lyrasis.org> *On Behalf Of *Cheryl > Ziegler > *Sent:* Wednesday, March 14, 2018 8:58 PM > *To:* archivesspace_member_reps at lyralists.lyrasis.org > *Subject:* [Archivesspace_member_reps] Migrating Data from Eloquent > Systems to ArchivesSpace > > > > Hello all, > > > > I am under significant time constraints to move my data from Eloquent > Systems to ArchivesSpace as my contract with Eloquent is over effective > April 30. I was led to believe that my data could be exported in EAD > format. Unfortunately, that is not true. I can only export my data into > ASCII delimited text format. > > > > I am flying blind here and I know there is not an easy "fix." If I need to > manually input my records, then I need to start doing that right away. If > there is a way to convert ASCII into a workable migration format, then I > need advise on how to accomplish that conversion. > > > > Some background: earlier in the year, my IT Director told me he had > figured out how to do this migration. He has resigned taking that > information with him although I am not sure that he actually *had* > figured it out. > > > > I am willing to do the work. I just need a process. > > > > Thank you, > > Cheryl > > > Cheryl L. Ziegler, MLIS > > Director of Library & Archives > Union League Club of Chicago > > 65 W. Jackson Blvd. > > Chicago, IL 60604 > > > P: 312.435.4818 <(312)%20435-4818> > > www.ulcc.org > > > > > [image: http://eline.ulcc.org/images/ULC_logo_platinum_2014_email.jpg] > > *Find out how the Union League Club of Chicago can help enrich your life > and improve the world by contacting **membership at ulcc.org* > * or **312.435.4825* <312.435.4825>*.* > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6609 bytes Desc: not available URL: From mcallahan at smith.edu Thu Mar 15 11:20:14 2018 From: mcallahan at smith.edu (Maureen Callahan) Date: Thu, 15 Mar 2018 11:20:14 -0400 Subject: [Archivesspace_Users_Group] patron-facing accession records Message-ID: Hi folks, One of my favorite conceptual things about the ArchivesSpace PUI is that it lets archives publish their accession records in an outward-facing way so that researchers can have access to these materials right away, even before they're included in resource records. I'm pulling together examples of archival descriptions for a DACS workshop, and I'm wondering if anyone has patron-facing accession records out in the world that they're particularly proud of and can point me too. Feel free to send me your examples offlist -- mcallahan at smith.edu Many thanks, Maureen -- Maureen Callahan Sophia Smith Collection Archivist Smith College Special Collections Northampton, Massachusetts 01063 T. 413 585 2981 C. 215.863.1860 mcallahan at smith.edu Pronouns: she/her/hers Facebook: https://www.facebook.com/SophiaSmithCollection/ Instagram: https://www.instagram.com/smithlibraries/ Twitter: https://twitter.com/archivalagents *Please note*. Smith College Special Collections is now housed at Young Library . Learn more about renovations to Neilson Library here . -------------- next part -------------- An HTML attachment was scrubbed... URL: From seth.shaw at unlv.edu Thu Mar 15 13:56:34 2018 From: seth.shaw at unlv.edu (Seth Shaw) Date: Thu, 15 Mar 2018 10:56:34 -0700 Subject: [Archivesspace_Users_Group] EAD export not including dao tags Message-ID: Using 2.3.1, I created a digital object instance for an archival object however the resource's EAD export is not including the dao tag. I've ensured that the "Include tags" option IS selected (I tested both on and off, just to be sure). The archival object, all parents, and the digital object are set to publish. I've included relevant screenshots below. Using the EAD3 *does* include the dao tag but produces an unrelated error (for the curious, in place of the abstract we get an error stating "incompatible encoding regexp match (UTF-8 regexp with ASCII-8BIT string)") so the problem is certainly with the EAD 2002 export. It is a problem because the PDF export relies on the EAD 2002 export. Anyone else running into this? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-03-15 at 10.47.11 AM.png Type: image/png Size: 351191 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-03-15 at 10.51.49 AM.png Type: image/png Size: 344687 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-03-15 at 10.53.46 AM.png Type: image/png Size: 108032 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2018-03-15 at 10.54.51 AM.png Type: image/png Size: 229325 bytes Desc: not available URL: From seth.shaw at unlv.edu Thu Mar 15 14:23:11 2018 From: seth.shaw at unlv.edu (Seth Shaw) Date: Thu, 15 Mar 2018 11:23:11 -0700 Subject: [Archivesspace_Users_Group] EAD export not including dao tags In-Reply-To: References: Message-ID: Okay, this is beginning to be like the boy who cried wolf. Please disregard my last email. Another local plugin that I somehow didn't notice on my first look for a culprit. (A fresh install worked properly and prompted another look.) On Thu, Mar 15, 2018 at 10:56 AM, Seth Shaw wrote: > Using 2.3.1, I created a digital object instance for an archival object > however the resource's EAD export is not including the dao tag. > > I've ensured that the "Include tags" option IS selected (I tested > both on and off, just to be sure). The archival object, all parents, and > the digital object are set to publish. I've included relevant screenshots > below. > > Using the EAD3 *does* include the dao tag but produces an unrelated error > (for the curious, in place of the abstract we get an error stating "incompatible > encoding regexp match (UTF-8 regexp with ASCII-8BIT string)") so the > problem is certainly with the EAD 2002 export. It is a problem because the > PDF export relies on the EAD 2002 export. > > Anyone else running into this? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ccauste1 at swarthmore.edu Thu Mar 15 15:28:18 2018 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Thu, 15 Mar 2018 15:28:18 -0400 Subject: [Archivesspace_Users_Group] Request for comments: draft specification for human-readable URLs in ASpace PUI In-Reply-To: References: Message-ID: Hello ASpacers, Just a reminder to please review and comment on this DRAFT specification for creating logical and customizable title or identifier-based URLs in the ArchivesSpace PUI: https://goo.gl/jjmtLF. Whether or not you have specific comments, if this feature is important to you, please vote for the ticket (JIRA ticket ANW-617 ). *Please add your comments and votes by March 30th, 2018. *After that point, Cory and I will finalize the specification and submit it to the ArchivesSpace team. Cheers, Celia and Cory On Wed, Feb 28, 2018 at 8:57 AM, Celia Caust-Ellenbogen < ccauste1 at swarthmore.edu> wrote: > Hello ASpacers, > > Please review and comment on this DRAFT specification for creating logical > and customizable title or identifier-based URLs in the ArchivesSpace PUI: > https://goo.gl/jjmtLF. > > This feature is important to me because it will improve the user > experience, improve SEO, and foster continuity with our previous (and > subsequent) finding aid systems. > > If this feature is important to you, please vote for the ticket (JIRA > ticket ANW-617 ) if > you haven't already done so. This will help demonstrate community interest > when it comes time to prioritize tickets. > > The specification was drafted by Cory Nimer (Brigham Young University) and > myself, with input from Lydia Tang (Michigan State University) and Mark > Custer (Yale). > > Your input is much appreciated. Thank you in advance! > > Cheers, > Celia and Cory > > -- > Celia Caust-Ellenbogen > Friends Historical Library of Swarthmore College > > 610-328-8496 <(610)%20328-8496> > ccauste1 at swarthmore.edu > she/her/hers > > > -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8496 ccauste1 at swarthmore.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From lynn.moulton at bc.edu Thu Mar 15 15:45:04 2018 From: lynn.moulton at bc.edu (Lynn Moulton) Date: Thu, 15 Mar 2018 15:45:04 -0400 Subject: [Archivesspace_Users_Group] Linking Agents to Archival Objects Message-ID: Thanks Alex. We're using 2.3.1. So it looks like it might be a problem with our (custom) stylesheet. Best, Lynn Lynn, Which version are you encountering this issue on? I tried reproducing this issue on the sandbox (http://sandbox.archivesspace. org/resources/11/edit#tree::resource_11, username/password are admin/admin), but the PDF didn't cause any issues. Thanks! --Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From reesj at mail.nlm.nih.gov Fri Mar 16 09:32:24 2018 From: reesj at mail.nlm.nih.gov (Rees, John (NIH/NLM) [E]) Date: Fri, 16 Mar 2018 13:32:24 +0000 Subject: [Archivesspace_Users_Group] patron-facing accession records In-Reply-To: References: Message-ID: We?ve been doing this for several years as an end-of-year task. We make brief collection level MARC records first, then grab them all through MarcEdit and spin them through the MARCXML-EAD conversion stylesheet to get EAD for our DLXS. You can see them at https://oculus.nlm.nih.gov/cgi/f/findaid/findaid-idx?c=nlmfindaid&cc=nlmfindaid&type=simple&rgn=Anywhere+in+Finding+Aid&q1=unprocessed+collection&Submit=Search John From: Maureen Callahan [mailto:mcallahan at smith.edu] Sent: Thursday, March 15, 2018 11:20 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] patron-facing accession records Hi folks, One of my favorite conceptual things about the ArchivesSpace PUI is that it lets archives publish their accession records in an outward-facing way so that researchers can have access to these materials right away, even before they're included in resource records. I'm pulling together examples of archival descriptions for a DACS workshop, and I'm wondering if anyone has patron-facing accession records out in the world that they're particularly proud of and can point me too. Feel free to send me your examples offlist -- mcallahan at smith.edu Many thanks, Maureen -- Maureen Callahan Sophia Smith Collection Archivist Smith College Special Collections Northampton, Massachusetts 01063 T. 413 585 2981 C. 215.863.1860 mcallahan at smith.edu Pronouns: she/her/hers Facebook: https://www.facebook.com/SophiaSmithCollection/ Instagram: https://www.instagram.com/smithlibraries/ Twitter: https://twitter.com/archivalagents Please note. Smith College Special Collections is now housed at Young Library. Learn more about renovations to Neilson Library here. -------------- next part -------------- An HTML attachment was scrubbed... URL: From benn.joseph at northwestern.edu Fri Mar 16 09:52:30 2018 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Fri, 16 Mar 2018 13:52:30 +0000 Subject: [Archivesspace_Users_Group] customizing PDF output for PUI Message-ID: <8ca4be47871b468aac5bf5c27c290eeb@evcspmbx04.ads.northwestern.edu> Hi all, We're on v2.3.0 and are interested in doing some customizations (adding branding, changing font sizes, reordering content) on the PDF output in our ArchivesSpace public interface. However, we can't seem to find where to make those changes. Can anyone point me to a directory or config file or something along those lines where we can get started? I remember also hearing at one point about there being a plugin that adds the Biographical Note from an Agent record to the PDF output. We're very interested in this plugin, but I also wonder if we need to be thinking about this too while we consider these customizations. We did discover how to make edits to the PDF output in the staff interface, but these seem to be two separate processes. Or maybe they're not and I'm missing something obvious! Thanks, --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Mar 16 10:28:45 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 16 Mar 2018 14:28:45 +0000 Subject: [Archivesspace_Users_Group] error on v2.2.0 PUI print PDF: InvalidAuthenticityToken In-Reply-To: References: <7D1A71F6-77CD-47A2-9D98-070DDA6E8065@virginia.edu> Message-ID: <0DFEC38F-EA45-46BF-BFFE-7DA1209CF322@virginia.edu> Just for the record: we were missing these two lines documented in README_HTTPS.md example in our apache config: RequestHeader set X-Forwarded-Proto "https" ProxyPreserveHost On After adding those lines it appears to work properly. ? Steve M. > On Jan 23, 2018, at 5:46 PM, Majewski, Steven Dennis (sdm7g) wrote: > > > Also discovered that PDF print thru SSL proxy does work in Firefox after googling ?authenticity token proxy ssl? > and seeing title of this Rails issue: > > CSRF protection prevents some webkit users from submitting forms ? Issue #21948 ? rails/rails > > I?ve been seeing the bug in Safari, and you?ve been seeing it in Chrome. Both, I believe, are webkit based. > > Long discussion thread that I haven?t digested yet, so I?m not sure if that is the problem here. > That same google search brings up some other issues that may be related to not passing all of the headers thru proxy. > > https://github.com/rails/rails/issues/22965 > > > ? Steve M. > > > >> On Jan 23, 2018, at 5:15 PM, Majewski, Steven Dennis (sdm7g) > wrote: >> >> >> Thanks. Yes: I?m still seeing the problem. No: no solution so far. >> The fact that I was only seeing it on production limited my ability to debug. >> Now that you?ve found it?s linked to SSL proxy, I will try to set up test machines to reproduce the problem. >> >> ? Steve. >> >> >> >>> On Jan 23, 2018, at 4:25 PM, Chelsea Lobdell > wrote: >>> >>> Update: we were able to identify that this error was happening only when running the application over SSL. Accessing the site over non-SSL allowed the print function to work. >>> >>> - Chelsea >>> >>> --------------- >>> Chelsea Lobdell >>> Library Web Developer/ Swarthmore College >>> clobdel1 at swarthmore.edu / (610)690-6818 >>> >>> On Tue, Jan 23, 2018 at 3:45 PM, Chelsea Lobdell > wrote: >>> Hi Aspace! >>> >>> I saw this post on the user group but was not able to find the thread in my email so I apologize for replying off thread. >>> >>> We are seeing this same error and we are running v.2.2.2 However, the error seems to be browser specific as it only happens in Chrome. Here's the log output: >>> >>> Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log >>> INFO: W, [2018-01-23T15:32:31.474750 #21127] WARN -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Can't verify CSRF token authenticity. >>> >>> Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log >>> INFO: I, [2018-01-23T15:32:31.478068 #21127] INFO -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] Completed 422 Unprocessable Entity in 6ms >>> >>> Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log >>> INFO: F, [2018-01-23T15:32:31.485699 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] >>> >>> Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log >>> INFO: F, [2018-01-23T15:32:31.486567 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] ActionController::InvalidAuthenticityToken (ActionController::InvalidAuthenticityToken): >>> >>> Jan 23, 2018 3:32:31 PM org.eclipse.jetty.server.handler.ContextHandler$Context log >>> INFO: F, [2018-01-23T15:32:31.487220 #21127] FATAL -- : [e1415e7e-47c5-4776-893f-cb5a7b33a4d9] >>> >>> Steve, were you ever able to find a solution for this? Has anybody else encountered this error when trying to print a PDF of a collection in Chrome? >>> >>> Thanks, >>> Chelsea >>> --------------- >>> Chelsea Lobdell >>> Library Web Developer/ Swarthmore College >>> clobdel1 at swarthmore.edu / (610)690-6818 >>> _______________________________________________ >>> 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From sdm7g at virginia.edu Fri Mar 16 10:58:26 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 16 Mar 2018 14:58:26 +0000 Subject: [Archivesspace_Users_Group] customizing PDF output for PUI In-Reply-To: <8ca4be47871b468aac5bf5c27c290eeb@evcspmbx04.ads.northwestern.edu> References: <8ca4be47871b468aac5bf5c27c290eeb@evcspmbx04.ads.northwestern.edu> Message-ID: <1BAD5AB1-DDAF-46EC-A486-3973436FE4EF@virginia.edu> You are correct: The PDF generation from the staff and the public interfaces are different and use two completely different toolchains. Staff: Resource -> EAD -> xsl -> fop -> PDF Public: Resource -> HTML + CSS -> iText -> PDF For public code look at: https://github.com/archivesspace/archivesspace/blob/master/public/app/controllers/pdf_controller.rb https://github.com/archivesspace/archivesspace/blob/master/public/app/models/finding_aid_pdf.rb It is using the rails view templates, but calling the partials manually to leave out the usual HTML headers, footers, menus and page decoration that is not wanted in the print version and to explicitly include the child content inline rather than as links. The iText renderer which generates the PDF from HTML+CSS is a Java library in common/lib/itext-2.1.7.js2.jar . You can google for API details, but you probably don?t need to get that deep in the weeds. If you are successful in customizing output, please report back, as we don?t yet have any documentation on customization process for PDF output from the public size. ? Steve. > On Mar 16, 2018, at 9:52 AM, Benn Joseph wrote: > > Hi all, > We?re on v2.3.0 and are interested in doing some customizations (adding branding, changing font sizes, reordering content) on the PDF output in our ArchivesSpace public interface. However, we can?t seem to find where to make those changes. Can anyone point me to a directory or config file or something along those lines where we can get started? I remember also hearing at one point about there being a plugin that adds the Biographical Note from an Agent record to the PDF output. We?re very interested in this plugin, but I also wonder if we need to be thinking about this too while we consider these customizations. > > We did discover how to make edits to the PDF output in the staff interface, but these seem to be two separate processes. Or maybe they?re not and I?m missing something obvious! > > Thanks, > --Benn > > Benn Joseph > Head of Archival Processing > Northwestern University Libraries > Northwestern University > www.library.northwestern.edu > benn.joseph at northwestern.edu > 847.467.6581 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From ltang5 at lib.msu.edu Fri Mar 16 11:24:36 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Fri, 16 Mar 2018 15:24:36 +0000 Subject: [Archivesspace_Users_Group] customizing PDF output for PUI In-Reply-To: <1BAD5AB1-DDAF-46EC-A486-3973436FE4EF@virginia.edu> References: <8ca4be47871b468aac5bf5c27c290eeb@evcspmbx04.ads.northwestern.edu> <1BAD5AB1-DDAF-46EC-A486-3973436FE4EF@virginia.edu> Message-ID: <30D7179C-9CD4-47E7-B345-791D45031435@lib.msu.edu> Yes, please report back! I am also interested in this as well. FYI, there is a JIRA ticket out there for reconciling some discrepancies between the two PDF options https://archivesspace.atlassian.net/browse/ANW-258 In general, it would be great to potentially crowdsource some documentation on how to customize it and perhaps address common/frequent complaints in updating the default stylesheet. Just my thoughts! Lydia From rachel.searcy at nyu.edu Fri Mar 16 11:31:00 2018 From: rachel.searcy at nyu.edu (Rachel Aileen Searcy) Date: Fri, 16 Mar 2018 11:31:00 -0400 Subject: [Archivesspace_Users_Group] Configuring barcode digits? Message-ID: Hello everyone, We're interested in configuring the barcode field of the top container record to enforce validation for the number of digits. It looks like this was included in the original development of the container management functionality , but after poking around a bit in the system and available documentation I don't see any further information. If anyone has done this locally, could you be so kind as to tell me how you made this happen? Thanks very much (and in the spirit of the season, go raibh maith agat ?), Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Mar 16 12:37:42 2018 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Fri, 16 Mar 2018 16:37:42 +0000 Subject: [Archivesspace_Users_Group] Configuring barcode digits? In-Reply-To: References: Message-ID: <807209B1-A446-4310-AFC2-D6D73DBC539C@virginia.edu> The generate_accession_identifiers plugin is an example of how to load javascript conditionally for a particular controller and action. For your case, you probably want to catch the top_containers controller for new and edit actions. https://github.com/archivesspace/archivesspace/blob/master/plugins/generate_accession_identifiers/frontend/views/layout_head.html.erb <% if controller.controller_name == 'accessions' && controller.action_name == 'new' %> <%= javascript_include_tag "#{@base_url}/assets/generate_accession_identifiers.js" %> <% end %> Inspecting the form html, the field you want to validate is: $( ?input#top_container_barcode_? ) You can google many examples of how to validate forms using jquery. Here?s one example: https://formden.com/blog/validate-contact-form-jquery ? Steve M. > On Mar 16, 2018, at 11:31 AM, Rachel Aileen Searcy wrote: > > Hello everyone, > > We're interested in configuring the barcode field of the top container record to enforce validation for the number of digits. It looks like this was included in the original development of the container management functionality , but after poking around a bit in the system and available documentation I don't see any further information. If anyone has done this locally, could you be so kind as to tell me how you made this happen? > > Thanks very much (and in the spirit of the season, go raibh maith agat ?), > > Rachel Searcy > Accessioning Archivist, Archival Collections Management > New York University Libraries > 212.998.2539 <> | rachel.searcy at nyu.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6091 bytes Desc: not available URL: From alexanderduryee at nypl.org Fri Mar 16 12:39:49 2018 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Fri, 16 Mar 2018 12:39:49 -0400 Subject: [Archivesspace_Users_Group] Configuring barcode digits? In-Reply-To: References: Message-ID: Rachel, It's an undocumented feature in config/config.rb. You'll need to add the following line, swapping our values for yours and expanding as needed: AppConfig[:container_management_barcode_length] = {"MSS" => {:min => '14', :max => '14'}, "THE" => {:min => '14', :max => '14'}} Note that this uses the repository code to match the validation to its repository. If a container has no barcode, it automatically validates - for our case, barcodes must be exactly either 0 or 14 characters long. (Code here - https://github.com/archivesspace/archivesspace/blob/master/common/barcode_check.rb ) Hope this helps, --Alex On Fri, Mar 16, 2018 at 11:31 AM, Rachel Aileen Searcy < rachel.searcy at nyu.edu> wrote: > Hello everyone, > > We're interested in configuring the barcode field of the top container > record to enforce validation for the number of digits. It looks like this > was included in the original development of the container management > functionality > , > but after poking around a bit in the system and available documentation I > don't see any further information. If anyone has done this locally, could > you be so kind as to tell me how you made this happen? > > Thanks very much (and in the spirit of the season, go raibh maith agat ?), > > Rachel Searcy > Accessioning Archivist, Archival Collections Management > New York University Libraries > 212.998.2539 | rachel.searcy at nyu.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Fri Mar 16 13:01:07 2018 From: mark.custer at yale.edu (Custer, Mark) Date: Fri, 16 Mar 2018 17:01:07 +0000 Subject: [Archivesspace_Users_Group] Configuring barcode digits? In-Reply-To: References: Message-ID: Rachel, all: It was documented in the plugin. I still refer to that documentation here: https://github.com/hudmol/container_management#configuring-it But it should be added to the core documentation, of course! Mark From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Alexander Duryee Sent: Friday, 16 March, 2018 12:40 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Configuring barcode digits? Rachel, It's an undocumented feature in config/config.rb. You'll need to add the following line, swapping our values for yours and expanding as needed: AppConfig[:container_management_barcode_length] = {"MSS" => {:min => '14', :max => '14'}, "THE" => {:min => '14', :max => '14'}} Note that this uses the repository code to match the validation to its repository. If a container has no barcode, it automatically validates - for our case, barcodes must be exactly either 0 or 14 characters long. (Code here - https://github.com/archivesspace/archivesspace/blob/master/common/barcode_check.rb) Hope this helps, --Alex On Fri, Mar 16, 2018 at 11:31 AM, Rachel Aileen Searcy > wrote: Hello everyone, We're interested in configuring the barcode field of the top container record to enforce validation for the number of digits. It looks like this was included in the original development of the container management functionality, but after poking around a bit in the system and available documentation I don't see any further information. If anyone has done this locally, could you be so kind as to tell me how you made this happen? Thanks very much (and in the spirit of the season, go raibh maith agat ?), Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From rachel.searcy at nyu.edu Fri Mar 16 13:38:05 2018 From: rachel.searcy at nyu.edu (Rachel Aileen Searcy) Date: Fri, 16 Mar 2018 13:38:05 -0400 Subject: [Archivesspace_Users_Group] Configuring barcode digits? In-Reply-To: References: Message-ID: Thanks, everyone! On Fri, Mar 16, 2018 at 1:01 PM, Custer, Mark wrote: > Rachel, all: > > > > It was documented in the plugin. I still refer to that documentation here: > > > > https://github.com/hudmol/container_management#configuring-it > > > > But it should be added to the core documentation, of course! > > > > Mark > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Alexander > Duryee > *Sent:* Friday, 16 March, 2018 12:40 PM > *To:* Archivesspace Users Group lyralists.lyrasis.org> > *Subject:* Re: [Archivesspace_Users_Group] Configuring barcode digits? > > > > Rachel, > > It's an undocumented feature in config/config.rb. You'll need to add the > following line, swapping our values for yours and expanding as needed: > > AppConfig[:container_management_barcode_length] = {"MSS" => {:min => '14', > :max => '14'}, "THE" => {:min => '14', :max => '14'}} > > Note that this uses the repository code to match the validation to its > repository. If a container has no barcode, it automatically validates - > for our case, barcodes must be exactly either 0 or 14 characters long. > > > > (Code here - https://github.com/archivesspace/archivesspace/ > blob/master/common/barcode_check.rb > > ) > > Hope this helps, > > --Alex > > > > On Fri, Mar 16, 2018 at 11:31 AM, Rachel Aileen Searcy < > rachel.searcy at nyu.edu> wrote: > > Hello everyone, > > > > We're interested in configuring the barcode field of the top container > record to enforce validation for the number of digits. It looks like this > was included in the original development of the container management > functionality > , > but after poking around a bit in the system and available documentation I > don't see any further information. If anyone has done this locally, could > you be so kind as to tell me how you made this happen? > > > > Thanks very much (and in the spirit of the season, go raibh maith agat ? > ), > > > > Rachel Searcy > Accessioning Archivist, Archival Collections Management > > New York University Libraries > > 212.998.2539 <(212)%20998-2539> | rachel.searcy at nyu.edu > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > > -- > > Alexander Duryee > > Metadata Archivist > > New York Public Library > > (917)-229-9590 <(917)%20229-9590> > > alexanderduryee at nypl.org > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexanderduryee at nypl.org Fri Mar 16 15:04:15 2018 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Fri, 16 Mar 2018 15:04:15 -0400 Subject: [Archivesspace_Users_Group] Configuring barcode digits? In-Reply-To: References: Message-ID: Mark, Thanks! I wasn't aware that these features were documented in the old plugin repo. I added documentation on container management options to config.rb ( https://github.com/archivesspace/archivesspace/commit/8ffeed29dd35649a2cf26bd908fb12794a803b22), and the tech-docs repo will be updated with documentation as well. They'll be less secret in future releases :) Thanks again! --Alex On Fri, Mar 16, 2018 at 1:38 PM, Rachel Aileen Searcy wrote: > Thanks, everyone! > > On Fri, Mar 16, 2018 at 1:01 PM, Custer, Mark > wrote: > >> Rachel, all: >> >> >> >> It was documented in the plugin. I still refer to that documentation >> here: >> >> >> >> https://github.com/hudmol/container_management#configuring-it >> >> >> >> But it should be added to the core documentation, of course! >> >> >> >> Mark >> >> >> >> >> >> >> >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: >> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Alexander >> Duryee >> *Sent:* Friday, 16 March, 2018 12:40 PM >> *To:* Archivesspace Users Group > alists.lyrasis.org> >> *Subject:* Re: [Archivesspace_Users_Group] Configuring barcode digits? >> >> >> >> Rachel, >> >> It's an undocumented feature in config/config.rb. You'll need to add the >> following line, swapping our values for yours and expanding as needed: >> >> AppConfig[:container_management_barcode_length] = {"MSS" => {:min => '14', >> :max => '14'}, "THE" => {:min => '14', :max => '14'}} >> >> Note that this uses the repository code to match the validation to its >> repository. If a container has no barcode, it automatically validates - >> for our case, barcodes must be exactly either 0 or 14 characters long. >> >> >> >> (Code here - https://github.com/archivesspace/archivesspace/blob/master/ >> common/barcode_check.rb >> >> ) >> >> Hope this helps, >> >> --Alex >> >> >> >> On Fri, Mar 16, 2018 at 11:31 AM, Rachel Aileen Searcy < >> rachel.searcy at nyu.edu> wrote: >> >> Hello everyone, >> >> >> >> We're interested in configuring the barcode field of the top container >> record to enforce validation for the number of digits. It looks like this >> was included in the original development of the container management >> functionality >> , >> but after poking around a bit in the system and available documentation I >> don't see any further information. If anyone has done this locally, could >> you be so kind as to tell me how you made this happen? >> >> >> >> Thanks very much (and in the spirit of the season, go raibh maith agat ? >> ), >> >> >> >> Rachel Searcy >> Accessioning Archivist, Archival Collections Management >> >> New York University Libraries >> >> 212.998.2539 <(212)%20998-2539> | rachel.searcy at nyu.edu >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> >> >> -- >> >> Alexander Duryee >> >> Metadata Archivist >> >> New York Public Library >> >> (917)-229-9590 <(917)%20229-9590> >> >> alexanderduryee at nypl.org >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Rachel Searcy > Accessioning Archivist, Archival Collections Management > New York University Libraries > 212.998.2539 | rachel.searcy at nyu.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Mon Mar 19 15:55:50 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Mon, 19 Mar 2018 19:55:50 +0000 Subject: [Archivesspace_Users_Group] Boston Regional Forum - lightning round reminder Message-ID: The lightning round submission deadline has been extended to next Friday, March 30th! More info here: http://archivesspace.org/boston-regional-forum-lightning-round-proposals/ Join us for the ArchivesSpace Regional Forum in Boston! The regional forums are opportunities for our diverse ArchivesSpace members to meet up more locally to share and learn from each other through workshops, focused discussion sessions, and presentations. Registration is now open! [cid:image002.png at 01D3B6B7.3BD065A0] PROGRAM The specifics continue to be shaped by the working group. The most current information is available on the ArchivesSpace wiki. Morning Program: The morning session will highlight stories and experiences through presentations, discussions, and a lightning round. * Lightning round: Currently accepting submissions! More info here: http://archivesspace.org/boston-regional-forum-lightning-round-proposals/ Afternoon program: The afternoon session will feature a hands on, engaging activity or workshop selected by a community poll provided during registration. (The poll will appear during check-out, and is available until April 3rd. The activity will be selected soon after this date, and will be announced shortly after.) Happy Hour: The Boston Library Consortium's Special Collections Community of Interest group is planning a fun evening to follow the program. Details will be provided at a later time. REGISTRATION Registration, including the afternoon session poll, is currently open: https://www.eventbrite.com/e/archivesspace-regional-forum-boston-2018-tickets-42955347601 QUESTIONS? If you have any questions (or ideas!) related to the regional forums, feel free to email Kim at christine.kim at lyrasis.org. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 772934 bytes Desc: image002.png URL: From msugimoto at pvld.org Mon Mar 19 17:05:12 2018 From: msugimoto at pvld.org (Monique Sugimoto) Date: Mon, 19 Mar 2018 14:05:12 -0700 Subject: [Archivesspace_Users_Group] 'cultural context' tag clarification Message-ID: Hello All, I'm working with the Subject heading module and want to confirm if what I'm seeing is correct. I added a dummy heading called 'testtest' and gave it the attribute 'cultural context'. This subject heading was assigned to a resource record. At export of the EAD, the subject heading was given the following tag: testtest Is 'geogname' the expected element tag for something defined as 'cultural context'? Thanks very much for any information. Monique - Monique Leahey Sugimoto Archivist & Adult Services Librarian Palos Verdes Library District 701 Silver Spur Road Rolling Hills Estates, CA 90274 P: 310-377-9584 ext 213 F: 310-541-6807 www.pvld.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 12670 bytes Desc: not available URL: From christine.dibella at lyrasis.org Wed Mar 21 11:26:32 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 21 Mar 2018 15:26:32 +0000 Subject: [Archivesspace_Users_Group] example finding aids/records for ArchivesSpace visual layout project In-Reply-To: References: Message-ID: Thanks to all who have already sent example records! Just a reminder that if you'd like your example records to be included in the test corpus for this project, please send them to me by Friday, March 23. The parameters for what is being accepted are in my original message, included below. Thanks! Christine From: Christine Di Bella Sent: Monday, March 12, 2018 10:55 AM To: Archivesspace Users Group ; 'Archivesspace Member Reps' Subject: example finding aids/records for ArchivesSpace visual layout project Hello again, ArchivesSpace members, I'm assembling a test corpus of finding aids and other records for use in the visual layout project with Cherry Hill Company. This data will be useful in helping those we're working with understand the diversity of forms that archival collections and their descriptions and other metadata take and designing to suit a range of needs. Since time is of the essence, I'm focusing on files known to successfully import in any format that ArchivesSpace accepts - EAD finding aids, accessions in CSV format, digital objects in CSV format, or MARCXML records. You can either send me your source files known to import successfully or export records from your ArchivesSpace in EAD or MARCXML and send them my way for this purpose. No record is too small or too big - or too weird - as long as it's something you manage in ArchivesSpace. Since some types of records do not import/export with collection descriptions, examples of ways you use things like classifications, events, and collection management records with your example records, as well as what you include in your repository record, would also be useful. Please limit example records to no more than 5 per type per submitter, please. The intent is to use these records to populate the test instance for this staff interface project and nothing else, but if you're willing for them to be used for any testing purposes, please indicate that when you send them and we may reuse them when other circumstances inevitably come up. If you'd like your example records to be included, please send them to me by Friday, March 23. Thanks for your help! Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 6608 bytes Desc: image002.jpg URL: From Sara.J.Szakaly at aphis.usda.gov Mon Mar 26 16:29:35 2018 From: Sara.J.Szakaly at aphis.usda.gov (Szakaly, Sara J - APHIS) Date: Mon, 26 Mar 2018 20:29:35 +0000 Subject: [Archivesspace_Users_Group] Hosting Service Providers Message-ID: Hello All, We are exploring options for ArchivesSpace hosting - other than the 3 registered providers and LibraryHost. Does anyone know of others? Thank you! Sara Szakaly Archivist/Records Manager USDA/APHIS/WS National Wildlife Research Center 4101 LaPorte Avenue Fort Collins, CO 80521 970-266-6021 http://www.aphis.usda.gov/wildlifedamage/nwrc This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Mon Mar 26 19:21:11 2018 From: gordon_daines at byu.edu (Gordon Daines) Date: Mon, 26 Mar 2018 23:21:11 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace User Advisory Council Message-ID: Colleagues, Here is a gentle reminder to self-nominate or nominate your colleagues for positions on the ArchivesSpace User Advisory Council. Gordon From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gordon Daines Sent: Thursday, March 01, 2018 11:07 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace User Advisory Council The ArchivesSpace Governance Board is seeking nominations to fill 8 vacancies on the ArchivesSpace User Advisory Council (UAC). Nominees should be presently employed at an ArchivesSpace member institution in any member category (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). Nominations may be made only by ArchivesSpace member representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities projected for UAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Friday, April 15, 2018. The Nominations Committee will review all nominations and recommend appointments to the Governance Board for approval. UAC (http://www.archivesspace.org/usersadvisory) is a critical part of the ArchivesSpace community, serving as a communication conduit between ArchivesSpace governance groups and ArchivesSpace users. It is also the group that implements and contributes to ArchivesSpace user services. Some of the activities UAC is currently engaged in are: * liaising with national and regional archives organizations; * soliciting, suggesting, gathering requirements for, and prioritizing enhancements to the ArchivesSpace application; * maintaining and updating user documentation, as needed, of the ArchivesSpace application; * developing and providing training to users; and * advising the Governance Board and LYRASIS on the design and delivery of user services, including but not limited to help desk support, training, and presentation of documentation. Sub-groups will be established within UAC to address the areas identified above, as well as other activities identified subsequently. Nominees will be appointed to UAC according to their ability to participate in and lead some of the activities mentioned above. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service will be July 1, 2018-June 30, 2020. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2020-June 30, 2022. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please identify the person and her/his organization in the form below, indicate the areas of activity to which the nominee is prepared to contribute. Again, self nominations are welcome. Return the completed form via email to ArchivesSpace Program Manager (Christine Di Bella) at christine.dibella at lyrasis.org, who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Friday, April 15, 2018. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: J. Gordon Daines III, Brigham Young University Chair, and Governance Board member Suzanne Stasiulatis, Pennsylvania Historical and Museum Commission, Chair of User Advisory Council Max Eckard, University of Michigan, Chair of Technical Advisory Council Jordon Steele, Johns Hopkins University, representing very large membership level Amanda Focke, Rice University, representing large membership level Amanda Lanthorne, San Diego State Universtiy, representing medium membership level Rebekah Irwin, Middlebury College, representing small membership level Dylan McDonald, Center for Sacramento History, representing very small membership level Christine Di Bella, (ArchivesSpace Program Manager), ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___Documentation ___Liaising with archives organizations. Please indicate the organizations: _____________________ ___New features, functional or technical specifications ___Training, design ___Training, provision ___ Usability testing ___User/Help support -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Mon Mar 26 19:21:54 2018 From: gordon_daines at byu.edu (Gordon Daines) Date: Mon, 26 Mar 2018 23:21:54 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Technical Advisory Council Message-ID: <8bdc820220b046d98641de298d7d5d07@MB7.byu.local> Colleagues, Here is a gentle reminder to self-nominate or nominate your colleagues for positions on the ArchivesSpace Technical Advisory Council. Gordon From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gordon Daines Sent: Thursday, March 01, 2018 11:14 AM To: 'Archivesspace_Users_Group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Technical Advisory Council The ArchivesSpace Governance Board is seeking nominations to fill 7 vacancies on the ArchivesSpace Technical Advisory Council (TAC). Nominees should be presently employed at an ArchivesSpace member institution (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). They may also be employees of a current Registered Service Provider (see: http://archivesspace.org/registered-service-providers/current-rsps/). Nominations may be made only by ArchivesSpace member representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities assigned to TAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Friday, April 15, 2018. The Nominations Committee will review all nominations and recommend appointments to the Governance Board for approval. TAC (http://www.archivesspace.org/technicaladvisory) is a critical part of the ArchivesSpace community, having responsibility for providing technical guidance to individuals or organizations contributing to application development, to the User Advisory Council, and to the ArchivesSpace Governance Board. TAC's current activities include: * developing a community of code committers, including helping to establish guidelines for contributing code and reviewing contributions, * reviewing enhancements and priorities and testing in collaboration with the User Advisory Council, * providing support for migrating data to ArchivesSpace from other systems and support for importing and exporting data such as EAD, MARCXML, CSV * documenting and assisting with resolving bugs identified in the application, * identifying integration points for ArchivesSpace with other systems (e.g. digital asset management systems, patron and request management systems, etc.), creating resources to assist the community with integration work and, for specific integrations, developing technical requirements, and * updating technical documentation. Sub-teams will be established within TAC to address the areas identified above, as well other activity areas identified subsequently. Nominees must have sufficient knowledge of application development methods, architectures and coding practices to participate in and lead some of the identified activities. Nominees with experience in open source projects, developing web applications (particularly using Ruby on Rails and Sinatra), software testing, or interest in those areas, are especially welcome. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service will be July 1, 2018-June 30, 2020. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2020-June 30, 2022. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please identify the person and her/his organization in the form below, indicate the areas of activity to which the nominee is prepared to contribute. Again, self nominations are welcome. Return the completed form via email to ArchivesSpace Program Manager (Christine Di Bella) at christine.dibella at lyrasis.org, who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Friday, April 15, 2018. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: J. Gordon Daines III, Brigham Young University Chair, and Governance Board member Max Eckard, University of Michigan, Chair of Technical Advisory Council Suzanne Stasiulatis, Pennsylvania Historical and Museum Commission, Chair of User Advisory Council Jordon Steele, Johns Hopkins University, representing very large membership level Amanda Focke, Rice University, representing large membership level Amanda Lanthorne, San Diego State Universtiy, representing medium membership level Rebekah Irwin, Middlebury College, representing small membership level Dylan McDonald, Center for Sacramento History, representing very small membership level Christine Di Bella, (ArchivesSpace Program Manager), ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___Managing/endorsing/eliciting code contributions ___Bug fixes ___Technical documentation ___Program architecture and integrations with other software ___Migration issues, including import/exports and API design and implementation ___Application testing -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Mon Mar 26 19:23:15 2018 From: gordon_daines at byu.edu (Gordon Daines) Date: Mon, 26 Mar 2018 23:23:15 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Governance Board Message-ID: <0e2bc74b128e4c519f3c5b4c14e5c250@MB7.byu.local> Colleagues, Here is a gentle reminder to self-nominate or nominate your colleagues for positions on the ArchivesSpace Governance Board. We are looking for nominations from the Small and Very Large membership categories. Gordon From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gordon Daines Sent: Thursday, March 01, 2018 11:24 AM To: 'Archivesspace_Users_Group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Governance Board As chair of the ArchivesSpace Nominating Committee, I am writing to seek your nominations of candidates to stand for election for the ArchivesSpace Governance Board representing the Very Large and Small membership levels. Member engagement is critical to the success of ArchivesSpace, and the Board relies upon your recommendations for strong candidates. Even if you represent a different category of membership, please consider colleagues you know at other institutions. Only ArchivesSpace members representatives may submit nominations. All other staff of ArchivesSpace member organizations must submit nominations through their Member Representative. All Member Representatives are strongly encouraged to consult with all interested colleagues within their organization to solicit recommendations for nominees. Self-nominations are also welcome if you represent a Very Large or Small member institution. To submit nominations, send names and the institutional affiliation for each, indicating whether or not you have contacted the nominee, so that a member of the nominating committee can follow up with the nominee accordingly to confirm interest. Self-nominees can simply indicate their interest. Nominees who confirm their interest in standing for election will be requested to supply a formal candidate statement outlining their qualifications for serving on the ArchivesSpace Governance Board (see: http://archivesspace.org/about/governance-board-and-councils/). Nominations must be received by 9:00 p.m. EDT Friday, April 15, 2018. They should be sent to ArchivesSpace Program Manager ArchivesSpace Program Manager (Christine Di Bella) at christine.dibella at lyrasis.org, who will collect nominations on behalf of the Nominating Committee. The Nominating Committee will review all nominations and confirm a slate of nominees with the current Governance Board. An election ballot will be circulated to member institutions in mid-May. The current incumbents at the Very Large and Small membership levels are not standing re-election as representatives to the Governance Board. The terms for their successors will be July 1, 2018-June 30, 2021. Each newly elected member representative will be eligible to run for a second term, July 1, 2021-June 30, 2024. Nominees must be currently employed by an ArchivesSpace member organization in either the Very Large or Small member levels (see the member lists at: http://archivesspace.org/community/whos-using-archivesspace/). Nominees should have administrative and fiscal oversight experience, characteristics typical of director or associate director level staff. The Governance Board is charged with providing oversight for the ArchivesSpace application and community, including fiscal oversight, the approval of development priorities, and oversight of the Technical and User Advisory councils. To meet the needs of a broad and diverse membership in a balanced and equitable way, the Governance Board is composed of twelve members, including: 9 voting members: 5 elected members, one from each of the five membership categories; 3 standing members, one representing each of the three original project partners (New York University, UC San Diego, and the University of Illinois, Urbana-Champaign); and 1 member representing the LYRASIS management team. 3 ex officio members: ArchivesSpace Program Manager, LYRASIS Director of Collection Services and Community Supported Software, and 1 member of the LYRASIS Board of Directors. Please feel free to contact me or any member of our Nominating Committee with any questions. Again, nominations should be sent to ArchivesSpace Program Manager (Christine Di Bella) at christine.dibella at lyrasis.org. All nominations must be received by April 15, 2018. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: J. Gordon Daines III, Brigham Young University Chair, and Governance Board member Max Eckard, University of Michigan, Chair of Technical Advisory Council Suzanne Stasiulatis, Pennsylvania Historical and Museum Commission, Chair of User Advisory Council Jordon Steele, Johns Hopkins University, representing very large membership level Amanda Focke, Rice University, representing large membership level Amanda Lanthorne, San Diego State Universtiy, representing medium membership level Rebekah Irwin, Middlebury College, representing small membership level Dylan McDonald, Center for Sacramento History, representing very small membership level Christine Di Bella, (ArchivesSpace Program Manager), ex officio -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Mon Mar 26 19:21:54 2018 From: gordon_daines at byu.edu (Gordon Daines) Date: Mon, 26 Mar 2018 23:21:54 +0000 Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Technical Advisory Council Message-ID: <8bdc820220b046d98641de298d7d5d07@MB7.byu.local> Colleagues, Here is a gentle reminder to self-nominate or nominate your colleagues for positions on the ArchivesSpace Technical Advisory Council. Gordon From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Gordon Daines Sent: Thursday, March 01, 2018 11:14 AM To: 'Archivesspace_Users_Group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Nominations Requested for ArchivesSpace Technical Advisory Council The ArchivesSpace Governance Board is seeking nominations to fill 7 vacancies on the ArchivesSpace Technical Advisory Council (TAC). Nominees should be presently employed at an ArchivesSpace member institution (please refer to the categorized member list at: http://archivesspace.org/community/whos-using-archivesspace/). They may also be employees of a current Registered Service Provider (see: http://archivesspace.org/registered-service-providers/current-rsps/). Nominations may be made only by ArchivesSpace member representatives. All other staff of ArchivesSpace member organizations may submit nominations through their Member Representative. Member representatives are encouraged to nominate persons from their institution or from other institutions who are experienced with some of the activities assigned to TAC and who are capable of participating on a regular basis throughout their term of service. Self-nominations are also welcome. Nominations must be received by 9:00 p.m. EDT Friday, April 15, 2018. The Nominations Committee will review all nominations and recommend appointments to the Governance Board for approval. TAC (http://www.archivesspace.org/technicaladvisory) is a critical part of the ArchivesSpace community, having responsibility for providing technical guidance to individuals or organizations contributing to application development, to the User Advisory Council, and to the ArchivesSpace Governance Board. TAC's current activities include: * developing a community of code committers, including helping to establish guidelines for contributing code and reviewing contributions, * reviewing enhancements and priorities and testing in collaboration with the User Advisory Council, * providing support for migrating data to ArchivesSpace from other systems and support for importing and exporting data such as EAD, MARCXML, CSV * documenting and assisting with resolving bugs identified in the application, * identifying integration points for ArchivesSpace with other systems (e.g. digital asset management systems, patron and request management systems, etc.), creating resources to assist the community with integration work and, for specific integrations, developing technical requirements, and * updating technical documentation. Sub-teams will be established within TAC to address the areas identified above, as well other activity areas identified subsequently. Nominees must have sufficient knowledge of application development methods, architectures and coding practices to participate in and lead some of the identified activities. Nominees with experience in open source projects, developing web applications (particularly using Ruby on Rails and Sinatra), software testing, or interest in those areas, are especially welcome. The anticipated time commitment for each appointee is expected to be two hours per week on average. The term of service will be July 1, 2018-June 30, 2020. Each new appointee will be eligible to have her/his appointment renewed for an additional two-year term, i.e., July 1, 2020-June 30, 2022. To nominate a candidate for the ArchivesSpace Technical Advisory Council, please identify the person and her/his organization in the form below, indicate the areas of activity to which the nominee is prepared to contribute. Again, self nominations are welcome. Return the completed form via email to ArchivesSpace Program Manager (Christine Di Bella) at christine.dibella at lyrasis.org, who will collect nominations on behalf of the ArchivesSpace Nominating Committee. All nominations must be submitted by 9:00 p.m. EDT Friday, April 15, 2018. Thank you for your participation in this important process, which is an essential part of our identity and operations as a community-based software organization. Respectfully, J. Gordon Daines III Brigham Young University Chair, and Governance Board member On behalf of Nominating Committee members: J. Gordon Daines III, Brigham Young University Chair, and Governance Board member Max Eckard, University of Michigan, Chair of Technical Advisory Council Suzanne Stasiulatis, Pennsylvania Historical and Museum Commission, Chair of User Advisory Council Jordon Steele, Johns Hopkins University, representing very large membership level Amanda Focke, Rice University, representing large membership level Amanda Lanthorne, San Diego State Universtiy, representing medium membership level Rebekah Irwin, Middlebury College, representing small membership level Dylan McDonald, Center for Sacramento History, representing very small membership level Christine Di Bella, (ArchivesSpace Program Manager), ex officio ________________________________ Nominee's Name: ______________________________________________ Nominee's Organization: ______________________________________________ Indicate all areas to which the nominee might contribute: ___Managing/endorsing/eliciting code contributions ___Bug fixes ___Technical documentation ___Program architecture and integrations with other software ___Migration issues, including import/exports and API design and implementation ___Application testing -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Mar 27 11:09:00 2018 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 27 Mar 2018 15:09:00 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 2.3.2 released Message-ID: Hello ArchivesSpace members, The ArchivesSpace program team is pleased to announce the availability of v2.3.2. This minor release contains several community pull requests and bug fixes. You can download this release at https://github.com/archivesspace/archivesspace/releases/tag/v2.3.2. Please note that while we were originally planning to put out a larger release in March, we have identified some search, indexing and infrastructure issues that we consider necessary to address before continuing to add more functionality to the application. As such we are postponing our next major release until later in the year and will be updating the roadmap later this week to reflect this. While the roadmap always represents our best estimate as to what will get accomplished in a particular timeframe, sometimes we get thrown an unexpected curveball and this is one of them. You'll see some additional messages from us in the coming weeks about progress on the issues to be addressed. Thanks for your patience as we do this important work to improve everyone's ArchivesSpace experience. Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not already upgraded to 2.3.0 or 2.3.1, we would recommend going directly to 2.3.2, but if you have already upgraded recently and would find it difficult to upgrade again so soon, we suggest upgrading to this release only if you need one of its specific changes right now. Thanks to the community members who contributed their time, energy, and coding skills to this release. If you have any questions or need help upgrading, please let us know. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From ccauste1 at swarthmore.edu Wed Mar 28 10:16:01 2018 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Wed, 28 Mar 2018 10:16:01 -0400 Subject: [Archivesspace_Users_Group] Request for comments: draft specification for human-readable URLs in ASpace PUI In-Reply-To: References: Message-ID: Last chance to review on this spec - your comments and feedback would be much appreciated! Celia On Thu, Mar 15, 2018 at 3:28 PM, Celia Caust-Ellenbogen < ccauste1 at swarthmore.edu> wrote: > Hello ASpacers, > > Just a reminder to please review and comment on this DRAFT specification > for creating logical and customizable title or identifier-based URLs in the > ArchivesSpace PUI: https://goo.gl/jjmtLF. Whether or not you have > specific comments, if this feature is important to you, please vote for > the ticket (JIRA ticket ANW-617 > ). > > *Please add your comments and votes by March 30th, 2018. *After that > point, Cory and I will finalize the specification and submit it to the > ArchivesSpace team. > > Cheers, > Celia and Cory > > > On Wed, Feb 28, 2018 at 8:57 AM, Celia Caust-Ellenbogen < > ccauste1 at swarthmore.edu> wrote: > >> Hello ASpacers, >> >> Please review and comment on this DRAFT specification for creating >> logical and customizable title or identifier-based URLs in the >> ArchivesSpace PUI: https://goo.gl/jjmtLF. >> >> This feature is important to me because it will improve the user >> experience, improve SEO, and foster continuity with our previous (and >> subsequent) finding aid systems. >> >> If this feature is important to you, please vote for the ticket (JIRA >> ticket ANW-617 ) if >> you haven't already done so. This will help demonstrate community interest >> when it comes time to prioritize tickets. >> >> The specification was drafted by Cory Nimer (Brigham Young University) >> and myself, with input from Lydia Tang (Michigan State University) and Mark >> Custer (Yale). >> >> Your input is much appreciated. Thank you in advance! >> >> Cheers, >> Celia and Cory >> >> -- >> Celia Caust-Ellenbogen >> Friends Historical Library of Swarthmore College >> >> 610-328-8496 <(610)%20328-8496> >> ccauste1 at swarthmore.edu >> she/her/hers >> >> >> > > > -- > Celia Caust-Ellenbogen > Friends Historical Library of Swarthmore College > > 610-328-8496 <(610)%20328-8496> > ccauste1 at swarthmore.edu > she/her/hers > > > -- Celia Caust-Ellenbogen Friends Historical Library of Swarthmore College 610-328-8496 ccauste1 at swarthmore.edu she/her/hers -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Wed Mar 28 12:39:16 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Wed, 28 Mar 2018 16:39:16 +0000 Subject: [Archivesspace_Users_Group] =?windows-1252?q?Webinar_Announcement?= =?windows-1252?q?=3A_A_Bug=92s_Life=3A_From_JIRA_to_Fix_-_April_11?= Message-ID: A Bug?s Life: From JIRA to Fix When: Wednesday, April 11, 2018 Time: 1:00 p.m. ? 2:00 p.m. ET (10:00 a.m. ? 11:00 a.m. PT) Where: Webinar at http://lyrasis.adobeconnect.com/rjtojl1sojrh/ Dial-in only option: 888-354-0094 ? Access code is 731627 No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. The webinar will be recorded and available for viewing at a later date. Webinar description: As an application fueled by the enthusiasm and energy of an incredibly proactive community, ArchivesSpace development continues to grow and evolve, sometimes faster than it can keep up. And though each release is carefully examined and tested by our Testing subteam, bugs still manage to sneak their way into the code. So, who ya gonna call? In this webinar, Jason Loeffler, Lydia Tang, Patrick Galligan, and Laney McGlohon will present an overview of an ArchivesSpace bug?s life cycle by examining the community?s approach to identifying, reporting, prioritizing, and fixing bugs. Jason will begin by describing what bugs are, Lydia will provide a demo on how anyone can submit a JIRA ticket, Patrick will share on the Development Prioritization subteam?s role, and Laney will finish by describing how the fix is designated into the code. Please feel free to bring any questions you have. Presenters: Jason Loeffler (Technology Consultant, American Academy in Rome) is a developer with over 15 years of experience working with archives and digital collections. Jason is a member of the ArchivesSpace Technical Advisory Committee, the Integrations Subcommittee, and the Development Prioritization subteam. Lydia Tang (Special Collections Archivist-Librarian, Michigan State University) has been heavily involved in ArchivesSpace activities. She currently serves on the User Advisory Council and is co-leader of the Development Prioritization subteam. She also has served on the Reports Sub-Committee and as chair of the ArchivesSpace Staff Interface Enhancement Working Group. Patrick Galligan (Digital Archivist, Rockefeller Archive Center) oversaw the RAC's migration to ArchivesSpace from Archivists Toolkit, and is a member of the ArchivesSpace Technical Advisory Committee, the Integrations Subcommittee, and the Development Prioritization subteam. Laney McGlohon (Technical Lead, ArchivesSpace) is an information scientist, software developer, librarian, and self-described data wrangler with seven years of experience working with special collections and institutional archivists. Who should attend: Everyone interested in learning about bugs and the approach our community takes to squash fix them. Questions? Please contact Kim at christine.kim at lyrasis.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From jane.labarbara at mail.wvu.edu Wed Mar 28 14:58:57 2018 From: jane.labarbara at mail.wvu.edu (Jane LaBarbara) Date: Wed, 28 Mar 2018 18:58:57 +0000 Subject: [Archivesspace_Users_Group] Export of archival objects / contents lists? Message-ID: Does anyone have a recommended way of exporting archival object information from a specific resource record in a way that results in a contents list spreadsheet? We have a lot of legacy contents list spreadsheets here, and we're working on converting and uploading them into ASpace. We don't want to have to enter data into both the spreadsheet and the ASpace record for every addendum, but we're reluctant to get rid of the spreadsheets if we can't get that information back out again in spreadsheet form should we ever need it for a future project. Thanks for your advice, Jane / Jane Metters LaBarbara Assistant Curator, West Virginia & Regional History Center West Virginia University Libraries (304) 293-0352 office jane.labarbara at mail.wvu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From benn.joseph at northwestern.edu Wed Mar 28 15:19:43 2018 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Wed, 28 Mar 2018 19:19:43 +0000 Subject: [Archivesspace_Users_Group] customizing PDF output for PUI In-Reply-To: <30D7179C-9CD4-47E7-B345-791D45031435@lib.msu.edu> References: <8ca4be47871b468aac5bf5c27c290eeb@evcspmbx04.ads.northwestern.edu> <1BAD5AB1-DDAF-46EC-A486-3973436FE4EF@virginia.edu> <30D7179C-9CD4-47E7-B345-791D45031435@lib.msu.edu> Message-ID: Thanks Steve, Lydia--I hadn't realized there was already a JIRA ticket for something along these lines. If this is ready for implementation then maybe we'll wait and see? Customizing PDF output on the staff side seemed more straightforward to us. If we do foray into customizing the PUI output we'll definitely share any documentation with the list. Best, --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Friday, March 16, 2018 10:25 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] customizing PDF output for PUI Yes, please report back! I am also interested in this as well. FYI, there is a JIRA ticket out there for reconciling some discrepancies between the two PDF options https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D258&d=DwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=LRSm7Ok0S5k74Zw9TWm_9d_SDKpu0Zkz3rkVTF4ouMk&s=LpdgFy9yGD7_dYnam1QXCT_QEZhMTZkhQ4lnPBFGIfQ&e= In general, it would be great to potentially crowdsource some documentation on how to customize it and perhaps address common/frequent complaints in updating the default stylesheet. Just my thoughts! Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=LRSm7Ok0S5k74Zw9TWm_9d_SDKpu0Zkz3rkVTF4ouMk&s=R1Va1zhoTz_b0R1G1ObdPXY7nxFwGBlzWZfcOwjRfso&e= From noah.huffman at duke.edu Wed Mar 28 15:22:21 2018 From: noah.huffman at duke.edu (Noah Huffman) Date: Wed, 28 Mar 2018 19:22:21 +0000 Subject: [Archivesspace_Users_Group] Export of archival objects / contents lists? In-Reply-To: References: Message-ID: Hi Jane, You might check out this Digitization Work Order plugin: https://github.com/hudmol/digitization_work_order It's designed for a more specific use case (generating scan list spreadsheets), but generally it does what you want and once you install the plugin you can run it from within the staff interface. Only a subset of the archival object metadata is exported as TSV (titles, dates, containers, barcodes, etc.). If I remember right, it does not export notes. Alternatively, there are some XSLT scripts in the wild that can produce CSV from EAD. So, to get a spreadsheet of archival object information for a resource you can: 1) Export EAD from ASpace 2) Transform EAD with XSLT to produce CSV of archival objects Here's one that I use occasionally for roundtripping archival object metadata in ASpace: https://github.com/duke-libraries/archivesspace-duke-scripts/blob/master/xslt/aspaceEAD_to_SteadyCSV.xsl There are probably some python scripts floating around as well that use the API to create CSVs of all of the archival objects in a collection/resource. A third option would be to run an SQL query against the backend database, but I find the two options above a bit easier as you'd probably have to join lots of tables in your query to get all of the metadata you'd want in your CSV. Hope this helps, -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Jane LaBarbara Sent: Wednesday, March 28, 2018 2:59 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Export of archival objects / contents lists? Does anyone have a recommended way of exporting archival object information from a specific resource record in a way that results in a contents list spreadsheet? We have a lot of legacy contents list spreadsheets here, and we're working on converting and uploading them into ASpace. We don't want to have to enter data into both the spreadsheet and the ASpace record for every addendum, but we're reluctant to get rid of the spreadsheets if we can't get that information back out again in spreadsheet form should we ever need it for a future project. Thanks for your advice, Jane / Jane Metters LaBarbara Assistant Curator, West Virginia & Regional History Center West Virginia University Libraries (304) 293-0352 office jane.labarbara at mail.wvu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From lmcphee at ucsd.edu Wed Mar 28 15:56:38 2018 From: lmcphee at ucsd.edu (McPhee, Laurel) Date: Wed, 28 Mar 2018 19:56:38 +0000 Subject: [Archivesspace_Users_Group] Export of archival objects / contents lists? In-Reply-To: References: Message-ID: Hi Jane, Yes, we do that all the time (we call it a "harvesting the EAD"), especially when a collection's container list is getting a major do-over or addition. With a bit of tech know-how, you can apply these instructions below from our tech specialist and the attached stylesheet. First, you export the EAD, but we do this all in one command line through the API: Attached is a simple xls stylesheet that can be used in conjunction with a xml parser (I use the Saxon parser http://saxon.sourceforge.net/) to transform the container list of an EAD file to CSV. It crawls through the container list and creates a row entry for each tag. It tracks the level and hierarchy via the LEVEL (the depth the c is nested) and just the position beneath other containers. It should be generic enough to work on any EAD (I think, it does use some specific checks like our Digital_File designator). You do need Java to run the XML parser and I do it from the command line but things like oXygen will let you run it from inside it (at least you used to be able to). Hope this helps and also might be of interest to others, Laurel Laurel McPhee Supervisory Archivist, Special Collections & Archives Program UC San Diego Library | * 858-534-5619 | * lmcphee at ucsd.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jane LaBarbara Sent: Wednesday, March 28, 2018 11:59 AM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: [Archivesspace_Users_Group] Export of archival objects / contents lists? Does anyone have a recommended way of exporting archival object information from a specific resource record in a way that results in a contents list spreadsheet? We have a lot of legacy contents list spreadsheets here, and we're working on converting and uploading them into ASpace. We don't want to have to enter data into both the spreadsheet and the ASpace record for every addendum, but we're reluctant to get rid of the spreadsheets if we can't get that information back out again in spreadsheet form should we ever need it for a future project. Thanks for your advice, Jane / Jane Metters LaBarbara Assistant Curator, West Virginia & Regional History Center West Virginia University Libraries (304) 293-0352 office jane.labarbara at mail.wvu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ead_to_csv.xsl Type: text/xml Size: 8251 bytes Desc: ead_to_csv.xsl URL: From laurie.arp at lyrasis.org Thu Mar 29 06:50:12 2018 From: laurie.arp at lyrasis.org (Laurie Arp) Date: Thu, 29 Mar 2018 10:50:12 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace board update Message-ID: Distributing for Carol Mandel... Dear ArchivesSpace members, I am writing to report on the ArchivesSpace Governance Board 3rd Quarter meeting, which was held in Chicago on March 19th. We were pleased to welcome back John Wilkin, who represents partner institution University of Illinois at Urbana-Champaign. Bill Mischo had been representing UIUC in John's place while he served as interim provost. We appreciate Bill's service and insight over the past year. We reviewed the continued excellent work of the Technical Advisory Council and User Advisory Council and thank the members for their dedicated participation. The Nominating Committee, chaired by Gordon Daines, is also continuing its strong work in preparing an election slate and identifying and soliciting people interested in serving on our Councils. The operations update highlighted continued member growth and enhanced opportunities for member engagement through webinars, open calls and regional forums. The operations report also spotlighted development accomplished through the work of core committers, various contractors and community members. The board is making progress on several important foundation documents. Work continues on the bylaws review and the organizational home agreement, and we reviewed several membership policies. Peter Carini chaired a committee focused on the mission and guiding principles and presented its work. The board was pleased to approve the following: ArchivesSpace Mission Statement * ArchivesSpace is a community of mutual support committed to helping cultural heritage organizations foster access to, and promote discovery of, historical records and primary sources through the provision of sustainable and highly functional software and tools. ArchivesSpace Guiding Principles 1. Develop and release ArchivesSpace software and tools in ways that are compatible with open source principles. 2. Foster a community of mutual support that makes it possible for users to help each other and themselves. 3. Establish and maintain membership and governance structures that ensure participation of diverse cultural heritage organizations, regardless of type, size, or geographic location. 4. Develop a healthy ecosystem of partners to provide support and enhancement for ArchivesSpace that benefit a wide spectrum of users. 5. Facilitate cooperative development in compliance with best practices and responsive to archival standards. 6. Ensure the long-term sustainability and maintenance of ArchivesSpace software and tools. We are pleased to have these as way to make explicit our community's shared purpose and values. They will facilitate prioritization and decision making among the staff, governance board and councils in the years to come. In closing, I am very happy to report that the ArchivesSpace membership organization is vibrant and continuing to grow at a steady rate. The budget reports are strong and we look forward to approving a FY18-19 budget focused on further growth and development in our June meeting. Members are participating in all facets of the program and continue to be its strongest advocates. The Board welcomes your communications and comments on any and all of this, and we extend our thanks to all of you for your continuing support and ongoing contributions to the community we have created. Respectfully, Carol A. Mandel Chair, ArchivesSpace Governance Board Dean, Division of Libraries, New York University -------------- next part -------------- An HTML attachment was scrubbed... URL: From Christine.Kim at lyrasis.org Thu Mar 29 17:28:46 2018 From: Christine.Kim at lyrasis.org (Christine Kim) Date: Thu, 29 Mar 2018 21:28:46 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - March 2018 Message-ID: [ASpaceOrgHome.jpg] March 2018 Update We kicked off this month with a webinar on the Assessments Module and we can look forward to a webinar on ArchivesSpace bugs in April. Keep up to date on upcoming regional forums as program content takes shape! New stories are up on the blog, continuing a series that will provide deep insight into the TAC and UAC activities! Read on for more news! Development The ArchivesSpace program team is pleased to announce the availability of v2.3.2. This minor release contains several community pull requests and bug fixes. You can download this release at https://github.com/archivesspace/archivesspace/releases/tag/v2.3.2. Please note that while we were originally planning to put out a larger release in March, we have identified some search, indexing and infrastructure issues that we consider necessary to address before continuing to add more functionality to the application. As such we are postponing our next major release until later in the year and will be updating the roadmap later this week to reflect this. While the roadmap always represents our best estimate as to what will get accomplished in a particular timeframe, sometimes we get thrown an unexpected curveball and this is one of them. You'll see some additional messages from us in the coming weeks about progress on the issues to be addressed. Thanks for your patience as we do this important work to improve everyone's ArchivesSpace experience. Information on upgrading to a new version of ArchivesSpace is available at http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/. If you have not already upgraded to 2.3.0 or 2.3.1, we would recommend going directly to 2.3.2, but if you have already upgraded recently and would find it difficult to upgrade again so soon, we suggest upgrading to this release only if you need one of its specific changes right now. Thanks to the community members who contributed their time, energy, and coding skills to this release. If you have any questions or need help upgrading, please let us know. Upcoming Releases Curious about what's to come in future releases? Check out the roadmap: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/18710568/Roadmap The deadline by which a pull request needs to be submitted for consideration for the May 2018 release is May 18th. Pull requests submitted after the end of day on May 18 will be considered for a future release. Webinar on A Bug's Life: From JIRA to Fix: April 11 at 1-2pm ET (10-11am PT) As an application fueled by the enthusiasm and energy of an incredibly proactive community, ArchivesSpace development continues to grow and evolve, sometimes faster than it can keep up. And though each release is carefully examined and tested by our Testing subteam, bugs still manage to sneak their way into the code. So, who ya gonna call? In this webinar, Jason Loeffler, Lydia Tang, Patrick Galligan, and Laney McGlohon will present an overview of an ArchivesSpace bug's life cycle by examining the community's approach to identifying, reporting, prioritizing, and fixing bugs. Jason will begin by describing what bugs are, Lydia will provide a demo on how anyone can submit a JIRA ticket, Patrick will share on the Development Prioritization subteam's role, and Laney will finish by describing how the fix is designated into the code. Please join us on April 11, 2018 at 1-2pm EST (10-11am PST) as Jason, Lydia, Patrick, and Laney share an overview of an ArchivesSpace bug's life cycle. Please feel free to bring any questions you have. The webinar will be available through: http://lyrasis.adobeconnect.com/rjtojl1sojrh/ and the recording will be available at a later date on the ArchivesSpace YouTube channel: https://www.youtube.com/channel/UCxR6D-UlSx6N6UWTeqHTjzA. No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. If you have any questions about this webinar, please contact Kim at christine.kim at lyrasis.org. We look forward to seeing you at the webinar! Save the date for upcoming web events! Formal announcements to follow. * Webinar: A Bug's Life: From JIRA to Fix [April 11, 1-2pm ET / 10-11am PT] * Webinar: A History of the Finding Aid [May 16, 1-2pm ET, 10-11am PT] * Open Members Call on Zoom! [May 24, 2-3pm ET / 11-noon PT] * Webinar: Transforming XSL into EAD & Importing Component Hierarchies [June 27, 1-2:30pm ET / 10-11:30am PT] Regional Forum updates Planning for our Spring and Summer regional forums is under way. Here are some of the most relevant news, dates, and links to keep you up to date on all the activity! Boston Regional Forum: May 3, 2018 at Tufts University * Lightning round proposals due March 30th: https://goo.gl/forms/0lXQz1MxAC1tETIY2 * Registration is open until May 3rd. But register by April 3rd to cast your vote for the afternoon activity: https://www.eventbrite.com/e/archivesspace-regional-forum-boston-2018-tickets-42955347601 * The program is taking shape! Keep up to date: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/455213059/Boston+Regional+Forum+-+May+2018 Southern California Regional Forum: Date TBA * Open call for working group to shape program content. Response requested by March 30th. Email Kim at christine.kim at lyrasis.org. If you have any questions (or ideas) related to the regional forums, feel free to email Kim at christine.kim at lyrasis.org. The regional forums are opportunities for our diverse ArchivesSpace members to meet up more locally to share and learn from each other through workshops, focused discussion sessions, and presentations. We look forward to having the content shaped by our community. Directory of ArchivesSpace Interest/Working Groups Are you involved in any local ArchivesSpace interest groups? Please feel free to add to this directory: https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/507314319 As a friendly reminder, anyone can create an account on the ArchivesSpace wiki. Once you create an account, you are welcome to add to the page directories or leave comments. New Stories on the Blog We have new stories posted on the blog! In All About Community, Laney McGlohon (Technical Lead, ArchivesSpace) provides an overview of the ArchivesSpace Core Committers Group. This is a continuation of a series that launches into the various subteams of the Technical Advisory Council as well as the User Advisory Council to provide insight into the variety of activities and initiatives in progress by these groups. All About Community is a blog series that highlights the many teams and groups that contribute to the growth and development of ArchivesSpace. http://archivesspace.org/category/all-about-community/ User Insights is a blog series that highlights diverse perspectives and experiences of ArchivesSpace users to enrich our entire community through shared stories, strategies, and lessons learned. http://archivesspace.org/category/user-insights/ We would love to include your ArchivesSpace stories on the blog! If you would like to contribute, please email Kim at christine.kim at lyrasis.org. Membership Update We are excited to welcome our newest members to our community! Our new members since February 24 include: * AIDS Healthcare Foundation (Los Angeles, CA) * Archiefbureau Ruerd de Vries (Netherlands) * National Library of Scotland (Edinburgh, Scotland, UK) * North Park University (Chicago, IL) * San Francisco Opera Association (San Francisco, CA) * St. Catherine University (St. Paul, MN) * Union League Club of Chicago (Chicago, IL) * University of Pennsylvania (Philadelphia, PA) As of March 29, we have 360 General members, 19 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. ________________________________ ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA's Collection Management Tools 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: 20006 bytes Desc: image003.jpg URL: From ltang5 at lib.msu.edu Fri Mar 30 15:56:49 2018 From: ltang5 at lib.msu.edu (Tang, Lydia) Date: Fri, 30 Mar 2018 19:56:49 +0000 Subject: [Archivesspace_Users_Group] customizing PDF output for PUI In-Reply-To: References: <8ca4be47871b468aac5bf5c27c290eeb@evcspmbx04.ads.northwestern.edu> <1BAD5AB1-DDAF-46EC-A486-3973436FE4EF@virginia.edu> <30D7179C-9CD4-47E7-B345-791D45031435@lib.msu.edu> Message-ID: <09B9144F-758C-4FBE-918D-F826816E426E@lib.msu.edu> Hi Benn, This ticket is just for fixing some of the inconsistencies between the two PDF output methods along the bullet points I mention in the ticket. If you, or others, have other points to add, please feel free to comment it in. These were some of the main points, but there is also opportunity for greater nitpicking. Jason Loeffler is working on the pull request and additionally, he might welcome other help/input. I still think it would be great to develop a spec for how the PDF output could be customized from the staff interface. If you and others would like to pool ideas, maybe we could come up with a big idea! Please contact me off list. Thanks! Lydia