From jane.labarbara at mail.wvu.edu Tue Mar 1 10:54:32 2016 From: jane.labarbara at mail.wvu.edu (Jane LaBarbara) Date: Tue, 1 Mar 2016 15:54:32 +0000 Subject: [Archivesspace_Users_Group] Need help making functional hyperlinks in finding aids Message-ID: (Apologies if this has been asked before.) Currently, my institution has hyperlinks in many of our Scope and Content notes that refer people to digitized content from the collections (example: View photographs associated with this collection in West Virginia History OnView.) The hyperlinks are not tagged in proper EAD fashion, so we have to fix that before we migrate to ASpace. I tried using the extref tag and some of its attributes a few different ways in a dummy collection's S/C note in ASpace--when I look at the public view I see the text but it is NOT hyperlinked. Can anyone give me some pointers or examples of successful hyperlinks in finding aids? Thank you, Jane Jane Metters LaBarbara Assistant Curator West Virginia & Regional History Center West Virginia University Libraries Reference desk: 304-293-3536 Office phone: 304-293-0352 Email: jane.labarbara at mail.wvu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From esha at nyu.edu Tue Mar 1 13:16:39 2016 From: esha at nyu.edu (Esha Datta) Date: Tue, 1 Mar 2016 13:16:39 -0500 Subject: [Archivesspace_Users_Group] marcxml exporter plugin questions Message-ID: Hi, I am trying to write a plugin to apply some custom mappings to the marc export for Archives Space records. I am using Hudson Molonglo's plugin and the ASpace plugin documentation as a template. My question is how do I access the archives space object? So far, I have created a custom marc serializer class where I specify the class in the MarcSerializer add decorator method. I can inspect the object(record) in the MarcCustomFieldSerialize class and see the marc record...which is pretty cool. However, I also need to access the archives space object before it's transformed to marc to access some other values. I see from the plugin listed above that the MarcModel class is being re-defined in it and is getting the aspace record. It also has some decorator logic which I assume got pulled back into the main code, as I see it there now. However, I'm not sure how object is being read in the plugin. I see how that's happening in the main source code. So far, I have: plugins/name/ plugin_init.rb: MARCSerializer.add_decorator(MARCCustomFieldSerialize) and the class: plugins/name/backend/lib/ class MARCCustomFieldSerialize ControlField = Struct.new(:tag, :text) DataField = Struct.new(:tag, :ind1, :ind2, :subfields) SubField = Struct.new(:code, :text) def initialize(record) @record = record end end I'd really appreciate any feedback on this. Thanks for your time! Please let me know if you need any clarifications. Thanks. Esha Datta Senior Programmer/Analyst Bobst Library NYU -------------- next part -------------- An HTML attachment was scrubbed... URL: From psuda1 at tulane.edu Tue Mar 1 15:52:07 2016 From: psuda1 at tulane.edu (Suda, Phillip J) Date: Tue, 1 Mar 2016 20:52:07 +0000 Subject: [Archivesspace_Users_Group] Printing out Resource page includes all links Message-ID: Good afternoon, When a user prints out an ArchivesSpace resource page, all of the uri/links are included on the printout even though they do not show up in the browser. Is there a fix for this? We are running 1.4.2. Thanks, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 -------------- next part -------------- An HTML attachment was scrubbed... URL: From l.ciuffa.ext at aarome.org Wed Mar 2 06:57:40 2016 From: l.ciuffa.ext at aarome.org (Lavinia Ciuffa) Date: Wed, 2 Mar 2016 12:57:40 +0100 Subject: [Archivesspace_Users_Group] AS & VRA Message-ID: Hi, Is there anyone who is using/or wish to use ArchiveSpace coming to next VRA Conference in Seattle (9 -14 March)? If so, we have organized a meeting to share opinions especially on Archivespace on Friday at 10am in one of the Westin Hotel available rooms. Please let me know! Thank you, Lavinia Lavinia Ciuffa ActingCurator Photographic Archive American Academy in Rome Via Angelo Masina, 5 00153 Roma, Italia Ph:+39065846281 www.aarome.org *Please consider the environment before printing this e-mail* -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Mar 2 08:45:29 2016 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 2 Mar 2016 13:45:29 +0000 Subject: [Archivesspace_Users_Group] FW: Invitation: National continuing education/professional development survey In-Reply-To: References: Message-ID: Though it?s not ArchivesSpace-specific, opportunities for continuing education related to applications like ArchivesSpace and the functions associated with it are, and this survey is likely to be of interest to many on this list. -- Christine ---------- Forwarded message ---------- From: Laurie Sather > Date: Tue, Mar 1, 2016 at 3:20 PM Subject: Invitation: National continuing education/professional development survey Dear colleague: You have been identified as a library, archives, or museum professional whose voice is needed in a national project to better understand continuing education/professional development (CE/PD). The Mapping the Landscapes project is the first comprehensive effort to establish a national dataset related to CE/PD within and across the library, archives, and museum sectors. This project is a joint effort of the Coalition to Advance Learning in Archives, Libraries and Museums ("Coalition"), the Educopia Institute, and TrueBearing Consulting, funded through a federal grant from the Institute of Museum and Library Services (IMLS). You are invited to complete the Mapping the Landscapes survey between now and March 24, 2016. This survey is designed to gather important information on common and unique individual wants and needs for CE/PD across these three sectors. The information gained from this project will advance efforts to make CE/PD more relevant, accessible, and effective in supporting professional development for you and your colleagues. As a professional who relies on CE/PD resources, this is an opportunity for your voice to be heard! To take the survey right away, just click the following link (one response per device, please)?: Take the Mapping the Landscapes Survey If you want to learn more, see the Frequently Asked Questions at this link: Mapping the Landscapes FAQs The survey will be available until March 24, 2016. If you have any questions about this project, please contact Dr. Nathan Brown, Project Research Lead, at nathan at truebearingconsulting.com. Thank you for your interest and support of your profession. Best, Laurie Laurie Sather Chair, Survey Task Force Committee Mapping the Landscapes Project -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Wed Mar 2 08:57:16 2016 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Wed, 2 Mar 2016 13:57:16 +0000 Subject: [Archivesspace_Users_Group] marcxml exporter plugin questions In-Reply-To: References: Message-ID: <26852077-F484-46BF-91D4-C0AA2C4E4936@dartmouth.edu> Hi Esha- I think you'll want something like the following, where I'm adding the ead_id to a new 035 field. def datafields extra_fields = [] if @record.aspace_record.ead_id extra_fields << DataField.new('035', ' ', ' ', [SubField.new('a', @record.aspace_record.ead_id)]) end (@record.datafields + extra_fields).sort_by(&:tag) end There's a complete view of what Dartmouth is doing - at least in my local test environment against v1.4+ here: https://github.com/jdshaw/dartmouth_udf_exports/tree/1.5-compatible I've optimistically labeled it 1.5+ compatible, but I think it should work with 1.4 as well. It's a work in progress, so feel free to let me know if you spot some major nastiness! We haven't updated from 1.3 in production yet, but I've rolled most of the changes to the exporter into a 1.3 version which ca be found here: https://github.com/jdshaw/dartmouth_udf_exports Best, Joshua From: Esha Datta Reply-To: "esha at nyu.edu", Archivesspace Users Group Date: Tuesday, March 1, 2016 at 1:16 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] marcxml exporter plugin questions Hi, I am trying to write a plugin to apply some custom mappings to the marc export for Archives Space records. I am using Hudson Molonglo's plugin and the ASpace plugin documentation as a template. My question is how do I access the archives space object? So far, I have created a custom marc serializer class where I specify the class in the MarcSerializer add decorator method. I can inspect the object(record) in the MarcCustomFieldSerialize class and see the marc record...which is pretty cool. However, I also need to access the archives space object before it's transformed to marc to access some other values. I see from the plugin listed above that the MarcModel class is being re-defined in it and is getting the aspace record. It also has some decorator logic which I assume got pulled back into the main code, as I see it there now. However, I'm not sure how object is being read in the plugin. I see how that's happening in the main source code. So far, I have: plugins/name/ plugin_init.rb: MARCSerializer.add_decorator(MARCCustomFieldSerialize) and the class: plugins/name/backend/lib/ class MARCCustomFieldSerialize ControlField = Struct.new(:tag, :text) DataField = Struct.new(:tag, :ind1, :ind2, :subfields) SubField = Struct.new(:code, :text) def initialize(record) @record = record end end I'd really appreciate any feedback on this. Thanks for your time! Please let me know if you need any clarifications. Thanks. Esha Datta Senior Programmer/Analyst Bobst Library NYU -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Wed Mar 2 09:42:10 2016 From: Kevin.Clair at du.edu (Kevin Clair) Date: Wed, 2 Mar 2016 14:42:10 +0000 Subject: [Archivesspace_Users_Group] customizing tokeninput dropdowns Message-ID: <55DF158B-94D2-423F-8031-B5587FA2DF76@du.edu> Hello, Our archivists would like, when searching for subjects in the Resource form, for the Tokeninput dropdown to display the first term type for a heading in addition to its label, because we have a handful of terms that are identical except for their type and it would be helpful for disambiguation. Is it possible to do this via a plugin? I know in theory from poking around at https://loopj.com/jquery-tokeninput/demo.html how to edit Tokeninput dropdowns, but in practice it seems buried pretty deep in the application so I thought I?d ask the list to see if anyone else has played around with it. thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at mail.lib.msu.edu Thu Mar 3 11:08:48 2016 From: ltang5 at mail.lib.msu.edu (Tang, Lydia) Date: Thu, 3 Mar 2016 16:08:48 +0000 Subject: [Archivesspace_Users_Group] more RDE - template issues Message-ID: <4CBB4328-81BC-4736-B2C4-49FF0B0E0F5D@mail.lib.msu.edu> Hello again! Thank you all so much for all of your help on this listserv! I just wanted to pass along another issue I?ve encountered while using Rapid Data Entry. I?ve been experimenting with using templates, however, I?ve encountered this issue a couple of times where I add a row and it appears to add the main default of spaces. Thus, if my template suppressed any fields earlier, the data fields shift over (see screen shot), which is disorienting. If I try to enter my data and save, then it basically crashes the entire system, ?beach balling? (sorry, I don?t know the technical term) when I try to access a record to continue editing and sometimes giving me the ?Error FULL HEAD? message. My local IT folks haven?t been able to identify the issue because they say the logs are not very descriptive, but basically I?ve been locked out of the system all morning. Any suggestions? Thanks so much! Lydia -------------- next part -------------- A non-text attachment was scrubbed... Name: RDE template issue.png Type: image/png Size: 204329 bytes Desc: RDE template issue.png URL: From Chris.Fitzpatrick at lyrasis.org Thu Mar 3 12:04:35 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 3 Mar 2016 17:04:35 +0000 Subject: [Archivesspace_Users_Group] more RDE - template issues In-Reply-To: <4CBB4328-81BC-4736-B2C4-49FF0B0E0F5D@mail.lib.msu.edu> References: <4CBB4328-81BC-4736-B2C4-49FF0B0E0F5D@mail.lib.msu.edu> Message-ID: How many rows are you trying to save at a time? Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tang, Lydia Sent: Thursday, March 03, 2016 5:08 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] more RDE - template issues Hello again! Thank you all so much for all of your help on this listserv! I just wanted to pass along another issue I?ve encountered while using Rapid Data Entry. I?ve been experimenting with using templates, however, I?ve encountered this issue a couple of times where I add a row and it appears to add the main default of spaces. Thus, if my template suppressed any fields earlier, the data fields shift over (see screen shot), which is disorienting. If I try to enter my data and save, then it basically crashes the entire system, ?beach balling? (sorry, I don?t know the technical term) when I try to access a record to continue editing and sometimes giving me the ?Error FULL HEAD? message. My local IT folks haven?t been able to identify the issue because they say the logs are not very descriptive, but basically I?ve been locked out of the system all morning. Any suggestions? Thanks so much! Lydia From kate_bowers at harvard.edu Thu Mar 3 13:53:23 2016 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Thu, 3 Mar 2016 18:53:23 +0000 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Message-ID: I have been told that this issue is in Sprint 19, the current sprint, but the status is "icebox". What does "icebox" mean? https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 One of the reasons we ar particularly interested is that many EAD descriptions of photo collections make particularly heavy use of and . Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Thu Mar 3 14:18:28 2016 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Thu, 3 Mar 2016 19:18:28 +0000 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? In-Reply-To: References: Message-ID: Kate, 1. AR-1134 is in the icebox, which means it has not been prioritized for inclusion in a sprint. Brad 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, March 03, 2016 1:53 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? I have been told that this issue is in Sprint 19, the current sprint, but the status is "icebox". What does "icebox" mean? https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 One of the reasons we ar particularly interested is that many EAD descriptions of photo collections make particularly heavy use of and . Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Thu Mar 3 14:18:54 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 3 Mar 2016 19:18:54 +0000 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? In-Reply-To: References: Message-ID: Hi, "icebox" is concept from PivotalTracker that we carried over to JIRA when we migrated. It means that it's not being worked on yet. The current sprint is actually Feb 2015 ( we changed the naming convention ), which you can see here: https://archivesspace.atlassian.net/wiki/display/ADC/2016+Sprints This ticket was not included in this sprint. It looks like there was quite a bit of discussion about it in the comment, and there was a pull-request submitted, but it seems to be in an unfinished state. If you could test it out and provide your thoughts, that would probably help move it along. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Bowers, Kate A. Sent: Thursday, March 03, 2016 7:53 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? I have been told that this issue is in Sprint 19, the current sprint, but the status is "icebox". What does "icebox" mean? https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 One of the reasons we ar particularly interested is that many EAD descriptions of photo collections make particularly heavy use of and . Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From esha at nyu.edu Thu Mar 3 14:43:33 2016 From: esha at nyu.edu (Esha Datta) Date: Thu, 3 Mar 2016 14:43:33 -0500 Subject: [Archivesspace_Users_Group] marcxml exporter plugin questions In-Reply-To: <26852077-F484-46BF-91D4-C0AA2C4E4936@dartmouth.edu> References: <26852077-F484-46BF-91D4-C0AA2C4E4936@dartmouth.edu> Message-ID: Hi Joshua, Thanks so much for the response. I don't want to do anything to the ead which is why I'm avoiding using the EADSerializer.add_serialize_step(EADUserDefinedFieldSerialize) step. I see that the MarcModel code is getting the archival object. I don't really have anything to override the mapping in MarcModel code or add anything to EADSerializer...so I'm a little stuck right now and apologize if I'm missing something obvious. Thanks again. On Wed, Mar 2, 2016 at 8:57 AM, Joshua D. Shaw wrote: > Hi Esha- > > I think you'll want something like the following, where I'm adding the > ead_id to a new 035 field. > > def datafields > extra_fields = [] > > if @record.aspace_record.ead_id > extra_fields << DataField.new('035', ' ', ' ', [SubField.new('a', > @record.aspace_record.ead_id)]) > end > > (@record.datafields + extra_fields).sort_by(&:tag) > end > > There's a complete view of what Dartmouth is doing - at least in my local > test environment against v1.4+ here: > https://github.com/jdshaw/dartmouth_udf_exports/tree/1.5-compatible I've > optimistically labeled it 1.5+ compatible, but I think it should work with > 1.4 as well. It's a work in progress, so feel free to let me know if you > spot some major nastiness! > > We haven't updated from 1.3 in production yet, but I've rolled most of the > changes to the exporter into a 1.3 version which ca be found here: > https://github.com/jdshaw/dartmouth_udf_exports > > Best, > Joshua > > > From: Esha Datta > Reply-To: "esha at nyu.edu", Archivesspace Users Group > Date: Tuesday, March 1, 2016 at 1:16 PM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] marcxml exporter plugin questions > > Hi, > > I am trying to write a plugin to apply some custom mappings to the marc > export for Archives Space records. I am using Hudson Molonglo's plugin > and the ASpace plugin > documentation > as > a template. My question is how do I access the archives space object? So > far, I have created a custom marc serializer class where I specify the > class in the MarcSerializer add decorator method. I can inspect the > object(record) in the MarcCustomFieldSerialize class and see the marc > record...which is pretty cool. However, I also need to access the archives > space object before it's transformed to marc to access some other values. > > I see from the plugin listed above that the MarcModel class is being > re-defined in it and is getting the aspace record. It also has some > decorator logic which I assume got pulled back into the main code, as I see > it there now. However, I'm not sure how object is being read in the plugin. > I see how that's happening in the main source code. > > So far, I have: > plugins/name/ > plugin_init.rb: > MARCSerializer.add_decorator(MARCCustomFieldSerialize) > and the class: > plugins/name/backend/lib/ > class MARCCustomFieldSerialize > ControlField = Struct.new(:tag, :text) > DataField = Struct.new(:tag, :ind1, :ind2, :subfields) > SubField = Struct.new(:code, :text) > > def initialize(record) > @record = record > end > end > > I'd really appreciate any feedback on this. Thanks for your time! Please > let me know if you need any clarifications. > > Thanks. > > Esha Datta > Senior Programmer/Analyst > Bobst Library > NYU > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvb at sfasu.edu Fri Mar 4 15:48:19 2016 From: jvb at sfasu.edu (Johna L Von Behrens) Date: Fri, 04 Mar 2016 20:48:19 +0000 Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) Message-ID: Good afternoon AS Users, We have records in AS that we would like to export and put into OCLC and our catalog. Has anyone exported a marcxml record and then imported it into OCLC and/or their catalog? If so, do you have instructions or a workflow? I am not a cataloger so excuse me if I am not using the correct terminology ? Have a wonderful weekend! Johna Von Behrens, MLIS, CA, MSEd University Archivist and Records Manager East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.7610 The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From luftsche at usc.edu Fri Mar 4 16:36:10 2016 From: luftsche at usc.edu (Susan Luftschein) Date: Fri, 4 Mar 2016 21:36:10 +0000 Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) In-Reply-To: References: Message-ID: Hi Johna, I do it all the time. You can export a resource record as MARCXML. You do it through the Export tab in the top level of the resource record. I do use OCLC Connexion to catalog, so if that?s what you want to do you have to transform the xml file into MARC21 format. Terry Reese?s MarcEdit program (free) will allow you to do that. Then you can just import the transformed MARC record into Connexion. Be aware that there are still some mapping issues with ASpace elements and MARC fields, so you definitely have to do some manual editing. Hope this helps, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Johna L Von Behrens Sent: Friday, March 04, 2016 12:48 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) Good afternoon AS Users, We have records in AS that we would like to export and put into OCLC and our catalog. Has anyone exported a marcxml record and then imported it into OCLC and/or their catalog? If so, do you have instructions or a workflow? I am not a cataloger so excuse me if I am not using the correct terminology ? Have a wonderful weekend! Johna Von Behrens, MLIS, CA, MSEd University Archivist and Records Manager East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.7610 The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sally.vermaaten at nyu.edu Sat Mar 5 17:08:46 2016 From: sally.vermaaten at nyu.edu (Sally Vermaaten) Date: Sat, 5 Mar 2016 17:08:46 -0500 Subject: [Archivesspace_Users_Group] Code4Lib 2016 events In-Reply-To: References: Message-ID: Hi Chris, I'll be at Code4lib and Code4arc as well and I really like the idea of an informal ArchivesSpace meet up to code / test / spec / connect. Could we hold a ultra-low-key Birds of a Feather session on Thursday afternoon ... or something on Wednesday? Look forward to seeing you there, Sally On Thu, Jan 7, 2016 at 3:59 PM, Chris Fitzpatrick < Chris.Fitzpatrick at lyrasis.org> wrote: > > Hi, > > > Great. Maybe we can plan some kind of meetup to do some coding work as > well... > > > I am seeing a convergence of your request and the others for the OAI-PHM > responder. I like your idea, since it I think most of it is actually pretty > much already built in the indexer, since it polls the Aspace backend for > created/updated/deleted records and triggers some actions to be passed off > to another API ( i.e Solr's ) > > > I think it would be pretty easy to essentially do something else, like > "when a record is created, POST the JSON to this URI". Or maybe something > slightly more sophisticated, like push it messaging queue like Redis or > RabbitMQ, that a second service (like a microservice ) could listen to and > consume messages. > > > What would a use case be? Like pushing to Blacklight or Primo or Ebsco? > > > best,chris. > > > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Arnold, Hillel > *Sent:* Thursday, January 7, 2016 7:47 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Code4Lib 2016 events > > Hey Chris, > I?ll be at Code4Lib too, although I?m already committed to other sessions > for the preconference. > > One idea we?ve been batting around here is some sort of messaging system > (inspired by Github?s webhooks [1]) which would allow authorized users to > activate customizable HTTP callbacks for events, for example creation, > modification or deletion of a resource or component. It seems like people > have taken a number of approaches to figuring out when data changes in AS, > but as far as I know all of these involve some sort of regularly scheduled > cron job that looks at the Solr index or makes a ton of API calls. It would > be amazing if the system could send notifications out ? I think it would > allow for much more efficient and flexible integration with other systems. > > Hillel > > ----------- > Hillel Arnold > Assistant Director, Head of Digital Programs > Rockefeller Archive Center > 914.366.6382 > > From: on behalf > of Chris Fitzpatrick > Reply-To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Date: Thursday, January 7, 2016 at 7:29 AM > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Subject: [Archivesspace_Users_Group] Code4Lib 2016 events > > Hi, > > > There was a question shortly before the holidays about some Aspace-related > activities at Code4Lib this year in March. > > > I am planning on attending, and will be at the Code4Arc pre-conf > , which was a great session > we had last year at C4L. > > I am thinking of also signing up to lead a breakout session one of the > days, and might put together something for a lighting talk. > > > Is anyone else planning on going? Are there some possible ideas that > anyone has or would like to see if attending? We might be able to expand on > the breakout, if there's critical mass to possibly meet more somewhere. > > > > Best, Chris. > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Sally Vermaaten Project Manager, Archival Systems New York University Libraries 1-212-992-6259 -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Sun Mar 6 16:37:14 2016 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Sun, 6 Mar 2016 16:37:14 -0500 Subject: [Archivesspace_Users_Group] Code4Lib 2016 events In-Reply-To: References: Message-ID: Sally, I'd definitely be down to talk about messaging etc. there's an artefactual meetup at Wednesday afternoon, but I'm down for any other time. -Patrick Sent with Good (www.good.com) -----Original Message----- From: Sally Vermaaten [sally.vermaaten at nyu.edu] Sent: Saturday, March 05, 2016 05:09 PM Eastern Standard Time To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Code4Lib 2016 events Hi Chris, I'll be at Code4lib and Code4arc as well and I really like the idea of an informal ArchivesSpace meet up to code / test / spec / connect. Could we hold a ultra-low-key Birds of a Feather session on Thursday afternoon ... or something on Wednesday? Look forward to seeing you there, Sally On Thu, Jan 7, 2016 at 3:59 PM, Chris Fitzpatrick > wrote: Hi, Great. Maybe we can plan some kind of meetup to do some coding work as well... I am seeing a convergence of your request and the others for the OAI-PHM responder. I like your idea, since it I think most of it is actually pretty much already built in the indexer, since it polls the Aspace backend for created/updated/deleted records and triggers some actions to be passed off to another API ( i.e Solr's ) I think it would be pretty easy to essentially do something else, like "when a record is created, POST the JSON to this URI". Or maybe something slightly more sophisticated, like push it messaging queue like Redis or RabbitMQ, that a second service (like a microservice ) could listen to and consume messages. What would a use case be? Like pushing to Blacklight or Primo or Ebsco? best,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Arnold, Hillel > Sent: Thursday, January 7, 2016 7:47 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Code4Lib 2016 events Hey Chris, I?ll be at Code4Lib too, although I?m already committed to other sessions for the preconference. One idea we?ve been batting around here is some sort of messaging system (inspired by Github?s webhooks [1]) which would allow authorized users to activate customizable HTTP callbacks for events, for example creation, modification or deletion of a resource or component. It seems like people have taken a number of approaches to figuring out when data changes in AS, but as far as I know all of these involve some sort of regularly scheduled cron job that looks at the Solr index or makes a ton of API calls. It would be amazing if the system could send notifications out ? I think it would allow for much more efficient and flexible integration with other systems. Hillel ----------- Hillel Arnold Assistant Director, Head of Digital Programs Rockefeller Archive Center 914.366.6382 From: > on behalf of Chris Fitzpatrick > Reply-To: Archivesspace Users Group > Date: Thursday, January 7, 2016 at 7:29 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Code4Lib 2016 events Hi, There was a question shortly before the holidays about some Aspace-related activities at Code4Lib this year in March. I am planning on attending, and will be at the Code4Arc pre-conf , which was a great session we had last year at C4L. I am thinking of also signing up to lead a breakout session one of the days, and might put together something for a lighting talk. Is anyone else planning on going? Are there some possible ideas that anyone has or would like to see if attending? We might be able to expand on the breakout, if there's critical mass to possibly meet more somewhere. Best, Chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Sally Vermaaten Project Manager, Archival Systems New York University Libraries 1-212-992-6259 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jjones at smith.edu Mon Mar 7 08:17:04 2016 From: jjones at smith.edu (Jasmine) Date: Mon, 7 Mar 2016 08:17:04 -0500 Subject: [Archivesspace_Users_Group] Second Call | SAA CMT Roundtable ArchivesSpace Repository Profiles Message-ID: Dear ArchivesSpace users: The SAA Collection Management Tools Roundtable Steering Committee is relaunching its Repository Profile series, where we ask users about their decision-making process, implementation strategies, and lessons learned with collection management tools. Past profile contributions may be found here: http://www2.archivists.org/groups/collection-management-tools-roundtable/repository-profiles . For this round of profiles, we are asking for ArchivesSpace users to share their experiences with us. If you would like to volunteer, please get in touch with us and/or send us your responses to the repository profile questions found here: http://bit.ly/aspace-repository-profile . If you have any questions or want to send in your responses, please contact Matt Gorzalski at mGorzalski at lib.siu.edu or Jasmine Jones at jjones at smith.edu . Looking forward to your participation and hearing about your experiences with ArchivesSpace! Collection Management Tools Roundtable Steering Committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Mon Mar 7 08:27:53 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Mon, 7 Mar 2016 13:27:53 +0000 Subject: [Archivesspace_Users_Group] Code4Lib 2016 events In-Reply-To: References: , Message-ID: Hi Sally, Yes, that would be great. However, I am leaving Wed evening. Maybe there's a time before then that would work? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Galligan, Patrick Sent: Sunday, March 06, 2016 10:37 PM To: 'Archivesspace Users Group'; 'Archivesspace Users Group' Subject: Re: [Archivesspace_Users_Group] Code4Lib 2016 events Sally, I'd definitely be down to talk about messaging etc. there's an artefactual meetup at Wednesday afternoon, but I'm down for any other time. -Patrick Sent with Good (www.good.com) -----Original Message----- From: Sally Vermaaten [sally.vermaaten at nyu.edu] Sent: Saturday, March 05, 2016 05:09 PM Eastern Standard Time To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Code4Lib 2016 events Hi Chris, I'll be at Code4lib and Code4arc as well and I really like the idea of an informal ArchivesSpace meet up to code / test / spec / connect. Could we hold a ultra-low-key Birds of a Feather session on Thursday afternoon ... or something on Wednesday? Look forward to seeing you there, Sally On Thu, Jan 7, 2016 at 3:59 PM, Chris Fitzpatrick > wrote: Hi, Great. Maybe we can plan some kind of meetup to do some coding work as well... I am seeing a convergence of your request and the others for the OAI-PHM responder. I like your idea, since it I think most of it is actually pretty much already built in the indexer, since it polls the Aspace backend for created/updated/deleted records and triggers some actions to be passed off to another API ( i.e Solr's ) I think it would be pretty easy to essentially do something else, like "when a record is created, POST the JSON to this URI". Or maybe something slightly more sophisticated, like push it messaging queue like Redis or RabbitMQ, that a second service (like a microservice ) could listen to and consume messages. What would a use case be? Like pushing to Blacklight or Primo or Ebsco? best,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Arnold, Hillel > Sent: Thursday, January 7, 2016 7:47 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Code4Lib 2016 events Hey Chris, I?ll be at Code4Lib too, although I?m already committed to other sessions for the preconference. One idea we?ve been batting around here is some sort of messaging system (inspired by Github?s webhooks [1]) which would allow authorized users to activate customizable HTTP callbacks for events, for example creation, modification or deletion of a resource or component. It seems like people have taken a number of approaches to figuring out when data changes in AS, but as far as I know all of these involve some sort of regularly scheduled cron job that looks at the Solr index or makes a ton of API calls. It would be amazing if the system could send notifications out ? I think it would allow for much more efficient and flexible integration with other systems. Hillel ----------- Hillel Arnold Assistant Director, Head of Digital Programs Rockefeller Archive Center 914.366.6382 From: > on behalf of Chris Fitzpatrick > Reply-To: Archivesspace Users Group > Date: Thursday, January 7, 2016 at 7:29 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Code4Lib 2016 events Hi, There was a question shortly before the holidays about some Aspace-related activities at Code4Lib this year in March. I am planning on attending, and will be at the Code4Arc pre-conf , which was a great session we had last year at C4L. I am thinking of also signing up to lead a breakout session one of the days, and might put together something for a lighting talk. Is anyone else planning on going? Are there some possible ideas that anyone has or would like to see if attending? We might be able to expand on the breakout, if there's critical mass to possibly meet more somewhere. Best, Chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Sally Vermaaten Project Manager, Archival Systems New York University Libraries 1-212-992-6259 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvb at sfasu.edu Mon Mar 7 10:45:57 2016 From: jvb at sfasu.edu (Johna L Von Behrens) Date: Mon, 07 Mar 2016 15:45:57 +0000 Subject: [Archivesspace_Users_Group] Newly Created Locations Not Popping Up Message-ID: I created new locations this morning. When the student tried to add them in the Instance they would not pop up in the list. We went to browse through the Location box and was able to add the location. We also did a Browse for the location and it is listed. VERSION v1.3.0 Did not know if this was a new issue or something that will be addressed with an update. Johna Von Behrens, MLIS, CA, MSEd University Archivist and Records Manager East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.7610 The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From psuda1 at tulane.edu Mon Mar 7 10:47:12 2016 From: psuda1 at tulane.edu (Suda, Phillip J) Date: Mon, 7 Mar 2016 15:47:12 +0000 Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) Message-ID: Doesn't Connexion accept MarcXML and DC as well? Just curious. Thanks, Phil On Mar 4, 2016 3:36 PM, Susan Luftschein wrote: Hi Johna, I do it all the time. You can export a resource record as MARCXML. You do it through the Export tab in the top level of the resource record. I do use OCLC Connexion to catalog, so if that?s what you want to do you have to transform the xml file into MARC21 format. Terry Reese?s MarcEdit program (free) will allow you to do that. Then you can just import the transformed MARC record into Connexion. Be aware that there are still some mapping issues with ASpace elements and MARC fields, so you definitely have to do some manual editing. Hope this helps, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Johna L Von Behrens Sent: Friday, March 04, 2016 12:48 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) Good afternoon AS Users, We have records in AS that we would like to export and put into OCLC and our catalog. Has anyone exported a marcxml record and then imported it into OCLC and/or their catalog? If so, do you have instructions or a workflow? I am not a cataloger so excuse me if I am not using the correct terminology J Have a wonderful weekend! Johna Von Behrens, MLIS, CA, MSEd University Archivist and Records Manager East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.7610 The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From christy.tomecek at yale.edu Mon Mar 7 11:43:15 2016 From: christy.tomecek at yale.edu (Tomecek, Christy) Date: Mon, 7 Mar 2016 16:43:15 +0000 Subject: [Archivesspace_Users_Group] Newly Created Locations Not Popping Up In-Reply-To: References: Message-ID: I'm more speaking from experience with top container records here, but when I've had that happen, it can mean that the indexer did not index the record yet. Ours indexes at around 30 seconds to a minute at a time, so if we immediately look for the record in the typeahead, it won't find it, but if you look again after a minute, it will then pick it up. I don't know if you've retried looking for it in the typeahead, but if you didn't, it might be worthwhile? Best, Christy -- Christy Tomecek Archives Assistant Manuscripts and Archives Yale University Library 203-432-7382 christy.tomecek at yale.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Johna L Von Behrens Sent: Monday, March 07, 2016 10:46 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Newly Created Locations Not Popping Up I created new locations this morning. When the student tried to add them in the Instance they would not pop up in the list. We went to browse through the Location box and was able to add the location. We also did a Browse for the location and it is listed. VERSION v1.3.0 Did not know if this was a new issue or something that will be addressed with an update. Johna Von Behrens, MLIS, CA, MSEd University Archivist and Records Manager East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.7610 The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From randy_stern at harvard.edu Mon Mar 7 17:43:05 2016 From: randy_stern at harvard.edu (Stern, Randy) Date: Mon, 7 Mar 2016 22:43:05 +0000 Subject: [Archivesspace_Users_Group] Public Interface Enhancement Project - Roadmap Message-ID: Hi all, What is the best way to get an overview of the roadmap for development of the Public Interface project? I can see the Cherry Hill report and U/I mockups at http://cherryhill.github.io/aspace_pui/index.html and the working group meeting notes at https://archivesspace.atlassian.net/wiki/display/ADC/Public+Interface+Enhancement+Project. But I can't really get a sense of the potential development resources available for the project, a timeline, or a plan for moving forward with development. Is there one that is available for review? Similarly, information about how the development community might collaborate to move the development forward would be helpful as well. Thanks for any information you can share. Randy Stern Director of Systems Development Harvard University IT, Library Technology Services -------------- next part -------------- An HTML attachment was scrubbed... URL: From randy_stern at harvard.edu Mon Mar 7 17:53:38 2016 From: randy_stern at harvard.edu (Stern, Randy) Date: Mon, 7 Mar 2016 22:53:38 +0000 Subject: [Archivesspace_Users_Group] Public Interface Enhancement Project - Roadmap Message-ID: Adding to my own email... I was also wondering if there has been any cross fertilization between the ArchivesSpace public u/I project and the ArcLight concept? If there is to be an open source public u/I project, it would be great to have one instead of two! Randy From: Stern, Randy Sent: Monday, March 07, 2016 5:43 PM To: Archivesspace Users Group Subject: Public Interface Enhancement Project - Roadmap Hi all, What is the best way to get an overview of the roadmap for development of the Public Interface project? I can see the Cherry Hill report and U/I mockups at http://cherryhill.github.io/aspace_pui/index.html and the working group meeting notes at https://archivesspace.atlassian.net/wiki/display/ADC/Public+Interface+Enhancement+Project. But I can't really get a sense of the potential development resources available for the project, a timeline, or a plan for moving forward with development. Is there one that is available for review? Similarly, information about how the development community might collaborate to move the development forward would be helpful as well. Thanks for any information you can share. Randy Stern Director of Systems Development Harvard University IT, Library Technology Services -------------- next part -------------- An HTML attachment was scrubbed... URL: From j at minorscience.com Mon Mar 7 18:22:14 2016 From: j at minorscience.com (Jason Loeffler) Date: Mon, 7 Mar 2016 18:22:14 -0500 Subject: [Archivesspace_Users_Group] Fwd: exporting resource components as MARCXML In-Reply-To: References: Message-ID: Hi all, I've seen some work from a few quarters on tweaking MARC and EAD exports. I may be missing something but these all seem to work with exporting resource records from the top of the tree. Our immediate use case is batch exporting descendant archival objects in MARC* for inclusion in our ILS. As such, resurrecting this thread to get a pulse of whether other institutions (and vendors) might have a use for this or if there's any work already ongoing in this area. (Unfortunately, we don't have a full-time Ruby dev on staff.) Best, Jason Jason Loeffler Technology Consultant The American Academy in Rome Minor Science | Application Development & Metadata Strategy Brooklyn, New York jason at minorscience.com (347) 405-0826 minorscience (Skype) ---------- Forwarded message ---------- From: Jason Loeffler Date: Fri, Nov 6, 2015 at 3:56 PM Subject: exporting resource components as MARCXML To: Archivesspace Users Group < archivesspace_users_group at lyralists.lyrasis.org> Hi everyone. Posted this on AR/JIRA and here, too, in the event any one has ideas. Here's how we're using ArchivesSpace to catalog visual materials: Repository Collection (Resource) Photographic Material (Archival Object, Resource Component) Item (Archival Object, Resource Component) Digital Object >From the OPAC side, we'd like to represent the Photographic Material resource component as a discrete biblio holding in our OPAC. As I understand it, ArchivesSpace only exports top-level resources as MARCXML (i.e. Collection, in this case). Child resource components are available by exporting EAD container objects. This is not ideal for our use case, as any post-processing and reformatting of EAD for consumption by OPACs is impractical. For example, EAD "flattens" subjects/agents (does not preserve datafield/subfields expected by consuming OPACs). Additionally, EAD output is monolithic; parsing several thousand container tags is onerous at best. Can someone confirm whether this sort of task suitable for plugin development? I'm new to plugin architecture and could use some guidance before I do the deep dive and/or promote this idea to the ArchivesSpace developers. Moreover, is this a feature other institutions could benefit from? Thanks and best, Jason Jason Loeffler Principal Minor Science | Application Development & Metadata Strategy Brooklyn, New York -------------- next part -------------- An HTML attachment was scrubbed... URL: From luftsche at usc.edu Mon Mar 7 18:46:49 2016 From: luftsche at usc.edu (Susan Luftschein) Date: Mon, 7 Mar 2016 23:46:49 +0000 Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) In-Reply-To: References: Message-ID: HI Phil, Yes, it does, I just looked. I?ve never done that, for no good reason! Always converted to MARC21. Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Suda, Phillip J Sent: Monday, March 07, 2016 7:47 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) Doesn't Connexion accept MarcXML and DC as well? Just curious. Thanks, Phil On Mar 4, 2016 3:36 PM, Susan Luftschein > wrote: Hi Johna, I do it all the time. You can export a resource record as MARCXML. You do it through the Export tab in the top level of the resource record. I do use OCLC Connexion to catalog, so if that?s what you want to do you have to transform the xml file into MARC21 format. Terry Reese?s MarcEdit program (free) will allow you to do that. Then you can just import the transformed MARC record into Connexion. Be aware that there are still some mapping issues with ASpace elements and MARC fields, so you definitely have to do some manual editing. Hope this helps, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Johna L Von Behrens Sent: Friday, March 04, 2016 12:48 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) Good afternoon AS Users, We have records in AS that we would like to export and put into OCLC and our catalog. Has anyone exported a marcxml record and then imported it into OCLC and/or their catalog? If so, do you have instructions or a workflow? I am not a cataloger so excuse me if I am not using the correct terminology ? Have a wonderful weekend! Johna Von Behrens, MLIS, CA, MSEd University Archivist and Records Manager East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.7610 The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From CurbowJ at bvu.edu Mon Mar 7 21:55:22 2016 From: CurbowJ at bvu.edu (Joan Curbow) Date: Tue, 8 Mar 2016 02:55:22 +0000 Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) In-Reply-To: References: Message-ID: We are also curious about this. We use Sirsi/Dynix Horizon, and our systems person doesn?t think it will take a MARC-XML record. Does anyone know? We would love instructions and clarification, too. Sincerely, Joan Curbow Reference Librarian and Archivist Buena Vista University Library Buena Vista University 610 West Fourth Street Storm Lake, IA 50588 712-749-2094 Email: curbowj at bvu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Johna L Von Behrens Sent: Friday, March 04, 2016 2:48 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) Good afternoon AS Users, We have records in AS that we would like to export and put into OCLC and our catalog. Has anyone exported a marcxml record and then imported it into OCLC and/or their catalog? If so, do you have instructions or a workflow? I am not a cataloger so excuse me if I am not using the correct terminology ? Have a wonderful weekend! Johna Von Behrens, MLIS, CA, MSEd University Archivist and Records Manager East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.7610 The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.hierl at aarome.org Tue Mar 8 03:07:28 2016 From: s.hierl at aarome.org (Sebastian Hierl) Date: Tue, 8 Mar 2016 09:07:28 +0100 Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) In-Reply-To: References: Message-ID: Same here, we would like to import records from AS to our Koha ILS, including records at the object and item level. -Sebastian -- Sebastian Hierl, Ph.D. Drue Heinz Librarian, Arthur & Janet C. Ross Library American Academy in Rome Via Angelo Masina 5 00153 Rome Italy T: +39 06 5846 417 F: +39 06 5810 788 On Tue, Mar 8, 2016 at 3:55 AM, Joan Curbow wrote: > We are also curious about this. We use Sirsi/Dynix Horizon, and our > systems person doesn?t think it will take a MARC-XML record. Does anyone > know? > > > > We would love instructions and clarification, too. > > > > Sincerely, > > > > Joan Curbow > > Reference Librarian and Archivist > > Buena Vista University Library > > Buena Vista University > > 610 West Fourth Street > > Storm Lake, IA 50588 > > 712-749-2094 > > Email: curbowj at bvu.edu > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Johna > L Von Behrens > *Sent:* Friday, March 04, 2016 2:48 PM > *To:* Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > *Subject:* [Archivesspace_Users_Group] marcxml - OCLC and Symphony > (catalog database) > > > > Good afternoon AS Users, > > > > We have records in AS that we would like to export and put into OCLC and > our catalog. > > > > Has anyone exported a marcxml record and then imported it into OCLC and/or > their catalog? > > > > If so, do you have instructions or a workflow? > > > > I am not a cataloger so excuse me if I am not using the correct > terminology J > > > > Have a wonderful weekend! > > > > Johna Von Behrens, MLIS, CA, MSEd > > University Archivist and Records > Manager > > East Texas Research Center > > Stephen F. Austin State University > > PO Box 13055 SFA Station > > Nacogdoches , TX 75962 > > Phone 936.468.1536 > > Fax 936.468.7610 > > > > *The views and opinions expressed in this message are my own and do not > necessarily reflect the views and opinions of * > > *Stephen F. Austin State University, its Board of Regents, or the State of > Texas.* > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kate_bowers at harvard.edu Tue Mar 8 11:16:30 2016 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Tue, 8 Mar 2016 16:16:30 +0000 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Message-ID: What are the next steps toward getting this bug fixed? I have just uploaded a document to https://archivesspace.atlassian.net/browse/AR-1134 It includes: 1) Undesirable behavior (current behavior) 2) Desired behavior 3) Multiple screenshots from my testing Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers 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, March 03, 2016 1:53 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? I have been told that this issue is in Sprint 19, the current sprint, but the status is "icebox". What does "icebox" mean? https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 One of the reasons we ar particularly interested is that many EAD descriptions of photo collections make particularly heavy use of and . Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianjhoffman at gmail.com Tue Mar 8 11:49:21 2016 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Tue, 8 Mar 2016 11:49:21 -0500 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? In-Reply-To: References: Message-ID: Hi Kate, Nice documentation! I?m not sure where the issue is in the planning process, but I think this removes the main obstacle to its resolution. Brian > On Mar 8, 2016, at 11:16 AM, Bowers, Kate A. wrote: > > What are the next steps toward getting this bug fixed? > > I have just uploaded a document to https://archivesspace.atlassian.net/browse/AR-1134 > It includes: > 1) Undesirable behavior (current behavior) > 2) Desired behavior > 3) Multiple screenshots from my testing > > Thanks! > > Kate > > Kate Bowers > Collections Services Archivist for Metadata, Systems, and Standards > Harvard University Archives > kate_bowers at harvard.edu > 617.496.2713 > voice: (617) 384-7787 > fax: (617) 495-8011 > web: http://nrs.harvard.edu/urn-3:hul.eresource:archives > Twitter: @k8_bowers > > > 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, March 03, 2016 1:53 PM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? > > > > I have been told that this issue is in Sprint 19, the current sprint, but the status is "icebox". What does "icebox" mean? > > https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 > > One of the reasons we ar particularly interested is that many EAD descriptions of photo collections make particularly heavy use of and . > > Thanks! > > Kate > > > Kate Bowers > Collections Services Archivist for Metadata, Systems, and Standards > Harvard University Archives > Cambridge, Massachusetts, USA > voice: (617) 384-7787 > fax: (617) 495-8011 > kate_bowers at harvard.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Tue Mar 8 11:49:47 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Tue, 8 Mar 2016 16:49:47 +0000 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? In-Reply-To: References: Message-ID: Hi, We did our March sprint planning yesterday afternoon and this feature request was not included in the sprint. However, looking through this ticket, it looks like a pull request was already submitted and accepted that adds this feature. The key is that the physdesc has to have an @altrender = "part". If someone is wanting to submit a PR to remove the @altrender requirement to the feature, we would certainly look at it. b,chris. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Bowers, Kate A. Sent: Tuesday, March 08, 2016 5:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? What are the next steps toward getting this bug fixed? I have just uploaded a document to https://archivesspace.atlassian.net/browse/AR-1134 It includes: 1) Undesirable behavior (current behavior) 2) Desired behavior 3) Multiple screenshots from my testing Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers 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, March 03, 2016 1:53 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? I have been told that this issue is in Sprint 19, the current sprint, but the status is "icebox". What does "icebox" mean? https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 One of the reasons we ar particularly interested is that many EAD descriptions of photo collections make particularly heavy use of and . Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From kate_bowers at harvard.edu Tue Mar 8 13:37:21 2016 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Tue, 8 Mar 2016 18:37:21 +0000 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? In-Reply-To: References: Message-ID: I don?t understand the reasoning behind this at all. Why would a that has or only ever be a ?part?? Is there any documentation of the EAD ingest where this is recorded? Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 08, 2016 11:50 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi, We did our March sprint planning yesterday afternoon and this feature request was not included in the sprint. However, looking through this ticket, it looks like a pull request was already submitted and accepted that adds this feature. The key is that the physdesc has to have an @altrender = "part". If someone is wanting to submit a PR to remove the @altrender requirement to the feature, we would certainly look at it. b,chris. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Bowers, Kate A. > Sent: Tuesday, March 08, 2016 5:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? What are the next steps toward getting this bug fixed? I have just uploaded a document to https://archivesspace.atlassian.net/browse/AR-1134 It includes: 1) Undesirable behavior (current behavior) 2) Desired behavior 3) Multiple screenshots from my testing Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers 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, March 03, 2016 1:53 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? I have been told that this issue is in Sprint 19, the current sprint, but the status is "icebox". What does "icebox" mean? https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 One of the reasons we ar particularly interested is that many EAD descriptions of photo collections make particularly heavy use of and . Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From djpillen at umich.edu Tue Mar 8 13:54:18 2016 From: djpillen at umich.edu (Dallas Pillen) Date: Tue, 8 Mar 2016 13:54:18 -0500 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? In-Reply-To: References: Message-ID: Hi all, We here at the Bentley submitted that PR a few months ago to fix this physdesc mapping issue. As far as I can tell, there is no requirement to have an @altrender="part" attribute; rather, the PR was meant to make ArchivesSpace ingest physdescs in the same way that it exports them. There was some discussion about that on the PR here: https://github.com/archivesspace/archivesspace/pull/312 Basically, the ArchivesSpace EAD exporter exports an extent record's "portion" value as an altrender attribute of "whole" or "part," so the PR that we submitted checks for an altrender attribute and, if it finds one AND the altrender value is "part," the imported extent will have a portion of "part." Otherwise, in cases where there is no altrender attribute or the altrender attribute is some value other than "part," the extent record's portion is set to "whole." See here: https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L248-L252 I just tested importing an EAD with several physdesc variations (some with altrenders, some without; some with multiple extents, a physfacet and a dimensions element, some with only a single extent or a single physfacet, etc.) and it imported as expected (physdescs with an extent + other elements create only an extent record and no duplicate notes; physdescs with only non-extent elements create physical facet, physical dimensions, or physical description notes, and so on). The imported resource is here: http://test.archivesspace.org/resources/54 As far as I can tell, this issue has been fixed but it just has not made it into an official release (the PR was accepted last November; v. 1.4.2 came out in October). I uploaded the EAD that I just tested to the JIRA issue as physdesc_variations_test.xml. On Tue, Mar 8, 2016 at 1:37 PM, Bowers, Kate A. wrote: > I don?t understand the reasoning behind this at all. Why would a > that has or only ever be a ?part?? Is > there any documentation of the EAD ingest where this is recorded? > > > > Thanks! > > > Kate > > > > > > > > *Kate Bowers* > > Collections Services Archivist for Metadata, Systems, and Standards > > Harvard University Archives > > kate_bowers at harvard.edu > > 617.496.2713 > > voice: (617) 384-7787 > > fax: (617) 495-8011 > > web: http://nrs.harvard.edu/urn-3:hul.eresource:archives > > Twitter: @k8_bowers > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Chris > Fitzpatrick > *Sent:* Tuesday, March 08, 2016 11:50 AM > > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Any progress on AR1134 > (ingesting EAD and )? > > > > > > > > Hi, > > > > We did our March sprint planning > > yesterday afternoon and this feature request was not included in the > sprint. > > > > However, looking through this ticket, it looks like a pull request was > already submitted and accepted that adds this feature. The key is that the > physdesc has to have an @altrender = "part". > > > > If someone is wanting to submit a PR to remove the @altrender requirement > to the feature, we would certainly look at it. > > > > b,chris. > > > > ------------------------------ > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Bowers, Kate A. > *Sent:* Tuesday, March 08, 2016 5:16 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Any progress on AR1134 > (ingesting EAD and )? > > > > What are the next steps toward getting this bug fixed? > > > > I have just uploaded a document to > https://archivesspace.atlassian.net/browse/AR-1134 > > > It includes: > > 1) Undesirable behavior (current behavior) > > 2) Desired behavior > > 3) Multiple screenshots from my testing > > > > Thanks! > > > > Kate > > > > *Kate Bowers* > > Collections Services Archivist for Metadata, Systems, and Standards > > Harvard University Archives > > kate_bowers at harvard.edu > > 617.496.2713 > > voice: (617) 384-7787 > > fax: (617) 495-8011 > > web: http://nrs.harvard.edu/urn-3:hul.eresource:archives > > Twitter: @k8_bowers > > > > > > *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, March 03, 2016 1:53 PM > *To:* Archivesspace Users Group > *Subject:* [Archivesspace_Users_Group] Any progress on AR1134 (ingesting > EAD and )? > > > > > > I have been told that this issue is in Sprint 19, the current sprint, but > the status is "icebox". What does "icebox" mean? > > > https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 > > > One of the reasons we ar particularly interested is that many EAD > descriptions of photo collections make particularly heavy use of > and . > > Thanks! > > Kate > > > Kate Bowers > Collections Services Archivist for Metadata, Systems, and Standards > Harvard University Archives > Cambridge, Massachusetts, USA > voice: (617) 384-7787 > fax: (617) 495-8011 > kate_bowers at harvard.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- *Dallas Pillen*Assistant Archivist for Metadata and Digital Projects Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Tue Mar 8 14:03:10 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Tue, 8 Mar 2016 19:03:10 +0000 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? In-Reply-To: References: , Message-ID: Hi, Ok, sorry about the altrender red herring. I just saw that was added to the test data and assume that was the hold up, but didn't look close enough. My bad... So...now I'm confused, since this seems to be reported as fixed, then not fixed, then fixed, etc. Kate are you testing against http://test.archivesspace.org ? The test site has the latest nightly build, so if it's fixed, it'll show it here. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dallas Pillen Sent: Tuesday, March 08, 2016 7:54 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi all, We here at the Bentley submitted that PR a few months ago to fix this physdesc mapping issue. As far as I can tell, there is no requirement to have an @altrender="part" attribute; rather, the PR was meant to make ArchivesSpace ingest physdescs in the same way that it exports them. There was some discussion about that on the PR here: https://github.com/archivesspace/archivesspace/pull/312 [https://avatars1.githubusercontent.com/u/7026330?v=3&s=400] AR-1134 and AR-1270: account for all physdesc subtags in EAD import by walkerdb ? Pull Request #312 ? archivesspace/archivesspace github.com JIRA references: AR-1134, AR-1270 We (at the Bentley Historical Library) wrote up a local fix for these issues, and thought we'd pass it upstream. Happy to refactor / edit if anything seems off! ... Basically, the ArchivesSpace EAD exporter exports an extent record's "portion" value as an altrender attribute of "whole" or "part," so the PR that we submitted checks for an altrender attribute and, if it finds one AND the altrender value is "part," the imported extent will have a portion of "part." Otherwise, in cases where there is no altrender attribute or the altrender attribute is some value other than "part," the extent record's portion is set to "whole." See here: https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L248-L252 I just tested importing an EAD with several physdesc variations (some with altrenders, some without; some with multiple extents, a physfacet and a dimensions element, some with only a single extent or a single physfacet, etc.) and it imported as expected (physdescs with an extent + other elements create only an extent record and no duplicate notes; physdescs with only non-extent elements create physical facet, physical dimensions, or physical description notes, and so on). The imported resource is here: http://test.archivesspace.org/resources/54 As far as I can tell, this issue has been fixed but it just has not made it into an official release (the PR was accepted last November; v. 1.4.2 came out in October). I uploaded the EAD that I just tested to the JIRA issue as physdesc_variations_test.xml. On Tue, Mar 8, 2016 at 1:37 PM, Bowers, Kate A. > wrote: I don?t understand the reasoning behind this at all. Why would a that has or only ever be a ?part?? Is there any documentation of the EAD ingest where this is recorded? Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 08, 2016 11:50 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi, We did our March sprint planning yesterday afternoon and this feature request was not included in the sprint. However, looking through this ticket, it looks like a pull request was already submitted and accepted that adds this feature. The key is that the physdesc has to have an @altrender = "part". If someone is wanting to submit a PR to remove the @altrender requirement to the feature, we would certainly look at it. b,chris. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Bowers, Kate A. > Sent: Tuesday, March 08, 2016 5:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? What are the next steps toward getting this bug fixed? I have just uploaded a document to https://archivesspace.atlassian.net/browse/AR-1134 It includes: 1) Undesirable behavior (current behavior) 2) Desired behavior 3) Multiple screenshots from my testing Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers 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, March 03, 2016 1:53 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? I have been told that this issue is in Sprint 19, the current sprint, but the status is "icebox". What does "icebox" mean? https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 One of the reasons we ar particularly interested is that many EAD descriptions of photo collections make particularly heavy use of and . Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Dallas Pillen Assistant Archivist for Metadata and Digital Projects [https://webapps.lsa.umich.edu/dean/lsa_emails/bentley-sig-em.png] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvb at sfasu.edu Tue Mar 8 14:49:32 2016 From: jvb at sfasu.edu (Johna L Von Behrens) Date: Tue, 08 Mar 2016 19:49:32 +0000 Subject: [Archivesspace_Users_Group] Batch Export of MarcXML Message-ID: Is there a way to export all the records at once? Johna Von Behrens, MLIS, CA, MSEd University Archivist and Records Manager East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.7610 The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at eservices.virginia.edu Tue Mar 8 15:07:42 2016 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 8 Mar 2016 20:07:42 +0000 Subject: [Archivesspace_Users_Group] Batch Export of MarcXML In-Reply-To: References: Message-ID: You could probably copy and modify the ead_export scripts and code, changing the backend API from: url = URI("#{AppConfig[:backend_url]}/repositories/#{repo_id}/resource_descriptions/#{id}.xml?#{params}") to: url = URI("#{AppConfig[:backend_url]}/repositories/#{repo_id}/resources/marc21/#{id}.xml?#{params}") https://github.com/archivesspace/archivesspace/blob/master/launcher/ead_export/lib/ead_export.rb#L19 ? Steve Majewski On Mar 8, 2016, at 2:49 PM, Johna L Von Behrens > wrote: Is there a way to export all the records at once? Johna Von Behrens, MLIS, CA, MSEd University Archivist and Records Manager East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.7610 The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at eservices.virginia.edu Tue Mar 8 15:09:18 2016 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Tue, 8 Mar 2016 20:09:18 +0000 Subject: [Archivesspace_Users_Group] Batch Export of MarcXML In-Reply-To: References: Message-ID: ? and I forgot: leave off the "#{params}? at the end. On Mar 8, 2016, at 3:07 PM, Majewski, Steven (sdm7g) > wrote: You could probably copy and modify the ead_export scripts and code, changing the backend API from: url = URI("#{AppConfig[:backend_url]}/repositories/#{repo_id}/resource_descriptions/#{id}.xml?#{params}") to: url = URI("#{AppConfig[:backend_url]}/repositories/#{repo_id}/resources/marc21/#{id}.xml?#{params}") https://github.com/archivesspace/archivesspace/blob/master/launcher/ead_export/lib/ead_export.rb#L19 ? Steve Majewski On Mar 8, 2016, at 2:49 PM, Johna L Von Behrens > wrote: Is there a way to export all the records at once? Johna Von Behrens, MLIS, CA, MSEd University Archivist and Records Manager East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.7610 The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. _______________________________________________ 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 psuda1 at tulane.edu Wed Mar 9 10:32:27 2016 From: psuda1 at tulane.edu (Suda, Phillip J) Date: Wed, 9 Mar 2016 15:32:27 +0000 Subject: [Archivesspace_Users_Group] Accessions & Agents Message-ID: Greetings all, We have multiple repositories/libraries in one ArchivesSpace instance. Users of one repository do not have access to resources from another repository. Problem: A repository does not want agents associated with accessions visible to other repositories. I can make it so that accessions are not visible to anyone outside of a repository based on user access rules. Is it possible to make agents associated with accessions from a specific repository only visible to the users assigned to that repository? This is an issue of privacy for agents (donors) associated with accession records. As far as I can tell, these agents to everyone. Thanks for any help. Thank you, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Wed Mar 9 10:58:35 2016 From: mark.custer at yale.edu (Custer, Mark) Date: Wed, 9 Mar 2016 15:58:35 +0000 Subject: [Archivesspace_Users_Group] Public Interface Enhancement Project - Roadmap In-Reply-To: References: Message-ID: Hi, Randy. A release date has not yet been set for the new PUI, although I'm hopeful that it will be the first major release after the "top container" release. Right now, we're in the second stage of development for the new PUI, but the next phase has not been mapped out yet, and until that's done I can't say that I'll have a good sense of a release date. But here's a quick overview of the project so far, with a few highlights in bullet points: Phase 1 of development, 2015 May - 2015 December: * Working group formed * Cherry Hill hired with remaining money from the Mellon grant * Working group created a group of user personas, which has helped to inform every subsequent step of the project * Usability tests conducted at Harvard, Rice, and Yale on current PUI to serve as a baseline for future tests * A "test corpus" of finding aids was created so that the new PUI code (to be developed in phase two) could be tested with real-world archival description. * Cherry Hill submitted its report and the working group disbanded Phase 2 of development, 2016 January - 2016 June * Brian Hoffman continues development work (which actually started near the end of phase 1) * The new PUI code has been merged into the master branch of ArchivesSpace, here: https://github.com/archivesspace/archivesspace/tree/master/public-new o The new PUI is not currently packaged with any of the development releases of ArchivesSpace just yet, but Brian Hoffman has provided instructions on how to download the source code and run the new PUI as a development server (if you start with an empty database, you'll also want to open two additional terminal windows, and "./build/run frontend:devserver", to get the staff side running, and "./build/run indexer"). * The "test corpus" site has been set up by LYRASIS to use the development version of the new PUI in place of the current one, but right now that site is password protected. Once the development moves further along, and a no crawling directive is adding to a robots.txt file, I hope that the public-side of that site can be opened for everyone to see. Either way, the new PUI will eventually make its way to a true sandbox, just like we have now at http://public.archivesspace.org for the current PUI. * Four members of the former working group have volunteered to do acceptance testing on the PUI JIRA tickets through at least June 30 (thanks Maura Carbone, Cory Nimer, Susan Pyzynski, and Scott Schwartz!) * The testing group has finished accepting/rejecting its first round of JIRA tickets for February. March through June tickets still await, and the tickets that Brian is working on for the rest of this month were identified on Monday (https://archivesspace.atlassian.net/issues/?jql=labels%20%3D%20public_interface%20AND%20Sprint%20%3D%203) For the rest of phase 2, the testing group will be testing new developments as they're delivered. Additionally, I'm hopeful that we'll be able to schedule another round of usability tests once the new PUI is fully usable/navigable (i.e. before the UI and underlying metadata is polished, but after a user can search, browse, and view all aspects of the site). I'm also hopeful that phase 3 will be the start of the release/publicity stage, but it's possible that more development work will still be required by that point to meet all of the features that have been identified as requirements for a minimum viable product for the new PUI. We should have a much better sense of a timeline for phase 3 in the next couple of months. As for resources: at this point, there is only one developer working on the project (you'll see Brian's name assigned to all of those tickets for the March sprint) and five archivists, including myself, who are actively testing and providing feedback about the development. I should also mention that at Yale we've set aside money to assist in the development of the PUI, so we're planning to contract with a development firm from April - June 30 to work under Brian's lead, contributing directly to the ArchivesSpace core code, to help realize all of the recommendations from Cherry Hill's report as well as to respond to additional feedback during development. And as Brian notes in the "public new" readme, he's happy for others to contribute (https://github.com/archivesspace/archivesspace/tree/master/public-new#contributing). If you have other ideas for how the community can contribute, please let us know! As soon as we know more about a release schedule, we'll follow up with more information. Also, your email reminds me that I need to get to work on updating the wiki site with information about phase 2, so thanks for that nudge. All my best, Mark P.S. I've been trying to follow ArcLight as much as I can, and I submitted feedback to that project early on. As far as I'm aware, that project has been put on hold for the time being, but I wouldn't be surprised if it picked back up again soon. I'll reach out again today, though, to see where they're at in the project. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stern, Randy Sent: Monday, 07 March, 2016 5:54 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Public Interface Enhancement Project - Roadmap Adding to my own email... I was also wondering if there has been any cross fertilization between the ArchivesSpace public u/I project and the ArcLight concept? If there is to be an open source public u/I project, it would be great to have one instead of two! Randy From: Stern, Randy Sent: Monday, March 07, 2016 5:43 PM To: Archivesspace Users Group Subject: Public Interface Enhancement Project - Roadmap Hi all, What is the best way to get an overview of the roadmap for development of the Public Interface project? I can see the Cherry Hill report and U/I mockups at http://cherryhill.github.io/aspace_pui/index.html and the working group meeting notes at https://archivesspace.atlassian.net/wiki/display/ADC/Public+Interface+Enhancement+Project. But I can't really get a sense of the potential development resources available for the project, a timeline, or a plan for moving forward with development. Is there one that is available for review? Similarly, information about how the development community might collaborate to move the development forward would be helpful as well. Thanks for any information you can share. Randy Stern Director of Systems Development Harvard University IT, Library Technology Services -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianjhoffman at gmail.com Wed Mar 9 11:09:43 2016 From: brianjhoffman at gmail.com (brian) Date: Wed, 09 Mar 2016 11:09:43 -0500 Subject: [Archivesspace_Users_Group] Accessions & Agents Message-ID: Hi Phil, Short answer: I think this would require a bit of customization, possibly via a plugin. Brian
-------- Original message --------
From: "Suda, Phillip J"
Date:03/09/2016 10:32 AM (GMT-05:00)
To: Archivesspace Users Group
Cc:
Subject: [Archivesspace_Users_Group] Accessions & Agents
Greetings all, We have multiple repositories/libraries in one ArchivesSpace instance. Users of one repository do not have access to resources from another repository. Problem: A repository does not want agents associated with accessions visible to other repositories. I can make it so that accessions are not visible to anyone outside of a repository based on user access rules. Is it possible to make agents associated with accessions from a specific repository only visible to the users assigned to that repository? This is an issue of privacy for agents (donors) associated with accession records. As far as I can tell, these agents to everyone. Thanks for any help. Thank you, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 -------------- next part -------------- An HTML attachment was scrubbed... URL: From randy_stern at harvard.edu Wed Mar 9 11:44:30 2016 From: randy_stern at harvard.edu (Stern, Randy) Date: Wed, 9 Mar 2016 16:44:30 +0000 Subject: [Archivesspace_Users_Group] Public Interface Enhancement Project - Roadmap In-Reply-To: References: Message-ID: Hi Mark, Thank you for the detailed overview - this helps a lot. Harvard is also actively looking into how we could contribute to accelerating the PUI work, and your explanation will be a great aide in our thinking. My understanding on ArcLight is the same as yours. I will be at the LDCX meeting at Stanford in March and plan to get an update on ArcLight while I am there. Randy From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark Sent: Wednesday, March 09, 2016 10:59 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Public Interface Enhancement Project - Roadmap Hi, Randy. A release date has not yet been set for the new PUI, although I'm hopeful that it will be the first major release after the "top container" release. Right now, we're in the second stage of development for the new PUI, but the next phase has not been mapped out yet, and until that's done I can't say that I'll have a good sense of a release date. But here's a quick overview of the project so far, with a few highlights in bullet points: Phase 1 of development, 2015 May - 2015 December: * Working group formed * Cherry Hill hired with remaining money from the Mellon grant * Working group created a group of user personas, which has helped to inform every subsequent step of the project * Usability tests conducted at Harvard, Rice, and Yale on current PUI to serve as a baseline for future tests * A "test corpus" of finding aids was created so that the new PUI code (to be developed in phase two) could be tested with real-world archival description. * Cherry Hill submitted its report and the working group disbanded Phase 2 of development, 2016 January - 2016 June * Brian Hoffman continues development work (which actually started near the end of phase 1) * The new PUI code has been merged into the master branch of ArchivesSpace, here: https://github.com/archivesspace/archivesspace/tree/master/public-new o The new PUI is not currently packaged with any of the development releases of ArchivesSpace just yet, but Brian Hoffman has provided instructions on how to download the source code and run the new PUI as a development server (if you start with an empty database, you'll also want to open two additional terminal windows, and "./build/run frontend:devserver", to get the staff side running, and "./build/run indexer"). * The "test corpus" site has been set up by LYRASIS to use the development version of the new PUI in place of the current one, but right now that site is password protected. Once the development moves further along, and a no crawling directive is adding to a robots.txt file, I hope that the public-side of that site can be opened for everyone to see. Either way, the new PUI will eventually make its way to a true sandbox, just like we have now at http://public.archivesspace.org for the current PUI. * Four members of the former working group have volunteered to do acceptance testing on the PUI JIRA tickets through at least June 30 (thanks Maura Carbone, Cory Nimer, Susan Pyzynski, and Scott Schwartz!) * The testing group has finished accepting/rejecting its first round of JIRA tickets for February. March through June tickets still await, and the tickets that Brian is working on for the rest of this month were identified on Monday (https://archivesspace.atlassian.net/issues/?jql=labels%20%3D%20public_interface%20AND%20Sprint%20%3D%203) For the rest of phase 2, the testing group will be testing new developments as they're delivered. Additionally, I'm hopeful that we'll be able to schedule another round of usability tests once the new PUI is fully usable/navigable (i.e. before the UI and underlying metadata is polished, but after a user can search, browse, and view all aspects of the site). I'm also hopeful that phase 3 will be the start of the release/publicity stage, but it's possible that more development work will still be required by that point to meet all of the features that have been identified as requirements for a minimum viable product for the new PUI. We should have a much better sense of a timeline for phase 3 in the next couple of months. As for resources: at this point, there is only one developer working on the project (you'll see Brian's name assigned to all of those tickets for the March sprint) and five archivists, including myself, who are actively testing and providing feedback about the development. I should also mention that at Yale we've set aside money to assist in the development of the PUI, so we're planning to contract with a development firm from April - June 30 to work under Brian's lead, contributing directly to the ArchivesSpace core code, to help realize all of the recommendations from Cherry Hill's report as well as to respond to additional feedback during development. And as Brian notes in the "public new" readme, he's happy for others to contribute (https://github.com/archivesspace/archivesspace/tree/master/public-new#contributing). If you have other ideas for how the community can contribute, please let us know! As soon as we know more about a release schedule, we'll follow up with more information. Also, your email reminds me that I need to get to work on updating the wiki site with information about phase 2, so thanks for that nudge. All my best, Mark P.S. I've been trying to follow ArcLight as much as I can, and I submitted feedback to that project early on. As far as I'm aware, that project has been put on hold for the time being, but I wouldn't be surprised if it picked back up again soon. I'll reach out again today, though, to see where they're at in the project. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stern, Randy Sent: Monday, 07 March, 2016 5:54 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Public Interface Enhancement Project - Roadmap Adding to my own email... I was also wondering if there has been any cross fertilization between the ArchivesSpace public u/I project and the ArcLight concept? If there is to be an open source public u/I project, it would be great to have one instead of two! Randy From: Stern, Randy Sent: Monday, March 07, 2016 5:43 PM To: Archivesspace Users Group Subject: Public Interface Enhancement Project - Roadmap Hi all, What is the best way to get an overview of the roadmap for development of the Public Interface project? I can see the Cherry Hill report and U/I mockups at http://cherryhill.github.io/aspace_pui/index.html and the working group meeting notes at https://archivesspace.atlassian.net/wiki/display/ADC/Public+Interface+Enhancement+Project. But I can't really get a sense of the potential development resources available for the project, a timeline, or a plan for moving forward with development. Is there one that is available for review? Similarly, information about how the development community might collaborate to move the development forward would be helpful as well. Thanks for any information you can share. Randy Stern Director of Systems Development Harvard University IT, Library Technology Services -------------- next part -------------- An HTML attachment was scrubbed... URL: From cbarber at amherst.edu Wed Mar 9 15:26:13 2016 From: cbarber at amherst.edu (Christina Barber) Date: Wed, 9 Mar 2016 20:26:13 +0000 Subject: [Archivesspace_Users_Group] Unpublish elements in Print to PDF Message-ID: Hi all, I have noticed that when we Print Resource to PDF that all elements of resource finding aids are being printed, including notes that have are unpublished. Do any of you know how to Print to PDF but not include unpublished notes? Also, is there any way to not include note titles for folder-level or item-level notes in exported EAD or PDFs? Thanks for any help! Chris Christina E. Barber Deputy Archivist Amherst College cbarber at amherst.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkottman at ku.edu Wed Mar 9 18:03:00 2016 From: mkottman at ku.edu (Kottman, Miloche) Date: Wed, 9 Mar 2016 23:03:00 +0000 Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) In-Reply-To: References: Message-ID: <1dbc69c44a8b4a5cad582e69a3f9ddd9@ex13-ell-cr-15.home.ku.edu> I?ve attached the instructions we use to export MARCXML from ArchivesSpace (tweaked al little to remove local edits) and then import into OCLC Connexion. For those who want to import MARCXML into their ILS without creating a ?real? record in OCLC, you can import into OCLC, edit the record and then export from OCLC as MARC-8 or MARC-UTF8. You?ll need to adjust your options to allow exporting of workforms to do this: 1. Click on Tools => Options 2. Click on the Export tab 3. In the bottom section, click to add a check mark in front of ?Allow export of workforms? 4. Click OK to save and close the window. --Miloche Miloche Kottman Head of Cataloging and Archival Processing University of Kansas Libraries Lawrence, KS 66045 mkottman at ku.edu 785-864-3916 or 785-864-4823 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Sebastian Hierl Sent: Tuesday, March 08, 2016 2:07 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) Same here, we would like to import records from AS to our Koha ILS, including records at the object and item level. -Sebastian -- Sebastian Hierl, Ph.D. Drue Heinz Librarian, Arthur & Janet C. Ross Library American Academy in Rome Via Angelo Masina 5 00153 Rome Italy T: +39 06 5846 417 F: +39 06 5810 788 On Tue, Mar 8, 2016 at 3:55 AM, Joan Curbow > wrote: We are also curious about this. We use Sirsi/Dynix Horizon, and our systems person doesn?t think it will take a MARC-XML record. Does anyone know? We would love instructions and clarification, too. Sincerely, Joan Curbow Reference Librarian and Archivist Buena Vista University Library Buena Vista University 610 West Fourth Street Storm Lake, IA 50588 712-749-2094 Email: curbowj at bvu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Johna L Von Behrens Sent: Friday, March 04, 2016 2:48 PM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] marcxml - OCLC and Symphony (catalog database) Good afternoon AS Users, We have records in AS that we would like to export and put into OCLC and our catalog. Has anyone exported a marcxml record and then imported it into OCLC and/or their catalog? If so, do you have instructions or a workflow? I am not a cataloger so excuse me if I am not using the correct terminology ? Have a wonderful weekend! Johna Von Behrens, MLIS, CA, MSEd University Archivist and Records Manager East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.7610 The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. _______________________________________________ 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: MARC record creation with ArchivesSpace.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 266776 bytes Desc: MARC record creation with ArchivesSpace.docx URL: From alexanderduryee at nypl.org Fri Mar 11 14:08:25 2016 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Fri, 11 Mar 2016 14:08:25 -0500 Subject: [Archivesspace_Users_Group] ArchivesSpace codebase repository setup Message-ID: We're undertaking local feature development for ArchivesSpace (ranging from EAD/MARC export tweaking to database migrations and corresponding UI updates); as such, we're setting up code repositories for our local codebase. Given that the ASpace application doesn't map cleanly to the source repo, it's not immediately clear what the best setup for a code repository will be. How has the list set up their local code repositories? Right now, there seem to be a few options for us: - fork the main ASpace repository, work there, and deploy a full copy of the repo into /plugins/local/ (losing migration/config source control) - set up a repo that contains the ASpace application, work in plugins/ (and migrations/ and config/ when needed), and deploy the entire application at once - set up a repo of just /plugins/, work there, and deploy that (losing config/migration source control) We're leaning towards the second option (if only to keep configs/migrations under source control), but none of these implementations feels satisfactory. Are there other methods of maintaining source control for ArchivesSpace code/config that the list is using? Thanks, --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Fri Mar 11 15:29:33 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Fri, 11 Mar 2016 20:29:33 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace codebase repository setup In-Reply-To: References: Message-ID: Hi, One thing you can do is to just set and upstream repo in git. I.e. : 0 ) Fork the main archivesspace/archivesspace repo and clone it 1 ) Add an upstream remote to your clone ( git remote add upstream https://github.com/archivesspace/archivesspace.git ) 2 ) now you can pull down any upstream changes ( git pull upstream master, or make a branch first, pull the upstream into that branch, then merge the brance into your master ) Does that make sense? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Alexander Duryee Sent: Friday, March 11, 2016 8:08 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] ArchivesSpace codebase repository setup We're undertaking local feature development for ArchivesSpace (ranging from EAD/MARC export tweaking to database migrations and corresponding UI updates); as such, we're setting up code repositories for our local codebase. Given that the ASpace application doesn't map cleanly to the source repo, it's not immediately clear what the best setup for a code repository will be. How has the list set up their local code repositories? Right now, there seem to be a few options for us: - fork the main ASpace repository, work there, and deploy a full copy of the repo into /plugins/local/ (losing migration/config source control) - set up a repo that contains the ASpace application, work in plugins/ (and migrations/ and config/ when needed), and deploy the entire application at once - set up a repo of just /plugins/, work there, and deploy that (losing config/migration source control) We're leaning towards the second option (if only to keep configs/migrations under source control), but none of these implementations feels satisfactory. Are there other methods of maintaining source control for ArchivesSpace code/config that the list is using? Thanks, --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexanderduryee at nypl.org Fri Mar 11 16:40:50 2016 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Fri, 11 Mar 2016 16:40:50 -0500 Subject: [Archivesspace_Users_Group] ArchivesSpace codebase repository setup In-Reply-To: References: Message-ID: Chris, Thanks! We'll definitely try that out to keep our code up-to-date. What we aren't clear on is the best method of turning our fork of https://github.com/archivesspace/archivesspace into something deployable. Should we fork the repository, commit to the fork, run the build system, and deploy the build? Or would it be wiser to fork the repository, commit to the fork, then copy any new code to a plugins repository (which then gets deployed)? Regarding plugins - is there any real limitation as to how far plugins can go before we would need to start rolling our own builds? Thanks, --Alex On Fri, Mar 11, 2016 at 3:29 PM, Chris Fitzpatrick < Chris.Fitzpatrick at lyrasis.org> wrote: > > Hi, > > > One thing you can do is to just set and upstream repo in git. I.e. : > > > 0 ) Fork the main archivesspace/archivesspace repo and clone it > > 1 ) Add an upstream remote to your clone ( git remote add upstream > https://github.com/archivesspace/archivesspace.git ) > > 2 ) now you can pull down any upstream changes ( git pull upstream master, > or make a branch first, pull the upstream into that branch, then merge the > brance into your master ) > > > Does that make sense? > > b,chris. > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Alexander Duryee > *Sent:* Friday, March 11, 2016 8:08 PM > *To:* Archivesspace Users Group > *Subject:* [Archivesspace_Users_Group] ArchivesSpace codebase repository > setup > > We're undertaking local feature development for ArchivesSpace (ranging > from EAD/MARC export tweaking to database migrations and corresponding UI > updates); as such, we're setting up code repositories for our local > codebase. Given that the ASpace application doesn't map cleanly to the > source repo, it's not immediately clear what the best setup for a code > repository will be. > > How has the list set up their local code repositories? Right now, there > seem to be a few options for us: > > - fork the main ASpace repository, work there, and deploy a full copy of > the repo into /plugins/local/ (losing migration/config source control) > - set up a repo that contains the ASpace application, work in plugins/ > (and migrations/ and config/ when needed), and deploy the entire > application at once > - set up a repo of just /plugins/, work there, and deploy that (losing > config/migration source control) > > We're leaning towards the second option (if only to keep > configs/migrations under source control), but none of these implementations > feels satisfactory. Are there other methods of maintaining source control > for ArchivesSpace code/config that the list is using? > > Thanks, > --Alex > > -- > Alexander Duryee > Metadata Archivist > New York Public Library > (917)-229-9590 > alexanderduryee at nypl.org > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From kate_bowers at harvard.edu Sun Mar 13 11:12:30 2016 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Sun, 13 Mar 2016 15:12:30 +0000 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? In-Reply-To: References: , , Message-ID: Chris: Yes, thanks! It is working there (see http://test.archivesspace.org/resources/57#tree::resource_57) Bravo! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Chris Fitzpatrick Sent: Tuesday, March 8, 2016 2:03 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi, Ok, sorry about the altrender red herring. I just saw that was added to the test data and assume that was the hold up, but didn't look close enough. My bad... So...now I'm confused, since this seems to be reported as fixed, then not fixed, then fixed, etc. Kate are you testing against http://test.archivesspace.org ? The test site has the latest nightly build, so if it's fixed, it'll show it here. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dallas Pillen Sent: Tuesday, March 08, 2016 7:54 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi all, We here at the Bentley submitted that PR a few months ago to fix this physdesc mapping issue. As far as I can tell, there is no requirement to have an @altrender="part" attribute; rather, the PR was meant to make ArchivesSpace ingest physdescs in the same way that it exports them. There was some discussion about that on the PR here: https://github.com/archivesspace/archivesspace/pull/312 [https://avatars1.githubusercontent.com/u/7026330?v=3&s=400] AR-1134 and AR-1270: account for all physdesc subtags in EAD import by walkerdb ? Pull Request #312 ? archivesspace/archivesspace github.com JIRA references: AR-1134, AR-1270 We (at the Bentley Historical Library) wrote up a local fix for these issues, and thought we'd pass it upstream. Happy to refactor / edit if anything seems off! ... Basically, the ArchivesSpace EAD exporter exports an extent record's "portion" value as an altrender attribute of "whole" or "part," so the PR that we submitted checks for an altrender attribute and, if it finds one AND the altrender value is "part," the imported extent will have a portion of "part." Otherwise, in cases where there is no altrender attribute or the altrender attribute is some value other than "part," the extent record's portion is set to "whole." See here: https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L248-L252 I just tested importing an EAD with several physdesc variations (some with altrenders, some without; some with multiple extents, a physfacet and a dimensions element, some with only a single extent or a single physfacet, etc.) and it imported as expected (physdescs with an extent + other elements create only an extent record and no duplicate notes; physdescs with only non-extent elements create physical facet, physical dimensions, or physical description notes, and so on). The imported resource is here: http://test.archivesspace.org/resources/54 As far as I can tell, this issue has been fixed but it just has not made it into an official release (the PR was accepted last November; v. 1.4.2 came out in October). I uploaded the EAD that I just tested to the JIRA issue as physdesc_variations_test.xml. On Tue, Mar 8, 2016 at 1:37 PM, Bowers, Kate A. > wrote: I don?t understand the reasoning behind this at all. Why would a that has or only ever be a ?part?? Is there any documentation of the EAD ingest where this is recorded? Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 08, 2016 11:50 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi, We did our March sprint planning yesterday afternoon and this feature request was not included in the sprint. However, looking through this ticket, it looks like a pull request was already submitted and accepted that adds this feature. The key is that the physdesc has to have an @altrender = "part". If someone is wanting to submit a PR to remove the @altrender requirement to the feature, we would certainly look at it. b,chris. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Bowers, Kate A. > Sent: Tuesday, March 08, 2016 5:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? What are the next steps toward getting this bug fixed? I have just uploaded a document to https://archivesspace.atlassian.net/browse/AR-1134 It includes: 1) Undesirable behavior (current behavior) 2) Desired behavior 3) Multiple screenshots from my testing Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers 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, March 03, 2016 1:53 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? I have been told that this issue is in Sprint 19, the current sprint, but the status is "icebox". What does "icebox" mean? https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 One of the reasons we ar particularly interested is that many EAD descriptions of photo collections make particularly heavy use of and . Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Dallas Pillen Assistant Archivist for Metadata and Digital Projects [https://webapps.lsa.umich.edu/dean/lsa_emails/bentley-sig-em.png] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Mon Mar 14 05:00:48 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Mon, 14 Mar 2016 09:00:48 +0000 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? In-Reply-To: References: , , , Message-ID: Hi Kate, Great. So, does everyone agree we can mark AR-1270 as Accepted? Or is there some outstanding issue? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Bowers, Kate A. Sent: Sunday, March 13, 2016 4:12 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Chris: Yes, thanks! It is working there (see http://test.archivesspace.org/resources/57#tree::resource_57) Bravo! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Chris Fitzpatrick Sent: Tuesday, March 8, 2016 2:03 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi, Ok, sorry about the altrender red herring. I just saw that was added to the test data and assume that was the hold up, but didn't look close enough. My bad... So...now I'm confused, since this seems to be reported as fixed, then not fixed, then fixed, etc. Kate are you testing against http://test.archivesspace.org ? The test site has the latest nightly build, so if it's fixed, it'll show it here. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dallas Pillen Sent: Tuesday, March 08, 2016 7:54 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi all, We here at the Bentley submitted that PR a few months ago to fix this physdesc mapping issue. As far as I can tell, there is no requirement to have an @altrender="part" attribute; rather, the PR was meant to make ArchivesSpace ingest physdescs in the same way that it exports them. There was some discussion about that on the PR here: https://github.com/archivesspace/archivesspace/pull/312 [https://avatars1.githubusercontent.com/u/7026330?v=3&s=400] AR-1134 and AR-1270: account for all physdesc subtags in EAD import by walkerdb ? Pull Request #312 ? archivesspace/archivesspace github.com JIRA references: AR-1134, AR-1270 We (at the Bentley Historical Library) wrote up a local fix for these issues, and thought we'd pass it upstream. Happy to refactor / edit if anything seems off! ... Basically, the ArchivesSpace EAD exporter exports an extent record's "portion" value as an altrender attribute of "whole" or "part," so the PR that we submitted checks for an altrender attribute and, if it finds one AND the altrender value is "part," the imported extent will have a portion of "part." Otherwise, in cases where there is no altrender attribute or the altrender attribute is some value other than "part," the extent record's portion is set to "whole." See here: https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L248-L252 I just tested importing an EAD with several physdesc variations (some with altrenders, some without; some with multiple extents, a physfacet and a dimensions element, some with only a single extent or a single physfacet, etc.) and it imported as expected (physdescs with an extent + other elements create only an extent record and no duplicate notes; physdescs with only non-extent elements create physical facet, physical dimensions, or physical description notes, and so on). The imported resource is here: http://test.archivesspace.org/resources/54 As far as I can tell, this issue has been fixed but it just has not made it into an official release (the PR was accepted last November; v. 1.4.2 came out in October). I uploaded the EAD that I just tested to the JIRA issue as physdesc_variations_test.xml. On Tue, Mar 8, 2016 at 1:37 PM, Bowers, Kate A. > wrote: I don?t understand the reasoning behind this at all. Why would a that has or only ever be a ?part?? Is there any documentation of the EAD ingest where this is recorded? Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 08, 2016 11:50 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi, We did our March sprint planning yesterday afternoon and this feature request was not included in the sprint. However, looking through this ticket, it looks like a pull request was already submitted and accepted that adds this feature. The key is that the physdesc has to have an @altrender = "part". If someone is wanting to submit a PR to remove the @altrender requirement to the feature, we would certainly look at it. b,chris. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Bowers, Kate A. > Sent: Tuesday, March 08, 2016 5:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? What are the next steps toward getting this bug fixed? I have just uploaded a document to https://archivesspace.atlassian.net/browse/AR-1134 It includes: 1) Undesirable behavior (current behavior) 2) Desired behavior 3) Multiple screenshots from my testing Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers 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, March 03, 2016 1:53 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? I have been told that this issue is in Sprint 19, the current sprint, but the status is "icebox". What does "icebox" mean? https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 One of the reasons we ar particularly interested is that many EAD descriptions of photo collections make particularly heavy use of and . Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Dallas Pillen Assistant Archivist for Metadata and Digital Projects [https://webapps.lsa.umich.edu/dean/lsa_emails/bentley-sig-em.png] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From Claire.Knowles at ed.ac.uk Mon Mar 14 08:14:12 2016 From: Claire.Knowles at ed.ac.uk (KNOWLES Claire) Date: Mon, 14 Mar 2016 12:14:12 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace codebase repository setup In-Reply-To: References: , Message-ID: Hi Chris and Alex, I'm interested in this discussion and the set-up others are using, as I'm not sure that the set-up we have for ArchivesSpace development is ideal. We are also customising ArchivesSpace and have made tweaks to the EAD import, footer, import jobs page. We have forked ArchivesSpace into a UoEMainLibrary GitHub account, which we then fork into our own accounts for doing development and then clone. This means that we make pull requests to the team account for changes. We have also created branches prefixed with uoe that are copies of the corresponding ArchivesSpace release tag. As I would rather than we only released the latest release from ArchivesSpace with our changes and not the master. We then deploy the whole application at once from this branch. Thanks, Claire ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Chris Fitzpatrick Sent: 11 March 2016 20:29 To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace codebase repository setup Hi, One thing you can do is to just set and upstream repo in git. I.e. : 0 ) Fork the main archivesspace/archivesspace repo and clone it 1 ) Add an upstream remote to your clone ( git remote add upstream https://github.com/archivesspace/archivesspace.git ) 2 ) now you can pull down any upstream changes ( git pull upstream master, or make a branch first, pull the upstream into that branch, then merge the brance into your master ) Does that make sense? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Alexander Duryee Sent: Friday, March 11, 2016 8:08 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] ArchivesSpace codebase repository setup We're undertaking local feature development for ArchivesSpace (ranging from EAD/MARC export tweaking to database migrations and corresponding UI updates); as such, we're setting up code repositories for our local codebase. Given that the ASpace application doesn't map cleanly to the source repo, it's not immediately clear what the best setup for a code repository will be. How has the list set up their local code repositories? Right now, there seem to be a few options for us: - fork the main ASpace repository, work there, and deploy a full copy of the repo into /plugins/local/ (losing migration/config source control) - set up a repo that contains the ASpace application, work in plugins/ (and migrations/ and config/ when needed), and deploy the entire application at once - set up a repo of just /plugins/, work there, and deploy that (losing config/migration source control) We're leaning towards the second option (if only to keep configs/migrations under source control), but none of these implementations feels satisfactory. Are there other methods of maintaining source control for ArchivesSpace code/config that the list is using? Thanks, --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: not available URL: From kate_bowers at harvard.edu Mon Mar 14 09:08:33 2016 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Mon, 14 Mar 2016 13:08:33 +0000 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? In-Reply-To: References: , , , , Message-ID: Something broke-- Before this fix, a lacking an created a Physical Description type note with mixed content. Now, a component lacking an extent results only in the dimensions and physical facet type notes, leaving the PCDATA in the behind entirely. See http://test.archivesspace.org/resources/58/edit#tree::archival_object_11931 No extent, single dimensions, single physfacet 1 photograph gelatin silver 8 x 10 inches Also attaching my test EAD. Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Chris Fitzpatrick Sent: Monday, March 14, 2016 5:00 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi Kate, Great. So, does everyone agree we can mark AR-1270 as Accepted? Or is there some outstanding issue? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Bowers, Kate A. Sent: Sunday, March 13, 2016 4:12 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Chris: Yes, thanks! It is working there (see http://test.archivesspace.org/resources/57#tree::resource_57) Bravo! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Chris Fitzpatrick Sent: Tuesday, March 8, 2016 2:03 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi, Ok, sorry about the altrender red herring. I just saw that was added to the test data and assume that was the hold up, but didn't look close enough. My bad... So...now I'm confused, since this seems to be reported as fixed, then not fixed, then fixed, etc. Kate are you testing against http://test.archivesspace.org ? The test site has the latest nightly build, so if it's fixed, it'll show it here. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dallas Pillen Sent: Tuesday, March 08, 2016 7:54 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi all, We here at the Bentley submitted that PR a few months ago to fix this physdesc mapping issue. As far as I can tell, there is no requirement to have an @altrender="part" attribute; rather, the PR was meant to make ArchivesSpace ingest physdescs in the same way that it exports them. There was some discussion about that on the PR here: https://github.com/archivesspace/archivesspace/pull/312 [https://avatars1.githubusercontent.com/u/7026330?v=3&s=400] AR-1134 and AR-1270: account for all physdesc subtags in EAD import by walkerdb ? Pull Request #312 ? archivesspace/archivesspace github.com JIRA references: AR-1134, AR-1270 We (at the Bentley Historical Library) wrote up a local fix for these issues, and thought we'd pass it upstream. Happy to refactor / edit if anything seems off! ... Basically, the ArchivesSpace EAD exporter exports an extent record's "portion" value as an altrender attribute of "whole" or "part," so the PR that we submitted checks for an altrender attribute and, if it finds one AND the altrender value is "part," the imported extent will have a portion of "part." Otherwise, in cases where there is no altrender attribute or the altrender attribute is some value other than "part," the extent record's portion is set to "whole." See here: https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L248-L252 I just tested importing an EAD with several physdesc variations (some with altrenders, some without; some with multiple extents, a physfacet and a dimensions element, some with only a single extent or a single physfacet, etc.) and it imported as expected (physdescs with an extent + other elements create only an extent record and no duplicate notes; physdescs with only non-extent elements create physical facet, physical dimensions, or physical description notes, and so on). The imported resource is here: http://test.archivesspace.org/resources/54 As far as I can tell, this issue has been fixed but it just has not made it into an official release (the PR was accepted last November; v. 1.4.2 came out in October). I uploaded the EAD that I just tested to the JIRA issue as physdesc_variations_test.xml. On Tue, Mar 8, 2016 at 1:37 PM, Bowers, Kate A. > wrote: I don?t understand the reasoning behind this at all. Why would a that has or only ever be a ?part?? Is there any documentation of the EAD ingest where this is recorded? Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 08, 2016 11:50 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi, We did our March sprint planning yesterday afternoon and this feature request was not included in the sprint. However, looking through this ticket, it looks like a pull request was already submitted and accepted that adds this feature. The key is that the physdesc has to have an @altrender = "part". If someone is wanting to submit a PR to remove the @altrender requirement to the feature, we would certainly look at it. b,chris. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Bowers, Kate A. > Sent: Tuesday, March 08, 2016 5:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? What are the next steps toward getting this bug fixed? I have just uploaded a document to https://archivesspace.atlassian.net/browse/AR-1134 It includes: 1) Undesirable behavior (current behavior) 2) Desired behavior 3) Multiple screenshots from my testing Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers 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, March 03, 2016 1:53 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? I have been told that this issue is in Sprint 19, the current sprint, but the status is "icebox". What does "icebox" mean? https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 One of the reasons we ar particularly interested is that many EAD descriptions of photo collections make particularly heavy use of and . Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Dallas Pillen Assistant Archivist for Metadata and Digital Projects [https://webapps.lsa.umich.edu/dean/lsa_emails/bentley-sig-em.png] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Test_physfacet_dimensions.xml Type: text/xml Size: 3507 bytes Desc: Test_physfacet_dimensions.xml URL: From Jessica.WagnerWebster at baruch.cuny.edu Mon Mar 14 09:50:24 2016 From: Jessica.WagnerWebster at baruch.cuny.edu (Jessica Wagner Webster) Date: Mon, 14 Mar 2016 13:50:24 +0000 Subject: [Archivesspace_Users_Group] archivesspace and omeka/csv resource metadata Message-ID: Hi all, I could use some help. Does anyone on this list use ArchivesSpace in conjunction with Omeka? In particular, I'm interested in figuring out a way to export metadata from AS to Omeka, which very much prefers flat Dublin Core CSV ingests to hierarchical data like XML. It seems clear that AS doesn't really want to export resource metadata to a CSV. Has anyone come up with a workaround? I've so far been exporting from AS into EAD and then using various methods of reformatting the XML into CSV, but that takes a lot of work. I'd appreciate any leads! (Or, if I'm missing some obvious way to do this, please let me know that too!) Thanks, Jessica Jessica Wagner Webster Digital Initiatives Librarian, Assistant Professor Baruch College, Newman Library 151 East 25th Street, Room 523 New York, NY 10010 (646) 312-1672 Jessica.WagnerWebster at baruch.cuny.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From PJFlanagan at ship.edu Mon Mar 14 11:09:38 2016 From: PJFlanagan at ship.edu (Flanagan, Patrick) Date: Mon, 14 Mar 2016 15:09:38 +0000 Subject: [Archivesspace_Users_Group] Plugin gems Message-ID: Good morning, I'm not exceedingly familiar with rails development. I'm making what should be a simple plugin, but I need a gem installed for it to work. gem install works on the OS side, but when ArchivesSpace gets to my plugin, it doesn't find the gem with require. What is the process of making ArchivesSpace aware of new gems for plugins? (Or rather, what is the correct way to do it?) This is for version 1.4.2. Thank you for your time, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave_mayo at harvard.edu Mon Mar 14 12:04:19 2016 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Mon, 14 Mar 2016 16:04:19 +0000 Subject: [Archivesspace_Users_Group] Plugin gems Message-ID: ArchivesSpace manages gems using bundler - and kind of a complicated bundler setup. The best solution is, as far as I understand it, to put the gemfiles in the appropriate place in the plugin, and then run bundler against the relevant gemfile/gemfiles. There's a build/run task called bundler, which would be run something like this: ./build/run bundler -Dgemfile=backend/Gemfile - Dave From: , Patrick > Reply-To: Archivesspace Users Group > Date: Monday, March 14, 2016 at 10:09 AM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Plugin gems Good morning, I'm not exceedingly familiar with rails development. I'm making what should be a simple plugin, but I need a gem installed for it to work. gem install works on the OS side, but when ArchivesSpace gets to my plugin, it doesn't find the gem with require. What is the process of making ArchivesSpace aware of new gems for plugins? (Or rather, what is the correct way to do it?) This is for version 1.4.2. Thank you for your time, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Mon Mar 14 12:52:54 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Mon, 14 Mar 2016 16:52:54 +0000 Subject: [Archivesspace_Users_Group] Plugin gems In-Reply-To: References: Message-ID: Hi, If you just want to develop against a packaged version of ArchivesSpace, you can just use the scripts/initialize_plugins.sh script and it will install your gems. Also, FYI and loop-back to something I talked with some folks at C4L, I just updated the initialize_plugins.sh script to unset the GEM_HOME and GEM_PATH variables, which was causing problems with the Redis demo plugin I did ( a problem if you're using something like RVM or Chruby ). I think that should fix it...no need to do a new update, you can just add those two UNSET lines to an existing script. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mayo, Dave Sent: Monday, March 14, 2016 5:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Plugin gems ArchivesSpace manages gems using bundler - and kind of a complicated bundler setup. The best solution is, as far as I understand it, to put the gemfiles in the appropriate place in the plugin, and then run bundler against the relevant gemfile/gemfiles. There's a build/run task called bundler, which would be run something like this: ./build/run bundler -Dgemfile=backend/Gemfile - Dave From: , Patrick > Reply-To: Archivesspace Users Group > Date: Monday, March 14, 2016 at 10:09 AM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Plugin gems Good morning, I'm not exceedingly familiar with rails development. I'm making what should be a simple plugin, but I need a gem installed for it to work. gem install works on the OS side, but when ArchivesSpace gets to my plugin, it doesn't find the gem with require. What is the process of making ArchivesSpace aware of new gems for plugins? (Or rather, what is the correct way to do it?) This is for version 1.4.2. Thank you for your time, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub -------------- next part -------------- An HTML attachment was scrubbed... URL: From PJFlanagan at ship.edu Mon Mar 14 15:16:20 2016 From: PJFlanagan at ship.edu (Flanagan, Patrick) Date: Mon, 14 Mar 2016 19:16:20 +0000 Subject: [Archivesspace_Users_Group] Plugin gems In-Reply-To: References: Message-ID: Thank you, Dave and Chris! I have a problem with bundler / initialize_plugins.sh. I wanted 'truncate_html' to do short summaries of certain fields in the public display. The script worked and installed it (or so it claims) by reading the Gemfile in my plugin. When I go to start aspace after that, it crashes due to not being able to find truncate_html java to install. If I remove the gemfile, it works again, but require 'truncate_html' fails, as though it had never been installed. It's a gem that is pure Ruby, so I'm surprised this happens. My plugin also fails if I just require 'nokogiri' and that's weird because I'm positive aspace has that already. The plugin's path for those require statements is "public/views/search/_result_summary_resource.html.erb" ~Patrick From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Monday, March 14, 2016 12:53 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Plugin gems Hi, If you just want to develop against a packaged version of ArchivesSpace, you can just use the scripts/initialize_plugins.sh script and it will install your gems. Also, FYI and loop-back to something I talked with some folks at C4L, I just updated the initialize_plugins.sh script to unset the GEM_HOME and GEM_PATH variables, which was causing problems with the Redis demo plugin I did ( a problem if you're using something like RVM or Chruby ). I think that should fix it...no need to do a new update, you can just add those two UNSET lines to an existing script. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Mayo, Dave > Sent: Monday, March 14, 2016 5:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Plugin gems ArchivesSpace manages gems using bundler - and kind of a complicated bundler setup. The best solution is, as far as I understand it, to put the gemfiles in the appropriate place in the plugin, and then run bundler against the relevant gemfile/gemfiles. There's a build/run task called bundler, which would be run something like this: ./build/run bundler -Dgemfile=backend/Gemfile - Dave From: , Patrick > Reply-To: Archivesspace Users Group > Date: Monday, March 14, 2016 at 10:09 AM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Plugin gems Good morning, I'm not exceedingly familiar with rails development. I'm making what should be a simple plugin, but I need a gem installed for it to work. gem install works on the OS side, but when ArchivesSpace gets to my plugin, it doesn't find the gem with require. What is the process of making ArchivesSpace aware of new gems for plugins? (Or rather, what is the correct way to do it?) This is for version 1.4.2. Thank you for your time, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at eservices.virginia.edu Mon Mar 14 15:53:49 2016 From: sdm7g at eservices.virginia.edu (Majewski, Steven Dennis (sdm7g)) Date: Mon, 14 Mar 2016 19:53:49 +0000 Subject: [Archivesspace_Users_Group] Plugin gems In-Reply-To: References: Message-ID: On Mar 14, 2016, at 3:16 PM, Flanagan, Patrick > wrote: Thank you, Dave and Chris! I have a problem with bundler / initialize_plugins.sh. I wanted ?truncate_html? to do short summaries of certain fields in the public display. The script worked and installed it (or so it claims) by reading the Gemfile in my plugin. When I go to start aspace after that, it crashes due to not being able to find truncate_html java to install. If I remove the gemfile, it works again, but require ?truncate_html? fails, as though it had never been installed. It?s a gem that is pure Ruby, so I?m surprised this happens. My plugin also fails if I just require ?nokogiri? and that?s weird because I?m positive aspace has that already. I think nokogiri gem is only included in backend and frontend Gemfiles, not in public. ( at least in v1.4.2 ) so if your require is in public would probably fail. dcs-archivesspace$ ack nokogiri */Gemfile backend/Gemfile 15:gem "nokogiri", '~> 1.6.1' frontend/Gemfile 49:gem "nokogiri", '~> 1.6.1' The plugin?s path for those require statements is ?public/views/search/_result_summary_resource.html.erb? ~Patrick From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Monday, March 14, 2016 12:53 PM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Plugin gems Hi, If you just want to develop against a packaged version of ArchivesSpace, you can just use the scripts/initialize_plugins.sh script and it will install your gems. Also, FYI and loop-back to something I talked with some folks at C4L, I just updated the initialize_plugins.sh script to unset the GEM_HOME and GEM_PATH variables, which was causing problems with the Redis demo plugin I did ( a problem if you're using something like RVM or Chruby ). I think that should fix it...no need to do a new update, you can just add those two UNSET lines to an existing script. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Mayo, Dave > Sent: Monday, March 14, 2016 5:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Plugin gems ArchivesSpace manages gems using bundler - and kind of a complicated bundler setup. The best solution is, as far as I understand it, to put the gemfiles in the appropriate place in the plugin, and then run bundler against the relevant gemfile/gemfiles. There's a build/run task called bundler, which would be run something like this: ./build/run bundler -Dgemfile=backend/Gemfile - Dave From: , Patrick > Reply-To: Archivesspace Users Group > Date: Monday, March 14, 2016 at 10:09 AM To: "archivesspace_users_group at lyralists.lyrasis.org" > Subject: [Archivesspace_Users_Group] Plugin gems Good morning, I?m not exceedingly familiar with rails development. I?m making what should be a simple plugin, but I need a gem installed for it to work. gem install works on the OS side, but when ArchivesSpace gets to my plugin, it doesn?t find the gem with require. What is the process of making ArchivesSpace aware of new gems for plugins? (Or rather, what is the correct way to do it?) This is for version 1.4.2. Thank you for your time, ~Patrick Flanagan KLN Applications Administrator Keystone Library Network Hub _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From r.carter at auckland.ac.nz Mon Mar 14 21:28:26 2016 From: r.carter at auckland.ac.nz (Robert Carter) Date: Tue, 15 Mar 2016 01:28:26 +0000 Subject: [Archivesspace_Users_Group] importing - preserving created, modified dates Message-ID: <39246DF2-4B61-4960-956E-D51B8673EB8F@auckland.ac.nz> Hi all, I?m running the migration from Archivists Toolkit -> ArchivesSpace using the AS plugin and it?s been going well. I have one issue. Is there a way preserve the created and modified dates of the AT items when they are imported into AS? Currently I have both these timestamped at the time the import happened, not their original timestamps. Best Rob Library Applications Development & Support Analyst & Programmer The University of Auckland From cspeterson at email.gwu.edu Tue Mar 15 08:49:49 2016 From: cspeterson at email.gwu.edu (Peterson, Christie) Date: Tue, 15 Mar 2016 08:49:49 -0400 Subject: [Archivesspace_Users_Group] importing - preserving created, modified dates In-Reply-To: <39246DF2-4B61-4960-956E-D51B8673EB8F@auckland.ac.nz> References: <39246DF2-4B61-4960-956E-D51B8673EB8F@auckland.ac.nz> Message-ID: The Yale team has a blog post on how they handled it: http://campuspress.yale.edu/yalearchivesspace/2015/05/01/keeping-timestamps-and-creator-names-from-at/, with link to the script in GitHub On Mon, Mar 14, 2016 at 9:28 PM, Robert Carter wrote: > Hi all, > > I?m running the migration from Archivists Toolkit -> ArchivesSpace using > the AS plugin and it?s been going well. I have one issue. > > Is there a way preserve the created and modified dates of the AT items > when they are imported into AS? Currently I have both these timestamped at > the time the import happened, not their original timestamps. > > Best > Rob > > Library Applications Development & Support > Analyst & Programmer > The University of Auckland > > > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Christie S. Peterson University Archivist George Washington University Libraries 704H Gelman Library cspeterson at gwu.edu 202.994.3925 -------------- next part -------------- An HTML attachment was scrubbed... URL: From shallcro at umich.edu Tue Mar 15 10:51:36 2016 From: shallcro at umich.edu (Michael Shallcross) Date: Tue, 15 Mar 2016 10:51:36 -0400 Subject: [Archivesspace_Users_Group] Registration Open: Free Aeon Symposium @ UM (June 15-17, 2016): Includes relevant ASpace sessions Message-ID: (Apologies for cross-posting...) Greetings, all; the University of Michigan Bentley Historical Library, Special Collections Library, and William L. Clements Library are pleased to announce an Aeon Symposium dedicated to Connecting Uses, Pushing Limits among current and prospective institutional users of Aeon. This *free* 2.5 day symposium will take place on June 15 ? 17, 2016 at the University of Michigan in Ann Arbor, Michigan. Topics will include: - The learning curve of Aeon - ?Aeon intelligence? from collections development to curation - The effect of Aeon on change management - Integration of Aeon and ArchivesSpace - Aeon and the undergraduate - Multiple languages in Aeon For more information and to register, please visit: http://www.aeonum2016.org/ If you have any questions about the event, please contact AeonUM2016 at umich.edu. Hope to see you in Ann Arbor this June! -- *Michael Shallcross, CA* *Assistant Director for Curation* Bentley Historical Library 1150 Beal Ave. Ann Arbor, MI 48109-2113 734.936.1344 http://bentley.umich.edu/ http://archival-integration.blogspot.com/ @umbhlcuration -------------- next part -------------- An HTML attachment was scrubbed... URL: From sziegler at amphilsoc.org Tue Mar 15 14:04:52 2016 From: sziegler at amphilsoc.org (Scott Ziegler) Date: Tue, 15 Mar 2016 14:04:52 -0400 Subject: [Archivesspace_Users_Group] Mid-Atlantic ArchivesSpace Interest Group Message-ID: Hi Everyone, I'm very happy to announce the formation of the Mid-Atlantic ArchivesSpace Interest Group. Growing from excitement after a workshop last week in the Philadelphia-area, this regional interest group offers a means of communication for organizations in the Mid-Atlantic region working with ASpace, and we might hold meet-ups from time to time (if so desired). If you are interested in joining the Google group, you can do so here: https://groups.google.com/forum/#!forum/mid-atlantic-archivesspace-interest-group If you have any questions, don't hesitate to ask. Thanks!? Scott Scott Ziegler, MA, MSLIS, CA Assistant Head of Technology/Web Development Librarian American Philosophical Society 105 South 5th Street Philadelphia, PA 19106 Telephone: 215.599.4299 Email: sziegler at amphilsoc.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From francis.lapka at yale.edu Tue Mar 15 14:19:12 2016 From: francis.lapka at yale.edu (Lapka, Francis) Date: Tue, 15 Mar 2016 18:19:12 +0000 Subject: [Archivesspace_Users_Group] customizing tokeninput dropdowns Message-ID: I'd like to strongly echo Kevin's request for a mechanism that would allow us to disambiguate terms that -- on the dropdown menu -- are identical. Our term list includes innumerable duplicates of authorized topical terms and form/genre terms, and the inability to tell one from the other while editing a resource description is a severe impediment. In the context of subjects, display of "type" information would solve the problem most of the time. There are times when it would also be useful to display the subject "source" value -- for example, to disambiguate identical genre terms from different thesauri. A similar feature for the agents dropdown may have warrant too (to disambiguate identical name forms, from different sources). Francis Francis Lapka * Catalog Librarian Department of Rare Books and Manuscripts Yale Center for British Art 203.432.9672 * francis.lapka at yale.edu --- [Archivesspace_Users_Group] customizing tokeninput dropdowns Kevin Clair Kevin.Clair at du.edu ... Hello, Our archivists would like, when searching for subjects in the Resource form, for the Tokeninput dropdown to display the first term type for a heading in addition to its label, because we have a handful of terms that are identical except for their type and it would be helpful for disambiguation. Is it possible to do this via a plugin? I know in theory from poking around at https://loopj.com/jquery-tokeninput/demo.html how to edit Tokeninput dropdowns, but in practice it seems buried pretty deep in the application so I thought I'd ask the list to see if anyone else has played around with it. thanks! -k From brad.westbrook at lyrasis.org Tue Mar 15 18:04:44 2016 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Tue, 15 Mar 2016 22:04:44 +0000 Subject: [Archivesspace_Users_Group] Mid-Atlantic ArchivesSpace Interest Group In-Reply-To: References: Message-ID: This is great news, Scott. Thank you for moving this forward and for sharing. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Scott Ziegler Sent: Tuesday, March 15, 2016 2:05 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Mid-Atlantic ArchivesSpace Interest Group Hi Everyone, I'm very happy to announce the formation of the Mid-Atlantic ArchivesSpace Interest Group. Growing from excitement after a workshop last week in the Philadelphia-area, this regional interest group offers a means of communication for organizations in the Mid-Atlantic region working with ASpace, and we might hold meet-ups from time to time (if so desired). If you are interested in joining the Google group, you can do so here: https://groups.google.com/forum/#!forum/mid-atlantic-archivesspace-interest-group If you have any questions, don't hesitate to ask. Thanks!? Scott Scott Ziegler, MA, MSLIS, CA Assistant Head of Technology/Web Development Librarian American Philosophical Society 105 South 5th Street Philadelphia, PA 19106 Telephone: 215.599.4299 Email: sziegler at amphilsoc.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Wed Mar 16 10:48:28 2016 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Wed, 16 Mar 2016 10:48:28 -0400 Subject: [Archivesspace_Users_Group] ArchivesSpace Integrations Update Message-ID: Hi all, The Integrations subteam has started collecting information related to ArchivesSpace integrations, and are currently accepting any and all information about complete, in-progress, or conceptual ArchivesSpace integrations on our Integrations and Other Community Projects page. As you can see we have three integrations here already, primarily pertaining to description of digital materials either through Archivematica or Preservica. I've included a brief overview of each below: * ArchivesSpace-Archivematica-DSpace Workflow Integration * Introduce functionality into Archivematica that will permit users to review, appraise, deaccession and arrange content in a new "Appraisal and Arrangement" tab in the system dashboard. * Load (and create) ArchivesSpace archival object records in the Archivematica "Appraisal and Arrangement" tab and then drag and drop content onto the appropriate archival objects to define Submission Information Packages (SIPs) that will in turn be described as 'digital objects' in ArchivesSpace and deposited as discrete 'items' in DSpace. * Create new archival object and digital object records in ArchivesSpace and associate the latter with DSpace handles to provide URIs/'href' values for elements in exported EADs. * ArchivesSpace-Archivematica Integration * Introduce functionality into Archivematica that will let users pair digital objects to ArchivesSpace resources/components and automatically generate Digital Objects in AS based on the digital objects. * Create Access/Restrict notes based on PREMIS information entered into Archivematica. * Automatically pair digital objects to ArchivesSpace resources/components through matching digital filenames and AS ref_ids. * Preservica-ArchivesSpace Integration * Introduce functionality into Preservica to manage ingested content according to ArchivesSpace record hierarchies, linked through ArchivesSpace ref_ids * Create linked ArchivesSpace digital records records for materials ingested into Preservica * Enable synchronization of metadata between ArchivesSpace and Preservica for preservation purposes We'd love to hear about more integrations the community is working on, so please take the time to enter any you are working on into this google form. We're also happy to answer any questions you might have. Best, Patrick Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 -------------- next part -------------- An HTML attachment was scrubbed... URL: From archives at mobilearchdiocese.org Wed Mar 16 10:54:56 2016 From: archives at mobilearchdiocese.org (AOM Archives) Date: Wed, 16 Mar 2016 09:54:56 -0500 Subject: [Archivesspace_Users_Group] Web-available workshop Message-ID: <1b25a4eb387c455e9a08f7d0f36b0539@mobilearchdiocese.org> Is there a reason that one of the basic workshops that are given here and there, mostly far away from me, could not be recorded and made available to the membership online? I really need the basic info, as this is my first encounter with archival description software of any kind and I'm struggling with things lots of y'all take for granted with data entry and concepts, things which are probable fairly simple if you know the secrets. I suspect that I am not the only person out there who would love, love, love to be able to attend a basic workshop but cannot--distance, finances, time, etc. Any advice, etc., would also be greatly appreciated. Karen Horton, CA Archivist, Archdiocese of Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Mar 16 11:16:01 2016 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 16 Mar 2016 15:16:01 +0000 Subject: [Archivesspace_Users_Group] Web-available workshop In-Reply-To: <1b25a4eb387c455e9a08f7d0f36b0539@mobilearchdiocese.org> References: <1b25a4eb387c455e9a08f7d0f36b0539@mobilearchdiocese.org> Message-ID: Hi Karen, Your timing in asking this question is excellent. The ArchivesSpace trainer corps is in the process of preparing (by contract) a multi-webinar version of our Basics workshop for staff from a number of institutions in the Keystone Library Network (KLN) that will start at the end of this month. Though this series will be limited to KLN staff members, we're hoping to use the experience to develop web content that will be accessible to other individuals and groups of members very soon after. This will all start to come into closer focus later this spring and I'll be glad to reach out to you directly, as well as share information on the list, when I have more information to share. The current model for the face-to-face training offered by the ArchivesSpace is that institutions, or groups of institutions, serve as the physical host for the sessions and contract with us to provide instructors. The hosting organization can invite whomever it wishes, and charge, or not charge, if it wishes. If there are a number of interested ArchivesSpace users in a particular geographic area or institution and hosting a face-to-face session is of interest, we definitely encourage you to pool resources to bring the training to you. In terms of currently available web content, I'll also give a plug for the screencasts we offer in the member area (http://docs.archivesspace.org), and for those who are comfortable with particular functions in ArchivesSpace to consider recording screencasts for the series (https://archivesspace.atlassian.net/wiki/display/ADC/Instructions+for+Creating+a+Video+for+the+ArchivesSpace+User+Screencast+Series). There are many topics still up for grabs, and there is a small honorarium available for those who finish videos. If anyone has other questions or suggestions related to training, please feel free to post them here, or get in touch with me directly. Getting more people more comfortable with ArchivesSpace benefits all of us! Best, Christine Christine Di Bella Community Outreach and Support Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [cid:image003.png at 01CE734E.FD759D30] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of AOM Archives Sent: Wednesday, March 16, 2016 10:55 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Web-available workshop Is there a reason that one of the basic workshops that are given here and there, mostly far away from me, could not be recorded and made available to the membership online? I really need the basic info, as this is my first encounter with archival description software of any kind and I'm struggling with things lots of y'all take for granted with data entry and concepts, things which are probable fairly simple if you know the secrets. I suspect that I am not the only person out there who would love, love, love to be able to attend a basic workshop but cannot--distance, finances, time, etc. Any advice, etc., would also be greatly appreciated. Karen Horton, CA Archivist, Archdiocese of Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7645 bytes Desc: image001.png URL: From eckardm at umich.edu Wed Mar 16 12:09:08 2016 From: eckardm at umich.edu (Max Eckard) Date: Wed, 16 Mar 2016 12:09:08 -0400 Subject: [Archivesspace_Users_Group] ArchivesSpace Integrations Update In-Reply-To: References: Message-ID: We forgot one from our friends at the American Academy in Rome! - *ASpace-to-Drupal* - Using currently available contributed and custom Drupal modules, this project will provide a mechanism to periodically poll the ArchivesSpace REST interface for newly created and changed archival and digital objects. - Currently, the project uses cURL HTTP (chr), Web Service Data (wsdata), and some glue code to pipe ArchivesSpace-provided JSON formatted objects into Drupal entities. These entities can be formatted, manipulated, and indexed via traditional Drupal methods (Views, Solr, Elastic Search, etc.). - Future releases will replace cURL HTTP and Web Service Data with custom Guzzle component requests. As always, we?d love to hear about more integrations the community is working on, so please take the time to let us know what you're up to using this Google Form . Thanks! Max On Wed, Mar 16, 2016 at 10:48 AM, Galligan, Patrick wrote: > Hi all, > > > > The Integrations subteam has started collecting information related to > ArchivesSpace integrations, and are currently accepting any and all > information about complete, in-progress, or conceptual ArchivesSpace > integrations on our Integrations and Other Community Projects > > page. > > > > As you can see we have three integrations here already, primarily > pertaining to description of digital materials either through Archivematica > or Preservica. I?ve included a brief overview of each below: > > > > ? *ArchivesSpace-Archivematica-DSpace Workflow Integration* > > - Introduce functionality into Archivematica that will permit users to > review, appraise, deaccession and arrange content in a new "Appraisal and > Arrangement" tab in the system dashboard. > - Load (and create) ArchivesSpace archival object records in the > Archivematica "Appraisal and Arrangement" tab and then drag and drop > content onto the appropriate archival objects to define Submission > Information Packages (SIPs) that will in turn be described as 'digital > objects' in ArchivesSpace and deposited as discrete 'items' in DSpace. > - Create new archival object and digital object records in > ArchivesSpace and associate the latter with DSpace handles to provide > URIs/'href' values for elements in exported EADs. > - *ArchivesSpace-Archivematica Integration* > - Introduce functionality into Archivematica that will let users > pair digital objects to ArchivesSpace resources/components and > automatically generate Digital Objects in AS based on the digital objects. > - Create Access/Restrict notes based on PREMIS information entered > into Archivematica. > - Automatically pair digital objects to ArchivesSpace > resources/components through matching digital filenames and AS ref_ids. > - *Preservica-ArchivesSpace Integration* > - Introduce functionality into Preservica to manage ingested > content according to ArchivesSpace record hierarchies, linked through > ArchivesSpace ref_ids > - Create linked ArchivesSpace digital records records for materials > ingested into Preservica > - Enable synchronization of metadata between ArchivesSpace and > Preservica for preservation purposes > > We?d love to hear about more integrations the community is working on, so > please take the time to enter any you are working on into this google form > > . > > > > We?re also happy to answer any questions you might have. > > > > Best, > > Patrick > > > > Patrick Galligan > > Rockefeller Archive Center > > Assistant Digital Archivist > > 914-366-6386 > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- *Max Eckard* *Assistant Archivist for Digital Curation* Bentley Historical Library 1150 Beal Ave. Ann Arbor, MI 48109-2113 734/763-7518 <734.763.7518> http://bentley.umich.edu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From smithkr at mit.edu Wed Mar 16 13:43:24 2016 From: smithkr at mit.edu (Kari R Smith) Date: Wed, 16 Mar 2016 17:43:24 +0000 Subject: [Archivesspace_Users_Group] importing - preserving created, modified dates In-Reply-To: <39246DF2-4B61-4960-956E-D51B8673EB8F@auckland.ac.nz> References: <39246DF2-4B61-4960-956E-D51B8673EB8F@auckland.ac.nz> Message-ID: <29F559819ACA9A4FBF208407D4B63ABBD74E0E3F@OC11EXPO32.exchange.mit.edu> Christie, thanks for the info of the blog post and script! Has anyone done this who is using LYRASIS as their Hosting provider? Thanks, Kari -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Robert Carter Sent: Monday, March 14, 2016 9:28 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] importing - preserving created, modified dates Hi all, I?m running the migration from Archivists Toolkit -> ArchivesSpace using the AS plugin and it?s been going well. I have one issue. Is there a way preserve the created and modified dates of the AT items when they are imported into AS? Currently I have both these timestamped at the time the import happened, not their original timestamps. Best Rob Library Applications Development & Support Analyst & Programmer The University of Auckland _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From ltang5 at mail.lib.msu.edu Thu Mar 17 10:47:00 2016 From: ltang5 at mail.lib.msu.edu (Tang, Lydia) Date: Thu, 17 Mar 2016 14:47:00 +0000 Subject: [Archivesspace_Users_Group] Export folder labels question Message-ID: <40F89A9C-C8EF-4EC5-A545-A56D82A2E035@mail.lib.msu.edu> Hello everyone! I saw in a 2013 Aspace Google forum post that version 0.4 was going to incorporate a function to export folder labels. https://groups.google.com/forum/#!searchin/archivesspace/folder$20labels/archivesspace/s3iYwe_LOas/ca-X4qvJNlMJ That sounds like a very helpful and timesaving tool, but I haven?t been able to find more information about how to access and use it. Not being particularly techie, I was really proud of myself for figuring out how to export container labels for a resource, but it only goes as far as the box level. Could anyone fill me in on how to use the Export Folder Labels function? Thanks so much for any help you could provide! Lydia From noah.huffman at duke.edu Thu Mar 17 11:13:08 2016 From: noah.huffman at duke.edu (Noah Huffman) Date: Thu, 17 Mar 2016 15:13:08 +0000 Subject: [Archivesspace_Users_Group] remove created/last-modified column from search results and browse pages? Message-ID: Hello, Reviving this old thread on the list. Has anyone successfully removed the created/last modified column from the browse and search result pages in the staff interface? I don?t think this is possible using the preference settings in the app. I?m sure this is possible in a plugin, but I can?t quite locate the relevant view templates in the application. Any advice? Thanks, -Noah ================ Noah Huffman Archivist for Metadata, Systems, and Digital Records David M. Rubenstein Rare Book & Manuscript Library Duke University | 919-660-5982 http://library.duke.edu/rubenstein/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Goldman Sent: Tuesday, September 02, 2014 11:29 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] search results Thanks, Patrick. I recall seeing this now. I'd still be interested in hearing whether it's possible to turn off certain columns like the created/last-modified. And while it's not terribly important, since in-module modification is possible, I'd be interested to know whether the cross-module search results (the Search All Records box in the toolbar) can be modified as well. Best, Ben ________________________________ From: "Patrick Galligan" > To: "Archivesspace Users Group" > Sent: Tuesday, September 2, 2014 11:02:01 AM Subject: Re: [Archivesspace_Users_Group] search results Ben, I can?t speak on the faceting options (it?s something we would be interested in knowing as well), but you can customize the grids in the browse screens at least. You just have to set the repository preferences to include identifier in column 1. However, this won?t change the results of the search all records box, just the searching/browsing within each module. Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Goldman Sent: Tuesday, September 02, 2014 10:58 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] search results Hello, I've seen some email threads about search behavior, but I can't recall seeing any about how search results are displayed, particularly as it relates to the staff interface. For our purposes, having the last_modified and date_created display in the search results isn't useful, but having the record's unique identifier would be -- in particular the Identifier associated with Accession and Resource records -- especially since we often sort these values when browsing results in AT. Is the search results grid customizable? Also, are the faceting options on the search results customizable? Because we have a poor legacy related to authorities in archival data, the facets related to Creator and Subject are cluttering up the results, and we'd prefer to remove them for now. Thanks, Ben Ben Goldman Digital Records Archivist Penn State University Libraries University Park, PA 814-863-8333 http://www.libraries.psu.edu/psul/speccolls.html _______________________________________________ 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 james at hudmol.com Thu Mar 17 18:19:47 2016 From: james at hudmol.com (James Bullen) Date: Fri, 18 Mar 2016 09:19:47 +1100 Subject: [Archivesspace_Users_Group] remove created/last-modified column from search results and browse pages? In-Reply-To: References: Message-ID: Hi Noah, I think you?d want to override this template: /views/search/_listing.html.erb Search for ?audit? in there and you should find what you?re looking for. Hope that helps. Cheers, James > On Mar 18, 2016, at 2:13 AM, Noah Huffman wrote: > > Hello, > > Reviving this old thread on the list. Has anyone successfully removed the created/last modified column from the browse and search result pages in the staff interface? I don?t think this is possible using the preference settings in the app. > > I?m sure this is possible in a plugin, but I can?t quite locate the relevant view templates in the application. > > Any advice? > > Thanks, > -Noah > > ================ > Noah Huffman > Archivist for Metadata, Systems, and Digital Records > David M. Rubenstein Rare Book & Manuscript Library > Duke University | 919-660-5982 > http://library.duke.edu/rubenstein/ > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org ] On Behalf Of Ben Goldman > Sent: Tuesday, September 02, 2014 11:29 AM > To: Archivesspace Users Group > > Subject: Re: [Archivesspace_Users_Group] search results > > Thanks, Patrick. I recall seeing this now. I'd still be interested in hearing whether it's possible to turn off certain columns like the created/last-modified. And while it's not terribly important, since in-module modification is possible, I'd be interested to know whether the cross-module search results (the Search All Records box in the toolbar) can be modified as well. > > Best, > Ben > > From: "Patrick Galligan" > > To: "Archivesspace Users Group" > > Sent: Tuesday, September 2, 2014 11:02:01 AM > Subject: Re: [Archivesspace_Users_Group] search results > > Ben, > > I can?t speak on the faceting options (it?s something we would be interested in knowing as well), but you can customize the grids in the browse screens at least. > > You just have to set the repository preferences to include identifier in column 1. However, this won?t change the results of the search all records box, just the searching/browsing within each module. > > Patrick Galligan > Rockefeller Archive Center > Assistant Digital Archivist > 914-366-6386 > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org ] On Behalf Of Ben Goldman > Sent: Tuesday, September 02, 2014 10:58 AM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] search results > > Hello, > > I've seen some email threads about search behavior, but I can't recall seeing any about how search results are displayed, particularly as it relates to the staff interface. > > For our purposes, having the last_modified and date_created display in the search results isn't useful, but having the record's unique identifier would be -- in particular the Identifier associated with Accession and Resource records -- especially since we often sort these values when browsing results in AT. Is the search results grid customizable? > > Also, are the faceting options on the search results customizable? Because we have a poor legacy related to authorities in archival data, the facets related to Creator and Subject are cluttering up the results, and we'd prefer to remove them for now. > > Thanks, > Ben > > Ben Goldman > Digital Records Archivist > Penn State University Libraries > University Park, PA > 814-863-8333 > http://www.libraries.psu.edu/psul/speccolls.html > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > !DSPAM:56eac994310203001118560! _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:56eac994310203001118560! -------------- next part -------------- An HTML attachment was scrubbed... URL: From cdeveyra at colburnschool.edu Mon Mar 21 15:33:46 2016 From: cdeveyra at colburnschool.edu (Clarice de Veyra) Date: Mon, 21 Mar 2016 19:33:46 +0000 Subject: [Archivesspace_Users_Group] ASpace and Microsoft Access? Message-ID: Hi, I'm new to ArchivesSpace and am wondering if anyone has used Microsoft Access instead of MySQL for their database? Thanks! Clarice -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Mon Mar 21 16:45:00 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Mon, 21 Mar 2016 20:45:00 +0000 Subject: [Archivesspace_Users_Group] ASpace and Microsoft Access? In-Reply-To: References: Message-ID: Hi, Sorry, Aspace currently doesn't support MS Access. Only MySQL. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Clarice de Veyra Sent: Monday, March 21, 2016 8:33 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] ASpace and Microsoft Access? Hi, I'm new to ArchivesSpace and am wondering if anyone has used Microsoft Access instead of MySQL for their database? Thanks! Clarice -------------- next part -------------- An HTML attachment was scrubbed... URL: From ktasker at library.berkeley.edu Tue Mar 22 13:38:10 2016 From: ktasker at library.berkeley.edu (Kate Tasker) Date: Tue, 22 Mar 2016 10:38:10 -0700 Subject: [Archivesspace_Users_Group] Save error: "FULL head" Message-ID: Hi ArchivesSpace Users, One of our staff has been encountering a save error while editing a Resource Record. The error message appears between the Resource Tree and the Basic Information section, and reads: An error occurred saving this record. FULL head Also see attached screenshot. Any clues? Thanks, -Kate Kate Tasker Digital Archivist The Bancroft Library University of California Berkeley, CA 94720-6000 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: save-error-full-head.png Type: image/png Size: 3888794 bytes Desc: not available URL: From mauraa at brandeis.edu Tue Mar 22 13:56:36 2016 From: mauraa at brandeis.edu (Maura Carbone) Date: Tue, 22 Mar 2016 13:56:36 -0400 Subject: [Archivesspace_Users_Group] EAC Export Error Message-ID: Hi all, I'm attempting to export some EAC for my agents and I've run into an error on the following export: http://findingaids.brandeis.edu/agents/59?agent_type=agent_person When I attempt to export this within my EAC I get the following error: ASPACE EXPORT ERROR : YOU HAVE A PROBLEM WITH YOUR EXPORT OF YOUR RESOURCE. THE FOLLOWING INFORMATION MAY HELP: undefined method `map' for nil:NilClass ["/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:119:in `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:112:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:111:in `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:109:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:99:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:82:in `_cpfdesc'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:23:in `_eac'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:16:in `_eac'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:7:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:293:in `initialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:6:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:94:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:108:in `generate_eac'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:208:in `ArchivesSpaceService'", "org/jruby/RubyBasicObject.java:1574:in `instance_eval'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:241:in `returns'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:123:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:99:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:122:in `_transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87:in `hold'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:98:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:122:in `open'", "org/jruby/RubyFixnum.java:280:in `times'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:119:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:223:in `returns'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:23:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:207:in `returns'", "org/jruby/RubyMethod.java:116:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1293:in `compile!'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:876:in `route_eval'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:897:in `process_route'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:895:in `process_route'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:859:in `route!'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:858:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:963:in `dispatch!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:960:in `dispatch!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in `call!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in `call!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:780:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:277:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/nulllogger.rb:9:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/head.rb:9:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:124:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1499:in `synchronize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/vendor/rack-1.5.5/rack/builder.rb:138:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:64:in `call'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:49:in `call'", "file:/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/rack/handler/servlet.rb:22:in `call'"] After the bioghist section I get the rest of the EAC. Our bioghist has 3 subnotes (text and 2 citations) none of which come across. Any idea why this is happening? I'm running 1.4.1 so I don't know if this is fixed in 1.4.2. I didn't see a ticket about this when I looked in JIRA but I might have missed it. -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Tue Mar 22 14:16:46 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Tue, 22 Mar 2016 18:16:46 +0000 Subject: [Archivesspace_Users_Group] Save error: "FULL head" In-Reply-To: References: Message-ID: Hi, Yes, doing a google search returned this: https://groups.google.com/forum/m/?fromgroups#!topic/archivesspace/A7C6P7EqQZY We need to increase the buffer size on jetty to handle larger record sizes. There is a temporary solution listed in the Google group thread... b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kate Tasker Sent: Tuesday, March 22, 2016 6:38 PM To: ArchivesSpace Users Group Subject: [Archivesspace_Users_Group] Save error: "FULL head" Hi ArchivesSpace Users, One of our staff has been encountering a save error while editing a Resource Record. The error message appears between the Resource Tree and the Basic Information section, and reads: An error occurred saving this record. FULL head Also see attached screenshot. Any clues? Thanks, -Kate Kate Tasker Digital Archivist The Bancroft Library University of California Berkeley, CA 94720-6000 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Tue Mar 22 14:29:02 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Tue, 22 Mar 2016 18:29:02 +0000 Subject: [Archivesspace_Users_Group] EAC Export ErrorY In-Reply-To: References: Message-ID: Yeah, looks like ther exporter assumes there's going to be something the Xlink section...if that's empty it causes a problem. Made a bug ticket here: https://archivesspace.atlassian.net/browse/AR-1453 b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Maura Carbone Sent: Tuesday, March 22, 2016 6:56 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] EAC Export Error Hi all, I'm attempting to export some EAC for my agents and I've run into an error on the following export: http://findingaids.brandeis.edu/agents/59?agent_type=agent_person When I attempt to export this within my EAC I get the following error: ASPACE EXPORT ERROR : YOU HAVE A PROBLEM WITH YOUR EXPORT OF YOUR RESOURCE. THE FOLLOWING INFORMATION MAY HELP: undefined method `map' for nil:NilClass ["/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:119:in `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:112:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:111:in `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:109:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:99:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:82:in `_cpfdesc'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:23:in `_eac'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:16:in `_eac'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:7:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:293:in `initialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:6:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:94:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:108:in `generate_eac'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:208:in `ArchivesSpaceService'", "org/jruby/RubyBasicObject.java:1574:in `instance_eval'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:241:in `returns'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:123:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:99:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:122:in `_transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87:in `hold'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:98:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:122:in `open'", "org/jruby/RubyFixnum.java:280:in `times'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:119:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:223:in `returns'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:23:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:207:in `returns'", "org/jruby/RubyMethod.java:116:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1293:in `compile!'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:876:in `route_eval'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:897:in `process_route'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:895:in `process_route'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:859:in `route!'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:858:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:963:in `dispatch!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:960:in `dispatch!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in `call!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in `call!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:780:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:277:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/nulllogger.rb:9:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/head.rb:9:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:124:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1499:in `synchronize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/vendor/rack-1.5.5/rack/builder.rb:138:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:64:in `call'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:49:in `call'", "file:/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/rack/handler/servlet.rb:22:in `call'"] After the bioghist section I get the rest of the EAC. Our bioghist has 3 subnotes (text and 2 citations) none of which come across. Any idea why this is happening? I'm running 1.4.1 so I don't know if this is fixed in 1.4.2. I didn't see a ticket about this when I looked in JIRA but I might have missed it. -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Tue Mar 22 14:58:00 2016 From: mauraa at brandeis.edu (Maura Carbone) Date: Tue, 22 Mar 2016 14:58:00 -0400 Subject: [Archivesspace_Users_Group] EAC Export ErrorY In-Reply-To: References: Message-ID: Filled in the xcode, which removes the error, but just FYI the biog/hist text still doesn't come through (I get my citation notes but none of the actual biog note itself). Don't know if that should go on that ticket or on a new one. On Tue, Mar 22, 2016 at 2:29 PM, Chris Fitzpatrick < Chris.Fitzpatrick at lyrasis.org> wrote: > > > Yeah, looks like ther exporter assumes there's going to be something the > Xlink section...if that's empty it causes a problem. > > Made a bug ticket here: > > https://archivesspace.atlassian.net/browse/AR-1453 > > > > > b,chris. > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Maura Carbone > *Sent:* Tuesday, March 22, 2016 6:56 PM > *To:* Archivesspace Users Group > *Subject:* [Archivesspace_Users_Group] EAC Export Error > > Hi all, > I'm attempting to export some EAC for my agents and I've run into an error > on the following export: > http://findingaids.brandeis.edu/agents/59?agent_type=agent_person > > When I attempt to export this within my EAC I get the following error: > > > ASPACE EXPORT ERROR : YOU HAVE A PROBLEM WITH > YOUR EXPORT OF YOUR RESOURCE. THE FOLLOWING INFORMATION MAY HELP: > > undefined method `map' for nil:NilClass > ["/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:119:in > `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:112:in > `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in > `insert'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in > `method_missing'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in > `method_missing'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:111:in > `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:109:in > `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in > `insert'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in > `method_missing'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in > `method_missing'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:99:in > `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in > `insert'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in > `method_missing'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in > `method_missing'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:82:in > `_cpfdesc'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:23:in > `_eac'", "org/jruby/RubyProc.java:271:in `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in > `insert'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in > `method_missing'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in > `method_missing'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:16:in > `_eac'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:7:in > `serialize'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:293:in > `initialize'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:6:in > `serialize'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:94:in > `serialize'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:108:in > `generate_eac'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:208:in > `ArchivesSpaceService'", "org/jruby/RubyBasicObject.java:1574:in > `instance_eval'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:241:in > `returns'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:123:in > `open'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:99:in > `transaction'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in > `_transaction'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:122:in > `_transaction'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in > `transaction'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in > `hold'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87:in > `hold'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in > `synchronize'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in > `transaction'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:98:in > `transaction'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:122:in > `open'", "org/jruby/RubyFixnum.java:280:in `times'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:119:in > `open'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:223:in > `returns'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in > `open'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:23:in > `open'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:207:in > `returns'", "org/jruby/RubyMethod.java:116:in `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1293:in > `compile!'", "org/jruby/RubyProc.java:271:in `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in > `route!'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:876:in > `route_eval'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in > `route!'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:897:in > `process_route'", "org/jruby/RubyKernel.java:1242:in `catch'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:895:in > `process_route'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:859:in > `route!'", "org/jruby/RubyArray.java:1613:in `each'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:858:in > `route!'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:963:in > `dispatch!'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in > `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in > `invoke'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:960:in > `dispatch!'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in > `call!'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in > `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in > `invoke'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in > `call!'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:780:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:277:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/nulllogger.rb:9:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/head.rb:9:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:124:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1499:in > `synchronize'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/vendor/rack-1.5.5/rack/builder.rb:138:in > `call'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:64:in > `call'", "org/jruby/RubyArray.java:1613:in `each'", > "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:49:in > `call'", > "file:/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/rack/handler/servlet.rb:22:in > `call'"] > > > After the bioghist section I get the rest of the EAC. Our bioghist has 3 > subnotes (text and 2 citations) none of which come across. > > Any idea why this is happening? I'm running 1.4.1 so I don't know if this > is fixed in 1.4.2. I didn't see a ticket about this when I looked in JIRA > but I might have missed it. > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Tue Mar 22 16:18:25 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Tue, 22 Mar 2016 20:18:25 +0000 Subject: [Archivesspace_Users_Group] EAC Export ErrorY In-Reply-To: References: , Message-ID: Yeah, I think you have to make sure that the note and subnote are published? Does that work? Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Maura Carbone Sent: Tuesday, March 22, 2016 7:58 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] EAC Export ErrorY Filled in the xcode, which removes the error, but just FYI the biog/hist text still doesn't come through (I get my citation notes but none of the actual biog note itself). Don't know if that should go on that ticket or on a new one. On Tue, Mar 22, 2016 at 2:29 PM, Chris Fitzpatrick > wrote: Yeah, looks like ther exporter assumes there's going to be something the Xlink section...if that's empty it causes a problem. Made a bug ticket here: https://archivesspace.atlassian.net/browse/AR-1453 b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Maura Carbone > Sent: Tuesday, March 22, 2016 6:56 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] EAC Export Error Hi all, I'm attempting to export some EAC for my agents and I've run into an error on the following export: http://findingaids.brandeis.edu/agents/59?agent_type=agent_person When I attempt to export this within my EAC I get the following error: ASPACE EXPORT ERROR : YOU HAVE A PROBLEM WITH YOUR EXPORT OF YOUR RESOURCE. THE FOLLOWING INFORMATION MAY HELP: undefined method `map' for nil:NilClass ["/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:119:in `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:112:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:111:in `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:109:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:99:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:82:in `_cpfdesc'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:23:in `_eac'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:16:in `_eac'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:7:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:293:in `initialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:6:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:94:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:108:in `generate_eac'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:208:in `ArchivesSpaceService'", "org/jruby/RubyBasicObject.java:1574:in `instance_eval'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:241:in `returns'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:123:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:99:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:122:in `_transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87:in `hold'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:98:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:122:in `open'", "org/jruby/RubyFixnum.java:280:in `times'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:119:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:223:in `returns'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:23:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:207:in `returns'", "org/jruby/RubyMethod.java:116:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1293:in `compile!'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:876:in `route_eval'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:897:in `process_route'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:895:in `process_route'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:859:in `route!'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:858:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:963:in `dispatch!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:960:in `dispatch!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in `call!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in `call!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:780:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:277:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/nulllogger.rb:9:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/head.rb:9:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:124:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1499:in `synchronize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/vendor/rack-1.5.5/rack/builder.rb:138:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:64:in `call'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:49:in `call'", "file:/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/rack/handler/servlet.rb:22:in `call'"] After the bioghist section I get the rest of the EAC. Our bioghist has 3 subnotes (text and 2 citations) none of which come across. Any idea why this is happening? I'm running 1.4.1 so I don't know if this is fixed in 1.4.2. I didn't see a ticket about this when I looked in JIRA but I might have missed it. -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Tue Mar 22 16:53:00 2016 From: mauraa at brandeis.edu (Maura Carbone) Date: Tue, 22 Mar 2016 16:53:00 -0400 Subject: [Archivesspace_Users_Group] EAC Export ErrorY In-Reply-To: References: Message-ID: It all appears to be published but the bioghist text still doesn't show. The tag is generated but the info is left out. On Tue, Mar 22, 2016 at 4:18 PM, Chris Fitzpatrick < Chris.Fitzpatrick at lyrasis.org> wrote: > > Yeah, I think you have to make sure that the note and subnote are > published? Does that work? > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Maura Carbone > *Sent:* Tuesday, March 22, 2016 7:58 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] EAC Export ErrorY > > Filled in the xcode, which removes the error, but just FYI the biog/hist > text still doesn't come through (I get my citation notes but none of the > actual biog note itself). Don't know if that should go on that ticket or on > a new one. > > On Tue, Mar 22, 2016 at 2:29 PM, Chris Fitzpatrick < > Chris.Fitzpatrick at lyrasis.org> wrote: > >> >> >> Yeah, looks like ther exporter assumes there's going to be something the >> Xlink section...if that's empty it causes a problem. >> >> Made a bug ticket here: >> >> https://archivesspace.atlassian.net/browse/AR-1453 >> >> >> >> >> b,chris. >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> >> >> ------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >> Maura Carbone >> *Sent:* Tuesday, March 22, 2016 6:56 PM >> *To:* Archivesspace Users Group >> *Subject:* [Archivesspace_Users_Group] EAC Export Error >> >> Hi all, >> I'm attempting to export some EAC for my agents and I've run into an >> error on the following export: >> http://findingaids.brandeis.edu/agents/59?agent_type=agent_person >> >> When I attempt to export this within my EAC I get the following error: >> >> >> ASPACE EXPORT ERROR : YOU HAVE A PROBLEM >> WITH YOUR EXPORT OF YOUR RESOURCE. THE FOLLOWING INFORMATION MAY HELP: >> >> undefined method `map' for nil:NilClass >> ["/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:119:in >> `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:112:in >> `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in >> `insert'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in >> `method_missing'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in >> `method_missing'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:111:in >> `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:109:in >> `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in >> `insert'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in >> `method_missing'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in >> `method_missing'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:99:in >> `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in >> `insert'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in >> `method_missing'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in >> `method_missing'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:82:in >> `_cpfdesc'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:23:in >> `_eac'", "org/jruby/RubyProc.java:271:in `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in >> `insert'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in >> `method_missing'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in >> `method_missing'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:16:in >> `_eac'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:7:in >> `serialize'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:293:in >> `initialize'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:6:in >> `serialize'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:94:in >> `serialize'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:108:in >> `generate_eac'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:208:in >> `ArchivesSpaceService'", "org/jruby/RubyBasicObject.java:1574:in >> `instance_eval'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:241:in >> `returns'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:123:in >> `open'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:99:in >> `transaction'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in >> `_transaction'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:122:in >> `_transaction'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in >> `transaction'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in >> `hold'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87:in >> `hold'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in >> `synchronize'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in >> `transaction'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:98:in >> `transaction'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:122:in >> `open'", "org/jruby/RubyFixnum.java:280:in `times'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:119:in >> `open'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:223:in >> `returns'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in >> `open'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:23:in >> `open'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:207:in >> `returns'", "org/jruby/RubyMethod.java:116:in `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1293:in >> `compile!'", "org/jruby/RubyProc.java:271:in `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in >> `route!'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:876:in >> `route_eval'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in >> `route!'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:897:in >> `process_route'", "org/jruby/RubyKernel.java:1242:in `catch'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:895:in >> `process_route'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:859:in >> `route!'", "org/jruby/RubyArray.java:1613:in `each'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:858:in >> `route!'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:963:in >> `dispatch!'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in >> `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in >> `invoke'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:960:in >> `dispatch!'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in >> `call!'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in >> `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in >> `invoke'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in >> `call!'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:780:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:277:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/nulllogger.rb:9:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/head.rb:9:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:124:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1499:in >> `synchronize'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/vendor/rack-1.5.5/rack/builder.rb:138:in >> `call'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:64:in >> `call'", "org/jruby/RubyArray.java:1613:in `each'", >> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:49:in >> `call'", >> "file:/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/rack/handler/servlet.rb:22:in >> `call'"] >> >> >> After the bioghist section I get the rest of the EAC. Our bioghist has 3 >> subnotes (text and 2 citations) none of which come across. >> >> Any idea why this is happening? I'm running 1.4.1 so I don't know if this >> is fixed in 1.4.2. I didn't see a ticket about this when I looked in JIRA >> but I might have missed it. >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From dundon at ucsc.edu Tue Mar 22 17:22:43 2016 From: dundon at ucsc.edu (Kate Dundon) Date: Tue, 22 Mar 2016 14:22:43 -0700 Subject: [Archivesspace_Users_Group] User defined values in en.yml file Message-ID: Hi all, We recently migrated to ASpace, and I'd like to edit a few of the user defined fields. According to the documentation , this is done in the en.yml file in the enums folder. But it looks like our file (attached) doesn't contain the same User Defined label options as those outlined in the documentation (below). Would it be possible we have the wrong file? Thanks for any help you can provide! Best, Kate Dundon Archivist, Special Collections & Archives University Library University of California, Santa Cruz 831-502-7587 Our file: user_defined_enum_1: User Defined Enum 1 user_defined_enum_2: User Defined Enum 2 user_defined_enum_3: User Defined Enum 3 user_defined_enum_4: User Defined Enum 4 Documentation: [image: http://docs.archivesspace.org/Content/Resources/Images/UserDefined2a.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ucsc-en.yml Type: application/octet-stream Size: 39555 bytes Desc: not available URL: From brad.westbrook at lyrasis.org Wed Mar 23 08:26:04 2016 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Wed, 23 Mar 2016 12:26:04 +0000 Subject: [Archivesspace_Users_Group] User defined values in en.yml file In-Reply-To: References: Message-ID: Hi, Kate, The documentation you reference is for editing the values on the user controlled value lists, aka enums, as well as all other controlled value lists. The en.yml file in the enums folder contains only the value/translation value lists for all the controlled value lists in the ArchivesSpace application. To establish the names of user defined values or change those of other data fields, you need to edit the en.yml file in the locales folder. Attached is a copy of an locales en.yml file edited per the example in the documentation and reflected in the screen clip below: [cid:image002.jpg at 01D184DD.F3D9C870] We?ll update the documentation so that modifying names / labels, as well as controlled value lists, is represented. Brad From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kate Dundon Sent: Tuesday, March 22, 2016 5:23 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] User defined values in en.yml file Hi all, We recently migrated to ASpace, and I'd like to edit a few of the user defined fields. According to the documentation, this is done in the en.yml file in the enums folder. But it looks like our file (attached) doesn't contain the same User Defined label options as those outlined in the documentation (below). Would it be possible we have the wrong file? Thanks for any help you can provide! Best, Kate Dundon Archivist, Special Collections & Archives University Library University of California, Santa Cruz 831-502-7587 Our file: user_defined_enum_1: User Defined Enum 1 user_defined_enum_2: User Defined Enum 2 user_defined_enum_3: User Defined Enum 3 user_defined_enum_4: User Defined Enum 4 Documentation: [http://docs.archivesspace.org/Content/Resources/Images/UserDefined2a.png] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 26759 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: en.yml Type: application/octet-stream Size: 88502 bytes Desc: en.yml URL: From brianjhoffman at gmail.com Wed Mar 23 11:24:05 2016 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Wed, 23 Mar 2016 11:24:05 -0400 Subject: [Archivesspace_Users_Group] EAC Export ErrorY In-Reply-To: References: Message-ID: <45357652-06AE-4D63-B815-CF82C70B5606@gmail.com> Hi Maura, Is your ?subnote? published too? See pic. Brian > On Mar 22, 2016, at 4:53 PM, Maura Carbone wrote: > > It all appears to be published but the bioghist text still doesn't show. The tag is generated but the info is left out. > > On Tue, Mar 22, 2016 at 4:18 PM, Chris Fitzpatrick > wrote: > > Yeah, I think you have to make sure that the note and subnote are published? Does that work? > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Maura Carbone > > Sent: Tuesday, March 22, 2016 7:58 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] EAC Export ErrorY > > Filled in the xcode, which removes the error, but just FYI the biog/hist text still doesn't come through (I get my citation notes but none of the actual biog note itself). Don't know if that should go on that ticket or on a new one. > > On Tue, Mar 22, 2016 at 2:29 PM, Chris Fitzpatrick > wrote: > > > Yeah, looks like ther exporter assumes there's going to be something the Xlink section...if that's empty it causes a problem. > Made a bug ticket here: > https://archivesspace.atlassian.net/browse/AR-1453 > > > > b,chris. > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Maura Carbone > > Sent: Tuesday, March 22, 2016 6:56 PM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] EAC Export Error > > Hi all, > I'm attempting to export some EAC for my agents and I've run into an error on the following export: > http://findingaids.brandeis.edu/agents/59?agent_type=agent_person > > When I attempt to export this within my EAC I get the following error: > > > ASPACE EXPORT ERROR : YOU HAVE A PROBLEM WITH YOUR EXPORT OF YOUR RESOURCE. THE FOLLOWING INFORMATION MAY HELP: > > undefined method `map' for nil:NilClass > ["/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:119:in `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:112:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:111:in `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:109:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:99:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:82:in `_cpfdesc'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:23:in `_eac'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:16:in `_eac'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:7:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:293:in `initialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:6:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:94:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:108:in `generate_eac'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:208:in `ArchivesSpaceService'", "org/jruby/RubyBasicObject.java:1574:in `instance_eval'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:241:in `returns'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:123:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:99:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:122:in `_transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87:in `hold'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:98:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:122:in `open'", "org/jruby/RubyFixnum.java:280:in `times'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:119:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:223:in `returns'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:23:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:207:in `returns'", "org/jruby/RubyMethod.java:116:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1293:in `compile!'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:876:in `route_eval'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:897:in `process_route'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:895:in `process_route'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:859:in `route!'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:858:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:963:in `dispatch!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:960:in `dispatch!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in `call!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in `call!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:780:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:277:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/nulllogger.rb:9:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/head.rb:9:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:124:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1499:in `synchronize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/vendor/rack-1.5.5/rack/builder.rb:138:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:64:in `call'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:49:in `call'", "file:/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/rack/handler/servlet.rb:22:in `call'"] > > > After the bioghist section I get the rest of the EAC. Our bioghist has 3 subnotes (text and 2 citations) none of which come across. > > Any idea why this is happening? I'm running 1.4.1 so I don't know if this is fixed in 1.4.2. I didn't see a ticket about this when I looked in JIRA but I might have missed it. > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.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: PastedGraphic-1.png Type: image/png Size: 89370 bytes Desc: not available URL: From mauraa at brandeis.edu Wed Mar 23 11:29:57 2016 From: mauraa at brandeis.edu (Maura Carbone) Date: Wed, 23 Mar 2016 11:29:57 -0400 Subject: [Archivesspace_Users_Group] EAC Export ErrorY In-Reply-To: <45357652-06AE-4D63-B815-CF82C70B5606@gmail.com> References: <45357652-06AE-4D63-B815-CF82C70B5606@gmail.com> Message-ID: Yep, they all appear to be checked as published (and can be viewed in the public side). When I fix the xlink issue I actually get the citations in the export, just not the actual text subnote of the bioghist. On Wed, Mar 23, 2016 at 11:24 AM, Brian Hoffman wrote: > Hi Maura, > > Is your ?subnote? published too? See pic. > > > Brian > > On Mar 22, 2016, at 4:53 PM, Maura Carbone wrote: > > It all appears to be published but the bioghist text still doesn't show. > The tag is generated but the info is left out. > > On Tue, Mar 22, 2016 at 4:18 PM, Chris Fitzpatrick < > Chris.Fitzpatrick at lyrasis.org> wrote: > >> >> Yeah, I think you have to make sure that the note and subnote are >> published? Does that work? >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> >> >> ------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >> Maura Carbone >> *Sent:* Tuesday, March 22, 2016 7:58 PM >> *To:* Archivesspace Users Group >> *Subject:* Re: [Archivesspace_Users_Group] EAC Export ErrorY >> >> Filled in the xcode, which removes the error, but just FYI the biog/hist >> text still doesn't come through (I get my citation notes but none of the >> actual biog note itself). Don't know if that should go on that ticket or on >> a new one. >> >> On Tue, Mar 22, 2016 at 2:29 PM, Chris Fitzpatrick < >> Chris.Fitzpatrick at lyrasis.org> wrote: >> >>> >>> >>> Yeah, looks like ther exporter assumes there's going to be something the >>> Xlink section...if that's empty it causes a problem. >>> >>> Made a bug ticket here: >>> >>> https://archivesspace.atlassian.net/browse/AR-1453 >>> >>> >>> >>> >>> b,chris. >>> >>> >>> Chris Fitzpatrick | Developer, ArchivesSpace >>> Skype: chrisfitzpat | Phone: 918.236.6048 >>> http://archivesspace.org/ >>> >>> >>> ------------------------------ >>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >>> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >>> Maura Carbone >>> *Sent:* Tuesday, March 22, 2016 6:56 PM >>> *To:* Archivesspace Users Group >>> *Subject:* [Archivesspace_Users_Group] EAC Export Error >>> >>> Hi all, >>> I'm attempting to export some EAC for my agents and I've run into an >>> error on the following export: >>> http://findingaids.brandeis.edu/agents/59?agent_type=agent_person >>> >>> When I attempt to export this within my EAC I get the following error: >>> >>> >>> ASPACE EXPORT ERROR : YOU HAVE A PROBLEM >>> WITH YOUR EXPORT OF YOUR RESOURCE. THE FOLLOWING INFORMATION MAY HELP: >>> >>> undefined method `map' for nil:NilClass >>> ["/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:119:in >>> `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:112:in >>> `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in >>> `insert'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in >>> `method_missing'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in >>> `method_missing'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:111:in >>> `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:109:in >>> `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in >>> `insert'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in >>> `method_missing'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in >>> `method_missing'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:99:in >>> `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in >>> `insert'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in >>> `method_missing'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in >>> `method_missing'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:82:in >>> `_cpfdesc'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:23:in >>> `_eac'", "org/jruby/RubyProc.java:271:in `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in >>> `insert'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in >>> `method_missing'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in >>> `method_missing'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:16:in >>> `_eac'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:7:in >>> `serialize'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:293:in >>> `initialize'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:6:in >>> `serialize'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:94:in >>> `serialize'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:108:in >>> `generate_eac'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:208:in >>> `ArchivesSpaceService'", "org/jruby/RubyBasicObject.java:1574:in >>> `instance_eval'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:241:in >>> `returns'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:123:in >>> `open'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:99:in >>> `transaction'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in >>> `_transaction'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:122:in >>> `_transaction'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in >>> `transaction'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in >>> `hold'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87:in >>> `hold'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in >>> `synchronize'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in >>> `transaction'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:98:in >>> `transaction'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:122:in >>> `open'", "org/jruby/RubyFixnum.java:280:in `times'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:119:in >>> `open'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:223:in >>> `returns'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in >>> `open'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:23:in >>> `open'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:207:in >>> `returns'", "org/jruby/RubyMethod.java:116:in `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1293:in >>> `compile!'", "org/jruby/RubyProc.java:271:in `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in >>> `route!'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:876:in >>> `route_eval'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in >>> `route!'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:897:in >>> `process_route'", "org/jruby/RubyKernel.java:1242:in `catch'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:895:in >>> `process_route'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:859:in >>> `route!'", "org/jruby/RubyArray.java:1613:in `each'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:858:in >>> `route!'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:963:in >>> `dispatch!'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in >>> `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in >>> `invoke'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:960:in >>> `dispatch!'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in >>> `call!'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in >>> `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in >>> `invoke'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in >>> `call!'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:780:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:277:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/nulllogger.rb:9:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/head.rb:9:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:124:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1499:in >>> `synchronize'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/vendor/rack-1.5.5/rack/builder.rb:138:in >>> `call'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:64:in >>> `call'", "org/jruby/RubyArray.java:1613:in `each'", >>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:49:in >>> `call'", >>> "file:/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/rack/handler/servlet.rb:22:in >>> `call'"] >>> >>> >>> After the bioghist section I get the rest of the EAC. Our bioghist has 3 >>> subnotes (text and 2 citations) none of which come across. >>> >>> Any idea why this is happening? I'm running 1.4.1 so I don't know if >>> this is fixed in 1.4.2. I didn't see a ticket about this when I looked in >>> JIRA but I might have missed it. >>> -- >>> Maura Carbone >>> Digital Initiatives Librarian >>> Brandeis University >>> Library and Technology Services >>> (781) 736-4659 >>> 415 South Street, (MS 017/P.O. Box 549110) >>> Waltham, MA 02454-9110 >>> email: mauraa at brandeis.edu >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >> >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-1.png Type: image/png Size: 89370 bytes Desc: not available URL: From brianjhoffman at gmail.com Wed Mar 23 12:08:46 2016 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Wed, 23 Mar 2016 12:08:46 -0400 Subject: [Archivesspace_Users_Group] EAC Export ErrorY In-Reply-To: References: <45357652-06AE-4D63-B815-CF82C70B5606@gmail.com> Message-ID: Well, this is probably just a bug then. I don?t think the EAC export has gotten much exercise so it?s not surprising. Do you want to file something in JIRA? Brian > On Mar 23, 2016, at 11:29 AM, Maura Carbone wrote: > > Yep, they all appear to be checked as published (and can be viewed in the public side). When I fix the xlink issue I actually get the citations in the export, just not the actual text subnote of the bioghist. > > On Wed, Mar 23, 2016 at 11:24 AM, Brian Hoffman > wrote: > Hi Maura, > > Is your ?subnote? published too? See pic. > > > > Brian > >> On Mar 22, 2016, at 4:53 PM, Maura Carbone > wrote: >> >> It all appears to be published but the bioghist text still doesn't show. The tag is generated but the info is left out. >> >> On Tue, Mar 22, 2016 at 4:18 PM, Chris Fitzpatrick > wrote: >> >> Yeah, I think you have to make sure that the note and subnote are published? Does that work? >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> >> >> From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Maura Carbone > >> Sent: Tuesday, March 22, 2016 7:58 PM >> To: Archivesspace Users Group >> Subject: Re: [Archivesspace_Users_Group] EAC Export ErrorY >> >> Filled in the xcode, which removes the error, but just FYI the biog/hist text still doesn't come through (I get my citation notes but none of the actual biog note itself). Don't know if that should go on that ticket or on a new one. >> >> On Tue, Mar 22, 2016 at 2:29 PM, Chris Fitzpatrick > wrote: >> >> >> Yeah, looks like ther exporter assumes there's going to be something the Xlink section...if that's empty it causes a problem. >> Made a bug ticket here: >> https://archivesspace.atlassian.net/browse/AR-1453 >> >> >> >> b,chris. >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> >> >> From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Maura Carbone > >> Sent: Tuesday, March 22, 2016 6:56 PM >> To: Archivesspace Users Group >> Subject: [Archivesspace_Users_Group] EAC Export Error >> >> Hi all, >> I'm attempting to export some EAC for my agents and I've run into an error on the following export: >> http://findingaids.brandeis.edu/agents/59?agent_type=agent_person >> >> When I attempt to export this within my EAC I get the following error: >> >> >> ASPACE EXPORT ERROR : YOU HAVE A PROBLEM WITH YOUR EXPORT OF YOUR RESOURCE. THE FOLLOWING INFORMATION MAY HELP: >> >> undefined method `map' for nil:NilClass >> ["/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:119:in `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:112:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:111:in `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:109:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:99:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:82:in `_cpfdesc'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:23:in `_eac'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:16:in `_eac'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:7:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:293:in `initialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:6:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:94:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:108:in `generate_eac'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:208:in `ArchivesSpaceService'", "org/jruby/RubyBasicObject.java:1574:in `instance_eval'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:241:in `returns'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:123:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:99:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:122:in `_transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87:in `hold'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:98:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:122:in `open'", "org/jruby/RubyFixnum.java:280:in `times'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:119:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:223:in `returns'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:23:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:207:in `returns'", "org/jruby/RubyMethod.java:116:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1293:in `compile!'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:876:in `route_eval'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:897:in `process_route'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:895:in `process_route'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:859:in `route!'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:858:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:963:in `dispatch!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:960:in `dispatch!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in `call!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in `call!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:780:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:277:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/nulllogger.rb:9:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/head.rb:9:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:124:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1499:in `synchronize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/vendor/rack-1.5.5/rack/builder.rb:138:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:64:in `call'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:49:in `call'", "file:/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/rack/handler/servlet.rb:22:in `call'"] >> >> >> After the bioghist section I get the rest of the EAC. Our bioghist has 3 subnotes (text and 2 citations) none of which come across. >> >> Any idea why this is happening? I'm running 1.4.1 so I don't know if this is fixed in 1.4.2. I didn't see a ticket about this when I looked in JIRA but I might have missed it. >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Wed Mar 23 12:09:45 2016 From: mauraa at brandeis.edu (Maura Carbone) Date: Wed, 23 Mar 2016 12:09:45 -0400 Subject: [Archivesspace_Users_Group] EAC Export ErrorY In-Reply-To: References: <45357652-06AE-4D63-B815-CF82C70B5606@gmail.com> Message-ID: Yeah I just wasn't sure if you wanted it separate from the bug report about requiring the optional xlink? On Wed, Mar 23, 2016 at 12:08 PM, Brian Hoffman wrote: > Well, this is probably just a bug then. I don?t think the EAC export has > gotten much exercise so it?s not surprising. Do you want to file something > in JIRA? > > Brian > > > On Mar 23, 2016, at 11:29 AM, Maura Carbone wrote: > > Yep, they all appear to be checked as published (and can be viewed in the > public side). When I fix the xlink issue I actually get the citations in > the export, just not the actual text subnote of the bioghist. > > On Wed, Mar 23, 2016 at 11:24 AM, Brian Hoffman > wrote: > >> Hi Maura, >> >> Is your ?subnote? published too? See pic. >> >> >> >> Brian >> >> On Mar 22, 2016, at 4:53 PM, Maura Carbone wrote: >> >> It all appears to be published but the bioghist text still doesn't show. >> The tag is generated but the info is left out. >> >> On Tue, Mar 22, 2016 at 4:18 PM, Chris Fitzpatrick < >> Chris.Fitzpatrick at lyrasis.org> wrote: >> >>> >>> Yeah, I think you have to make sure that the note and subnote are >>> published? Does that work? >>> >>> >>> Chris Fitzpatrick | Developer, ArchivesSpace >>> Skype: chrisfitzpat | Phone: 918.236.6048 >>> http://archivesspace.org/ >>> >>> >>> ------------------------------ >>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >>> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >>> Maura Carbone >>> *Sent:* Tuesday, March 22, 2016 7:58 PM >>> *To:* Archivesspace Users Group >>> *Subject:* Re: [Archivesspace_Users_Group] EAC Export ErrorY >>> >>> Filled in the xcode, which removes the error, but just FYI the biog/hist >>> text still doesn't come through (I get my citation notes but none of the >>> actual biog note itself). Don't know if that should go on that ticket or on >>> a new one. >>> >>> On Tue, Mar 22, 2016 at 2:29 PM, Chris Fitzpatrick < >>> Chris.Fitzpatrick at lyrasis.org> wrote: >>> >>>> >>>> >>>> Yeah, looks like ther exporter assumes there's going to be something >>>> the Xlink section...if that's empty it causes a problem. >>>> >>>> Made a bug ticket here: >>>> >>>> https://archivesspace.atlassian.net/browse/AR-1453 >>>> >>>> >>>> >>>> >>>> b,chris. >>>> >>>> >>>> Chris Fitzpatrick | Developer, ArchivesSpace >>>> Skype: chrisfitzpat | Phone: 918.236.6048 >>>> http://archivesspace.org/ >>>> >>>> >>>> ------------------------------ >>>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >>>> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >>>> Maura Carbone >>>> *Sent:* Tuesday, March 22, 2016 6:56 PM >>>> *To:* Archivesspace Users Group >>>> *Subject:* [Archivesspace_Users_Group] EAC Export Error >>>> >>>> Hi all, >>>> I'm attempting to export some EAC for my agents and I've run into an >>>> error on the following export: >>>> http://findingaids.brandeis.edu/agents/59?agent_type=agent_person >>>> >>>> When I attempt to export this within my EAC I get the following error: >>>> >>>> >>>> ASPACE EXPORT ERROR : YOU HAVE A PROBLEM >>>> WITH YOUR EXPORT OF YOUR RESOURCE. THE FOLLOWING INFORMATION MAY HELP: >>>> >>>> undefined method `map' for nil:NilClass >>>> ["/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:119:in >>>> `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:112:in >>>> `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in >>>> `insert'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in >>>> `method_missing'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in >>>> `method_missing'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:111:in >>>> `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:109:in >>>> `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in >>>> `insert'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in >>>> `method_missing'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in >>>> `method_missing'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:99:in >>>> `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in >>>> `insert'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in >>>> `method_missing'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in >>>> `method_missing'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:82:in >>>> `_cpfdesc'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:23:in >>>> `_eac'", "org/jruby/RubyProc.java:271:in `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in >>>> `insert'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in >>>> `method_missing'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in >>>> `method_missing'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:16:in >>>> `_eac'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:7:in >>>> `serialize'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:293:in >>>> `initialize'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:6:in >>>> `serialize'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:94:in >>>> `serialize'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:108:in >>>> `generate_eac'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:208:in >>>> `ArchivesSpaceService'", "org/jruby/RubyBasicObject.java:1574:in >>>> `instance_eval'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:241:in >>>> `returns'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:123:in >>>> `open'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:99:in >>>> `transaction'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in >>>> `_transaction'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:122:in >>>> `_transaction'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in >>>> `transaction'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in >>>> `hold'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87:in >>>> `hold'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in >>>> `synchronize'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in >>>> `transaction'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:98:in >>>> `transaction'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:122:in >>>> `open'", "org/jruby/RubyFixnum.java:280:in `times'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:119:in >>>> `open'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:223:in >>>> `returns'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in >>>> `open'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:23:in >>>> `open'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:207:in >>>> `returns'", "org/jruby/RubyMethod.java:116:in `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1293:in >>>> `compile!'", "org/jruby/RubyProc.java:271:in `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in >>>> `route!'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:876:in >>>> `route_eval'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in >>>> `route!'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:897:in >>>> `process_route'", "org/jruby/RubyKernel.java:1242:in `catch'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:895:in >>>> `process_route'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:859:in >>>> `route!'", "org/jruby/RubyArray.java:1613:in `each'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:858:in >>>> `route!'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:963:in >>>> `dispatch!'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in >>>> `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in >>>> `invoke'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:960:in >>>> `dispatch!'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in >>>> `call!'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in >>>> `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in >>>> `invoke'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in >>>> `call!'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:780:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:277:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/nulllogger.rb:9:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/head.rb:9:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:124:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1499:in >>>> `synchronize'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/vendor/rack-1.5.5/rack/builder.rb:138:in >>>> `call'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:64:in >>>> `call'", "org/jruby/RubyArray.java:1613:in `each'", >>>> "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:49:in >>>> `call'", >>>> "file:/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/rack/handler/servlet.rb:22:in >>>> `call'"] >>>> >>>> >>>> After the bioghist section I get the rest of the EAC. Our bioghist has >>>> 3 subnotes (text and 2 citations) none of which come across. >>>> >>>> Any idea why this is happening? I'm running 1.4.1 so I don't know if >>>> this is fixed in 1.4.2. I didn't see a ticket about this when I looked in >>>> JIRA but I might have missed it. >>>> -- >>>> Maura Carbone >>>> Digital Initiatives Librarian >>>> Brandeis University >>>> Library and Technology Services >>>> (781) 736-4659 >>>> 415 South Street, (MS 017/P.O. Box 549110) >>>> Waltham, MA 02454-9110 >>>> email: mauraa at brandeis.edu >>>> >>>> _______________________________________________ >>>> Archivesspace_Users_Group mailing list >>>> Archivesspace_Users_Group at lyralists.lyrasis.org >>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>>> >>>> >>> >>> >>> -- >>> Maura Carbone >>> Digital Initiatives Librarian >>> Brandeis University >>> Library and Technology Services >>> (781) 736-4659 >>> 415 South Street, (MS 017/P.O. Box 549110) >>> Waltham, MA 02454-9110 >>> email: mauraa at brandeis.edu >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >> >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianjhoffman at gmail.com Wed Mar 23 12:35:53 2016 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Wed, 23 Mar 2016 12:35:53 -0400 Subject: [Archivesspace_Users_Group] EAC Export ErrorY In-Reply-To: References: <45357652-06AE-4D63-B815-CF82C70B5606@gmail.com> Message-ID: <6EF29957-E10D-4299-9036-F0D4A9128F94@gmail.com> If it?s doable, the ideal thing would probably be a single report with: - an EAD that can be imported to create sample data. - an EAC showing how the export should look. or if that?s not doable, a text description of the whole problem would probably be fine. Brian > On Mar 23, 2016, at 12:09 PM, Maura Carbone wrote: > > Yeah I just wasn't sure if you wanted it separate from the bug report about requiring the optional xlink? > > On Wed, Mar 23, 2016 at 12:08 PM, Brian Hoffman > wrote: > Well, this is probably just a bug then. I don?t think the EAC export has gotten much exercise so it?s not surprising. Do you want to file something in JIRA? > > Brian > > >> On Mar 23, 2016, at 11:29 AM, Maura Carbone > wrote: >> >> Yep, they all appear to be checked as published (and can be viewed in the public side). When I fix the xlink issue I actually get the citations in the export, just not the actual text subnote of the bioghist. >> >> On Wed, Mar 23, 2016 at 11:24 AM, Brian Hoffman > wrote: >> Hi Maura, >> >> Is your ?subnote? published too? See pic. >> >> >> >> Brian >> >>> On Mar 22, 2016, at 4:53 PM, Maura Carbone > wrote: >>> >>> It all appears to be published but the bioghist text still doesn't show. The tag is generated but the info is left out. >>> >>> On Tue, Mar 22, 2016 at 4:18 PM, Chris Fitzpatrick > wrote: >>> >>> Yeah, I think you have to make sure that the note and subnote are published? Does that work? >>> >>> Chris Fitzpatrick | Developer, ArchivesSpace >>> Skype: chrisfitzpat | Phone: 918.236.6048 >>> http://archivesspace.org/ >>> >>> >>> From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Maura Carbone > >>> Sent: Tuesday, March 22, 2016 7:58 PM >>> To: Archivesspace Users Group >>> Subject: Re: [Archivesspace_Users_Group] EAC Export ErrorY >>> >>> Filled in the xcode, which removes the error, but just FYI the biog/hist text still doesn't come through (I get my citation notes but none of the actual biog note itself). Don't know if that should go on that ticket or on a new one. >>> >>> On Tue, Mar 22, 2016 at 2:29 PM, Chris Fitzpatrick > wrote: >>> >>> >>> Yeah, looks like ther exporter assumes there's going to be something the Xlink section...if that's empty it causes a problem. >>> Made a bug ticket here: >>> https://archivesspace.atlassian.net/browse/AR-1453 >>> >>> >>> >>> b,chris. >>> >>> Chris Fitzpatrick | Developer, ArchivesSpace >>> Skype: chrisfitzpat | Phone: 918.236.6048 >>> http://archivesspace.org/ >>> >>> >>> From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Maura Carbone > >>> Sent: Tuesday, March 22, 2016 6:56 PM >>> To: Archivesspace Users Group >>> Subject: [Archivesspace_Users_Group] EAC Export Error >>> >>> Hi all, >>> I'm attempting to export some EAC for my agents and I've run into an error on the following export: >>> http://findingaids.brandeis.edu/agents/59?agent_type=agent_person >>> >>> When I attempt to export this within my EAC I get the following error: >>> >>> >>> ASPACE EXPORT ERROR : YOU HAVE A PROBLEM WITH YOUR EXPORT OF YOUR RESOURCE. THE FOLLOWING INFORMATION MAY HELP: >>> >>> undefined method `map' for nil:NilClass >>> ["/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:119:in `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:112:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:111:in `_cpfdesc'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:109:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:99:in `_cpfdesc'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:82:in `_cpfdesc'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:23:in `_eac'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:391:in `insert'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:375:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:177:in `method_missing'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:16:in `_eac'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:7:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/nokogiri-1.6.6.2-java/lib/nokogiri/xml/builder.rb:293:in `initialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/serializers/eac.rb:6:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/exporters/lib/exporter.rb:94:in `serialize'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/export.rb:108:in `generate_eac'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/controllers/exports.rb:208:in `ArchivesSpaceService'", "org/jruby/RubyBasicObject.java:1574:in `instance_eval'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:241:in `returns'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:123:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:99:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134:in `_transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:122:in `_transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98:in `hold'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87:in `hold'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255:in `synchronize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:98:in `transaction'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:122:in `open'", "org/jruby/RubyFixnum.java:280:in `times'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:119:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:223:in `returns'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:23:in `open'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/rest.rb:207:in `returns'", "org/jruby/RubyMethod.java:116:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1293:in `compile!'", "org/jruby/RubyProc.java:271:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:876:in `route_eval'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:860:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:897:in `process_route'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:895:in `process_route'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:859:in `route!'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:858:in `route!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:963:in `dispatch!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:960:in `dispatch!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in `call!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "org/jruby/RubyKernel.java:1242:in `catch'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:946:in `invoke'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:794:in `call!'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:780:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:277:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/xss_header.rb:18:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/path_traversal.rb:16:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/json_csrf.rb:18:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/base.rb:49:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/nulllogger.rb:9:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/head.rb:9:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:124:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1499:in `synchronize'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/sinatra-1.3.6/lib/sinatra/base.rb:1417:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/vendor/rack-1.5.5/rack/builder.rb:138:in `call'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:64:in `call'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/rack-1.4.7/lib/rack/urlmap.rb:49:in `call'", "file:/usr/local/archivesspace-v1.4.1/archivesspace/gems/gems/jruby-rack-1.1.19/lib/jruby-rack-1.1.19.jar!/rack/handler/servlet.rb:22:in `call'"] >>> >>> >>> After the bioghist section I get the rest of the EAC. Our bioghist has 3 subnotes (text and 2 citations) none of which come across. >>> >>> Any idea why this is happening? I'm running 1.4.1 so I don't know if this is fixed in 1.4.2. I didn't see a ticket about this when I looked in JIRA but I might have missed it. >>> -- >>> Maura Carbone >>> Digital Initiatives Librarian >>> Brandeis University >>> Library and Technology Services >>> (781) 736-4659 >>> 415 South Street, (MS 017/P.O. Box 549110) >>> Waltham, MA 02454-9110 >>> email: mauraa at brandeis.edu >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> >>> >>> -- >>> Maura Carbone >>> Digital Initiatives Librarian >>> Brandeis University >>> Library and Technology Services >>> (781) 736-4659 >>> 415 South Street, (MS 017/P.O. Box 549110) >>> Waltham, MA 02454-9110 >>> email: mauraa at brandeis.edu >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> >>> >>> -- >>> Maura Carbone >>> Digital Initiatives Librarian >>> Brandeis University >>> Library and Technology Services >>> (781) 736-4659 >>> 415 South Street, (MS 017/P.O. Box 549110) >>> Waltham, MA 02454-9110 >>> email: mauraa at brandeis.edu >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From dundon at ucsc.edu Wed Mar 23 17:06:30 2016 From: dundon at ucsc.edu (Kate Dundon) Date: Wed, 23 Mar 2016 14:06:30 -0700 Subject: [Archivesspace_Users_Group] User defined values in en.yml file In-Reply-To: References: Message-ID: Thank you Brad! Kate Dundon Archivist, Special Collections & Archives University Library University of California, Santa Cruz 831-502-7587 On Wed, Mar 23, 2016 at 5:26 AM, Brad Westbrook wrote: > Hi, Kate, > > > > The documentation you reference is for editing the values on the user > controlled value lists, aka enums, as well as all other controlled value > lists. The en.yml file in the enums folder contains only the > value/translation value lists for all the controlled value lists in the > ArchivesSpace application. > > > > To establish the names of user defined values or change those of other > data fields, you need to edit the en.yml file in the locales folder. > Attached is a copy of an locales en.yml file edited per the example in the > documentation and reflected in the screen clip below: > > > > > > > > We?ll update the documentation so that modifying names / labels, as well > as controlled value lists, is represented. > > > > Brad > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Kate > Dundon > *Sent:* Tuesday, March 22, 2016 5:23 PM > *To:* Archivesspace Users Group > *Subject:* [Archivesspace_Users_Group] User defined values in en.yml file > > > > Hi all, > > We recently migrated to ASpace, and I'd like to edit a few of the user > defined fields. According to the documentation > , > this is done in the en.yml file in the enums folder. But it looks like our > file (attached) doesn't contain the same User Defined label options as > those outlined in the documentation (below). Would it be possible we have > the wrong file? > > Thanks for any help you can provide! > > Best, > > Kate Dundon > Archivist, Special Collections & Archives > > University Library > > University of California, Santa Cruz > 831-502-7587 > > > > Our file: > user_defined_enum_1: User Defined Enum 1 > user_defined_enum_2: User Defined Enum 2 > user_defined_enum_3: User Defined Enum 3 > user_defined_enum_4: User Defined Enum 4 > > > > Documentation: > [image: > http://docs.archivesspace.org/Content/Resources/Images/UserDefined2a.png] > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 26759 bytes Desc: not available URL: From esha at nyu.edu Thu Mar 24 15:57:31 2016 From: esha at nyu.edu (Esha Datta) Date: Thu, 24 Mar 2016 15:57:31 -0400 Subject: [Archivesspace_Users_Group] running individual rspec tests Message-ID: Hello, Thanks to all of those who have helped me so far along the road to plugin development. The time now has come to write tests for the plugin. I noticed that in the dev instance I can specify which part of the application to test, for example: the backend, frontend, common, or all. Is there a way to run just one test or one suite of tests from the plugin? I'd like to have both options if possible. That way, when I'm checking on the tests, I don't have to wait for the backend tests to run every time. Thanks in advance for your help! In MRI rails projects, I've managed to just do rspec spec/dir/whatever_suite_of_tests and if I want to specify a line or something: rspec spec/dir/whatever_suite_of_tests:line number, can I try something like this in archivesspace? I tried reading through the build.xml, specifically, the backend:test part but I wasn't really getting how to specify a plugin test...I see that I runs through all the backend tests. Thanks. Esha Esha Datta NYU Libraries -------------- next part -------------- An HTML attachment was scrubbed... URL: From james at hudmol.com Thu Mar 24 20:27:23 2016 From: james at hudmol.com (James Bullen) Date: Fri, 25 Mar 2016 11:27:23 +1100 Subject: [Archivesspace_Users_Group] running individual rspec tests In-Reply-To: References: Message-ID: <3DAA49CA-75BC-4C60-BE5F-116EA48E78B1@hudmol.com> Hi Esha, You can say something like this: build/run backend:test -Dexample="User model can yield a list of all permissions? To run a single test, or just ?User model? to run all of the user model tests. It actually just does a match, so you could say: build/run backend:test -Dexample="permissions? And it would run any test it finds with ?permissions? its description. A test?s full description is a concat of the ?describe' blocks and ?it' block it is contained in, so in the top example, it?s spec looks like this: describe 'User model' do ? it "can yield a list of all permissions" do ? end ? end There is also a way to run only a specific _spec.rb file, but I can?t remember what it is. ;) Hope that helps. Cheers, James > On Mar 25, 2016, at 6:57 AM, Esha Datta wrote: > > Hello, > > Thanks to all of those who have helped me so far along the road to plugin development. The time now has come to write tests for the plugin. I noticed that in the dev instance I can specify which part of the application to test, for example: the backend, frontend, common, or all. Is there a way to run just one test or one suite of tests from the plugin? I'd like to have both options if possible. That way, when I'm checking on the tests, I don't have to wait for the backend tests to run every time. Thanks in advance for your help! > > In MRI rails projects, I've managed to just do rspec spec/dir/whatever_suite_of_tests and if I want to specify a line or something: rspec spec/dir/whatever_suite_of_tests:line number, can I try something like this in archivesspace? > > I tried reading through the build.xml, specifically, the backend:test part but I wasn't really getting how to specify a plugin test...I see that I runs through all the backend tests. > > Thanks. > > Esha > > Esha Datta > NYU Libraries > !DSPAM:56f446ce244601971738366! _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:56f446ce244601971738366! -------------- next part -------------- An HTML attachment was scrubbed... URL: From sustasiula at pa.gov Fri Mar 25 14:49:21 2016 From: sustasiula at pa.gov (Stasiulatis, Suzanne) Date: Fri, 25 Mar 2016 18:49:21 +0000 Subject: [Archivesspace_Users_Group] Batch Find and Replace Message-ID: <09f233c25bba4fca9eb7478e65f4568c@ENCTCEXCH008.PA.LCL> Hello! I'm looking for some additional information/instructions on using the beta Batch Find and Replace. Can anyone point me in the right direction? Thanks in advance, Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 Phone: 717-787-5953 http://www.phmc.pa.gov sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Sun Mar 27 16:54:50 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Sun, 27 Mar 2016 20:54:50 +0000 Subject: [Archivesspace_Users_Group] Batch Find and Replace In-Reply-To: <09f233c25bba4fca9eb7478e65f4568c@ENCTCEXCH008.PA.LCL> References: <09f233c25bba4fca9eb7478e65f4568c@ENCTCEXCH008.PA.LCL> Message-ID: Hi Suzanne, I'm not sure if there's any documentation for this, as it was kind of a "Beta" feature. Do you have any specific questions about it? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Stasiulatis, Suzanne Sent: Friday, March 25, 2016 7:49 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Batch Find and Replace Hello! I'm looking for some additional information/instructions on using the beta Batch Find and Replace. Can anyone point me in the right direction? Thanks in advance, Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 Phone: 717-787-5953 http://www.phmc.pa.gov Pennsylvania Historical and Museum Commission www.phmc.pa.gov The Pennsylvania Historical and Museum Commission (PHMC) is the official history agency of the Commonwealth of Pennsylvania. Created in 1945, we are responsible for ... sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From sustasiula at pa.gov Mon Mar 28 08:22:41 2016 From: sustasiula at pa.gov (Stasiulatis, Suzanne) Date: Mon, 28 Mar 2016 12:22:41 +0000 Subject: [Archivesspace_Users_Group] Batch Find and Replace In-Reply-To: References: <09f233c25bba4fca9eb7478e65f4568c@ENCTCEXCH008.PA.LCL> Message-ID: <4bec6a4bfdb84cb8b9786f2be6045109@ENCTCEXCH008.PA.LCL> Hello: I've tried to run the batch find and replace multiple ways. I always get the message "All done, no records modified." Any suggestions? Also - Can you populate a field that's not already populated via batch find and replace? Thanks, Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 Phone: 717-787-5953 http://www.phmc.pa.gov sustasiula at pa.gov From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Sunday, March 27, 2016 4:55 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Batch Find and Replace Hi Suzanne, I'm not sure if there's any documentation for this, as it was kind of a "Beta" feature. Do you have any specific questions about it? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Stasiulatis, Suzanne > Sent: Friday, March 25, 2016 7:49 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Batch Find and Replace Hello! I'm looking for some additional information/instructions on using the beta Batch Find and Replace. Can anyone point me in the right direction? Thanks in advance, Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 Phone: 717-787-5953 http://www.phmc.pa.gov Pennsylvania Historical and Museum Commission www.phmc.pa.gov The Pennsylvania Historical and Museum Commission (PHMC) is the official history agency of the Commonwealth of Pennsylvania. Created in 1945, we are responsible for ... sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Mon Mar 28 09:20:22 2016 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Mon, 28 Mar 2016 13:20:22 +0000 Subject: [Archivesspace_Users_Group] Batch Find and Replace In-Reply-To: <4bec6a4bfdb84cb8b9786f2be6045109@ENCTCEXCH008.PA.LCL> References: <09f233c25bba4fca9eb7478e65f4568c@ENCTCEXCH008.PA.LCL> <4bec6a4bfdb84cb8b9786f2be6045109@ENCTCEXCH008.PA.LCL> Message-ID: Hi Suzanne, The batch find and replace is limited to a single resource, and only a small set of fields - Resource Component Title, Ref ID, Component Unique Identifier, Other Level, or Repository Processing Note; Extent Number, Container Summary, Physical Details, or Dimensions; or Date Expression, Begin, or End - within a resource. In its beta state, I think it's primarily useful for changing text in resource component titles, but there may be others that are using the other options. It cannot be used to populate a field that's not already populated. If you are trying to find and replace text that's not there, or that only appears in fields other than the ones specified, you will get the "All done, no records modified" message. Does that help explain the results that you're seeing for the things you've tried? Christine Christine Di Bella Community Outreach and Support Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [cid:image003.png at 01CE734E.FD759D30] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne Sent: Monday, March 28, 2016 8:23 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Batch Find and Replace Hello: I've tried to run the batch find and replace multiple ways. I always get the message "All done, no records modified." Any suggestions? Also - Can you populate a field that's not already populated via batch find and replace? Thanks, Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 Phone: 717-787-5953 http://www.phmc.pa.gov sustasiula at pa.gov From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Sunday, March 27, 2016 4:55 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Batch Find and Replace Hi Suzanne, I'm not sure if there's any documentation for this, as it was kind of a "Beta" feature. Do you have any specific questions about it? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Stasiulatis, Suzanne > Sent: Friday, March 25, 2016 7:49 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Batch Find and Replace Hello! I'm looking for some additional information/instructions on using the beta Batch Find and Replace. Can anyone point me in the right direction? Thanks in advance, Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 Phone: 717-787-5953 http://www.phmc.pa.gov Pennsylvania Historical and Museum Commission www.phmc.pa.gov The Pennsylvania Historical and Museum Commission (PHMC) is the official history agency of the Commonwealth of Pennsylvania. Created in 1945, we are responsible for ... sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7645 bytes Desc: image001.png URL: From sustasiula at pa.gov Mon Mar 28 09:25:34 2016 From: sustasiula at pa.gov (Stasiulatis, Suzanne) Date: Mon, 28 Mar 2016 13:25:34 +0000 Subject: [Archivesspace_Users_Group] Batch Find and Replace In-Reply-To: References: <09f233c25bba4fca9eb7478e65f4568c@ENCTCEXCH008.PA.LCL> <4bec6a4bfdb84cb8b9786f2be6045109@ENCTCEXCH008.PA.LCL> Message-ID: Yes. Thank you for clarifying the limits Christine. I did also try to find and replace textual information. Unfortunately, I got the same error message no matter what I tried. Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 Phone: 717-787-5953 http://www.phmc.pa.gov sustasiula at pa.gov 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: Monday, March 28, 2016 9:20 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Batch Find and Replace Hi Suzanne, The batch find and replace is limited to a single resource, and only a small set of fields - Resource Component Title, Ref ID, Component Unique Identifier, Other Level, or Repository Processing Note; Extent Number, Container Summary, Physical Details, or Dimensions; or Date Expression, Begin, or End - within a resource. In its beta state, I think it's primarily useful for changing text in resource component titles, but there may be others that are using the other options. It cannot be used to populate a field that's not already populated. If you are trying to find and replace text that's not there, or that only appears in fields other than the ones specified, you will get the "All done, no records modified" message. Does that help explain the results that you're seeing for the things you've tried? Christine Christine Di Bella Community Outreach and Support Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [cid:image003.png at 01CE734E.FD759D30] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stasiulatis, Suzanne Sent: Monday, March 28, 2016 8:23 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Batch Find and Replace Hello: I've tried to run the batch find and replace multiple ways. I always get the message "All done, no records modified." Any suggestions? Also - Can you populate a field that's not already populated via batch find and replace? Thanks, Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 Phone: 717-787-5953 http://www.phmc.pa.gov sustasiula at pa.gov From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Sunday, March 27, 2016 4:55 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Batch Find and Replace Hi Suzanne, I'm not sure if there's any documentation for this, as it was kind of a "Beta" feature. Do you have any specific questions about it? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Stasiulatis, Suzanne > Sent: Friday, March 25, 2016 7:49 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Batch Find and Replace Hello! I'm looking for some additional information/instructions on using the beta Batch Find and Replace. Can anyone point me in the right direction? Thanks in advance, Suzanne Suzanne Stasiulatis | Archivist II Pennsylvania Historical and Museum Commission | Pennsylvania State Archives 350 North Street | Harrisburg, PA 17120-0090 Phone: 717-787-5953 http://www.phmc.pa.gov Pennsylvania Historical and Museum Commission www.phmc.pa.gov The Pennsylvania Historical and Museum Commission (PHMC) is the official history agency of the Commonwealth of Pennsylvania. Created in 1945, we are responsible for ... sustasiula at pa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7645 bytes Desc: image001.png URL: From kate_bowers at harvard.edu Mon Mar 28 11:32:42 2016 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Mon, 28 Mar 2016 15:32:42 +0000 Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? In-Reply-To: References: , , , , Message-ID: On March 14, 2016 Chris Fitzpatrick wrote: ?Great. So, does everyone agree we can mark AR-1270 as Accepted? Or is there some outstanding issue?? And I responded later that day: ?Something broke...? Is there any information on where this fix now stands? I?ve just added a comment replicating my email about what was broken and attached the test file I used to find the broken bit here: https://archivesspace.atlassian.net/browse/AR-1270 Thanks! Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 998-5238 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers 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: Monday, March 14, 2016 9:09 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Something broke-- Before this fix, a lacking an created a Physical Description type note with mixed content. Now, a component lacking an extent results only in the dimensions and physical facet type notes, leaving the PCDATA in the behind entirely. See http://test.archivesspace.org/resources/58/edit#tree::archival_object_11931 No extent, single dimensions, single physfacet 1 photograph gelatin silver 8 x 10 inches Also attaching my test EAD. Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Chris Fitzpatrick > Sent: Monday, March 14, 2016 5:00 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi Kate, Great. So, does everyone agree we can mark AR-1270 as Accepted? Or is there some outstanding issue? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Bowers, Kate A. > Sent: Sunday, March 13, 2016 4:12 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Chris: Yes, thanks! It is working there (see http://test.archivesspace.org/resources/57#tree::resource_57) Bravo! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Chris Fitzpatrick > Sent: Tuesday, March 8, 2016 2:03 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi, Ok, sorry about the altrender red herring. I just saw that was added to the test data and assume that was the hold up, but didn't look close enough. My bad... So...now I'm confused, since this seems to be reported as fixed, then not fixed, then fixed, etc. Kate are you testing against http://test.archivesspace.org ? The test site has the latest nightly build, so if it's fixed, it'll show it here. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Dallas Pillen > Sent: Tuesday, March 08, 2016 7:54 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi all, We here at the Bentley submitted that PR a few months ago to fix this physdesc mapping issue. As far as I can tell, there is no requirement to have an @altrender="part" attribute; rather, the PR was meant to make ArchivesSpace ingest physdescs in the same way that it exports them. There was some discussion about that on the PR here: https://github.com/archivesspace/archivesspace/pull/312 [https://avatars1.githubusercontent.com/u/7026330?v=3&s=400] AR-1134 and AR-1270: account for all physdesc subtags in EAD import by walkerdb ? Pull Request #312 ? archivesspace/archivesspace github.com JIRA references: AR-1134, AR-1270 We (at the Bentley Historical Library) wrote up a local fix for these issues, and thought we'd pass it upstream. Happy to refactor / edit if anything seems off! ... Basically, the ArchivesSpace EAD exporter exports an extent record's "portion" value as an altrender attribute of "whole" or "part," so the PR that we submitted checks for an altrender attribute and, if it finds one AND the altrender value is "part," the imported extent will have a portion of "part." Otherwise, in cases where there is no altrender attribute or the altrender attribute is some value other than "part," the extent record's portion is set to "whole." See here: https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L248-L252 I just tested importing an EAD with several physdesc variations (some with altrenders, some without; some with multiple extents, a physfacet and a dimensions element, some with only a single extent or a single physfacet, etc.) and it imported as expected (physdescs with an extent + other elements create only an extent record and no duplicate notes; physdescs with only non-extent elements create physical facet, physical dimensions, or physical description notes, and so on). The imported resource is here: http://test.archivesspace.org/resources/54 As far as I can tell, this issue has been fixed but it just has not made it into an official release (the PR was accepted last November; v. 1.4.2 came out in October). I uploaded the EAD that I just tested to the JIRA issue as physdesc_variations_test.xml. On Tue, Mar 8, 2016 at 1:37 PM, Bowers, Kate A. > wrote: I don?t understand the reasoning behind this at all. Why would a that has or only ever be a ?part?? Is there any documentation of the EAD ingest where this is recorded? Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 08, 2016 11:50 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? Hi, We did our March sprint planning yesterday afternoon and this feature request was not included in the sprint. However, looking through this ticket, it looks like a pull request was already submitted and accepted that adds this feature. The key is that the physdesc has to have an @altrender = "part". If someone is wanting to submit a PR to remove the @altrender requirement to the feature, we would certainly look at it. b,chris. ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Bowers, Kate A. > Sent: Tuesday, March 08, 2016 5:16 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? What are the next steps toward getting this bug fixed? I have just uploaded a document to https://archivesspace.atlassian.net/browse/AR-1134 It includes: 1) Undesirable behavior (current behavior) 2) Desired behavior 3) Multiple screenshots from my testing Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers 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, March 03, 2016 1:53 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Any progress on AR1134 (ingesting EAD and )? I have been told that this issue is in Sprint 19, the current sprint, but the status is "icebox". What does "icebox" mean? https://archivesspace.atlassian.net/browse/AR-1134?jql=text%20~%20%22Dimensions%22 One of the reasons we ar particularly interested is that many EAD descriptions of photo collections make particularly heavy use of and . Thanks! Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Dallas Pillen Assistant Archivist for Metadata and Digital Projects [https://webapps.lsa.umich.edu/dean/lsa_emails/bentley-sig-em.png] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Tue Mar 29 09:51:12 2016 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Tue, 29 Mar 2016 09:51:12 -0400 Subject: [Archivesspace_Users_Group] Common script repository? Message-ID: Hi all, Right before and during Code4Lib there was some talk about the best place to advertise the work different people have been doing with scripts related to ArchivesSpace, and the best way to collect or get the word out about the stuff we're doing. I will preface this with saying that I am aware of the Plugins and Scripts pages on AS found here (https://archivesspace.atlassian.net/wiki/display/ADC/Plugins+and+Scripts), but it doesn't seem very comprehensive at all, and is primarily plugins. I just wanted to get the conversation started about the best way to get the word out and get people involved. We could: 1. Keep things the way they are, just be more vocal about advertising the wiki page to a wider audience 2. Create a Github organization where people could add the repositories that they're working on. We would need a couple of people managing the org and adding anyone that requests membership. 3. Something else? I really just wanted to get the conversation started. Does anyone else know a better way to share the work we've been doing with a wider community? Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 -------------- next part -------------- An HTML attachment was scrubbed... URL: From psuda1 at tulane.edu Tue Mar 29 09:55:41 2016 From: psuda1 at tulane.edu (Suda, Phillip J) Date: Tue, 29 Mar 2016 13:55:41 +0000 Subject: [Archivesspace_Users_Group] Common script repository? In-Reply-To: References: Message-ID: Patrick, I was thinking of about this very thing this morning: where can I post some of my plugins or scripts to share with the larger community? I personally like the Github org/repository idea. Thanks, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick Sent: Tuesday, March 29, 2016 8:51 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Common script repository? Hi all, Right before and during Code4Lib there was some talk about the best place to advertise the work different people have been doing with scripts related to ArchivesSpace, and the best way to collect or get the word out about the stuff we're doing. I will preface this with saying that I am aware of the Plugins and Scripts pages on AS found here (https://archivesspace.atlassian.net/wiki/display/ADC/Plugins+and+Scripts), but it doesn't seem very comprehensive at all, and is primarily plugins. I just wanted to get the conversation started about the best way to get the word out and get people involved. We could: 1. Keep things the way they are, just be more vocal about advertising the wiki page to a wider audience 2. Create a Github organization where people could add the repositories that they're working on. We would need a couple of people managing the org and adding anyone that requests membership. 3. Something else? I really just wanted to get the conversation started. Does anyone else know a better way to share the work we've been doing with a wider community? Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave_mayo at harvard.edu Tue Mar 29 11:02:38 2016 From: dave_mayo at harvard.edu (Mayo, Dave) Date: Tue, 29 Mar 2016 15:02:38 +0000 Subject: [Archivesspace_Users_Group] Common script repository? Message-ID: Also interested - I think it needs to be somewhere that's more publicly accessible than the ASpace wiki (I think Github more or less qualifies, as there's no money/institutional barrier to making a PR or editing wiki. - Dave From: , Phillip J > Reply-To: Archivesspace Users Group > Date: Tuesday, March 29, 2016 at 9:55 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Common script repository? Patrick, I was thinking of about this very thing this morning: where can I post some of my plugins or scripts to share with the larger community? I personally like the Github org/repository idea. Thanks, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick Sent: Tuesday, March 29, 2016 8:51 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Common script repository? Hi all, Right before and during Code4Lib there was some talk about the best place to advertise the work different people have been doing with scripts related to ArchivesSpace, and the best way to collect or get the word out about the stuff we're doing. I will preface this with saying that I am aware of the Plugins and Scripts pages on AS found here (https://archivesspace.atlassian.net/wiki/display/ADC/Plugins+and+Scripts), but it doesn't seem very comprehensive at all, and is primarily plugins. I just wanted to get the conversation started about the best way to get the word out and get people involved. We could: 1. Keep things the way they are, just be more vocal about advertising the wiki page to a wider audience 2. Create a Github organization where people could add the repositories that they're working on. We would need a couple of people managing the org and adding anyone that requests membership. 3. Something else? I really just wanted to get the conversation started. Does anyone else know a better way to share the work we've been doing with a wider community? Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vaddoniz at jhu.edu Tue Mar 29 13:31:19 2016 From: vaddoniz at jhu.edu (Valerie Addonizio) Date: Tue, 29 Mar 2016 17:31:19 +0000 Subject: [Archivesspace_Users_Group] Status migration advice Message-ID: <6237ed0638434ec2a4cb460c4177ee84@ESGMTWEX12.win.ad.jhu.edu> Greetings all, Hopkins is working to address a legacy problem with our Processing Status in preparation for going live with ASpace. However, knowing that processing_status is in a state of flux given the discussions around AR-1426, we're wondering whether it will make sense to update AT with our accurate processing_status before migrating, rather than through the API after migrating. I am asking because I see mention of a plugin being written to move this field back for institutions that want it (I hesitatingly believe we are one such institution), and am wondering where that plugin will be looking, and whether putting the updated process_status into AT will simply make this easier in the future. Any comments welcome. -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at mail.lib.msu.edu Tue Mar 29 17:03:10 2016 From: ltang5 at mail.lib.msu.edu (Tang, Lydia) Date: Tue, 29 Mar 2016 21:03:10 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out Message-ID: <886304DC-2345-489A-B87C-BBAA5340B61A@mail.lib.msu.edu> Hello! Sometimes when I am inputting data with the Rapid Data Entry (RDE) tool, our Aspace instance tends to go to a white screen and basically locks me out. I try even closing the browser window and then relogging back in, but it still will be completely white for trying to access the particular resource. I was just wondering if this is a local problem for me, or whether it is more widespread? Thank you so much, Lydia From Chris.Fitzpatrick at lyrasis.org Wed Mar 30 03:54:00 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Wed, 30 Mar 2016 07:54:00 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out In-Reply-To: <886304DC-2345-489A-B87C-BBAA5340B61A@mail.lib.msu.edu> References: <886304DC-2345-489A-B87C-BBAA5340B61A@mail.lib.msu.edu> Message-ID: Hi Lydia, How many rows are you trying to save at once? And which browser? You might be killing your browser's javascript engine. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tang, Lydia Sent: Tuesday, March 29, 2016 11:03 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] white screen lock-out Hello! Sometimes when I am inputting data with the Rapid Data Entry (RDE) tool, our Aspace instance tends to go to a white screen and basically locks me out. I try even closing the browser window and then relogging back in, but it still will be completely white for trying to access the particular resource. I was just wondering if this is a local problem for me, or whether it is more widespread? Thank you so much, Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From Chris.Fitzpatrick at lyrasis.org Wed Mar 30 04:06:26 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Wed, 30 Mar 2016 08:06:26 +0000 Subject: [Archivesspace_Users_Group] Common script repository? In-Reply-To: References: Message-ID: 100% agree. I think development and tech stuff should be moved on the other side of the paywall. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mayo, Dave Sent: Tuesday, March 29, 2016 5:02 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Common script repository? Also interested - I think it needs to be somewhere that's more publicly accessible than the ASpace wiki (I think Github more or less qualifies, as there's no money/institutional barrier to making a PR or editing wiki. - Dave From: , Phillip J > Reply-To: Archivesspace Users Group > Date: Tuesday, March 29, 2016 at 9:55 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Common script repository? Patrick, I was thinking of about this very thing this morning: where can I post some of my plugins or scripts to share with the larger community? I personally like the Github org/repository idea. Thanks, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick Sent: Tuesday, March 29, 2016 8:51 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Common script repository? Hi all, Right before and during Code4Lib there was some talk about the best place to advertise the work different people have been doing with scripts related to ArchivesSpace, and the best way to collect or get the word out about the stuff we're doing. I will preface this with saying that I am aware of the Plugins and Scripts pages on AS found here (https://archivesspace.atlassian.net/wiki/display/ADC/Plugins+and+Scripts), but it doesn't seem very comprehensive at all, and is primarily plugins. I just wanted to get the conversation started about the best way to get the word out and get people involved. We could: 1. Keep things the way they are, just be more vocal about advertising the wiki page to a wider audience 2. Create a Github organization where people could add the repositories that they're working on. We would need a couple of people managing the org and adding anyone that requests membership. 3. Something else? I really just wanted to get the conversation started. Does anyone else know a better way to share the work we've been doing with a wider community? Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Mar 30 07:22:12 2016 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 30 Mar 2016 11:22:12 +0000 Subject: [Archivesspace_Users_Group] Common script repository? In-Reply-To: References: , Message-ID: <4C4D6C6A-052E-4FC9-9E37-98215634D2C3@lyrasis.org> Not to sidetrack this discussion, but in case there is confusion here, most development and tech resources, including the ArchivesSpace wiki page mentioned in this thread, are not limited to members. The pages are public. (A Google search for "archivesspace plugins" brings up that wiki page as the first result.) That, of course, doesn't mean the current plugins page on the wiki is the best place to share these items. I'd prefer to have that page just point to a community-run repository on Github or somewhere else that the people doing the bulk of that dev work decide on and find easy to contribute to, since it sounds like the wiki isn't that place. In the case of the wiki, anyone - member or nonmember - can request an account to edit community pages. In the case of the github documentation, anyone can join the archivesspace repository and submit a pull request to make the documentation better. There are people within the member community and program staff that have more responsibilities and editing/approval privileges than others, but most of the efforts themselves are open to all. Just wanted to clarify that for people who may not realize. This is a great discussion and I'm looking forward to seeing what you decide. Christine Christine Di Bella Community Outreach and Support Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [cid:image003.png at 01CE734E.FD759D30] On Mar 30, 2016, at 4:06 AM, Chris Fitzpatrick > wrote: 100% agree. I think development and tech stuff should be moved on the other side of the paywall. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Mayo, Dave > Sent: Tuesday, March 29, 2016 5:02 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Common script repository? Also interested - I think it needs to be somewhere that's more publicly accessible than the ASpace wiki (I think Github more or less qualifies, as there's no money/institutional barrier to making a PR or editing wiki. - Dave From: , Phillip J > Reply-To: Archivesspace Users Group > Date: Tuesday, March 29, 2016 at 9:55 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Common script repository? Patrick, I was thinking of about this very thing this morning: where can I post some of my plugins or scripts to share with the larger community? I personally like the Github org/repository idea. Thanks, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick Sent: Tuesday, March 29, 2016 8:51 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Common script repository? Hi all, Right before and during Code4Lib there was some talk about the best place to advertise the work different people have been doing with scripts related to ArchivesSpace, and the best way to collect or get the word out about the stuff we?re doing. I will preface this with saying that I am aware of the Plugins and Scripts pages on AS found here (https://archivesspace.atlassian.net/wiki/display/ADC/Plugins+and+Scripts), but it doesn?t seem very comprehensive at all, and is primarily plugins. I just wanted to get the conversation started about the best way to get the word out and get people involved. We could: 1. Keep things the way they are, just be more vocal about advertising the wiki page to a wider audience 2. Create a Github organization where people could add the repositories that they?re working on. We would need a couple of people managing the org and adding anyone that requests membership. 3. Something else? I really just wanted to get the conversation started. Does anyone else know a better way to share the work we?ve been doing with a wider community? Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7645 bytes Desc: image001.png URL: From brad.westbrook at lyrasis.org Wed Mar 30 07:24:16 2016 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Wed, 30 Mar 2016 11:24:16 +0000 Subject: [Archivesspace_Users_Group] Common script repository? In-Reply-To: References: Message-ID: Good morning, Dave Mayo and Patrick Galligan's points are well taken: moving the contents of the AS Plugins and Scripts page to a more visible site and one that might enable more participation would be a very good idea. The AS page could then simply become a reference to that more comprehensive page. Brad W. Bradley D. Westbrook Program Manager brad.westbrook at lyrasis.org 800.999.8558 x2910 678.235.2910 bradley_d_westbrook (Skype) [cid:image003.png at 01CE734E.FD759D30] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Wednesday, March 30, 2016 4:06 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Common script repository? 100% agree. I think development and tech stuff should be moved on the other side of the paywall. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Mayo, Dave > Sent: Tuesday, March 29, 2016 5:02 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Common script repository? Also interested - I think it needs to be somewhere that's more publicly accessible than the ASpace wiki (I think Github more or less qualifies, as there's no money/institutional barrier to making a PR or editing wiki. - Dave From: , Phillip J > Reply-To: Archivesspace Users Group > Date: Tuesday, March 29, 2016 at 9:55 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Common script repository? Patrick, I was thinking of about this very thing this morning: where can I post some of my plugins or scripts to share with the larger community? I personally like the Github org/repository idea. Thanks, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick Sent: Tuesday, March 29, 2016 8:51 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Common script repository? Hi all, Right before and during Code4Lib there was some talk about the best place to advertise the work different people have been doing with scripts related to ArchivesSpace, and the best way to collect or get the word out about the stuff we're doing. I will preface this with saying that I am aware of the Plugins and Scripts pages on AS found here (https://archivesspace.atlassian.net/wiki/display/ADC/Plugins+and+Scripts), but it doesn't seem very comprehensive at all, and is primarily plugins. I just wanted to get the conversation started about the best way to get the word out and get people involved. We could: 1. Keep things the way they are, just be more vocal about advertising the wiki page to a wider audience 2. Create a Github organization where people could add the repositories that they're working on. We would need a couple of people managing the org and adding anyone that requests membership. 3. Something else? I really just wanted to get the conversation started. Does anyone else know a better way to share the work we've been doing with a wider community? Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7645 bytes Desc: image001.png URL: From ltang5 at mail.lib.msu.edu Wed Mar 30 10:07:21 2016 From: ltang5 at mail.lib.msu.edu (Tang, Lydia) Date: Wed, 30 Mar 2016 14:07:21 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out In-Reply-To: <886304DC-2345-489A-B87C-BBAA5340B61A@mail.lib.msu.edu> References: <886304DC-2345-489A-B87C-BBAA5340B61A@mail.lib.msu.edu> Message-ID: <4F9426A4-4E01-4935-B027-AEDCA660247E@mail.lib.msu.edu> Hi Chris and everyone, I wouldn?t be trying to save more then 10 lines at once (referring to my earlier post about the ease of losing RDE data ? which BTW has gotten better, maybe I?m getting the hang of it or maybe there was a tweak on the back end, but I haven?t lost my data nearly as often as the fall), but the white screen lock-out happens even when I erase an archival object. It happens on a regular basis for me, where I either have to log back in to our Aspace instance or even have to switch to a new browser and try again. I am using Google Chrome as the browser, but also use Safari if I have to. My IT folks increased the uh ? buffer (sorry, not techie) memory, but this lock-out still occurs. When it does, their logs are not able to show the problem. Thanks so much for any help you could provide! Lydia ? Hi Lydia, How many rows are you trying to save at once? And which browser? You might be killing your browser's javascript engine. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Tang, Lydia > Sent: Tuesday, March 29, 2016 11:03 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] white screen lock-out Hello! Sometimes when I am inputting data with the Rapid Data Entry (RDE) tool, our Aspace instance tends to go to a white screen and basically locks me out. I try even closing the browser window and then relogging back in, but it still will be completely white for trying to access the particular resource. I was just wondering if this is a local problem for me, or whether it is more widespread? Thank you so much, Lydia From benefiea at gvsu.edu Wed Mar 30 12:53:32 2016 From: benefiea at gvsu.edu (Annie Benefiel) Date: Wed, 30 Mar 2016 16:53:32 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out In-Reply-To: <4F9426A4-4E01-4935-B027-AEDCA660247E@mail.lib.msu.edu> References: <886304DC-2345-489A-B87C-BBAA5340B61A@mail.lib.msu.edu> <4F9426A4-4E01-4935-B027-AEDCA660247E@mail.lib.msu.edu> Message-ID: I have experienced a similar problem using RDE (also in Chrome browser). I have found that when it happens the resource gets "locked out" for about a day, and is accessible when I come back to it the next day. Even attempting to access the resource in another browser fails (tried IE and Firefox). Not so great when you've got a lot of data to enter! In my experimentation I have found that validating the rows before saving them seems to help prevent the "lock out" problem. But I haven't exactly been scientific about it. For longer finding aids I'm using a MS Excel>EAD>ASpace workflow to prevent data loss and lock outs. Annie Benefiel Assistant Archivist Grand Valley State University Special Collections & University Archives (616) 331-8727 www.gvsu.edu/library/specialcollections -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Wednesday, March 30, 2016 10:07 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] white screen lock-out Hi Chris and everyone, I wouldn?t be trying to save more then 10 lines at once (referring to my earlier post about the ease of losing RDE data ? which BTW has gotten better, maybe I?m getting the hang of it or maybe there was a tweak on the back end, but I haven?t lost my data nearly as often as the fall), but the white screen lock-out happens even when I erase an archival object. It happens on a regular basis for me, where I either have to log back in to our Aspace instance or even have to switch to a new browser and try again. I am using Google Chrome as the browser, but also use Safari if I have to. My IT folks increased the uh ? buffer (sorry, not techie) memory, but this lock-out still occurs. When it does, their logs are not able to show the problem. Thanks so much for any help you could provide! Lydia ? Hi Lydia, How many rows are you trying to save at once? And which browser? You might be killing your browser's javascript engine. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Tang, Lydia > Sent: Tuesday, March 29, 2016 11:03 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] white screen lock-out Hello! Sometimes when I am inputting data with the Rapid Data Entry (RDE) tool, our Aspace instance tends to go to a white screen and basically locks me out. I try even closing the browser window and then relogging back in, but it still will be completely white for trying to access the particular resource. I was just wondering if this is a local problem for me, or whether it is more widespread? Thank you so much, Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From Chris.Fitzpatrick at lyrasis.org Wed Mar 30 13:23:24 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Wed, 30 Mar 2016 17:23:24 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out In-Reply-To: References: <886304DC-2345-489A-B87C-BBAA5340B61A@mail.lib.msu.edu> <4F9426A4-4E01-4935-B027-AEDCA660247E@mail.lib.msu.edu>, Message-ID: Hm. And Annie you get the same white screen when it locks out? Yeah, 10 rows shouldn't be too many ( I was thinking like 50 or more ). And if you're getting the same white screen with different browsers, then we can rule that out. Do the Resources have a lot of child archival objects? Like a child with hundreds of direct siblings? Also..weird technical question but do you know if you're using a proxy? Like is your archivesspace have the :8080 port numbers in the URL or not? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Annie Benefiel Sent: Wednesday, March 30, 2016 6:53 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] white screen lock-out I have experienced a similar problem using RDE (also in Chrome browser). I have found that when it happens the resource gets "locked out" for about a day, and is accessible when I come back to it the next day. Even attempting to access the resource in another browser fails (tried IE and Firefox). Not so great when you've got a lot of data to enter! In my experimentation I have found that validating the rows before saving them seems to help prevent the "lock out" problem. But I haven't exactly been scientific about it. For longer finding aids I'm using a MS Excel>EAD>ASpace workflow to prevent data loss and lock outs. Annie Benefiel Assistant Archivist Grand Valley State University Special Collections & University Archives (616) 331-8727 www.gvsu.edu/library/specialcollections -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Wednesday, March 30, 2016 10:07 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] white screen lock-out Hi Chris and everyone, I wouldn?t be trying to save more then 10 lines at once (referring to my earlier post about the ease of losing RDE data ? which BTW has gotten better, maybe I?m getting the hang of it or maybe there was a tweak on the back end, but I haven?t lost my data nearly as often as the fall), but the white screen lock-out happens even when I erase an archival object. It happens on a regular basis for me, where I either have to log back in to our Aspace instance or even have to switch to a new browser and try again. I am using Google Chrome as the browser, but also use Safari if I have to. My IT folks increased the uh ? buffer (sorry, not techie) memory, but this lock-out still occurs. When it does, their logs are not able to show the problem. Thanks so much for any help you could provide! Lydia ? Hi Lydia, How many rows are you trying to save at once? And which browser? You might be killing your browser's javascript engine. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Tang, Lydia > Sent: Tuesday, March 29, 2016 11:03 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] white screen lock-out Hello! Sometimes when I am inputting data with the Rapid Data Entry (RDE) tool, our Aspace instance tends to go to a white screen and basically locks me out. I try even closing the browser window and then relogging back in, but it still will be completely white for trying to access the particular resource. I was just wondering if this is a local problem for me, or whether it is more widespread? Thank you so much, Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From tcramer at stanford.edu Wed Mar 30 13:49:34 2016 From: tcramer at stanford.edu (Tom Cramer) Date: Wed, 30 Mar 2016 17:49:34 +0000 Subject: [Archivesspace_Users_Group] Common script repository? In-Reply-To: <4C4D6C6A-052E-4FC9-9E37-98215634D2C3@lyrasis.org> References: <4C4D6C6A-052E-4FC9-9E37-98215634D2C3@lyrasis.org> Message-ID: Christine, Thanks for this. Is there a concise summary somewhere of what ArchiveSpace resources and channels are publicly available, and which are restricted to members and/or ASpace governance groups? I am having a hard time grokking the current constellation?and it seems I might not be the only one. Thanks, - Tom On Mar 30, 2016, at 4:22 AM, Christine Di Bella > wrote: Not to sidetrack this discussion, but in case there is confusion here, most development and tech resources, including the ArchivesSpace wiki page mentioned in this thread, are not limited to members. The pages are public. (A Google search for "archivesspace plugins" brings up that wiki page as the first result.) That, of course, doesn't mean the current plugins page on the wiki is the best place to share these items. I'd prefer to have that page just point to a community-run repository on Github or somewhere else that the people doing the bulk of that dev work decide on and find easy to contribute to, since it sounds like the wiki isn't that place. In the case of the wiki, anyone - member or nonmember - can request an account to edit community pages. In the case of the github documentation, anyone can join the archivesspace repository and submit a pull request to make the documentation better. There are people within the member community and program staff that have more responsibilities and editing/approval privileges than others, but most of the efforts themselves are open to all. Just wanted to clarify that for people who may not realize. This is a great discussion and I'm looking forward to seeing what you decide. Christine Christine Di Bella Community Outreach and Support Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) On Mar 30, 2016, at 4:06 AM, Chris Fitzpatrick > wrote: 100% agree. I think development and tech stuff should be moved on the other side of the paywall. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Mayo, Dave > Sent: Tuesday, March 29, 2016 5:02 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Common script repository? Also interested - I think it needs to be somewhere that's more publicly accessible than the ASpace wiki (I think Github more or less qualifies, as there's no money/institutional barrier to making a PR or editing wiki. - Dave From: , Phillip J > Reply-To: Archivesspace Users Group > Date: Tuesday, March 29, 2016 at 9:55 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Common script repository? Patrick, I was thinking of about this very thing this morning: where can I post some of my plugins or scripts to share with the larger community? I personally like the Github org/repository idea. Thanks, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick Sent: Tuesday, March 29, 2016 8:51 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Common script repository? Hi all, Right before and during Code4Lib there was some talk about the best place to advertise the work different people have been doing with scripts related to ArchivesSpace, and the best way to collect or get the word out about the stuff we?re doing. I will preface this with saying that I am aware of the Plugins and Scripts pages on AS found here (https://archivesspace.atlassian.net/wiki/display/ADC/Plugins+and+Scripts), but it doesn?t seem very comprehensive at all, and is primarily plugins. I just wanted to get the conversation started about the best way to get the word out and get people involved. We could: 1. Keep things the way they are, just be more vocal about advertising the wiki page to a wider audience 2. Create a Github organization where people could add the repositories that they?re working on. We would need a couple of people managing the org and adding anyone that requests membership. 3. Something else? I really just wanted to get the conversation started. Does anyone else know a better way to share the work we?ve been doing with a wider community? Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From vdodier at eastman.org Wed Mar 30 14:35:12 2016 From: vdodier at eastman.org (Virginia Dodier) Date: Wed, 30 Mar 2016 14:35:12 -0400 Subject: [Archivesspace_Users_Group] Newbie question: is there a crosswalk for DACS to AS available? Message-ID: Hello, I'm just getting familiar with ArchivesSpace -- and I wonder if anyone has mapped/crosswalked AS field names with the corresponding DACS elements? This would be really helpful to me in understanding how we're going to handle our legacy finding aids ... Point me in the right direction, please! -- *Virginia Dodier* Associate Librarian Richard and Ronay Menschel Library George Eastman Museum 900 East Ave. Rochester, NY 14607 vdodier at eastman.org (585) 271-3361 ext. 307 or ext. 336 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Elizabeth.Dunham at asu.edu Wed Mar 30 14:41:21 2016 From: Elizabeth.Dunham at asu.edu (Elizabeth Dunham) Date: Wed, 30 Mar 2016 18:41:21 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out In-Reply-To: References: <886304DC-2345-489A-B87C-BBAA5340B61A@mail.lib.msu.edu> <4F9426A4-4E01-4935-B027-AEDCA660247E@mail.lib.msu.edu>, Message-ID: Hi all, I've had the same issue as Annie and Lydia - I get the white screen lockout when using RDE with Chrome. I've found it doesn't happen with Internet Explorer and it generally lasts for a few days. I reported it and it's logged as AR-1372, but the following notes indicate that it couldn't be replicated. I also checked the URL for my ArchivesSpace instance, and we aren't using a proxy (or at least I don't have :8080 in the URL). Best, Elizabeth Dunham ------------------------ Assistant Archivist Arizona State University Libraries Archives and Special Collections Tempe, AZ 85287-1006 Elizabeth.Dunham at asu.edu -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Wednesday, March 30, 2016 10:23 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] white screen lock-out Hm. And Annie you get the same white screen when it locks out? Yeah, 10 rows shouldn't be too many ( I was thinking like 50 or more ). And if you're getting the same white screen with different browsers, then we can rule that out. Do the Resources have a lot of child archival objects? Like a child with hundreds of direct siblings? Also..weird technical question but do you know if you're using a proxy? Like is your archivesspace have the :8080 port numbers in the URL or not? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Annie Benefiel Sent: Wednesday, March 30, 2016 6:53 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] white screen lock-out I have experienced a similar problem using RDE (also in Chrome browser). I have found that when it happens the resource gets "locked out" for about a day, and is accessible when I come back to it the next day. Even attempting to access the resource in another browser fails (tried IE and Firefox). Not so great when you've got a lot of data to enter! In my experimentation I have found that validating the rows before saving them seems to help prevent the "lock out" problem. But I haven't exactly been scientific about it. For longer finding aids I'm using a MS Excel>EAD>ASpace workflow to prevent data loss and lock outs. Annie Benefiel Assistant Archivist Grand Valley State University Special Collections & University Archives (616) 331-8727 www.gvsu.edu/library/specialcollections From luftsche at usc.edu Wed Mar 30 14:48:09 2016 From: luftsche at usc.edu (Susan Luftschein) Date: Wed, 30 Mar 2016 18:48:09 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out In-Reply-To: References: <886304DC-2345-489A-B87C-BBAA5340B61A@mail.lib.msu.edu> <4F9426A4-4E01-4935-B027-AEDCA660247E@mail.lib.msu.edu>, , Message-ID: Hi Chris et al, I also experience this problem, on both Firefox and Chrome. I have to exit the browser and re log into ASpace, but my data is saved. Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Chris Fitzpatrick Sent: Wednesday, March 30, 2016 10:23 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] white screen lock-out Hm. And Annie you get the same white screen when it locks out? Yeah, 10 rows shouldn't be too many ( I was thinking like 50 or more ). And if you're getting the same white screen with different browsers, then we can rule that out. Do the Resources have a lot of child archival objects? Like a child with hundreds of direct siblings? Also..weird technical question but do you know if you're using a proxy? Like is your archivesspace have the :8080 port numbers in the URL or not? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.org_&d=CwIF-g&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=G9iOZhE_THmV6rgRVOmCFA&m=fILE3emOhc-riEeKQJrgV_eV37ySG5wScaSwG6uyOLs&s=wCWjrm2hF5RoKcDoFiiOS67c04aS8RGYhyKkZQEqqPM&e= ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Annie Benefiel Sent: Wednesday, March 30, 2016 6:53 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] white screen lock-out I have experienced a similar problem using RDE (also in Chrome browser). I have found that when it happens the resource gets "locked out" for about a day, and is accessible when I come back to it the next day. Even attempting to access the resource in another browser fails (tried IE and Firefox). Not so great when you've got a lot of data to enter! In my experimentation I have found that validating the rows before saving them seems to help prevent the "lock out" problem. But I haven't exactly been scientific about it. For longer finding aids I'm using a MS Excel>EAD>ASpace workflow to prevent data loss and lock outs. Annie Benefiel Assistant Archivist Grand Valley State University Special Collections & University Archives (616) 331-8727 www.gvsu.edu/library/specialcollections -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia Sent: Wednesday, March 30, 2016 10:07 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] white screen lock-out Hi Chris and everyone, I wouldn?t be trying to save more then 10 lines at once (referring to my earlier post about the ease of losing RDE data ? which BTW has gotten better, maybe I?m getting the hang of it or maybe there was a tweak on the back end, but I haven?t lost my data nearly as often as the fall), but the white screen lock-out happens even when I erase an archival object. It happens on a regular basis for me, where I either have to log back in to our Aspace instance or even have to switch to a new browser and try again. I am using Google Chrome as the browser, but also use Safari if I have to. My IT folks increased the uh ? buffer (sorry, not techie) memory, but this lock-out still occurs. When it does, their logs are not able to show the problem. Thanks so much for any help you could provide! Lydia ? Hi Lydia, How many rows are you trying to save at once? And which browser? You might be killing your browser's javascript engine. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.org_&d=CwIF-g&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=G9iOZhE_THmV6rgRVOmCFA&m=fILE3emOhc-riEeKQJrgV_eV37ySG5wScaSwG6uyOLs&s=wCWjrm2hF5RoKcDoFiiOS67c04aS8RGYhyKkZQEqqPM&e= ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Tang, Lydia > Sent: Tuesday, March 29, 2016 11:03 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] white screen lock-out Hello! Sometimes when I am inputting data with the Rapid Data Entry (RDE) tool, our Aspace instance tends to go to a white screen and basically locks me out. I try even closing the browser window and then relogging back in, but it still will be completely white for trying to access the particular resource. I was just wondering if this is a local problem for me, or whether it is more widespread? Thank you so much, Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=CwIF-g&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=G9iOZhE_THmV6rgRVOmCFA&m=fILE3emOhc-riEeKQJrgV_eV37ySG5wScaSwG6uyOLs&s=pH4f8PUCkQmKwXkygtNwHKJLwTvo4JprCIcpC6ZLDMs&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=CwIF-g&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=G9iOZhE_THmV6rgRVOmCFA&m=fILE3emOhc-riEeKQJrgV_eV37ySG5wScaSwG6uyOLs&s=pH4f8PUCkQmKwXkygtNwHKJLwTvo4JprCIcpC6ZLDMs&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=CwIF-g&c=clK7kQUTWtAVEOVIgvi0NU5BOUHhpN0H8p7CSfnc_gI&r=G9iOZhE_THmV6rgRVOmCFA&m=fILE3emOhc-riEeKQJrgV_eV37ySG5wScaSwG6uyOLs&s=pH4f8PUCkQmKwXkygtNwHKJLwTvo4JprCIcpC6ZLDMs&e= From christy.tomecek at yale.edu Wed Mar 30 14:57:10 2016 From: christy.tomecek at yale.edu (Tomecek, Christy) Date: Wed, 30 Mar 2016 18:57:10 +0000 Subject: [Archivesspace_Users_Group] Newbie question: is there a crosswalk for DACS to AS available? In-Reply-To: References: Message-ID: Hi Virginia, If you hover your mouse over the titles of fields in a record, a tooltip will come up with a description of what it?s used for and the corresponding DACS element. Here?s what it looks like for me here: [cid:image001.jpg at 01D18A94.6EF66750] We have edited the examples and some of the language in the box, FYI. Best, Christy -- Christy Tomecek Archives Assistant Manuscripts and Archives Yale University Library 203-432-7382 christy.tomecek at yale.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Virginia Dodier Sent: Wednesday, March 30, 2016 2:35 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Newbie question: is there a crosswalk for DACS to AS available? Hello, I'm just getting familiar with ArchivesSpace -- and I wonder if anyone has mapped/crosswalked AS field names with the corresponding DACS elements? This would be really helpful to me in understanding how we're going to handle our legacy finding aids ... Point me in the right direction, please! -- Virginia Dodier Associate Librarian Richard and Ronay Menschel Library George Eastman Museum 900 East Ave. Rochester, NY 14607 vdodier at eastman.org (585) 271-3361 ext. 307 or ext. 336 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 24086 bytes Desc: image001.jpg URL: From annee at radcliffe.harvard.edu Wed Mar 30 15:15:10 2016 From: annee at radcliffe.harvard.edu (Engelhart, Anne) Date: Wed, 30 Mar 2016 19:15:10 +0000 Subject: [Archivesspace_Users_Group] Status migration advice In-Reply-To: <6237ed0638434ec2a4cb460c4177ee84@ESGMTWEX12.win.ad.jhu.edu> References: <6237ed0638434ec2a4cb460c4177ee84@ESGMTWEX12.win.ad.jhu.edu> Message-ID: Hello everyone, Apparently AS-76 is now AR-1426? This still seems to be unresolved. Harvard University continues to advocate for: * The restoration of processing status to collection management records * No reverse migration of data * Processing event records should stay Anne Engelhart Harvard University Member Representative Head, Collection Services Schlesinger Library, Radcliffe Institute 10 Garden St. Cambridge, MA 02138 617.495.8521 Find the Schlesinger Library on Facebook at https://www.facebook.com/SchlesingerLibrary From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Valerie Addonizio Sent: Tuesday, March 29, 2016 1:31 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Status migration advice Greetings all, Hopkins is working to address a legacy problem with our Processing Status in preparation for going live with ASpace. However, knowing that processing_status is in a state of flux given the discussions around AR-1426, we're wondering whether it will make sense to update AT with our accurate processing_status before migrating, rather than through the API after migrating. I am asking because I see mention of a plugin being written to move this field back for institutions that want it (I hesitatingly believe we are one such institution), and am wondering where that plugin will be looking, and whether putting the updated process_status into AT will simply make this easier in the future. Any comments welcome. -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vdodier at eastman.org Wed Mar 30 15:15:34 2016 From: vdodier at eastman.org (Virginia Dodier) Date: Wed, 30 Mar 2016 15:15:34 -0400 Subject: [Archivesspace_Users_Group] Newbie question: is there a crosswalk for DACS to AS available? In-Reply-To: References: Message-ID: Hi Christy, Thanks for your helpful response. I've used the drop-down menus -- I just wondered if that information was in a handy spreadsheet or chart so that I could see all the fields/elements at a glance. Thanks again, Virginia On Wed, Mar 30, 2016 at 2:57 PM, Tomecek, Christy wrote: > Hi Virginia, > > > > If you hover your mouse over the titles of fields in a record, a tooltip > will come up with a description of what it?s used for and the corresponding > DACS element. > > > > Here?s what it looks like for me here: > > > > We have edited the examples and some of the language in the box, FYI. > > > > Best, > > Christy > > -- > > > > Christy Tomecek > > Archives Assistant > > Manuscripts and Archives > > Yale University Library > > 203-432-7382 > > christy.tomecek at yale.edu > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Virginia > Dodier > *Sent:* Wednesday, March 30, 2016 2:35 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Newbie question: is there a > crosswalk for DACS to AS available? > > > > Hello, > > > > I'm just getting familiar with ArchivesSpace -- and I wonder if anyone has > mapped/crosswalked AS field names with the corresponding DACS elements? > > > > This would be really helpful to me in understanding how we're going to > handle our legacy finding aids ... > > > > Point me in the right direction, please! > > > > > > > -- > > *Virginia Dodier* > > Associate Librarian > > Richard and Ronay Menschel Library > > George Eastman Museum > > 900 East Ave. > > Rochester, NY 14607 > > vdodier at eastman.org > > (585) 271-3361 ext. 307 or ext. 336 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- *Virginia Dodier* Associate Librarian Richard and Ronay Menschel Library George Eastman Museum 900 East Ave. Rochester, NY 14607 vdodier at eastman.org (585) 271-3361 ext. 307 or ext. 336 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 24086 bytes Desc: not available URL: From ltang5 at mail.lib.msu.edu Wed Mar 30 15:35:14 2016 From: ltang5 at mail.lib.msu.edu (Tang, Lydia) Date: Wed, 30 Mar 2016 19:35:14 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out Message-ID: <3E6167E2-7180-4185-93DC-B4B709F0320E@mail.lib.msu.edu> Hi Chris and everybody, Well, actually, there was one section of the finding aid which had a run of 224 sibling components (file level description), but most of the other sections are 50 or so at the most. Do you think that could be it? I don?t think we?re using a proxy. We don?t have the :8080 in the URL (but I will let you know if I find out differently). Thanks so much for your help! Lydia From Chris.Fitzpatrick at lyrasis.org Thu Mar 31 04:19:01 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 31 Mar 2016 08:19:01 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out In-Reply-To: <3E6167E2-7180-4185-93DC-B4B709F0320E@mail.lib.msu.edu> References: <3E6167E2-7180-4185-93DC-B4B709F0320E@mail.lib.msu.edu> Message-ID: Hi, Ok...so, yeah 224 should not be too much either. And, it does sound like you're using a proxy ( this is a webserver like Apache or Nginx which directs regular WWW traffic to the :8080 ports that Java uses...so not having "8080" in your URLs probably means you have one.. ) And Susan, you're hosted with LYRASIS, right? So, that will probably rule out most server performance / "we don't have enough RAM" issues. Trying to replicate this...Let me break this down: 1) Using the RDE, I complete 10 rows or so and hit "Save" Q1) There's a period of time ( like it's trying to save) or does it just go to white screen? 2) White screen 4) I restart my browser, log into aspace, go back to edit the record...white screen. Q2) Do you know what happens if you look at the view/readonly page? Q3) Other records are totally unaffected? It's just that one record? Also...anyone who can share their logs ( with a period of time where this was known to have happened ) would be great...if you do can you tell me the URL of the record affected? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tang, Lydia Sent: Wednesday, March 30, 2016 9:35 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] white screen lock-out Hi Chris and everybody, Well, actually, there was one section of the finding aid which had a run of 224 sibling components (file level description), but most of the other sections are 50 or so at the most. Do you think that could be it? I don?t think we?re using a proxy. We don?t have the :8080 in the URL (but I will let you know if I find out differently). Thanks so much for your help! Lydia _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From Chris.Fitzpatrick at lyrasis.org Thu Mar 31 04:44:45 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 31 Mar 2016 08:44:45 +0000 Subject: [Archivesspace_Users_Group] Status migration advice In-Reply-To: References: <6237ed0638434ec2a4cb460c4177ee84@ESGMTWEX12.win.ad.jhu.edu>, Message-ID: Hi Harvard, We definitely haven't forgotten about you. Right now I just don't have enough time to sort this all out. Pretty much scrambling to work through this container management conversion work that's planned to be included in the next release. But...we really need to gather up all the requirements here and spec this out. Some of the things that are being requested are actually contradictory. Is there a way we can maybe figure out how to capture the requirements in a place were everyone can follow a common thread? Listservs are really hard to do this kind of thing effectively... I could maybe post a summary of what I've hearing and seeing to get things kicked off... best, Chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Engelhart, Anne Sent: Wednesday, March 30, 2016 9:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Status migration advice Hello everyone, Apparently AS-76 is now AR-1426? This still seems to be unresolved. Harvard University continues to advocate for: * The restoration of processing status to collection management records * No reverse migration of data * Processing event records should stay Anne Engelhart Harvard University Member Representative Head, Collection Services Schlesinger Library, Radcliffe Institute 10 Garden St. Cambridge, MA 02138 617.495.8521 Find the Schlesinger Library on Facebook at https://www.facebook.com/SchlesingerLibrary [https://scontent-sea1-1.xx.fbcdn.net/hprofile-xpf1/v/t1.0-1/c0.53.158.158/189832_146310392097852_6553760_n.jpg?oh=84e505a389053b4e3e11ebdf14f32358&oe=575B434C] Schlesinger Library | Radcliffe Institute | Harvard University www.facebook.com Schlesinger Library | Radcliffe Institute | Harvard University, Cambridge, MA. 1,297 likes ? 13 talking about this ? 244 were here. The Arthur and... From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Valerie Addonizio Sent: Tuesday, March 29, 2016 1:31 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Status migration advice Greetings all, Hopkins is working to address a legacy problem with our Processing Status in preparation for going live with ASpace. However, knowing that processing_status is in a state of flux given the discussions around AR-1426, we're wondering whether it will make sense to update AT with our accurate processing_status before migrating, rather than through the API after migrating. I am asking because I see mention of a plugin being written to move this field back for institutions that want it (I hesitatingly believe we are one such institution), and am wondering where that plugin will be looking, and whether putting the updated process_status into AT will simply make this easier in the future. Any comments welcome. -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Thu Mar 31 05:50:22 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 31 Mar 2016 09:50:22 +0000 Subject: [Archivesspace_Users_Group] Status migration advice In-Reply-To: References: <6237ed0638434ec2a4cb460c4177ee84@ESGMTWEX12.win.ad.jhu.edu>, , Message-ID: Hi, Quick followup, I just put a longish comment in the ticket to start a conversation : https://archivesspace.atlassian.net/browse/AR-1426 ( and a note, yeah AS-76 became AR-1426. AS is the support jira, where support issues come in. If the support issue is found to be a bug, it gets moved into AR which is where development work is tracked. The original AS-76 url redirects to the new one. Sorry if that's confusing...) b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Chris Fitzpatrick Sent: Thursday, March 31, 2016 10:44 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Status migration advice Hi Harvard, We definitely haven't forgotten about you. Right now I just don't have enough time to sort this all out. Pretty much scrambling to work through this container management conversion work that's planned to be included in the next release. But...we really need to gather up all the requirements here and spec this out. Some of the things that are being requested are actually contradictory. Is there a way we can maybe figure out how to capture the requirements in a place were everyone can follow a common thread? Listservs are really hard to do this kind of thing effectively... I could maybe post a summary of what I've hearing and seeing to get things kicked off... best, Chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Engelhart, Anne Sent: Wednesday, March 30, 2016 9:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Status migration advice Hello everyone, Apparently AS-76 is now AR-1426? This still seems to be unresolved. Harvard University continues to advocate for: ? The restoration of processing status to collection management records ? No reverse migration of data ? Processing event records should stay Anne Engelhart Harvard University Member Representative Head, Collection Services Schlesinger Library, Radcliffe Institute 10 Garden St. Cambridge, MA 02138 617.495.8521 Find the Schlesinger Library on Facebook at https://www.facebook.com/SchlesingerLibrary [https://scontent-sea1-1.xx.fbcdn.net/hprofile-xpf1/v/t1.0-1/c0.53.158.158/189832_146310392097852_6553760_n.jpg?oh=84e505a389053b4e3e11ebdf14f32358&oe=575B434C] Schlesinger Library | Radcliffe Institute | Harvard University www.facebook.com Schlesinger Library | Radcliffe Institute | Harvard University, Cambridge, MA. 1,297 likes ? 13 talking about this ? 244 were here. The Arthur and... From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Valerie Addonizio Sent: Tuesday, March 29, 2016 1:31 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Status migration advice Greetings all, Hopkins is working to address a legacy problem with our Processing Status in preparation for going live with ASpace. However, knowing that processing_status is in a state of flux given the discussions around AR-1426, we?re wondering whether it will make sense to update AT with our accurate processing_status before migrating, rather than through the API after migrating. I am asking because I see mention of a plugin being written to move this field back for institutions that want it (I hesitatingly believe we are one such institution), and am wondering where that plugin will be looking, and whether putting the updated process_status into AT will simply make this easier in the future. Any comments welcome. -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at mail.lib.msu.edu Thu Mar 31 08:18:02 2016 From: ltang5 at mail.lib.msu.edu (Tang, Lydia) Date: Thu, 31 Mar 2016 12:18:02 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out Message-ID: Hi Chris and everyone, Thank you so much for looking into this. It happens also when I delete an archival object. Actually, next time it happens, I?ll try accessing a different record. Since I am usually working intensely on one record at a time, my priority has always been to get back to that one record but I?ll check! It seems to lock me out of the archival resource completely, so I can?t access the view vs. edit view of that record. I guess we are using a proxy! (Sorry, not a techie here?) Here is the information from my IT folks "We use Apache to proxy to Jetty on the AS server. Archivesspace runs on Jetty, a Java servlet container. If we served AS directly from Jetty, there would be a port number in the URL, like :8080, but when you request the AS URL without the port number, it uses port 80, where we have Apache accepting requests. Apache relays the requests to Jetty, which is running Archivesspace. So yes, we use Apache as a proxy for Jetty, but not a separate proxy server. Hope this helps.? I will ask about the logs. Thanks for your help! Lydia From benefiea at gvsu.edu Thu Mar 31 08:49:12 2016 From: benefiea at gvsu.edu (Annie Benefiel) Date: Thu, 31 Mar 2016 12:49:12 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out In-Reply-To: References: <3E6167E2-7180-4185-93DC-B4B709F0320E@mail.lib.msu.edu> Message-ID: Hi Chris, We're hosted with LYRASIS, too. I also experience a blank white screen when this problem occurs. In my experience with this issue, if I try to access the read only/public view of the resource by clicking a direct link for instance, it doesn't exist, just white screen. Links within AS to the resource no longer show up in searching or browsing in the public or staff view. Other resources appear to be unaffected. When the resource re-appears the next day or so, everything seems fine, but it's a toss-up if the data I entered just before the white-out happened has been retained or not, sometimes it has been retained and other times it hasn't. Thanks, Annie Benefiel Assistant Archivist Grand Valley State University Special Collections & University Archives (616) 331-8727 www.gvsu.edu/library/specialcollections -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Thursday, March 31, 2016 4:19 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] white screen lock-out Hi, Ok...so, yeah 224 should not be too much either. And, it does sound like you're using a proxy ( this is a webserver like Apache or Nginx which directs regular WWW traffic to the :8080 ports that Java uses...so not having "8080" in your URLs probably means you have one.. ) And Susan, you're hosted with LYRASIS, right? So, that will probably rule out most server performance / "we don't have enough RAM" issues. Trying to replicate this...Let me break this down: 1) Using the RDE, I complete 10 rows or so and hit "Save" Q1) There's a period of time ( like it's trying to save) or does it just go to white screen? 2) White screen 4) I restart my browser, log into aspace, go back to edit the record...white screen. Q2) Do you know what happens if you look at the view/readonly page? Q3) Other records are totally unaffected? It's just that one record? Also...anyone who can share their logs ( with a period of time where this was known to have happened ) would be great...if you do can you tell me the URL of the record affected? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ From christine.dibella at lyrasis.org Thu Mar 31 10:23:58 2016 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 31 Mar 2016 14:23:58 +0000 Subject: [Archivesspace_Users_Group] Common script repository? In-Reply-To: References: <4C4D6C6A-052E-4FC9-9E37-98215634D2C3@lyrasis.org> Message-ID: Dear Tom, The FAQ on the ArchivesSpace website is still pretty accurate on this topic (see http://archivesspace.org/faq#memberbenefits). We could definitely add explicit mention of the wiki (http://wiki.archivesspace.org) there given that it's a point of confusion here. As far as the different channels go, the wiki itself is public and explains the various channels and tools we use for communication, development, and community interaction. When channels are only available to members, we mention that. If we don't mention it being closed, it's open. Given the number of inquiries we get that way, I think most people realize that we do have a public email address (ArchivesSpaceHome at lyrasis.org) that reaches members of the program team. Lots of people use it to contact us with general and more specific questions about the application, membership, and other services and activities. While we can't provide much in the way of technical support through that channel for non-members, we do not distinguish between members and non-members in answering questions about the application and pointing people in the direction of other resources available to them, regardless of what they decide about membership. But I know when there is confusion, there's a reason. We can definitely go over our online sites and materials we give out at conferences with an eye toward ways to make this clearer. If any of you have ideas or suggestions of what would help you or colleagues that have these concerns, we'd be very glad to have them. Christine From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tom Cramer Sent: Wednesday, March 30, 2016 1:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Common script repository? Christine, Thanks for this. Is there a concise summary somewhere of what ArchiveSpace resources and channels are publicly available, and which are restricted to members and/or ASpace governance groups? I am having a hard time grokking the current constellation-and it seems I might not be the only one. Thanks, - Tom On Mar 30, 2016, at 4:22 AM, Christine Di Bella > wrote: Not to sidetrack this discussion, but in case there is confusion here, most development and tech resources, including the ArchivesSpace wiki page mentioned in this thread, are not limited to members. The pages are public. (A Google search for "archivesspace plugins" brings up that wiki page as the first result.) That, of course, doesn't mean the current plugins page on the wiki is the best place to share these items. I'd prefer to have that page just point to a community-run repository on Github or somewhere else that the people doing the bulk of that dev work decide on and find easy to contribute to, since it sounds like the wiki isn't that place. In the case of the wiki, anyone - member or nonmember - can request an account to edit community pages. In the case of the github documentation, anyone can join the archivesspace repository and submit a pull request to make the documentation better. There are people within the member community and program staff that have more responsibilities and editing/approval privileges than others, but most of the efforts themselves are open to all. Just wanted to clarify that for people who may not realize. This is a great discussion and I'm looking forward to seeing what you decide. Christine Christine Di Bella Community Outreach and Support Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) On Mar 30, 2016, at 4:06 AM, Chris Fitzpatrick > wrote: 100% agree. I think development and tech stuff should be moved on the other side of the paywall. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Mayo, Dave > Sent: Tuesday, March 29, 2016 5:02 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Common script repository? Also interested - I think it needs to be somewhere that's more publicly accessible than the ASpace wiki (I think Github more or less qualifies, as there's no money/institutional barrier to making a PR or editing wiki. - Dave From: , Phillip J > Reply-To: Archivesspace Users Group > Date: Tuesday, March 29, 2016 at 9:55 AM To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Common script repository? Patrick, I was thinking of about this very thing this morning: where can I post some of my plugins or scripts to share with the larger community? I personally like the Github org/repository idea. Thanks, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick Sent: Tuesday, March 29, 2016 8:51 AM To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Common script repository? Hi all, Right before and during Code4Lib there was some talk about the best place to advertise the work different people have been doing with scripts related to ArchivesSpace, and the best way to collect or get the word out about the stuff we're doing. I will preface this with saying that I am aware of the Plugins and Scripts pages on AS found here (https://archivesspace.atlassian.net/wiki/display/ADC/Plugins+and+Scripts), but it doesn't seem very comprehensive at all, and is primarily plugins. I just wanted to get the conversation started about the best way to get the word out and get people involved. We could: 1. Keep things the way they are, just be more vocal about advertising the wiki page to a wider audience 2. Create a Github organization where people could add the repositories that they're working on. We would need a couple of people managing the org and adding anyone that requests membership. 3. Something else? I really just wanted to get the conversation started. Does anyone else know a better way to share the work we've been doing with a wider community? Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From library at princeofpeaceabbey.org Thu Mar 31 12:21:42 2016 From: library at princeofpeaceabbey.org (library at princeofpeaceabbey.org) Date: Thu, 31 Mar 2016 11:21:42 -0500 Subject: [Archivesspace_Users_Group] Status migration advice In-Reply-To: References: <6237ed0638434ec2a4cb460c4177ee84@ESGMTWEX12.win.ad.jhu.edu> Message-ID: <20160331112142.Horde.ZfrgvTedl796zC_B2E2NQ16@gator3088.hostgator.com> Chris, If I can chime in. How hard would it be to let everyone put the fields in the form that they want? I know that in Access and others like it you can put the fields any where. Br Raphael Quoting Chris Fitzpatrick : > Hi Harvard, > > > We definitely haven't forgotten about you. > > > Right now I just don't have enough time to sort this all out. Pretty > much scrambling to work through this container management conversion > work that's planned to be included in the next release. > > > But...we really need to gather up all the requirements here and spec > this out. Some of the things that are being requested are actually > contradictory. > > > Is there a way we can maybe figure out how to capture the > requirements in a place were everyone can follow a common thread? > Listservs are really hard to do this kind of thing effectively... > > I could maybe post a summary of what I've hearing and seeing to get > things kicked off... > > > > best, Chris. > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > > ________________________________ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf > of Engelhart, Anne > Sent: Wednesday, March 30, 2016 9:15 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Status migration advice > > > Hello everyone, > > > > Apparently AS-76 is now AR-1426? This still seems to be unresolved. > Harvard University continues to advocate for: > > * The restoration of processing status to collection > management records > > * No reverse migration of data > > * Processing event records should stay > > > > Anne Engelhart > > Harvard University Member Representative > > Head, Collection Services > > Schlesinger Library, Radcliffe Institute > > 10 Garden St. > > Cambridge, MA 02138 > > 617.495.8521 > > Find the Schlesinger Library on Facebook at > https://www.facebook.com/SchlesingerLibrary > > [https://scontent-sea1-1.xx.fbcdn.net/hprofile-xpf1/v/t1.0-1/c0.53.158.158/189832_146310392097852_6553760_n.jpg?oh=84e505a389053b4e3e11ebdf14f32358&oe=575B434C] > > Schlesinger Library | Radcliffe Institute | Harvard > University > www.facebook.com > Schlesinger Library | Radcliffe Institute | Harvard University, > Cambridge, MA. 1,297 likes ? 13 talking about this ? 244 were here. > The Arthur and... > > > > > > > > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On > Behalf Of Valerie Addonizio > Sent: Tuesday, March 29, 2016 1:31 PM > To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] Status migration advice > > > > Greetings all, > > > > Hopkins is working to address a legacy problem with our Processing > Status in preparation for going live with ASpace. However, knowing > that processing_status is in a state of flux given the discussions > around > AR-1426, we're wondering whether it will make sense to update AT with our accurate processing_status before migrating, rather than through the API after migrating. I am asking because I see mention of a plugin being written to move this field back for institutions that want it (I hesitatingly believe we are one such institution), and am wondering where that plugin will be looking, and whether putting the updated process_status into AT will simply make this easier in the future. Any comments > welcome. > > > > -Valerie > > > > > > > > -------------------------------- > > Valerie Addonizio > > Archivist > > The Sheridan Libraries > > Johns Hopkins University > > vaddoniz at jhu.edu > > 410-516-5261 From psuda1 at tulane.edu Thu Mar 31 12:26:26 2016 From: psuda1 at tulane.edu (Suda, Phillip J) Date: Thu, 31 Mar 2016 16:26:26 +0000 Subject: [Archivesspace_Users_Group] Altering Homepage Search functionality Message-ID: Greetings all, Has anyone altered the ASpace Home Searchbox to just search Collections? It seems users want the initial search to be on Collections instead of the entire set of resources within ArchivesSpace. Thanks, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ltang5 at mail.lib.msu.edu Thu Mar 31 14:06:59 2016 From: ltang5 at mail.lib.msu.edu (Tang, Lydia) Date: Thu, 31 Mar 2016 18:06:59 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out Aspace logs Message-ID: Hi Chris and everyone, Attached is the logs for the last two days. I had incidents a little before Tuesday, March 29, 2016 at 4:40 PM and Wednesday, March 30, 2016 at 11:50 AM . I hope this helps! Lydia -------------- next part -------------- A non-text attachment was scrubbed... Name: aslogs.txt.gz Type: application/gzip Size: 162226 bytes Desc: aslogs.txt.gz URL: From Chris.Fitzpatrick at lyrasis.org Thu Mar 31 16:20:32 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 31 Mar 2016 20:20:32 +0000 Subject: [Archivesspace_Users_Group] white screen lock-out Aspace logs In-Reply-To: References: Message-ID: Oh dang. I think you might have cracked the case. Hopefully, anyways.. In the log at around 16:30 timeframe, I'm seeing an error that says the request size is too big. I just played around with this and it looks like the RDE is setting a cookie that can get rather large, and that can indeed cause the request size to be too big. ( the cookie is tied to the record's URL, so it will only affect that record ) But we will be updating the allowed request size considerable and I will also look into ensuring the cookie size does not balloon. An immediate fix for when this happens might be to delete your archivesspace_rde cookies and see if stops the white page issue... But yeah, this was really helpful. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Tang, Lydia Sent: Thursday, March 31, 2016 8:06 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] white screen lock-out Aspace logs Hi Chris and everyone, Attached is the logs for the last two days. I had incidents a little before Tuesday, March 29, 2016 at 4:40 PM and Wednesday, March 30, 2016 at 11:50 AM . I hope this helps! Lydia From Chris.Fitzpatrick at lyrasis.org Thu Mar 31 17:14:04 2016 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 31 Mar 2016 21:14:04 +0000 Subject: [Archivesspace_Users_Group] Status migration advice In-Reply-To: <20160331112142.Horde.ZfrgvTedl796zC_B2E2NQ16@gator3088.hostgator.com> References: <6237ed0638434ec2a4cb460c4177ee84@ESGMTWEX12.win.ad.jhu.edu> , <20160331112142.Horde.ZfrgvTedl796zC_B2E2NQ16@gator3088.hostgator.com> Message-ID: Hi Br Raphael, No, unfortunately it's not as easy to add fields as in Access since it requires a bit of programming for the web application. However, the field for processing_status are actually still on the container_management table, so it actually won't require much programing to make a plugin that re-adds the fields. However, of course those values would be the pre-upgrade to v1.3.0 values ( if you've used the Events method, they would not be correct values ). Def not a fix for everyone, but there were some people who seemed to be looking for a "I just want that pull-down back and I never used Events" situation. Is that something that would help people out? Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of library at princeofpeaceabbey.org Sent: Thursday, March 31, 2016 6:21 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Status migration advice Chris, If I can chime in. How hard would it be to let everyone put the fields in the form that they want? I know that in Access and others like it you can put the fields any where. Br Raphael Quoting Chris Fitzpatrick : > Hi Harvard, > > > We definitely haven't forgotten about you. > > > Right now I just don't have enough time to sort this all out. Pretty > much scrambling to work through this container management conversion > work that's planned to be included in the next release. > > > But...we really need to gather up all the requirements here and spec > this out. Some of the things that are being requested are actually > contradictory. > > > Is there a way we can maybe figure out how to capture the > requirements in a place were everyone can follow a common thread? > Listservs are really hard to do this kind of thing effectively... > > I could maybe post a summary of what I've hearing and seeing to get > things kicked off... > > > > best, Chris. > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > > ________________________________ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf > of Engelhart, Anne > Sent: Wednesday, March 30, 2016 9:15 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Status migration advice > > > Hello everyone, > > > > Apparently AS-76 is now AR-1426? This still seems to be unresolved. > Harvard University continues to advocate for: > > * The restoration of processing status to collection > management records > > * No reverse migration of data > > * Processing event records should stay > > > > Anne Engelhart > > Harvard University Member Representative > > Head, Collection Services > > Schlesinger Library, Radcliffe Institute > > 10 Garden St. > > Cambridge, MA 02138 > > 617.495.8521 > > Find the Schlesinger Library on Facebook at > https://www.facebook.com/SchlesingerLibrary > > [https://scontent-sea1-1.xx.fbcdn.net/hprofile-xpf1/v/t1.0-1/c0.53.158.158/189832_146310392097852_6553760_n.jpg?oh=84e505a389053b4e3e11ebdf14f32358&oe=575B434C] > > Schlesinger Library | Radcliffe Institute | Harvard > University > www.facebook.com > Schlesinger Library | Radcliffe Institute | Harvard University, > Cambridge, MA. 1,297 likes ? 13 talking about this ? 244 were here. > The Arthur and... > > > > > > > > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On > Behalf Of Valerie Addonizio > Sent: Tuesday, March 29, 2016 1:31 PM > To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] Status migration advice > > > > Greetings all, > > > > Hopkins is working to address a legacy problem with our Processing > Status in preparation for going live with ASpace. However, knowing > that processing_status is in a state of flux given the discussions > around > AR-1426, we're wondering whether it will make sense to update AT with our accurate processing_status before migrating, rather than through the API after migrating. I am asking because I see mention of a plugin being written to move this field back for institutions that want it (I hesitatingly believe we are one such institution), and am wondering where that plugin will be looking, and whether putting the updated process_status into AT will simply make this easier in the future. Any comments > welcome. > > > > -Valerie > > > > > > > > -------------------------------- > > Valerie Addonizio > > Archivist > > The Sheridan Libraries > > Johns Hopkins University > > vaddoniz at jhu.edu > > 410-516-5261 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group