From npwb2 at cam.ac.uk Mon Jun 3 04:18:04 2019 From: npwb2 at cam.ac.uk (Nick Butler) Date: Mon, 3 Jun 2019 08:18:04 +0000 Subject: [Archivesspace_Users_Group] Plugin problems: want the Notes section to default to open In-Reply-To: References: <2329bb709747e7653fc2af9be42e985a55c2b0e3.camel@cam.ac.uk> Message-ID: <21d585328d483ccbd13fa6778810b56f3e46cdd1.camel@cam.ac.uk> Hi Blake, Eventually I stumbled across some relevant code in the user_defined_in_basic plugin (https://github.com/hudmol/user_defined_in_basic/blob/master/frontend/assets/user_defined_in_basic.js, lines 17-18). I don't understand why the window.scrollTo(0,0); is necessary but adding it to my plugin after the .click() seems to prevent the problem - the button is clicked as if with a mouse. Would you happen to know whether this is expected behaviour, or why this seemingly (to someone with very limited JS knowledge) rather hacky fix works? Many thanks, Nick -----Original Message----- From: Blake Carver > Reply-To: Archivesspace Users Group > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Plugin problems: want the Notes section to default to open Date: Fri, 31 May 2019 16:56:03 +0000 Hi Nick, Did you ever get this one figured out? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Nick Butler Sent: Tuesday, May 21, 2019 10:10 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Plugin problems: want the Notes section to default to open Hi all, We're trying to write a plugin to default the Notes section of the new and edit resources pages to being open (i.e. as if the "Add Note" button had been clicked automatically when the page loaded). I've got a layout_head.html.erb file which loads the appropriate js file in the correct page, my difficulty just comes from getting the button to click without creating errors. Here are the contents of my js file: $(function () { var click_the_button = function () { var button = document.querySelector('.btn.btn-sm.btn-default.pull-right.add-note'); button.click(); }; click_the_button(); }); When the page loads I get the error messages seen in my attached screenshot. I've also tried requiring notes.crud.js and simply running the createTopLevelNote function, but this gives precisely the same error messages. Note that the URL for creating a new resource is https://arcspace-dev.lib.cam.ac.uk/staff/resources/new, but when the error messages appear this changes to https://arcspace-dev.lib.cam.ac.uk/staff/resources. As a test I've changed the click_the_button function to perform another task instead: var click_the_button = function () { var button = document.querySelector('.btn.btn-sm.btn-default.pull-right.add-note'); button.style.backgroundColor = 'green'; }; This works exactly as expected, changing the button colour to green. No error messages appear and the URL stays as expected. I haven't found any other plugins that do something like this (and I know very little Javascript!) so I'm at a loss here. Any advice or links to relevant documentation would be greatly appreciated. Many thanks, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Jun 3 12:31:10 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 3 Jun 2019 16:31:10 +0000 Subject: [Archivesspace_Users_Group] Call for Speakers and Topics - Member Forum 2019 Message-ID: <09F8EA4C-374F-4B59-9676-814EADE34777@lyrasis.org> Hello ArchivesSpace members, ArchivesSpace will be holding its fifth Annual Member Forum on August 2, 2019 in Austin, Texas at our member institution, University of Texas-Austin. Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. More information on the developing program is on the ArchivesSpace wiki at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/863436816/ArchivesSpace+Member+Forum+2019. The planning group is looking for presenters and topic suggestions for the forum. Anything related to ArchivesSpace is fair game and we are looking for topics and presentations that range from five minute lightning round sessions to half day workshops. There is a short Google submission form available at https://forms.gle/1xMLNbY81y1hnkL78; you can submit ideas or volunteer yourself to speak either via the form or by emailing Jessica Crouch directly. Proposals, ideas, and suggestions received by June 14 will receive priority consideration so that we can get the program squared away as soon as possible. You will receive a response by July 1. If you have any questions or other suggestions at this point, please feel free to email Jessica at jessica.crouch at lyrasis.org. Registration for the Member Forum will open soon. We look forward to seeing you in Austin! Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29058 bytes Desc: image001.jpg URL: From marci.hahnfabris at wellesley.edu Mon Jun 3 12:33:57 2019 From: marci.hahnfabris at wellesley.edu (Marci Hahn-Fabris) Date: Mon, 3 Jun 2019 12:33:57 -0400 Subject: [Archivesspace_Users_Group] Digitization Work Order Plugin for filenaming Message-ID: Hi all, Here at Wellesley, we are currently exploring using the CUID that is created by the Digitization Work Order Plugin for file naming. We have some questions about how it is working for people. Some of our questions/concerns are: - Is there a way to reset the serial #? We would like to start with a 5 digit ID, and right now it starts at 0. - Our Systems librarian would like to know where the serial # lives on the backend. - We are thinking of having our filenames be: Root (WCA for Wellesley College Archives), Collection number and CUID. An example might be: WCA_3P_cuid1234_001.tif. Are people using the actual letters "cuid" in the filename? Is there an argument for or against that? One plus I can see is you can search "cuid1234" and find the exact item/archival object. But I know it can also be changed. - We also want to make sure the CUID is really, truly a unique ID, no chance of duplication? We realized we can't manually add a CUID and then have the plugin recognize that, all CUIDs would need to be created via the plugin. - We also wonder if anyone has had problems with the plugin as they move to newer versions of ArchivesSpace? thanks for any help you can give us! Marci *Marci Hahn-FabrisDigital Collections LibrarianWellesley College781.283.3331* *marci.hahnfabris at wellesley.edu * she/her/hers ***Many people want your password so they can steal your information. If you receive an email asking you to send your password or directs you to a page that is NOT in the wellesley.edu domain, DO NOT provide your password. LTS will never ask for your passwords -- when in doubt, contact the LTS Computing Help Desk.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From ccauste1 at swarthmore.edu Mon Jun 3 13:17:52 2019 From: ccauste1 at swarthmore.edu (Celia Caust-Ellenbogen) Date: Mon, 3 Jun 2019 13:17:52 -0400 Subject: [Archivesspace_Users_Group] EAC-CPF in ASpace Message-ID: Hi folks, We are just starting to think about implementing EAC-CPF at our repository. ASpace's agents module supports some EAC-CPF elements, but it seems like some are missing, or maybe I am just not seeing how to utilize them. (For example, how to create a if the resource is owned by another repository and not in my ASpace instance?) I would love to hear from other folks who are using EAC-CPF. Are you using ASpace to create the records? Also curious if you are using a different interface besides ASpace (and besides SNAC) to display the records? Best, Celia -- Celia Caust-Ellenbogen (she/her/hers ) Friends Historical Library of Swarthmore College | Swarthmore College Archives ccauste1 at swarthmore.edu 610-328-8496 -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Jun 4 16:45:02 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 4 Jun 2019 20:45:02 +0000 Subject: [Archivesspace_Users_Group] EAC-CPF in ASpace In-Reply-To: References: Message-ID: Hi Celia, Others can address how they?re working around the limits of current ArchivesSpace support for EAC-CPF, but I?ll just mention what?s planned for the application in terms of fuller EAC-CPF support, including the ability to exchange records with SNAC. A community specification, authored by Cory Nimer, Brad Westbrook, and Sue Luftschein, was circulated about 2 years ago and finalized later that year. You can see the specification components and its updates in the comments to this JIRA issue: https://archivesspace.atlassian.net/browse/ANW-429. We?ve been slowly building in some pieces of the functionality requested, such as the additional control over merging agents which came out in 2.5.2, and are currently working on the data model changes that form the core of what?s needed. That work includes adding the fields to the underlying database, adding API endpoints, updating the views in the staff and public interfaces, and updating the importers and exporters. The data model work will appear in the application later this year. On a parallel but related track, representatives of SNAC are working on the mapping between SNAC and ArchivesSpace. In all likelihood, the first goal once the data model changes have been made to ArchivesSpace and the ArchivesSpace/SNAC mapping is done is to build a plugin (or plugins) for basic importing and exporting of these records between the two systems. Hope that helps, 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 Celia Caust-Ellenbogen Sent: Monday, June 3, 2019 1:18 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] EAC-CPF in ASpace Hi folks, We are just starting to think about implementing EAC-CPF at our repository. ASpace's agents module supports some EAC-CPF elements, but it seems like some are missing, or maybe I am just not seeing how to utilize them. (For example, how to create a if the resource is owned by another repository and not in my ASpace instance?) I would love to hear from other folks who are using EAC-CPF. Are you using ASpace to create the records? Also curious if you are using a different interface besides ASpace (and besides SNAC) to display the records? Best, Celia -- Celia Caust-Ellenbogen (she/her/hers) Friends Historical Library of Swarthmore College | Swarthmore College Archives ccauste1 at swarthmore.edu 610-328-8496 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 6608 bytes Desc: image001.jpg URL: From christine.dibella at lyrasis.org Tue Jun 4 16:49:56 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 4 Jun 2019 20:49:56 +0000 Subject: [Archivesspace_Users_Group] merge Top Container functionality In-Reply-To: References: Message-ID: Hi Benn, Merging Top Containers has been on our development roadmap, and we know it is of great interest to a number of people in the community, but until recently we had not been able to identify a developer to take this on. We've now determined that we will be able to work on this after some of the large projects related to agents and infrastructure that are currently in progress have been completed. We're aiming for this functionality to be available in the application later this year. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Benn Joseph Sent: Tuesday, May 21, 2019 5:22 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] merge Top Container functionality Hi all, I'm curious whether there are any updates re: the ability to merge Top Containers. It looks like ANW-462 deals specifically with this but I can't tell if there has been much activity on it lately: https://archivesspace.atlassian.net/browse/ANW-462?atlOrigin=eyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9 Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Wednesday, January 16, 2019 12:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I second the ability to merge containers! ? Lydia From: on behalf of Valerie Addonizio Reply-To: Archivesspace Users Group Date: Wednesday, January 16, 2019 at 1:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I know that the comment period is closed, but this seemed like a logical place to ask whether the idea of container merging functionality was considered as part of this effort (I know it is not in the scope of work, but was it considered and not selected?) and whether other institutions are in need of such functionality? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Thursday, December 20, 2018 4:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace community: Apologies for the length of this. I?ll try to address a lot of comments, but not all! Please let me know if (as they may well do) my elaborations only elicit more questions! In general, most of these proposals are derived from facing problems of scale. Harvard has 30 repositories and over 200 users of ArchivesSpace. Others have to do with managing ?medium rare? materials? locations and containers in ArchivesSpace. (Medium-rare is a tongue-in-cheek term used to cover materials that might exist in multiple manifestations but that have archival or rare characteristics or treatment. Examples include entire libraries ingested into an archives, author?s own copies of their books, annotated books, or the record copy of serials or reports kept by institutional archives.) ? Multi-field top container indicators Some commenters wondered if the multiple fields were to accommodate child containers. To clarify, the suggestion was to facilitate parsing top container identifiers. As a few commenters have surmised, this is to cope with legacy numbers. These are especially common on medium-rare materials. One suggestion was to use a sort algorithm that would obviate the need for separated fields for data. However, because there would be is more than one algorithm necessary over the installation, such a solution would require an added field to identify the algorithm and probably a third field retain a value derived by the algorithm to be sorted alphanumerically. Thus, the direct 3-field solution seems simpler. (A 4-field suggestion was mooted in the committee as potentially more useful communally.) It does occur to me that there just might not be enough really old, really big repositories with lots of legacy identifiers in the ArchivesSpace community for the parsing of legacy numbers to be a common problem. I appreciate the recognition that a plug-in might be needed instead, but it would be worth hearing from any repositories with similar issues. ? Container and location profiles by repository We were envisioning a one-to-one profile-to-repository scenario. Due to the ArchivesSpace staff user interface requirement that one identify only a single repository at login, it is extremely easy for users to forget the impact they might have beyond their repository if they change or delete a shared record. We have already experienced mistaken mergers and deletions of agents due to the design of AS staff user interface that does not allow one to see where the record may be linked beyond their repository. For this reason, it is wise to be able to limit changes and deletions of location profiles and container profiles impact to the same chosen repository. ? Inactive As Maureen wisely intuited, inactive locations are necessary to recording a complete location history. However, there are additional use cases. When a repository is renovating, for example (as is happening now at the Schlesinger Library) the shelves in a location may be inactive for a time and become active again when the building re-opens. Other scenarios include water intrusion or other occasions when a smaller sub-set of shelves may have to become inactive until repairs are completed and tested before the shelving can again come into use. Because inactive locations are to be eliminated by default from search results, we can prevent them from overwhelming staff members? search results or sending staff to unusable locations. ? Notes in containers and locations Notes are for dedicated shelving or rehousing issues. Notes on containers may contain things like ?Label falling off? ?Acidic-needs replacing? ?Acid box replaced with acid-free box 2017-06-08? ?Not on shelf 2015-10-10?. Notes on locations may contain things like ?only use as last resort?overhead drip pan makes retrieval difficult? ?reserved for outgoing transfers until 2019-01-01?. In locations especially, we would expect the reason for a location becoming inactive might be noted. ?Made inactive because next to heating duct?do not reactivate?. ? Bibliographic record IDs in containers This data would allow for more sustainable interoperability between systems and more flexibility in workflows. Especially with medium-rare materials, the physical item?s location might need to be recorded before description is finalized, and if the description is to be created in foreign system and ingested to ArchivesSpace, hooking up the container and location will be problematic. In this scenario, a resource with initial description in a bibliographic system could be placed on an archives? shelf, and the description, once completed in the ILS, could be ingested via MARC XML ingest for example. After the resource is ingested, the ILS bibliographic record number could be searched in the containers to link the container to the resource. When an ILS system migrates, it is unlikely that the migration would maintain obsolte holding or item system numbers, but it is common to migrate with obsolete bibliographic system record numbers embedded into the new system. Should there be a need to re-migrate holdings or items from ArchivesSpace to a new ILS, bibliographic record numbers would ensure continuity. Thanks for reading! Kate From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Maureen Callahan Sent: Monday, December 17, 2018 2:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input A million thanks to folks from Harvard for showing leadership and investing to improve the experience of the software for all of us. I was having pleasant flashbacks to my days at Yale working through the original specifications for the container management functionality -- what it all means, what it should do, how this will improve the experience for archivists and patrons, and how to abstract all of this work to more general archival and data management principles. It's such fun, hard work! Generally speaking, it would be really helpful if user stories gave a better sense of what you want to accomplish instead of what you want to see on the screen. For some of this, I had a hard time understanding where you were coming from and I think it's possible that there are different ways of accomplishing what you've laid out. "As an W, I want to have X feature, so that Y behavior happens in Z way and lets me do my work in ABC fashion." I think that many of the goals behind this proposal are sound, but that perhaps there's too narrow an approach to solutions to meet these goals. Developers might find better ways to address the problems you've identified. 1. Hell YES there need to be easier ways to browse/sort/find locations!!!! 2. I agree that it would be useful to have the option to filter locations/container profiles by the repository they tend to belong to and that this should also be extensible so that it's easy to change this information after a move or administrative change. I sort of remember that folks at NYU talked about this as a possible outcome in the beginning of their location profile work, so it may be worth talking with them about the best way to think about it and any reasons they might have opted to not associate a repository with a location profile. 3. Lora did some nice work with search to make it possible to see the entire breadcrumb trail of where a search result comes from (the hierarchies of AOs within a resource). I'm thinking that perhaps you just want the same thing to happen when you look at the associated archival objects / accessions in a top container, rather than adding another column (resource) to the search result. 4. As someone who has had to do a lot of systems migrations that involved moving heterogenous data into more structured places, I get really nervous about a notes field for either the location or the top container. If there are common types of information that end up in this field, it may be worth considering adding more structured fields to either the location or the location profile or container or container profile so that it can be better managed, queried, and kept tidy & up-to-date. What's the scenario by which someone would actually look at this notes field? What do you want to go in there? 5. Soooooo tell me more about this inactive location idea. AFAIR, ArchivesSpace doesn't keep an audit trail of previous locations. What's the value of knowing that inactive locations exist when there aren't containers living in those locations and there's no way to see that those locations perviously held containers? 6. This may be implicit in your proposal, but it sounds like you want "repository" to be a multi-valued field in your location profiles and your container profiles. Paige boxes, for instance, will probably end up being associated with every repository. 7. I was initially a bit perplexed by the request to add additional fields for container indicators, but reading between the lines, my guess is that you want to be able to sort them properly in various circumstances. If, for instance, you have boxes 2, 2a, and 3, you want to be able to make sure that when you sort by indicator, they appear in this order. That's a great goal! But I think that you might want to state this goal instead of stating one possible outcome. I definitely DO NOT want a three-part container indicator because who knows what kind of crap people will put in those fields and they could potentially be a nightmare to clean up. Plus, it would have to account for every possible heterodox way that people design their container indicators -- or just default to Harvard's scheme, which... I mean, this is software for the whole community. Instead, I would suggest making the requirement that you want for alphanumeric characters to sort properly and clever developers can come up with the best way to do this. That seems like a more elegant solution than changing the data model. 8. YES BIBIDs!!!! But my read is that a BIBID is a control number for intellectual description, not for holdings. I know that folks are currently putting BIBIDs in user-defined fields in the resource record, and it would be great for those to have a canonical spot to help with systems integrations. I would much rather see the addition of a BIBID to the resource record, which can then be displayed with the top container by the system if desired (although why?). There's already a field for the ILS holdings ID to go with the top container. Thanks all, Maureen -- Maureen Callahan Sophia Smith Collection Archivist Smith College Special Collections Northampton, Massachusetts 01063 413 585 2981 mcallahan at smith.edu Pronouns: she/her/hers Smith College Special Collections is now housed at Young Library. Learn more about renovations to Neilson Library here. On Mon, Dec 17, 2018 at 12:42 PM Rackley, Marilyn > wrote: Dear all, Please remember to review the Harvard Library proposal for container management enhancements and submit feedback by Wednesday, December 19, 2018. See the email below for more information. In case people are not able to access the attachment, the proposal can also be accessed through this link: https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-3Fid-3D14-2D6CFEAATfwYc1JZoAmCSD3CQVW7p3b3&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=bInpBUPKeV0QKr-JQH2j9yaDdfw8v580qBTSZmMBwx4&e=. We really appreciate all the comments provided so far. Best, Marilyn From: Rackley, Marilyn Sent: Monday, December 3, 2018 9:36 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace Community, The Harvard Library has been reviewing container and location management functionality in ArchivesSpace and we are proposing to make enhancements to this functionality that we would like to contribute to the core code. With these enhancements, we hope to make finding, viewing, and updating information related to containers and locations in the staff interface more efficient and effective. We have completed the draft proposal attached to this email and we are now asking for community review and feedback. The proposal includes the rationale for the changes, a list of database fields to be added, user stories describing the specific changes we are proposing, and mockups of the related updates to the staff interface. Please note that in the proposal, certain changes are designated as being a lower priority; it is possible that we may not be able to complete all the proposed changes at this time. If you have questions or feedback, please email me at marilyn_rackley at harvard.edu and/or Robin Wendler at robin_wendler at harvard.edu. We will be accepting comments through Wednesday, December 19, 2018. We look forward to receiving community input. Best, Marilyn Marilyn Rackley Aeon Project Manager and Digital Librarian Harvard Library | 617.496.4043 marilyn_rackley at harvard.edu _______________________________________________ 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=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=FB4KqB3TcRmkmN9zqyRn6s9tpjfpDzM3U9XYqkb3Ock&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=FB4KqB3TcRmkmN9zqyRn6s9tpjfpDzM3U9XYqkb3Ock&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From benn.joseph at northwestern.edu Tue Jun 4 17:12:18 2019 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Tue, 4 Jun 2019 21:12:18 +0000 Subject: [Archivesspace_Users_Group] merge Top Container functionality In-Reply-To: References: Message-ID: <83fc16d18d8c45489acdcd2ce7111b94@evcspmbx04.ads.northwestern.edu> This is great news--thanks Christine! --Benn -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Christine Di Bella Sent: Tuesday, June 04, 2019 3:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] merge Top Container functionality Hi Benn, Merging Top Containers has been on our development roadmap, and we know it is of great interest to a number of people in the community, but until recently we had not been able to identify a developer to take this on. We've now determined that we will be able to work on this after some of the large projects related to agents and infrastructure that are currently in progress have been completed. We're aiming for this functionality to be available in the application later this year. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Benn Joseph Sent: Tuesday, May 21, 2019 5:22 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] merge Top Container functionality Hi all, I'm curious whether there are any updates re: the ability to merge Top Containers. It looks like ANW-462 deals specifically with this but I can't tell if there has been much activity on it lately: https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D462-3FatlOrigin-3DeyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=JsdQrq3-4cQNlnTtW_etByY6HRDT9SoyTiaqfiwb5y0&s=I-fDdOiQzR-Odd9-5gE0AXg2ze9rU3Euw_qY32UHQVc&e= Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University http://www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Wednesday, January 16, 2019 12:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I second the ability to merge containers! ? Lydia From: on behalf of Valerie Addonizio Reply-To: Archivesspace Users Group Date: Wednesday, January 16, 2019 at 1:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I know that the comment period is closed, but this seemed like a logical place to ask whether the idea of container merging functionality was considered as part of this effort (I know it is not in the scope of work, but was it considered and not selected?) and whether other institutions are in need of such functionality? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Thursday, December 20, 2018 4:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace community: Apologies for the length of this. I?ll try to address a lot of comments, but not all! Please let me know if (as they may well do) my elaborations only elicit more questions! In general, most of these proposals are derived from facing problems of scale. Harvard has 30 repositories and over 200 users of ArchivesSpace. Others have to do with managing ?medium rare? materials? locations and containers in ArchivesSpace. (Medium-rare is a tongue-in-cheek term used to cover materials that might exist in multiple manifestations but that have archival or rare characteristics or treatment. Examples include entire libraries ingested into an archives, author?s own copies of their books, annotated books, or the record copy of serials or reports kept by institutional archives.) ? Multi-field top container indicators Some commenters wondered if the multiple fields were to accommodate child containers. To clarify, the suggestion was to facilitate parsing top container identifiers. As a few commenters have surmised, this is to cope with legacy numbers. These are especially common on medium-rare materials. One suggestion was to use a sort algorithm that would obviate the need for separated fields for data. However, because there would be is more than one algorithm necessary over the installation, such a solution would require an added field to identify the algorithm and probably a third field retain a value derived by the algorithm to be sorted alphanumerically. Thus, the direct 3-field solution seems simpler. (A 4-field suggestion was mooted in the committee as potentially more useful communally.) It does occur to me that there just might not be enough really old, really big repositories with lots of legacy identifiers in the ArchivesSpace community for the parsing of legacy numbers to be a common problem. I appreciate the recognition that a plug-in might be needed instead, but it would be worth hearing from any repositories with similar issues. ? Container and location profiles by repository We were envisioning a one-to-one profile-to-repository scenario. Due to the ArchivesSpace staff user interface requirement that one identify only a single repository at login, it is extremely easy for users to forget the impact they might have beyond their repository if they change or delete a shared record. We have already experienced mistaken mergers and deletions of agents due to the design of AS staff user interface that does not allow one to see where the record may be linked beyond their repository. For this reason, it is wise to be able to limit changes and deletions of location profiles and container profiles impact to the same chosen repository. ? Inactive As Maureen wisely intuited, inactive locations are necessary to recording a complete location history. However, there are additional use cases. When a repository is renovating, for example (as is happening now at the Schlesinger Library) the shelves in a location may be inactive for a time and become active again when the building re-opens. Other scenarios include water intrusion or other occasions when a smaller sub-set of shelves may have to become inactive until repairs are completed and tested before the shelving can again come into use. Because inactive locations are to be eliminated by default from search results, we can prevent them from overwhelming staff members? search results or sending staff to unusable locations. ? Notes in containers and locations Notes are for dedicated shelving or rehousing issues. Notes on containers may contain things like ?Label falling off? ?Acidic-needs replacing? ?Acid box replaced with acid-free box 2017-06-08? ?Not on shelf 2015-10-10?. Notes on locations may contain things like ?only use as last resort?overhead drip pan makes retrieval difficult? ?reserved for outgoing transfers until 2019-01-01?. In locations especially, we would expect the reason for a location becoming inactive might be noted. ?Made inactive because next to heating duct?do not reactivate?. ? Bibliographic record IDs in containers This data would allow for more sustainable interoperability between systems and more flexibility in workflows. Especially with medium-rare materials, the physical item?s location might need to be recorded before description is finalized, and if the description is to be created in foreign system and ingested to ArchivesSpace, hooking up the container and location will be problematic. In this scenario, a resource with initial description in a bibliographic system could be placed on an archives? shelf, and the description, once completed in the ILS, could be ingested via MARC XML ingest for example. After the resource is ingested, the ILS bibliographic record number could be searched in the containers to link the container to the resource. When an ILS system migrates, it is unlikely that the migration would maintain obsolte holding or item system numbers, but it is common to migrate with obsolete bibliographic system record numbers embedded into the new system. Should there be a need to re-migrate holdings or items from ArchivesSpace to a new ILS, bibliographic record numbers would ensure continuity. Thanks for reading! Kate From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Maureen Callahan Sent: Monday, December 17, 2018 2:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input A million thanks to folks from Harvard for showing leadership and investing to improve the experience of the software for all of us. I was having pleasant flashbacks to my days at Yale working through the original specifications for the container management functionality -- what it all means, what it should do, how this will improve the experience for archivists and patrons, and how to abstract all of this work to more general archival and data management principles. It's such fun, hard work! Generally speaking, it would be really helpful if user stories gave a better sense of what you want to accomplish instead of what you want to see on the screen. For some of this, I had a hard time understanding where you were coming from and I think it's possible that there are different ways of accomplishing what you've laid out. "As an W, I want to have X feature, so that Y behavior happens in Z way and lets me do my work in ABC fashion." I think that many of the goals behind this proposal are sound, but that perhaps there's too narrow an approach to solutions to meet these goals. Developers might find better ways to address the problems you've identified. 1. Hell YES there need to be easier ways to browse/sort/find locations!!!! 2. I agree that it would be useful to have the option to filter locations/container profiles by the repository they tend to belong to and that this should also be extensible so that it's easy to change this information after a move or administrative change. I sort of remember that folks at NYU talked about this as a possible outcome in the beginning of their location profile work, so it may be worth talking with them about the best way to think about it and any reasons they might have opted to not associate a repository with a location profile. 3. Lora did some nice work with search to make it possible to see the entire breadcrumb trail of where a search result comes from (the hierarchies of AOs within a resource). I'm thinking that perhaps you just want the same thing to happen when you look at the associated archival objects / accessions in a top container, rather than adding another column (resource) to the search result. 4. As someone who has had to do a lot of systems migrations that involved moving heterogenous data into more structured places, I get really nervous about a notes field for either the location or the top container. If there are common types of information that end up in this field, it may be worth considering adding more structured fields to either the location or the location profile or container or container profile so that it can be better managed, queried, and kept tidy & up-to-date. What's the scenario by which someone would actually look at this notes field? What do you want to go in there? 5. Soooooo tell me more about this inactive location idea. AFAIR, ArchivesSpace doesn't keep an audit trail of previous locations. What's the value of knowing that inactive locations exist when there aren't containers living in those locations and there's no way to see that those locations perviously held containers? 6. This may be implicit in your proposal, but it sounds like you want "repository" to be a multi-valued field in your location profiles and your container profiles. Paige boxes, for instance, will probably end up being associated with every repository. 7. I was initially a bit perplexed by the request to add additional fields for container indicators, but reading between the lines, my guess is that you want to be able to sort them properly in various circumstances. If, for instance, you have boxes 2, 2a, and 3, you want to be able to make sure that when you sort by indicator, they appear in this order. That's a great goal! But I think that you might want to state this goal instead of stating one possible outcome. I definitely DO NOT want a three-part container indicator because who knows what kind of crap people will put in those fields and they could potentially be a nightmare to clean up. Plus, it would have to account for every possible heterodox way that people design their container indicators -- or just default to Harvard's scheme, which... I mean, this is software for the whole community. Instead, I would suggest making the requirement that you want for alphanumeric characters to sort properly and clever developers can come up with the best way to do this. That seems like a more elegant solution than changing the data model. 8. YES BIBIDs!!!! But my read is that a BIBID is a control number for intellectual description, not for holdings. I know that folks are currently putting BIBIDs in user-defined fields in the resource record, and it would be great for those to have a canonical spot to help with systems integrations. I would much rather see the addition of a BIBID to the resource record, which can then be displayed with the top container by the system if desired (although why?). There's already a field for the ILS holdings ID to go with the top container. Thanks all, Maureen -- Maureen Callahan Sophia Smith Collection Archivist Smith College Special Collections Northampton, Massachusetts 01063 413 585 2981 mcallahan at smith.edu Pronouns: she/her/hers Smith College Special Collections is now housed at Young Library. Learn more about renovations to Neilson Library here. On Mon, Dec 17, 2018 at 12:42 PM Rackley, Marilyn > wrote: Dear all, Please remember to review the Harvard Library proposal for container management enhancements and submit feedback by Wednesday, December 19, 2018. See the email below for more information. In case people are not able to access the attachment, the proposal can also be accessed through this link: https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-3Fid-3D14-2D6CFEAATfwYc1JZoAmCSD3CQVW7p3b3&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=bInpBUPKeV0QKr-JQH2j9yaDdfw8v580qBTSZmMBwx4&e=. We really appreciate all the comments provided so far. Best, Marilyn From: Rackley, Marilyn Sent: Monday, December 3, 2018 9:36 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace Community, The Harvard Library has been reviewing container and location management functionality in ArchivesSpace and we are proposing to make enhancements to this functionality that we would like to contribute to the core code. With these enhancements, we hope to make finding, viewing, and updating information related to containers and locations in the staff interface more efficient and effective. We have completed the draft proposal attached to this email and we are now asking for community review and feedback. The proposal includes the rationale for the changes, a list of database fields to be added, user stories describing the specific changes we are proposing, and mockups of the related updates to the staff interface. Please note that in the proposal, certain changes are designated as being a lower priority; it is possible that we may not be able to complete all the proposed changes at this time. If you have questions or feedback, please email me at marilyn_rackley at harvard.edu and/or Robin Wendler at robin_wendler at harvard.edu. We will be accepting comments through Wednesday, December 19, 2018. We look forward to receiving community input. Best, Marilyn Marilyn Rackley Aeon Project Manager and Digital Librarian Harvard Library | 617.496.4043 marilyn_rackley at harvard.edu _______________________________________________ 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=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=FB4KqB3TcRmkmN9zqyRn6s9tpjfpDzM3U9XYqkb3Ock&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=FB4KqB3TcRmkmN9zqyRn6s9tpjfpDzM3U9XYqkb3Ock&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=JsdQrq3-4cQNlnTtW_etByY6HRDT9SoyTiaqfiwb5y0&s=tAwZZRIm-RwqtisDdGvn0YcWEWv4iMdXZBZxrfIOWyc&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=JsdQrq3-4cQNlnTtW_etByY6HRDT9SoyTiaqfiwb5y0&s=tAwZZRIm-RwqtisDdGvn0YcWEWv4iMdXZBZxrfIOWyc&e= From Kevin.Clair at du.edu Tue Jun 4 19:47:46 2019 From: Kevin.Clair at du.edu (Kevin Clair) Date: Tue, 4 Jun 2019 23:47:46 +0000 Subject: [Archivesspace_Users_Group] merge Top Container functionality Message-ID: Thanks, Christine! Will there be similar functionality for Container Profiles? Someone at our shop asked me about that the other day and I saw there's a ticket for it at https://archivesspace.atlassian.net/browse/ANW-550, but it looks like it hasn't been updated since last summer. -k ?On 6/4/19, 2:50 PM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Christine Di Bella" wrote: Hi Benn, Merging Top Containers has been on our development roadmap, and we know it is of great interest to a number of people in the community, but until recently we had not been able to identify a developer to take this on. We've now determined that we will be able to work on this after some of the large projects related to agents and infrastructure that are currently in progress have been completed. We're aiming for this functionality to be available in the application later this year. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Benn Joseph Sent: Tuesday, May 21, 2019 5:22 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] merge Top Container functionality Hi all, I'm curious whether there are any updates re: the ability to merge Top Containers. It looks like ANW-462 deals specifically with this but I can't tell if there has been much activity on it lately: https://archivesspace.atlassian.net/browse/ANW-462?atlOrigin=eyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9 Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Wednesday, January 16, 2019 12:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I second the ability to merge containers! ? Lydia From: on behalf of Valerie Addonizio Reply-To: Archivesspace Users Group Date: Wednesday, January 16, 2019 at 1:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I know that the comment period is closed, but this seemed like a logical place to ask whether the idea of container merging functionality was considered as part of this effort (I know it is not in the scope of work, but was it considered and not selected?) and whether other institutions are in need of such functionality? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Thursday, December 20, 2018 4:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace community: Apologies for the length of this. I?ll try to address a lot of comments, but not all! Please let me know if (as they may well do) my elaborations only elicit more questions! In general, most of these proposals are derived from facing problems of scale. Harvard has 30 repositories and over 200 users of ArchivesSpace. Others have to do with managing ?medium rare? materials? locations and containers in ArchivesSpace. (Medium-rare is a tongue-in-cheek term used to cover materials that might exist in multiple manifestations but that have archival or rare characteristics or treatment. Examples include entire libraries ingested into an archives, author?s own copies of their books, annotated books, or the record copy of serials or reports kept by institutional archives.) ? Multi-field top container indicators Some commenters wondered if the multiple fields were to accommodate child containers. To clarify, the suggestion was to facilitate parsing top container identifiers. As a few commenters have surmised, this is to cope with legacy numbers. These are especially common on medium-rare materials. One suggestion was to use a sort algorithm that would obviate the need for separated fields for data. However, because there would be is more than one algorithm necessary over the installation, such a solution would require an added field to identify the algorithm and probably a third field retain a value derived by the algorithm to be sorted alphanumerically. Thus, the direct 3-field solution seems simpler. (A 4-field suggestion was mooted in the committee as potentially more useful communally.) It does occur to me that there just might not be enough really old, really big repositories with lots of legacy identifiers in the ArchivesSpace community for the parsing of legacy numbers to be a common problem. I appreciate the recognition that a plug-in might be needed instead, but it would be worth hearing from any repositories with similar issues. ? Container and location profiles by repository We were envisioning a one-to-one profile-to-repository scenario. Due to the ArchivesSpace staff user interface requirement that one identify only a single repository at login, it is extremely easy for users to forget the impact they might have beyond their repository if they change or delete a shared record. We have already experienced mistaken mergers and deletions of agents due to the design of AS staff user interface that does not allow one to see where the record may be linked beyond their repository. For this reason, it is wise to be able to limit changes and deletions of location profiles and container profiles impact to the same chosen repository. ? Inactive As Maureen wisely intuited, inactive locations are necessary to recording a complete location history. However, there are additional use cases. When a repository is renovating, for example (as is happening now at the Schlesinger Library) the shelves in a location may be inactive for a time and become active again when the building re-opens. Other scenarios include water intrusion or other occasions when a smaller sub-set of shelves may have to become inactive until repairs are completed and tested before the shelving can again come into use. Because inactive locations are to be eliminated by default from search results, we can prevent them from overwhelming staff members? search results or sending staff to unusable locations. ? Notes in containers and locations Notes are for dedicated shelving or rehousing issues. Notes on containers may contain things like ?Label falling off? ?Acidic-needs replacing? ?Acid box replaced with acid-free box 2017-06-08? ?Not on shelf 2015-10-10?. Notes on locations may contain things like ?only use as last resort?overhead drip pan makes retrieval difficult? ?reserved for outgoing transfers until 2019-01-01?. In locations especially, we would expect the reason for a location becoming inactive might be noted. ?Made inactive because next to heating duct?do not reactivate?. ? Bibliographic record IDs in containers This data would allow for more sustainable interoperability between systems and more flexibility in workflows. Especially with medium-rare materials, the physical item?s location might need to be recorded before description is finalized, and if the description is to be created in foreign system and ingested to ArchivesSpace, hooking up the container and location will be problematic. In this scenario, a resource with initial description in a bibliographic system could be placed on an archives? shelf, and the description, once completed in the ILS, could be ingested via MARC XML ingest for example. After the resource is ingested, the ILS bibliographic record number could be searched in the containers to link the container to the resource. When an ILS system migrates, it is unlikely that the migration would maintain obsolte holding or item system numbers, but it is common to migrate with obsolete bibliographic system record numbers embedded into the new system. Should there be a need to re-migrate holdings or items from ArchivesSpace to a new ILS, bibliographic record numbers would ensure continuity. Thanks for reading! Kate From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Maureen Callahan Sent: Monday, December 17, 2018 2:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input A million thanks to folks from Harvard for showing leadership and investing to improve the experience of the software for all of us. I was having pleasant flashbacks to my days at Yale working through the original specifications for the container management functionality -- what it all means, what it should do, how this will improve the experience for archivists and patrons, and how to abstract all of this work to more general archival and data management principles. It's such fun, hard work! Generally speaking, it would be really helpful if user stories gave a better sense of what you want to accomplish instead of what you want to see on the screen. For some of this, I had a hard time understanding where you were coming from and I think it's possible that there are different ways of accomplishing what you've laid out. "As an W, I want to have X feature, so that Y behavior happens in Z way and lets me do my work in ABC fashion." I think that many of the goals behind this proposal are sound, but that perhaps there's too narrow an approach to solutions to meet these goals. Developers might find better ways to address the problems you've identified. 1. Hell YES there need to be easier ways to browse/sort/find locations!!!! 2. I agree that it would be useful to have the option to filter locations/container profiles by the repository they tend to belong to and that this should also be extensible so that it's easy to change this information after a move or administrative change. I sort of remember that folks at NYU talked about this as a possible outcome in the beginning of their location profile work, so it may be worth talking with them about the best way to think about it and any reasons they might have opted to not associate a repository with a location profile. 3. Lora did some nice work with search to make it possible to see the entire breadcrumb trail of where a search result comes from (the hierarchies of AOs within a resource). I'm thinking that perhaps you just want the same thing to happen when you look at the associated archival objects / accessions in a top container, rather than adding another column (resource) to the search result. 4. As someone who has had to do a lot of systems migrations that involved moving heterogenous data into more structured places, I get really nervous about a notes field for either the location or the top container. If there are common types of information that end up in this field, it may be worth considering adding more structured fields to either the location or the location profile or container or container profile so that it can be better managed, queried, and kept tidy & up-to-date. What's the scenario by which someone would actually look at this notes field? What do you want to go in there? 5. Soooooo tell me more about this inactive location idea. AFAIR, ArchivesSpace doesn't keep an audit trail of previous locations. What's the value of knowing that inactive locations exist when there aren't containers living in those locations and there's no way to see that those locations perviously held containers? 6. This may be implicit in your proposal, but it sounds like you want "repository" to be a multi-valued field in your location profiles and your container profiles. Paige boxes, for instance, will probably end up being associated with every repository. 7. I was initially a bit perplexed by the request to add additional fields for container indicators, but reading between the lines, my guess is that you want to be able to sort them properly in various circumstances. If, for instance, you have boxes 2, 2a, and 3, you want to be able to make sure that when you sort by indicator, they appear in this order. That's a great goal! But I think that you might want to state this goal instead of stating one possible outcome. I definitely DO NOT want a three-part container indicator because who knows what kind of crap people will put in those fields and they could potentially be a nightmare to clean up. Plus, it would have to account for every possible heterodox way that people design their container indicators -- or just default to Harvard's scheme, which... I mean, this is software for the whole community. Instead, I would suggest making the requirement that you want for alphanumeric characters to sort properly and clever developers can come up with the best way to do this. That seems like a more elegant solution than changing the data model. 8. YES BIBIDs!!!! But my read is that a BIBID is a control number for intellectual description, not for holdings. I know that folks are currently putting BIBIDs in user-defined fields in the resource record, and it would be great for those to have a canonical spot to help with systems integrations. I would much rather see the addition of a BIBID to the resource record, which can then be displayed with the top container by the system if desired (although why?). There's already a field for the ILS holdings ID to go with the top container. Thanks all, Maureen -- Maureen Callahan Sophia Smith Collection Archivist Smith College Special Collections Northampton, Massachusetts 01063 413 585 2981 mcallahan at smith.edu Pronouns: she/her/hers Smith College Special Collections is now housed at Young Library. Learn more about renovations to Neilson Library here. On Mon, Dec 17, 2018 at 12:42 PM Rackley, Marilyn > wrote: Dear all, Please remember to review the Harvard Library proposal for container management enhancements and submit feedback by Wednesday, December 19, 2018. See the email below for more information. In case people are not able to access the attachment, the proposal can also be accessed through this link: https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-3Fid-3D14-2D6CFEAATfwYc1JZoAmCSD3CQVW7p3b3&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=bInpBUPKeV0QKr-JQH2j9yaDdfw8v580qBTSZmMBwx4&e=. We really appreciate all the comments provided so far. Best, Marilyn From: Rackley, Marilyn Sent: Monday, December 3, 2018 9:36 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace Community, The Harvard Library has been reviewing container and location management functionality in ArchivesSpace and we are proposing to make enhancements to this functionality that we would like to contribute to the core code. With these enhancements, we hope to make finding, viewing, and updating information related to containers and locations in the staff interface more efficient and effective. We have completed the draft proposal attached to this email and we are now asking for community review and feedback. The proposal includes the rationale for the changes, a list of database fields to be added, user stories describing the specific changes we are proposing, and mockups of the related updates to the staff interface. Please note that in the proposal, certain changes are designated as being a lower priority; it is possible that we may not be able to complete all the proposed changes at this time. If you have questions or feedback, please email me at marilyn_rackley at harvard.edu and/or Robin Wendler at robin_wendler at harvard.edu. We will be accepting comments through Wednesday, December 19, 2018. We look forward to receiving community input. Best, Marilyn Marilyn Rackley Aeon Project Manager and Digital Librarian Harvard Library | 617.496.4043 marilyn_rackley at harvard.edu _______________________________________________ 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=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=FB4KqB3TcRmkmN9zqyRn6s9tpjfpDzM3U9XYqkb3Ock&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=FB4KqB3TcRmkmN9zqyRn6s9tpjfpDzM3U9XYqkb3Ock&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From christine.dibella at lyrasis.org Wed Jun 5 08:21:45 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 5 Jun 2019 12:21:45 +0000 Subject: [Archivesspace_Users_Group] merge Top Container functionality In-Reply-To: References: Message-ID: For container management improvements, merging top containers has been the priority for awhile based on the Staff Interface Enhancement Working Group recommendations and what we've heard from the community -- that's definitely what we're aiming for first. But, as you note, there's a JIRA for merging container profiles as well. We'll need to revisit this when we get there, but I'd think that once we get top containers worked out, adding the ability to merge container profiles would be a comparatively short step from there. (Of course, if a community developer is able to tackle merging container profiles before we get there, we 'd love to hear from them. The program team or community members could likely create a more detailed specification for how it should look/behave based on what's in the JIRA.) Christine -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Kevin Clair Sent: Tuesday, June 4, 2019 7:48 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] merge Top Container functionality Thanks, Christine! Will there be similar functionality for Container Profiles? Someone at our shop asked me about that the other day and I saw there's a ticket for it at https://archivesspace.atlassian.net/browse/ANW-550, but it looks like it hasn't been updated since last summer. -k ?On 6/4/19, 2:50 PM, "archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Christine Di Bella" wrote: Hi Benn, Merging Top Containers has been on our development roadmap, and we know it is of great interest to a number of people in the community, but until recently we had not been able to identify a developer to take this on. We've now determined that we will be able to work on this after some of the large projects related to agents and infrastructure that are currently in progress have been completed. We're aiming for this functionality to be available in the application later this year. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Benn Joseph Sent: Tuesday, May 21, 2019 5:22 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] merge Top Container functionality Hi all, I'm curious whether there are any updates re: the ability to merge Top Containers. It looks like ANW-462 deals specifically with this but I can't tell if there has been much activity on it lately: https://archivesspace.atlassian.net/browse/ANW-462?atlOrigin=eyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9 Thanks! --Benn Benn Joseph Head of Archival Processing Northwestern University Libraries Northwestern University www.library.northwestern.edu benn.joseph at northwestern.edu 847.467.6581 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Tang, Lydia Sent: Wednesday, January 16, 2019 12:18 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I second the ability to merge containers! ? Lydia From: on behalf of Valerie Addonizio Reply-To: Archivesspace Users Group Date: Wednesday, January 16, 2019 at 1:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input I know that the comment period is closed, but this seemed like a logical place to ask whether the idea of container merging functionality was considered as part of this effort (I know it is not in the scope of work, but was it considered and not selected?) and whether other institutions are in need of such functionality? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Bowers, Kate A. Sent: Thursday, December 20, 2018 4:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace community: Apologies for the length of this. I?ll try to address a lot of comments, but not all! Please let me know if (as they may well do) my elaborations only elicit more questions! In general, most of these proposals are derived from facing problems of scale. Harvard has 30 repositories and over 200 users of ArchivesSpace. Others have to do with managing ?medium rare? materials? locations and containers in ArchivesSpace. (Medium-rare is a tongue-in-cheek term used to cover materials that might exist in multiple manifestations but that have archival or rare characteristics or treatment. Examples include entire libraries ingested into an archives, author?s own copies of their books, annotated books, or the record copy of serials or reports kept by institutional archives.) ? Multi-field top container indicators Some commenters wondered if the multiple fields were to accommodate child containers. To clarify, the suggestion was to facilitate parsing top container identifiers. As a few commenters have surmised, this is to cope with legacy numbers. These are especially common on medium-rare materials. One suggestion was to use a sort algorithm that would obviate the need for separated fields for data. However, because there would be is more than one algorithm necessary over the installation, such a solution would require an added field to identify the algorithm and probably a third field retain a value derived by the algorithm to be sorted alphanumerically. Thus, the direct 3-field solution seems simpler. (A 4-field suggestion was mooted in the committee as potentially more useful communally.) It does occur to me that there just might not be enough really old, really big repositories with lots of legacy identifiers in the ArchivesSpace community for the parsing of legacy numbers to be a common problem. I appreciate the recognition that a plug-in might be needed instead, but it would be worth hearing from any repositories with similar issues. ? Container and location profiles by repository We were envisioning a one-to-one profile-to-repository scenario. Due to the ArchivesSpace staff user interface requirement that one identify only a single repository at login, it is extremely easy for users to forget the impact they might have beyond their repository if they change or delete a shared record. We have already experienced mistaken mergers and deletions of agents due to the design of AS staff user interface that does not allow one to see where the record may be linked beyond their repository. For this reason, it is wise to be able to limit changes and deletions of location profiles and container profiles impact to the same chosen repository. ? Inactive As Maureen wisely intuited, inactive locations are necessary to recording a complete location history. However, there are additional use cases. When a repository is renovating, for example (as is happening now at the Schlesinger Library) the shelves in a location may be inactive for a time and become active again when the building re-opens. Other scenarios include water intrusion or other occasions when a smaller sub-set of shelves may have to become inactive until repairs are completed and tested before the shelving can again come into use. Because inactive locations are to be eliminated by default from search results, we can prevent them from overwhelming staff members? search results or sending staff to unusable locations. ? Notes in containers and locations Notes are for dedicated shelving or rehousing issues. Notes on containers may contain things like ?Label falling off? ?Acidic-needs replacing? ?Acid box replaced with acid-free box 2017-06-08? ?Not on shelf 2015-10-10?. Notes on locations may contain things like ?only use as last resort?overhead drip pan makes retrieval difficult? ?reserved for outgoing transfers until 2019-01-01?. In locations especially, we would expect the reason for a location becoming inactive might be noted. ?Made inactive because next to heating duct?do not reactivate?. ? Bibliographic record IDs in containers This data would allow for more sustainable interoperability between systems and more flexibility in workflows. Especially with medium-rare materials, the physical item?s location might need to be recorded before description is finalized, and if the description is to be created in foreign system and ingested to ArchivesSpace, hooking up the container and location will be problematic. In this scenario, a resource with initial description in a bibliographic system could be placed on an archives? shelf, and the description, once completed in the ILS, could be ingested via MARC XML ingest for example. After the resource is ingested, the ILS bibliographic record number could be searched in the containers to link the container to the resource. When an ILS system migrates, it is unlikely that the migration would maintain obsolte holding or item system numbers, but it is common to migrate with obsolete bibliographic system record numbers embedded into the new system. Should there be a need to re-migrate holdings or items from ArchivesSpace to a new ILS, bibliographic record numbers would ensure continuity. Thanks for reading! Kate From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Maureen Callahan Sent: Monday, December 17, 2018 2:09 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container Management Enhancements - Call for Community Input A million thanks to folks from Harvard for showing leadership and investing to improve the experience of the software for all of us. I was having pleasant flashbacks to my days at Yale working through the original specifications for the container management functionality -- what it all means, what it should do, how this will improve the experience for archivists and patrons, and how to abstract all of this work to more general archival and data management principles. It's such fun, hard work! Generally speaking, it would be really helpful if user stories gave a better sense of what you want to accomplish instead of what you want to see on the screen. For some of this, I had a hard time understanding where you were coming from and I think it's possible that there are different ways of accomplishing what you've laid out. "As an W, I want to have X feature, so that Y behavior happens in Z way and lets me do my work in ABC fashion." I think that many of the goals behind this proposal are sound, but that perhaps there's too narrow an approach to solutions to meet these goals. Developers might find better ways to address the problems you've identified. 1. Hell YES there need to be easier ways to browse/sort/find locations!!!! 2. I agree that it would be useful to have the option to filter locations/container profiles by the repository they tend to belong to and that this should also be extensible so that it's easy to change this information after a move or administrative change. I sort of remember that folks at NYU talked about this as a possible outcome in the beginning of their location profile work, so it may be worth talking with them about the best way to think about it and any reasons they might have opted to not associate a repository with a location profile. 3. Lora did some nice work with search to make it possible to see the entire breadcrumb trail of where a search result comes from (the hierarchies of AOs within a resource). I'm thinking that perhaps you just want the same thing to happen when you look at the associated archival objects / accessions in a top container, rather than adding another column (resource) to the search result. 4. As someone who has had to do a lot of systems migrations that involved moving heterogenous data into more structured places, I get really nervous about a notes field for either the location or the top container. If there are common types of information that end up in this field, it may be worth considering adding more structured fields to either the location or the location profile or container or container profile so that it can be better managed, queried, and kept tidy & up-to-date. What's the scenario by which someone would actually look at this notes field? What do you want to go in there? 5. Soooooo tell me more about this inactive location idea. AFAIR, ArchivesSpace doesn't keep an audit trail of previous locations. What's the value of knowing that inactive locations exist when there aren't containers living in those locations and there's no way to see that those locations perviously held containers? 6. This may be implicit in your proposal, but it sounds like you want "repository" to be a multi-valued field in your location profiles and your container profiles. Paige boxes, for instance, will probably end up being associated with every repository. 7. I was initially a bit perplexed by the request to add additional fields for container indicators, but reading between the lines, my guess is that you want to be able to sort them properly in various circumstances. If, for instance, you have boxes 2, 2a, and 3, you want to be able to make sure that when you sort by indicator, they appear in this order. That's a great goal! But I think that you might want to state this goal instead of stating one possible outcome. I definitely DO NOT want a three-part container indicator because who knows what kind of crap people will put in those fields and they could potentially be a nightmare to clean up. Plus, it would have to account for every possible heterodox way that people design their container indicators -- or just default to Harvard's scheme, which... I mean, this is software for the whole community. Instead, I would suggest making the requirement that you want for alphanumeric characters to sort properly and clever developers can come up with the best way to do this. That seems like a more elegant solution than changing the data model. 8. YES BIBIDs!!!! But my read is that a BIBID is a control number for intellectual description, not for holdings. I know that folks are currently putting BIBIDs in user-defined fields in the resource record, and it would be great for those to have a canonical spot to help with systems integrations. I would much rather see the addition of a BIBID to the resource record, which can then be displayed with the top container by the system if desired (although why?). There's already a field for the ILS holdings ID to go with the top container. Thanks all, Maureen -- Maureen Callahan Sophia Smith Collection Archivist Smith College Special Collections Northampton, Massachusetts 01063 413 585 2981 mcallahan at smith.edu Pronouns: she/her/hers Smith College Special Collections is now housed at Young Library. Learn more about renovations to Neilson Library here. On Mon, Dec 17, 2018 at 12:42 PM Rackley, Marilyn > wrote: Dear all, Please remember to review the Harvard Library proposal for container management enhancements and submit feedback by Wednesday, December 19, 2018. See the email below for more information. In case people are not able to access the attachment, the proposal can also be accessed through this link: https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-3Fid-3D14-2D6CFEAATfwYc1JZoAmCSD3CQVW7p3b3&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=bInpBUPKeV0QKr-JQH2j9yaDdfw8v580qBTSZmMBwx4&e=. We really appreciate all the comments provided so far. Best, Marilyn From: Rackley, Marilyn Sent: Monday, December 3, 2018 9:36 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Proposal for Container Management Enhancements - Call for Community Input Dear ArchivesSpace Community, The Harvard Library has been reviewing container and location management functionality in ArchivesSpace and we are proposing to make enhancements to this functionality that we would like to contribute to the core code. With these enhancements, we hope to make finding, viewing, and updating information related to containers and locations in the staff interface more efficient and effective. We have completed the draft proposal attached to this email and we are now asking for community review and feedback. The proposal includes the rationale for the changes, a list of database fields to be added, user stories describing the specific changes we are proposing, and mockups of the related updates to the staff interface. Please note that in the proposal, certain changes are designated as being a lower priority; it is possible that we may not be able to complete all the proposed changes at this time. If you have questions or feedback, please email me at marilyn_rackley at harvard.edu and/or Robin Wendler at robin_wendler at harvard.edu. We will be accepting comments through Wednesday, December 19, 2018. We look forward to receiving community input. Best, Marilyn Marilyn Rackley Aeon Project Manager and Digital Librarian Harvard Library | 617.496.4043 marilyn_rackley at harvard.edu _______________________________________________ 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=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=FB4KqB3TcRmkmN9zqyRn6s9tpjfpDzM3U9XYqkb3Ock&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=FB4KqB3TcRmkmN9zqyRn6s9tpjfpDzM3U9XYqkb3Ock&e= _______________________________________________ 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 From rachel.searcy at nyu.edu Wed Jun 5 09:22:25 2019 From: rachel.searcy at nyu.edu (Rachel Aileen Searcy) Date: Wed, 5 Jun 2019 09:22:25 -0400 Subject: [Archivesspace_Users_Group] merge Top Container functionality In-Reply-To: References: Message-ID: This is great news! - thank you for the update on this, Christine. We wanted to add our voices to the chorus that we too are looking forward to this functionality. We would also very much welcome the ability to merge container profiles, as Kevin just brought up. Thanks, Rachel On Wed, Jun 5, 2019 at 8:21 AM Christine Di Bella < christine.dibella at lyrasis.org> wrote: > For container management improvements, merging top containers has been the > priority for awhile based on the Staff Interface Enhancement Working Group > recommendations and what we've heard from the community -- that's > definitely what we're aiming for first. But, as you note, there's a JIRA > for merging container profiles as well. We'll need to revisit this when we > get there, but I'd think that once we get top containers worked out, adding > the ability to merge container profiles would be a comparatively short step > from there. > > (Of course, if a community developer is able to tackle merging container > profiles before we get there, we 'd love to hear from them. The program > team or community members could likely create a more detailed specification > for how it should look/behave based on what's in the JIRA.) > > Christine > > -----Original Message----- > From: archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of > Kevin Clair > Sent: Tuesday, June 4, 2019 7:48 PM > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: Re: [Archivesspace_Users_Group] merge Top Container functionality > > Thanks, Christine! Will there be similar functionality for Container > Profiles? Someone at our shop asked me about that the other day and I saw > there's a ticket for it at > https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D550&d=DwIGaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=WzsSfhV5voLsah7Ip9vFy81tN7BDqOAUmc829ruDPKo&s=0e1WDtwfatT5pXluM5NJQ8U6w6Aq7hlx6hjwS_PwgFI&e= > , but it looks like it hasn't been updated since last summer. -k > > ?On 6/4/19, 2:50 PM, " > archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of > Christine Di Bella" < > archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of > christine.dibella at lyrasis.org> wrote: > > Hi Benn, > > Merging Top Containers has been on our development roadmap, and we > know it is of great interest to a number of people in the community, but > until recently we had not been able to identify a developer to take this > on. We've now determined that we will be able to work on this after some of > the large projects related to agents and infrastructure that are currently > in progress have been completed. We're aiming for this functionality to be > available in the application later this year. > > Christine > > Christine Di Bella > ArchivesSpace Program Manager > christine.dibella at lyrasis.org > 800.999.8558 x2905 > 678-235-2905 > cdibella13 (Skype) > > > > -----Original Message----- > From: archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of > Benn Joseph > Sent: Tuesday, May 21, 2019 5:22 PM > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] merge Top Container functionality > > Hi all, > I'm curious whether there are any updates re: the ability to merge Top > Containers. It looks like ANW-462 deals specifically with this but I can't > tell if there has been much activity on it lately: > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D462-3FatlOrigin-3DeyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9&d=DwIGaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=WzsSfhV5voLsah7Ip9vFy81tN7BDqOAUmc829ruDPKo&s=B-W8Y4bxQ_l6xQ-rv-XOPKDsOq4yF4EJxCKeQnJnKIw&e= > > Thanks! > --Benn > > Benn Joseph > Head of Archival Processing > Northwestern University Libraries > Northwestern University > > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.library.northwestern.edu&d=DwIGaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=WzsSfhV5voLsah7Ip9vFy81tN7BDqOAUmc829ruDPKo&s=6YgNz1fy5Ld4xc-vCQ2ZXPR7HADFt1gIsPzEPtV_dKQ&e= > benn.joseph at northwestern.edu > 847.467.6581 > > > > -----Original Message----- > From: archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of > Tang, Lydia > Sent: Wednesday, January 16, 2019 12:18 PM > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for > Container Management Enhancements - Call for Community Input > > I second the ability to merge containers! ? > Lydia > > From: on > behalf of Valerie Addonizio > Reply-To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Date: Wednesday, January 16, 2019 at 1:17 PM > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for > Container Management Enhancements - Call for Community Input > > I know that the comment period is closed, but this seemed like a > logical place to ask whether the idea of container merging functionality > was considered as part of this effort (I know it is not in the scope of > work, but was it considered and not selected?) and whether other > institutions are in need of such functionality? > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of > Bowers, Kate A. > Sent: Thursday, December 20, 2018 4:16 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for > Container Management Enhancements - Call for Community Input > > Dear ArchivesSpace community: > > Apologies for the length of this. I?ll try to address a lot of > comments, but not all! Please let me know if (as they may well do) my > elaborations only elicit more questions! > > In general, most of these proposals are derived from facing problems > of scale. Harvard has 30 repositories and over 200 users of ArchivesSpace. > Others have to do with managing ?medium rare? materials? locations and > containers in ArchivesSpace. (Medium-rare is a tongue-in-cheek term used > to cover materials that might exist in multiple manifestations but that > have archival or rare characteristics or treatment. Examples include entire > libraries ingested into an archives, author?s own copies of their books, > annotated books, or the record copy of serials or reports kept by > institutional archives.) > > ? Multi-field top container indicators > Some commenters wondered if the multiple fields were to > accommodate child containers. To clarify, the suggestion was to facilitate > parsing top container identifiers. As a few commenters have surmised, this > is to cope with legacy numbers. These are especially common on medium-rare > materials. > One suggestion was to use a sort algorithm that would obviate the > need for separated fields for data. However, because there would be is more > than one algorithm necessary over the installation, such a solution would > require an added field to identify the algorithm and probably a third field > retain a value derived by the algorithm to be sorted alphanumerically. > Thus, the direct 3-field solution seems simpler. (A 4-field suggestion was > mooted in the committee as potentially more useful communally.) It does > occur to me that there just might not be enough really old, really big > repositories with lots of legacy identifiers in the ArchivesSpace community > for the parsing of legacy numbers to be a common problem. I appreciate the > recognition that a plug-in might be needed instead, but it would be worth > hearing from any repositories with similar issues. > > ? Container and location profiles by repository > We were envisioning a one-to-one profile-to-repository > scenario. Due to the ArchivesSpace staff user interface requirement that > one identify only a single repository at login, it is extremely easy for > users to forget the impact they might have beyond their repository if they > change or delete a shared record. We have already experienced mistaken > mergers and deletions of agents due to the design of AS staff user > interface that does not allow one to see where the record may be linked > beyond their repository. For this reason, it is wise to be able to limit > changes and deletions of location profiles and container profiles impact to > the same chosen repository. > > ? Inactive > As Maureen wisely intuited, inactive locations are necessary to > recording a complete location history. However, there are additional use > cases. When a repository is renovating, for example (as is happening now at > the Schlesinger Library) the shelves in a location may be inactive for a > time and become active again when the building re-opens. Other scenarios > include water intrusion or other occasions when a smaller sub-set of > shelves may have to become inactive until repairs are completed and tested > before the shelving can again come into use. Because inactive locations are > to be eliminated by default from search results, we can prevent them from > overwhelming staff members? search results or sending staff to unusable > locations. > > ? Notes in containers and locations > Notes are for dedicated shelving or rehousing issues. Notes on > containers may contain things like ?Label falling off? ?Acidic-needs > replacing? ?Acid box replaced with acid-free box 2017-06-08? ?Not on shelf > 2015-10-10?. Notes on locations may contain things like ?only use as last > resort?overhead drip pan makes retrieval difficult? ?reserved for outgoing > transfers until 2019-01-01?. In locations especially, we would expect the > reason for a location becoming inactive might be noted. ?Made inactive > because next to heating duct?do not reactivate?. > > ? Bibliographic record IDs in containers > This data would allow for more sustainable interoperability > between systems and more flexibility in workflows. > Especially with medium-rare materials, the physical item?s > location might need to be recorded before description is finalized, and if > the description is to be created in foreign system and ingested to > ArchivesSpace, hooking up the container and location will be problematic. > In this scenario, a resource with initial description in a bibliographic > system could be placed on an archives? shelf, and the description, once > completed in the ILS, could be ingested via MARC XML ingest for example. > After the resource is ingested, the ILS bibliographic record number could > be searched in the containers to link the container to the resource. > When an ILS system migrates, it is unlikely that the migration > would maintain obsolte holding or item system numbers, but it is common to > migrate with obsolete bibliographic system record numbers embedded into the > new system. Should there be a need to re-migrate holdings or items from > ArchivesSpace to a new ILS, bibliographic record numbers would ensure > continuity. > > Thanks for reading! > > Kate > > > > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of > Maureen Callahan > Sent: Monday, December 17, 2018 2:09 PM > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for > Container Management Enhancements - Call for Community Input > > A million thanks to folks from Harvard for showing leadership and > investing to improve the experience of the software for all of us. > > I was having pleasant flashbacks to my days at Yale working through > the original specifications for the container management functionality -- > what it all means, what it should do, how this will improve the experience > for archivists and patrons, and how to abstract all of this work to more > general archival and data management principles. It's such fun, hard work! > > Generally speaking, it would be really helpful if user stories gave a > better sense of what you want to accomplish instead of what you want to see > on the screen. For some of this, I had a hard time understanding where you > were coming from and I think it's possible that there are different ways of > accomplishing what you've laid out. "As an W, I want to have X feature, so > that Y behavior happens in Z way and lets me do my work in ABC fashion." I > think that many of the goals behind this proposal are sound, but that > perhaps there's too narrow an approach to solutions to meet these goals. > Developers might find better ways to address the problems you've identified. > > 1. Hell YES there need to be easier ways to browse/sort/find > locations!!!! > > 2. I agree that it would be useful to have the option to filter > locations/container profiles by the repository they tend to belong to and > that this should also be extensible so that it's easy to change this > information after a move or administrative change. I sort of remember that > folks at NYU talked about this as a possible outcome in the beginning of > their location profile work, so it may be worth talking with them about the > best way to think about it and any reasons they might have opted to not > associate a repository with a location profile. > > 3. Lora did some nice work with search to make it possible to see the > entire breadcrumb trail of where a search result comes from (the > hierarchies of AOs within a resource). I'm thinking that perhaps you just > want the same thing to happen when you look at the associated archival > objects / accessions in a top container, rather than adding another column > (resource) to the search result. > > 4. As someone who has had to do a lot of systems migrations that > involved moving heterogenous data into more structured places, I get really > nervous about a notes field for either the location or the top container. > If there are common types of information that end up in this field, it may > be worth considering adding more structured fields to either the location > or the location profile or container or container profile so that it can be > better managed, queried, and kept tidy & up-to-date. What's the scenario by > which someone would actually look at this notes field? What do you want to > go in there? > > 5. Soooooo tell me more about this inactive location idea. AFAIR, > ArchivesSpace doesn't keep an audit trail of previous locations. What's the > value of knowing that inactive locations exist when there aren't containers > living in those locations and there's no way to see that those locations > perviously held containers? > > 6. This may be implicit in your proposal, but it sounds like you want > "repository" to be a multi-valued field in your location profiles and your > container profiles. Paige boxes, for instance, will probably end up being > associated with every repository. > > 7. I was initially a bit perplexed by the request to add additional > fields for container indicators, but reading between the lines, my guess is > that you want to be able to sort them properly in various circumstances. > > If, for instance, you have boxes 2, 2a, and 3, you want to be able to > make sure that when you sort by indicator, they appear in this order. > That's a great goal! But I think that you might want to state this goal > instead of stating one possible outcome. > > I definitely DO NOT want a three-part container indicator because who > knows what kind of crap people will put in those fields and they could > potentially be a nightmare to clean up. Plus, it would have to account for > every possible heterodox way that people design their container indicators > -- or just default to Harvard's scheme, which... I mean, this is software > for the whole community. > > Instead, I would suggest making the requirement that you want for > alphanumeric characters to sort properly and clever developers can come up > with the best way to do this. That seems like a more elegant solution than > changing the data model. > > 8. YES BIBIDs!!!! But my read is that a BIBID is a control number for > intellectual description, not for holdings. I know that folks are currently > putting BIBIDs in user-defined fields in the resource record, and it would > be great for those to have a canonical spot to help with systems > integrations. I would much rather see the addition of a BIBID to the > resource record, which can then be displayed with the top container by the > system if desired (although why?). There's already a field for the ILS > holdings ID to go with the top container. > > Thanks all, > Maureen > > > -- > Maureen Callahan > Sophia Smith Collection Archivist > Smith College Special Collections > Northampton, Massachusetts 01063 > 413 585 2981 > mcallahan at smith.edu > > Pronouns: she/her/hers > > Smith College Special Collections is now housed at Young Library< > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.smith.edu_libraries_about_new-2Dneilson_wheres-2Dmy-2Dlibrary&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=bbRMI526TLbYRRGdpIJjhaQSNXcp3-xidB745mYa688&s=6_5o894RumU3UiMWDspYsi9hvlxzwybbDZhwqxoqzUk&e=>. > Learn more about renovations to Neilson Library here< > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.smith.edu_libraries_about_new-2Dneilson&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=bbRMI526TLbYRRGdpIJjhaQSNXcp3-xidB745mYa688&s=D7vktPydut0KZQpgPuTDeMfGLme5d9GNsfXHoWV7CRk&e= > >. > > On Mon, Dec 17, 2018 at 12:42 PM Rackley, Marilyn < > marilyn_rackley at harvard.edu> wrote: > Dear all, > > Please remember to review the Harvard Library proposal for container > management enhancements and submit feedback by Wednesday, December 19, > 2018. See the email below for more information. > > In case people are not able to access the attachment, the proposal can > also be accessed through this link: > https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-3Fid-3D14-2D6CFEAATfwYc1JZoAmCSD3CQVW7p3b3&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=bInpBUPKeV0QKr-JQH2j9yaDdfw8v580qBTSZmMBwx4&e= > < > https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com_open-3Fid-3D14-2D6CFEAATfwYc1JZoAmCSD3CQVW7p3b3&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=bbRMI526TLbYRRGdpIJjhaQSNXcp3-xidB745mYa688&s=1GjU8ktQ9bncQdhvdE2zi0a2fHSWL8NDj17jV9byJn8&e= > >. > > We really appreciate all the comments provided so far. > > Best, > Marilyn > > From: Rackley, Marilyn > Sent: Monday, December 3, 2018 9:36 AM > To: archivesspace_users_group at lyralists.lyrasis.org archivesspace_users_group at lyralists.lyrasis.org> > Subject: Proposal for Container Management Enhancements - Call for > Community Input > > Dear ArchivesSpace Community, > > The Harvard Library has been reviewing container and location > management functionality in ArchivesSpace and we are proposing to make > enhancements to this functionality that we would like to contribute to the > core code. > > With these enhancements, we hope to make finding, viewing, and > updating information related to containers and locations in the staff > interface more efficient and effective. > > We have completed the draft proposal attached to this email and we are > now asking for community review and feedback. The proposal includes the > rationale for the changes, a list of database fields to be added, user > stories describing the specific changes we are proposing, and mockups of > the related updates to the staff interface. Please note that in the > proposal, certain changes are designated as being a lower priority; it is > possible that we may not be able to complete all the proposed changes at > this time. > > If you have questions or feedback, please email me at > marilyn_rackley at harvard.edu and/or > Robin Wendler at robin_wendler at harvard.edu robin_wendler at harvard.edu>. We will be accepting comments through > Wednesday, December 19, 2018. > > We look forward to receiving community input. > > Best, > Marilyn > > Marilyn Rackley > Aeon Project Manager and Digital Librarian Harvard Library | > 617.496.4043 marilyn_rackley at harvard.edu marilyn_rackley at harvard.edu> > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org 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=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=FB4KqB3TcRmkmN9zqyRn6s9tpjfpDzM3U9XYqkb3Ock&e= > < > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=bbRMI526TLbYRRGdpIJjhaQSNXcp3-xidB745mYa688&s=Ia_oQ7YT5R2fLTqMbss7oSChwO-HRtiNxwPbTe1RCRM&e= > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=yHlS04HhBraes5BQ9ueu5zKhE7rtNXt_d012z2PA6ws&r=fciHLC2ou0tXKp-JlPlsrEmslFw9tnR331DgXAhVLvo&m=K5QjuKlUxPPrg2p5830gF8oT3Voegkm_3vzVJ05lgm4&s=FB4KqB3TcRmkmN9zqyRn6s9tpjfpDzM3U9XYqkb3Ock&e= > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=WzsSfhV5voLsah7Ip9vFy81tN7BDqOAUmc829ruDPKo&s=BRsURHLQOmtDZAN8BQtkBD2HXVpghzeetqPkOR8viw4&e= > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=WzsSfhV5voLsah7Ip9vFy81tN7BDqOAUmc829ruDPKo&s=BRsURHLQOmtDZAN8BQtkBD2HXVpghzeetqPkOR8viw4&e= > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=WzsSfhV5voLsah7Ip9vFy81tN7BDqOAUmc829ruDPKo&s=BRsURHLQOmtDZAN8BQtkBD2HXVpghzeetqPkOR8viw4&e= > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=WzsSfhV5voLsah7Ip9vFy81tN7BDqOAUmc829ruDPKo&s=BRsURHLQOmtDZAN8BQtkBD2HXVpghzeetqPkOR8viw4&e= > -- Rachel Searcy Accessioning Archivist, Archival Collections Management New York University Libraries 212.998.2539 | rachel.searcy at nyu.edu My pronouns are she/her -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmichelson at smith.edu Fri Jun 7 10:14:20 2019 From: dmichelson at smith.edu (Daniel Michelson) Date: Fri, 7 Jun 2019 10:14:20 -0400 Subject: [Archivesspace_Users_Group] PUI Citation Customization Message-ID: Hi All, As we look to implement the PUI, we're wondering how other repositories are handling the PUI's citation function. Based on the wiki text , it seems that the URI and date of access is always appended to the citation. I find this puzzling, as the purpose of the preferred citation note is to provide researchers a way to easily cite the material being described, not so they can cite the finding aid itself (see DACS 7.1.5 ). Has anyone customized their citation function to remove the URI and access date? Thanks, Dan -- Dan Michelson Project Manager Archivist Smith College Special Collections -------------- next part -------------- An HTML attachment was scrubbed... URL: From mpaquette at smith.edu Mon Jun 10 10:12:17 2019 From: mpaquette at smith.edu (Michelle Paquette) Date: Mon, 10 Jun 2019 10:12:17 -0400 Subject: [Archivesspace_Users_Group] OAI returns unpublished agent Message-ID: Hi all, Has anyone else run into this issue with unpublished agents being returned by the OAI service? https://archivesspace.atlassian.net/browse/ANW-906 Due to privacy concerns we cannot enable OAI-PMH harvesting if unpublished agents are included in the returned data. We're using version 2.5.2. If this in an important issue for you or is preventing your institution from enabling OAI, please let me know, Michelle -- Michelle Paquette Metadata & Technical Services Archivist Special Collections Smith College 413-585-7029 mpaquette at smith.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Mon Jun 10 11:02:49 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Mon, 10 Jun 2019 15:02:49 +0000 Subject: [Archivesspace_Users_Group] OAI returns unpublished agent In-Reply-To: References: Message-ID: Is this an issue with all OAI metadata payloads: DC,MARC, EAD ? Or with only one ? And does it produce something different in the OAI payload compared to exporting from the staff interface ? For example, oai_ead metadata payload vs EAD export with include unpublished FALSE. ? Steve M. > On Jun 10, 2019, at 10:12 AM, Michelle Paquette wrote: > > Hi all, > > Has anyone else run into this issue with unpublished agents being returned by the OAI service? https://archivesspace.atlassian.net/browse/ANW-906 Due to privacy concerns we cannot enable OAI-PMH harvesting if unpublished agents are included in the returned data. We're using version 2.5.2. If this in an important issue for you or is preventing your institution from enabling OAI, please let me know, > > Michelle > > -- > Michelle Paquette > Metadata & Technical Services Archivist > Special Collections > Smith College > 413-585-7029 > mpaquette at smith.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: 3598 bytes Desc: not available URL: From rex.hughes at ndsu.edu Mon Jun 10 14:36:06 2019 From: rex.hughes at ndsu.edu (Hughes ll, Rex) Date: Mon, 10 Jun 2019 18:36:06 +0000 Subject: [Archivesspace_Users_Group] Setting Imported Agents to Publish Message-ID: Hello, We recently imported our legacy records into ArchivesSpace, and while I was able to import all existing Subject Headings and Agents (Authorities), I noticed that the Subjects imported as "Publish True" and the Agents imported as "Publish False." Is there a way to set multiple Agent entries as "Publish True" through a batch or system job in ArchivesSpace? I would rather not edit every single Agent entry to simply check the box for "Publish" if this tedious work could be avoided. Thank you! Sincerely, Rex Hughes, II, M.L.I.S. Metadata and Cataloging Librarian Resource Acquisition, Management, and Discovery NDSU Libraries Dept. 2080, PO Box 6050 Fargo ND 58108-6050 Phone:701.231.9677 -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Mon Jun 10 15:24:24 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Mon, 10 Jun 2019 19:24:24 +0000 Subject: [Archivesspace_Users_Group] Setting Imported Agents to Publish In-Reply-To: References: Message-ID: That can be done in the database, shoot me a support email and we can figure that out. And for the record here on the list, it's something like: UPDATE subject SET publish = 1, system_mtime = NOW(); That will set ALL subjects to publish and tell ArchivesSpace to reindex them all. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Hughes ll, Rex Sent: Monday, June 10, 2019 2:36 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Setting Imported Agents to Publish Hello, We recently imported our legacy records into ArchivesSpace, and while I was able to import all existing Subject Headings and Agents (Authorities), I noticed that the Subjects imported as ?Publish True? and the Agents imported as ?Publish False.? Is there a way to set multiple Agent entries as ?Publish True? through a batch or system job in ArchivesSpace? I would rather not edit every single Agent entry to simply check the box for ?Publish? if this tedious work could be avoided. Thank you! Sincerely, Rex Hughes, II, M.L.I.S. Metadata and Cataloging Librarian Resource Acquisition, Management, and Discovery NDSU Libraries Dept. 2080, PO Box 6050 Fargo ND 58108-6050 Phone:701.231.9677 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gordon_daines at byu.edu Mon Jun 10 17:11:41 2019 From: gordon_daines at byu.edu (Gordon Daines) Date: Mon, 10 Jun 2019 21:11:41 +0000 Subject: [Archivesspace_Users_Group] New members of the Technical Advisory Council and the User Advisory Council Message-ID: I am pleased to announce that the Governance Board has approved the appointment of new members of the User Advisory Council and the Technical Advisory Council. The following individuals have been appointed with terms running from July 1st, 2019 to June 30th, 2021: Technical Advisory Council Sarit Hand-AP Corporate Archives-Small Randy Kuehn-University of Louisville-Large James Griffin III-Princeton-Very Large Kevin Schlottmann-Columbia University-Very Large User Advisory Council Dan Michelson-Smith College-Small Althea Topek-Tulane University-Medium Lori Dedeyan-UCLA-Very Large Please join me in welcoming these new members to the Councils. Gordon Daines Chair, Nominating Committee _________________________ J. Gordon Daines III Supervisor of Reference Services Department Chair L. Tom Perry Special Collections Brigham Young University Provo, UT 84602 801-422-5821 gordon_daines at byu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From rodmang at ripon.edu Tue Jun 11 15:25:47 2019 From: rodmang at ripon.edu (Rodman, Gary) Date: Tue, 11 Jun 2019 14:25:47 -0500 Subject: [Archivesspace_Users_Group] Troubleshooting archivesspace 2.6 on Windows Server 2012R2 Message-ID: Hello, I've installed archivesspace 2.6 on a windows 2012 server. I believe I have installed all necessary prerequisites including: MySQL community server, MySQL Connector J platform independent, commons-daemon (prunmgr.exe and prunsrv.exe), edited config.rb to point to the archivesspace database within MySQL, created the JAVA_HOME environment variable, added the Java executable to the path statement. However, I cannot get the archivesspace service to launch (neither the windows event viewer error nor the archivesspace.out error logs are helpful) When I execute archivesspace.bat from an elevated command prompt, that seems to run, but browsing to http://localhost:8089/ gives an internal server error Internal Server Error (500) Request Method: GET Request URL: http://localhost:8089/ Database connection failed from D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in `block in ArchivesSpaceService' from D:/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure' from D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in `' from D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in `
' from org/jruby/RubyKernel.java:956:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `block in require' from org/jruby/RubyBasicObject.java:1691:in `instance_eval' from D:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4:in `(root)' from uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:157:in `main' from launcher/launcher.rb:261:in `
' You're seeing this error because you use JRuby::Rack::ErrorApp::ShowStatus. The other URLs (:8080, :8081, :8082 give connection refused errors. Looking for any advice on troubleshooting. Thank you. *Gary Rodman* Director of Enterprise Applications Ripon College 300 W. Seward St. Ripon, WI 54971 (direct) 920-748-83 <920-748-8365>43 RodmanG at ripon.edu [image: image.png] Visit us at *ripon.edu * -- _This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information.? Any review, dissemination, copying, printing, or other use of this email by persons or entities other than the addressee is prohibited. If you have received this email in error, please contact the sender immediately and delete the material from your computer._ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 17747 bytes Desc: not available URL: From blake.carver at lyrasis.org Tue Jun 11 15:32:47 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Tue, 11 Jun 2019 19:32:47 +0000 Subject: [Archivesspace_Users_Group] Troubleshooting archivesspace 2.6 on Windows Server 2012R2 In-Reply-To: References: Message-ID: "Database connection failed..." For some reason ArchivesSpace can't talk to your DB. The answer is probably in your archivesspace.out file, though it can be hard to spot sometimes. Could be a user/password issue, or a port or URL issue, or a migration issue. Take another look at that log file, and within the first 50 or so lines, there's probably something that screams "ERROR" with an explanation of some kind. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Rodman, Gary Sent: Tuesday, June 11, 2019 3:25 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Troubleshooting archivesspace 2.6 on Windows Server 2012R2 Hello, I've installed archivesspace 2.6 on a windows 2012 server. I believe I have installed all necessary prerequisites including: MySQL community server, MySQL Connector J platform independent, commons-daemon (prunmgr.exe and prunsrv.exe), edited config.rb to point to the archivesspace database within MySQL, created the JAVA_HOME environment variable, added the Java executable to the path statement. However, I cannot get the archivesspace service to launch (neither the windows event viewer error nor the archivesspace.out error logs are helpful) When I execute archivesspace.bat from an elevated command prompt, that seems to run, but browsing to http://localhost:8089/ gives an internal server error Internal Server Error (500) Request Method: GET Request URL: http://localhost:8089/ Database connection failed from D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:101:in `block in ArchivesSpaceService' from D:/archivesspace/gems/gems/sinatra-1.4.7/lib/sinatra/base.rb:1411:in `configure' from D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:78:in `' from D:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:38:in `
' from org/jruby/RubyKernel.java:956:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `block in require' from org/jruby/RubyBasicObject.java:1691:in `instance_eval' from D:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4:in `(root)' from uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:157:in `main' from launcher/launcher.rb:261:in `
' You're seeing this error because you use JRuby::Rack::ErrorApp::ShowStatus. The other URLs (:8080, :8081, :8082 give connection refused errors. Looking for any advice on troubleshooting. Thank you. Gary Rodman Director of Enterprise Applications Ripon College 300 W. Seward St. Ripon, WI 54971 (direct) 920-748-8343 RodmanG at ripon.edu [image.png] Visit us at ripon.edu This e?mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing, or other use of this email by persons or entities other than the addressee is prohibited. If you have received this email in error, please contact the sender immediately and delete the material from your computer. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 17747 bytes Desc: image.png URL: From Jessica.Crouch at lyrasis.org Wed Jun 12 10:06:36 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Wed, 12 Jun 2019 14:06:36 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Member Forum - Deadline to submit presentations is June 14 Message-ID: <3756C4B7-4080-4A77-AEB9-5EFB4547A574@lyrasis.org> ArchivesSpace will be holding its fifth Annual Member Forum on August 2, 2019 in Austin, Texas at our member institution, University of Texas-Austin. Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. More information on the developing program is on the ArchivesSpace wiki at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/863436816/ArchivesSpace+Member+Forum+2019. The planning group is looking for presenters and topic suggestions for the forum. Anything related to ArchivesSpace is fair game. We are specifically interested in presentations or topics suitable for lightning round sessions or panels that highlight the work individual member intuitions are accomplishing in ArchivesSpace. There is particular interest in presentations related to the development of workflows within institutions that have integrated ArchivesSpace into their daily practice. There is a short Google submission form available at https://forms.gle/1xMLNbY81y1hnkL78; you can submit ideas or volunteer yourself to speak either via the form or by emailing Jessica Crouch directly. Proposals, ideas, and suggestions received by June 14 will receive priority consideration so that we can get the program squared away as soon as possible. You will receive a response by July 1. If you have any questions or other suggestions at this point, please feel free to email Jessica at jessica.crouch at lyrasis.org. Registration for the Member Forum will open soon. We look forward to seeing you in Austin! Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 29058 bytes Desc: image001.jpg URL: From CHRISTOPHER_LOVELL at pba.edu Wed Jun 12 10:35:12 2019 From: CHRISTOPHER_LOVELL at pba.edu (CHRISTOPHER LOVELL) Date: Wed, 12 Jun 2019 14:35:12 +0000 Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Message-ID: Hello all, I just performed a fresh install of the latest release of ArchivesSpace on a Windows 2008 R2 server with Java 1.7.0_55 and am seeing the error "Could not find childprocess-1.0.1 in any of the sources" in the log. I am unable to determine the cause. Can anyone offer suggestions? Here's a snip from the beginning of the log file. Thanks in advance for any assistance you can provide. [snip] Loading ArchivesSpace configuration file from path: C:\archivesspace\config/config.rb Jun 12, 2019 10:12:31 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup Could not find childprocess-1.0.1 in any of the sources --- System jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 Java HotSpot(TM) 64-Bit Server VM 24.55-b03 on 1.7.0_55-b13 +jit [mswin32-x86_64] Time: 2019-06-12 10:12:31 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.compat.version = 1.9 jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Bundler::GemNotFound: Could not find childprocess-1.0.1 in any of the sources block in materialize at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88 map! at org/jruby/RubyArray.java:2519 materialize at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82 specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170 specs_for at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237 requested_specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226 block in requested_specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108 setup at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20 setup at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107
at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20 require at org/jruby/RubyKernel.java:956 (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133 require at org/jruby/RubyKernel.java:956 (root) at C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1 block in (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1 instance_eval at org/jruby/RubyBasicObject.java:1691 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
at C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:157
at launcher/launcher.rb:261 --- RubyGems Gem.dir: C:/archivesspace/gems Gem.path: C:/Users/lovellc/.gem/jruby/2.3.0 uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared C:/archivesspace/gems Activated gems: did_you_mean-1.0.1 bundler-1.16.1 --- Bundler Bundler.bundle_path: C:/archivesspace/gems Bundler.root: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF Gemfile: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile Settings: without = [:test, :development, :doc] --- JRuby-Rack Config compat_version = RUBY1_9 default_logger = org.jruby.rack.logging.StandardOutLogger at 30f74da2 equals = err = java.io.PrintStream at d97643c filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 242ca061 logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 46417f28 rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},C:\archivesspace\wars/backend.war throw_init_exception = false Jun 12, 2019 10:12:31 AM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: Could not find childprocess-1.0.1 in any of the sources from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88:in `block in materialize' from org/jruby/RubyArray.java:2519:in `map!' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82:in `materialize' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170:in `specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237:in `specs_for' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226:in `requested_specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108:in `block in requested_specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20:in `setup' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107:in `setup' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20:in `
' from org/jruby/RubyKernel.java:956:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133:in `
' from org/jruby/RubyKernel.java:956:in `require' from C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `block in (root)' from org/jruby/RubyBasicObject.java:1691:in `instance_eval' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:157:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther155:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:178) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:338) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:183) at launcher.launcher.invokeOther290:start_server(launcher/launcher.rb:157) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:157) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther503:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.jruby.ir.Compiler$1.load(Compiler.java:94) at org.jruby.Ruby.runScript(Ruby.java:830) at org.jruby.Ruby.runNormally(Ruby.java:749) at org.jruby.Ruby.runNormally(Ruby.java:767) at org.jruby.Ruby.runFromMain(Ruby.java:580) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (GemNotFound) Could not find childprocess-1.0.1 in any of the sources at RUBY.block in materialize(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88) at org.jruby.RubyArray.map!(org/jruby/RubyArray.java:2519) at RUBY.materialize(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82) at RUBY.specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170) at RUBY.specs_for(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237) at RUBY.requested_specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226) at RUBY.block in requested_specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108) at RUBY.setup(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20) at RUBY.setup(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107) at RUBY.
(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1) at RUBY.block in (root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1691) at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.
(C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:157) at launcher.launcher.
(launcher/launcher.rb:261) Best regards, Christopher Lovell Campus Information Services/Warren Library Palm Beach Atlantic University (561) 803-2221 Soli Deo Gloria! -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Jun 12 10:41:27 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 12 Jun 2019 14:41:27 +0000 Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 In-Reply-To: References: Message-ID: Dear Christopher, We're still researching this, but some other users with Java 1.7 have reported this problem when trying to run 2.6.0. There was a Rails and other infrastructure updates in 2.6.0 and retaining support for this significantly older version of Java may not be possible with these necessary updates. Are you able to update to Java 1.8? That seems to have resolved the issue for others. 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 CHRISTOPHER LOVELL Sent: Wednesday, June 12, 2019 10:35 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Hello all, I just performed a fresh install of the latest release of ArchivesSpace on a Windows 2008 R2 server with Java 1.7.0_55 and am seeing the error "Could not find childprocess-1.0.1 in any of the sources" in the log. I am unable to determine the cause. Can anyone offer suggestions? Here's a snip from the beginning of the log file. Thanks in advance for any assistance you can provide. [snip] Loading ArchivesSpace configuration file from path: C:\archivesspace\config/config.rb Jun 12, 2019 10:12:31 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup Could not find childprocess-1.0.1 in any of the sources --- System jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 Java HotSpot(TM) 64-Bit Server VM 24.55-b03 on 1.7.0_55-b13 +jit [mswin32-x86_64] Time: 2019-06-12 10:12:31 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.compat.version = 1.9 jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Bundler::GemNotFound: Could not find childprocess-1.0.1 in any of the sources block in materialize at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88 map! at org/jruby/RubyArray.java:2519 materialize at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82 specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170 specs_for at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237 requested_specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226 block in requested_specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108 setup at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20 setup at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107
at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20 require at org/jruby/RubyKernel.java:956 (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133 require at org/jruby/RubyKernel.java:956 (root) at C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1 block in (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1 instance_eval at org/jruby/RubyBasicObject.java:1691 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
at C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:157
at launcher/launcher.rb:261 --- RubyGems Gem.dir: C:/archivesspace/gems Gem.path: C:/Users/lovellc/.gem/jruby/2.3.0 uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared C:/archivesspace/gems Activated gems: did_you_mean-1.0.1 bundler-1.16.1 --- Bundler Bundler.bundle_path: C:/archivesspace/gems Bundler.root: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF Gemfile: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile Settings: without = [:test, :development, :doc] --- JRuby-Rack Config compat_version = RUBY1_9 default_logger = org.jruby.rack.logging.StandardOutLogger at 30f74da2 equals = err = java.io.PrintStream at d97643c filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 242ca061 logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 46417f28 rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},C:\archivesspace\wars/backend.war throw_init_exception = false Jun 12, 2019 10:12:31 AM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: Could not find childprocess-1.0.1 in any of the sources from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88:in `block in materialize' from org/jruby/RubyArray.java:2519:in `map!' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82:in `materialize' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170:in `specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237:in `specs_for' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226:in `requested_specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108:in `block in requested_specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20:in `setup' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107:in `setup' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20:in `
' from org/jruby/RubyKernel.java:956:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133:in `
' from org/jruby/RubyKernel.java:956:in `require' from C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `block in (root)' from org/jruby/RubyBasicObject.java:1691:in `instance_eval' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:157:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther155:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:178) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:338) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:183) at launcher.launcher.invokeOther290:start_server(launcher/launcher.rb:157) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:157) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther503:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.jruby.ir.Compiler$1.load(Compiler.java:94) at org.jruby.Ruby.runScript(Ruby.java:830) at org.jruby.Ruby.runNormally(Ruby.java:749) at org.jruby.Ruby.runNormally(Ruby.java:767) at org.jruby.Ruby.runFromMain(Ruby.java:580) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (GemNotFound) Could not find childprocess-1.0.1 in any of the sources at RUBY.block in materialize(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88) at org.jruby.RubyArray.map!(org/jruby/RubyArray.java:2519) at RUBY.materialize(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82) at RUBY.specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170) at RUBY.specs_for(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237) at RUBY.requested_specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226) at RUBY.block in requested_specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108) at RUBY.setup(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20) at RUBY.setup(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107) at RUBY.
(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1) at RUBY.block in (root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1691) at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.
(C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:157) at launcher.launcher.
(launcher/launcher.rb:261) Best regards, Christopher Lovell Campus Information Services/Warren Library Palm Beach Atlantic University (561) 803-2221 Soli Deo Gloria! -------------- 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 CHRISTOPHER_LOVELL at pba.edu Wed Jun 12 14:27:22 2019 From: CHRISTOPHER_LOVELL at pba.edu (CHRISTOPHER LOVELL) Date: Wed, 12 Jun 2019 18:27:22 +0000 Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 In-Reply-To: References: Message-ID: Dear Christine, Thank you for your reply. I will install Java 1.8 and let you know how it goes. I?m out of the office this week, so my reply may be delayed, but I very much appreciate your suggestion. Best regards, Christopher From: > on behalf of Christine Di Bella > Reply-To: Archivesspace Users Group > Date: Wednesday, June 12, 2019 at 10:41 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Dear Christopher, We?re still researching this, but some other users with Java 1.7 have reported this problem when trying to run 2.6.0. There was a Rails and other infrastructure updates in 2.6.0 and retaining support for this significantly older version of Java may not be possible with these necessary updates. Are you able to update to Java 1.8? That seems to have resolved the issue for others. 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 CHRISTOPHER LOVELL Sent: Wednesday, June 12, 2019 10:35 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Hello all, I just performed a fresh install of the latest release of ArchivesSpace on a Windows 2008 R2 server with Java 1.7.0_55 and am seeing the error ?Could not find childprocess-1.0.1 in any of the sources? in the log. I am unable to determine the cause. Can anyone offer suggestions? Here?s a snip from the beginning of the log file. Thanks in advance for any assistance you can provide. [snip] Loading ArchivesSpace configuration file from path: C:\archivesspace\config/config.rb Jun 12, 2019 10:12:31 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup Could not find childprocess-1.0.1 in any of the sources --- System jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 Java HotSpot(TM) 64-Bit Server VM 24.55-b03 on 1.7.0_55-b13 +jit [mswin32-x86_64] Time: 2019-06-12 10:12:31 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.compat.version = 1.9 jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Bundler::GemNotFound: Could not find childprocess-1.0.1 in any of the sources block in materialize at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88 map! at org/jruby/RubyArray.java:2519 materialize at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82 specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170 specs_for at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237 requested_specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226 block in requested_specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108 setup at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20 setup at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107
at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20 require at org/jruby/RubyKernel.java:956 (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133 require at org/jruby/RubyKernel.java:956 (root) at C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1 block in (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1 instance_eval at org/jruby/RubyBasicObject.java:1691 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
at C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:157
at launcher/launcher.rb:261 --- RubyGems Gem.dir: C:/archivesspace/gems Gem.path: C:/Users/lovellc/.gem/jruby/2.3.0 uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared C:/archivesspace/gems Activated gems: did_you_mean-1.0.1 bundler-1.16.1 --- Bundler Bundler.bundle_path: C:/archivesspace/gems Bundler.root: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF Gemfile: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile Settings: without = [:test, :development, :doc] --- JRuby-Rack Config compat_version = RUBY1_9 default_logger = org.jruby.rack.logging.StandardOutLogger at 30f74da2 equals = err = java.io.PrintStream at d97643c filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 242ca061 logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 46417f28 rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},C:\archivesspace\wars/backend.war throw_init_exception = false Jun 12, 2019 10:12:31 AM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: Could not find childprocess-1.0.1 in any of the sources from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88:in `block in materialize' from org/jruby/RubyArray.java:2519:in `map!' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82:in `materialize' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170:in `specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237:in `specs_for' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226:in `requested_specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108:in `block in requested_specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20:in `setup' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107:in `setup' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20:in `
' from org/jruby/RubyKernel.java:956:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133:in `
' from org/jruby/RubyKernel.java:956:in `require' from C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `block in (root)' from org/jruby/RubyBasicObject.java:1691:in `instance_eval' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:157:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther155:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:178) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:338) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:183) at launcher.launcher.invokeOther290:start_server(launcher/launcher.rb:157) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:157) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther503:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.jruby.ir.Compiler$1.load(Compiler.java:94) at org.jruby.Ruby.runScript(Ruby.java:830) at org.jruby.Ruby.runNormally(Ruby.java:749) at org.jruby.Ruby.runNormally(Ruby.java:767) at org.jruby.Ruby.runFromMain(Ruby.java:580) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (GemNotFound) Could not find childprocess-1.0.1 in any of the sources at RUBY.block in materialize(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88) at org.jruby.RubyArray.map!(org/jruby/RubyArray.java:2519) at RUBY.materialize(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82) at RUBY.specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170) at RUBY.specs_for(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237) at RUBY.requested_specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226) at RUBY.block in requested_specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108) at RUBY.setup(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20) at RUBY.setup(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107) at RUBY.
(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1) at RUBY.block in (root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1691) at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.
(C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:157) at launcher.launcher.
(launcher/launcher.rb:261) Best regards, Christopher Lovell Campus Information Services/Warren Library Palm Beach Atlantic University (561) 803-2221 Soli Deo Gloria! -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 6608 bytes Desc: image003.jpg URL: From cory_nimer at byu.edu Wed Jun 12 17:55:27 2019 From: cory_nimer at byu.edu (Cory Nimer) Date: Wed, 12 Jun 2019 21:55:27 +0000 Subject: [Archivesspace_Users_Group] Call for community input--Proposal for controlled value list enhancement Message-ID: <1789ce105e9444e5b2e73bfa8ad397ad@MB7.byu.local> ArchivesSpace community members, The Development Prioritization Team has requested public comment on a specification for a proposed expansion of ArchivesSpace's controlled value lists to include URI values. The addition of these values would enhance EAD3 and EAC-CPF exports, and improve compatibility with linked data formats. The draft specification is available at https://docs.google.com/document/d/1plu1M-hBT9Q0YfKwwi7i8KhU-iLqhE_G8PpMeaVy1Uo/edit?usp=sharing, and open for commenting. We would be interested in gathering comments and finalizing the document to facilitate the Development Prioritization Team's review. If you could please add comments by June 21, 2019, that would be very helpful. Any questions can also be send to me directly at cory_nimer at byu.edu. Sincerely, Cory Nimer University Archivist Brigham Young University 801-422-6091 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Mon Jun 17 16:12:50 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Mon, 17 Jun 2019 20:12:50 +0000 Subject: [Archivesspace_Users_Group] Deadline Extended! Submissions for the ArchivesSpace Member Forum open until July 1 Message-ID: The deadline for presentation submissions for the fifth Annual Member Forum on August 2, 2019 in Austin, Texas at our member institution, University of Texas-Austin has been extended until July 1! The planning group is specifically looking for proposals for lightning round sessions or discussions to highlight the work individual member intuitions are accomplishing in ArchivesSpace. There is particular interest in presentations related to the development of workflows within institutions that have integrated ArchivesSpace into their daily practice but anything related to ArchivesSpace is fair game. There is a short Google submission form available at https://forms.gle/1xMLNbY81y1hnkL78; you can submit ideas or volunteer yourself to speak either via the form or by emailing Jessica Crouch directly. The deadline for submission has been extended to July 1. Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. More information on the developing program is on the ArchivesSpace wiki at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/863436816/ArchivesSpace+Member+Forum+2019. If you have any questions or other suggestions at this point, please feel free to email Jessica at jessica.crouch at lyrasis.org. We look forward to seeing you in Austin! Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 8548 bytes Desc: image001.jpg URL: From na207 at cam.ac.uk Tue Jun 18 10:10:53 2019 From: na207 at cam.ac.uk (na207) Date: Tue, 18 Jun 2019 14:10:53 +0000 Subject: [Archivesspace_Users_Group] Users with basic data entry credentials and access to agent contact details Message-ID: Dear all, This is my first message to the user group- I've been making great use of the list's archives and am hoping someone may be able to help with my question. I'm working through issues concerning sharing personal data about living individuals in ArchivesSpace- seeking to ensure that personal data is only accessible and shared if necessary and appropriate to comply with the UK Data Protection Act and GDPR. We were lucky enough to receive 2 days training on ArchivesSpace last summer and our training notes about the types of user record set out the following : Basic Data Entry Staff: Has no application customization permissions; is unable to read or write name contact information; has read-only access to Accession, Digital Object, Agent, and Subject records, has read/write permissions on Resource records. I have just set up a test user account and given it basic data entry privileges. When I log in as that user I can view (but not edit) agent records including contact information. The agent records have been created by the repository to which the test user belongs but the test user can also see contact details of agents created by another repository. I have looked at the 'manage groups' menu to check what basic data entry users can do, and found that the following boxes only are checked:- create/update resources in this repository; create/update digital objects in this repository; view the records in this repository; create and run a background job. It doesn't look as though there is another box I could tick to limit access to contact information. I may be missing something obvious but is there a way to limit access to contact information in ArchivesSpace? I would be very grateful for any assistance, Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library West Road Cambridge Cambridge, CB3 9DR Tel 01223 766377 www.lib.cam.ac.uk/ Normal working days are Monday-Wednesday -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jessica.Crouch at lyrasis.org Tue Jun 18 13:12:39 2019 From: Jessica.Crouch at lyrasis.org (Jessica Crouch) Date: Tue, 18 Jun 2019 17:12:39 +0000 Subject: [Archivesspace_Users_Group] Join us for the 5th annual ArchivesSpace Member Forum in Austin, Texas! Message-ID: [cid:image001.jpg at 01D525D7.802C2230] Registration is now open for the ArchivesSpace 5th Annual Member Forum on August 2, 2019, at the Thompson Conference Center at ArchivesSpace member institution the University of Texas at Austin. Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. SCHEDULE OVERVIEW The specifics of the program continue to be shaped by the working group. The most current information is available on the ArchivesSpace wiki page for the forum. * Morning program: The morning will highlight shared stories and experiences through lightning round presentations, focused discussions, and demonstrations. * Lunch: A catered lunch will be provided. * Afternoon program: The afternoon will continue to highlight member experiences through continued discussions and presentations. * Workshops: Two workshops will be provided in the afternoon. Each workshop will be limited to 25 participants. Participants should plan to bring their own laptops. Workshop A will be an introduction to the API and using ArchivesSnake Workshop B will focus on gaining authority control over your ArchivesSpace data * Reception: The day will conclude with a joint reception with Archive-It from 5pm-7pm at the AT&T Executive Education and Conference Center, also on the University of Texas at Austin campus! PARKING & TRANSPORTATION Directions and maps can be found on the ArchivesSpace wiki page for the forum. QUESTIONS? If you have questions, please email Jessica at jessica.crouch at lyrasis.org. Jessica Dowd Crouch Community Engagement Coordinator for ArchivesSpace jessica.crouch at lyrasis.org Skype: jdowdcrouch [page1image482511520] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 628117 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 29058 bytes Desc: image002.jpg URL: From CHRISTOPHER_LOVELL at pba.edu Wed Jun 19 10:20:03 2019 From: CHRISTOPHER_LOVELL at pba.edu (CHRISTOPHER LOVELL) Date: Wed, 19 Jun 2019 14:20:03 +0000 Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 In-Reply-To: References: Message-ID: Dear Christine, I upgraded to Java 1.8 and made additional progress in the ArchivesSpace startup procedures, but am now facing the following error related to net-ldap gem (still during startup). A log snippet follows. Any suggestions? Thanks again for your help! INFO: INFO: jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 OpenJDK Client VM 25.40-b25 on 1.8.0_40-b25 +jit [mswin32-x86] Jun 19, 2019 10:11:43 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: C:\archivesspace\config/config.rb Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: setting default path failed: the trustAnchors parameter must be non-empty Backtrace for gem load error is: org/jruby/ext/openssl/X509Store.java:186:in `set_default_paths' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:26:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `block in require' org/jruby/RubyBasicObject.java:1691:in `instance_eval' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: --- System jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 OpenJDK Client VM 25.40-b25 on 1.8.0_40-b25 +jit [mswin32-x86] Time: 2019-06-19 10:11:47 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.compat.version = 1.9 jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Bundler::GemRequireError: There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: setting default path failed: the trustAnchors parameter must be non-empty Backtrace for gem load error is: org/jruby/ext/openssl/X509Store.java:186:in `set_default_paths' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:26:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `block in require' org/jruby/RubyBasicObject.java:1691:in `instance_eval' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: block in require at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:84 each at org/jruby/RubyArray.java:1735 block in require at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76 each at org/jruby/RubyArray.java:1735 require at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65 require at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114
at C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2 require at org/jruby/RubyKernel.java:956 (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1 block in require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55 instance_eval at org/jruby/RubyBasicObject.java:1691 (root) at C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4
at uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:157
at launcher/launcher.rb:261 --- RubyGems Gem.dir: C:/archivesspace/gems Gem.path: C:/Users/lovellc/.gem/jruby/2.3.0 uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared C:/archivesspace/gems Activated gems: did_you_mean-1.0.1 bundler-1.16.1 rake-12.3.2 concurrent-ruby-1.1.5 i18n-0.9.1 minitest-5.11.3 thread_safe-0.3.6-java tzinfo-1.2.5 activesupport-5.0.7.2 atomic-1.0.1-java backports-3.12.0 bcrypt-3.1.7-java builder-3.2.3 childprocess-1.0.1 choice-0.2.0 multipart-post-1.2.0 faraday-0.15.4 faraday_middleware-0.13.1 fastimage-2.1.5 ffi-1.10.0-java jdbc-derby-10.12.1.1 jruby-jars-9.1.17.0 jruby-rack-1.1.21 json-1.8.6-java json-schema-1.0.10 rack-1.6.11 mizuno-0.6.11 multi_json-1.13.1 net-http-persistent-2.8 net-ldap-0.16.1 nokogiri-1.8.5-java oai-0.4.0 rack-protection-1.5.5 sequel-4.20.0 rack-session-sequel-0.0.1 rack-test-1.1.0 rjack-jackson-1.8.11.0-java tidy-1.1.2 rrtf-1.3.0 rubyzip-1.2.2 rufus-lru-1.0.5 rufus-scheduler-2.0.24 saxerator-0.9.2 saxon-xslt-0.8.2.1-java tilt-2.0.9 sinatra-1.4.7 sinatra-contrib-1.4.7 tzinfo-data-1.2019.1 warbler-2.0.4 zip-zip-0.3 --- Bundler Bundler.bundle_path: C:/archivesspace/gems Bundler.root: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF Gemfile: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile Settings: without = [:test, :development, :doc] bin_path = C:/archivesspace/gems/gems/bundler-1.16.1/exe/bundle gemfile = C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile --- JRuby-Rack Config compat_version = RUBY1_9 default_logger = org.jruby.rack.logging.StandardOutLogger at b90ab3 equals = err = java.io.PrintStream at a0d249 filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 6c84fa logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 688978 rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},C:\archivesspace\wars/backend.war throw_init_exception = false Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: setting default path failed: the trustAnchors parameter must be non-empty Backtrace for gem load error is: org/jruby/ext/openssl/X509Store.java:186:in `set_default_paths' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:26:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `block in require' org/jruby/RubyBasicObject.java:1691:in `instance_eval' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:84:in `block in require' from org/jruby/RubyArray.java:1735:in `each' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `block in require' from org/jruby/RubyArray.java:1735:in `each' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `require' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' from C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' from org/jruby/RubyKernel.java:956:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `block in require' from org/jruby/RubyBasicObject.java:1691:in `instance_eval' from C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4:in `(root)' from uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:157:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther155:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:178) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:338) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:183) at launcher.launcher.invokeOther290:start_server(launcher/launcher.rb:157) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:157) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther503:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:625) at org.jruby.ir.Compiler$1.load(Compiler.java:94) at org.jruby.Ruby.runScript(Ruby.java:830) at org.jruby.Ruby.runNormally(Ruby.java:749) at org.jruby.Ruby.runNormally(Ruby.java:767) at org.jruby.Ruby.runFromMain(Ruby.java:580) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (GemRequireError) There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: setting default path failed: the trustAnchors parameter must be non-empty Backtrace for gem load error is: org/jruby/ext/openssl/X509Store.java:186:in `set_default_paths' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:26:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `block in require' org/jruby/RubyBasicObject.java:1691:in `instance_eval' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: at RUBY.block in require(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:84) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1735) at RUBY.block in require(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1735) at RUBY.require(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65) at RUBY.require(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114) at RUBY.
(C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at RUBY.block in require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1691) at RUBY.(root)(C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4) at RUBY.
(uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:157) at launcher.launcher.
(launcher/launcher.rb:261) Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},C:\archivesspace\wars/backend.war Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8089 Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.Server doStart Best regards, Christopher Lovell Campus Information Services/Warren Library Palm Beach Atlantic University (561) 803-2221 Soli Deo Gloria! 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, June 12, 2019 10:41 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Dear Christopher, We're still researching this, but some other users with Java 1.7 have reported this problem when trying to run 2.6.0. There was a Rails and other infrastructure updates in 2.6.0 and retaining support for this significantly older version of Java may not be possible with these necessary updates. Are you able to update to Java 1.8? That seems to have resolved the issue for others. 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 CHRISTOPHER LOVELL Sent: Wednesday, June 12, 2019 10:35 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Hello all, I just performed a fresh install of the latest release of ArchivesSpace on a Windows 2008 R2 server with Java 1.7.0_55 and am seeing the error "Could not find childprocess-1.0.1 in any of the sources" in the log. I am unable to determine the cause. Can anyone offer suggestions? Here's a snip from the beginning of the log file. Thanks in advance for any assistance you can provide. [snip] Loading ArchivesSpace configuration file from path: C:\archivesspace\config/config.rb Jun 12, 2019 10:12:31 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup Could not find childprocess-1.0.1 in any of the sources --- System jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 Java HotSpot(TM) 64-Bit Server VM 24.55-b03 on 1.7.0_55-b13 +jit [mswin32-x86_64] Time: 2019-06-12 10:12:31 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.compat.version = 1.9 jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Bundler::GemNotFound: Could not find childprocess-1.0.1 in any of the sources block in materialize at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88 map! at org/jruby/RubyArray.java:2519 materialize at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82 specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170 specs_for at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237 requested_specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226 block in requested_specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108 setup at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20 setup at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107
at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20 require at org/jruby/RubyKernel.java:956 (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133 require at org/jruby/RubyKernel.java:956 (root) at C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1 block in (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1 instance_eval at org/jruby/RubyBasicObject.java:1691 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
at C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:157
at launcher/launcher.rb:261 --- RubyGems Gem.dir: C:/archivesspace/gems Gem.path: C:/Users/lovellc/.gem/jruby/2.3.0 uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared C:/archivesspace/gems Activated gems: did_you_mean-1.0.1 bundler-1.16.1 --- Bundler Bundler.bundle_path: C:/archivesspace/gems Bundler.root: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF Gemfile: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile Settings: without = [:test, :development, :doc] --- JRuby-Rack Config compat_version = RUBY1_9 default_logger = org.jruby.rack.logging.StandardOutLogger at 30f74da2 equals = err = java.io.PrintStream at d97643c filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 242ca061 logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 46417f28 rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},C:\archivesspace\wars/backend.war throw_init_exception = false Jun 12, 2019 10:12:31 AM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: Could not find childprocess-1.0.1 in any of the sources from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88:in `block in materialize' from org/jruby/RubyArray.java:2519:in `map!' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82:in `materialize' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170:in `specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237:in `specs_for' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226:in `requested_specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108:in `block in requested_specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20:in `setup' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107:in `setup' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20:in `
' from org/jruby/RubyKernel.java:956:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133:in `
' from org/jruby/RubyKernel.java:956:in `require' from C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `block in (root)' from org/jruby/RubyBasicObject.java:1691:in `instance_eval' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:157:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther155:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:178) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:338) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:183) at launcher.launcher.invokeOther290:start_server(launcher/launcher.rb:157) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:157) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther503:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.jruby.ir.Compiler$1.load(Compiler.java:94) at org.jruby.Ruby.runScript(Ruby.java:830) at org.jruby.Ruby.runNormally(Ruby.java:749) at org.jruby.Ruby.runNormally(Ruby.java:767) at org.jruby.Ruby.runFromMain(Ruby.java:580) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (GemNotFound) Could not find childprocess-1.0.1 in any of the sources at RUBY.block in materialize(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88) at org.jruby.RubyArray.map!(org/jruby/RubyArray.java:2519) at RUBY.materialize(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82) at RUBY.specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170) at RUBY.specs_for(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237) at RUBY.requested_specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226) at RUBY.block in requested_specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108) at RUBY.setup(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20) at RUBY.setup(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107) at RUBY.
(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1) at RUBY.block in (root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1691) at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.
(C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:157) at launcher.launcher.
(launcher/launcher.rb:261) Best regards, Christopher Lovell Campus Information Services/Warren Library Palm Beach Atlantic University (561) 803-2221 Soli Deo Gloria! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4011 bytes Desc: image001.jpg URL: From sdm7g at virginia.edu Wed Jun 19 10:44:53 2019 From: sdm7g at virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Wed, 19 Jun 2019 14:44:53 +0000 Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 In-Reply-To: References: Message-ID: <3945679C-FFC1-43F8-8AAC-C950646D91BF@virginia.edu> Do you have an LDAP configuration that you added to config.rb, or is this error without using or configuring LDAP ? > On Jun 19, 2019, at 10:20 AM, CHRISTOPHER LOVELL wrote: > > > I upgraded to Java 1.8 and made additional progress in the ArchivesSpace startup procedures, but am now facing the following error related to net-ldap gem (still during startup). A log snippet follows. Any suggestions? Thanks again for your help! > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3598 bytes Desc: not available URL: From blake.carver at lyrasis.org Wed Jun 19 10:48:48 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Wed, 19 Jun 2019 14:48:48 +0000 Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 In-Reply-To: References: , Message-ID: In addition to Steve's question, what plugins are you using? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of CHRISTOPHER LOVELL Sent: Wednesday, June 19, 2019 10:20 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Dear Christine, I upgraded to Java 1.8 and made additional progress in the ArchivesSpace startup procedures, but am now facing the following error related to net-ldap gem (still during startup). A log snippet follows. Any suggestions? Thanks again for your help! INFO: INFO: jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 OpenJDK Client VM 25.40-b25 on 1.8.0_40-b25 +jit [mswin32-x86] Jun 19, 2019 10:11:43 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: C:\archivesspace\config/config.rb Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: setting default path failed: the trustAnchors parameter must be non-empty Backtrace for gem load error is: org/jruby/ext/openssl/X509Store.java:186:in `set_default_paths' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:26:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `block in require' org/jruby/RubyBasicObject.java:1691:in `instance_eval' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: --- System jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 OpenJDK Client VM 25.40-b25 on 1.8.0_40-b25 +jit [mswin32-x86] Time: 2019-06-19 10:11:47 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.compat.version = 1.9 jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Bundler::GemRequireError: There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: setting default path failed: the trustAnchors parameter must be non-empty Backtrace for gem load error is: org/jruby/ext/openssl/X509Store.java:186:in `set_default_paths' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:26:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `block in require' org/jruby/RubyBasicObject.java:1691:in `instance_eval' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: block in require at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:84 each at org/jruby/RubyArray.java:1735 block in require at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76 each at org/jruby/RubyArray.java:1735 require at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65 require at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114
at C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2 require at org/jruby/RubyKernel.java:956 (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1 block in require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55 instance_eval at org/jruby/RubyBasicObject.java:1691 (root) at C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4
at uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:157
at launcher/launcher.rb:261 --- RubyGems Gem.dir: C:/archivesspace/gems Gem.path: C:/Users/lovellc/.gem/jruby/2.3.0 uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared C:/archivesspace/gems Activated gems: did_you_mean-1.0.1 bundler-1.16.1 rake-12.3.2 concurrent-ruby-1.1.5 i18n-0.9.1 minitest-5.11.3 thread_safe-0.3.6-java tzinfo-1.2.5 activesupport-5.0.7.2 atomic-1.0.1-java backports-3.12.0 bcrypt-3.1.7-java builder-3.2.3 childprocess-1.0.1 choice-0.2.0 multipart-post-1.2.0 faraday-0.15.4 faraday_middleware-0.13.1 fastimage-2.1.5 ffi-1.10.0-java jdbc-derby-10.12.1.1 jruby-jars-9.1.17.0 jruby-rack-1.1.21 json-1.8.6-java json-schema-1.0.10 rack-1.6.11 mizuno-0.6.11 multi_json-1.13.1 net-http-persistent-2.8 net-ldap-0.16.1 nokogiri-1.8.5-java oai-0.4.0 rack-protection-1.5.5 sequel-4.20.0 rack-session-sequel-0.0.1 rack-test-1.1.0 rjack-jackson-1.8.11.0-java tidy-1.1.2 rrtf-1.3.0 rubyzip-1.2.2 rufus-lru-1.0.5 rufus-scheduler-2.0.24 saxerator-0.9.2 saxon-xslt-0.8.2.1-java tilt-2.0.9 sinatra-1.4.7 sinatra-contrib-1.4.7 tzinfo-data-1.2019.1 warbler-2.0.4 zip-zip-0.3 --- Bundler Bundler.bundle_path: C:/archivesspace/gems Bundler.root: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF Gemfile: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile Settings: without = [:test, :development, :doc] bin_path = C:/archivesspace/gems/gems/bundler-1.16.1/exe/bundle gemfile = C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile --- JRuby-Rack Config compat_version = RUBY1_9 default_logger = org.jruby.rack.logging.StandardOutLogger at b90ab3 equals = err = java.io.PrintStream at a0d249 filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 6c84fa logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 688978 rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},C:\archivesspace\wars/backend.war throw_init_exception = false Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: setting default path failed: the trustAnchors parameter must be non-empty Backtrace for gem load error is: org/jruby/ext/openssl/X509Store.java:186:in `set_default_paths' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:26:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `block in require' org/jruby/RubyBasicObject.java:1691:in `instance_eval' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:84:in `block in require' from org/jruby/RubyArray.java:1735:in `each' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `block in require' from org/jruby/RubyArray.java:1735:in `each' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `require' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' from C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' from org/jruby/RubyKernel.java:956:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `block in require' from org/jruby/RubyBasicObject.java:1691:in `instance_eval' from C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4:in `(root)' from uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:157:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther155:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:178) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:338) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:183) at launcher.launcher.invokeOther290:start_server(launcher/launcher.rb:157) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:157) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther503:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:625) at org.jruby.ir.Compiler$1.load(Compiler.java:94) at org.jruby.Ruby.runScript(Ruby.java:830) at org.jruby.Ruby.runNormally(Ruby.java:749) at org.jruby.Ruby.runNormally(Ruby.java:767) at org.jruby.Ruby.runFromMain(Ruby.java:580) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (GemRequireError) There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: setting default path failed: the trustAnchors parameter must be non-empty Backtrace for gem load error is: org/jruby/ext/openssl/X509Store.java:186:in `set_default_paths' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:26:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `block in require' org/jruby/RubyBasicObject.java:1691:in `instance_eval' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: at RUBY.block in require(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:84) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1735) at RUBY.block in require(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1735) at RUBY.require(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65) at RUBY.require(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114) at RUBY.
(C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at RUBY.block in require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1691) at RUBY.(root)(C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4) at RUBY.
(uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:157) at launcher.launcher.
(launcher/launcher.rb:261) Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},C:\archivesspace\wars/backend.war Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8089 Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.Server doStart Best regards, Christopher Lovell Campus Information Services/Warren Library Palm Beach Atlantic University (561) 803-2221 Soli Deo Gloria! 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, June 12, 2019 10:41 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Dear Christopher, We?re still researching this, but some other users with Java 1.7 have reported this problem when trying to run 2.6.0. There was a Rails and other infrastructure updates in 2.6.0 and retaining support for this significantly older version of Java may not be possible with these necessary updates. Are you able to update to Java 1.8? That seems to have resolved the issue for others. 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 CHRISTOPHER LOVELL Sent: Wednesday, June 12, 2019 10:35 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Hello all, I just performed a fresh install of the latest release of ArchivesSpace on a Windows 2008 R2 server with Java 1.7.0_55 and am seeing the error ?Could not find childprocess-1.0.1 in any of the sources? in the log. I am unable to determine the cause. Can anyone offer suggestions? Here?s a snip from the beginning of the log file. Thanks in advance for any assistance you can provide. [snip] Loading ArchivesSpace configuration file from path: C:\archivesspace\config/config.rb Jun 12, 2019 10:12:31 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup Could not find childprocess-1.0.1 in any of the sources --- System jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 Java HotSpot(TM) 64-Bit Server VM 24.55-b03 on 1.7.0_55-b13 +jit [mswin32-x86_64] Time: 2019-06-12 10:12:31 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.compat.version = 1.9 jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Bundler::GemNotFound: Could not find childprocess-1.0.1 in any of the sources block in materialize at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88 map! at org/jruby/RubyArray.java:2519 materialize at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82 specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170 specs_for at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237 requested_specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226 block in requested_specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108 setup at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20 setup at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107
at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20 require at org/jruby/RubyKernel.java:956 (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133 require at org/jruby/RubyKernel.java:956 (root) at C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1 block in (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1 instance_eval at org/jruby/RubyBasicObject.java:1691 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
at C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:157
at launcher/launcher.rb:261 --- RubyGems Gem.dir: C:/archivesspace/gems Gem.path: C:/Users/lovellc/.gem/jruby/2.3.0 uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared C:/archivesspace/gems Activated gems: did_you_mean-1.0.1 bundler-1.16.1 --- Bundler Bundler.bundle_path: C:/archivesspace/gems Bundler.root: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF Gemfile: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile Settings: without = [:test, :development, :doc] --- JRuby-Rack Config compat_version = RUBY1_9 default_logger = org.jruby.rack.logging.StandardOutLogger at 30f74da2 equals = err = java.io.PrintStream at d97643c filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 242ca061 logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 46417f28 rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},C:\archivesspace\wars/backend.war throw_init_exception = false Jun 12, 2019 10:12:31 AM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: Could not find childprocess-1.0.1 in any of the sources from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88:in `block in materialize' from org/jruby/RubyArray.java:2519:in `map!' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82:in `materialize' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170:in `specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237:in `specs_for' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226:in `requested_specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108:in `block in requested_specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20:in `setup' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107:in `setup' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20:in `
' from org/jruby/RubyKernel.java:956:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133:in `
' from org/jruby/RubyKernel.java:956:in `require' from C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `block in (root)' from org/jruby/RubyBasicObject.java:1691:in `instance_eval' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:157:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther155:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:178) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:338) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:183) at launcher.launcher.invokeOther290:start_server(launcher/launcher.rb:157) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:157) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther503:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.jruby.ir.Compiler$1.load(Compiler.java:94) at org.jruby.Ruby.runScript(Ruby.java:830) at org.jruby.Ruby.runNormally(Ruby.java:749) at org.jruby.Ruby.runNormally(Ruby.java:767) at org.jruby.Ruby.runFromMain(Ruby.java:580) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (GemNotFound) Could not find childprocess-1.0.1 in any of the sources at RUBY.block in materialize(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88) at org.jruby.RubyArray.map!(org/jruby/RubyArray.java:2519) at RUBY.materialize(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82) at RUBY.specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170) at RUBY.specs_for(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237) at RUBY.requested_specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226) at RUBY.block in requested_specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108) at RUBY.setup(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20) at RUBY.setup(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107) at RUBY.
(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1) at RUBY.block in (root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1691) at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.
(C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:157) at launcher.launcher.
(launcher/launcher.rb:261) Best regards, Christopher Lovell Campus Information Services/Warren Library Palm Beach Atlantic University (561) 803-2221 Soli Deo Gloria! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4011 bytes Desc: image001.jpg URL: From CHRISTOPHER_LOVELL at pba.edu Wed Jun 19 10:55:53 2019 From: CHRISTOPHER_LOVELL at pba.edu (CHRISTOPHER LOVELL) Date: Wed, 19 Jun 2019 14:55:53 +0000 Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 In-Reply-To: <3945679C-FFC1-43F8-8AAC-C950646D91BF@virginia.edu> References: <3945679C-FFC1-43F8-8AAC-C950646D91BF@virginia.edu> Message-ID: Thanks for the quick reply. I am running from a fresh install of ArchivesSpace with no changes or additions to anything other than the environment variables as specified on the installation web page, and archivesspace.bat to launch using the correct version of Java. Best regards, Christopher Lovell Campus Information Services/Warren Library Palm Beach Atlantic University (561) 803-2221 Soli Deo Gloria! 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, June 19, 2019 10:45 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Do you have an LDAP configuration that you added to config.rb, or is this error without using or configuring LDAP ? On Jun 19, 2019, at 10:20 AM, CHRISTOPHER LOVELL > wrote: I upgraded to Java 1.8 and made additional progress in the ArchivesSpace startup procedures, but am now facing the following error related to net-ldap gem (still during startup). A log snippet follows. Any suggestions? Thanks again for your help! -------------- next part -------------- An HTML attachment was scrubbed... URL: From CHRISTOPHER_LOVELL at pba.edu Wed Jun 19 11:52:12 2019 From: CHRISTOPHER_LOVELL at pba.edu (CHRISTOPHER LOVELL) Date: Wed, 19 Jun 2019 15:52:12 +0000 Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 In-Reply-To: References: , Message-ID: Blake, Steve, Christine, Though I have been having trouble with the fresh installation of ArchivesSpace on the Windows Server 2008 R2 box that has been the subject of this dialogue, I have had no trouble doing the same thing on a Windows 10 box. So, I copied the JRE from the Windows 10 box (C:\Program Files\Java\jre1.8.0_121) to the Windows 2008 R2 server that has been giving me trouble, updating the environment variables as directed on the ArchivesSpace installation web page, and registering the JRE within the Java control panel. And now, joy! I can browse to the running application on the 2008 Server and the log looks good. Thank you so much for taking the time to help me. Hopefully, this email chain will be of help to someone else in the future. Best regards, Christopher Lovell Campus Information Services/Warren Library Palm Beach Atlantic University (561) 803-2221 Soli Deo Gloria! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Blake Carver Sent: Wednesday, June 19, 2019 10:49 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 In addition to Steve's question, what plugins are you using? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of CHRISTOPHER LOVELL > Sent: Wednesday, June 19, 2019 10:20 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Dear Christine, I upgraded to Java 1.8 and made additional progress in the ArchivesSpace startup procedures, but am now facing the following error related to net-ldap gem (still during startup). A log snippet follows. Any suggestions? Thanks again for your help! INFO: INFO: jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 OpenJDK Client VM 25.40-b25 on 1.8.0_40-b25 +jit [mswin32-x86] Jun 19, 2019 10:11:43 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: C:\archivesspace\config/config.rb Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: setting default path failed: the trustAnchors parameter must be non-empty Backtrace for gem load error is: org/jruby/ext/openssl/X509Store.java:186:in `set_default_paths' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:26:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `block in require' org/jruby/RubyBasicObject.java:1691:in `instance_eval' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: --- System jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 OpenJDK Client VM 25.40-b25 on 1.8.0_40-b25 +jit [mswin32-x86] Time: 2019-06-19 10:11:47 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.compat.version = 1.9 jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Bundler::GemRequireError: There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: setting default path failed: the trustAnchors parameter must be non-empty Backtrace for gem load error is: org/jruby/ext/openssl/X509Store.java:186:in `set_default_paths' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:26:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `block in require' org/jruby/RubyBasicObject.java:1691:in `instance_eval' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: block in require at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:84 each at org/jruby/RubyArray.java:1735 block in require at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76 each at org/jruby/RubyArray.java:1735 require at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65 require at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114
at C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2 require at org/jruby/RubyKernel.java:956 (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1 block in require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55 instance_eval at org/jruby/RubyBasicObject.java:1691 (root) at C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4
at uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:157
at launcher/launcher.rb:261 --- RubyGems Gem.dir: C:/archivesspace/gems Gem.path: C:/Users/lovellc/.gem/jruby/2.3.0 uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared C:/archivesspace/gems Activated gems: did_you_mean-1.0.1 bundler-1.16.1 rake-12.3.2 concurrent-ruby-1.1.5 i18n-0.9.1 minitest-5.11.3 thread_safe-0.3.6-java tzinfo-1.2.5 activesupport-5.0.7.2 atomic-1.0.1-java backports-3.12.0 bcrypt-3.1.7-java builder-3.2.3 childprocess-1.0.1 choice-0.2.0 multipart-post-1.2.0 faraday-0.15.4 faraday_middleware-0.13.1 fastimage-2.1.5 ffi-1.10.0-java jdbc-derby-10.12.1.1 jruby-jars-9.1.17.0 jruby-rack-1.1.21 json-1.8.6-java json-schema-1.0.10 rack-1.6.11 mizuno-0.6.11 multi_json-1.13.1 net-http-persistent-2.8 net-ldap-0.16.1 nokogiri-1.8.5-java oai-0.4.0 rack-protection-1.5.5 sequel-4.20.0 rack-session-sequel-0.0.1 rack-test-1.1.0 rjack-jackson-1.8.11.0-java tidy-1.1.2 rrtf-1.3.0 rubyzip-1.2.2 rufus-lru-1.0.5 rufus-scheduler-2.0.24 saxerator-0.9.2 saxon-xslt-0.8.2.1-java tilt-2.0.9 sinatra-1.4.7 sinatra-contrib-1.4.7 tzinfo-data-1.2019.1 warbler-2.0.4 zip-zip-0.3 --- Bundler Bundler.bundle_path: C:/archivesspace/gems Bundler.root: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF Gemfile: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile Settings: without = [:test, :development, :doc] bin_path = C:/archivesspace/gems/gems/bundler-1.16.1/exe/bundle gemfile = C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile --- JRuby-Rack Config compat_version = RUBY1_9 default_logger = org.jruby.rack.logging.StandardOutLogger at b90ab3 equals = err = java.io.PrintStream at a0d249 filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 6c84fa logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 688978 rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},C:\archivesspace\wars/backend.war throw_init_exception = false Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: setting default path failed: the trustAnchors parameter must be non-empty Backtrace for gem load error is: org/jruby/ext/openssl/X509Store.java:186:in `set_default_paths' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:26:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `block in require' org/jruby/RubyBasicObject.java:1691:in `instance_eval' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:84:in `block in require' from org/jruby/RubyArray.java:1735:in `each' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `block in require' from org/jruby/RubyArray.java:1735:in `each' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `require' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' from C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' from org/jruby/RubyKernel.java:956:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `block in require' from org/jruby/RubyBasicObject.java:1691:in `instance_eval' from C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4:in `(root)' from uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:157:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther155:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:178) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:338) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:183) at launcher.launcher.invokeOther290:start_server(launcher/launcher.rb:157) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:157) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther503:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:625) at org.jruby.ir.Compiler$1.load(Compiler.java:94) at org.jruby.Ruby.runScript(Ruby.java:830) at org.jruby.Ruby.runNormally(Ruby.java:749) at org.jruby.Ruby.runNormally(Ruby.java:767) at org.jruby.Ruby.runFromMain(Ruby.java:580) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (GemRequireError) There was an error while trying to load the gem 'net-ldap'. Gem Load Error is: setting default path failed: the trustAnchors parameter must be non-empty Backtrace for gem load error is: org/jruby/ext/openssl/X509Store.java:186:in `set_default_paths' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/jopenssl/load.rb:26:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `
' org/jruby/RubyKernel.java:956:in `require' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/openssl.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:1:in `' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:7:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:5:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net/ldap.rb:4:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:1:in `block in (root)' org/jruby/RubyArray.java:1735:in `each' C:/archivesspace/gems/gems/net-ldap-0.16.1/lib/net-ldap.rb:2:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:1:in `(root)' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:81:in `
' org/jruby/RubyKernel.java:956:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76:in `require' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65:in `block in require' org/jruby/RubyBasicObject.java:1691:in `instance_eval' C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114:in `require' C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2:in `
' launcher/launcher.rb:92:in `start_server' launcher/launcher.rb:157:in `main' launcher/launcher.rb:261:in `
' Bundler Error Backtrace: at RUBY.block in require(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:84) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1735) at RUBY.block in require(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:76) at org.jruby.RubyArray.each(org/jruby/RubyArray.java:1735) at RUBY.require(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:65) at RUBY.require(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:114) at RUBY.
(C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:2) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at RUBY.block in require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1691) at RUBY.(root)(C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4) at RUBY.
(uri:classloader:/vendor/rack-1.6.8/rack/builder.rb:55) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:157) at launcher.launcher.
(launcher/launcher.rb:261) Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.handler.ContextHandler callContextInitialized INFO: started o.e.j.w.WebAppContext{/,file:/C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},C:\archivesspace\wars/backend.war Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.AbstractConnector doStart INFO: Started SelectChannelConnector at 0.0.0.0:8089 Jun 19, 2019 10:11:47 AM org.eclipse.jetty.server.Server doStart Best regards, Christopher Lovell Campus Information Services/Warren Library Palm Beach Atlantic University (561) 803-2221 Soli Deo Gloria! 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, June 12, 2019 10:41 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Dear Christopher, We're still researching this, but some other users with Java 1.7 have reported this problem when trying to run 2.6.0. There was a Rails and other infrastructure updates in 2.6.0 and retaining support for this significantly older version of Java may not be possible with these necessary updates. Are you able to update to Java 1.8? That seems to have resolved the issue for others. 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 CHRISTOPHER LOVELL Sent: Wednesday, June 12, 2019 10:35 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1 Hello all, I just performed a fresh install of the latest release of ArchivesSpace on a Windows 2008 R2 server with Java 1.7.0_55 and am seeing the error "Could not find childprocess-1.0.1 in any of the sources" in the log. I am unable to determine the cause. Can anyone offer suggestions? Here's a snip from the beginning of the log file. Thanks in advance for any assistance you can provide. [snip] Loading ArchivesSpace configuration file from path: C:\archivesspace\config/config.rb Jun 12, 2019 10:12:31 AM org.eclipse.jetty.server.handler.ContextHandler$Context log INFO: An exception happened during JRuby-Rack startup Could not find childprocess-1.0.1 in any of the sources --- System jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 Java HotSpot(TM) 64-Bit Server VM 24.55-b03 on 1.7.0_55-b13 +jit [mswin32-x86_64] Time: 2019-06-12 10:12:31 -0400 Server: jetty/8.1.5.v20120716 jruby.home: uri:classloader://META-INF/jruby.home --- Context Init Parameters: jruby.compat.version = 1.9 jruby.max.runtimes = 1 jruby.min.runtimes = 1 public.root = / rack.env = production --- Backtrace Bundler::GemNotFound: Could not find childprocess-1.0.1 in any of the sources block in materialize at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88 map! at org/jruby/RubyArray.java:2519 materialize at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82 specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170 specs_for at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237 requested_specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226 block in requested_specs at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108 setup at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20 setup at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107
at C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20 require at org/jruby/RubyKernel.java:956 (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1
at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133 require at org/jruby/RubyKernel.java:956 (root) at C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1 block in (root) at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1 instance_eval at org/jruby/RubyBasicObject.java:1691 require at uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
at C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4 start_server at launcher/launcher.rb:92 main at launcher/launcher.rb:157
at launcher/launcher.rb:261 --- RubyGems Gem.dir: C:/archivesspace/gems Gem.path: C:/Users/lovellc/.gem/jruby/2.3.0 uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared C:/archivesspace/gems Activated gems: did_you_mean-1.0.1 bundler-1.16.1 --- Bundler Bundler.bundle_path: C:/archivesspace/gems Bundler.root: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF Gemfile: C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile Settings: without = [:test, :development, :doc] --- JRuby-Rack Config compat_version = RUBY1_9 default_logger = org.jruby.rack.logging.StandardOutLogger at 30f74da2 equals = err = java.io.PrintStream at d97643c filter_adds_html = true filter_verifies_resource = false ignore_environment = false initial_memory_buffer_size = initial_runtimes = 1 jms_connection_factory = jms_jndi_properties = logger = org.jruby.rack.logging.ServletContextLogger at 242ca061 logger_class_name = servlet_context logger_name = jruby.rack maximum_memory_buffer_size = maximum_runtimes = 1 num_initializer_threads = out = java.io.PrintStream at 46417f28 rackup = rackup_path = rewindable = true runtime_arguments = runtime_environment = runtime_timeout_seconds = serial_initialization = false servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/},C:\archivesspace\wars/backend.war throw_init_exception = false Jun 12, 2019 10:12:31 AM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: ERROR: initialization failed org.jruby.rack.RackInitializationException: Could not find childprocess-1.0.1 in any of the sources from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88:in `block in materialize' from org/jruby/RubyArray.java:2519:in `map!' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82:in `materialize' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170:in `specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237:in `specs_for' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226:in `requested_specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108:in `block in requested_specs' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20:in `setup' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107:in `setup' from C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20:in `
' from org/jruby/RubyKernel.java:956:in `require' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133:in `
' from org/jruby/RubyKernel.java:956:in `require' from C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1:in `(root)' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `block in (root)' from org/jruby/RubyBasicObject.java:1691:in `instance_eval' from uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in `require' from C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4:in `
' from launcher/launcher.rb:92:in `start_server' from launcher/launcher.rb:157:in `main' from launcher/launcher.rb:261:in `
' at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:438) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:302) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther155:start(launcher/launcher.rb:92) at launcher.launcher.RUBY$method$start_server$1(launcher/launcher.rb:92) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:77) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:178) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:338) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:183) at launcher.launcher.invokeOther290:start_server(launcher/launcher.rb:157) at launcher.launcher.RUBY$method$main$6(launcher/launcher.rb:157) at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:155) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:298) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:127) at launcher.launcher.invokeOther503:main(launcher/launcher.rb:261) at launcher.launcher.RUBY$script(launcher/launcher.rb:261) at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown Source) at org.jruby.ir.Compiler$1.load(Compiler.java:94) at org.jruby.Ruby.runScript(Ruby.java:830) at org.jruby.Ruby.runNormally(Ruby.java:749) at org.jruby.Ruby.runNormally(Ruby.java:767) at org.jruby.Ruby.runFromMain(Ruby.java:580) at org.jruby.Main.doRunFromMain(Main.java:417) at org.jruby.Main.internalRun(Main.java:305) at org.jruby.Main.run(Main.java:232) at org.jruby.Main.main(Main.java:204) Caused by: org.jruby.exceptions.RaiseException: (GemNotFound) Could not find childprocess-1.0.1 in any of the sources at RUBY.block in materialize(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88) at org.jruby.RubyArray.map!(org/jruby/RubyArray.java:2519) at RUBY.materialize(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82) at RUBY.specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170) at RUBY.specs_for(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237) at RUBY.requested_specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226) at RUBY.block in requested_specs(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108) at RUBY.setup(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20) at RUBY.setup(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107) at RUBY.
(C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at RUBY.
(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133) at org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:956) at RUBY.(root)(C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1) at RUBY.block in (root)(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1) at org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1691) at RUBY.require(uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55) at RUBY.
(C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4) at launcher.launcher.start_server(launcher/launcher.rb:92) at launcher.launcher.main(launcher/launcher.rb:157) at launcher.launcher.
(launcher/launcher.rb:261) Best regards, Christopher Lovell Campus Information Services/Warren Library Palm Beach Atlantic University (561) 803-2221 Soli Deo Gloria! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4011 bytes Desc: image001.jpg URL: From kstrosch at wellesley.edu Thu Jun 20 11:39:23 2019 From: kstrosch at wellesley.edu (Kara Hart) Date: Thu, 20 Jun 2019 11:39:23 -0400 Subject: [Archivesspace_Users_Group] Ubuntu server configuration for fresh install of 2.6.0 Message-ID: Hi community, We are running ArchivesSpace 2.5.1 using MySQL 5.5.54 Apache 2.2.22 OpenJDK java version 1.7.0_65 on a Ubuntu 12.04 server. As Ubuntu 12.04 is no longer supported, we are looking to upgrade the server as well as to version 2.6.0 of ArchivesSpace (also requires a java update apparently). My IT Systems staff are asking what I need/want on the new server and I'm feeling a little unsure because of the vagueness of the Systems Requirements in the documentation. I was wondering if others would share their server setups for Ubuntu or what you would use if you were upgrading to a fresh server. Is anyone using Ubuntu 18.04? or would 16.04 be more advisable? What version of Ubuntu, MySQL, Java? Apache? (see question below) >From chatter on another post it appears we would need OpenJDK 8 and not 9 to run AS 2.6.0. Does that also exclude OpenJDK 10 and 11? I also would like to clarify that AS doesn't need a web server? I see no mention of Apache or the like on Application System Requirements, yet when I look at the pages to set up AS to over HTTPS it "assumes a server with Apache or Nginx" So is it using Apache on my current server or only if/when I implement HTTPS? Thanks for any thoughts and clarifications! Kara ~~~ Kara S. Hart Systems Librarian - Library & Technology Services - Wellesley College -------------- next part -------------- An HTML attachment was scrubbed... URL: From kayiwa at princeton.edu Thu Jun 20 11:52:41 2019 From: kayiwa at princeton.edu (Francis Kayiwa) Date: Thu, 20 Jun 2019 11:52:41 -0400 Subject: [Archivesspace_Users_Group] Ubuntu server configuration for fresh install of 2.6.0 In-Reply-To: References: Message-ID: Heya, My responses interleaved below On 6/20/19 11:39 AM, Kara Hart wrote: > Hi community, > We are running ArchivesSpace 2.5.1 using MySQL 5.5.54 Apache 2.2.22 > OpenJDK java version 1.7.0_65 on a Ubuntu 12.04 server.? As Ubuntu 12.04 > is no longer supported, we are looking to upgrade the server as well as > to version 2.6.0 of ArchivesSpace (also requires a java update > apparently).? ?My IT Systems staff are asking what I need/want on the > new server and I'm feeling a little unsure because of the vagueness of > the Systems Requirements in the documentation.? > > I was wondering if others would share their server setups for Ubuntu or > what you would use if you were upgrading to a fresh server. Is anyone > using Ubuntu 18.04?? or would 16.04 be more advisable?? > What version of Ubuntu, MySQL, Java? Apache? (see question below) > I'd skip to 18.04 if only because you'll lengthen the long term support of the Ubuntu project. We use mariadb 10.2 and moving this to percona (it is on an externally hosted Cluster but can run locally) > From chatter on another post it appears we would need OpenJDK 8 and not > 9 to run AS 2.6.0.? Does that also exclude OpenJDK 10 and 11? We are using OpenJDK8 > > I also would like to clarify that AS doesn't need a web server?? I see > no mention of Apache or the like on Application System Requirements, yet > when I look at the pages to set up AS to over HTTPS it "assumes a server > with Apache or Nginx" So is it using Apache on my current server or only > if/when I implement HTTPS?? You will need a reverse proxy (both Nginx and Apache can do this) because by default archivesspace will be broadcasting on port 8080/8081. So traffic to your instance will do patron <-> Apache/Nginx (443:80) <-> archivesspace (8080/8081) This is gross over simplification because you could also put this as a servlet on Apache Tomcat (I think) Cheers, ./fxk > > Thanks for any thoughts and clarifications! From blake.carver at lyrasis.org Thu Jun 20 13:35:15 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Thu, 20 Jun 2019 17:35:15 +0000 Subject: [Archivesspace_Users_Group] Ubuntu server configuration for fresh install of 2.6.0 In-Reply-To: References: , Message-ID: I'll second what Francis said. Go with Ubuntu 18, and it should run on any MySQL, though it's happiest with 5.latest. Get as much RAM and procs as you can, ArchivesSpace is happiest with at least 2gigs in general. It does require Java 8 right now for 2.6, though that'll likely change. You only need to go the Apache/nginx route if you want to drop the ports and run it on a real domain name and/or enable TLS. If you're running the public side and that's on a public network, you'll want to do that. I think many people just run it on localhost:8080 or some ip address :8080. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Francis Kayiwa Sent: Thursday, June 20, 2019 11:52 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Ubuntu server configuration for fresh install of 2.6.0 Heya, My responses interleaved below On 6/20/19 11:39 AM, Kara Hart wrote: > Hi community, > We are running ArchivesSpace 2.5.1 using MySQL 5.5.54 Apache 2.2.22 > OpenJDK java version 1.7.0_65 on a Ubuntu 12.04 server. As Ubuntu 12.04 > is no longer supported, we are looking to upgrade the server as well as > to version 2.6.0 of ArchivesSpace (also requires a java update > apparently). My IT Systems staff are asking what I need/want on the > new server and I'm feeling a little unsure because of the vagueness of > the Systems Requirements in the documentation. > > I was wondering if others would share their server setups for Ubuntu or > what you would use if you were upgrading to a fresh server. Is anyone > using Ubuntu 18.04? or would 16.04 be more advisable? > What version of Ubuntu, MySQL, Java? Apache? (see question below) > I'd skip to 18.04 if only because you'll lengthen the long term support of the Ubuntu project. We use mariadb 10.2 and moving this to percona (it is on an externally hosted Cluster but can run locally) > From chatter on another post it appears we would need OpenJDK 8 and not > 9 to run AS 2.6.0. Does that also exclude OpenJDK 10 and 11? We are using OpenJDK8 > > I also would like to clarify that AS doesn't need a web server? I see > no mention of Apache or the like on Application System Requirements, yet > when I look at the pages to set up AS to over HTTPS it "assumes a server > with Apache or Nginx" So is it using Apache on my current server or only > if/when I implement HTTPS? You will need a reverse proxy (both Nginx and Apache can do this) because by default archivesspace will be broadcasting on port 8080/8081. So traffic to your instance will do patron <-> Apache/Nginx (443:80) <-> archivesspace (8080/8081) This is gross over simplification because you could also put this as a servlet on Apache Tomcat (I think) Cheers, ./fxk > > Thanks for any thoughts and clarifications! _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Jun 21 08:29:28 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 21 Jun 2019 12:29:28 +0000 Subject: [Archivesspace_Users_Group] Users with basic data entry credentials and access to agent contact details In-Reply-To: References: Message-ID: Dear Natalie, First off, welcome! Your mention of our training materials and the implications of this particular permission for the UK Data Protection Act and GDPR made us look to see what was happening in the application. As far as we can tell, all permission levels with access to view agent records have been able to view the contact details part of the record. This is clearly not what was intended, given how this was written up for the purposes of training and the user manual. And we know it's an even more important feature now given international laws around securing personal information. I'm pleased to say that one of our developers was able to determine what was wrong and to add a specific permission for viewing the contact details part of an agent record. This permission will be automatically included for the out-of-the-box permission levels above Advanced Data Entry users and also selectable if high level users want to include it for other permission groups (and de-selectable if people don't want it included for the permission groups for which it comes automatically). This feature will need additional testing, but assuming it passes muster, we anticipate including it in our next release, which will come out later in the summer. We've added a JIRA issue (https://archivesspace.atlassian.net/browse/ANW-910) and work can be tracked there. Thanks for bringing this oversight to our attention. We typically can't make changes to the application as quickly as this, but I'm glad it was possible in this case. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of na207 Sent: Tuesday, June 18, 2019 10:11 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Users with basic data entry credentials and access to agent contact details Dear all, This is my first message to the user group- I've been making great use of the list's archives and am hoping someone may be able to help with my question. I'm working through issues concerning sharing personal data about living individuals in ArchivesSpace- seeking to ensure that personal data is only accessible and shared if necessary and appropriate to comply with the UK Data Protection Act and GDPR. We were lucky enough to receive 2 days training on ArchivesSpace last summer and our training notes about the types of user record set out the following : Basic Data Entry Staff: Has no application customization permissions; is unable to read or write name contact information; has read-only access to Accession, Digital Object, Agent, and Subject records, has read/write permissions on Resource records. I have just set up a test user account and given it basic data entry privileges. When I log in as that user I can view (but not edit) agent records including contact information. The agent records have been created by the repository to which the test user belongs but the test user can also see contact details of agents created by another repository. I have looked at the 'manage groups' menu to check what basic data entry users can do, and found that the following boxes only are checked:- create/update resources in this repository; create/update digital objects in this repository; view the records in this repository; create and run a background job. It doesn't look as though there is another box I could tick to limit access to contact information. I may be missing something obvious but is there a way to limit access to contact information in ArchivesSpace? I would be very grateful for any assistance, Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library West Road Cambridge Cambridge, CB3 9DR Tel 01223 766377 www.lib.cam.ac.uk/ Normal working days are Monday-Wednesday -------------- 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 benn.joseph at northwestern.edu Fri Jun 21 13:39:29 2019 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Fri, 21 Jun 2019 17:39:29 +0000 Subject: [Archivesspace_Users_Group] barcode validation for ASpace Message-ID: Good afternoon, Over the past few years, our standard procedure when processing a new collection has been to barcode the finished boxes and assign those barcodes to their Top Containers in ASpace. ArchivesSpace does a great job of keeping a user from assigning a barcode that has already been assigned elsewhere--which we recently discovered after mistakenly being given a sheet of piggyback barcodes that had already been assigned to various other collections. The system reports an error: "Barcode - A barcode must be unique within a repository". Great! One thing it doesn't do is check for valid barcodes against a schema. For instance, we try to be very careful about only using barcode scanners to enter barcodes into ArchivesSpace, but every now and then one will get entered by hand, or there will be an accidental keystroke after scanning. In those cases, it would be ideal if ASpace were able to validate this number to ensure that it's correct (I understand that Alma does this using a Codabar 13 validation routine, though there are other validation options that would also look for a check digit). Would this be a plugin? A feature request? Would it even be possible? The reason it's important for us to ensure barcode accuracy is that a large volume of our collections get sent offsite to a facility that uses GFA as their inventory system. So, if we enter the barcode for a box that is incorrect in ASpace and GFA records it differently, it ends up being very difficult to recall that box if a researcher requests it. 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 na207 at cam.ac.uk Mon Jun 24 04:06:16 2019 From: na207 at cam.ac.uk (na207) Date: Mon, 24 Jun 2019 08:06:16 +0000 Subject: [Archivesspace_Users_Group] Users with basic data entry credentials and access to agent contact details In-Reply-To: References: Message-ID: Dear Christine, This is excellent news- thank you very much! Best wishes, Natalie From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Christine Di Bella Sent: 21 June 2019 13:29 To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Users with basic data entry credentials and access to agent contact details Dear Natalie, First off, welcome! Your mention of our training materials and the implications of this particular permission for the UK Data Protection Act and GDPR made us look to see what was happening in the application. As far as we can tell, all permission levels with access to view agent records have been able to view the contact details part of the record. This is clearly not what was intended, given how this was written up for the purposes of training and the user manual. And we know it's an even more important feature now given international laws around securing personal information. I'm pleased to say that one of our developers was able to determine what was wrong and to add a specific permission for viewing the contact details part of an agent record. This permission will be automatically included for the out-of-the-box permission levels above Advanced Data Entry users and also selectable if high level users want to include it for other permission groups (and de-selectable if people don't want it included for the permission groups for which it comes automatically). This feature will need additional testing, but assuming it passes muster, we anticipate including it in our next release, which will come out later in the summer. We've added a JIRA issue (https://archivesspace.atlassian.net/browse/ANW-910) and work can be tracked there. Thanks for bringing this oversight to our attention. We typically can't make changes to the application as quickly as this, but I'm glad it was possible in this case. Christine Christine Di Bella ArchivesSpace Program Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of na207 Sent: Tuesday, June 18, 2019 10:11 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Users with basic data entry credentials and access to agent contact details Dear all, This is my first message to the user group- I've been making great use of the list's archives and am hoping someone may be able to help with my question. I'm working through issues concerning sharing personal data about living individuals in ArchivesSpace- seeking to ensure that personal data is only accessible and shared if necessary and appropriate to comply with the UK Data Protection Act and GDPR. We were lucky enough to receive 2 days training on ArchivesSpace last summer and our training notes about the types of user record set out the following : Basic Data Entry Staff: Has no application customization permissions; is unable to read or write name contact information; has read-only access to Accession, Digital Object, Agent, and Subject records, has read/write permissions on Resource records. I have just set up a test user account and given it basic data entry privileges. When I log in as that user I can view (but not edit) agent records including contact information. The agent records have been created by the repository to which the test user belongs but the test user can also see contact details of agents created by another repository. I have looked at the 'manage groups' menu to check what basic data entry users can do, and found that the following boxes only are checked:- create/update resources in this repository; create/update digital objects in this repository; view the records in this repository; create and run a background job. It doesn't look as though there is another box I could tick to limit access to contact information. I may be missing something obvious but is there a way to limit access to contact information in ArchivesSpace? I would be very grateful for any assistance, Best wishes, Natalie Natalie Adams Systems Archivist Cambridge University Library West Road Cambridge Cambridge, CB3 9DR Tel 01223 766377 www.lib.cam.ac.uk/ Normal working days are Monday-Wednesday -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4014 bytes Desc: image001.jpg URL: From PGalligan at rockarch.org Mon Jun 24 09:03:01 2019 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Mon, 24 Jun 2019 13:03:01 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Integrations Survey Message-ID: <8884BAAC-0310-44A1-9531-6272B0194075@rockarch.org> Hi all, The ArchivesSpace Technical Advisory Council?s Integrations subteam has been working on a survey to gather more information about desired systems integrations with ArchivesSpace and we?d be extremely grateful if you filled it out. The survey should only take 10-15 minutes at most. You can find the survey here: https://forms.gle/VR6UwqqQ4SXfyKav6 Please fill out this survey if you have any interest at all in ASpace software integrations. You do not have to be a member institution or currently be using ASpace. The results of this survey will help you and the ASpace community. Our goals are to: 1) produce anonymized public findings about what integrations the community wants and 2) identify and facilitate integrations collaborations with partners. It's important to note that the results of this survey alone will not determine what integrations work gets done and by whom. But, we have high hopes that the results will inform and drive future community work. Once again, you can find the survey here. Let us know if you have any questions or concerns. Thanks! -- Patrick Galligan Digital Archivist Rockefeller Archive Center (914) 366-6386 He/Him/His -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexanderduryee at nypl.org Mon Jun 24 10:21:57 2019 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Mon, 24 Jun 2019 10:21:57 -0400 Subject: [Archivesspace_Users_Group] barcode validation for ASpace In-Reply-To: References: Message-ID: Benn, It's possible to validate barcodes for length via ASpace by modifying config.rb (ref. https://github.com/archivesspace/archivesspace/blob/master/docs/user/configuring-archivesspace.md). If the min and max values are set to the same length, then barcodes will only validate if they're either 0 or that exact length. You won't need to do anything elaborate to implement this - just add the correct values to config.rb and restart ASpace, and it'll immediately go into effect. I'm not aware of anything in ASpace that will do more elaborate validation (e.g. verifying that a barcode's check digits are correct); this would likely require either a plugin or feature request. Thanks, --Alex On Fri, Jun 21, 2019 at 1:39 PM Benn Joseph wrote: > Good afternoon, > > Over the past few years, our standard procedure when processing a new > collection has been to barcode the finished boxes and assign those barcodes > to their Top Containers in ASpace. > > > > ArchivesSpace does a great job of keeping a user from assigning a barcode > that has already been assigned elsewhere--which we recently discovered > after mistakenly being given a sheet of piggyback barcodes that had already > been assigned to various other collections. The system reports an error: > ?Barcode ? A barcode must be unique within a repository?. Great! > > > > One thing it doesn?t do is check for valid barcodes against a schema. For > instance, we try to be very careful about only using barcode scanners to > enter barcodes into ArchivesSpace, but every now and then one will get > entered by hand, or there will be an accidental keystroke after scanning. > In those cases, it would be ideal if ASpace were able to validate this > number to ensure that it?s correct (I understand that Alma does this using > a Codabar 13 validation routine, though there are other validation options > that would also look for a check digit). Would this be a plugin? A feature > request? Would it even be possible? > > > > The reason it?s important for us to ensure barcode accuracy is that a > large volume of our collections get sent offsite to a facility that uses > GFA as their inventory system. So, if we enter the barcode for a box that > is incorrect in ASpace and GFA records it differently, it ends up being > very difficult to recall that box if a researcher requests it. > > > > 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 > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From kbreneman at ubalt.edu Mon Jun 24 10:44:04 2019 From: kbreneman at ubalt.edu (Kyle Breneman) Date: Mon, 24 Jun 2019 14:44:04 +0000 Subject: [Archivesspace_Users_Group] Custom search box? Message-ID: Does anyone out there have a working custom search box for ArchivesSpace? We had a custom search box for ArchivesSpace on our library homepage, but it quit working several updates ago, and I never could figure out what was wrong. Regards, Kyle Breneman Integrated Digital Services Librarian University of Baltimore kbreneman at ubalt.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Mon Jun 24 11:43:31 2019 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 24 Jun 2019 15:43:31 +0000 Subject: [Archivesspace_Users_Group] barcode validation for ASpace In-Reply-To: References: Message-ID: Benn, Alex is exactly right. At Yale, we use the length configuration to help ensure a basic level of validity (one of our repositories has 9 character barcodes, and the rest have 14 character barcodes). I can also add that during the development of the top container module, I was hopeful that we might be able to include the ability to validate check digits for a few different barcoding systems as additional configuration options. It was decided not to pursue that option at the time, but I imagine that such a thing could definitely be handled in a plugin. I?m not entirely sure how it would be handled throughout the application, but I expect that it could be baked into the JSON and database schemas. I wrote a process in XSLT to verify barcode check digits according to the Luhn algorithm (https://en.wikipedia.org/wiki/Luhn_algorithm), if that would be of interest. What types of barcodes do you use? I had been meaning to add the barcode-digit check to our EAD validation process at some point anyway, so this is a good reminder to do that ?. So far, I have just been using that check during a project to reconcile item records in our ILS with top container records in ArchivesSpace. In each case, I?ve stumbled across a handful of barcodes with invalid check digits, so you?re right that those errors definitely will creep in when left unchecked. 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: Monday, 24 June, 2019 10:22 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] barcode validation for ASpace Benn, It's possible to validate barcodes for length via ASpace by modifying config.rb (ref. https://github.com/archivesspace/archivesspace/blob/master/docs/user/configuring-archivesspace.md). If the min and max values are set to the same length, then barcodes will only validate if they're either 0 or that exact length. You won't need to do anything elaborate to implement this - just add the correct values to config.rb and restart ASpace, and it'll immediately go into effect. I'm not aware of anything in ASpace that will do more elaborate validation (e.g. verifying that a barcode's check digits are correct); this would likely require either a plugin or feature request. Thanks, --Alex On Fri, Jun 21, 2019 at 1:39 PM Benn Joseph > wrote: Good afternoon, Over the past few years, our standard procedure when processing a new collection has been to barcode the finished boxes and assign those barcodes to their Top Containers in ASpace. ArchivesSpace does a great job of keeping a user from assigning a barcode that has already been assigned elsewhere--which we recently discovered after mistakenly being given a sheet of piggyback barcodes that had already been assigned to various other collections. The system reports an error: ?Barcode ? A barcode must be unique within a repository?. Great! One thing it doesn?t do is check for valid barcodes against a schema. For instance, we try to be very careful about only using barcode scanners to enter barcodes into ArchivesSpace, but every now and then one will get entered by hand, or there will be an accidental keystroke after scanning. In those cases, it would be ideal if ASpace were able to validate this number to ensure that it?s correct (I understand that Alma does this using a Codabar 13 validation routine, though there are other validation options that would also look for a check digit). Would this be a plugin? A feature request? Would it even be possible? The reason it?s important for us to ensure barcode accuracy is that a large volume of our collections get sent offsite to a facility that uses GFA as their inventory system. So, if we enter the barcode for a box that is incorrect in ASpace and GFA records it differently, it ends up being very difficult to recall that box if a researcher requests it. 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 -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From amstangl at morris.umn.edu Mon Jun 24 12:19:10 2019 From: amstangl at morris.umn.edu (Angela Stangl) Date: Mon, 24 Jun 2019 11:19:10 -0500 Subject: [Archivesspace_Users_Group] Error Update from Archives 2.2 to 2.3 Message-ID: Hello! Has anyone else encountered this problem? We are updating from 2.2 to 2.3 and are seeing a database migration error saying "DROP FUNCTION IF EXISTS" when running the set up database script in 2.3 coming from version 2.2. Thank you for any advice! Angela Stangl Digital Services Coordinator | Rodney A. Briggs Library | library.morris.umn.edu University of Minnesota, Morris | morris.umn.edu amstangl at morris.umn.edu | (320) 589-6164 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcaffrey at towson.edu Mon Jun 24 17:39:28 2019 From: jcaffrey at towson.edu (Caffrey, Julia) Date: Mon, 24 Jun 2019 21:39:28 +0000 Subject: [Archivesspace_Users_Group] Custom search box? In-Reply-To: References: Message-ID: Hi Kyle!! I am not surprised to hear this. There are some special characters in the values that have to be passed through in recent versions, including the check symbol (??), which is downright strange. If anyone from development wants to chime in with why that was done, I'd be curious. In any case, we have one up and running at https://libraries.towson.edu/university-archives Best of luck!! Julia From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Kyle Breneman Sent: Monday, June 24, 2019 10:44 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Custom search box? Does anyone out there have a working custom search box for ArchivesSpace? We had a custom search box for ArchivesSpace on our library homepage, but it quit working several updates ago, and I never could figure out what was wrong. Regards, Kyle Breneman Integrated Digital Services Librarian University of Baltimore kbreneman at ubalt.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From benn.joseph at northwestern.edu Tue Jun 25 16:00:32 2019 From: benn.joseph at northwestern.edu (Benn Joseph) Date: Tue, 25 Jun 2019 20:00:32 +0000 Subject: [Archivesspace_Users_Group] barcode validation for ASpace In-Reply-To: References: Message-ID: <88d01e3ad1fe4e9993e7937a5bc6368a@evcspmbx04.ads.northwestern.edu> Alex, Mark, Thanks for this! We use 14 character barcodes, so I think for now our best immediate approach will be to modify our config.rb file so that the min and max values are both set to 14. That will at least keep us from going forward with entries that are the wrong length (we do have those, and they stand out pretty clearly in a list). Mark, we just have the same Codabar (I think) labels that the rest of the library uses, like for books and such, for which we can use Mod 10 (Luhn algorithm) to determine the check digit. So yes, that XSLT process would be useful! James Bullen at Hudson Molonglo also sent along this, as a proof of concept plugin for the same verification algorithm (thanks James!): https://github.com/jambun/as_barcode_validator_poc I?m not a programmer, but this may be something we can try out on our local sandbox. --Benn From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Custer, Mark Sent: Monday, June 24, 2019 10:44 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] barcode validation for ASpace Benn, Alex is exactly right. At Yale, we use the length configuration to help ensure a basic level of validity (one of our repositories has 9 character barcodes, and the rest have 14 character barcodes). I can also add that during the development of the top container module, I was hopeful that we might be able to include the ability to validate check digits for a few different barcoding systems as additional configuration options. It was decided not to pursue that option at the time, but I imagine that such a thing could definitely be handled in a plugin. I?m not entirely sure how it would be handled throughout the application, but I expect that it could be baked into the JSON and database schemas. I wrote a process in XSLT to verify barcode check digits according to the Luhn algorithm (https://en.wikipedia.org/wiki/Luhn_algorithm), if that would be of interest. What types of barcodes do you use? I had been meaning to add the barcode-digit check to our EAD validation process at some point anyway, so this is a good reminder to do that ?. So far, I have just been using that check during a project to reconcile item records in our ILS with top container records in ArchivesSpace. In each case, I?ve stumbled across a handful of barcodes with invalid check digits, so you?re right that those errors definitely will creep in when left unchecked. 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: Monday, 24 June, 2019 10:22 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] barcode validation for ASpace Benn, It's possible to validate barcodes for length via ASpace by modifying config.rb (ref. https://github.com/archivesspace/archivesspace/blob/master/docs/user/configuring-archivesspace.md). If the min and max values are set to the same length, then barcodes will only validate if they're either 0 or that exact length. You won't need to do anything elaborate to implement this - just add the correct values to config.rb and restart ASpace, and it'll immediately go into effect. I'm not aware of anything in ASpace that will do more elaborate validation (e.g. verifying that a barcode's check digits are correct); this would likely require either a plugin or feature request. Thanks, --Alex On Fri, Jun 21, 2019 at 1:39 PM Benn Joseph > wrote: Good afternoon, Over the past few years, our standard procedure when processing a new collection has been to barcode the finished boxes and assign those barcodes to their Top Containers in ASpace. ArchivesSpace does a great job of keeping a user from assigning a barcode that has already been assigned elsewhere--which we recently discovered after mistakenly being given a sheet of piggyback barcodes that had already been assigned to various other collections. The system reports an error: ?Barcode ? A barcode must be unique within a repository?. Great! One thing it doesn?t do is check for valid barcodes against a schema. For instance, we try to be very careful about only using barcode scanners to enter barcodes into ArchivesSpace, but every now and then one will get entered by hand, or there will be an accidental keystroke after scanning. In those cases, it would be ideal if ASpace were able to validate this number to ensure that it?s correct (I understand that Alma does this using a Codabar 13 validation routine, though there are other validation options that would also look for a check digit). Would this be a plugin? A feature request? Would it even be possible? The reason it?s important for us to ensure barcode accuracy is that a large volume of our collections get sent offsite to a facility that uses GFA as their inventory system. So, if we enter the barcode for a box that is incorrect in ASpace and GFA records it differently, it ends up being very difficult to recall that box if a researcher requests it. 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 -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From npwb2 at cam.ac.uk Thu Jun 27 11:21:20 2019 From: npwb2 at cam.ac.uk (Nick Butler) Date: Thu, 27 Jun 2019 15:21:20 +0000 Subject: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments Message-ID: Good afternoon, Our archivists are wondering if it's possible to add record identifiers to the following areas: * The record(s) in Assessments (i.e. each entry in div class="input-group linker-wrapper multiplicity-many sortable" in the edit or new Assessments screen). Currently it just has the object title, we'd like it to have the identifier concatenated too. * The entries in resource trees (i.e. each entry in div class="largetree-container ui-resizable" in the edit Resources screen). Again it currently only has the object title (or display_string, for archival objects). Might anyone know if there's any way to achieve this with a plugin? Has anyone done something like this before? Many thanks for any suggestions! Best wishes, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cory_nimer at byu.edu Thu Jun 27 12:17:52 2019 From: cory_nimer at byu.edu (Cory Nimer) Date: Thu, 27 Jun 2019 16:17:52 +0000 Subject: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments In-Reply-To: References: Message-ID: <3adeeca5a37548808f890e2c93b1a057@MB7.byu.local> Nick, It appears that the second of your requests below was previously proposed as part of ANW-780 (https://archivesspace.atlassian.net/browse/ANW-780). The comments there suggest that there is some interest in replacing the Instance Type in the resource tree with the component unique identifier (CUI), but the Development Prioritization Team felt the data being recorded in the CUI field was not consistent enough yet to merit a change in the base code. However, the ticket does include a link to a plug-in from the University of Denver that appears to replace the instance number column in the resource tree with the CUI--if that would meet your need. Best, Cory Nimer University Archivist Brigham Young University 801-422-6091 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Nick Butler Sent: Thursday, June 27, 2019 9:21 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments Good afternoon, Our archivists are wondering if it's possible to add record identifiers to the following areas: * The record(s) in Assessments (i.e. each entry in div class="input-group linker-wrapper multiplicity-many sortable" in the edit or new Assessments screen). Currently it just has the object title, we'd like it to have the identifier concatenated too. * The entries in resource trees (i.e. each entry in div class="largetree-container ui-resizable" in the edit Resources screen). Again it currently only has the object title (or display_string, for archival objects). Might anyone know if there's any way to achieve this with a plugin? Has anyone done something like this before? Many thanks for any suggestions! Best wishes, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From npwb2 at cam.ac.uk Fri Jun 28 05:35:06 2019 From: npwb2 at cam.ac.uk (Nick Butler) Date: Fri, 28 Jun 2019 09:35:06 +0000 Subject: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments In-Reply-To: <3adeeca5a37548808f890e2c93b1a057@MB7.byu.local> References: <3adeeca5a37548808f890e2c93b1a057@MB7.byu.local> Message-ID: <7571e966321e0170deba876298ac1df3e0c2e3b1.camel@cam.ac.uk> Hi Cory, Thank you very much for the link - the tree_component_id plugin looks like it should do exactly what we need for the resource trees. Best wishes, Nick -----Original Message----- From: Cory Nimer > Reply-To: Archivesspace Users Group > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments Date: Thu, 27 Jun 2019 16:17:52 +0000 Nick, It appears that the second of your requests below was previously proposed as part of ANW-780 (https://archivesspace.atlassian.net/browse/ANW-780). The comments there suggest that there is some interest in replacing the Instance Type in the resource tree with the component unique identifier (CUI), but the Development Prioritization Team felt the data being recorded in the CUI field was not consistent enough yet to merit a change in the base code. However, the ticket does include a link to a plug-in from the University of Denver that appears to replace the instance number column in the resource tree with the CUI--if that would meet your need. Best, Cory Nimer University Archivist Brigham Young University 801-422-6091 From: archivesspace_users_group-bounces at lyralists.lyrasis.org On Behalf Of Nick Butler Sent: Thursday, June 27, 2019 9:21 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments Good afternoon, Our archivists are wondering if it's possible to add record identifiers to the following areas: * The record(s) in Assessments (i.e. each entry in div class="input-group linker-wrapper multiplicity-many sortable" in the edit or new Assessments screen). Currently it just has the object title, we'd like it to have the identifier concatenated too. * The entries in resource trees (i.e. each entry in div class="largetree-container ui-resizable" in the edit Resources screen). Again it currently only has the object title (or display_string, for archival objects). Might anyone know if there's any way to achieve this with a plugin? Has anyone done something like this before? Many thanks for any suggestions! Best wishes, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- next part -------------- An HTML attachment was scrubbed... URL: From blake.carver at lyrasis.org Fri Jun 28 08:27:49 2019 From: blake.carver at lyrasis.org (Blake Carver) Date: Fri, 28 Jun 2019 12:27:49 +0000 Subject: [Archivesspace_Users_Group] Error Update from Archives 2.2 to 2.3 In-Reply-To: References: Message-ID: Hi Angela, Did you get this figured out? What was the full error from the migration script? Any chance someone ran it twice? What's the number in the schema_info table? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Angela Stangl Sent: Monday, June 24, 2019 12:19 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Error Update from Archives 2.2 to 2.3 Hello! Has anyone else encountered this problem? We are updating from 2.2 to 2.3 and are seeing a database migration error saying "DROP FUNCTION IF EXISTS" when running the set up database script in 2.3 coming from version 2.2. Thank you for any advice! Angela Stangl Digital Services Coordinator | Rodney A. Briggs Library | library.morris.umn.edu University of Minnesota, Morris | morris.umn.edu amstangl at morris.umn.edu | (320) 589-6164 -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Fri Jun 28 08:38:48 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 28 Jun 2019 12:38:48 +0000 Subject: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments In-Reply-To: <7571e966321e0170deba876298ac1df3e0c2e3b1.camel@cam.ac.uk> References: <3adeeca5a37548808f890e2c93b1a057@MB7.byu.local> <7571e966321e0170deba876298ac1df3e0c2e3b1.camel@cam.ac.uk> Message-ID: Hi Nick, Identifiers were added to the assessment record display in version 2.6.0 (see https://archivesspace.atlassian.net/browse/ANW-274 for the issue). The CUID is not part of that, though a plug-in should similarly be able to change that behavior for you locally if you wish. I?ll also just mention that if anyone develops plug-ins for these or other functions that they think might have relevance outside their own institution, please consider adding them as links on the Awesome ArchivesSpace list (https://github.com/archivesspace/awesome-archivesspace). This is a wonderful community-maintained web guide that points to a variety of resources developed across the community. It includes links to documentation, plug-ins, scripts, integration possibilities and more. 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 Nick Butler Sent: Friday, June 28, 2019 5:35 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments Hi Cory, Thank you very much for the link - the tree_component_id plugin looks like it should do exactly what we need for the resource trees. Best wishes, Nick -----Original Message----- From: Cory Nimer > Reply-To: Archivesspace Users Group > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments Date: Thu, 27 Jun 2019 16:17:52 +0000 Nick, It appears that the second of your requests below was previously proposed as part of ANW-780 (https://archivesspace.atlassian.net/browse/ANW-780). The comments there suggest that there is some interest in replacing the Instance Type in the resource tree with the component unique identifier (CUI), but the Development Prioritization Team felt the data being recorded in the CUI field was not consistent enough yet to merit a change in the base code. However, the ticket does include a link to a plug-in from the University of Denver that appears to replace the instance number column in the resource tree with the CUI--if that would meet your need. Best, Cory Nimer University Archivist Brigham Young University 801-422-6091 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Nick Butler Sent: Thursday, June 27, 2019 9:21 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments Good afternoon, Our archivists are wondering if it's possible to add record identifiers to the following areas: * The record(s) in Assessments (i.e. each entry in div class="input-group linker-wrapper multiplicity-many sortable" in the edit or new Assessments screen). Currently it just has the object title, we'd like it to have the identifier concatenated too. * The entries in resource trees (i.e. each entry in div class="largetree-container ui-resizable" in the edit Resources screen). Again it currently only has the object title (or display_string, for archival objects). Might anyone know if there's any way to achieve this with a plugin? Has anyone done something like this before? Many thanks for any suggestions! Best wishes, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- 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 amstangl at morris.umn.edu Fri Jun 28 10:36:38 2019 From: amstangl at morris.umn.edu (Angela Stangl) Date: Fri, 28 Jun 2019 09:36:38 -0500 Subject: [Archivesspace_Users_Group] Error Update from Archives 2.2 to 2.3 In-Reply-To: References: Message-ID: Hi Blake, We did! There was an underlying issue with how the new server had been set up. So, when IT migrated the database to the new server correctly, ArchivesSpace updated correctly! Thanks for checking! Angela On Fri, Jun 28, 2019, 7:27 AM Blake Carver wrote: > Hi Angela, > Did you get this figured out? What was the full error from the migration > script? Any chance someone ran it twice? What's the number in the > schema_info table? > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Angela Stangl > *Sent:* Monday, June 24, 2019 12:19 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Error Update from Archives 2.2 to > 2.3 > > Hello! > > Has anyone else encountered this problem? We are updating from 2.2 to 2.3 > and are seeing a database migration error saying "DROP FUNCTION IF EXISTS" > when running the set up database script in 2.3 coming from version 2.2. > > Thank you for any advice! > Angela Stangl > > Digital Services Coordinator | Rodney A. Briggs Library | > library.morris.umn.edu > University of Minnesota, Morris | morris.umn.edu > amstangl at morris.umn.edu | (320) 589-6164 > _______________________________________________ > 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 npwb2 at cam.ac.uk Fri Jun 28 10:41:21 2019 From: npwb2 at cam.ac.uk (Nick Butler) Date: Fri, 28 Jun 2019 14:41:21 +0000 Subject: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments In-Reply-To: References: <3adeeca5a37548808f890e2c93b1a057@MB7.byu.local> <7571e966321e0170deba876298ac1df3e0c2e3b1.camel@cam.ac.uk> Message-ID: <76ab5171751c568d99a16bd5f6432cdf820c5f01.camel@cam.ac.uk> Hi Christine, That's brilliant news! We're currently on 2.5.2, so we'll have to think about upgrading. Many thanks, Nick -----Original Message----- From: Christine Di Bella > Reply-To: Archivesspace Users Group > To: archivesspace_users_group at lyralists.lyrasis.org > Subject: Re: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments Date: Fri, 28 Jun 2019 12:38:48 +0000 Hi Nick, Identifiers were added to the assessment record display in version 2.6.0 (see https://archivesspace.atlassian.net/browse/ANW-274 for the issue). The CUID is not part of that, though a plug-in should similarly be able to change that behavior for you locally if you wish. I?ll also just mention that if anyone develops plug-ins for these or other functions that they think might have relevance outside their own institution, please consider adding them as links on the Awesome ArchivesSpace list (https://github.com/archivesspace/awesome-archivesspace). This is a wonderful community-maintained web guide that points to a variety of resources developed across the community. It includes links to documentation, plug-ins, scripts, integration possibilities and more. 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 Nick Butler Sent: Friday, June 28, 2019 5:35 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments Hi Cory, Thank you very much for the link - the tree_component_id plugin looks like it should do exactly what we need for the resource trees. Best wishes, Nick -----Original Message----- From: Cory Nimer > Reply-To: Archivesspace Users Group > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments Date: Thu, 27 Jun 2019 16:17:52 +0000 Nick, It appears that the second of your requests below was previously proposed as part of ANW-780 (https://archivesspace.atlassian.net/browse/ANW-780). The comments there suggest that there is some interest in replacing the Instance Type in the resource tree with the component unique identifier (CUI), but the Development Prioritization Team felt the data being recorded in the CUI field was not consistent enough yet to merit a change in the base code. However, the ticket does include a link to a plug-in from the University of Denver that appears to replace the instance number column in the resource tree with the CUI--if that would meet your need. Best, Cory Nimer University Archivist Brigham Young University 801-422-6091 From: archivesspace_users_group-bounces at lyralists.lyrasis.org > On Behalf Of Nick Butler Sent: Thursday, June 27, 2019 9:21 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments Good afternoon, Our archivists are wondering if it's possible to add record identifiers to the following areas: * The record(s) in Assessments (i.e. each entry in div class="input-group linker-wrapper multiplicity-many sortable" in the edit or new Assessments screen). Currently it just has the object title, we'd like it to have the identifier concatenated too. * The entries in resource trees (i.e. each entry in div class="largetree-container ui-resizable" in the edit Resources screen). Again it currently only has the object title (or display_string, for archival objects). Might anyone know if there's any way to achieve this with a plugin? Has anyone done something like this before? Many thanks for any suggestions! Best wishes, Nick -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nick Butler Software Developer Digital Services Cambridge University Library West Road Cambridge CB3 9DR, UK npwb2 at cam.ac.uk Internal tel: 33067 -------------- 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 Fri Jun 28 13:58:03 2019 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Fri, 28 Jun 2019 17:58:03 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Update - June 2019 Message-ID: [ASpaceOrgHome.jpg] June 2019 Update Development Version 2.6.0 of ArchivesSpace was released last month. We have now turned our attention to some needed infrastructure improvements for the application. We are also doing work on agents and recording language information that will make ArchivesSpace more standards-compliant in these areas. We're aiming for the next release to come out later this summer. Registration is now open for the 5th Annual Member Forum! Registration is now open for ArchivesSpace's fifth Annual Member Forum, taking place on August 2, 2019, at the Thompson Conference Center at ArchivesSpace member institution the University of Texas at Austin. Just as in previous years, this will be a free opportunity for staff from ArchivesSpace member institutions to meet and share information with each other and the program team about all things ArchivesSpace. Check out our wiki for details and registration information! New Appointments to Our Advisory Councils The ArchivesSpace Governance Board recently made appointments to our Technical Advisory Council and User Advisory Council for terms running from July 1, 2019 to June 30, 2021: Technical Advisory Council James Griffin III, Princeton University Sarit Hand, AP Corporate Archives Randy Kuehn, University of Louisville Kevin Schlottmann, Columbia University User Advisory Council Lori Dedeyan, UCLA Dan Michelson, Smith College Althea Topek, Tulane University Thanks to this year's Nominating Committee for soliciting and evaluating a diverse range of nominees for the openings. The Nominating Committee members this year were Gordon Daines, Brigham Young University, Chair, and Governance Board member; Ashley Knox, University of North Carolina Wilmington, Chair of the User Advisory Council; Max Eckard, University of Michigan, Chair of the Technical Advisory Council; Caitlin Wells, University of Michigan, representing the Very Large membership level; Jay Trask, University of Northern Colorado, representing the Large membership level; Carolyn Runyon, University of Tennessee Chattanooga, representing the Medium membership level; Suzanne Stasiulitis, Pennsylvania State Archives, representing the Small membership level; and Jonathan Lawler, Southeastern Baptist Theological Seminary, representing the Very Small membership level; as well as Christine Di Bella, ArchivesSpace Program Manager, ex officio. Thanks to Our Outgoing Advisory Council Members As one set of Advisory Council members arrives, we must say good-bye to another. We're very appreciative of our outgoing TAC and UAC members for all they've done on behalf of the ArchivesSpace community: Technical Advisory Council Max Eckard, University of Michigan (special thanks to Max for his able leadership as chair of the TAC since 2017) Terry Catapano, University of California Berkeley Bobbi Fox, independent Patrick Galligan, Rockefeller Archive Center Jason Loeffler, independent User Advisory Council Alston Cobourn, East Carolina University Sue Luftschein, University of Southern California Nikki Lynn Thomas, University of North Carolina, Charlotte The ArchivesSpace community has been very fortunate to benefit from their many talents during their time as Council members. We look forward to continuing to work with these valued community members in other capacities in the future. Take the Integrations Sub-Team Survey (based on a message sent by Patrick Galligan, leader of the Integrations sub-team) The ArchivesSpace Technical Advisory Council's Integrations sub-team is conducting a survey to gather more information about desired systems integrations with ArchivesSpace. The goals are to produce anonymized public findings about what integrations the community wants and to identify and facilitate integrations collaborations with partners. The survey should only take 10-15 minutes at most. You can find the survey here: https://forms.gle/VR6UwqqQ4SXfyKav6 Please fill out this survey if you have any interest at all in ArchivesSpace software integrations. You do not have to be a member institution or currently be using ArchivesSpace. It's important to note that the results of this survey alone will not determine what integrations work gets done and by whom. But, the Integrations sub-team has high hopes that the results will inform and drive future community work. Membership Update We are excited to welcome our newest members to our community! Our new members since May 31 include: * Drexel University (Philadelphia, Pennsylvania) * Indiana University (Bloomington, Indiana) * Maryland Historical Society (Baltimore, Maryland) * Ouachita Baptist University (Arkadelphia, Arkansas) * Santa Barbara Trust for Historic Preservation (Santa Barbara, California) * Southern Illinois University Edwardsville (Edwardsville, Illinois) * Upstate Medical University (Syracuse, New York) Renewals have been sent to all current members for 2019/2020. If your institution has not received its renewal, or if you have any questions about it, please email us. As of June 28, we have 395 General members, 19 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org for more information. ________________________________ ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA's Collection Management Tools Section listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 20006 bytes Desc: image002.jpg URL: