From sdm7g at virginia.edu Sat Mar 1 11:14:06 2014 From: sdm7g at virginia.edu (Steven Majewski) Date: Sat, 1 Mar 2014 11:14:06 -0500 Subject: [Archivesspace_Users_Group] EAD Import - cryptic error messages In-Reply-To: References: <0BBA24EE4B6BFC4A855CB402E92B8408265DAD02@ex-mbg-01.win.duke.edu> <16d86616692b49dea40a4c3714e9ef14@DM2PR08MB351.namprd08.prod.outlook.com> <07DBDB1E-84D5-43E9-A6FB-F4AEC6360847@virginia.edu> <24e7fdf359b04120a576c7a73a150079@BLUPR08MB102.namprd08.prod.outlook.com> Message-ID: <0E19A228-57ED-4AB8-89CD-23FDFADE14DD@virginia.edu> I found a way to get info on the EAD -> JSON_schema mappings, and I?ve managed to fix those notes/0/content errors as well as several others. For debugging purposes, I make this temporary change to jsonmodel_wrap.rb to ignore all validation errors, and I run my command line EAD import parser. ( I haven?t tried running this code on the backend server ? no idea what that might break. ) --- a/backend/app/converters/lib/jsonmodel_wrap.rb +++ b/backend/app/converters/lib/jsonmodel_wrap.rb @@ -13,10 +13,10 @@ module ASpaceImport # TODO - speed things up by avoiding this another way rescue JSONModel::ValidationException => e - e.errors.reject! {|path, mssg| - e.attribute_types && - e.attribute_types.has_key?(path) && - e.attribute_types[path] == 'ArchivesSpaceDynamicEnum'} + e.errors.reject! {|path, mssg| true } +# e.attribute_types && +# e.attribute_types.has_key?(path) && +# e.attribute_types[path] == 'ArchivesSpaceDynamicEnum'} This generates json files for almost all of the EAD files. ( except for about 30, which I assume are the ones with errors other than #<:ValidationException?> ). The ones that would not have normally validated correctly will still generate validation errors if POSTED to /repositories/$ID/batch_imports. However, I can pipe them thru json_pp and search for the schema property in the error message. So far, this has yielded enough context information to identify the source of the problem in the EAD file. Most of these problems seem to trace back to empty elements in the EAD file. In a few cases, there is a missing required element ( unitid, for example ), but in most cases, removing the empty element fixes the problem. Is this something that could be fixed in the parser ? : if the element is empty, don?t create a JSON property for it ? ( For now, I?m adding templates for all of the glitches I?ve found to a AS fixup stylesheet run as a pre-process to AS import. ) ? Steve Majewski On Feb 28, 2014, at 8:43 AM, Brad Westbrook wrote: > Hi, Steve, > > I won?t be able to address your mapping request until next week. > > We are working on a public release now which will address the LDAP security hole reported a couple of weeks ago and include a number of enhancements made since the 1.0.4 release on Jan. 20. We are aiming to announce the release later today, but it might not be until Monday, depending on resolution of one item. > > Brad > > Bradley D. Westbrook > Program Manager > brad.westbrook at lyrasis.org > 800.999.8558 x2910 > 678.235.2910 > bradley_d_westbrook (Skype) > > > > > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org]On Behalf Of Steven Majewski > Sent: Friday, February 28, 2014 8:33 AM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] EAD Import - cryptic error messages > > > Brad: > > Can you express this requirement in terms of EAD elements instead of JSONModel schema types ? > It?s that mapping that is giving me trouble: trying to turn the schema references in those error messages > into elements in the imported EAD that need to be addressed. > > Any ETA for that next release ? > I?ve managed to fixup some of the import problems with a stylesheet: I?m up to 2749 files out of 4074 parsing successfully ( up from 0 and 300+ on my > initial efforts ). That notes/0/content message is my greatest outstanding issue: > > 1210 #<:ValidationException: {:errors=>{"notes/0/content"=>["At least 1 item(s) is required"]}}> > 31 Unexpected Object Type in Queue: Expected archival_object got container > 30 #<:ValidationException: {:errors=>{"dates"=>["one or more required (or enter a Title)"], "title"=>["must not be an empty string (or enter a Date)"]}}> > 11 #<:ValidationException: {:errors=>{"instances/0/container/indicator_1"=>["Property is required but was missing"]}}> > 11 #<:ValidationException: {:errors=>{"id_0"=>["Property is required but was missing"]}}> > 8 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"], "notes/0/content"=>["At least 1 item(s) is required"]}}> > 6 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"]}}> > 5 #<:ValidationException: {:errors=>{"notes/0/content"=>["At least 1 item(s) is required"], "id_0"=>["Property is required but was missing"]}}> > 5 #<:ValidationException: {:errors=>{"ead_id"=>["Must be 255 characters or fewer"]}}> > 2 #<:ValidationException: {:errors=>{"instances/0/container/type_1"=>["Property is required but was missing"]}}> > 1 Invalid schema given: string > 1 #<:ValidationException: {:errors=>{"record"=>["Can't unambiguously match {:reference_text=>\"(In non correspondence -legal)\"} against schema types: [\"JSONModel(:note_index_item) object\"]. Resolve this by adding a 'jsonmodel_type' property to {:reference_text=>\"(In non correspondence -legal)\"}"]}}> > 1 #<:ValidationException: {:errors=>{"notes/7/subnotes/0/content"=>["Must be 65000 characters or fewer"]}}> > 1 #<:ValidationException: {:errors=>{"notes/0/content"=>["At least 1 item(s) is required"], "notes/8/subnotes/0/content"=>["Must be 65000 characters or fewer"]}}> > 1 #<:ValidationException: {:errors=>{"instances/0/container/type_1"=>["Property is required but was missing"], "instances/0/container/indicator_1"=>["Property is required but was missing"]}}> > 1 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"], "ead_id"=>["Must be 255 characters or fewer"]}}> > > > > ? Steve M. > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: From Chris.Fitzpatrick at lyrasis.org Mon Mar 3 17:25:52 2014 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Mon, 3 Mar 2014 22:25:52 +0000 Subject: [Archivesspace_Users_Group] EAD Import - cryptic error messages In-Reply-To: <0E19A228-57ED-4AB8-89CD-23FDFADE14DD@virginia.edu> References: <0BBA24EE4B6BFC4A855CB402E92B8408265DAD02@ex-mbg-01.win.duke.edu> <16d86616692b49dea40a4c3714e9ef14@DM2PR08MB351.namprd08.prod.outlook.com> <07DBDB1E-84D5-43E9-A6FB-F4AEC6360847@virginia.edu> <24e7fdf359b04120a576c7a73a150079@BLUPR08MB102.namprd08.prod.outlook.com> , <0E19A228-57ED-4AB8-89CD-23FDFADE14DD@virginia.edu> Message-ID: <8ef06033dcac438ca3e4549747a0f235@BLUPR08MB343.namprd08.prod.outlook.com> Hi Steven, Wow, thanks for this. I'm am going over this and it really helps for the improved error messaging we are trying to setup. I definitely think it should be doable to strip out any empty XML tags and not have them create JSON nodes. Also looking at the diff you sent..it seems to cause some problems with the test suite, but I need to figure out what's going on there and way this is stripping out some of these error messages. Will update soon. But yes, until then a good work around would be to strip out empty EAD tags prior to import.... best,chris. Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Steven Majewski Sent: Saturday, March 01, 2014 5:14 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] EAD Import - cryptic error messages I found a way to get info on the EAD -> JSON_schema mappings, and I?ve managed to fix those notes/0/content errors as well as several others. For debugging purposes, I make this temporary change to jsonmodel_wrap.rb to ignore all validation errors, and I run my command line EAD import parser. ( I haven?t tried running this code on the backend server ? no idea what that might break. ) --- a/backend/app/converters/lib/jsonmodel_wrap.rb +++ b/backend/app/converters/lib/jsonmodel_wrap.rb @@ -13,10 +13,10 @@ module ASpaceImport # TODO - speed things up by avoiding this another way rescue JSONModel::ValidationException => e - e.errors.reject! {|path, mssg| - e.attribute_types && - e.attribute_types.has_key?(path) && - e.attribute_types[path] == 'ArchivesSpaceDynamicEnum'} + e.errors.reject! {|path, mssg| true } +# e.attribute_types && +# e.attribute_types.has_key?(path) && +# e.attribute_types[path] == 'ArchivesSpaceDynamicEnum'} This generates json files for almost all of the EAD files. ( except for about 30, which I assume are the ones with errors other than #<:ValidationException?> ). The ones that would not have normally validated correctly will still generate validation errors if POSTED to /repositories/$ID/batch_imports. However, I can pipe them thru json_pp and search for the schema property in the error message. So far, this has yielded enough context information to identify the source of the problem in the EAD file. Most of these problems seem to trace back to empty elements in the EAD file. In a few cases, there is a missing required element ( unitid, for example ), but in most cases, removing the empty element fixes the problem. Is this something that could be fixed in the parser ? : if the element is empty, don?t create a JSON property for it ? ( For now, I?m adding templates for all of the glitches I?ve found to a AS fixup stylesheet run as a pre-process to AS import. ) ? Steve Majewski On Feb 28, 2014, at 8:43 AM, Brad Westbrook > wrote: Hi, Steve, I won?t be able to address your mapping request until next week. We are working on a public release now which will address the LDAP security hole reported a couple of weeks ago and include a number of enhancements made since the 1.0.4 release on Jan. 20. We are aiming to announce the release later today, but it might not be until Monday, depending on resolution of one item. Brad Bradley D. Westbrook Program Manager brad.westbrook at lyrasis.org 800.999.8558 x2910 678.235.2910 bradley_d_westbrook (Skype) From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org]On Behalf Of Steven Majewski Sent: Friday, February 28, 2014 8:33 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] EAD Import - cryptic error messages Brad: Can you express this requirement in terms of EAD elements instead of JSONModel schema types ? It?s that mapping that is giving me trouble: trying to turn the schema references in those error messages into elements in the imported EAD that need to be addressed. Any ETA for that next release ? I?ve managed to fixup some of the import problems with a stylesheet: I?m up to 2749 files out of 4074 parsing successfully ( up from 0 and 300+ on my initial efforts ). That notes/0/content message is my greatest outstanding issue: 1210 #<:ValidationException: {:errors=>{"notes/0/content"=>["At least 1 item(s) is required"]}}> 31 Unexpected Object Type in Queue: Expected archival_object got container 30 #<:ValidationException: {:errors=>{"dates"=>["one or more required (or enter a Title)"], "title"=>["must not be an empty string (or enter a Date)"]}}> 11 #<:ValidationException: {:errors=>{"instances/0/container/indicator_1"=>["Property is required but was missing"]}}> 11 #<:ValidationException: {:errors=>{"id_0"=>["Property is required but was missing"]}}> 8 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"], "notes/0/content"=>["At least 1 item(s) is required"]}}> 6 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"]}}> 5 #<:ValidationException: {:errors=>{"notes/0/content"=>["At least 1 item(s) is required"], "id_0"=>["Property is required but was missing"]}}> 5 #<:ValidationException: {:errors=>{"ead_id"=>["Must be 255 characters or fewer"]}}> 2 #<:ValidationException: {:errors=>{"instances/0/container/type_1"=>["Property is required but was missing"]}}> 1 Invalid schema given: string 1 #<:ValidationException: {:errors=>{"record"=>["Can't unambiguously match {:reference_text=>\"(In non correspondence -legal)\"} against schema types: [\"JSONModel(:note_index_item) object\"]. Resolve this by adding a 'jsonmodel_type' property to {:reference_text=>\"(In non correspondence -legal)\"}"]}}> 1 #<:ValidationException: {:errors=>{"notes/7/subnotes/0/content"=>["Must be 65000 characters or fewer"]}}> 1 #<:ValidationException: {:errors=>{"notes/0/content"=>["At least 1 item(s) is required"], "notes/8/subnotes/0/content"=>["Must be 65000 characters or fewer"]}}> 1 #<:ValidationException: {:errors=>{"instances/0/container/type_1"=>["Property is required but was missing"], "instances/0/container/indicator_1"=>["Property is required but was missing"]}}> 1 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"], "ead_id"=>["Must be 255 characters or fewer"]}}> ? Steve M. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Tue Mar 4 13:13:20 2014 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Tue, 4 Mar 2014 18:13:20 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace 1.0.7 Released Message-ID: <93afab0488a140eda8c03199a4d5d71e@BLUPR08MB343.namprd08.prod.outlook.com> The ArchivesSpace team is pleased to announce the release of 1.0.7. This release includes several new features and bugfixes, including a fix for a very critical security ?hole?for ArchivesSpace deployments using LDAP authentication. This release also supports use of the Archon to ArchivesSpace migration tool and includes the following features and fixes: * BUG [#66853752](https://www.pivotaltracker.com/s/projects/386247/stories/66853752): LDAP Login with no password * FEATURE [#62105014](https://www.pivotaltracker.com/s/projects/386247/stories/62105014): Collection management: add processing started date property * FEATURE [#62848096](https://www.pivotaltracker.com/s/projects/386247/stories/62848096): As a public user, I would like to see linked digital object files rendered in the UI (where possible) * FEATURE [#49569471](https://www.pivotaltracker.com/s/projects/386247/stories/49569471): As an Administrator, I want to define a rule to construct ref_ids for resource components * FEATURE [#52047705](https://www.pivotaltracker.com/s/projects/386247/stories/52047705): Add identifier (id_0..id_3 concatenated) to Resources index view (staff UI) * FEATURE [#62785022](https://www.pivotaltracker.com/s/projects/386247/stories/62785022): As a user, I want to be able to sort (primary and secondary) on any data element appearing in a browse screen. * FEATURE [#62894440](https://www.pivotaltracker.com/s/projects/386247/stories/62894440): As an archivist, I would like to have a Rapid Data Entry Tool for creating digital object component records * FEATURE [#48085781](https://www.pivotaltracker.com/s/projects/386247/stories/48085781): EAD imports should map "audience" attributes appropriately * FEATURE [#52316641](https://www.pivotaltracker.com/s/projects/386247/stories/52316641): Public UI should render index items in a way that allows users to navigate to the designated component * BUG [#62026654](https://www.pivotaltracker.com/s/projects/386247/stories/62026654): MARCXML import breaks on authority records * FEATURE [#23369937](https://www.pivotaltracker.com/s/projects/386247/stories/23369937): As an Archivist, I want to import Name records from the LCNAF web service * FEATURE [#62551360](https://www.pivotaltracker.com/s/projects/386247/stories/62551360): Make sort by features for agents and subjects consistent across Staff and Public UIs * FEATURE [#51597121](https://www.pivotaltracker.com/s/projects/386247/stories/51597121): Locations: break building, floor, room, area into separate columns and facets in index view * FEATURE [#39233355](https://www.pivotaltracker.com/s/projects/386247/stories/39233355): As a Repository Manager or Administor, I want to avoid seeing suppressed records by default * FEATURE [#65000166](https://www.pivotaltracker.com/s/projects/386247/stories/65000166): As a repository manager, I would like multi-part notes to require one sub-note/part to be saved and the sub-note/part can be any type that is available. * FEATURE [#64612226](https://www.pivotaltracker.com/s/projects/386247/stories/64612226): As an archivist editing a resource or resource component in the staff UI, I would like instance records to be in a collapsed view by default, and I would like to expand and collapse them on demand. * FEATURE [#47583573](https://www.pivotaltracker.com/s/projects/386247/stories/47583573): As an Archivist, I want to be able to collapse notes in the edit view in the staff UI, with each entry consisting of the note type, the note label (when different than type) and about 25 characters from the beginning of the note * FEATURE [#63846730](https://www.pivotaltracker.com/s/projects/386247/stories/63846730): As public user and as an archivist, I want to search for a defined resource by entering a mulitpart collection ID in the search box * FEATURE [#20740465](https://www.pivotaltracker.com/s/projects/386247/stories/20740465): As an Administrator, I want to export my repository record as CSV * FEATURE [#46401143](https://www.pivotaltracker.com/s/projects/386247/stories/46401143): As a researcher, I want to be able to use Subjects in an Advanced Search * FEATURE [#52226471](https://www.pivotaltracker.com/s/projects/386247/stories/52226471): Events should be displayed/linked on (Accession | DO | Resource | Component) show views and index views, with the option to create new events on the edit view * FEATURE [#65825396](https://www.pivotaltracker.com/s/projects/386247/stories/65825396): As a repository manager, I do not want name contact information published to the web. * FEATURE [#39402005](https://www.pivotaltracker.com/s/projects/386247/stories/39402005): As a Repository Manager or an Administrator, I want to suppress a (Digital Object | Digital Object Component | Resource | Resource Component) * BUG [#65864630](https://www.pivotaltracker.com/s/projects/386247/stories/65864630): Link statements using HTTPS are not active in the Digital Object view in Public UI. * FEATURE [#65826472](https://www.pivotaltracker.com/s/projects/386247/stories/65826472): There should be a delete option on the location record staff view and edit modes. * BUG [#66535718](https://www.pivotaltracker.com/s/projects/386247/stories/66535718): merge button in edit controlled value lists not working in v 1.0.7 rc1 * BUG [#66589136](https://www.pivotaltracker.com/s/projects/386247/stories/66589136): Cannot search or browse for Agents to be merged * BUG [#66125918](https://www.pivotaltracker.com/s/projects/386247/stories/66125918): CSV importer errors out on UTF-8 file with a BOM * BUG [#54842798](https://www.pivotaltracker.com/s/projects/386247/stories/54842798): When tabbing through tree nodes, there is no indication which node has focus ArchivesSpace 1.0.7 is open source software; the application and its source code are available on Github. Build instructions and technical documentation are also provided for the more technically inclined. ArchivesSpace is also a member-supported community. Lists of current members are posted at http://www.archivesspace.org/members. If you are interested in becoming a member, please send a request to ArchivesSpaceHome at lyrasis.org. ? Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Wed Mar 5 05:36:10 2014 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Wed, 5 Mar 2014 10:36:10 +0000 Subject: [Archivesspace_Users_Group] Customizable Staff-Side Interface? In-Reply-To: References: <0eac88dadf904c3fa8a147c7e5b51a27@DM2PR08MB351.namprd08.prod.outlook.com>, Message-ID: <71c8ba718f2b4f98af2f58de8cea8b01@BLUPR08MB343.namprd08.prod.outlook.com> Hi Chris, Apologize this one slipped through the cracks. Just noticed it while going through my backlog... Yes, for modifying the interfacers (both staff and public), you can add files to the plugins/local directory. For example, if you wanted update the frontend's layout, you could add a file to puglins/local/frontend/views/layouts/application.html.erb with your local modifications. This works for controllers and helpers as well. However, for things that require a lot of logic changes, it might be better to make changes to the code and rebuild rather than a plugin. This might be more work, but it would allow you to add testing to your customized logic. My initial thought for this notes request was that it require more customization then I first thought...on reflection, I realized this was something that could probably be easily handled in a plugin. In regards to different themes for different repositories, you could do that, but you would have to add some code to apply the logic to the view. You probably could do this in a helper. Let me know if you have any questions.. best, chris. Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Prom, Christopher John Sent: Tuesday, February 18, 2014 3:59 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Customizable Staff-Side Interface? Chris, Thanks for this note. Can you clarify the procedure would be to modify the staff interface? I read the documentation in the plugins folder: https://github.com/hudmol/archivesspace/tree/master/plugins If I am reading this correctly, one should be able to put any local modifications in the 'local' folder, without having to modify the core code to the application, if you use the same folder/file naming convention as in the main part of the app, then rebuild the code. Is that the basic procedure one should follow to modify stuff on the staff side? Reading your note below, it makes it sound like you should modify the core files, which would then get your code out of sync with the main code base. One other question I have is whether it is possible to have multiple 'local' versions, so that you can have separate themes for repository a, repository b, repository c, etc. Chris Prom On Feb 18, 2014, at 8:38 AM, Chris Fitzpatrick > wrote: Hi Jamie, Well, I would say the interface is very customizable?, but it requires going in editing the source code and rebuilding, so it depends on how comfortable you feel doing that. What you're looking to do would be in the these files: https://github.com/hudmol/archivesspace/blob/master/frontend/app/views/resources/_form_container.html.erb https://github.com/hudmol/archivesspace/blob/master/frontend/app/views/notes/_form.html.erb The first is the partial for editing/creating a resource. The second is the partial for the resources' note. You could modify these files to render out the note partials broken out as their own sections. I can do an example of how this would work if you feel that rebuilding AS from the source. Or do you think this should be a feature request? best,chris. Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Jaime Margalotti > Sent: Monday, February 17, 2014 9:34 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Customizable Staff-Side Interface? How customizable is the back-end interface for ArchivesSpace? I've been getting feedback from our staff and one thing which folks would like to change is the sidebar navigation present when creating new Resources. It currently seems like about 3/4 or more of the collection-level information is dumped into the Notes. Is there a way to break more of these out? Many thanks, Jaime -- Jaime L. Margalotti Senior Assistant Librarian Manuscripts and Archives Department University of Delaware Library Newark, DE 19717-5267 302-831-0554 jmargalo at udel.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 smithkr at MIT.EDU Wed Mar 5 11:24:56 2014 From: smithkr at MIT.EDU (Kari R Smith) Date: Wed, 5 Mar 2014 16:24:56 +0000 Subject: [Archivesspace_Users_Group] Question about Browsing Collections in Public UI Message-ID: <29F559819ACA9A4FBF208407D4B63ABB55107BAC@OC11expo28.exchange.mit.edu> When we look at our Public UI for version 1.0.0 there appears to be no way to list just the collection records (resources). Is this an expected behavior? We know that we have at least 27 Resources published to the Public UI (according to the Staff side). Is this fixed in the 1.0.7 release or should we be able to see Resources (Collections) in the Public UI now? Thank you, Kari Kari R. Smith, Digital Archivist MIT Libraries, Institute Archives and Special Collections 617-258-5568 | smithkr (at) mit.edu http://libraries.mit.edu/archives/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.custer at yale.edu Wed Mar 5 17:12:55 2014 From: mark.custer at yale.edu (Custer, Mark) Date: Wed, 5 Mar 2014 22:12:55 +0000 Subject: [Archivesspace_Users_Group] Migration / EAD export testing: preliminary results Message-ID: All, I just wrapped up performing a bit of migration testing from Archivists' Toolkit to ArchivesSpace, and I thought that I would share my results here, even though I'm still going through the details. Attached are 3 files: 1. A word document that breaks down my notes into three problem categories: a. Migration tool b. ArchivesSpace EAD export c. ArchivesSpace editing interface / database 2. An excel document that lists out all of the EAD elements and attribute in a set of 34 EAD files, as exported from Archivists' Toolkit. 3. An excel document that lists out all of the EAD elements and attribute in a set of 34 EAD files, as exported from ArchivesSpace. Those last two documents are what I'm still analyzing at this point, but I figured that I'd share the results now in case anyone else is doing their own migration testing right now. Also, I should say that I did all of my testing with version 1.0.4. of ArchivesSpace and version 1.0.4 (02-11-2014) of the AT Data Migrator tool. That said, I did quickly verify within the ArchivesSpace sandbox that both the "accessrestrict" and "legalstatus" notes are still not being exported into EAD in version 1.0.7. I've also noted a few irregularities between importing EAD documents vs. using the migration tool. One example: when I import an EAD file, the position of the first component, in the "archival_object" table, is never 0 but generally 1. I suppose that this is because it's counting the number of children element of DSC, and there's a head element in there?.... but when I use the migration tool, the position value of the first component is always 0, as expected. But, I'm going to hold off on doing any more analysis of the EAD import tool until after we've installed version 1.0.7 of ArchivesSpace. And regardless, I think that we'll be using the AT Data Migration tool to get all of our EAD files into ArchivesSpace, since so far it seems to be doing a very good job, and I've also had trouble doing batch EAD imports. All my best, Mark Custer Archivist / Metadata Coordinator Beinecke Rare Book & Manuscript Library 203-432-2969 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: findings2share.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 21108 bytes Desc: findings2share.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ycba-migration-comparison-ASpace.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 12556 bytes Desc: ycba-migration-comparison-ASpace.xlsx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ycba-migration-comparison-AT.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 11743 bytes Desc: ycba-migration-comparison-AT.xlsx URL: From brad.westbrook at lyrasis.org Thu Mar 6 08:28:44 2014 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Thu, 6 Mar 2014 13:28:44 +0000 Subject: [Archivesspace_Users_Group] Question about Browsing Collections in Public UI In-Reply-To: <29F559819ACA9A4FBF208407D4B63ABB55107BAC@OC11expo28.exchange.mit.edu> References: <29F559819ACA9A4FBF208407D4B63ABB55107BAC@OC11expo28.exchange.mit.edu> Message-ID: <71ed3a7edfd14619891039209ba07e52@BLUPR08MB102.namprd08.prod.outlook.com> Hi, Kari, ArchivesSpace 1.0.7 includes in the public browse screens for Collections and Digital Objects a toggle for having the list include / exclude component records. The default is to exclude them. Does your last question below indicate that Resources are not being displayed at all in the Collection browse list in the public interface? In any event, I would recommend you update your implementation to the current version, as many enhancements have been added and bugs fixed since the 1.0.0 release last summer. Yrs, 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 Kari R Smith Sent: Wednesday, March 05, 2014 11:25 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Question about Browsing Collections in Public UI When we look at our Public UI for version 1.0.0 there appears to be no way to list just the collection records (resources). Is this an expected behavior? We know that we have at least 27 Resources published to the Public UI (according to the Staff side). Is this fixed in the 1.0.7 release or should we be able to see Resources (Collections) in the Public UI now? Thank you, Kari Kari R. Smith, Digital Archivist MIT Libraries, Institute Archives and Special Collections 617-258-5568 | smithkr (at) mit.edu http://libraries.mit.edu/archives/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7640 bytes Desc: image001.png URL: From schmitt at umd.edu Thu Mar 6 08:35:33 2014 From: schmitt at umd.edu (Cassandra A Schmitt) Date: Thu, 6 Mar 2014 13:35:33 +0000 Subject: [Archivesspace_Users_Group] Migration / EAD export testing: preliminary results Message-ID: Hi Mark, Thanks so much for sending along! Brad- I think the digest version of this list strips out all attachments. There was a prior email with an attachment that never made it through too. Is there a way to address this? Or provide members with a space where we can share these types of documents? Thanks, Cassie -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of archivesspace_users_group-request at lyralists.lyrasis.org Sent: Wednesday, March 05, 2014 5:47 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Archivesspace_Users_Group Digest, Vol 8, Issue 5 Send Archivesspace_Users_Group mailing list submissions to archivesspace_users_group at lyralists.lyrasis.org To subscribe or unsubscribe via the World Wide Web, visit http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group or, via email, send a message with subject or body 'help' to archivesspace_users_group-request at lyralists.lyrasis.org You can reach the person managing the list at archivesspace_users_group-owner at lyralists.lyrasis.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Archivesspace_Users_Group digest..." Today's Topics: 1. Migration / EAD export testing: preliminary results (Custer, Mark) ---------------------------------------------------------------------- Message: 1 Date: Wed, 5 Mar 2014 22:12:55 +0000 From: "Custer, Mark" To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Migration / EAD export testing: preliminary results Message-ID: Content-Type: text/plain; charset="us-ascii" All, I just wrapped up performing a bit of migration testing from Archivists' Toolkit to ArchivesSpace, and I thought that I would share my results here, even though I'm still going through the details. Attached are 3 files: 1. A word document that breaks down my notes into three problem categories: a. Migration tool b. ArchivesSpace EAD export c. ArchivesSpace editing interface / database 2. An excel document that lists out all of the EAD elements and attribute in a set of 34 EAD files, as exported from Archivists' Toolkit. 3. An excel document that lists out all of the EAD elements and attribute in a set of 34 EAD files, as exported from ArchivesSpace. Those last two documents are what I'm still analyzing at this point, but I figured that I'd share the results now in case anyone else is doing their own migration testing right now. Also, I should say that I did all of my testing with version 1.0.4. of ArchivesSpace and version 1.0.4 (02-11-2014) of the AT Data Migrator tool. That said, I did quickly verify within the ArchivesSpace sandbox that both the "accessrestrict" and "legalstatus" notes are still not being exported into EAD in version 1.0.7. I've also noted a few irregularities between importing EAD documents vs. using the migration tool. One example: when I import an EAD file, the position of the first component, in the "archival_object" table, is never 0 but generally 1. I suppose that this is because it's counting the number of children element of DSC, and there's a head element in there?.... but when I use the migration tool, the position value of the first component is always 0, as expected. But, I'm going to hold off on doing any more analysis of the EAD import tool until after we've installed version 1.0.7 of ArchivesSpace. And regardless, I think that we'll be using the AT Data Migration tool to get all of our EAD files into ArchivesSpace, since so far it seems to be doing a very good job, and I've also had trouble doing batch EAD imports. All my best, Mark Custer Archivist / Metadata Coordinator Beinecke Rare Book & Manuscript Library 203-432-2969 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: findings2share.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 21108 bytes Desc: findings2share.docx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ycba-migration-comparison-ASpace.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 12556 bytes Desc: ycba-migration-comparison-ASpace.xlsx URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ycba-migration-comparison-AT.xlsx Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet Size: 11743 bytes Desc: ycba-migration-comparison-AT.xlsx URL: ------------------------------ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group End of Archivesspace_Users_Group Digest, Vol 8, Issue 5 ******************************************************* From smithkr at MIT.EDU Thu Mar 6 09:29:04 2014 From: smithkr at MIT.EDU (Kari R Smith) Date: Thu, 6 Mar 2014 14:29:04 +0000 Subject: [Archivesspace_Users_Group] Question about Browsing Collections in Public UI In-Reply-To: <71ed3a7edfd14619891039209ba07e52@BLUPR08MB102.namprd08.prod.outlook.com> References: <29F559819ACA9A4FBF208407D4B63ABB55107BAC@OC11expo28.exchange.mit.edu> <71ed3a7edfd14619891039209ba07e52@BLUPR08MB102.namprd08.prod.outlook.com> Message-ID: <29F559819ACA9A4FBF208407D4B63ABB551098AA@OC11expo28.exchange.mit.edu> Hi Brad, We are planning to upgrade to 1.0.7 next week and we are anticipating the enhancements. But to answer your question, it is correct that no resources are being displayed at all in the Collection browse list in the public interface, although we've confirmed there are resource records published. If we are still having trouble after the upgrade I'll write back to the list. Thank you, Kari Kari R. Smith, Digital Archivist MIT Libraries, Institute Archives and Special Collections 617-258-5568 | smithkr (at) mit.edu http://libraries.mit.edu/archives/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brad Westbrook Sent: Thursday, March 06, 2014 8:29 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Question about Browsing Collections in Public UI Hi, Kari, ArchivesSpace 1.0.7 includes in the public browse screens for Collections and Digital Objects a toggle for having the list include / exclude component records. The default is to exclude them. Does your last question below indicate that Resources are not being displayed at all in the Collection browse list in the public interface? In any event, I would recommend you update your implementation to the current version, as many enhancements have been added and bugs fixed since the 1.0.0 release last summer. Yrs, 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 Kari R Smith Sent: Wednesday, March 05, 2014 11:25 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Question about Browsing Collections in Public UI When we look at our Public UI for version 1.0.0 there appears to be no way to list just the collection records (resources). Is this an expected behavior? We know that we have at least 27 Resources published to the Public UI (according to the Staff side). Is this fixed in the 1.0.7 release or should we be able to see Resources (Collections) in the Public UI now? Thank you, Kari Kari R. Smith, Digital Archivist MIT Libraries, Institute Archives and Special Collections 617-258-5568 | smithkr (at) mit.edu http://libraries.mit.edu/archives/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7640 bytes Desc: image001.png URL: From Chris.Fitzpatrick at lyrasis.org Fri Mar 7 08:00:25 2014 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Fri, 7 Mar 2014 13:00:25 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update Message-ID: Hi All, We discovered a bug in the recently released v1.0.7 version of ArchivesSpace that was causing issues with most browsers on the Staff UI, specifically with the ability to add agent relationships in the Agent edit form. Considering this is a blocker for a major piece of functionality, we have pulled v1.0.7 and issued a new version v1.0.7.1 that fixes this issue. You can download the updated version here : https://github.com/archivesspace/archivesspace/releases/tag/v1.0.7.1 With the upgrade guide at: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING.md? We apologize about this inconvenience. Test coverage has been updated to ensure this is avoided in the future. Please let me know if you have any questions... best regards, Chris Fitzpatrick Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Fri Mar 7 17:04:06 2014 From: sdm7g at virginia.edu (Steven Majewski) Date: Fri, 7 Mar 2014 17:04:06 -0500 Subject: [Archivesspace_Users_Group] EAD Import - cryptic error messages In-Reply-To: <8ef06033dcac438ca3e4549747a0f235@BLUPR08MB343.namprd08.prod.outlook.com> References: <0BBA24EE4B6BFC4A855CB402E92B8408265DAD02@ex-mbg-01.win.duke.edu> <16d86616692b49dea40a4c3714e9ef14@DM2PR08MB351.namprd08.prod.outlook.com> <07DBDB1E-84D5-43E9-A6FB-F4AEC6360847@virginia.edu> <24e7fdf359b04120a576c7a73a150079@BLUPR08MB102.namprd08.prod.outlook.com> , <0E19A228-57ED-4AB8-89CD-23FDFADE14DD@virginia.edu> <8ef06033dcac438ca3e4549747a0f235@BLUPR08MB343.namprd08.prod.outlook.com> Message-ID: I can now batch import a large majority of our 4074 EAD files into ArchivesSpace. ( I?ve only samples and tested a portion of other Virginia Heritage institutions 6000+ files. ) All but 21 files parse and produce json files with my batch import parser. Not all of those json files import with POST /repositories/$ID/batch_imports: several hundred fail, usually with Java memory errors returned. In the one instance I?ve tried, I was able to import the file successfully using the frontend web import job upload form. The remaining error messages are: 1 #<:ValidationException: {:errors=>{"instances/0/container/type_1"=>["Property is required but was missing"]}}> 1 #<:ValidationException: {:errors=>{"record"=>["Can't unambiguously match {:reference_text=>\"(In non correspondence -legal)\"} against schema types: [\"JSONModel(:note_index_item) object\"]. Resolve this by adding a 'jsonmodel_type' property to {:reference_text=>\"(In non correspondence -legal)\"}"]}}> 1 Invalid schema given: string 2 #<:ValidationException: {:errors=>{"notes/7/subnotes/0/content"=>["Must be 65000 characters or fewer"]}}> 16 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"]}}> I will continue to investigate these errors, but in the mean time, it seemed we could import a sufficient number to go on to evaluating the rest of the system. Here is the stylesheet I?m using to fix some of these import problems. In some cases, the ?fix? is just papering over a problem to get the guide imported. For example, we?re inserting ?1 arbitrary_unit? for missing elements; or arbitrarily truncating the at 255 characters. The desired plan would be to get all of the collections imported into ArchivesSpace and review and correct them there (rather than editing EAD xml files). But we need a good way of tagging the elements that need review and correction. I don?t know if the xml comments I?ve inserted will prove to be a useful solution to that. Here, I believe Archivist?s Toolkit solution was to import files even when it didn?t meet it?s requirements, but then you could not publish or expand the hierarchy of the guide until you had gone thru and corrected the issues, which were hilighted in the edit form. This would be the ideal, but I would at least like to figure out how to tag elements as needing review. ( BTW: What is the difference between not-published & suppressed ? ) Looking directly at the json files (using that patch below) definitely speeded up finding the source of the problems. This is the main problem with using an intermediate representation like json-model: the error messages all reference the intermediate language, and not the source language. What is the poor EAD author to make of an error message like this: #<:ValidationException: {:errors=>{"record"=>["Can't unambiguously match {:reference_text=>\"(In non correspondence -legal)\"} against schema types: [\"JSONModel(:note_index_item) object\"]. Resolve this by adding a 'jsonmodel_type' property to {:reference_text=>\"(In non correspondence -legal)\"}"]}}> ?? If fixing the error messages proves to be too difficult a task, maybe it would be simpler to produce a schema that matches what AS EAD import accepts, and people can do their own pre-validation against that restricted schema. ( Or is the goal the other way around ? to eventually get AS imported to handle any valid EAD file ? ) ? Steve Majewski / UVA Alderman Library On Mar 3, 2014, at 5:25 PM, Chris Fitzpatrick wrote: > Hi Steven, > > Wow, thanks for this. I'm am going over this and it really helps for the improved error messaging we are trying to setup. > > I definitely think it should be doable to strip out any empty XML tags and not have them create JSON nodes. > > Also looking at the diff you sent..it seems to cause some problems with the test suite, but I need to figure out what's going on there and way this is stripping out some of these error messages. Will update soon. > > But yes, until then a good work around would be to strip out empty EAD tags prior to import.... > > best,chris. > > > Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org > Developer, ArchivesSpace > http://archivesspace.org/ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Steven Majewski > Sent: Saturday, March 01, 2014 5:14 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] EAD Import - cryptic error messages > > > I found a way to get info on the EAD -> JSON_schema mappings, and I?ve managed to fix those notes/0/content errors as well as several others. > > For debugging purposes, I make this temporary change to jsonmodel_wrap.rb to ignore all validation errors, > and I run my command line EAD import parser. ( I haven?t tried running this code on the backend server ? no idea what that might break. ) > > --- a/backend/app/converters/lib/jsonmodel_wrap.rb > +++ b/backend/app/converters/lib/jsonmodel_wrap.rb > @@ -13,10 +13,10 @@ module ASpaceImport > # TODO - speed things up by avoiding this another way > rescue JSONModel::ValidationException => e > > - e.errors.reject! {|path, mssg| > - e.attribute_types && > - e.attribute_types.has_key?(path) && > - e.attribute_types[path] == 'ArchivesSpaceDynamicEnum'} > + e.errors.reject! {|path, mssg| true } > +# e.attribute_types && > +# e.attribute_types.has_key?(path) && > +# e.attribute_types[path] == 'ArchivesSpaceDynamicEnum'} > > > This generates json files for almost all of the EAD files. ( except for about 30, which I assume are the ones with errors other > than #<:ValidationException?> ). The ones that would not have normally validated correctly will still generate validation > errors if POSTED to /repositories/$ID/batch_imports. However, I can pipe them thru json_pp and search for the schema > property in the error message. So far, this has yielded enough context information to identify the source of the problem > in the EAD file. > > Most of these problems seem to trace back to empty elements in the EAD file. > > In a few cases, there is a missing required element ( unitid, for example ), but in most cases, removing the empty element > fixes the problem. Is this something that could be fixed in the parser ? : if the element is empty, don?t create a JSON property > for it ? > ( For now, I?m adding templates for all of the glitches I?ve found to a AS fixup stylesheet run as a pre-process to AS import. ) > > > ? Steve Majewski > > > On Feb 28, 2014, at 8:43 AM, Brad Westbrook wrote: > >> Hi, Steve, >> >> I won?t be able to address your mapping request until next week. >> >> We are working on a public release now which will address the LDAP security hole reported a couple of weeks ago and include a number of enhancements made since the 1.0.4 release on Jan. 20. We are aiming to announce the release later today, but it might not be until Monday, depending on resolution of one item. >> >> Brad >> >> Bradley D. Westbrook >> Program Manager >> brad.westbrook at lyrasis.org >> 800.999.8558 x2910 >> 678.235.2910 >> bradley_d_westbrook (Skype) >> >> >> >> >> >> >> From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org]On Behalf Of Steven Majewski >> Sent: Friday, February 28, 2014 8:33 AM >> To: Archivesspace Users Group >> Subject: Re: [Archivesspace_Users_Group] EAD Import - cryptic error messages >> >> >> Brad: >> >> Can you express this requirement in terms of EAD elements instead of JSONModel schema types ? >> It?s that mapping that is giving me trouble: trying to turn the schema references in those error messages >> into elements in the imported EAD that need to be addressed. >> >> Any ETA for that next release ? >> I?ve managed to fixup some of the import problems with a stylesheet: I?m up to 2749 files out of 4074 parsing successfully ( up from 0 and 300+ on my >> initial efforts ). That notes/0/content message is my greatest outstanding issue: >> >> 1210 #<:ValidationException: {:errors=>{"notes/0/content"=>["At least 1 item(s) is required"]}}> >> 31 Unexpected Object Type in Queue: Expected archival_object got container >> 30 #<:ValidationException: {:errors=>{"dates"=>["one or more required (or enter a Title)"], "title"=>["must not be an empty string (or enter a Date)"]}}> >> 11 #<:ValidationException: {:errors=>{"instances/0/container/indicator_1"=>["Property is required but was missing"]}}> >> 11 #<:ValidationException: {:errors=>{"id_0"=>["Property is required but was missing"]}}> >> 8 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"], "notes/0/content"=>["At least 1 item(s) is required"]}}> >> 6 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"]}}> >> 5 #<:ValidationException: {:errors=>{"notes/0/content"=>["At least 1 item(s) is required"], "id_0"=>["Property is required but was missing"]}}> >> 5 #<:ValidationException: {:errors=>{"ead_id"=>["Must be 255 characters or fewer"]}}> >> 2 #<:ValidationException: {:errors=>{"instances/0/container/type_1"=>["Property is required but was missing"]}}> >> 1 Invalid schema given: string >> 1 #<:ValidationException: {:errors=>{"record"=>["Can't unambiguously match {:reference_text=>\"(In non correspondence -legal)\"} against schema types: [\"JSONModel(:note_index_item) object\"]. Resolve this by adding a 'jsonmodel_type' property to {:reference_text=>\"(In non correspondence -legal)\"}"]}}> >> 1 #<:ValidationException: {:errors=>{"notes/7/subnotes/0/content"=>["Must be 65000 characters or fewer"]}}> >> 1 #<:ValidationException: {:errors=>{"notes/0/content"=>["At least 1 item(s) is required"], "notes/8/subnotes/0/content"=>["Must be 65000 characters or fewer"]}}> >> 1 #<:ValidationException: {:errors=>{"instances/0/container/type_1"=>["Property is required but was missing"], "instances/0/container/indicator_1"=>["Property is required but was missing"]}}> >> 1 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"], "ead_id"=>["Must be 255 characters or fewer"]}}> >> >> >> >> ? Steve M. >> > > _______________________________________________ > 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: as-munger.xsl Type: application/octet-stream Size: 6508 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: From michael.rush at yale.edu Sun Mar 9 22:23:33 2014 From: michael.rush at yale.edu (Rush, Michael) Date: Mon, 10 Mar 2014 02:23:33 +0000 Subject: [Archivesspace_Users_Group] Interest in payments/accounting module? Message-ID: Fellow ArchivesSpace members, I am participating in the implementation of ArchivesSpace here at Yale. I'm particularly involved with how we will use the accessioning module. One critical piece of functionality for us not present in ArchivesSpace is the ability to create records of payments made for new accessions. In the Archivists' Toolkit we use User Defined Fields to capture the necessary data, but in ArchivesSpace we hope to structure better the relevant data and generally improve the way we do things. Right now we imagine working with developers to create a new payments module within ArchivesSpace. This would allow payments to be linked to accession records, or conceivably to resources or digital objects. After discussing our preliminary ideas with Brad Westbrook, he wisely suggested that others in the ArchivesSpace community might be interested in something like this as well. If you would find a payments module useful in your local implementation, please let me know. I'd love to develop something that will be useful to the broader ArchivesSpace community, not just in a local Yale context. Best, Mike _____________________________________ Michael Rush Accessioning Archivist Beinecke Rare Book and Manuscript Library Yale University 203-432-8123 The Beinecke Library will be closed for renovations May 2015 to August 2016.? We will maintain a temporary reading room in Sterling Memorial Library during this time.? However, access to collections will be limited.? Please see?http://beineckelibraryrenovation.yale.edu/?for more information. From mark.custer at yale.edu Mon Mar 10 10:55:54 2014 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 10 Mar 2014 14:55:54 +0000 Subject: [Archivesspace_Users_Group] EAD Import - cryptic error messages In-Reply-To: References: <0BBA24EE4B6BFC4A855CB402E92B8408265DAD02@ex-mbg-01.win.duke.edu> <16d86616692b49dea40a4c3714e9ef14@DM2PR08MB351.namprd08.prod.outlook.com> <07DBDB1E-84D5-43E9-A6FB-F4AEC6360847@virginia.edu> <24e7fdf359b04120a576c7a73a150079@BLUPR08MB102.namprd08.prod.outlook.com> , <0E19A228-57ED-4AB8-89CD-23FDFADE14DD@virginia.edu> <8ef06033dcac438ca3e4549747a0f235@BLUPR08MB343.namprd08.prod.outlook.com> Message-ID: Just to second this: I would love to have a schema available that defines what type of EAD files are supported by ArchivesSpace! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Steven Majewski Sent: Friday, March 07, 2014 5:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] EAD Import - cryptic error messages I can now batch import a large majority of our 4074 EAD files into ArchivesSpace. ( I've only samples and tested a portion of other Virginia Heritage institutions 6000+ files. ) All but 21 files parse and produce json files with my batch import parser. Not all of those json files import with POST /repositories/$ID/batch_imports: several hundred fail, usually with Java memory errors returned. In the one instance I've tried, I was able to import the file successfully using the frontend web import job upload form. The remaining error messages are: 1 #<:ValidationException: {:errors=>{"instances/0/container/type_1"=>["Property is required but was missing"]}}> 1 #<:ValidationException: {:errors=>{"record"=>["Can't unambiguously match {:reference_text=>\"(In non correspondence -legal)\"} against schema types: [\"JSONModel(:note_index_item) object\"]. Resolve this by adding a 'jsonmodel_type' property to {:reference_text=>\"(In non correspondence -legal)\"}"]}}> 1 Invalid schema given: string 2 #<:ValidationException: {:errors=>{"notes/7/subnotes/0/content"=>["Must be 65000 characters or fewer"]}}> 16 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"]}}> I will continue to investigate these errors, but in the mean time, it seemed we could import a sufficient number to go on to evaluating the rest of the system. Here is the stylesheet I'm using to fix some of these import problems. In some cases, the "fix" is just papering over a problem to get the guide imported. For example, we're inserting "1 arbitrary_unit" for missing elements; or arbitrarily truncating the at 255 characters. The desired plan would be to get all of the collections imported into ArchivesSpace and review and correct them there (rather than editing EAD xml files). But we need a good way of tagging the elements that need review and correction. I don't know if the xml comments I've inserted will prove to be a useful solution to that. Here, I believe Archivist's Toolkit solution was to import files even when it didn't meet it's requirements, but then you could not publish or expand the hierarchy of the guide until you had gone thru and corrected the issues, which were hilighted in the edit form. This would be the ideal, but I would at least like to figure out how to tag elements as needing review. ( BTW: What is the difference between not-published & suppressed ? ) Looking directly at the json files (using that patch below) definitely speeded up finding the source of the problems. This is the main problem with using an intermediate representation like json-model: the error messages all reference the intermediate language, and not the source language. What is the poor EAD author to make of an error message like this: #<:ValidationException: {:errors=>{"record"=>["Can't unambiguously match {:reference_text=>\"(In non correspondence -legal)\"} against schema types: [\"JSONModel(:note_index_item) object\"]. Resolve this by adding a 'jsonmodel_type' property to {:reference_text=>\"(In non correspondence -legal)\"}"]}}> ?? If fixing the error messages proves to be too difficult a task, maybe it would be simpler to produce a schema that matches what AS EAD import accepts, and people can do their own pre-validation against that restricted schema. ( Or is the goal the other way around ? to eventually get AS imported to handle any valid EAD file ? ) - Steve Majewski / UVA Alderman Library On Mar 3, 2014, at 5:25 PM, Chris Fitzpatrick > wrote: Hi Steven, Wow, thanks for this. I'm am going over this and it really helps for the improved error messaging we are trying to setup. I definitely think it should be doable to strip out any empty XML tags and not have them create JSON nodes. Also looking at the diff you sent..it seems to cause some problems with the test suite, but I need to figure out what's going on there and way this is stripping out some of these error messages. Will update soon. But yes, until then a good work around would be to strip out empty EAD tags prior to import.... best,chris. Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Steven Majewski > Sent: Saturday, March 01, 2014 5:14 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] EAD Import - cryptic error messages I found a way to get info on the EAD -> JSON_schema mappings, and I've managed to fix those notes/0/content errors as well as several others. For debugging purposes, I make this temporary change to jsonmodel_wrap.rb to ignore all validation errors, and I run my command line EAD import parser. ( I haven't tried running this code on the backend server - no idea what that might break. ) --- a/backend/app/converters/lib/jsonmodel_wrap.rb +++ b/backend/app/converters/lib/jsonmodel_wrap.rb @@ -13,10 +13,10 @@ module ASpaceImport # TODO - speed things up by avoiding this another way rescue JSONModel::ValidationException => e - e.errors.reject! {|path, mssg| - e.attribute_types && - e.attribute_types.has_key?(path) && - e.attribute_types[path] == 'ArchivesSpaceDynamicEnum'} + e.errors.reject! {|path, mssg| true } +# e.attribute_types && +# e.attribute_types.has_key?(path) && +# e.attribute_types[path] == 'ArchivesSpaceDynamicEnum'} This generates json files for almost all of the EAD files. ( except for about 30, which I assume are the ones with errors other than #<:ValidationException...> ). The ones that would not have normally validated correctly will still generate validation errors if POSTED to /repositories/$ID/batch_imports. However, I can pipe them thru json_pp and search for the schema property in the error message. So far, this has yielded enough context information to identify the source of the problem in the EAD file. Most of these problems seem to trace back to empty elements in the EAD file. In a few cases, there is a missing required element ( unitid, for example ), but in most cases, removing the empty element fixes the problem. Is this something that could be fixed in the parser ? : if the element is empty, don't create a JSON property for it ? ( For now, I'm adding templates for all of the glitches I've found to a AS fixup stylesheet run as a pre-process to AS import. ) - Steve Majewski On Feb 28, 2014, at 8:43 AM, Brad Westbrook > wrote: Hi, Steve, I won't be able to address your mapping request until next week. We are working on a public release now which will address the LDAP security hole reported a couple of weeks ago and include a number of enhancements made since the 1.0.4 release on Jan. 20. We are aiming to announce the release later today, but it might not be until Monday, depending on resolution of one item. Brad Bradley D. Westbrook Program Manager brad.westbrook at lyrasis.org 800.999.8558 x2910 678.235.2910 bradley_d_westbrook (Skype) From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org]On Behalf Of Steven Majewski Sent: Friday, February 28, 2014 8:33 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] EAD Import - cryptic error messages Brad: Can you express this requirement in terms of EAD elements instead of JSONModel schema types ? It's that mapping that is giving me trouble: trying to turn the schema references in those error messages into elements in the imported EAD that need to be addressed. Any ETA for that next release ? I've managed to fixup some of the import problems with a stylesheet: I'm up to 2749 files out of 4074 parsing successfully ( up from 0 and 300+ on my initial efforts ). That notes/0/content message is my greatest outstanding issue: 1210 #<:ValidationException: {:errors=>{"notes/0/content"=>["At least 1 item(s) is required"]}}> 31 Unexpected Object Type in Queue: Expected archival_object got container 30 #<:ValidationException: {:errors=>{"dates"=>["one or more required (or enter a Title)"], "title"=>["must not be an empty string (or enter a Date)"]}}> 11 #<:ValidationException: {:errors=>{"instances/0/container/indicator_1"=>["Property is required but was missing"]}}> 11 #<:ValidationException: {:errors=>{"id_0"=>["Property is required but was missing"]}}> 8 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"], "notes/0/content"=>["At least 1 item(s) is required"]}}> 6 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"]}}> 5 #<:ValidationException: {:errors=>{"notes/0/content"=>["At least 1 item(s) is required"], "id_0"=>["Property is required but was missing"]}}> 5 #<:ValidationException: {:errors=>{"ead_id"=>["Must be 255 characters or fewer"]}}> 2 #<:ValidationException: {:errors=>{"instances/0/container/type_1"=>["Property is required but was missing"]}}> 1 Invalid schema given: string 1 #<:ValidationException: {:errors=>{"record"=>["Can't unambiguously match {:reference_text=>\"(In non correspondence -legal)\"} against schema types: [\"JSONModel(:note_index_item) object\"]. Resolve this by adding a 'jsonmodel_type' property to {:reference_text=>\"(In non correspondence -legal)\"}"]}}> 1 #<:ValidationException: {:errors=>{"notes/7/subnotes/0/content"=>["Must be 65000 characters or fewer"]}}> 1 #<:ValidationException: {:errors=>{"notes/0/content"=>["At least 1 item(s) is required"], "notes/8/subnotes/0/content"=>["Must be 65000 characters or fewer"]}}> 1 #<:ValidationException: {:errors=>{"instances/0/container/type_1"=>["Property is required but was missing"], "instances/0/container/indicator_1"=>["Property is required but was missing"]}}> 1 #<:ValidationException: {:errors=>{"extents"=>["At least 1 item(s) is required"], "ead_id"=>["Must be 255 characters or fewer"]}}> - Steve M. _______________________________________________ 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 cdibella at ias.edu Mon Mar 10 14:35:41 2014 From: cdibella at ias.edu (Christine Di Bella) Date: Mon, 10 Mar 2014 14:35:41 -0400 (EDT) Subject: [Archivesspace_Users_Group] published/unpublished (observations based on using migration tool for AT records) Message-ID: I used the migration tool to import records from my Archivists' Toolkit instance to my ArchivesSpace 1.0.7.1 testing instance. I have a few questions related to publishing information in the Public Interface. * It seems that, when using the migration tool, Digital Objects are set to publish by default, whereas Resources and Accessions are set to not be published by default. Is there are way to change this? It seems like this behavior should be consistent across the three types of records. * Though when one publishes a record for the first time all the lower levels inherit that setting, I've found that if I decide to unpublish a previously published record, lower levels do not inherit that setting and listings still appear via Browse or Search in the Public Interface, which means I would need to unpublish each component individually to make them go away. That said, clicking on the listing in the public interface brings up the "Sorry, something went wrong" screen, so something in the system knows that it's not supposed to be shown. (If I manually update the component to be unpublished, it disappears from the Public Interface entirely as expected.) A previously published record that is later suppressed exhibits the same behavior, as well as still being listed at the top level - clicking on the listing yields a screen that says "Record Not Found. The record you've tried to access does not exist or may have been removed." . * Following off of both of these things, is there a way to bulk update records to be published or unpublished, or a thought to providing this functionality in the future? Thanks, Christine Christine Di Bella Archivist Shelby White and Leon Levy Archives Center Institute for Advanced Study Einstein Drive Princeton, NJ 08540 Email : cdibella at ias.edu Phone: 609-734-8368 Website : http://library.ias.edu/archives -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Mon Mar 10 16:55:00 2014 From: sdm7g at virginia.edu (Steven Majewski) Date: Mon, 10 Mar 2014 16:55:00 -0400 Subject: [Archivesspace_Users_Group] Can't delete guide under mysql: foreign key constraint. Message-ID: With ArchivesSpace 1.0.7.1 using mysql, I Imported an EAD guide and then tried to delete it. If I try to delete the collection from the View of Edit page, I get: We're sorry, but something went wrong. If I try to delete my checking it in the browse page and clicking delete, I get: Unable to delete records: ["{\"error\":\"Record deletion failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLIntegrityConstraintViolationException: Cannot delete or update a parent row: a foreign key constraint fails (`archivesspace/archival_object`, CONSTRAINT `archival_object_ibfk_5` FOREIGN KEY (`parent_id`) REFERENCES `archival_object` (`id`))\"}\n"] [/repositories/2/resources/3719] I was finally able to delete the collection only after individually deleting all of it?s components. I tried with another install of 1.0.7.1 on my laptop, using the development db instead of mysql. I imported EAD and then deleted the top level collection with no problem. Then I reconfigured it to use mysql, and I get the same errors as above. ? Steve Majewski -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: From Elizabeth.Dunham at asu.edu Mon Mar 10 17:57:40 2014 From: Elizabeth.Dunham at asu.edu (Elizabeth Dunham) Date: Mon, 10 Mar 2014 21:57:40 +0000 Subject: [Archivesspace_Users_Group] Controlled Value List Merge Issue/Error Message-ID: Hello, When I migrated all of my accession records into Archives Space using the CSV template, the importer created apparently duplicate values for a number of items in the controlled value lists (box, folder, etc.). I used the merge feature to eliminate most of the duplicates, but in the process apparently overwrote the default value for "Completed" in the "Collection Management" section with the duplicate value, with the result that "Processing Status" shows up as "-" rather than "Completed" on the main screen. I checked the collection_management table and noticed that for processed collections, processing_status_id is 1325. What should it be instead? Thanks for your help! Elizabeth Dunham ------------------------ Assistant Archivist Arizona State University Libraries Archives and Special Collections Tempe, AZ 85287-1006 Elizabeth.Dunham at asu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From lammrl at lamaritimemuseum.org Mon Mar 10 18:41:13 2014 From: lammrl at lamaritimemuseum.org (Liz Ruth) Date: Mon, 10 Mar 2014 15:41:13 -0700 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update Message-ID: <1C0CA8A3B2C7484E805911D98833B5B9.MAI@sanpedro.net> An HTML attachment was scrubbed... URL: From lammrl at lamaritimemuseum.org Mon Mar 10 19:17:12 2014 From: lammrl at lamaritimemuseum.org (Liz Ruth) Date: Mon, 10 Mar 2014 16:17:12 -0700 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update Message-ID: An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Tue Mar 11 05:39:34 2014 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Tue, 11 Mar 2014 09:39:34 +0000 Subject: [Archivesspace_Users_Group] Can't delete guide under mysql: foreign key constraint. In-Reply-To: References: Message-ID: <1fc03c9ff62b499a8ed9d319c86d95dd@BLUPR08MB343.namprd08.prod.outlook.com> Hi Steven, Thanks for this. This is indeed a bug, I've replicated this, and I have made a ticket? here => https://www.pivotaltracker.com/story/show/67289478 MySQL needs to be explicitly told to perform a cascade delete, so that all the children are deleted with the parent. This slipped through because the test suite runs on derby. Will get a fix in for this for an upcoming release... The work around now is to delete the children first then the parent. ?Apologize about the inconvenience. Thanks again! very much appreciated. best, chris fitzpatrick Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Steven Majewski Sent: Monday, March 10, 2014 9:55 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Can't delete guide under mysql: foreign key constraint. With ArchivesSpace 1.0.7.1 using mysql, I Imported an EAD guide and then tried to delete it. If I try to delete the collection from the View of Edit page, I get: We're sorry, but something went wrong. If I try to delete my checking it in the browse page and clicking delete, I get: Unable to delete records: ["{\"error\":\"Record deletion failed: Java::ComMysqlJdbcExceptionsJdbc4::MySQLIntegrityConstraintViolationException: Cannot delete or update a parent row: a foreign key constraint fails (`archivesspace/archival_object`, CONSTRAINT `archival_object_ibfk_5` FOREIGN KEY (`parent_id`) REFERENCES `archival_object` (`id`))\"}\n"] [/repositories/2/resources/3719] I was finally able to delete the collection only after individually deleting all of it's components. I tried with another install of 1.0.7.1 on my laptop, using the development db instead of mysql. I imported EAD and then deleted the top level collection with no problem. Then I reconfigured it to use mysql, and I get the same errors as above. - Steve Majewski -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Tue Mar 11 08:41:13 2014 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Tue, 11 Mar 2014 12:41:13 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update In-Reply-To: References: Message-ID: <989b92139589445b84b46c0da1e4b057@BLUPR08MB343.namprd08.prod.outlook.com> Hi Liz, You are still having problems logging in? It sounds possibly like a sporadic thing? ? One thing I might check is if your desktop and server are both syncing their time correctly. And what browser are you using? best,chris. Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Liz Ruth Sent: Tuesday, March 11, 2014 12:17 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update Chris, Now I can get in, but it seems to be erratic. My apologies. Sincerely, Liz Liz Ruth-Abramian Archivist/Librarian Los Angeles Maritime Museum Berth 84 Foot of Sixth Street San Pedro, CA 90731 T. 310-548-7618 x. 215 F. 310-832-6537 website: lamaritimemuseum.org blog: http://www.maritimehistoryadventures.blogspot.com ----- Original Message ----- From: Liz Ruth [mailto:lammrl at lamaritimemuseum.org] To: archivesspace_users_group at lyralists.lyrasis.org Sent: Mon, 10 Mar 2014 15:41:13 -0700 Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update Chris, Would that cover problems like I have with not being able to log in at all now that I upgraded to version 1.0.7? Thanks, Liz Liz Ruth-Abramian Archivist/Librarian Los Angeles Maritime Museum Berth 84 Foot of Sixth Street San Pedro, CA 90731 T. 310-548-7618 x. 215 F. 310-832-6537 website: lamaritimemuseum.org blog: http://www.maritimehistoryadventures.blogspot.com ----- Original Message ----- From: Chris Fitzpatrick [mailto:Chris.Fitzpatrick at lyrasis.org] To: archivesspace_member_reps at lyralists.lyrasis.org,archivesspace_users_group at lyralists.lyrasis.org,archivesspace at googlegroups.com,archivesspace_tac_members at lyralists.lyrasis.org Sent: Fri, 7 Mar 2014 13:00:25 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update Hi All, We discovered a bug in the recently released v1.0.7 version of ArchivesSpace that was causing issues with most browsers on the Staff UI, specifically with the ability to add agent relationships in the Agent edit form. Considering this is a blocker for a major piece of functionality, we have pulled v1.0.7 and issued a new version v1.0.7.1 that fixes this issue. You can download the updated version here : https://github.com/archivesspace/archivesspace/releases/tag/v1.0.7.1 With the upgrade guide at: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING.md? We apologize about this inconvenience. Test coverage has been updated to ensure this is avoided in the future. Please let me know if you have any questions... best regards, Chris Fitzpatrick Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From lammrl at lamaritimemuseum.org Tue Mar 11 11:23:15 2014 From: lammrl at lamaritimemuseum.org (Liz Ruth) Date: Tue, 11 Mar 2014 08:23:15 -0700 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update Message-ID: <3744C9135A56485AA6DF5C960708286C.MAI@sanpedro.net> An HTML attachment was scrubbed... URL: From lammrl at lamaritimemuseum.org Tue Mar 11 15:04:47 2014 From: lammrl at lamaritimemuseum.org (Liz Ruth) Date: Tue, 11 Mar 2014 12:04:47 -0700 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update + more Tuesday March 11 Message-ID: An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Tue Mar 11 22:46:57 2014 From: sdm7g at virginia.edu (Steven Majewski) Date: Tue, 11 Mar 2014 22:46:57 -0400 Subject: [Archivesspace_Users_Group] daogrp ? Message-ID: No digital objects were created on importing my EAD. From the import mappings Data Import and Export Maps it appears that , , & all have assigned mappings, but I only see a template for ?dao? in ead_converter.rb. We are using in our files, as typically we have links to several page images that make up a letter. ( This will likely change as those images do into our repository and become part of a Fedora object. ) As a test, I?ve tried in one file, removing the ?s and turning the ?s into ?s, but I get this error: Error: Unexpected Object Type in Queue: Expected archival_object got file_version Import Mapping for Resources from EAD2002 to ArchivesSpace Last Updated: 8/31/13 DAO's instance.instance_type = digital_object @title instance.digital_object.title @role instance.digital_object.file_versions[].use_statement @href instance.digital_object.file_versions[].uri @actuate instance.digital_object.file_versions[].xlink_actuate_attribute @show instance.digital_object.file_versions[].xlink_show_attribute EACH within treated as individual file_versions within a single digital_object instance. instance.instance_type = digital_object Should these end up being components? @role instance.digital_object.file_versions[].use_statement @href instance.digital_object.file_versions[].uri @label instance.digital_object.file_versions[].title instance.digital_object.title -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: From Chris.Fitzpatrick at lyrasis.org Thu Mar 13 04:29:43 2014 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 13 Mar 2014 08:29:43 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update + more Tuesday March 11 In-Reply-To: References: Message-ID: Hi Liz, This is definitely not good. ?...So, you are not able to log into at all in the updated version of the application? What version are you able to log into? Just as a sanity check, would it be possible for you to try and 1) log in with a different browser (not IE)? and 2) try and log in from a different computer? And, this started happening again this week? There might be a chance either your computer or the server have not had their time updated since the time change. This can throw off the permission cookie being set. Can you check that both your computer and the server have updated their time settings? best, chris. Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Liz Ruth Sent: Tuesday, March 11, 2014 8:04 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update + more Tuesday March 11 Chris, I need to access by the earlier version, or I can't get in. Also, should I leave my session without activity for an hour, I get shut out. This is difficult, to lose a lot of work because of having to leave the application opne for a while. Sincerely, Liz Liz Ruth-Abramian Archivist/Librarian Los Angeles Maritime Museum Berth 84 Foot of Sixth Street San Pedro, CA 90731 T. 310-548-7618 x. 215 F. 310-832-6537 website: lamaritimemuseum.org blog: http://www.maritimehistoryadventures.blogspot.com ----- Original Message ----- From: Chris Fitzpatrick [mailto:Chris.Fitzpatrick at lyrasis.org] To: archivesspace_users_group at lyralists.lyrasis.org Sent: Tue, 11 Mar 2014 12:41:13 +0000 Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update Hi Liz, You are still having problems logging in? It sounds possibly like a sporadic thing? ? One thing I might check is if your desktop and server are both syncing their time correctly. And what browser are you using? best,chris. Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Liz Ruth Sent: Tuesday, March 11, 2014 12:17 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update Chris, Now I can get in, but it seems to be erratic. My apologies. Sincerely, Liz Liz Ruth-Abramian Archivist/Librarian Los Angeles Maritime Museum Berth 84 Foot of Sixth Street San Pedro, CA 90731 T. 310-548-7618 x. 215 F. 310-832-6537 website: lamaritimemuseum.org blog: http://www.maritimehistoryadventures.blogspot.com ----- Original Message ----- From: Liz Ruth [mailto:lammrl at lamaritimemuseum.org] To: archivesspace_users_group at lyralists.lyrasis.org Sent: Mon, 10 Mar 2014 15:41:13 -0700 Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update Chris, Would that cover problems like I have with not being able to log in at all now that I upgraded to version 1.0.7? Thanks, Liz Liz Ruth-Abramian Archivist/Librarian Los Angeles Maritime Museum Berth 84 Foot of Sixth Street San Pedro, CA 90731 T. 310-548-7618 x. 215 F. 310-832-6537 website: lamaritimemuseum.org blog: http://www.maritimehistoryadventures.blogspot.com ----- Original Message ----- From: Chris Fitzpatrick [mailto:Chris.Fitzpatrick at lyrasis.org] To: archivesspace_member_reps at lyralists.lyrasis.org,archivesspace_users_group at lyralists.lyrasis.org,archivesspace at googlegroups.com,archivesspace_tac_members at lyralists.lyrasis.org Sent: Fri, 7 Mar 2014 13:00:25 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.0.7.1 patch update Hi All, We discovered a bug in the recently released v1.0.7 version of ArchivesSpace that was causing issues with most browsers on the Staff UI, specifically with the ability to add agent relationships in the Agent edit form. Considering this is a blocker for a major piece of functionality, we have pulled v1.0.7 and issued a new version v1.0.7.1 that fixes this issue. You can download the updated version here : https://github.com/archivesspace/archivesspace/releases/tag/v1.0.7.1 With the upgrade guide at: https://github.com/archivesspace/archivesspace/blob/master/UPGRADING.md? We apologize about this inconvenience. Test coverage has been updated to ensure this is avoided in the future. Please let me know if you have any questions... best regards, Chris Fitzpatrick Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Claire.Knowles at ed.ac.uk Thu Mar 13 04:48:19 2014 From: Claire.Knowles at ed.ac.uk (KNOWLES Claire) Date: Thu, 13 Mar 2014 08:48:19 +0000 Subject: [Archivesspace_Users_Group] AuthFileNumber for EAD import Message-ID: Hi, We are currently investigating how we will link to our authority data (subjects) within Archives Space when importing EAD. We would like to use the authfilenumber, but from our tests it appears to be ignored in the EAD import and it is commented out of lib_ead_converter.rb. Can you let us know when this will be implemented? Thanks Claire Claire Knowles Library Digital Development Manager Library and University Collections University of Edinburgh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: not available URL: From bmg17 at psu.edu Thu Mar 13 12:04:05 2014 From: bmg17 at psu.edu (Ben Goldman) Date: Thu, 13 Mar 2014 12:04:05 -0400 (EDT) Subject: [Archivesspace_Users_Group] construct unique ref IDs In-Reply-To: <858757066.1004797.1394640126004.JavaMail.zimbra@psu.edu> Message-ID: <1228613970.1419219.1394726645540.JavaMail.zimbra@psu.edu> Hello, I see this made it into the newest release, https://www.pivotaltracker.com/s/projects/386247/stories/49569471, but after a cursory search of the staff interface, I am unclear how to actually go about using this feature. Any direction you can provide is appreciated. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Fri Mar 14 05:40:05 2014 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Fri, 14 Mar 2014 09:40:05 +0000 Subject: [Archivesspace_Users_Group] construct unique ref IDs In-Reply-To: <1228613970.1419219.1394726645540.JavaMail.zimbra@psu.edu> References: <858757066.1004797.1394640126004.JavaMail.zimbra@psu.edu>, <1228613970.1419219.1394726645540.JavaMail.zimbra@psu.edu> Message-ID: <3227463d6d304d449f2d71a52bf518c8@BLUPR08MB343.namprd08.prod.outlook.com> Hi Ben, Yes, the refid rules have been implemented as a plugin. The documentation is here : https://github.com/archivesspace/archivesspace/tree/master/plugins/refid_rules So, to enable this, edit the config/config.rb file to load the plugin (about line 102) : AppConfig[:plugins] = ['refid_rules', 'local'] Then, define the rule that you want to use in the config/config.rb. For example: AppConfig[:refid_rule] = "<%= repository['repo_code'] %>_<%= resource['formatted_id'] %>_<%= SecureRandom.hex %>" This is using a templating languaged call ERB, so you can call variables with-in a <%= %> block. You can do something like: AppConfig[:refid_rule] = "Bananas_<%= SecureRandom.hex %>" Which would generate a RefID like "Bananas_" + a randomly generated hexadecimal. Does this make sense? Let me know if you have any questions... best, chris. Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Ben Goldman Sent: Thursday, March 13, 2014 5:04 PM To: archivesspace users group Subject: [Archivesspace_Users_Group] construct unique ref IDs Hello, I see this made it into the newest release, https://www.pivotaltracker.com/s/projects/386247/stories/49569471, but after a cursory search of the staff interface, I am unclear how to actually go about using this feature. Any direction you can provide is appreciated. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ns96 at nyu.edu Fri Mar 14 09:51:54 2014 From: ns96 at nyu.edu (Nathan Stevens) Date: Fri, 14 Mar 2014 09:51:54 -0400 Subject: [Archivesspace_Users_Group] published/unpublished (observations based on using migration tool for AT records) In-Reply-To: References: Message-ID: OK we will take a look and probable have an updated migration tool for testing in a couple weeks. On Mon, Mar 10, 2014 at 2:35 PM, Christine Di Bella wrote: > I used the migration tool to import records from my Archivists' Toolkit > instance to my ArchivesSpace 1.0.7.1 testing instance. I have a few > questions related to publishing information in the Public Interface. > > ? It seems that, when using the migration tool, Digital Objects are > set to publish by default, whereas Resources and Accessions are set to > not be published by default. Is there are way to change this? It seems > like this behavior should be consistent across the three types of records. > > ? Though when one publishes a record for the first time all the > lower levels inherit that setting, I've found that if I decide to > unpublish a previously published record, lower levels do not inherit that > setting and listings still appear via Browse or Search in the Public > Interface, which means I would need to unpublish each component individual > ly to make them go away. That said, clicking on the listing in the public > interface brings up the "Sorry, something went wrong" screen, so > something in the system knows that it's not supposed to be shown. (If I > manually update the component to be unpublished, it disappears from the > Public Interface entirely as expected.) A previously published record > that is later suppressed exhibits the same behavior, as well as still > being listed at the top level - clicking on the listing yields a screen > that says "Record Not Found. The record you've tried to access does not > exist or may have been removed." . > > ? Following off of both of these things, is there a way to bulk > update records to be published or unpublished, or a thought to providing > this functionality in the future? > > Thanks, > > Christine > > Christine Di Bella > Archivist > Shelby White and Leon Levy Archives Center > Institute for Advanced Study > Einstein Drive > Princeton, NJ 08540 > > Email : *cdibella at ias.edu* > Phone: 609-734-8368 > Website : *http://library.ias.edu/archives* > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Nathan Stevens Programmer/Analyst Digital Library Technology Services New York University 1212-998-2653 ns96 at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmg17 at psu.edu Fri Mar 14 10:15:26 2014 From: bmg17 at psu.edu (Ben Goldman) Date: Fri, 14 Mar 2014 10:15:26 -0400 (EDT) Subject: [Archivesspace_Users_Group] construct unique ref IDs In-Reply-To: <3227463d6d304d449f2d71a52bf518c8@BLUPR08MB343.namprd08.prod.outlook.com> References: <858757066.1004797.1394640126004.JavaMail.zimbra@psu.edu> <1228613970.1419219.1394726645540.JavaMail.zimbra@psu.edu> <3227463d6d304d449f2d71a52bf518c8@BLUPR08MB343.namprd08.prod.outlook.com> Message-ID: <2091562568.1653483.1394806526827.JavaMail.zimbra@psu.edu> Thanks! ----- Original Message ----- From: "Chris Fitzpatrick" To: "archivesspace users group" Sent: Friday, March 14, 2014 5:40:05 AM Subject: Re: [Archivesspace_Users_Group] construct unique ref IDs Hi Ben, Yes, the refid rules have been implemented as a plugin. The documentation is here : https://github.com/archivesspace/archivesspace/tree/master/plugins/refid_rules So, to enable this, edit the config/config.rb file to load the plugin (about line 102) : AppConfig[:plugins] = ['refid_rules', 'local'] Then, define the rule that you want to use in the config/config.rb. For example: AppConfig[:refid_rule] = "<%= repository['repo_code'] %>_<%= resource['formatted_id'] %>_<%= SecureRandom.hex %>" This is using a templating languaged call ERB, so you can call variables with-in a <%= %> block. You can do something like: AppConfig[:refid_rule] = "Bananas_<%= SecureRandom.hex %>" Which would generate a RefID like "Bananas_" + a randomly generated hexadecimal. Does this make sense? Let me know if you have any questions... best, chris. Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Ben Goldman Sent: Thursday, March 13, 2014 5:04 PM To: archivesspace users group Subject: [Archivesspace_Users_Group] construct unique ref IDs Hello, I see this made it into the newest release, https://www.pivotaltracker.com/s/projects/386247/stories/49569471, but after a cursory search of the staff interface, I am unclear how to actually go about using this feature. Any direction you can provide is appreciated. 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 lammrl at lamaritimemuseum.org Fri Mar 14 15:22:59 2014 From: lammrl at lamaritimemuseum.org (Liz Ruth) Date: Fri, 14 Mar 2014 12:22:59 -0700 Subject: [Archivesspace_Users_Group] construct unique ref IDs Message-ID: <67BB0A5E28F64F8DB37865028257B15F.MAI@sanpedro.net> An HTML attachment was scrubbed... URL: From cdibella at ias.edu Mon Mar 17 12:10:44 2014 From: cdibella at ias.edu (Christine Di Bella) Date: Mon, 17 Mar 2014 12:10:44 -0400 (EDT) Subject: [Archivesspace_Users_Group] search behavior Message-ID: <4c135136.00001554.0000000f@LHLSANXA.itg.ias.edu> (Apologies if this has been answered before.) Now that I have more data in my test ArchivesSpace instance, I'm noticing things that I'm sure have been there all along and I just didn't realize it. Is the search engine on ArchivesSpace set up as an "OR" rather than an "AND"? Any multi-word search I do pulls up way more results than I would have expected, i.e. any record of any type that has any of the words included. (Perhaps this may also be part of the reason that provided LCNAF plugin seems to be virtually unusable?) Since Google and its ilk have spoiled many of us, I'm sure I'm not alone in saying an "AND" search would be more useful. I do see that I can use quotation marks or "and" between search terms to further focus searches for my own records (though doing so seems to have no effect on the LCNAF plugin). That's definitely helpful. Is this the intended behavior? Are more advanced search and faceting browsing capabilities intended for near term future releases? Best, Christine Christine Di Bella Archivist Shelby White and Leon Levy Archives Center Institute for Advanced Study Einstein Drive Princeton, NJ 08540 Email : cdibella at ias.edu Phone: 609-734-8368 Website : http://library.ias.edu/archives -------------- next part -------------- An HTML attachment was scrubbed... URL: From rneal at richmond.edu Mon Mar 17 12:52:48 2014 From: rneal at richmond.edu (Neal, Rick) Date: Mon, 17 Mar 2014 16:52:48 +0000 Subject: [Archivesspace_Users_Group] Question concerning installation directory Message-ID: <82E1D707847BFD40976E2E16B04C62C3EE409C06@quorra.richmond.edu> Good afternoon, I will shortly be installing ArchiveSpace on a Linux server. I downloaded the application but cannot find any information on where I should unzip the application for the install. Can someone tell me which directory should I install from? (ie /usr/local or /tmp or some other directory) Thanks, Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Rick Neal Library Applications and Systems Administrator Boatwright Memorial Library University of Richmond, VA 23173 rneal at richmond.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.rush at yale.edu Wed Mar 19 14:05:39 2014 From: michael.rush at yale.edu (Rush, Michael) Date: Wed, 19 Mar 2014 18:05:39 +0000 Subject: [Archivesspace_Users_Group] Event type associations with record types Message-ID: Hello, I'm reviewing the available event type values for both accessions and resources. As far as I can tell, all of the available event types are available for association with resources and digital objects, but only six values (Acknowledgment Sent, Agreement Signed, Agreement Sent, Cataloged, Copyright Transfer, and Processed) are available for association with accessions. Is this by design or a bug? If by design, how can we specify which event types may be associated with a given record type? Thanks, Mike _____________________________________ Michael Rush Accessioning Archivist Beinecke Rare Book and Manuscript Library Yale University 203-432-8123 The Beinecke Rare Book & Manuscript Library will close for a major renovation in May 2015, reopening in August 2016. ?We will maintain a reading room in Sterling Memorial Library during this time, but access to various collections will be limited as early as April 2014 while we prepare for closure. For details, please visit?our renovation website. From PGalligan at rockarch.org Fri Mar 21 12:09:27 2014 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Fri, 21 Mar 2014 12:09:27 -0400 Subject: [Archivesspace_Users_Group] AT to ASpace Migration -- Digital Object Date Label Message-ID: In migrating our Digital Objects from AT to ArchivesSpace using the migration plugin, we noticed that the Digital Object Date Label defaults to "digitized" in ArchivesSpace. So where our Digital Objects in AT might have a Date Begin in 1950 and Date End in 1951, ArchivesSpace now defaults to displaying those dates as the dates the materials were digitized. Is there any way to change this default label? It really isn't ideal for us to have all of the DOs default to a digitized date, as that is not the information that we have been putting in the Date boxes in AT. -Patrick Galligan -------------- next part -------------- An HTML attachment was scrubbed... URL: From JacobDB at vmi.edu Wed Mar 26 11:47:13 2014 From: JacobDB at vmi.edu (Jacob, Diane B.) Date: Wed, 26 Mar 2014 15:47:13 +0000 Subject: [Archivesspace_Users_Group] Error message in saving record Message-ID: <445643DE838938489E0EBC1D2FDBAEF18ABBAF1F@LEE04.vmi.edu> I'm having trouble saving a record. This occurred after I was adding two instances - one physical, and one digital object. I added the digital object first, saved the record, and all was well. After I added the second instance, I received the error. I have deleted the record and created it again, but the same pattern occurs. Can someone help explain what's happening here? translation missing: en.no key - translation missing: en.validation_errors.database_integrity_constraint_conflict__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__cannot_delete_or_update_a_parent_row__a_foreign_key_constraint_fails_(`archivesspaceram`.`instance_do_link_rlshp`__constraint_`instance_do_link_rlshp_ibfk_2`_foreign_key_(`instance_id`)_references_`instance`_(`id`)) Thanks, Diane Diane B. Jacob Head, Archives & Records Management Virginia Military Institute Preston Library Lexington, VA 24450 540-464-7566 www.vmi.edu/archives -------------- next part -------------- An HTML attachment was scrubbed... URL: From aimee_brown at mcad.edu Wed Mar 26 16:11:01 2014 From: aimee_brown at mcad.edu (Aimee Brown) Date: Wed, 26 Mar 2014 15:11:01 -0500 Subject: [Archivesspace_Users_Group] Corporate entity agent record / associative relationship records problem Message-ID: Hi, A corporate entity agent record for the name of an organization has so many (60 or so) associative relationship records connected to it (from agent records for individuals associated with the organization) that it is very slow to load and produces an error message sometimes when viewed. Is anyone else having this problem? Thanks. Aimee Aimee Brown, CA Archivist Library, Room 113 Minneapolis College of Art and Design 2501 Stevens Avenue Minneapolis, MN 55404 (612) 874-3660 aimee_brown at mcad.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Thu Mar 27 12:13:25 2014 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 27 Mar 2014 16:13:25 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace hackfest/meetup TODAY! Message-ID: <6e6f0d6cdc3946ccb909bd72ecb3dfe9@DM2PR08MB351.namprd08.prod.outlook.com> <<<< forgive the cross posting...>>>> Hi everyone, In Raleigh for this afternoon? If so, please feel free to stop by the ArchivesSpace hackfest/meetup that we're hosting today at 1pm. We will be in Magnolia 1, which is on the first floor of the Sheraton. We will be going over some install and deployment for ArchivesSpace, as well as going over migration and plugins architecture. All are welcome. See you this afternoon! best, chris fitzpatrick ArchivesSpace Developer http://archivesspace.org? Chris Fitzpatrick | chris.fitzpatrick at lyrasis.org Developer, ArchivesSpace http://archivesspace.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From eliam at buffalo.edu Fri Mar 28 11:41:35 2014 From: eliam at buffalo.edu (Elia, Marie) Date: Fri, 28 Mar 2014 15:41:35 +0000 Subject: [Archivesspace_Users_Group] Error importing EAD file Message-ID: Hi, all, We just became members and installed ArchivesSpace. We had been using a test instance. I created two collections in the test instance and exported the EAD files before we installed the supported version. When I try to import the files back in, I get this error: "Error: undefined method `container' for #." I can import our legacy EAD files, just not the ones created in the test instance. Any ideas? Thanks! Marie Elia Processing Archivist The Poetry Collection University at Buffalo State University of New York 420 Capen Hall Buffalo, NY 14260-1674 eliam at buffalo.edu (716) 645-1370 library.buffalo.edu/pl -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Fri Mar 28 12:04:46 2014 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Fri, 28 Mar 2014 16:04:46 +0000 Subject: [Archivesspace_Users_Group] Error importing EAD file In-Reply-To: References: Message-ID: <24301e18160844a3ae30a8a6a78fd038@BLUPR08MB102.namprd08.prod.outlook.com> Hi, Marie, Could you send the two EADs, in a zip file, Chris Fitzpatrick (chris.fitzpatrick at lyrasis.org) and me (brad.westbrook at lyrasis.org)? We'll investigate and then report back. Please indicate the ASpace version for the test instance, also. Thanks, Brad From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Elia, Marie Sent: Friday, March 28, 2014 11:42 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Error importing EAD file Hi, all, We just became members and installed ArchivesSpace. We had been using a test instance. I created two collections in the test instance and exported the EAD files before we installed the supported version. When I try to import the files back in, I get this error: "Error: undefined method `container' for #." I can import our legacy EAD files, just not the ones created in the test instance. Any ideas? Thanks! Marie Elia Processing Archivist The Poetry Collection University at Buffalo State University of New York 420 Capen Hall Buffalo, NY 14260-1674 eliam at buffalo.edu (716) 645-1370 library.buffalo.edu/pl -------------- next part -------------- An HTML attachment was scrubbed... URL: From Cyndi.Shein at unlv.edu Fri Mar 28 12:32:10 2014 From: Cyndi.Shein at unlv.edu (Cyndi.Shein at unlv.edu) Date: Fri, 28 Mar 2014 09:32:10 -0700 Subject: [Archivesspace_Users_Group] PDF export from ASpace? Message-ID: Hi All, We're in the process of implementing ArchivesSpace. We've installed a local instance. We'd like to begin managing accessions and resources in ArchivesSpace ASAP, but are not planning to go public with the web interface until we have the database largely populated. Meanwhile, we need a way to get a human-readable finding aid (preferably PDF) out of the database during the transition between now and when we go public. I looked through the ArchivesSpace members' documentation. I can't seem to figure out how to export a pdf of an accession or resource record. If the option is there and I'm just not seeing it, would somebody point me in the right direction? I noticed the Google Group discussion last May indicated that the developers were looking for someone to create a style sheet to transform ArchivesSpace's exported EAD into a PDF. Is that style sheet available to members yet? Many thanks, Cyndi Shein Head, Special Collections Technical Services University Libraries, University of Nevada, Las Vegas cyndi.shein at unlv.edu (702) 895-2223 -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.rush at yale.edu Fri Mar 28 15:30:55 2014 From: michael.rush at yale.edu (Rush, Michael) Date: Fri, 28 Mar 2014 19:30:55 +0000 Subject: [Archivesspace_Users_Group] Inconsistent Accession Identifer display Message-ID: All, I've noticed that way in which multi-part accession identifiers is displayed is inconsistent. First, the segments of the accession number display as part of the accession title, both in the title column in any list of accessions and across the top of the accession record. I personally don't think the identifier should be included in the accession title in this way, but it's confusing because the identifier segments are separated by commas in that context. In the Identifier column of a list of accessions, the segments are separated by dashes. I think it would be helpful to display accession identifiers more consistently. My personal preference would be to remove them from displays of accession titles altogether, but if the community consensus is to keep them there, they should be consistent with display elsewhere and dash-separated. Has anyone else noticed this? Thoughts? Mike _____________________________________ Michael Rush Accessioning Archivist Beinecke Rare Book and Manuscript Library Yale University 203-432-8123 The Beinecke Rare Book and Manuscript Library will close for a major renovation in May 2015, reopening in August 2016. ?We will maintain a reading room in Sterling Memorial Library during this time, but access to various collections will be limited as early as April 2014 while we prepare for closure. For details, please visit?our renovation website at http://beineckelibraryrenovation.yale.edu/. From cdibella at ias.edu Fri Mar 28 16:03:55 2014 From: cdibella at ias.edu (Christine Di Bella) Date: Fri, 28 Mar 2014 16:03:55 -0400 (EDT) Subject: [Archivesspace_Users_Group] Inconsistent Accession Identifer display Message-ID: I've noticed this as well, and have also noted that neither matches the default display in Archivists' Toolkit, which separates the segments by a period. Taking them out of the collection title display, and consistency elsewhere, or, preferably, the ability to customize these displays, would be my preference. This goes for Resource identifiers, whose segments are also separated by dashes in ASpace and periods in AT, too. Small in the grand scheme of things, of course, but would be nice. :) Christine Christine Di Bella Archivist Shelby White and Leon Levy Archives Center Institute for Advanced Study Einstein Drive Princeton, NJ 08540 Email : cdibella at ias.edu Phone: 609-734-8368 Website : http://library.ias.edu/archives -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Rush, Michael Sent: Friday, March 28, 2014 3:31 PM To: Archivesspace_Users_Group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Inconsistent Accession Identifer display All, I've noticed that way in which multi-part accession identifiers is displayed is inconsistent. First, the segments of the accession number display as part of the accession title, both in the title column in any list of accessions and across the top of the accession record. I personally don't think the identifier should be included in the accession title in this way, but it's confusing because the identifier segments are separated by commas in that context. In the Identifier column of a list of accessions, the segments are separated by dashes. I think it would be helpful to display accession identifiers more consistently. My personal preference would be to remove them from displays of accession titles altogether, but if the community consensus is to keep them there, they should be consistent with display elsewhere and dash-separated. Has anyone else noticed this? Thoughts? Mike _____________________________________ Michael Rush Accessioning Archivist Beinecke Rare Book and Manuscript Library Yale University 203-432-8123 The Beinecke Rare Book and Manuscript Library will close for a major renovation in May 2015, reopening in August 2016. ?We will maintain a reading room in Sterling Memorial Library during this time, but access to various collections will be limited as early as April 2014 while we prepare for closure. For details, please visit?our renovation website at http://beineckelibraryrenovation.yale.edu/. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From prom at illinois.edu Fri Mar 28 16:08:26 2014 From: prom at illinois.edu (Prom, Christopher John) Date: Fri, 28 Mar 2014 20:08:26 +0000 Subject: [Archivesspace_Users_Group] Inconsistent Accession Identifer display In-Reply-To: References: Message-ID: <154709B8-68D6-402C-9528-792798CC3D29@illinois.edu> The default separator for ID segments in Archon is a forward slash, so +1 for making these configurable. There may already be a way to do it, but I have not had time to research the issue. Chris Prom University of Illinois On Mar 28, 2014, at 3:03 PM, Christine Di Bella wrote: > I've noticed this as well, and have also noted that neither matches the > default display in Archivists' Toolkit, which separates the segments by a > period. Taking them out of the collection title display, and consistency > elsewhere, or, preferably, the ability to customize these displays, would > be my preference. This goes for Resource identifiers, whose segments are > also separated by dashes in ASpace and periods in AT, too. > > Small in the grand scheme of things, of course, but would be nice. :) > > Christine > > Christine Di Bella > Archivist > Shelby White and Leon Levy Archives Center > Institute for Advanced Study > Einstein Drive > Princeton, NJ 08540 > Email : cdibella at ias.edu > Phone: 609-734-8368 > Website : http://library.ias.edu/archives > > > -----Original Message----- > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf > Of Rush, Michael > Sent: Friday, March 28, 2014 3:31 PM > To: Archivesspace_Users_Group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] Inconsistent Accession Identifer > display > > All, > > I've noticed that way in which multi-part accession identifiers is > displayed is inconsistent. > > First, the segments of the accession number display as part of the > accession title, both in the title column in any list of accessions and > across the top of the accession record. I personally don't think the > identifier should be included in the accession title in this way, but it's > confusing because the identifier segments are separated by commas in that > context. In the Identifier column of a list of accessions, the segments > are separated by dashes. > > I think it would be helpful to display accession identifiers more > consistently. My personal preference would be to remove them from > displays of accession titles altogether, but if the community consensus is > to keep them there, they should be consistent with display elsewhere and > dash-separated. > > Has anyone else noticed this? Thoughts? > > Mike > > _____________________________________ > Michael Rush > Accessioning Archivist > Beinecke Rare Book and Manuscript Library Yale University > 203-432-8123 > > The Beinecke Rare Book and Manuscript Library will close for a major > renovation in May 2015, reopening in August 2016. We will maintain a > reading room in Sterling Memorial Library during this time, but access to > various collections will be limited as early as April 2014 while we > prepare for closure. For details, please visit our renovation website at > http://beineckelibraryrenovation.yale.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 From schmitt at umd.edu Fri Mar 28 16:16:32 2014 From: schmitt at umd.edu (Cassandra A Schmitt) Date: Fri, 28 Mar 2014 20:16:32 +0000 Subject: [Archivesspace_Users_Group] Inconsistent Accession Identifer display In-Reply-To: <154709B8-68D6-402C-9528-792798CC3D29@illinois.edu> References: , <154709B8-68D6-402C-9528-792798CC3D29@illinois.edu> Message-ID: I had also sent in a request including some screenshots for what Mike is describing a few weeks ago, so I think it is on the radar somewhere. I would agree that the preference would be to remove the number from the title display and rely on the identifier column. (and I also dislike the commas.) -Cassie ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Prom, Christopher John [prom at illinois.edu] Sent: Friday, March 28, 2014 4:08 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Inconsistent Accession Identifer display The default separator for ID segments in Archon is a forward slash, so +1 for making these configurable. There may already be a way to do it, but I have not had time to research the issue. Chris Prom University of Illinois On Mar 28, 2014, at 3:03 PM, Christine Di Bella wrote: > I've noticed this as well, and have also noted that neither matches the > default display in Archivists' Toolkit, which separates the segments by a > period. Taking them out of the collection title display, and consistency > elsewhere, or, preferably, the ability to customize these displays, would > be my preference. This goes for Resource identifiers, whose segments are > also separated by dashes in ASpace and periods in AT, too. > > Small in the grand scheme of things, of course, but would be nice. :) > > Christine > > Christine Di Bella > Archivist > Shelby White and Leon Levy Archives Center > Institute for Advanced Study > Einstein Drive > Princeton, NJ 08540 > Email : cdibella at ias.edu > Phone: 609-734-8368 > Website : http://library.ias.edu/archives > > > -----Original Message----- > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf > Of Rush, Michael > Sent: Friday, March 28, 2014 3:31 PM > To: Archivesspace_Users_Group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] Inconsistent Accession Identifer > display > > All, > > I've noticed that way in which multi-part accession identifiers is > displayed is inconsistent. > > First, the segments of the accession number display as part of the > accession title, both in the title column in any list of accessions and > across the top of the accession record. I personally don't think the > identifier should be included in the accession title in this way, but it's > confusing because the identifier segments are separated by commas in that > context. In the Identifier column of a list of accessions, the segments > are separated by dashes. > > I think it would be helpful to display accession identifiers more > consistently. My personal preference would be to remove them from > displays of accession titles altogether, but if the community consensus is > to keep them there, they should be consistent with display elsewhere and > dash-separated. > > Has anyone else noticed this? Thoughts? > > Mike > > _____________________________________ > Michael Rush > Accessioning Archivist > Beinecke Rare Book and Manuscript Library Yale University > 203-432-8123 > > The Beinecke Rare Book and Manuscript Library will close for a major > renovation in May 2015, reopening in August 2016. We will maintain a > reading room in Sterling Memorial Library during this time, but access to > various collections will be limited as early as April 2014 while we > prepare for closure. For details, please visit our renovation website at > http://beineckelibraryrenovation.yale.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 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From CurbowJ at bvu.edu Fri Mar 28 16:35:01 2014 From: CurbowJ at bvu.edu (Joan Curbow) Date: Fri, 28 Mar 2014 20:35:01 +0000 Subject: [Archivesspace_Users_Group] Inconsistent Accession Identifer display In-Reply-To: References: Message-ID: <77B81078A4B47D4A9B2EFCF5EAE6FF4F5E3450@MAILBOX1.domain1.bvu.edu> I noticed that, too, and asked about it. The designers are aware of this glitch and have plans to remove the identifier (with the annoying comma separation) from the title display. At some point. -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Rush, Michael Sent: Friday, March 28, 2014 2:31 PM To: Archivesspace_Users_Group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Inconsistent Accession Identifer display All, I've noticed that way in which multi-part accession identifiers is displayed is inconsistent. First, the segments of the accession number display as part of the accession title, both in the title column in any list of accessions and across the top of the accession record. I personally don't think the identifier should be included in the accession title in this way, but it's confusing because the identifier segments are separated by commas in that context. In the Identifier column of a list of accessions, the segments are separated by dashes. I think it would be helpful to display accession identifiers more consistently. My personal preference would be to remove them from displays of accession titles altogether, but if the community consensus is to keep them there, they should be consistent with display elsewhere and dash-separated. Has anyone else noticed this? Thoughts? Mike _____________________________________ Michael Rush Accessioning Archivist Beinecke Rare Book and Manuscript Library Yale University 203-432-8123 The Beinecke Rare Book and Manuscript Library will close for a major renovation in May 2015, reopening in August 2016. ?We will maintain a reading room in Sterling Memorial Library during this time, but access to various collections will be limited as early as April 2014 while we prepare for closure. For details, please visit?our renovation website at http://beineckelibraryrenovation.yale.edu/. _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From brad.westbrook at lyrasis.org Fri Mar 28 16:37:59 2014 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Fri, 28 Mar 2014 20:37:59 +0000 Subject: [Archivesspace_Users_Group] Inconsistent Accession Identifer display In-Reply-To: References: , <154709B8-68D6-402C-9528-792798CC3D29@illinois.edu> Message-ID: <53b3a2d13307469abda8d60c0aeaae21@BLUPR08MB102.namprd08.prod.outlook.com> Hi, Cassie, Chris, Mike, Joan, et al. The issue described in this thread will be addressed in a new release forthcoming soon. The user story is at https://www.pivotaltracker.com/story/show/64905804. Basically, the accession identifier will no longer appear as part of the accession title. I think you will also be interested to know that staff browse screens will be configurable to a degree. See the user story https://www.pivotaltracker.com/story/show/51597537. Cheers, Brad W. Bradley D. Westbrook Program Manager brad.westbrook at lyrasis.org 800.999.8558 x2910 678.235.2910 bradley_d_westbrook (Skype)? -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Cassandra A Schmitt Sent: Friday, March 28, 2014 4:17 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Inconsistent Accession Identifer display I had also sent in a request including some screenshots for what Mike is describing a few weeks ago, so I think it is on the radar somewhere. I would agree that the preference would be to remove the number from the title display and rely on the identifier column. (and I also dislike the commas.) -Cassie ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Prom, Christopher John [prom at illinois.edu] Sent: Friday, March 28, 2014 4:08 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Inconsistent Accession Identifer display The default separator for ID segments in Archon is a forward slash, so +1 for making these configurable. There may already be a way to do it, but I have not had time to research the issue. Chris Prom University of Illinois On Mar 28, 2014, at 3:03 PM, Christine Di Bella wrote: > I've noticed this as well, and have also noted that neither matches > the default display in Archivists' Toolkit, which separates the > segments by a period. Taking them out of the collection title display, > and consistency elsewhere, or, preferably, the ability to customize > these displays, would be my preference. This goes for Resource > identifiers, whose segments are also separated by dashes in ASpace and periods in AT, too. > > Small in the grand scheme of things, of course, but would be nice. :) > > Christine > > Christine Di Bella > Archivist > Shelby White and Leon Levy Archives Center Institute for Advanced > Study Einstein Drive Princeton, NJ 08540 Email : cdibella at ias.edu > Phone: 609-734-8368 > Website : http://library.ias.edu/archives > > > -----Original Message----- > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On > Behalf Of Rush, Michael > Sent: Friday, March 28, 2014 3:31 PM > To: Archivesspace_Users_Group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] Inconsistent Accession Identifer > display > > All, > > I've noticed that way in which multi-part accession identifiers is > displayed is inconsistent. > > First, the segments of the accession number display as part of the > accession title, both in the title column in any list of accessions > and across the top of the accession record. I personally don't think > the identifier should be included in the accession title in this way, > but it's confusing because the identifier segments are separated by > commas in that context. In the Identifier column of a list of > accessions, the segments are separated by dashes. > > I think it would be helpful to display accession identifiers more > consistently. My personal preference would be to remove them from > displays of accession titles altogether, but if the community > consensus is to keep them there, they should be consistent with > display elsewhere and dash-separated. > > Has anyone else noticed this? Thoughts? > > Mike > > _____________________________________ > Michael Rush > Accessioning Archivist > Beinecke Rare Book and Manuscript Library Yale University > 203-432-8123 > > The Beinecke Rare Book and Manuscript Library will close for a major > renovation in May 2015, reopening in August 2016. We will maintain a > reading room in Sterling Memorial Library during this time, but access > to various collections will be limited as early as April 2014 while we > prepare for closure. For details, please visit our renovation website > at http://beineckelibraryrenovation.yale.edu/. > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_grou > p _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_grou > p _______________________________________________ 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 ns96 at nyu.edu Mon Mar 31 11:11:54 2014 From: ns96 at nyu.edu (Nathan Stevens) Date: Mon, 31 Mar 2014 11:11:54 -0400 Subject: [Archivesspace_Users_Group] Updated Version of AT to ArchivesSpace Migration Plugin Available Message-ID: An updated version of the AT to ArchivesSpace Migration Plugin (v1.0.7.2) is available for download at https://docs.archivesspace.org/tools/index.html This releases addresses the following: 1. Migrates Accession Disposition Notes 2. Migrates "Internal Only" field for Notes, and Resource Components 3. Set the Default Thread parameter to 1 as a workaround for migration related issues being seen in ArchivesSpace version 1.0.7.1 -- Nathan Stevens Programmer/Analyst Digital Library Technology Services New York University 1212-998-2653 ns96 at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mlevy at ushmm.org Mon Mar 31 11:43:08 2014 From: mlevy at ushmm.org (Levy, Michael) Date: Mon, 31 Mar 2014 11:43:08 -0400 Subject: [Archivesspace_Users_Group] Error message in saving record In-Reply-To: <445643DE838938489E0EBC1D2FDBAEF18ABBAF1F@LEE04.vmi.edu> References: <445643DE838938489E0EBC1D2FDBAEF18ABBAF1F@LEE04.vmi.edu> Message-ID: We are experiencing something similar with 1.0.7.1. We created an item, added an instance and a digital object, saved it with no problems. Then we tried to remove the digital object and got this error message: translation missing: en.no key - This log output includes the SQL constraint error. We'd be happy to help narrow this down if that would be useful. in", :login_time=>2014-03-31 11:25:08 -0400, :expirable=>true}, @id="dd1c8c2d4f851d57fe3cdc754ee54a9d0bddddd31f1df8f34ea2f885d7dd91b6">] D, [2014-03-31T11:31:37.078000 #29151] DEBUG -- : Thread-379022: Post-processed params: {} D, [2014-03-31T11:31:37.578000 #29151] DEBUG -- : Thread-379022: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"25577"}, ["[{\"lock_version\":0,\"name\":\"linked_agent_archival_record_relators\",\"editable\":true,\"create_time\":\"2014-03-07T20:52:11Z\",\"system_mtime\":\"2014-03-07T20:52:11Z\",\"user_mtime\":\"2014-03-07T20:52:11Z\",\"jsonmodel_type\":\"enumeration\",\"values\":[\"acp\",\"act\",\"adp\",\"aft\",\"anl\",\"anm\",\"ann\",\"ant\",\"app\",\"aqt\",\"arc\",\"ard\",\"arr\",\"art\",\"asg\",\"as... in 518.0ms D, [2014-03-31T11:31:37.663000 #29151] DEBUG -- : Thread-378916: POST /repositories/2/archival_objects/2 [session: #"admin", :login_time=>2014-03-31 11:25:08 -0400, :expirable=>true}, @id="dd1c8c2d4f851d57fe3cdc754ee54a9d0bddddd31f1df8f34ea2f885d7dd91b6">] D, [2014-03-31T11:31:37.697000 #29151] DEBUG -- : Thread-378916: Post-processed params: {:id=>2, :archival_object=>#"1", "resource"=>{"ref"=>"/repositories/2/resources/1"}, "position"=>0, "title"=>"one page letter from Josef Broniatowski to the Perloff family about the problem with the affidavit in his immigration application", "ref_id"=>"67c485e3e79e1d23ac23207a18c4615e", "level"=>"item", "publish"=>true, "dates"=>[{"lock_version"=>"0", "label"=>"other", "expression"=>"July 14, 1938", "date_type"=>"single"}], "instances"=>[{"lock_version"=>"0", "instance_type"=>"text", "container"=>{"lock_version"=>"0", "type_1"=>"folder", "indicator_1"=>"1", "container_locations"=>[]}}, {"lock_version"=>"0", "instance_type"=>"digital_object", "digital_object"=>{"ref"=>"/repositories/2/digital_objects/1"}}], "restrictions_apply"=>false, "jsonmodel_type"=>"archival_object", "external_ids"=>[], "subjects"=>[], "extents"=>[], "external_documents"=>[], "rights_statements"=>[], "linked_agents"=>[], "notes"=>[], "linked_events"=>[], "component_id"=>""}>, :repo_id=>2} E, [2014-03-31T11:31:38.143000 #29151] ERROR -- : Java::JavaSql::SQLIntegrityConstraintViolationException: DELETE on table 'INSTANCE' caused a violation of foreign key constraint 'SQL140307155144480' for key (9). The statement has been rolled back. org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source) org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source) org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source) org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source) sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:455) org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:316) org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:61) org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:168) rubyjit.Sequel::JDBC::Database$$execute_BA39EE6C9DF8254AA4544BFB9356606B35D67A19.block_6$RUBY$__file__(/data/sites/apps/public/archivesspace-v1.0.7.1/gems/gems/sequel-3.41.0/lib/sequel/adapters/jdbc.rb:266) rubyjit$Sequel::JDBC::Database$$execute_BA39EE6C9DF8254AA4544BFB9356606B35D67A19$block_6$RUBY$__file__.call(rubyjit$Sequel::JDBC::Database$$execute_BA39EE6C9DF8254AA4544BFB9356606B35D67A19$block_6$RUBY$__file__) org.jruby.runtime.CompiledBlock19.yieldSpecificInternal(CompiledBlock19.java:117) org.jruby.runtime.CompiledBlock19.yieldSpecific(CompiledBlock19.java:92) org.jruby.runtime.Block.yieldSpecific(Block.java:111) rubyjit.Sequel::Database$$log_yield_639CF3E5DAF05FE8E8A5DE26EB5A99A37DE0E0B6.__file__(/data/sites/apps/public/archivesspace-v1.0.7.1/gems/gems/sequel-3.41.0/lib/sequel/database/logging.rb:33) rubyjit.Sequel::Database$$log_yield_639CF3E5DAF05FE8E8A5DE26EB5A99A37DE0E0B6.__file__(/data/sites/apps/public/archivesspace-v1.0.7.1/gems/gems/sequel-3.41.0/lib/sequel/database/logging.rb) org.jruby.ast.executable.AbstractScript.__file__(AbstractScript.java:42) : On Wed, Mar 26, 2014 at 11:47 AM, Jacob, Diane B. wrote: > I'm having trouble saving a record. This occurred after I was adding > two instances - one physical, and one digital object. I added the digital > object first, saved the record, and all was well. After I added the second > instance, I received the error. I have deleted the record and created it > again, but the same pattern occurs. Can someone help explain what's > happening here? > > > > translation missing: en.no key - translation missing: > en.validation_errors.database_integrity_constraint_conflict__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__cannot_delete_or_update_a_parent_row__a_foreign_key_constraint_fails_(`archivesspaceram`.`instance_do_link_rlshp`__constraint_`instance_do_link_rlshp_ibfk_2`_foreign_key_(`instance_id`)_references_`instance`_(`id`)) > > > > Thanks, Diane > > > > Diane B. Jacob > > Head, Archives & Records Management > > Virginia Military Institute > > Preston Library > > Lexington, VA 24450 > > 540-464-7566 > > www.vmi.edu/archives > > _______________________________________________ > 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 PGalligan at rockarch.org Mon Mar 31 12:45:56 2014 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Mon, 31 Mar 2014 12:45:56 -0400 Subject: [Archivesspace_Users_Group] AT to ASpace Migration -- Digital Object Date Label Message-ID: Hey, Has anyone else run into this problem with Digital Objects? We anticipate this being a larger problem as we get into digitizing more of our legacy collections and would love to see a revision to how ASpace handles the digital object dates. -Patrick From: Galligan, Patrick Sent: Friday, March 21, 2014 12:09 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: AT to ASpace Migration -- Digital Object Date Label In migrating our Digital Objects from AT to ArchivesSpace using the migration plugin, we noticed that the Digital Object Date Label defaults to "digitized" in ArchivesSpace. So where our Digital Objects in AT might have a Date Begin in 1950 and Date End in 1951, ArchivesSpace now defaults to displaying those dates as the dates the materials were digitized. Is there any way to change this default label? It really isn't ideal for us to have all of the DOs default to a digitized date, as that is not the information that we have been putting in the Date boxes in AT. -Patrick Galligan -------------- next part -------------- An HTML attachment was scrubbed... URL: From cdibella at ias.edu Mon Mar 31 13:08:06 2014 From: cdibella at ias.edu (Christine Di Bella) Date: Mon, 31 Mar 2014 13:08:06 -0400 (EDT) Subject: [Archivesspace_Users_Group] AT to ASpace Migration -- Digital Object Date Label In-Reply-To: References: Message-ID: I don't really have anything to add, but yes, I've definitely seen this as well. (I'll note that when one adds a Digital Object instance to an existing file/item in AT, the date field is automatically populated with the date information from the resource component record, so this isn't a matter of the field being used incorrectly in our AT deployments.) I agree that this will be problematic going forward and would like to see a change. I haven't tried out the version of the migration plugin released this morning yet - perhaps this was already addressed there? Christine Christine Di Bella Archivist Shelby White and Leon Levy Archives Center Institute for Advanced Study Einstein Drive Princeton, NJ 08540 Email : cdibella at ias.edu Phone: 609-734-8368 Website : http://library.ias.edu/archives From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick Sent: Monday, March 31, 2014 12:46 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] AT to ASpace Migration -- Digital Object Date Label Hey, Has anyone else run into this problem with Digital Objects? We anticipate this being a larger problem as we get into digitizing more of our legacy collections and would love to see a revision to how ASpace handles the digital object dates. -Patrick From: Galligan, Patrick Sent: Friday, March 21, 2014 12:09 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: AT to ASpace Migration -- Digital Object Date Label In migrating our Digital Objects from AT to ArchivesSpace using the migration plugin, we noticed that the Digital Object Date Label defaults to "digitized" in ArchivesSpace. So where our Digital Objects in AT might have a Date Begin in 1950 and Date End in 1951, ArchivesSpace now defaults to displaying those dates as the dates the materials were digitized. Is there any way to change this default label? It really isn't ideal for us to have all of the DOs default to a digitized date, as that is not the information that we have been putting in the Date boxes in AT. -Patrick Galligan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ns96 at nyu.edu Mon Mar 31 13:54:38 2014 From: ns96 at nyu.edu (Nathan Stevens) Date: Mon, 31 Mar 2014 13:54:38 -0400 Subject: [Archivesspace_Users_Group] AT to ASpace Migration -- Digital Object Date Label In-Reply-To: References: Message-ID: What should the default be for Digital Object? Creation instead of Digitize? On Mon, Mar 31, 2014 at 1:08 PM, Christine Di Bella wrote: > I don't really have anything to add, but yes, I've definitely seen this as > well. (I'll note that when one adds a Digital Object instance to an > existing file/item in AT, the date field is automatically populated with > the date information from the resource component record, so this isn't a > matter of the field being used incorrectly in our AT deployments.) > > > > I agree that this will be problematic going forward and would like to see > a change. I haven't tried out the version of the migration plugin released > this morning yet - perhaps this was already addressed there? > > > > Christine > > Christine Di Bella > Archivist > Shelby White and Leon Levy Archives Center > Institute for Advanced Study > Einstein Drive > Princeton, NJ 08540 > Email : cdibella at ias.edu > Phone: 609-734-8368 > Website : http://library.ias.edu/archives > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Galligan, > Patrick > *Sent:* Monday, March 31, 2014 12:46 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* Re: [Archivesspace_Users_Group] AT to ASpace Migration -- > Digital Object Date Label > > > > Hey, > > > > Has anyone else run into this problem with Digital Objects? > > > > We anticipate this being a larger problem as we get into digitizing more > of our legacy collections and would love to see a revision to how ASpace > handles the digital object dates. > > > > -Patrick > > > > *From:* Galligan, Patrick > *Sent:* Friday, March 21, 2014 12:09 PM > *To:* 'archivesspace_users_group at lyralists.lyrasis.org' > *Subject:* AT to ASpace Migration -- Digital Object Date Label > > > > In migrating our Digital Objects from AT to ArchivesSpace using the > migration plugin, we noticed that the Digital Object Date Label defaults to > "digitized" in ArchivesSpace. > > > > So where our Digital Objects in AT might have a Date Begin in 1950 and > Date End in 1951, ArchivesSpace now defaults to displaying those dates as > the dates the materials were digitized. > > > > Is there any way to change this default label? It really isn't ideal for > us to have all of the DOs default to a digitized date, as that is not the > information that we have been putting in the Date boxes in AT. > > > > -Patrick Galligan > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Nathan Stevens Programmer/Analyst Digital Library Technology Services New York University 1212-998-2653 ns96 at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From smithkr at MIT.EDU Mon Mar 31 14:24:40 2014 From: smithkr at MIT.EDU (Kari R Smith) Date: Mon, 31 Mar 2014 18:24:40 +0000 Subject: [Archivesspace_Users_Group] AT to ASpace Migration -- Digital Object Date Label In-Reply-To: References: Message-ID: <29F559819ACA9A4FBF208407D4B63ABB55127326@OC11expo28.exchange.mit.edu> I could see two attributes: Creation [actual] [presumed] Last updated date [the most likely known date for digital files] Kari Smith From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Nathan Stevens Sent: Monday, March 31, 2014 1:55 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] AT to ASpace Migration -- Digital Object Date Label What should the default be for Digital Object? Creation instead of Digitize? On Mon, Mar 31, 2014 at 1:08 PM, Christine Di Bella > wrote: I don't really have anything to add, but yes, I've definitely seen this as well. (I'll note that when one adds a Digital Object instance to an existing file/item in AT, the date field is automatically populated with the date information from the resource component record, so this isn't a matter of the field being used incorrectly in our AT deployments.) I agree that this will be problematic going forward and would like to see a change. I haven't tried out the version of the migration plugin released this morning yet - perhaps this was already addressed there? Christine Christine Di Bella Archivist Shelby White and Leon Levy Archives Center Institute for Advanced Study Einstein Drive Princeton, NJ 08540 Email : cdibella at ias.edu Phone: 609-734-8368 Website : http://library.ias.edu/archives From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick Sent: Monday, March 31, 2014 12:46 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] AT to ASpace Migration -- Digital Object Date Label Hey, Has anyone else run into this problem with Digital Objects? We anticipate this being a larger problem as we get into digitizing more of our legacy collections and would love to see a revision to how ASpace handles the digital object dates. -Patrick From: Galligan, Patrick Sent: Friday, March 21, 2014 12:09 PM To: 'archivesspace_users_group at lyralists.lyrasis.org' Subject: AT to ASpace Migration -- Digital Object Date Label In migrating our Digital Objects from AT to ArchivesSpace using the migration plugin, we noticed that the Digital Object Date Label defaults to "digitized" in ArchivesSpace. So where our Digital Objects in AT might have a Date Begin in 1950 and Date End in 1951, ArchivesSpace now defaults to displaying those dates as the dates the materials were digitized. Is there any way to change this default label? It really isn't ideal for us to have all of the DOs default to a digitized date, as that is not the information that we have been putting in the Date boxes in AT. -Patrick Galligan _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nathan Stevens Programmer/Analyst Digital Library Technology Services New York University 1212-998-2653 ns96 at nyu.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Mon Mar 31 14:54:58 2014 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Mon, 31 Mar 2014 18:54:58 +0000 Subject: [Archivesspace_Users_Group] Error message in saving record In-Reply-To: References: <445643DE838938489E0EBC1D2FDBAEF18ABBAF1F@LEE04.vmi.edu> Message-ID: <1299d3344d4c433cae25a476a05007e9@BLUPR08MB102.namprd08.prod.outlook.com> Hi, Michael. This is a known bug and will be fixed in the next release, which we are closing in on finishing. You can see the user story at https://www.pivotaltracker.com/story/show/68437254. 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 Levy, Michael Sent: Monday, March 31, 2014 11:43 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Error message in saving record We are experiencing something similar with 1.0.7.1. We created an item, added an instance and a digital object, saved it with no problems. Then we tried to remove the digital object and got this error message: translation missing: en.no key - This log output includes the SQL constraint error. We'd be happy to help narrow this down if that would be useful. in", :login_time=>2014-03-31 11:25:08 -0400, :expirable=>true}, @id="dd1c8c2d4f851d57fe3cdc754ee54a9d0bddddd31f1df8f34ea2f885d7dd91b6">] D, [2014-03-31T11:31:37.078000 #29151] DEBUG -- : Thread-379022: Post-processed params: {} D, [2014-03-31T11:31:37.578000 #29151] DEBUG -- : Thread-379022: Responded with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"25577"}, ["[{\"lock_version\":0,\"name\":\"linked_agent_archival_record_relators\",\"editable\":true,\"create_time\":\"2014-03-07T20:52:11Z\",\"system_mtime\":\"2014-03-07T20:52:11Z\",\"user_mtime\":\"2014-03-07T20:52:11Z\",\"jsonmodel_type\":\"enumeration\",\"values\":[\"acp\",\"act\",\"adp\",\"aft\",\"anl\",\"anm\",\"ann\",\"ant\",\"app\",\"aqt\",\"arc\",\"ard\",\"arr\",\"art\",\"asg\",\"as... in 518.0ms D, [2014-03-31T11:31:37.663000 #29151] DEBUG -- : Thread-378916: POST /repositories/2/archival_objects/2 [session: #"admin", :login_time=>2014-03-31 11:25:08 -0400, :expirable=>true}, @id="dd1c8c2d4f851d57fe3cdc754ee54a9d0bddddd31f1df8f34ea2f885d7dd91b6">] D, [2014-03-31T11:31:37.697000 #29151] DEBUG -- : Thread-378916: Post-processed params: {:id=>2, :archival_object=>#"1", "resource"=>{"ref"=>"/repositories/2/resources/1"}, "position"=>0, "title"=>"one page letter from Josef Broniatowski to the Perloff family about the problem with the affidavit in his immigration application", "ref_id"=>"67c485e3e79e1d23ac23207a18c4615e", "level"=>"item", "publish"=>true, "dates"=>[{"lock_version"=>"0", "label"=>"other", "expression"=>"July 14, 1938", "date_type"=>"single"}], "instances"=>[{"lock_version"=>"0", "instance_type"=>"text", "container"=>{"lock_version"=>"0", "type_1"=>"folder", "indicator_1"=>"1", "container_locations"=>[]}}, {"lock_version"=>"0", "instance_type"=>"digital_object", "digital_object"=>{"ref"=>"/repositories/2/digital_objects/1"}}], "restrictions_apply"=>false, "jsonmodel_type"=>"archival_object", "external_ids"=>[], "subjects"=>[], "extents"=>[], "external_documents"=>[], "rights_statements"=>[], "linked_agents"=>[], "notes"=>[], "linked_events"=>[], "component_id"=>""}>, :repo_id=>2} E, [2014-03-31T11:31:38.143000 #29151] ERROR -- : Java::JavaSql::SQLIntegrityConstraintViolationException: DELETE on table 'INSTANCE' caused a violation of foreign key constraint 'SQL140307155144480' for key (9). The statement has been rolled back. org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source) org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown Source) org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown Source) org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source) org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source) org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source) sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:597) org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:455) org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:316) org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:61) org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:168) rubyjit.Sequel::JDBC::Database$$execute_BA39EE6C9DF8254AA4544BFB9356606B35D67A19.block_6$RUBY$__file__(/data/sites/apps/public/archivesspace-v1.0.7.1/gems/gems/sequel-3.41.0/lib/sequel/adapters/jdbc.rb:266) rubyjit$Sequel::JDBC::Database$$execute_BA39EE6C9DF8254AA4544BFB9356606B35D67A19$block_6$RUBY$__file__.call(rubyjit$Sequel::JDBC::Database$$execute_BA39EE6C9DF8254AA4544BFB9356606B35D67A19$block_6$RUBY$__file__) org.jruby.runtime.CompiledBlock19.yieldSpecificInternal(CompiledBlock19.java:117) org.jruby.runtime.CompiledBlock19.yieldSpecific(CompiledBlock19.java:92) org.jruby.runtime.Block.yieldSpecific(Block.java:111) rubyjit.Sequel::Database$$log_yield_639CF3E5DAF05FE8E8A5DE26EB5A99A37DE0E0B6.__file__(/data/sites/apps/public/archivesspace-v1.0.7.1/gems/gems/sequel-3.41.0/lib/sequel/database/logging.rb:33) rubyjit.Sequel::Database$$log_yield_639CF3E5DAF05FE8E8A5DE26EB5A99A37DE0E0B6.__file__(/data/sites/apps/public/archivesspace-v1.0.7.1/gems/gems/sequel-3.41.0/lib/sequel/database/logging.rb) org.jruby.ast.executable.AbstractScript.__file__(AbstractScript.java:42) : On Wed, Mar 26, 2014 at 11:47 AM, Jacob, Diane B. > wrote: I'm having trouble saving a record. This occurred after I was adding two instances - one physical, and one digital object. I added the digital object first, saved the record, and all was well. After I added the second instance, I received the error. I have deleted the record and created it again, but the same pattern occurs. Can someone help explain what's happening here? translation missing: en.no key - translation missing: en.validation_errors.database_integrity_constraint_conflict__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__cannot_delete_or_update_a_parent_row__a_foreign_key_constraint_fails_(`archivesspaceram`.`instance_do_link_rlshp`__constraint_`instance_do_link_rlshp_ibfk_2`_foreign_key_(`instance_id`)_references_`instance`_(`id`)) Thanks, Diane Diane B. Jacob Head, Archives & Records Management Virginia Military Institute Preston Library Lexington, VA 24450 540-464-7566 www.vmi.edu/archives _______________________________________________ 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 mlevy at ushmm.org Mon Mar 31 15:07:15 2014 From: mlevy at ushmm.org (Levy, Michael) Date: Mon, 31 Mar 2014 15:07:15 -0400 Subject: [Archivesspace_Users_Group] Error message in saving record In-Reply-To: <1299d3344d4c433cae25a476a05007e9@BLUPR08MB102.namprd08.prod.outlook.com> References: <445643DE838938489E0EBC1D2FDBAEF18ABBAF1F@LEE04.vmi.edu> <1299d3344d4c433cae25a476a05007e9@BLUPR08MB102.namprd08.prod.outlook.com> Message-ID: Brad and all, thanks. I'll start perusing the Pivotal issues more closely from now on. On Mon, Mar 31, 2014 at 2:54 PM, Brad Westbrook wrote: > Hi, Michael. > > > > This is a known bug and will be fixed in the next release, which we are > closing in on finishing. You can see the user story at > https://www.pivotaltracker.com/story/show/68437254. > > > > Brad W. > > > > > > Bradley D. Westbrook > > Program Manager > > brad.westbrook at lyrasis.org > > 800.999.8558 x2910 > > 678.235.2910 > > bradley_d_westbrook (Skype) > > [image: 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 *Levy, > Michael > *Sent:* Monday, March 31, 2014 11:43 AM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Error message in saving record > > > > We are experiencing something similar with 1.0.7.1. > > > > We created an item, added an instance and a digital object, saved it with > no problems. Then we tried to remove the digital object and got this error > message: > > > > translation missing: en.no key - > > > > This log output includes the SQL constraint error. > > > > We'd be happy to help narrow this down if that would be useful. > > > > in", :login_time=>2014-03-31 11:25:08 -0400, :expirable=>true}, > @id="dd1c8c2d4f851d57fe3cdc754ee54a9d0bddddd31f1df8f34ea2f885d7dd91b6">] > > D, [2014-03-31T11:31:37.078000 #29151] DEBUG -- : Thread-379022: > Post-processed params: {} > > D, [2014-03-31T11:31:37.578000 #29151] DEBUG -- : Thread-379022: Responded > with [200, {"Content-Type"=>"application/json", "Cache-Control"=>"private, > must-revalidate, max-age=0", "Content-Length"=>"25577"}, > ["[{\"lock_version\":0,\"name\":\"linked_agent_archival_record_relators\",\"editable\":true,\"create_time\":\"2014-03-07T20:52:11Z\",\"system_mtime\":\"2014-03-07T20:52:11Z\",\"user_mtime\":\"2014-03-07T20:52:11Z\",\"jsonmodel_type\":\"enumeration\",\"values\":[\"acp\",\"act\",\"adp\",\"aft\",\"anl\",\"anm\",\"ann\",\"ant\",\"app\",\"aqt\",\"arc\",\"ard\",\"arr\",\"art\",\"asg\",\"as... > in 518.0ms > > D, [2014-03-31T11:31:37.663000 #29151] DEBUG -- : Thread-378916: POST > /repositories/2/archival_objects/2 [session: # @store={:user=>"admin", :login_time=>2014-03-31 11:25:08 -0400, > :expirable=>true}, > @id="dd1c8c2d4f851d57fe3cdc754ee54a9d0bddddd31f1df8f34ea2f885d7dd91b6">] > > D, [2014-03-31T11:31:37.697000 #29151] DEBUG -- : Thread-378916: > Post-processed params: {:id=>2, > :archival_object=>#"1", > "resource"=>{"ref"=>"/repositories/2/resources/1"}, "position"=>0, > "title"=>"one page letter from Josef Broniatowski to the Perloff family > about the problem with the affidavit in his immigration application", > "ref_id"=>"67c485e3e79e1d23ac23207a18c4615e", "level"=>"item", > "publish"=>true, "dates"=>[{"lock_version"=>"0", "label"=>"other", > "expression"=>"July 14, 1938", "date_type"=>"single"}], > "instances"=>[{"lock_version"=>"0", "instance_type"=>"text", > "container"=>{"lock_version"=>"0", "type_1"=>"folder", "indicator_1"=>"1", > "container_locations"=>[]}}, {"lock_version"=>"0", > "instance_type"=>"digital_object", > "digital_object"=>{"ref"=>"/repositories/2/digital_objects/1"}}], > "restrictions_apply"=>false, "jsonmodel_type"=>"archival_object", > "external_ids"=>[], "subjects"=>[], "extents"=>[], > "external_documents"=>[], "rights_statements"=>[], "linked_agents"=>[], > "notes"=>[], "linked_events"=>[], "component_id"=>""}>, :repo_id=>2} > > E, [2014-03-31T11:31:38.143000 #29151] ERROR -- : > > Java::JavaSql::SQLIntegrityConstraintViolationException: DELETE on table > 'INSTANCE' caused a violation of foreign key constraint > 'SQL140307155144480' for key (9). The statement has been rolled back. > > org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown > Source) > > org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) > > org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown > Source) > > org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown > Source) > > org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown Source) > > org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown Source) > > org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) > > org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) > > org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source) > > sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source) > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > > java.lang.reflect.Method.invoke(Method.java:597) > > > org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:455) > > org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:316) > > > org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:61) > > org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:168) > > > rubyjit.Sequel::JDBC::Database$$execute_BA39EE6C9DF8254AA4544BFB9356606B35D67A19.block_6$RUBY$__file__(/data/sites/apps/public/archivesspace-v1.0.7.1/gems/gems/sequel-3.41.0/lib/sequel/adapters/jdbc.rb:266) > > > rubyjit$Sequel::JDBC::Database$$execute_BA39EE6C9DF8254AA4544BFB9356606B35D67A19$block_6$RUBY$__file__.call(rubyjit$Sequel::JDBC::Database$$execute_BA39EE6C9DF8254AA4544BFB9356606B35D67A19$block_6$RUBY$__file__) > > > org.jruby.runtime.CompiledBlock19.yieldSpecificInternal(CompiledBlock19.java:117) > > org.jruby.runtime.CompiledBlock19.yieldSpecific(CompiledBlock19.java:92) > > org.jruby.runtime.Block.yieldSpecific(Block.java:111) > > > rubyjit.Sequel::Database$$log_yield_639CF3E5DAF05FE8E8A5DE26EB5A99A37DE0E0B6.__file__(/data/sites/apps/public/archivesspace-v1.0.7.1/gems/gems/sequel-3.41.0/lib/sequel/database/logging.rb:33) > > > rubyjit.Sequel::Database$$log_yield_639CF3E5DAF05FE8E8A5DE26EB5A99A37DE0E0B6.__file__(/data/sites/apps/public/archivesspace-v1.0.7.1/gems/gems/sequel-3.41.0/lib/sequel/database/logging.rb) > > org.jruby.ast.executable.AbstractScript.__file__(AbstractScript.java:42) > > : > > > > > > On Wed, Mar 26, 2014 at 11:47 AM, Jacob, Diane B. wrote: > > I'm having trouble saving a record. This occurred after I was adding two > instances - one physical, and one digital object. I added the digital > object first, saved the record, and all was well. After I added the second > instance, I received the error. I have deleted the record and created it > again, but the same pattern occurs. Can someone help explain what's > happening here? > > > > translation missing: en.no key - translation missing: > en.validation_errors.database_integrity_constraint_conflict__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__cannot_delete_or_update_a_parent_row__a_foreign_key_constraint_fails_(`archivesspaceram`.`instance_do_link_rlshp`__constraint_`instance_do_link_rlshp_ibfk_2`_foreign_key_(`instance_id`)_references_`instance`_(`id`)) > > > > Thanks, Diane > > > > Diane B. Jacob > > Head, Archives & Records Management > > Virginia Military Institute > > Preston Library > > Lexington, VA 24450 > > 540-464-7566 > > www.vmi.edu/archives > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7645 bytes Desc: not available URL: From PGalligan at rockarch.org Mon Mar 31 16:24:26 2014 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Mon, 31 Mar 2014 16:24:26 -0400 Subject: [Archivesspace_Users_Group] (no subject) Message-ID: Nathan, I'd default to Creation Date. DACS can be wishy-washy, but more often than not, dates refer to the creation date. Patrick Galligan Rockefeller Archives Center Assistant Digital Archivist 914-366-6386 From: Nathan Stevens > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] AT to ASpace Migration -- Digital Object Date Label Message-ID: > Content-Type: text/plain; charset="iso-8859-1" What should the default be for Digital Object? Creation instead of Digitize? On Mon, Mar 31, 2014 at 1:08 PM, Christine Di Bella >wrote: -------------- next part -------------- An HTML attachment was scrubbed... URL: