From sukerr at davidson.edu Wed Apr 1 08:47:33 2015 From: sukerr at davidson.edu (Kerr, Susan) Date: Wed, 1 Apr 2015 12:47:33 +0000 Subject: [Archivesspace_Users_Group] Import error with Accession CSV Template Message-ID: <30c04caa9a944b6fbbdfb4aeaa9f8803@MBX13A.davidson.edu> Sadly, I am not experienced enough to interpret your question. This is a test WAMP environment on my computer where I have admin rights and can delete files in the folder. The user account on the server in this case is "aspace" with ALL privileges, Grant YES. When I try to edit this, I see that there are no Table-specific privileges. This is from my config.rb file and is the only not-commented line in that file: AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" The user logged into ArchiveSpace is my personal account and I am an administrator. Baby steps. Thanks, Susan From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 31, 2015 5:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Hi, What I am seeing is that the job completed, but the last step ( removing the import file ) is running into a permission problem. Not sure about what your deployment method is, but does the use running the application have delete permissions in the application's data directory? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Tuesday, March 31, 2015 10:34 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Log file is attached. Thanks, Susan From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 31, 2015 3:27 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Hi Susan, What does the archivesspace.out log file say? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Tuesday, March 31, 2015 8:08 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Import error with Accession CSV Template I am trying to use the http://www.archivesspace.org/importexport Accession CSV Template with some very basic information for a test accession. System details: ArchivesSpace version 1.1.2; Windows Apache MySQL PHP (WAMP) Most of my experiments resulted in this error !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! When I removed all but the three elements required of an accession: title, accession_number, accession date, I get this error: ================================================== testAccImport.csv ================================================== 1. STARTED: Reading JSON records 1. DONE: Reading JSON records 2. STARTED: Validating records and checking links 2. DONE: Validating records and checking links 3. STARTED: Evaluating record relationships 3. DONE: Evaluating record relationships 4. STARTED: Saving records: cycle 1 Created: /repositories/import/accessions/import_24b4c82f-7f39-475d-aabd-5d58e4dbe696 4. DONE: Saving records: cycle 1 5. STARTED: Cleaning up 5. DONE: Cleaning up !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!! This is the test import file. accession_title,accession_number_1,accession_number_2,accession_number_3,accession_number_4,accession_accession_date,accession_access_restrictions,accession_access_restrictions_note,accession_acquisition_type,accession_condition_description,accession_content_description,accession_disposition,accession_general_note,accession_inventory,accession_provenance,accession_publish,accession_resource_type,accession_restrictions_apply,accession_retention_rule,accession_use_restrictions,accession_use_restrictions_note,accession_cataloged_note,accession_processing_hours_total,accession_processing_plan,accession_processing_priority,accession_processing_status,accession_processing_started_date,accession_processing_total_extent,accession_processing_total_extent_type,accession_processors,accession_rights_determined,date_1_label,date_1_expression,date_1_begin,date_1_end,date_1_type,date_2_label,date_2_expression,date_2_begin,date_2_end,date_2_type,extent_type,extent_container_summary,extent_number,accession_acknowledgement_sent,accession_acknowledgement_sent_date,accession_agreement_received,accession_agreement_received_date,accession_agreement_sent,accession_agreement_sent_date,accession_cataloged,accession_cataloged_date,accession_processed,accession_processed_date,user_defined_boolean_t,user_defined_boolean_2,user_defined_boolean_3,user_defined_integer_1,user_defined_integer_2,user_defined_integer_3,user_defined_real_1,user_defined_real_2,user_defined_real_3,user_defined_string_1,user_defined_string_2,user_defined_string_3,user_defined_string_4,user_defined_text_1,user_defined_text_2,user_defined_text_3,user_defined_text_4,user_defined_text_5,user_defined_date_1,user_defined_date_2,user_defined_date_3,user_defined_enum_1,user_defined_enum_2,user_defined_enum_3,user_defined_enum_4,agent_role,agent_type,agent_contact_address_1,agent_contact_address_2,agent_contact_address_3,agent_contact_city,agent_contact_country,agent_contact_email,agent_contact_fax,agent_contact_name,agent_contact_post_code,agent_contact_region,agent_contact_salutation,agent_contact_telephone,agent_contact_telephone_ext,agent_name_authority_id,agent_name_dates,agent_name_fuller_form,agent_name_name_order,agent_name_number,agent_name_prefix,agent_name_primary_name,agent_name_qualifier,agent_name_rest_of_name,agent_name_rules,agent_name_sort_name,agent_name_source,agent_name_subordinate_name_1,agent_name_subordinate_name_2,agent_name_suffix,agent_name_description_note,agent_name_description_citation,subject_source,subject_term,subject_term_type 29-Mar-94,1994-001,,,,1994-03-29,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, I have also tried to import a file that had successfully imported in a Linux environment and get the error with no results. I would appreciate any help in solving this problem Thanks, Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Wed Apr 1 08:49:34 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Wed, 1 Apr 2015 12:49:34 +0000 Subject: [Archivesspace_Users_Group] Appointment of ArchivesSpace Community Outreach and Support Manager Message-ID: Good morning ArchivesSpace members. I am very pleased to report that, as of today, Christine Di Bella will be the Community Outreach and Support Manager for the ArchivesSpace program. Christine will have primary responsibility for community outreach and engagement, including managing the ArchivesSpace wikis and website; for event organization, such as the scheduled ArchivesSpace members meeting on August 22 in Cleveland, OH; and for leading the updating of user documentation and the production of video tutorials. Also, Christine will become one of the ArchivesSpace trainers and will be attending various archives conferences as an ArchivesSpace representative. These are all key areas in the ArchivesSpace program, and they will progress substantially under Christine's leadership. Please join me in welcoming Christine to her new role. Cheers, 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] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7640 bytes Desc: image003.png URL: From christine.dibella at lyrasis.org Wed Apr 1 10:14:57 2015 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 1 Apr 2015 14:14:57 +0000 Subject: [Archivesspace_Users_Group] Who is live with ASpace? In-Reply-To: <96B305F061ED68428DDA721BECE2ED1551666866@ITSNT440.iowa.uiowa.edu> References: <96B305F061ED68428DDA721BECE2ED1551666866@ITSNT440.iowa.uiowa.edu> Message-ID: As you would imagine, seeing implementations of ArchivesSpace is of great interest to members and potential members of ArchivesSpace. If you have a public ArchivesSpace site and/or implementation blog or similar resource, we'd love to link to it from the ArchivesSpace members page (http://archivesspace.org/members). Please feel free to send your links directly to me, and I'll be glad to add them. Best, Christine Christine Di Bella Community Outreach and Support Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [cid:image003.png at 01CE734E.FD759D30] -------------- 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 mang.sun at rice.edu Wed Apr 1 12:06:56 2015 From: mang.sun at rice.edu (Mang Sun) Date: Wed, 01 Apr 2015 11:06:56 -0500 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: <1427746077682.56800@lyrasis.org> References: <1427746077682.56800@lyrasis.org> Message-ID: <551C17A0.3080904@rice.edu> Chris, After I deployed a clone copy of the AS master branch, I see "V1.1.4-dev02" instead of v1.2.0 at the footers of the front and public interfaces. Is it right? Thank you. Mang Sun Rice U. On 3/30/2015 3:07 PM, Chris Fitzpatrick wrote: > The ArchivesSpace team is happy to release version v1.2.0 > . > > Please see the technical documentation > for > information on how to upgrade your ArchivesSpace installs. > > Please see the release page > for a > listing of all the new features and bug fixes included in this release. > > Of particular note: This release includes an upgrade to Bootstrap 3 > for the staff interface. This version has > significant changes to HTML, CSS, and Javascript components in the > staff UI, so any plugins or custom templates will have to be modified > to work with Bootstrap 3. > > Also included in this release is a Find-And-Replace background job, > which allows users to bulk edit records. As this is a currently a > beta-feature, it is recommended that users backup their database > frequently if using this feature. > > Thanks to all the volunteers on the ArchivesSpace User Advisory and > Technical Advisory Councils, who are vital to keeping ArchivesSpace > development on track. > Please let us know if you have any questions, comments, or concerns. > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From psuda1 at tulane.edu Wed Apr 1 12:33:34 2015 From: psuda1 at tulane.edu (Suda, Phillip J) Date: Wed, 1 Apr 2015 16:33:34 +0000 Subject: [Archivesspace_Users_Group] Problem with version 1.2.0 Message-ID: Greetings all, I am having a problem with a clean install of ASpace 1.2.0. I setup the mysql database, updated the config.rb, etc. When I try to run the scripts/setup-database.sh command, I get the following error, "Sequel::AdapterNotFound: com.mysql.jdbc.driver not loaded, try installing jdbc-mysql gem." When I check the gems, jdbc-mysql is installed/present. Any advice. Thanks, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianjhoffman at gmail.com Wed Apr 1 12:35:40 2015 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Wed, 1 Apr 2015 12:35:40 -0400 Subject: [Archivesspace_Users_Group] Problem with version 1.2.0 In-Reply-To: References: Message-ID: <251C6DB7-DE8B-467F-BCB1-8A3C3E340F15@gmail.com> Hi, Did you download the MySql connector per the README? https://github.com/archivesspace/archivesspace/#download-mysql-connector Brian On Apr 1, 2015, at 12:33 PM, Suda, Phillip J wrote: > Greetings all, > > I am having a problem with a clean install of ASpace 1.2.0. I setup the mysql database, updated the config.rb, etc. When I try to run the scripts/setup-database.sh command, I get the following error, ?Sequel::AdapterNotFound: com.mysql.jdbc.driver not loaded, try installing jdbc-mysql gem.? When I check the gems, jdbc-mysql is installed/present. Any advice. > > Thanks, > > Phil > > Phillip Suda > Systems Librarian > Howard-Tilton Memorial Library > Tulane University > psuda1 at tulane.edu > 504-865-5607 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From psuda1 at tulane.edu Wed Apr 1 12:44:26 2015 From: psuda1 at tulane.edu (Suda, Phillip J) Date: Wed, 1 Apr 2015 16:44:26 +0000 Subject: [Archivesspace_Users_Group] Problem with version 1.2.0 In-Reply-To: References: Message-ID: Apologies all, Had mysql connector in wrong location. Thanks to Brian for assist. Thanks, Phil From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Suda, Phillip J Sent: Wednesday, April 01, 2015 11:34 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Problem with version 1.2.0 Greetings all, I am having a problem with a clean install of ASpace 1.2.0. I setup the mysql database, updated the config.rb, etc. When I try to run the scripts/setup-database.sh command, I get the following error, "Sequel::AdapterNotFound: com.mysql.jdbc.driver not loaded, try installing jdbc-mysql gem." When I check the gems, jdbc-mysql is installed/present. Any advice. Thanks, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 -------------- next part -------------- An HTML attachment was scrubbed... URL: From tcramer at stanford.edu Wed Apr 1 13:18:48 2015 From: tcramer at stanford.edu (Tom Cramer) Date: Wed, 1 Apr 2015 10:18:48 -0700 Subject: [Archivesspace_Users_Group] Appointment of ArchivesSpace Community Outreach and Support Manager In-Reply-To: References: Message-ID: <63EA69A1-8417-4221-8552-C65479A359FB@stanford.edu> Welcome, Christine. It's great to have you coordinating the community activity for ArchivesSpace, and I look forward to your leadership on the project overall. Best, - Tom | Tom Cramer | Chief Technology Strategist & Associate Director | Digital Library Systems & Services | Stanford University Libraries | tcramer at stanford.edu On Apr 1, 2015, at 5:49 AM, Brad Westbrook wrote: > Good morning ArchivesSpace members. > > I am very pleased to report that, as of today, Christine Di Bella will be the Community Outreach and Support Manager for the ArchivesSpace program. Christine will have primary responsibility for community outreach and engagement, including managing the ArchivesSpace wikis and website; for event organization, such as the scheduled ArchivesSpace members meeting on August 22 in Cleveland, OH; and for leading the updating of user documentation and the production of video tutorials. Also, Christine will become one of the ArchivesSpace trainers and will be attending various archives conferences as an ArchivesSpace representative. These are all key areas in the ArchivesSpace program, and they will progress substantially under Christine?s leadership. > > Please join me in welcoming Christine to her new role. > > Cheers, > > Brad W. > > Bradley D. Westbrook > Program Manager > brad.westbrook at lyrasis.org > 800.999.8558 x2910 > 678.235.2910 > bradley_d_westbrook (Skype) > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Wed Apr 1 13:38:47 2015 From: sdm7g at virginia.edu (Steven Majewski) Date: Wed, 1 Apr 2015 13:38:47 -0400 Subject: [Archivesspace_Users_Group] build_release and custom config Message-ID: <5536B5D8-17BE-47EC-BB6A-3967217FEC58@virginia.edu> With the v1.2.0 release, I finally got tired of saving and merging config.rb, local plugins, and mysql connector to upgrade on several test servers. I tried adding my changes to common/config/config.rb ? the changes worked when running devserver from the distribution, but they didn?t get exported into the distribution zip file after running build_release. It appears that all of that is intentional ? the dist target is intended to build the standard distribution, not a custom one. ( i.e. it does not include local plugins, and it specifically excludes the mysql connector if it is present. ) I made the following changes to the build-zip target to include local-plugins, mysql connector and common/config/config.rb is they are present. Then copied them to build/mybuild.xml where it can be run by: ./build/run -buildfile mybuild.xml dist -Dversion=?v1.2.0+local? https://github.com/uvalib-dcs/archivesspace/blob/local-mods/build/mybuild.xml Assuming you?re using mysql and there isn?t a local demo database to be migrated, you can just unzip, run migrate_db and restart and it will rebuild the solr indexes. ? Steve Majewski diff --git a/build/build.xml b/build/build.xml index e6ff44b..a9c13c3 100644 --- a/build/build.xml +++ b/build/build.xml @@ -491,3 +491,3 @@ - + + + + + + @@ -588,4 +594,9 @@ + + + + + - + -------------- 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 sukerr at davidson.edu Wed Apr 1 15:04:08 2015 From: sukerr at davidson.edu (Kerr, Susan) Date: Wed, 1 Apr 2015 19:04:08 +0000 Subject: [Archivesspace_Users_Group] Import error with Accession CSV Template Message-ID: Further experimenting, I found that if I created a user account in ArchivesSpace for the aspace db user, that user was able to import a file. So, I added another line to the config.rb file copying and replacing the user and password with my credentials which are also a valid server user. AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" I am now able to load a file. I had not understood this requirement for importing. Thanks, Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 From: Kerr, Susan Sent: Wednesday, April 01, 2015 8:47 AM To: 'Archivesspace Users Group' Subject: RE: [Archivesspace_Users_Group] Import error with Accession CSV Template Sadly, I am not experienced enough to interpret your question. This is a test WAMP environment on my computer where I have admin rights and can delete files in the folder. The user account on the server in this case is "aspace" with ALL privileges, Grant YES. When I try to edit this, I see that there are no Table-specific privileges. This is from my config.rb file and is the only not-commented line in that file: AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" The user logged into ArchiveSpace is my personal account and I am an administrator. Baby steps. Thanks, Susan From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 31, 2015 5:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Hi, What I am seeing is that the job completed, but the last step ( removing the import file ) is running into a permission problem. Not sure about what your deployment method is, but does the use running the application have delete permissions in the application's data directory? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Tuesday, March 31, 2015 10:34 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Log file is attached. Thanks, Susan From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 31, 2015 3:27 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Hi Susan, What does the archivesspace.out log file say? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Tuesday, March 31, 2015 8:08 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Import error with Accession CSV Template I am trying to use the http://www.archivesspace.org/importexport Accession CSV Template with some very basic information for a test accession. System details: ArchivesSpace version 1.1.2; Windows Apache MySQL PHP (WAMP) Most of my experiments resulted in this error !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! When I removed all but the three elements required of an accession: title, accession_number, accession date, I get this error: ================================================== testAccImport.csv ================================================== 1. STARTED: Reading JSON records 1. DONE: Reading JSON records 2. STARTED: Validating records and checking links 2. DONE: Validating records and checking links 3. STARTED: Evaluating record relationships 3. DONE: Evaluating record relationships 4. STARTED: Saving records: cycle 1 Created: /repositories/import/accessions/import_24b4c82f-7f39-475d-aabd-5d58e4dbe696 4. DONE: Saving records: cycle 1 5. STARTED: Cleaning up 5. DONE: Cleaning up !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!! This is the test import file. accession_title,accession_number_1,accession_number_2,accession_number_3,accession_number_4,accession_accession_date,accession_access_restrictions,accession_access_restrictions_note,accession_acquisition_type,accession_condition_description,accession_content_description,accession_disposition,accession_general_note,accession_inventory,accession_provenance,accession_publish,accession_resource_type,accession_restrictions_apply,accession_retention_rule,accession_use_restrictions,accession_use_restrictions_note,accession_cataloged_note,accession_processing_hours_total,accession_processing_plan,accession_processing_priority,accession_processing_status,accession_processing_started_date,accession_processing_total_extent,accession_processing_total_extent_type,accession_processors,accession_rights_determined,date_1_label,date_1_expression,date_1_begin,date_1_end,date_1_type,date_2_label,date_2_expression,date_2_begin,date_2_end,date_2_type,extent_type,extent_container_summary,extent_number,accession_acknowledgement_sent,accession_acknowledgement_sent_date,accession_agreement_received,accession_agreement_received_date,accession_agreement_sent,accession_agreement_sent_date,accession_cataloged,accession_cataloged_date,accession_processed,accession_processed_date,user_defined_boolean_t,user_defined_boolean_2,user_defined_boolean_3,user_defined_integer_1,user_defined_integer_2,user_defined_integer_3,user_defined_real_1,user_defined_real_2,user_defined_real_3,user_defined_string_1,user_defined_string_2,user_defined_string_3,user_defined_string_4,user_defined_text_1,user_defined_text_2,user_defined_text_3,user_defined_text_4,user_defined_text_5,user_defined_date_1,user_defined_date_2,user_defined_date_3,user_defined_enum_1,user_defined_enum_2,user_defined_enum_3,user_defined_enum_4,agent_role,agent_type,agent_contact_address_1,agent_contact_address_2,agent_contact_address_3,agent_contact_city,agent_contact_country,agent_contact_email,agent_contact_fax,agent_contact_name,agent_contact_post_code,agent_contact_region,agent_contact_salutation,agent_contact_telephone,agent_contact_telephone_ext,agent_name_authority_id,agent_name_dates,agent_name_fuller_form,agent_name_name_order,agent_name_number,agent_name_prefix,agent_name_primary_name,agent_name_qualifier,agent_name_rest_of_name,agent_name_rules,agent_name_sort_name,agent_name_source,agent_name_subordinate_name_1,agent_name_subordinate_name_2,agent_name_suffix,agent_name_description_note,agent_name_description_citation,subject_source,subject_term,subject_term_type 29-Mar-94,1994-001,,,,1994-03-29,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, I have also tried to import a file that had successfully imported in a Linux environment and get the error with no results. I would appreciate any help in solving this problem Thanks, Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Wed Apr 1 15:52:37 2015 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Wed, 1 Apr 2015 19:52:37 +0000 Subject: [Archivesspace_Users_Group] Parallel Expressions in Extents Message-ID: Hi All- We (Dartmouth) are ramping up our custom development and starting to finalize the data mapping between our old system and ArchivesSpace. One of the areas that we're having a bit of trouble with is extents - specifically parallel expressions. For example, we have about 400 resources whose extents look something like: 98 boxes (147 linear ft.) 54 volumes OR 252 boxes (378 linear ft.) 157 rolls 168 folders OR 45 sound cassettes (45 hours) 1 transcript (782 pages) 10 boxes (3 linear ft.) What would be the recommended way of entering this data in ArchivesSpace? Thanks! Joshua -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Wed Apr 1 16:11:46 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Wed, 1 Apr 2015 16:11:46 -0400 Subject: [Archivesspace_Users_Group] Parallel Expressions in Extents In-Reply-To: References: Message-ID: Hi Joshua, You have the option to have more than one extent expression on resource items. I'm not entirely sure what you mean by 'recommended way' of entering the data, but you could have a collection with three extent expressions: 1 for boxes, 1 for folders, 1 for cassettes, etc. Is that what you meant? -Maura On Wed, Apr 1, 2015 at 3:52 PM, Joshua D. Shaw wrote: > Hi All- > > We (Dartmouth) are ramping up our custom development and starting to > finalize the data mapping between our old system and ArchivesSpace. One of > the areas that we're having a bit of trouble with is extents - specifically > parallel expressions. For example, we have about 400 resources whose > extents look something like: > > 98 boxes (147 linear ft.) > 54 volumes > > OR > > 252 boxes (378 linear ft.) > 157 rolls > 168 folders > > OR > > 45 sound cassettes (45 hours) > 1 transcript (782 pages) > 10 boxes (3 linear ft.) > > What would be the recommended way of entering this data in ArchivesSpace? > > Thanks! > Joshua > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From danelle.moon at sjsu.edu Wed Apr 1 16:22:11 2015 From: danelle.moon at sjsu.edu (Danelle Moon) Date: Wed, 1 Apr 2015 13:22:11 -0700 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: <1427746077682.56800@lyrasis.org> References: <1427746077682.56800@lyrasis.org> Message-ID: Chris Do you have updated documentation for v1.2.0? Or are we to following the documentation instructions for the two previous releases? Please send me the link to the updated documentation needed to proceed with this version Thanks Danelle Danelle Moon Full Librarian Director SJSU Special Collections One Washington Square San Jose, CA 95192-0028 408/808-2061 office 408/808-2063 fax Danelle.Moon at sjsu.edu On Mon, Mar 30, 2015 at 1:07 PM, Chris Fitzpatrick < Chris.Fitzpatrick at lyrasis.org> wrote: > The ArchivesSpace team is happy to release version v1.2.0 > . > > Please see the technical documentation > > for information on how to upgrade your ArchivesSpace installs. > > Please see the release page > for > a listing of all the new features and bug fixes included in this release. > > Of particular note: This release includes an upgrade to Bootstrap 3 > for the staff interface. This version has > significant changes to HTML, CSS, and Javascript components in the > staff UI, so any plugins or custom templates will have to be modified > to work with Bootstrap 3. > > Also included in this release is a Find-And-Replace background job, which > allows users to bulk edit records. As this is a currently a beta-feature, > it is recommended that users backup their database frequently if using this > feature. > > Thanks to all the volunteers on the ArchivesSpace User Advisory and > Technical Advisory Councils, who are vital to keeping ArchivesSpace > development on track. > > Please let us know if you have any questions, comments, or concerns. > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sukerr at davidson.edu Wed Apr 1 16:24:46 2015 From: sukerr at davidson.edu (Kerr, Susan) Date: Wed, 1 Apr 2015 20:24:46 +0000 Subject: [Archivesspace_Users_Group] NEW Import error with Accession CSV Template Message-ID: <4a8dbd7a8b9249d599e0baead0ee62c3@MBX13A.davidson.edu> After this initial test, I have discovered that I am only able to import ONE file successfully. To get a 2nd file imported, I must stop the application and restart the server. Then the file which failed imports successfully. Is there some setting that I need to add to allow multiple imports? Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kerr, Susan Sent: Wednesday, April 01, 2015 3:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Further experimenting, I found that if I created a user account in ArchivesSpace for the aspace db user, that user was able to import a file. So, I added another line to the config.rb file copying and replacing the user and password with my credentials which are also a valid server user. AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" I am now able to load a file. I had not understood this requirement for importing. Thanks, Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 From: Kerr, Susan Sent: Wednesday, April 01, 2015 8:47 AM To: 'Archivesspace Users Group' Subject: RE: [Archivesspace_Users_Group] Import error with Accession CSV Template Sadly, I am not experienced enough to interpret your question. This is a test WAMP environment on my computer where I have admin rights and can delete files in the folder. The user account on the server in this case is "aspace" with ALL privileges, Grant YES. When I try to edit this, I see that there are no Table-specific privileges. This is from my config.rb file and is the only not-commented line in that file: AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" The user logged into ArchiveSpace is my personal account and I am an administrator. Baby steps. Thanks, Susan From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 31, 2015 5:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Hi, What I am seeing is that the job completed, but the last step ( removing the import file ) is running into a permission problem. Not sure about what your deployment method is, but does the use running the application have delete permissions in the application's data directory? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Tuesday, March 31, 2015 10:34 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Log file is attached. Thanks, Susan From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 31, 2015 3:27 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Hi Susan, What does the archivesspace.out log file say? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Tuesday, March 31, 2015 8:08 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Import error with Accession CSV Template I am trying to use the http://www.archivesspace.org/importexport Accession CSV Template with some very basic information for a test accession. System details: ArchivesSpace version 1.1.2; Windows Apache MySQL PHP (WAMP) Most of my experiments resulted in this error !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! When I removed all but the three elements required of an accession: title, accession_number, accession date, I get this error: ================================================== testAccImport.csv ================================================== 1. STARTED: Reading JSON records 1. DONE: Reading JSON records 2. STARTED: Validating records and checking links 2. DONE: Validating records and checking links 3. STARTED: Evaluating record relationships 3. DONE: Evaluating record relationships 4. STARTED: Saving records: cycle 1 Created: /repositories/import/accessions/import_24b4c82f-7f39-475d-aabd-5d58e4dbe696 4. DONE: Saving records: cycle 1 5. STARTED: Cleaning up 5. DONE: Cleaning up !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!! This is the test import file. accession_title,accession_number_1,accession_number_2,accession_number_3,accession_number_4,accession_accession_date,accession_access_restrictions,accession_access_restrictions_note,accession_acquisition_type,accession_condition_description,accession_content_description,accession_disposition,accession_general_note,accession_inventory,accession_provenance,accession_publish,accession_resource_type,accession_restrictions_apply,accession_retention_rule,accession_use_restrictions,accession_use_restrictions_note,accession_cataloged_note,accession_processing_hours_total,accession_processing_plan,accession_processing_priority,accession_processing_status,accession_processing_started_date,accession_processing_total_extent,accession_processing_total_extent_type,accession_processors,accession_rights_determined,date_1_label,date_1_expression,date_1_begin,date_1_end,date_1_type,date_2_label,date_2_expression,date_2_begin,date_2_end,date_2_type,extent_type,extent_container_summary,extent_number,accession_acknowledgement_sent,accession_acknowledgement_sent_date,accession_agreement_received,accession_agreement_received_date,accession_agreement_sent,accession_agreement_sent_date,accession_cataloged,accession_cataloged_date,accession_processed,accession_processed_date,user_defined_boolean_t,user_defined_boolean_2,user_defined_boolean_3,user_defined_integer_1,user_defined_integer_2,user_defined_integer_3,user_defined_real_1,user_defined_real_2,user_defined_real_3,user_defined_string_1,user_defined_string_2,user_defined_string_3,user_defined_string_4,user_defined_text_1,user_defined_text_2,user_defined_text_3,user_defined_text_4,user_defined_text_5,user_defined_date_1,user_defined_date_2,user_defined_date_3,user_defined_enum_1,user_defined_enum_2,user_defined_enum_3,user_defined_enum_4,agent_role,agent_type,agent_contact_address_1,agent_contact_address_2,agent_contact_address_3,agent_contact_city,agent_contact_country,agent_contact_email,agent_contact_fax,agent_contact_name,agent_contact_post_code,agent_contact_region,agent_contact_salutation,agent_contact_telephone,agent_contact_telephone_ext,agent_name_authority_id,agent_name_dates,agent_name_fuller_form,agent_name_name_order,agent_name_number,agent_name_prefix,agent_name_primary_name,agent_name_qualifier,agent_name_rest_of_name,agent_name_rules,agent_name_sort_name,agent_name_source,agent_name_subordinate_name_1,agent_name_subordinate_name_2,agent_name_suffix,agent_name_description_note,agent_name_description_citation,subject_source,subject_term,subject_term_type 29-Mar-94,1994-001,,,,1994-03-29,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, I have also tried to import a file that had successfully imported in a Linux environment and get the error with no results. I would appreciate any help in solving this problem Thanks, Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Wed Apr 1 16:27:52 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Wed, 1 Apr 2015 16:27:52 -0400 Subject: [Archivesspace_Users_Group] NEW Import error with Accession CSV Template In-Reply-To: <4a8dbd7a8b9249d599e0baead0ee62c3@MBX13A.davidson.edu> References: <4a8dbd7a8b9249d599e0baead0ee62c3@MBX13A.davidson.edu> Message-ID: Hi Susan, Are you getting an error or is it just staying in queue and never loading? -Maura On Wed, Apr 1, 2015 at 4:24 PM, Kerr, Susan wrote: > After this initial test, I have discovered that I am only able to import > ONE file successfully. To get a 2nd file imported, I must stop the > application and restart the server. Then the file which failed imports > successfully. > > > > Is there some setting that I need to add to allow multiple imports? > > > > Susan > > > > ------------------------------------ > Susan Kerr > Systems Librarian > 704-894-2424, 704-894-2625 (fax) > sukerr at davidson.edu > > > > DAVIDSON COLLEGE LIBRARY > > 209 RIDGE RD > > BOX 7200 > > DAVIDSON, NC 28035-7200 > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Kerr, > Susan > *Sent:* Wednesday, April 01, 2015 3:04 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Import error with Accession > CSV Template > > > > Further experimenting, I found that if I created a user account in > ArchivesSpace for the aspace db user, that user *was* able to import a > file. > > So, I added another line to the config.rb file copying and replacing the > user and password with my credentials which are also a valid server user. > > AppConfig[:db_url] = > "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" > > > > > I am now able to load a file. > > I had not understood this requirement for importing. > > > > Thanks, > > > > Susan > > ------------------------------------ > Susan Kerr > Systems Librarian > 704-894-2424, 704-894-2625 (fax) > sukerr at davidson.edu > > > > DAVIDSON COLLEGE LIBRARY > > 209 RIDGE RD > > BOX 7200 > > DAVIDSON, NC 28035-7200 > > > > > > > > *From:* Kerr, Susan > *Sent:* Wednesday, April 01, 2015 8:47 AM > *To:* 'Archivesspace Users Group' > *Subject:* RE: [Archivesspace_Users_Group] Import error with Accession > CSV Template > > > > Sadly, I am not experienced enough to interpret your question. > > > > This is a test WAMP environment on my computer where I have admin rights > and can delete files in the folder. > > > > The user account on the server in this case is ?aspace? with ALL > privileges, Grant YES. When I try to edit this, I see that there are no > Table-specific privileges. > > This is from my config.rb file and is the only not-commented line in that > file: > > > > AppConfig[:db_url] = > "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" > > > > > The user logged into ArchiveSpace is my personal account and I am an > administrator. > > > > Baby steps. > > > > Thanks, > > Susan > > > > > > > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Chris > Fitzpatrick > *Sent:* Tuesday, March 31, 2015 5:50 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Import error with Accession > CSV Template > > > > Hi, > > > > What I am seeing is that the job completed, but the last step ( removing > the import file ) is running into a permission problem. > > > > Not sure about what your deployment method is, but does the use running > the application have delete permissions in the application's data > directory? > > > > b,chris. > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ------------------------------ > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Kerr, Susan > *Sent:* Tuesday, March 31, 2015 10:34 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Import error with Accession > CSV Template > > > > Log file is attached. > > Thanks, > > Susan > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Chris > Fitzpatrick > *Sent:* Tuesday, March 31, 2015 3:27 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* Re: [Archivesspace_Users_Group] Import error with Accession > CSV Template > > > > Hi Susan, > > > > What does the archivesspace.out log file say? > > > > b,chris. > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ------------------------------ > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Kerr, Susan > *Sent:* Tuesday, March 31, 2015 8:08 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Import error with Accession CSV > Template > > > > I am trying to use the http://www.archivesspace.org/importexport > Accession CSV Template with some very basic information for a test > accession. > > > > System details: ArchivesSpace version 1.1.2; Windows Apache MySQL PHP > (WAMP) > > > > Most of my experiments resulted in this error > > > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > Error: # > > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > > > When I removed all but the three elements required of an accession: title, > accession_number, accession date, I get this error: > > > > ================================================== > > testAccImport.csv > > ================================================== > > 1. STARTED: Reading JSON records > > 1. DONE: Reading JSON records > > 2. STARTED: Validating records and checking links > > 2. DONE: Validating records and checking links > > 3. STARTED: Evaluating record relationships > > 3. DONE: Evaluating record relationships > > 4. STARTED: Saving records: cycle 1 > > Created: > /repositories/import/accessions/import_24b4c82f-7f39-475d-aabd-5d58e4dbe696 > > 4. DONE: Saving records: cycle 1 > > 5. STARTED: Cleaning up > > 5. DONE: Cleaning up > > > > > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > Error: # > > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > !!!!!!!!!!!!!!!!! > > > > This is the test import file. > > > > > accession_title,accession_number_1,accession_number_2,accession_number_3,accession_number_4,accession_accession_date,accession_access_restrictions,accession_access_restrictions_note,accession_acquisition_type,accession_condition_description,accession_content_description,accession_disposition,accession_general_note,accession_inventory,accession_provenance,accession_publish,accession_resource_type,accession_restrictions_apply,accession_retention_rule,accession_use_restrictions,accession_use_restrictions_note,accession_cataloged_note,accession_processing_hours_total,accession_processing_plan,accession_processing_priority,accession_processing_status,accession_processing_started_date,accession_processing_total_extent,accession_processing_total_extent_type,accession_processors,accession_rights_determined,date_1_label,date_1_expression,date_1_begin,date_1_end,date_1_type,date_2_label,date_2_expression,date_2_begin,date_2_end,date_2_type,extent_type,extent_container_summary,extent_number,accession_acknowledgement_sent,accession_acknowledgement_sent_date,accession_agreement_received,accession_agreement_received_date,accession_agreement_sent,accession_agreement_sent_date,accession_cataloged,accession_cataloged_date,accession_processed,accession_processed_date,user_defined_boolean_t,user_defined_boolean_2,user_defined_boolean_3,user_defined_integer_1,user_defined_integer_2,user_defined_integer_3,user_defined_real_1,user_defined_real_2,user_defined_real_3,user_defined_string_1,user_defined_string_2,user_defined_string_3,user_defined_string_4,user_defined_text_1,user_defined_text_2,user_defined_text_3,user_defined_text_4,user_defined_text_5,user_defined_date_1,user_defined_date_2,user_defined_date_3,user_defined_enum_1,user_defined_enum_2,user_defined_enum_3,user_defined_enum_4,agent_role,agent_type,agent_contact_address_1,agent_contact_address_2,agent_contact_address_3,agent_contact_city,agent_contact_country,agent_contact_email,agent_contact_fax,agent_contact_name,agent_contact_post_code,agent_contact_region,agent_contact_salutation,agent_contact_telephone,agent_contact_telephone_ext,agent_name_authority_id,agent_name_dates,agent_name_fuller_form,agent_name_name_order,agent_name_number,agent_name_prefix,agent_name_primary_name,agent_name_qualifier,agent_name_rest_of_name,agent_name_rules,agent_name_sort_name,agent_name_source,agent_name_subordinate_name_1,agent_name_subordinate_name_2,agent_name_suffix,agent_name_description_note,agent_name_description_citation,subject_source,subject_term,subject_term_type > > > 29-Mar-94,1994-001,,,,1994-03-29,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, > > > > I have also tried to import a file that had successfully imported in a > Linux environment and get the error with no results. > > > > I would appreciate any help in solving this problem > > > > Thanks, > > Susan > > > > ------------------------------------ > Susan Kerr > Systems Librarian > 704-894-2424, 704-894-2625 (fax) > sukerr at davidson.edu > > > > DAVIDSON COLLEGE LIBRARY > > 209 RIDGE RD > > BOX 7200 > > DAVIDSON, NC 28035-7200 > > > > > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sukerr at davidson.edu Wed Apr 1 16:29:33 2015 From: sukerr at davidson.edu (Kerr, Susan) Date: Wed, 1 Apr 2015 20:29:33 +0000 Subject: [Archivesspace_Users_Group] NEW Import error with Accession CSV Template In-Reply-To: References: <4a8dbd7a8b9249d599e0baead0ee62c3@MBX13A.davidson.edu> Message-ID: <1d78cac61d8a4f44983ee83ac90b6af5@MBX13A.davidson.edu> It processes then fails with the permissions error when cleaning up. When I restart the server and the application it processes completely. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maura Carbone Sent: Wednesday, April 01, 2015 4:28 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] NEW Import error with Accession CSV Template Hi Susan, Are you getting an error or is it just staying in queue and never loading? -Maura On Wed, Apr 1, 2015 at 4:24 PM, Kerr, Susan > wrote: After this initial test, I have discovered that I am only able to import ONE file successfully. To get a 2nd file imported, I must stop the application and restart the server. Then the file which failed imports successfully. Is there some setting that I need to add to allow multiple imports? Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kerr, Susan Sent: Wednesday, April 01, 2015 3:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Further experimenting, I found that if I created a user account in ArchivesSpace for the aspace db user, that user was able to import a file. So, I added another line to the config.rb file copying and replacing the user and password with my credentials which are also a valid server user. AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" I am now able to load a file. I had not understood this requirement for importing. Thanks, Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 From: Kerr, Susan Sent: Wednesday, April 01, 2015 8:47 AM To: 'Archivesspace Users Group' Subject: RE: [Archivesspace_Users_Group] Import error with Accession CSV Template Sadly, I am not experienced enough to interpret your question. This is a test WAMP environment on my computer where I have admin rights and can delete files in the folder. The user account on the server in this case is ?aspace? with ALL privileges, Grant YES. When I try to edit this, I see that there are no Table-specific privileges. This is from my config.rb file and is the only not-commented line in that file: AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" The user logged into ArchiveSpace is my personal account and I am an administrator. Baby steps. Thanks, Susan From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 31, 2015 5:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Hi, What I am seeing is that the job completed, but the last step ( removing the import file ) is running into a permission problem. Not sure about what your deployment method is, but does the use running the application have delete permissions in the application's data directory? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Tuesday, March 31, 2015 10:34 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Log file is attached. Thanks, Susan From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 31, 2015 3:27 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Hi Susan, What does the archivesspace.out log file say? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Tuesday, March 31, 2015 8:08 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Import error with Accession CSV Template I am trying to use the http://www.archivesspace.org/importexport Accession CSV Template with some very basic information for a test accession. System details: ArchivesSpace version 1.1.2; Windows Apache MySQL PHP (WAMP) Most of my experiments resulted in this error !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! When I removed all but the three elements required of an accession: title, accession_number, accession date, I get this error: ================================================== testAccImport.csv ================================================== 1. STARTED: Reading JSON records 1. DONE: Reading JSON records 2. STARTED: Validating records and checking links 2. DONE: Validating records and checking links 3. STARTED: Evaluating record relationships 3. DONE: Evaluating record relationships 4. STARTED: Saving records: cycle 1 Created: /repositories/import/accessions/import_24b4c82f-7f39-475d-aabd-5d58e4dbe696 4. DONE: Saving records: cycle 1 5. STARTED: Cleaning up 5. DONE: Cleaning up !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!! This is the test import file. accession_title,accession_number_1,accession_number_2,accession_number_3,accession_number_4,accession_accession_date,accession_access_restrictions,accession_access_restrictions_note,accession_acquisition_type,accession_condition_description,accession_content_description,accession_disposition,accession_general_note,accession_inventory,accession_provenance,accession_publish,accession_resource_type,accession_restrictions_apply,accession_retention_rule,accession_use_restrictions,accession_use_restrictions_note,accession_cataloged_note,accession_processing_hours_total,accession_processing_plan,accession_processing_priority,accession_processing_status,accession_processing_started_date,accession_processing_total_extent,accession_processing_total_extent_type,accession_processors,accession_rights_determined,date_1_label,date_1_expression,date_1_begin,date_1_end,date_1_type,date_2_label,date_2_expression,date_2_begin,date_2_end,date_2_type,extent_type,extent_container_summary,extent_number,accession_acknowledgement_sent,accession_acknowledgement_sent_date,accession_agreement_received,accession_agreement_received_date,accession_agreement_sent,accession_agreement_sent_date,accession_cataloged,accession_cataloged_date,accession_processed,accession_processed_date,user_defined_boolean_t,user_defined_boolean_2,user_defined_boolean_3,user_defined_integer_1,user_defined_integer_2,user_defined_integer_3,user_defined_real_1,user_defined_real_2,user_defined_real_3,user_defined_string_1,user_defined_string_2,user_defined_string_3,user_defined_string_4,user_defined_text_1,user_defined_text_2,user_defined_text_3,user_defined_text_4,user_defined_text_5,user_defined_date_1,user_defined_date_2,user_defined_date_3,user_defined_enum_1,user_defined_enum_2,user_defined_enum_3,user_defined_enum_4,agent_role,agent_type,agent_contact_address_1,agent_contact_address_2,agent_contact_address_3,agent_contact_city,agent_contact_country,agent_contact_email,agent_contact_fax,agent_contact_name,agent_contact_post_code,agent_contact_region,agent_contact_salutation,agent_contact_telephone,agent_contact_telephone_ext,agent_name_authority_id,agent_name_dates,agent_name_fuller_form,agent_name_name_order,agent_name_number,agent_name_prefix,agent_name_primary_name,agent_name_qualifier,agent_name_rest_of_name,agent_name_rules,agent_name_sort_name,agent_name_source,agent_name_subordinate_name_1,agent_name_subordinate_name_2,agent_name_suffix,agent_name_description_note,agent_name_description_citation,subject_source,subject_term,subject_term_type 29-Mar-94,1994-001,,,,1994-03-29,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, I have also tried to import a file that had successfully imported in a Linux environment and get the error with no results. I would appreciate any help in solving this problem Thanks, Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Wed Apr 1 17:14:30 2015 From: Kevin.Clair at du.edu (Kevin Clair) Date: Wed, 1 Apr 2015 21:14:30 +0000 Subject: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 Message-ID: <1F1E72103798F04D96C355B296D7C61B47B82A@mb2-uts.du.edu> Hello, I've been testing v1.2.0 this week and noticed while editing records that the columns aren't aligning properly, with the result being that the shortcuts on the left hand side are overlaying the actual editing form and making it difficult to use. I'm attaching a screen shot to show what it looks like. So far I've noticed this with Resources and Archival Objects; not sure if it happens across the board or not. -k -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: broken css 1.png Type: image/png Size: 593056 bytes Desc: broken css 1.png URL: From luftsche at usc.edu Wed Apr 1 19:20:12 2015 From: luftsche at usc.edu (Susan Luftschein) Date: Wed, 1 Apr 2015 23:20:12 +0000 Subject: [Archivesspace_Users_Group] Problems with MARC export Message-ID: Hi programmers, I just exported a MARCXML record that included a Processing Information note. In the MARC record it mapped to a 520 $2 note, and included the header, but not the contents of the note (the note is set to publish). Can you guys look into fixing this? Thanks, Sue Luftschein Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Thu Apr 2 03:02:55 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 2 Apr 2015 07:02:55 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: <551C17A0.3080904@rice.edu> References: <1427746077682.56800@lyrasis.org>,<551C17A0.3080904@rice.edu> Message-ID: <1427958173801.28804@lyrasis.org> Hi Mang Sun, Ah, sorry, this is a thing with Tomcat that the version number has to be hardcoded rather than pulling from the the version file on disk. The version that you downloaded from https://github.com/archivesspace/archivesspace/releases/tag/v1.2.0 is the correct version. b,chris. [https://avatars2.githubusercontent.com/u/1311559?v=3&s=400] Release ArchivesSpace v1.2.0 ? archivesspace/archivesspace ? GitHub archivesspace - The ArchivesSpace archives management tool Read more... Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mang Sun Sent: Wednesday, April 1, 2015 6:06 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released Chris, After I deployed a clone copy of the AS master branch, I see "V1.1.4-dev02" instead of v1.2.0 at the footers of the front and public interfaces. Is it right? Thank you. Mang Sun Rice U. On 3/30/2015 3:07 PM, Chris Fitzpatrick wrote: The ArchivesSpace team is happy to release version v1.2.0. Please see the technical documentation for information on how to upgrade your ArchivesSpace installs. Please see the release page for a listing of all the new features and bug fixes included in this release. Of particular note: This release includes an upgrade to Bootstrap 3 for the staff interface. This version has significant changes to HTML, CSS, and Javascript components in the staff UI, so any plugins or custom templates will have to be modified to work with Bootstrap 3. Also included in this release is a Find-And-Replace background job, which allows users to bulk edit records. As this is a currently a beta-feature, it is recommended that users backup their database frequently if using this feature. Thanks to all the volunteers on the ArchivesSpace User Advisory and Technical Advisory Councils, who are vital to keeping ArchivesSpace development on track. Please let us know if you have any questions, comments, or concerns. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Thu Apr 2 03:14:11 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 2 Apr 2015 07:14:11 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: References: <1427746077682.56800@lyrasis.org>, Message-ID: <1427958850322.21749@lyrasis.org> Hi Danelle, Which documentation are you referring to? The technical documentation is on http://archivesspace.github.io/archivesspace/doc/ and the User documentation is at https://docs.archivesspace.org/_help_proxy/login . B,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Danelle Moon Sent: Wednesday, April 1, 2015 10:22 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released Chris Do you have updated documentation for v1.2.0? Or are we to following the documentation instructions for the two previous releases? Please send me the link to the updated documentation needed to proceed with this version Thanks Danelle Danelle Moon Full Librarian Director SJSU Special Collections One Washington Square San Jose, CA 95192-0028 408/808-2061 office 408/808-2063 fax Danelle.Moon at sjsu.edu On Mon, Mar 30, 2015 at 1:07 PM, Chris Fitzpatrick > wrote: The ArchivesSpace team is happy to release version v1.2.0. Please see the technical documentation for information on how to upgrade your ArchivesSpace installs. Please see the release page for a listing of all the new features and bug fixes included in this release. Of particular note: This release includes an upgrade to Bootstrap 3 for the staff interface. This version has significant changes to HTML, CSS, and Javascript components in the staff UI, so any plugins or custom templates will have to be modified to work with Bootstrap 3. Also included in this release is a Find-And-Replace background job, which allows users to bulk edit records. As this is a currently a beta-feature, it is recommended that users backup their database frequently if using this feature. Thanks to all the volunteers on the ArchivesSpace User Advisory and Technical Advisory Councils, who are vital to keeping ArchivesSpace development on track. Please let us know if you have any questions, comments, or concerns. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Thu Apr 2 03:18:32 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 2 Apr 2015 07:18:32 +0000 Subject: [Archivesspace_Users_Group] NEW Import error with Accession CSV Template In-Reply-To: <1d78cac61d8a4f44983ee83ac90b6af5@MBX13A.davidson.edu> References: <4a8dbd7a8b9249d599e0baead0ee62c3@MBX13A.davidson.edu> , <1d78cac61d8a4f44983ee83ac90b6af5@MBX13A.davidson.edu> Message-ID: <1427959110038.68519@lyrasis.org> Hi Susan, Yes, I think you have some file level permissions issues. The final step of the import job is to clean up and delete the import file from disk, which the log you sent indicated it could not do. What are the file permissions in the data/shared directory? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kerr, Susan Sent: Wednesday, April 1, 2015 10:29 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] NEW Import error with Accession CSV Template It processes then fails with the permissions error when cleaning up. When I restart the server and the application it processes completely. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maura Carbone Sent: Wednesday, April 01, 2015 4:28 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] NEW Import error with Accession CSV Template Hi Susan, Are you getting an error or is it just staying in queue and never loading? -Maura On Wed, Apr 1, 2015 at 4:24 PM, Kerr, Susan > wrote: After this initial test, I have discovered that I am only able to import ONE file successfully. To get a 2nd file imported, I must stop the application and restart the server. Then the file which failed imports successfully. Is there some setting that I need to add to allow multiple imports? Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kerr, Susan Sent: Wednesday, April 01, 2015 3:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Further experimenting, I found that if I created a user account in ArchivesSpace for the aspace db user, that user was able to import a file. So, I added another line to the config.rb file copying and replacing the user and password with my credentials which are also a valid server user. AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" I am now able to load a file. I had not understood this requirement for importing. Thanks, Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 From: Kerr, Susan Sent: Wednesday, April 01, 2015 8:47 AM To: 'Archivesspace Users Group' Subject: RE: [Archivesspace_Users_Group] Import error with Accession CSV Template Sadly, I am not experienced enough to interpret your question. This is a test WAMP environment on my computer where I have admin rights and can delete files in the folder. The user account on the server in this case is ?aspace? with ALL privileges, Grant YES. When I try to edit this, I see that there are no Table-specific privileges. This is from my config.rb file and is the only not-commented line in that file: AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" The user logged into ArchiveSpace is my personal account and I am an administrator. Baby steps. Thanks, Susan From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 31, 2015 5:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Hi, What I am seeing is that the job completed, but the last step ( removing the import file ) is running into a permission problem. Not sure about what your deployment method is, but does the use running the application have delete permissions in the application's data directory? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Tuesday, March 31, 2015 10:34 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Log file is attached. Thanks, Susan From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 31, 2015 3:27 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Hi Susan, What does the archivesspace.out log file say? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Tuesday, March 31, 2015 8:08 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Import error with Accession CSV Template I am trying to use the http://www.archivesspace.org/importexport Accession CSV Template with some very basic information for a test accession. System details: ArchivesSpace version 1.1.2; Windows Apache MySQL PHP (WAMP) Most of my experiments resulted in this error !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! When I removed all but the three elements required of an accession: title, accession_number, accession date, I get this error: ================================================== testAccImport.csv ================================================== 1. STARTED: Reading JSON records 1. DONE: Reading JSON records 2. STARTED: Validating records and checking links 2. DONE: Validating records and checking links 3. STARTED: Evaluating record relationships 3. DONE: Evaluating record relationships 4. STARTED: Saving records: cycle 1 Created: /repositories/import/accessions/import_24b4c82f-7f39-475d-aabd-5d58e4dbe696 4. DONE: Saving records: cycle 1 5. STARTED: Cleaning up 5. DONE: Cleaning up !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!! This is the test import file. accession_title,accession_number_1,accession_number_2,accession_number_3,accession_number_4,accession_accession_date,accession_access_restrictions,accession_access_restrictions_note,accession_acquisition_type,accession_condition_description,accession_content_description,accession_disposition,accession_general_note,accession_inventory,accession_provenance,accession_publish,accession_resource_type,accession_restrictions_apply,accession_retention_rule,accession_use_restrictions,accession_use_restrictions_note,accession_cataloged_note,accession_processing_hours_total,accession_processing_plan,accession_processing_priority,accession_processing_status,accession_processing_started_date,accession_processing_total_extent,accession_processing_total_extent_type,accession_processors,accession_rights_determined,date_1_label,date_1_expression,date_1_begin,date_1_end,date_1_type,date_2_label,date_2_expression,date_2_begin,date_2_end,date_2_type,extent_type,extent_container_summary,extent_number,accession_acknowledgement_sent,accession_acknowledgement_sent_date,accession_agreement_received,accession_agreement_received_date,accession_agreement_sent,accession_agreement_sent_date,accession_cataloged,accession_cataloged_date,accession_processed,accession_processed_date,user_defined_boolean_t,user_defined_boolean_2,user_defined_boolean_3,user_defined_integer_1,user_defined_integer_2,user_defined_integer_3,user_defined_real_1,user_defined_real_2,user_defined_real_3,user_defined_string_1,user_defined_string_2,user_defined_string_3,user_defined_string_4,user_defined_text_1,user_defined_text_2,user_defined_text_3,user_defined_text_4,user_defined_text_5,user_defined_date_1,user_defined_date_2,user_defined_date_3,user_defined_enum_1,user_defined_enum_2,user_defined_enum_3,user_defined_enum_4,agent_role,agent_type,agent_contact_address_1,agent_contact_address_2,agent_contact_address_3,agent_contact_city,agent_contact_country,agent_contact_email,agent_contact_fax,agent_contact_name,agent_contact_post_code,agent_contact_region,agent_contact_salutation,agent_contact_telephone,agent_contact_telephone_ext,agent_name_authority_id,agent_name_dates,agent_name_fuller_form,agent_name_name_order,agent_name_number,agent_name_prefix,agent_name_primary_name,agent_name_qualifier,agent_name_rest_of_name,agent_name_rules,agent_name_sort_name,agent_name_source,agent_name_subordinate_name_1,agent_name_subordinate_name_2,agent_name_suffix,agent_name_description_note,agent_name_description_citation,subject_source,subject_term,subject_term_type 29-Mar-94,1994-001,,,,1994-03-29,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, I have also tried to import a file that had successfully imported in a Linux environment and get the error with no results. I would appreciate any help in solving this problem Thanks, Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Thu Apr 2 07:31:43 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Thu, 2 Apr 2015 11:31:43 +0000 Subject: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 In-Reply-To: <1F1E72103798F04D96C355B296D7C61B47B82A@mb2-uts.du.edu> References: <1F1E72103798F04D96C355B296D7C61B47B82A@mb2-uts.du.edu> Message-ID: Hi, Kevin, Thanks for reporting this problem. Unfortunately, I have not been able to replicate it. I tried to using two resource records in the sandbox: http://sandbox.archivesspace.org/resources/6/edit#tree::resource_6 and http://sandbox.archivesspace.org/resources/13/edit#tree::resource_13. Perhaps there are some specific steps that trigger it. Can you provide any more details? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair Sent: Wednesday, April 01, 2015 5:15 PM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 Hello, I've been testing v1.2.0 this week and noticed while editing records that the columns aren't aligning properly, with the result being that the shortcuts on the left hand side are overlaying the actual editing form and making it difficult to use. I'm attaching a screen shot to show what it looks like. So far I've noticed this with Resources and Archival Objects; not sure if it happens across the board or not. -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Thu Apr 2 08:49:46 2015 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 2 Apr 2015 12:49:46 +0000 Subject: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 In-Reply-To: References: <1F1E72103798F04D96C355B296D7C61B47B82A@mb2-uts.du.edu>, Message-ID: <1F1E72103798F04D96C355B296D7C61B47B995@mb2-uts.du.edu> Hi Brad, Thanks for your reply. Hearing you couldn't replicate it made me think it might be an issue with my local plugins; turning them off solved the problem. Guess I have some cleaning up to do in there... thanks again! I've noticed a few other, more minor layout issues with the new stylesheets, if you happen to want a list of those. -k ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Brad Westbrook [brad.westbrook at lyrasis.org] Sent: Thursday, April 02, 2015 5:31 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 Hi, Kevin, Thanks for reporting this problem. Unfortunately, I have not been able to replicate it. I tried to using two resource records in the sandbox: http://sandbox.archivesspace.org/resources/6/edit#tree::resource_6 and http://sandbox.archivesspace.org/resources/13/edit#tree::resource_13. Perhaps there are some specific steps that trigger it. Can you provide any more details? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair Sent: Wednesday, April 01, 2015 5:15 PM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 Hello, I?ve been testing v1.2.0 this week and noticed while editing records that the columns aren?t aligning properly, with the result being that the shortcuts on the left hand side are overlaying the actual editing form and making it difficult to use. I?m attaching a screen shot to show what it looks like. So far I?ve noticed this with Resources and Archival Objects; not sure if it happens across the board or not. -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Thu Apr 2 09:04:15 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Thu, 2 Apr 2015 13:04:15 +0000 Subject: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 In-Reply-To: <1F1E72103798F04D96C355B296D7C61B47B995@mb2-uts.du.edu> References: <1F1E72103798F04D96C355B296D7C61B47B82A@mb2-uts.du.edu>, <1F1E72103798F04D96C355B296D7C61B47B995@mb2-uts.du.edu> Message-ID: Hi, Kevin, Please send the list along. And am glad you are able to locate the problem you experienced yesterday. Brad From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair Sent: Thursday, April 02, 2015 8:50 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 Hi Brad, Thanks for your reply. Hearing you couldn't replicate it made me think it might be an issue with my local plugins; turning them off solved the problem. Guess I have some cleaning up to do in there... thanks again! I've noticed a few other, more minor layout issues with the new stylesheets, if you happen to want a list of those. -k ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Brad Westbrook [brad.westbrook at lyrasis.org] Sent: Thursday, April 02, 2015 5:31 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 Hi, Kevin, Thanks for reporting this problem. Unfortunately, I have not been able to replicate it. I tried to using two resource records in the sandbox: http://sandbox.archivesspace.org/resources/6/edit#tree::resource_6 and http://sandbox.archivesspace.org/resources/13/edit#tree::resource_13. Perhaps there are some specific steps that trigger it. Can you provide any more details? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair Sent: Wednesday, April 01, 2015 5:15 PM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 Hello, I've been testing v1.2.0 this week and noticed while editing records that the columns aren't aligning properly, with the result being that the shortcuts on the left hand side are overlaying the actual editing form and making it difficult to use. I'm attaching a screen shot to show what it looks like. So far I've noticed this with Resources and Archival Objects; not sure if it happens across the board or not. -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Thu Apr 2 09:20:23 2015 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Thu, 2 Apr 2015 09:20:23 -0400 Subject: [Archivesspace_Users_Group] Display issues with instances/Digital Objects? Message-ID: We have installed 1.2.0 on our dev server, and I noticed a couple of weird display issues with the Instances and Digital objects screens. I've attached screenshots. Has anyone else seen these? We haven't made any plugins that would change these sections, so I assume it's an issue with the base code. Thanks, Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: File_Version_1.2.0.JPG Type: image/jpeg Size: 61627 bytes Desc: File_Version_1.2.0.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Instances_1.2.0.JPG Type: image/jpeg Size: 32914 bytes Desc: Instances_1.2.0.JPG URL: From Joshua.D.Shaw at dartmouth.edu Thu Apr 2 09:59:27 2015 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Thu, 2 Apr 2015 13:59:27 +0000 Subject: [Archivesspace_Users_Group] Parallel Expressions in Extents Message-ID: <8F95A035-900D-4F1B-A727-6EF7DEAD3E08@dartmouth.edu> Hi Maura- I should have been a bit clearer in my first post. The problem that I see is that when you have one or more parallel expressions of extent there's no obvious way to enter what are otherwise legal DACS extent expressions. The best example I can come up with is: 1 transcript (782 pages) 10 boxes (15 linear ft.) There's no container in the transcript expression, nor is there a dimension or physical detail specified. That leaves us with two parallel extents statements: a) 1 transcript & b) 782 pages. It appears that we would have to enter these as two separate extent instances in AS. Now that's fine if there are only these two statements and we mark both as "whole" for the portion. However, what happens when you mix in the other extent expression: 10 boxes (15 linear ft.)? There is no way to link the extents that are parallel expressions since you would essentially have something like: Extent 1: Portion, 1, transcript Extent 2: Portion, 782, pages Extent 3: Portion, 15, linear ft. with "container summary" set to: 25 boxes Its impossible (at least from a scripting perspective and hence MARC export) to be certain that Extent 1 & Extent 2 are parallel expressions. Does that explain the issue more? I'm hoping I'm missing something simple! Thanks! Joshua -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Thu Apr 2 10:22:13 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Thu, 2 Apr 2015 14:22:13 +0000 Subject: [Archivesspace_Users_Group] Problems with MARC export In-Reply-To: References: Message-ID: Hi, Sue, Thanks for catching and reporting this problem. It is, indeed, something new in v.1.2.0. I have filed a bug report (https://archivesspace.atlassian.net/browse/AR-1187?jql=) Brad From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Wednesday, April 01, 2015 7:20 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Problems with MARC export Hi programmers, I just exported a MARCXML record that included a Processing Information note. In the MARC record it mapped to a 520 $2 note, and included the header, but not the contents of the note (the note is set to publish). Can you guys look into fixing this? Thanks, Sue Luftschein Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sukerr at davidson.edu Thu Apr 2 11:08:53 2015 From: sukerr at davidson.edu (Kerr, Susan) Date: Thu, 2 Apr 2015 15:08:53 +0000 Subject: [Archivesspace_Users_Group] NEW Import error with Accession CSV Template In-Reply-To: <1427959110038.68519@lyrasis.org> References: <4a8dbd7a8b9249d599e0baead0ee62c3@MBX13A.davidson.edu> , <1d78cac61d8a4f44983ee83ac90b6af5@MBX13A.davidson.edu> <1427959110038.68519@lyrasis.org> Message-ID: Thanks Chris, This is what I have tried so far: Full rights to all users on C:\wamp\www\archivesspace-v1.1.2\archivesspace\data\shared - failure with 2nd import, nothing is removed from the tmp folder, all load reports are in the C:\wamp\www\archivesspace-v1.1.2\archivesspace\data\shared\import_jobs Full rights to all users on C:\wamp\www\archivesspace-v1.1.2\archivesspace\data - same behavior Yesterday, I made sure that the aspace user and sukerr user accounts had full rights on the database and had entries in the config.rb. This step allowed these ArchivesSpace users to successfully import one file, but fail on the 2nd file. Attached is part of the log from my most recent restart where the first file succeeds and the 2nd file fails. With each experiment, the failed file will import successfully after restarting the ArchivesSpace application. Thanks, Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Thursday, April 02, 2015 3:19 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] NEW Import error with Accession CSV Template Hi Susan, Yes, I think you have some file level permissions issues. The final step of the import job is to clean up and delete the import file from disk, which the log you sent indicated it could not do. What are the file permissions in the data/shared directory? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Wednesday, April 1, 2015 10:29 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] NEW Import error with Accession CSV Template It processes then fails with the permissions error when cleaning up. When I restart the server and the application it processes completely. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maura Carbone Sent: Wednesday, April 01, 2015 4:28 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] NEW Import error with Accession CSV Template Hi Susan, Are you getting an error or is it just staying in queue and never loading? -Maura On Wed, Apr 1, 2015 at 4:24 PM, Kerr, Susan > wrote: After this initial test, I have discovered that I am only able to import ONE file successfully. To get a 2nd file imported, I must stop the application and restart the server. Then the file which failed imports successfully. Is there some setting that I need to add to allow multiple imports? Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kerr, Susan Sent: Wednesday, April 01, 2015 3:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Further experimenting, I found that if I created a user account in ArchivesSpace for the aspace db user, that user was able to import a file. So, I added another line to the config.rb file copying and replacing the user and password with my credentials which are also a valid server user. AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" I am now able to load a file. I had not understood this requirement for importing. Thanks, Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 From: Kerr, Susan Sent: Wednesday, April 01, 2015 8:47 AM To: 'Archivesspace Users Group' Subject: RE: [Archivesspace_Users_Group] Import error with Accession CSV Template Sadly, I am not experienced enough to interpret your question. This is a test WAMP environment on my computer where I have admin rights and can delete files in the folder. The user account on the server in this case is "aspace" with ALL privileges, Grant YES. When I try to edit this, I see that there are no Table-specific privileges. This is from my config.rb file and is the only not-commented line in that file: AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=aspace&password=aspace123&useUnicode=true&characterEncoding=UTF-8" The user logged into ArchiveSpace is my personal account and I am an administrator. Baby steps. Thanks, Susan From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 31, 2015 5:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Hi, What I am seeing is that the job completed, but the last step ( removing the import file ) is running into a permission problem. Not sure about what your deployment method is, but does the use running the application have delete permissions in the application's data directory? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Tuesday, March 31, 2015 10:34 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Log file is attached. Thanks, Susan From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Tuesday, March 31, 2015 3:27 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] Import error with Accession CSV Template Hi Susan, What does the archivesspace.out log file say? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kerr, Susan > Sent: Tuesday, March 31, 2015 8:08 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Import error with Accession CSV Template I am trying to use the http://www.archivesspace.org/importexport Accession CSV Template with some very basic information for a test accession. System details: ArchivesSpace version 1.1.2; Windows Apache MySQL PHP (WAMP) Most of my experiments resulted in this error !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! When I removed all but the three elements required of an accession: title, accession_number, accession date, I get this error: ================================================== testAccImport.csv ================================================== 1. STARTED: Reading JSON records 1. DONE: Reading JSON records 2. STARTED: Validating records and checking links 2. DONE: Validating records and checking links 3. STARTED: Evaluating record relationships 3. DONE: Evaluating record relationships 4. STARTED: Saving records: cycle 1 Created: /repositories/import/accessions/import_24b4c82f-7f39-475d-aabd-5d58e4dbe696 4. DONE: Saving records: cycle 1 5. STARTED: Cleaning up 5. DONE: Cleaning up !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! IMPORT ERROR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Error: # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!! This is the test import file. accession_title,accession_number_1,accession_number_2,accession_number_3,accession_number_4,accession_accession_date,accession_access_restrictions,accession_access_restrictions_note,accession_acquisition_type,accession_condition_description,accession_content_description,accession_disposition,accession_general_note,accession_inventory,accession_provenance,accession_publish,accession_resource_type,accession_restrictions_apply,accession_retention_rule,accession_use_restrictions,accession_use_restrictions_note,accession_cataloged_note,accession_processing_hours_total,accession_processing_plan,accession_processing_priority,accession_processing_status,accession_processing_started_date,accession_processing_total_extent,accession_processing_total_extent_type,accession_processors,accession_rights_determined,date_1_label,date_1_expression,date_1_begin,date_1_end,date_1_type,date_2_label,date_2_expression,date_2_begin,date_2_end,date_2_type,extent_type,extent_container_summary,extent_number,accession_acknowledgement_sent,accession_acknowledgement_sent_date,accession_agreement_received,accession_agreement_received_date,accession_agreement_sent,accession_agreement_sent_date,accession_cataloged,accession_cataloged_date,accession_processed,accession_processed_date,user_defined_boolean_t,user_defined_boolean_2,user_defined_boolean_3,user_defined_integer_1,user_defined_integer_2,user_defined_integer_3,user_defined_real_1,user_defined_real_2,user_defined_real_3,user_defined_string_1,user_defined_string_2,user_defined_string_3,user_defined_string_4,user_defined_text_1,user_defined_text_2,user_defined_text_3,user_defined_text_4,user_defined_text_5,user_defined_date_1,user_defined_date_2,user_defined_date_3,user_defined_enum_1,user_defined_enum_2,user_defined_enum_3,user_defined_enum_4,agent_role,agent_type,agent_contact_address_1,agent_contact_address_2,agent_contact_address_3,agent_contact_city,agent_contact_country,agent_contact_email,agent_contact_fax,agent_contact_name,agent_contact_post_code,agent_contact_region,agent_contact_salutation,agent_contact_telephone,agent_contact_telephone_ext,agent_name_authority_id,agent_name_dates,agent_name_fuller_form,agent_name_name_order,agent_name_number,agent_name_prefix,agent_name_primary_name,agent_name_qualifier,agent_name_rest_of_name,agent_name_rules,agent_name_sort_name,agent_name_source,agent_name_subordinate_name_1,agent_name_subordinate_name_2,agent_name_suffix,agent_name_description_note,agent_name_description_citation,subject_source,subject_term,subject_term_type 29-Mar-94,1994-001,,,,1994-03-29,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, I have also tried to import a file that had successfully imported in a Linux environment and get the error with no results. I would appreciate any help in solving this problem Thanks, Susan ------------------------------------ Susan Kerr Systems Librarian 704-894-2424, 704-894-2625 (fax) sukerr at davidson.edu DAVIDSON COLLEGE LIBRARY 209 RIDGE RD BOX 7200 DAVIDSON, NC 28035-7200 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: archivesspaceReport2.out Type: application/octet-stream Size: 297328 bytes Desc: archivesspaceReport2.out URL: From ktari at westfordma.gov Thu Apr 2 11:14:21 2015 From: ktari at westfordma.gov (Kaari Tari) Date: Thu, 02 Apr 2015 11:14:21 -0400 Subject: [Archivesspace_Users_Group] printing EAD finding aid as a pdf? Message-ID: Hi, The export option to print an EAD record as a pdf is not available in version 1.2.0. Is there another way to print out a finding aid? Thanks, Kaari Kaari Mai Tari Town Clerk 55 Main Street Westford, MA 01886 tel: 978-692-5515 fax: 978-399-2555 general office email: townclerk at westfordma.gov www.westfordma.gov ________________________________________________________________ All email messages and attached content sent from and to this email account are public records unless qualified as an exemption under the [ http://www.sec.state.ma.us/pre/preidx.htm ]Massachusetts Public Records Law. -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianjhoffman at gmail.com Thu Apr 2 11:17:06 2015 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Thu, 2 Apr 2015 11:17:06 -0400 Subject: [Archivesspace_Users_Group] printing EAD finding aid as a pdf? In-Reply-To: References: Message-ID: <2A149BCB-E4C8-40ED-AD69-D94C2162B5A9@gmail.com> Hi Kari, It has moved to the ?Background jobs? page because it is now a job you start and wait for, like an import. Brian On Apr 2, 2015, at 11:14 AM, Kaari Tari wrote: > Hi, > > The export option to print an EAD record as a pdf is not available in version 1.2.0. Is there another way to print out a finding aid? > > Thanks, > > Kaari > > Kaari Mai Tari > Town Clerk > 55 Main Street > Westford, MA 01886 > tel: 978-692-5515 > fax: 978-399-2555 > general office email: townclerk at westfordma.gov > www.westfordma.gov > > > > ________________________________________________________________ > All email messages and attached content sent from and to this email account are public records unless qualified as an exemption under the Massachusetts Public Records Law. > > _______________________________________________ > 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 Thu Apr 2 11:17:48 2015 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Thu, 2 Apr 2015 11:17:48 -0400 Subject: [Archivesspace_Users_Group] printing EAD finding aid as a pdf? In-Reply-To: References: Message-ID: Kaari, It?s in background jobs now. Still available for me. Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kaari Tari Sent: Thursday, April 02, 2015 11:14 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] printing EAD finding aid as a pdf? Hi, The export option to print an EAD record as a pdf is not available in version 1.2.0. Is there another way to print out a finding aid? Thanks, Kaari Kaari Mai Tari Town Clerk 55 Main Street Westford, MA 01886 tel: 978-692-5515 fax: 978-399-2555 general office email: townclerk at westfordma.gov www.westfordma.gov ________________________________________________________________ All email messages and attached content sent from and to this email account are public records unless qualified as an exemption under the Massachusetts Public Records Law. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Thu Apr 2 11:27:16 2015 From: sdm7g at virginia.edu (Steven Majewski) Date: Thu, 2 Apr 2015 11:27:16 -0400 Subject: [Archivesspace_Users_Group] printing EAD finding aid as a pdf? In-Reply-To: References: Message-ID: I notice with the background job method, the downloaded PDF gets named by the job: ?job_4_file_6.pdf? instead of getting named from the MSS number: ?MSS13421_ead.pdf? The former naming scheme was much more useful. Could we bring that back ? ? Steve Majewski On Apr 2, 2015, at 11:17 AM, Galligan, Patrick wrote: > Kaari, > > It?s in background jobs now. Still available for me. > > > > Patrick Galligan > Rockefeller Archive Center > Assistant Digital Archivist > 914-366-6386 > > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf OfKaari Tari > Sent: Thursday, April 02, 2015 11:14 AM > To: archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] printing EAD finding aid as a pdf? > > > Hi, > > The export option to print an EAD record as a pdf is not available in version 1.2.0. Is there another way to print out a finding aid? > > Thanks, > > Kaari > > Kaari Mai Tari > Town Clerk > 55 Main Street > Westford, MA 01886 > tel: 978-692-5515 > fax: 978-399-2555 > general office email: townclerk at westfordma.gov > www.westfordma.gov > > > > ________________________________________________________________ > All email messages and attached content sent from and to this email account are public records unless qualified as an exemption under theMassachusetts Public Records Law. > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: From ktari at westfordma.gov Thu Apr 2 11:39:03 2015 From: ktari at westfordma.gov (Kaari Tari) Date: Thu, 02 Apr 2015 11:39:03 -0400 Subject: [Archivesspace_Users_Group] printing EAD finding aid as a pdf? In-Reply-To: <2A149BCB-E4C8-40ED-AD69-D94C2162B5A9@gmail.com> References: <2A149BCB-E4C8-40ED-AD69-D94C2162B5A9@gmail.com> Message-ID: Thank you!! Kaari Mai Tari Town Clerk 55 Main Street Westford, MA 01886 tel: 978-692-5515 fax: 978-399-2555 general office email: townclerk at westfordma.gov www.westfordma.gov Archivesspace Users Group on Thursday, April 02, 2015 at 11:17 AM -0400 wrote: >Hi Kari, > > >It has moved to the ?Background jobs? page because it is now a job >you start and wait for, like an import. > > >Brian > > > >On Apr 2, 2015, at 11:14 AM, Kaari Tari <[ mailto:ktari at westfordma.gov >]ktari at westfordma.gov> wrote: > > > >Hi, > >The export option to print an EAD record as a pdf is not available in >version 1.2.0. ?Is there another way to print out a finding aid? > >Thanks, > >Kaari > >Kaari Mai Tari >Town Clerk >55 Main Street >Westford, MA ?01886 >tel: 978-692-5515 >fax: 978-399-2555 >general office email: ?[ mailto:townclerk at westfordma.gov >]townclerk at westfordma.gov >[ http://www.westfordma.gov/ ]www.westfordma.gov > > > >________________________________________________________________ >All email messages and attached content sent from and to this email >account are public records unless qualified as an exemption under the?[ >http://www.sec.state.ma.us/pre/preidx.htm ]Massachusetts Public Records >Law. > >_______________________________________________ >Archivesspace_Users_Group mailing list >[ mailto:Archivesspace_Users_Group at lyralists.lyrasis.org >]Archivesspace_Users_Group at lyralists.lyrasis.org >[ http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >]http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > ________________________________________________________________ All email messages and attached content sent from and to this email account are public records unless qualified as an exemption under the [ http://www.sec.state.ma.us/pre/preidx.htm ]Massachusetts Public Records Law. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mang.sun at rice.edu Thu Apr 2 11:49:23 2015 From: mang.sun at rice.edu (Mang Sun) Date: Thu, 02 Apr 2015 10:49:23 -0500 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 Message-ID: <551D6503.8000500@rice.edu> When clicking the ead_pdf link turned on by the public_formats_resource_links plugin does not work with AS 1.2 throwing the error message as follows. -Mang Sun Rice U. EOFError in PublicFormatsController#generate |Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public | Request *Parameters*: {"repo_id"=>"2", "type"=>"resources", "id"=>"116", "format"=>"ead_pdf"} Show session dump _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" session_id: "c419289cb412f46af571004e4b0c0830" Show env dump GATEWAY_INTERFACE: "CGI/1.2" HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" HTTP_ACCEPT_ENCODING: "gzip, deflate" HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" REMOTE_ADDR: "10.xx.xx.xx" SERVER_NAME: "10.xx.22.xx" SERVER_PROTOCOL: "HTTP/1.1" Response *Headers*: None ----------------- The Full trace is pasted as below. |org/jruby/RubyIO.java:2858:in `read_nonblock' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request' org/jruby/RubyKernel.java:1270:in `catch' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request' /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle' /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate' actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action' actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action' actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action' actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action' activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action' actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action' actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action' activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument' activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument' activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action' actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action' actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process' actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process' actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch' actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch' actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action' org/jruby/RubyProc.java:271:in `call' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call' journey (1.0.4) lib/journey/router.rb:68:in `call' org/jruby/RubyArray.java:1613:in `each' journey (1.0.4) lib/journey/router.rb:56:in `call' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call' rack (1.4.5) lib/rack/etag.rb:23:in `call' rack (1.4.5) lib/rack/conditionalget.rb:25:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call' rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context' rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call' activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app' railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged' railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call' rack (1.4.5) lib/rack/methodoverride.rb:21:in `call' rack (1.4.5) lib/rack/runtime.rb:17:in `call' activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call' rack (1.4.5) lib/rack/lock.rb:15:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call' railties (3.2.19) lib/rails/engine.rb:484:in `call' railties (3.2.19) lib/rails/application.rb:231:in `call' rack (1.4.5) lib/rack/content_length.rb:14:in `call' railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call' puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request' puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request' puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client' puma-2.8.2 (java) lib/puma/server.rb:254:in `run' org/jruby/RubyProc.java:271:in `call' puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread'| -------------- next part -------------- An HTML attachment was scrubbed... URL: From danelle.moon at sjsu.edu Thu Apr 2 11:52:45 2015 From: danelle.moon at sjsu.edu (Danelle Moon) Date: Thu, 2 Apr 2015 08:52:45 -0700 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: <1427958850322.21749@lyrasis.org> References: <1427746077682.56800@lyrasis.org> <1427958850322.21749@lyrasis.org> Message-ID: In your email announcing the new release the links you provide refer to the previous releases so we are looking for 1.2 instructions. Danelle Sent from my iPhone > On Apr 2, 2015, at 12:14 AM, Chris Fitzpatrick wrote: > > Hi Danelle, > > > Which documentation are you referring to? The technical documentation is on http://archivesspace.github.io/archivesspace/doc/ and the User documentation is at https://docs.archivesspace.org/_help_proxy/login . > > > B,chris. > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Danelle Moon > Sent: Wednesday, April 1, 2015 10:22 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released > > Chris > > Do you have updated documentation for v1.2.0? Or are we to following the documentation instructions for the two previous releases? Please send me the link to the updated documentation needed to proceed with this version > > Thanks > Danelle > > Danelle Moon > Full Librarian > Director SJSU Special Collections > One Washington Square > San Jose, CA 95192-0028 > 408/808-2061 office > 408/808-2063 fax > Danelle.Moon at sjsu.edu > >> On Mon, Mar 30, 2015 at 1:07 PM, Chris Fitzpatrick wrote: >> The ArchivesSpace team is happy to release version v1.2.0. >> >> Please see the technical documentation for information on how to upgrade your ArchivesSpace installs. >> >> Please see the release page for a listing of all the new features and bug fixes included in this release. >> >> Of particular note: This release includes an upgrade to Bootstrap 3 for the staff interface. This version has significant changes to HTML, CSS, and Javascript components in the staff UI, so any plugins or custom templates will have to be modified to work with Bootstrap 3. >> >> Also included in this release is a Find-And-Replace background job, which allows users to bulk edit records. As this is a currently a beta-feature, it is recommended that users backup their database frequently if using this feature. >> >> Thanks to all the volunteers on the ArchivesSpace User Advisory and Technical Advisory Councils, who are vital to keeping ArchivesSpace development on track. >> >> Please let us know if you have any questions, comments, or concerns. >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Thu Apr 2 11:54:58 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 2 Apr 2015 15:54:58 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: References: <1427746077682.56800@lyrasis.org> <1427958850322.21749@lyrasis.org>, Message-ID: <1427990098459.95963@lyrasis.org> Hi, Which links? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Danelle Moon Sent: Thursday, April 2, 2015 5:52 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In your email announcing the new release the links you provide refer to the previous releases so we are looking for 1.2 instructions. Danelle Sent from my iPhone On Apr 2, 2015, at 12:14 AM, Chris Fitzpatrick > wrote: Hi Danelle, Which documentation are you referring to? The technical documentation is on http://archivesspace.github.io/archivesspace/doc/ and the User documentation is at https://docs.archivesspace.org/_help_proxy/login . B,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Danelle Moon > Sent: Wednesday, April 1, 2015 10:22 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released Chris Do you have updated documentation for v1.2.0? Or are we to following the documentation instructions for the two previous releases? Please send me the link to the updated documentation needed to proceed with this version Thanks Danelle Danelle Moon Full Librarian Director SJSU Special Collections One Washington Square San Jose, CA 95192-0028 408/808-2061 office 408/808-2063 fax Danelle.Moon at sjsu.edu On Mon, Mar 30, 2015 at 1:07 PM, Chris Fitzpatrick > wrote: The ArchivesSpace team is happy to release version v1.2.0. Please see the technical documentation for information on how to upgrade your ArchivesSpace installs. Please see the release page for a listing of all the new features and bug fixes included in this release. Of particular note: This release includes an upgrade to Bootstrap 3 for the staff interface. This version has significant changes to HTML, CSS, and Javascript components in the staff UI, so any plugins or custom templates will have to be modified to work with Bootstrap 3. Also included in this release is a Find-And-Replace background job, which allows users to bulk edit records. As this is a currently a beta-feature, it is recommended that users backup their database frequently if using this feature. Thanks to all the volunteers on the ArchivesSpace User Advisory and Technical Advisory Councils, who are vital to keeping ArchivesSpace development on track. Please let us know if you have any questions, comments, or concerns. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ 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 mlevy at ushmm.org Thu Apr 2 12:02:56 2015 From: mlevy at ushmm.org (Levy, Michael) Date: Thu, 2 Apr 2015 12:02:56 -0400 Subject: [Archivesspace_Users_Group] Database migration from 1.0.9 to 1.2.0 produces NoMethodError: undefined method `to_sequel_blob' for # Message-ID: Starting with a small test instance with no modifications, under RHEL, using derby, from a working v1.0.9 instance (which had been stopped), and then attempting to upgrade to 1.2.0. I just copied the [www at saturn archivesspace-v1.2.0]$ scripts/setup-database.sh Loading ArchivesSpace configuration file from path: /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb Loading ArchivesSpace configuration file from path: /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb Running migrations against jdbc:derby:/data/sites/apps/public/archivesspace-v1.2.0/data/archivesspace_demo_db;create=true;aspacedemo=true Adding separate permissions for updating major record types ... accession records ... resource records ... digital object records ... running import jobs ... managing vocabulary records Updating groups to include the new permssions Deleting update_archival_record permission Adding 'Date Not Yet Determined' to resource 2/4 Adding 'Date Not Yet Determined' to resource 2/23 Adding 'Date Not Yet Determined' to resource 2/24 ............ Adding 'Date Not Yet Determined' to resource 2/52 Adding 'Date Not Yet Determined' to resource 2/53 *** ADDING SOME ENUMS *** Genre Form to note_index_item_type enum list Triggering reindex of resource Triggering reindex of archival_object Triggering reindex of digital_object Making location_temporary list editble {:id=>1, :import_type=>"marcxml_lcnaf_subjects_and_agents", :repo_id=>2, :lock_version=>5, :json_schema_version=>1, :filenames=>"[\"lcnaf_import_d2adf1d5-64f5-4577-b55a-2e00b3bac1d5\"]", :time_submitted=>2014-03-26 17:51:23 UTC, :time_started=>2014-03-26 17:51:27 UTC, :time_finished=>2014-03-26 17:51:42 UTC, :owner_id=>1, :status=>"completed", :created_by=>"admin", :last_modified_by=>"admin", :create_time=>2014-03-26 17:51:23 UTC, :system_mtime=>2014-03-26 17:51:42 UTC, :user_mtime=>2014-03-26 17:51:23 UTC} 1297 NoMethodError: undefined method `to_sequel_blob' for # blobify at /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/utils.rb:33 (root) at /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:44 each at org/jruby/RubyArray.java:1613 (root) at /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:37 instance_eval at org/jruby/RubyBasicObject.java:1533 apply at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:100 run at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:528 _transaction at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134 transaction at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108 hold at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98 hold at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87 synchronize at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255 transaction at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97 checked_transaction at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:464 run at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:527 each at org/jruby/RubyArray.java:1613 run at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:524 run at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:391 setup_database at file:/data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/db_migrator.rb:184 (root) at ../scripts/rb/migrate_db.rb:43 connect at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:69 connect at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/core.rb:95 (root) at ../scripts/rb/migrate_db.rb:28 [www at saturn archivesspace-v1.2.0]$ -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianjhoffman at gmail.com Thu Apr 2 12:07:07 2015 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Thu, 2 Apr 2015 12:07:07 -0400 Subject: [Archivesspace_Users_Group] Database migration from 1.0.9 to 1.2.0 produces NoMethodError: undefined method `to_sequel_blob' for # In-Reply-To: References: Message-ID: <4080B059-CCA9-4D05-BEDD-D064C23288EE@gmail.com> Thank you! https://archivesspace.atlassian.net/browse/AR-1188 On Apr 2, 2015, at 12:02 PM, Levy, Michael wrote: > Starting with a small test instance with no modifications, under RHEL, using derby, from a working v1.0.9 instance (which had been stopped), and then attempting to upgrade to 1.2.0. I just copied the > > [www at saturn archivesspace-v1.2.0]$ scripts/setup-database.sh > Loading ArchivesSpace configuration file from path: /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb > Loading ArchivesSpace configuration file from path: /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb > Running migrations against jdbc:derby:/data/sites/apps/public/archivesspace-v1.2.0/data/archivesspace_demo_db;create=true;aspacedemo=true > Adding separate permissions for updating major record types > ... accession records > ... resource records > ... digital object records > ... running import jobs > ... managing vocabulary records > Updating groups to include the new permssions > Deleting update_archival_record permission > Adding 'Date Not Yet Determined' to resource 2/4 > Adding 'Date Not Yet Determined' to resource 2/23 > Adding 'Date Not Yet Determined' to resource 2/24 > > ............ > > Adding 'Date Not Yet Determined' to resource 2/52 > Adding 'Date Not Yet Determined' to resource 2/53 > *** ADDING SOME ENUMS > *** Genre Form to note_index_item_type enum list > Triggering reindex of resource > Triggering reindex of archival_object > Triggering reindex of digital_object > Making location_temporary list editble > {:id=>1, :import_type=>"marcxml_lcnaf_subjects_and_agents", :repo_id=>2, :lock_version=>5, :json_schema_version=>1, :filenames=>"[\"lcnaf_import_d2adf1d5-64f5-4577-b55a-2e00b3bac1d5\"]", :time_submitted=>2014-03-26 17:51:23 UTC, :time_started=>2014-03-26 17:51:27 UTC, :time_finished=>2014-03-26 17:51:42 UTC, :owner_id=>1, :status=>"completed", :created_by=>"admin", :last_modified_by=>"admin", :create_time=>2014-03-26 17:51:23 UTC, :system_mtime=>2014-03-26 17:51:42 UTC, :user_mtime=>2014-03-26 17:51:23 UTC} > 1297 > NoMethodError: undefined method `to_sequel_blob' for # > blobify at /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/utils.rb:33 > (root) at /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:44 > each at org/jruby/RubyArray.java:1613 > (root) at /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:37 > instance_eval at org/jruby/RubyBasicObject.java:1533 > apply at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:100 > run at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:528 > _transaction at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134 > transaction at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108 > hold at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98 > hold at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87 > synchronize at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255 > transaction at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97 > checked_transaction at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:464 > run at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:527 > each at org/jruby/RubyArray.java:1613 > run at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:524 > run at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:391 > setup_database at file:/data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/db_migrator.rb:184 > (root) at ../scripts/rb/migrate_db.rb:43 > connect at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:69 > connect at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/core.rb:95 > (root) at ../scripts/rb/migrate_db.rb:28 > [www at saturn archivesspace-v1.2.0]$ > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From luftsche at usc.edu Thu Apr 2 12:39:20 2015 From: luftsche at usc.edu (Susan Luftschein) Date: Thu, 2 Apr 2015 16:39:20 +0000 Subject: [Archivesspace_Users_Group] Problems with MARC export In-Reply-To: References: Message-ID: Thanks Brad! On a related note, there are other mapping issues with MARCXML export that I reported via Mark Cooper, but I wanted to check in as to their status. One of the ones I notice is still not fixed is the Preferred Citation note. AS exports it as a 534 and it should be 524 (see http://www.oclc.org/bibformats/en/5xx/524.html). Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brad Westbrook Sent: Thursday, April 02, 2015 7:22 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Problems with MARC export Hi, Sue, Thanks for catching and reporting this problem. It is, indeed, something new in v.1.2.0. I have filed a bug report (https://archivesspace.atlassian.net/browse/AR-1187?jql=) Brad From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Wednesday, April 01, 2015 7:20 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Problems with MARC export Hi programmers, I just exported a MARCXML record that included a Processing Information note. In the MARC record it mapped to a 520 $2 note, and included the header, but not the contents of the note (the note is set to publish). Can you guys look into fixing this? Thanks, Sue Luftschein Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From danelle.moon at sjsu.edu Thu Apr 2 12:53:23 2015 From: danelle.moon at sjsu.edu (Danelle Moon) Date: Thu, 2 Apr 2015 09:53:23 -0700 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: <1427990098459.95963@lyrasis.org> References: <1427746077682.56800@lyrasis.org> <1427958850322.21749@lyrasis.org> <1427990098459.95963@lyrasis.org> Message-ID: here is the body of your message with the links ...if you click on documentation it leads you to the info for 1 and 1.1 release not 1.2.0. All I need to know what should follow to install? The ArchivesSpace team is happy to release version v1.2.0 . Please see the technical documentation for information on how to upgrade your ArchivesSpace installs. Please see the release page for a listing of all the new features and bug fixes included in this release. Of particular note: This release includes an upgrade to Bootstrap 3 for the staff interface. This version has significant changes to HTML, CSS, and Javascript components in the staff UI, so any plugins or custom templates will have to be modified to work with Bootstrap 3. Also included in this release is a Find-And-Replace background job, which allows users to bulk edit records. As this is a currently a beta-feature, it is recommended that users backup their database frequently if using this feature. Thanks to all the volunteers on the ArchivesSpace User Advisory and Technical Advisory Councils, who are vital to keeping ArchivesSpace development on track. Please let us know if you have any questions, comments, or concerns. Danelle Moon Full Librarian Director SJSU Special Collections One Washington Square San Jose, CA 95192-0028 408/808-2061 office 408/808-2063 fax Danelle.Moon at sjsu.edu On Thu, Apr 2, 2015 at 8:54 AM, Chris Fitzpatrick < Chris.Fitzpatrick at lyrasis.org> wrote: > Hi, > > > Which links? > > > b,chris. > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Danelle Moon > *Sent:* Thursday, April 2, 2015 5:52 PM > > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released > > In your email announcing the new release the links you provide refer to > the previous releases so we are looking for 1.2 instructions. > > Danelle > > Sent from my iPhone > > On Apr 2, 2015, at 12:14 AM, Chris Fitzpatrick < > Chris.Fitzpatrick at lyrasis.org> wrote: > > Hi Danelle, > > > Which documentation are you referring to? The technical documentation is > on http://archivesspace.github.io/archivesspace/doc/ and the User > documentation is at https://docs.archivesspace.org/_help_proxy/login . > > > B,chris. > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Danelle Moon > *Sent:* Wednesday, April 1, 2015 10:22 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released > > Chris > > Do you have updated documentation for v1.2.0? Or are we to following > the documentation instructions for the two previous releases? Please send > me the link to the updated documentation needed to proceed with this version > > Thanks > Danelle > > Danelle Moon > Full Librarian > Director SJSU Special Collections > One Washington Square > San Jose, CA 95192-0028 > 408/808-2061 office > 408/808-2063 fax > Danelle.Moon at sjsu.edu > > On Mon, Mar 30, 2015 at 1:07 PM, Chris Fitzpatrick < > Chris.Fitzpatrick at lyrasis.org> wrote: > >> The ArchivesSpace team is happy to release version v1.2.0 >> . >> >> Please see the technical documentation >> >> for information on how to upgrade your ArchivesSpace installs. >> >> Please see the release page >> for >> a listing of all the new features and bug fixes included in this release. >> >> Of particular note: This release includes an upgrade to Bootstrap 3 >> for the staff interface. This version has >> significant changes to HTML, CSS, and Javascript components in the >> staff UI, so any plugins or custom templates will have to be modified >> to work with Bootstrap 3. >> >> Also included in this release is a Find-And-Replace background job, which >> allows users to bulk edit records. As this is a currently a beta-feature, >> it is recommended that users backup their database frequently if using this >> feature. >> >> Thanks to all the volunteers on the ArchivesSpace User Advisory and >> Technical Advisory Councils, who are vital to keeping ArchivesSpace >> development on track. >> >> Please let us know if you have any questions, comments, or concerns. >> >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianjhoffman at gmail.com Thu Apr 2 12:58:19 2015 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Thu, 2 Apr 2015 12:58:19 -0400 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: References: <1427746077682.56800@lyrasis.org> <1427958850322.21749@lyrasis.org> <1427990098459.95963@lyrasis.org> Message-ID: <2D2C41A0-A716-4091-9357-1CC7A551790B@gmail.com> Hi Danelle, That page documents the standard upgrade procedure from any version to any version. Some versions require special steps, and those have links at the top. If you are migrating ?through? one of those versions, for example from 1.0.9 to 1.2, you should still read the special instructions for the versions in between. Brian On Apr 2, 2015, at 12:53 PM, Danelle Moon wrote: > here is the body of your message with the links ...if you click on documentation it leads you to the info for 1 and 1.1 release not 1.2.0. All I need to know what should follow to install? > > The ArchivesSpace team is happy to release version v1.2.0. > > Please see the technical documentation for information on how to upgrade your ArchivesSpace installs. > > Please see the release page for a listing of all the new features and bug fixes included in this release. > > Of particular note: This release includes an upgrade to Bootstrap 3 for the staff interface. This version has significant changes to HTML, CSS, and Javascript components in the staff UI, so any plugins or custom templates will have to be modified to work with Bootstrap 3. > > Also included in this release is a Find-And-Replace background job, which allows users to bulk edit records. As this is a currently a beta-feature, it is recommended that users backup their database frequently if using this feature. > > Thanks to all the volunteers on the ArchivesSpace User Advisory and Technical Advisory Councils, who are vital to keeping ArchivesSpace development on track. > > Please let us know if you have any questions, comments, or concerns. > > > Danelle Moon > Full Librarian > Director SJSU Special Collections > One Washington Square > San Jose, CA 95192-0028 > 408/808-2061 office > 408/808-2063 fax > Danelle.Moon at sjsu.edu > > On Thu, Apr 2, 2015 at 8:54 AM, Chris Fitzpatrick wrote: > Hi, > > > Which links? > > > b,chris. > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Danelle Moon > Sent: Thursday, April 2, 2015 5:52 PM > > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released > > In your email announcing the new release the links you provide refer to the previous releases so we are looking for 1.2 instructions. > > Danelle > > Sent from my iPhone > > On Apr 2, 2015, at 12:14 AM, Chris Fitzpatrick wrote: > >> Hi Danelle, >> >> >> Which documentation are you referring to? The technical documentation is on http://archivesspace.github.io/archivesspace/doc/ and the User documentation is at https://docs.archivesspace.org/_help_proxy/login . >> >> >> B,chris. >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Danelle Moon >> Sent: Wednesday, April 1, 2015 10:22 PM >> To: Archivesspace Users Group >> Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released >> >> Chris >> >> Do you have updated documentation for v1.2.0? Or are we to following the documentation instructions for the two previous releases? Please send me the link to the updated documentation needed to proceed with this version >> >> Thanks >> Danelle >> >> Danelle Moon >> Full Librarian >> Director SJSU Special Collections >> One Washington Square >> San Jose, CA 95192-0028 >> 408/808-2061 office >> 408/808-2063 fax >> Danelle.Moon at sjsu.edu >> >> On Mon, Mar 30, 2015 at 1:07 PM, Chris Fitzpatrick wrote: >> The ArchivesSpace team is happy to release version v1.2.0. >> >> Please see the technical documentation for information on how to upgrade your ArchivesSpace installs. >> >> Please see the release page for a listing of all the new features and bug fixes included in this release. >> >> Of particular note: This release includes an upgrade to Bootstrap 3 for the staff interface. This version has significant changes to HTML, CSS, and Javascript components in the staff UI, so any plugins or custom templates will have to be modified to work with Bootstrap 3. >> >> Also included in this release is a Find-And-Replace background job, which allows users to bulk edit records. As this is a currently a beta-feature, it is recommended that users backup their database frequently if using this feature. >> >> Thanks to all the volunteers on the ArchivesSpace User Advisory and Technical Advisory Councils, who are vital to keeping ArchivesSpace development on track. >> >> Please let us know if you have any questions, comments, or concerns. >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From danelle.moon at sjsu.edu Thu Apr 2 13:07:24 2015 From: danelle.moon at sjsu.edu (Danelle Moon) Date: Thu, 2 Apr 2015 10:07:24 -0700 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: <2D2C41A0-A716-4091-9357-1CC7A551790B@gmail.com> References: <1427746077682.56800@lyrasis.org> <1427958850322.21749@lyrasis.org> <1427990098459.95963@lyrasis.org> <2D2C41A0-A716-4091-9357-1CC7A551790B@gmail.com> Message-ID: Thanks Brian. My IT staff is doing the work but they didn't want to upgrade wihout documentation. I will pass this on..... Danelle Moon Full Librarian Director SJSU Special Collections One Washington Square San Jose, CA 95192-0028 408/808-2061 office 408/808-2063 fax Danelle.Moon at sjsu.edu On Thu, Apr 2, 2015 at 9:58 AM, Brian Hoffman wrote: > Hi Danelle, > > That page documents the standard upgrade procedure from any version to any > version. Some versions require special steps, and those have links at the > top. If you are migrating ?through? one of those versions, for example from > 1.0.9 to 1.2, you should still read the special instructions for the > versions in between. > > Brian > > > > > On Apr 2, 2015, at 12:53 PM, Danelle Moon wrote: > > here is the body of your message with the links ...if you click on > documentation it leads you to the info for 1 and 1.1 release not 1.2.0. All > I need to know what should follow to install? > > The ArchivesSpace team is happy to release version v1.2.0 > . > > Please see the technical documentation > for > information on how to upgrade your ArchivesSpace installs. > > Please see the release page > for > a listing of all the new features and bug fixes included in this release. > > Of particular note: This release includes an upgrade to Bootstrap 3 > for the staff interface. This version has > significant changes to HTML, CSS, and Javascript components in the > staff UI, so any plugins or custom templates will have to be modified > to work with Bootstrap 3. > > Also included in this release is a Find-And-Replace background job, which > allows users to bulk edit records. As this is a currently a beta-feature, > it is recommended that users backup their database frequently if using this > feature. > > Thanks to all the volunteers on the ArchivesSpace User Advisory and > Technical Advisory Councils, who are vital to keeping ArchivesSpace > development on track. > > Please let us know if you have any questions, comments, or concerns. > > > Danelle Moon > Full Librarian > Director SJSU Special Collections > One Washington Square > San Jose, CA 95192-0028 > 408/808-2061 office > 408/808-2063 fax > Danelle.Moon at sjsu.edu > > On Thu, Apr 2, 2015 at 8:54 AM, Chris Fitzpatrick < > Chris.Fitzpatrick at lyrasis.org> wrote: > >> Hi, >> >> >> Which links? >> >> >> b,chris. >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> ------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >> Danelle Moon >> *Sent:* Thursday, April 2, 2015 5:52 PM >> >> *To:* Archivesspace Users Group >> *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released >> >> In your email announcing the new release the links you provide refer to >> the previous releases so we are looking for 1.2 instructions. >> >> Danelle >> >> Sent from my iPhone >> >> On Apr 2, 2015, at 12:14 AM, Chris Fitzpatrick < >> Chris.Fitzpatrick at lyrasis.org> wrote: >> >> Hi Danelle, >> >> >> Which documentation are you referring to? The technical documentation is >> on http://archivesspace.github.io/archivesspace/doc/ and the User >> documentation is at https://docs.archivesspace.org/_help_proxy/login . >> >> >> B,chris. >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> ------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >> Danelle Moon >> *Sent:* Wednesday, April 1, 2015 10:22 PM >> *To:* Archivesspace Users Group >> *Subject:* Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released >> >> Chris >> >> Do you have updated documentation for v1.2.0? Or are we to following >> the documentation instructions for the two previous releases? Please send >> me the link to the updated documentation needed to proceed with this version >> >> Thanks >> Danelle >> >> Danelle Moon >> Full Librarian >> Director SJSU Special Collections >> One Washington Square >> San Jose, CA 95192-0028 >> 408/808-2061 office >> 408/808-2063 fax >> Danelle.Moon at sjsu.edu >> >> On Mon, Mar 30, 2015 at 1:07 PM, Chris Fitzpatrick < >> Chris.Fitzpatrick at lyrasis.org> wrote: >> >>> The ArchivesSpace team is happy to release version v1.2.0 >>> . >>> >>> Please see the technical documentation >>> >>> for information on how to upgrade your ArchivesSpace installs. >>> >>> Please see the release page >>> >>> for a listing of all the new features and bug fixes included in this >>> release. >>> >>> Of particular note: This release includes an upgrade to Bootstrap 3 >>> for the staff interface. This version has >>> significant changes to HTML, CSS, and Javascript components in the >>> staff UI, so any plugins or custom templates will have to be modified >>> to work with Bootstrap 3. >>> >>> Also included in this release is a Find-And-Replace background job, >>> which allows users to bulk edit records. As this is a currently a >>> beta-feature, it is recommended that users backup their database frequently >>> if using this feature. >>> >>> Thanks to all the volunteers on the ArchivesSpace User Advisory and >>> Technical Advisory Councils, who are vital to keeping ArchivesSpace >>> development on track. >>> >>> Please let us know if you have any questions, comments, or concerns. >>> >>> >>> >>> Chris Fitzpatrick | Developer, ArchivesSpace >>> Skype: chrisfitzpat | Phone: 918.236.6048 >>> http://archivesspace.org/ >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kate at woodyguthriecenter.org Wed Apr 1 11:10:40 2015 From: Kate at woodyguthriecenter.org (Kate Blalack) Date: Wed, 1 Apr 2015 15:10:40 +0000 Subject: [Archivesspace_Users_Group] [Archivesspace_member_reps] Appointment of ArchivesSpace Community Outreach and Support Manager In-Reply-To: References: Message-ID: Welcome Christine! I look forward to meeting you :) Kate Blalack, MLIS, CA Archivist Woody Guthrie Center 918-574-2710 (office) 405-762-2158 (cell) From: Brad Westbrook > Reply-To: Archivesspace Member Reps > Date: Wednesday, April 1, 2015 7:49 AM To: "archivesspace_users_group at lyralists.lyrasis.org" >, "Archivesspace_member_reps at lyralists.lyrasis.org" >, "archivesspace_bot_members at lyralists.lyrasis.org" >, "archivesspace_tac_uac at lyralists.lyrasis.org" > Subject: [Archivesspace_member_reps] Appointment of ArchivesSpace Community Outreach and Support Manager Good morning ArchivesSpace members. I am very pleased to report that, as of today, Christine Di Bella will be the Community Outreach and Support Manager for the ArchivesSpace program. Christine will have primary responsibility for community outreach and engagement, including managing the ArchivesSpace wikis and website; for event organization, such as the scheduled ArchivesSpace members meeting on August 22 in Cleveland, OH; and for leading the updating of user documentation and the production of video tutorials. Also, Christine will become one of the ArchivesSpace trainers and will be attending various archives conferences as an ArchivesSpace representative. These are all key areas in the ArchivesSpace program, and they will progress substantially under Christine's leadership. Please join me in welcoming Christine to her new role. Cheers, 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] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7640 bytes Desc: image003.png URL: From robin_mcelheny at harvard.edu Thu Apr 2 14:01:38 2015 From: robin_mcelheny at harvard.edu (McElheny, Robin G.) Date: Thu, 2 Apr 2015 18:01:38 +0000 Subject: [Archivesspace_Users_Group] Question re new features Message-ID: Here at Harvard we were glad to see the list of new features in the latest release of ASpace, especially the following: * NEW FEATURE #AR-885 : Accession receipt * NEW FEATURE #AR-883 : Accession(s) acquired Now that we have installed the new version, we're eager to try these out - but where do we find them? We didn't see them under the list of reports, nor did we find them in Background Jobs. Are we misunderstanding what these features are? Can you help us out? Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Thu Apr 2 14:38:36 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Thu, 2 Apr 2015 18:38:36 +0000 Subject: [Archivesspace_Users_Group] Question re new features In-Reply-To: References: Message-ID: Hi, Robin, Apparently there was a mix up with tagging issues for the release. All the reports listed in the v1.2 release passed a first test, but still must pass a subsequent test. If you are interested, you can test the reports listed for v.1.2, and others under development, using the aReports testing tool at https://github.com/archivesspace/aReports. Brad W. From: McElheny, Robin G. [mailto:robin_mcelheny at harvard.edu] Sent: Thursday, April 02, 2015 2:02 PM To: archivesspace_users_group at lyralists.lyrasis.org; Brad Westbrook Cc: Carll, Johanna; Della Monica, Ilaria; Engelhart, Anne; Gustainis, Emily; Moloy, Edwin C.; Pyzynski, Susan C.; Vandermillen, Michael; Wendler, Robin King; Wise, Rachel A; Zalduendo, Ines Subject: Question re new features Here at Harvard we were glad to see the list of new features in the latest release of ASpace, especially the following: * NEW FEATURE #AR-885 : Accession receipt * NEW FEATURE #AR-883 : Accession(s) acquired Now that we have installed the new version, we're eager to try these out - but where do we find them? We didn't see them under the list of reports, nor did we find them in Background Jobs. Are we misunderstanding what these features are? Can you help us out? Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jkjaer at skidmore.edu Thu Apr 2 15:08:45 2015 From: jkjaer at skidmore.edu (Jane Kjaer) Date: Thu, 2 Apr 2015 19:08:45 +0000 Subject: [Archivesspace_Users_Group] Question re new features In-Reply-To: References: Message-ID: And the empirical "we" Jane (YANA) Jane Kjaer Reserves Lucy Scribner Library Skidmore College 518-580-5507 The single biggest problem with communication is the illusion that it has taken place." George Bernard Shaw From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McElheny, Robin G. Sent: Thursday, April 02, 2015 2:02 PM To: archivesspace_users_group at lyralists.lyrasis.org; Brad Westbrook (brad.westbrook at lyrasis.org) Cc: Zalduendo, Ines; Vandermillen, Michael; Wendler, Robin King; Della Monica, Ilaria Subject: [Archivesspace_Users_Group] Question re new features Here at Harvard we were glad to see the list of new features in the latest release of ASpace, especially the following: * NEW FEATURE #AR-885 : Accession receipt * NEW FEATURE #AR-883 : Accession(s) acquired Now that we have installed the new version, we're eager to try these out - but where do we find them? We didn't see them under the list of reports, nor did we find them in Background Jobs. Are we misunderstanding what these features are? Can you help us out? Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mlevy at ushmm.org Thu Apr 2 17:17:40 2015 From: mlevy at ushmm.org (Levy, Michael) Date: Thu, 2 Apr 2015 17:17:40 -0400 Subject: [Archivesspace_Users_Group] Database migration from 1.0.9 to 1.2.0 produces NoMethodError: undefined method `to_sequel_blob' for # In-Reply-To: <4080B059-CCA9-4D05-BEDD-D064C23288EE@gmail.com> References: <4080B059-CCA9-4D05-BEDD-D064C23288EE@gmail.com> Message-ID: Any suggestions on what I ought to try to work around this issue? Should I try running the upgrade incrementally from the 1.0.9 instance I have running to some other interim version(s) and then on to 1.2.0? In my initial posting I did not finish a sentence. I merely meant to say I copied the data folder and configuration, and that I had not added any plugins. On Thu, Apr 2, 2015 at 12:07 PM, Brian Hoffman wrote: > Thank you! > > https://archivesspace.atlassian.net/browse/AR-1188 > > > On Apr 2, 2015, at 12:02 PM, Levy, Michael wrote: > > > Starting with a small test instance with no modifications, under RHEL, > using derby, from a working v1.0.9 instance (which had been stopped), and > then attempting to upgrade to 1.2.0. I just copied the > > > > [www at saturn archivesspace-v1.2.0]$ scripts/setup-database.sh > > Loading ArchivesSpace configuration file from path: > /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb > > Loading ArchivesSpace configuration file from path: > /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb > > Running migrations against > jdbc:derby:/data/sites/apps/public/archivesspace-v1.2.0/data/archivesspace_demo_db;create=true;aspacedemo=true > > Adding separate permissions for updating major record types > > ... accession records > > ... resource records > > ... digital object records > > ... running import jobs > > ... managing vocabulary records > > Updating groups to include the new permssions > > Deleting update_archival_record permission > > Adding 'Date Not Yet Determined' to resource 2/4 > > Adding 'Date Not Yet Determined' to resource 2/23 > > Adding 'Date Not Yet Determined' to resource 2/24 > > > > ............ > > > > Adding 'Date Not Yet Determined' to resource 2/52 > > Adding 'Date Not Yet Determined' to resource 2/53 > > *** ADDING SOME ENUMS > > *** Genre Form to note_index_item_type enum list > > Triggering reindex of resource > > Triggering reindex of archival_object > > Triggering reindex of digital_object > > Making location_temporary list editble > > {:id=>1, :import_type=>"marcxml_lcnaf_subjects_and_agents", :repo_id=>2, > :lock_version=>5, :json_schema_version=>1, > :filenames=>"[\"lcnaf_import_d2adf1d5-64f5-4577-b55a-2e00b3bac1d5\"]", > :time_submitted=>2014-03-26 17:51:23 UTC, :time_started=>2014-03-26 > 17:51:27 UTC, :time_finished=>2014-03-26 17:51:42 UTC, :owner_id=>1, > :status=>"completed", :created_by=>"admin", :last_modified_by=>"admin", > :create_time=>2014-03-26 17:51:23 UTC, :system_mtime=>2014-03-26 17:51:42 > UTC, :user_mtime=>2014-03-26 17:51:23 UTC} > > 1297 > > NoMethodError: undefined method `to_sequel_blob' for # > > blobify at > /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/utils.rb:33 > > (root) at > /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:44 > > each at org/jruby/RubyArray.java:1613 > > (root) at > /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:37 > > instance_eval at org/jruby/RubyBasicObject.java:1533 > > apply at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:100 > > run at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:528 > > _transaction at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134 > > transaction at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108 > > hold at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98 > > hold at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87 > > synchronize at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255 > > transaction at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97 > > checked_transaction at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:464 > > run at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:527 > > each at org/jruby/RubyArray.java:1613 > > run at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:524 > > run at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:391 > > setup_database at > file:/data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/db_migrator.rb:184 > > (root) at ../scripts/rb/migrate_db.rb:43 > > connect at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:69 > > connect at > /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/core.rb:95 > > (root) at ../scripts/rb/migrate_db.rb:28 > > [www at saturn archivesspace-v1.2.0]$ > > > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianjhoffman at gmail.com Thu Apr 2 17:20:03 2015 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Thu, 2 Apr 2015 17:20:03 -0400 Subject: [Archivesspace_Users_Group] Database migration from 1.0.9 to 1.2.0 produces NoMethodError: undefined method `to_sequel_blob' for # In-Reply-To: References: <4080B059-CCA9-4D05-BEDD-D064C23288EE@gmail.com> Message-ID: <28D3226C-2186-48CA-AE97-14D9D3581082@gmail.com> Hi Michael, I think the best thing would be to wait for us to fix it. We?ll post a minor release next week. Can you wait till then? I?d hate for your data to get corrupted. Brian On Apr 2, 2015, at 5:17 PM, Levy, Michael wrote: > Any suggestions on what I ought to try to work around this issue? Should I try running the upgrade incrementally from the 1.0.9 instance I have running to some other interim version(s) and then on to 1.2.0? > > In my initial posting I did not finish a sentence. I merely meant to say I copied the data folder and configuration, and that I had not added any plugins. > > On Thu, Apr 2, 2015 at 12:07 PM, Brian Hoffman wrote: > Thank you! > > https://archivesspace.atlassian.net/browse/AR-1188 > > > On Apr 2, 2015, at 12:02 PM, Levy, Michael wrote: > > > Starting with a small test instance with no modifications, under RHEL, using derby, from a working v1.0.9 instance (which had been stopped), and then attempting to upgrade to 1.2.0. I just copied the > > > > [www at saturn archivesspace-v1.2.0]$ scripts/setup-database.sh > > Loading ArchivesSpace configuration file from path: /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb > > Loading ArchivesSpace configuration file from path: /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb > > Running migrations against jdbc:derby:/data/sites/apps/public/archivesspace-v1.2.0/data/archivesspace_demo_db;create=true;aspacedemo=true > > Adding separate permissions for updating major record types > > ... accession records > > ... resource records > > ... digital object records > > ... running import jobs > > ... managing vocabulary records > > Updating groups to include the new permssions > > Deleting update_archival_record permission > > Adding 'Date Not Yet Determined' to resource 2/4 > > Adding 'Date Not Yet Determined' to resource 2/23 > > Adding 'Date Not Yet Determined' to resource 2/24 > > > > ............ > > > > Adding 'Date Not Yet Determined' to resource 2/52 > > Adding 'Date Not Yet Determined' to resource 2/53 > > *** ADDING SOME ENUMS > > *** Genre Form to note_index_item_type enum list > > Triggering reindex of resource > > Triggering reindex of archival_object > > Triggering reindex of digital_object > > Making location_temporary list editble > > {:id=>1, :import_type=>"marcxml_lcnaf_subjects_and_agents", :repo_id=>2, :lock_version=>5, :json_schema_version=>1, :filenames=>"[\"lcnaf_import_d2adf1d5-64f5-4577-b55a-2e00b3bac1d5\"]", :time_submitted=>2014-03-26 17:51:23 UTC, :time_started=>2014-03-26 17:51:27 UTC, :time_finished=>2014-03-26 17:51:42 UTC, :owner_id=>1, :status=>"completed", :created_by=>"admin", :last_modified_by=>"admin", :create_time=>2014-03-26 17:51:23 UTC, :system_mtime=>2014-03-26 17:51:42 UTC, :user_mtime=>2014-03-26 17:51:23 UTC} > > 1297 > > NoMethodError: undefined method `to_sequel_blob' for # > > blobify at /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/utils.rb:33 > > (root) at /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:44 > > each at org/jruby/RubyArray.java:1613 > > (root) at /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:37 > > instance_eval at org/jruby/RubyBasicObject.java:1533 > > apply at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:100 > > run at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:528 > > _transaction at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134 > > transaction at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108 > > hold at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98 > > hold at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87 > > synchronize at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255 > > transaction at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97 > > checked_transaction at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:464 > > run at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:527 > > each at org/jruby/RubyArray.java:1613 > > run at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:524 > > run at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:391 > > setup_database at file:/data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/db_migrator.rb:184 > > (root) at ../scripts/rb/migrate_db.rb:43 > > connect at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:69 > > connect at /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/core.rb:95 > > (root) at ../scripts/rb/migrate_db.rb:28 > > [www at saturn archivesspace-v1.2.0]$ > > > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mlevy at ushmm.org Thu Apr 2 17:22:26 2015 From: mlevy at ushmm.org (Levy, Michael) Date: Thu, 2 Apr 2015 17:22:26 -0400 Subject: [Archivesspace_Users_Group] Database migration from 1.0.9 to 1.2.0 produces NoMethodError: undefined method `to_sequel_blob' for # In-Reply-To: <28D3226C-2186-48CA-AE97-14D9D3581082@gmail.com> References: <4080B059-CCA9-4D05-BEDD-D064C23288EE@gmail.com> <28D3226C-2186-48CA-AE97-14D9D3581082@gmail.com> Message-ID: We'll be happy to wait for a fix. Thanks Brian. On Thu, Apr 2, 2015 at 5:20 PM, Brian Hoffman wrote: > Hi Michael, > > I think the best thing would be to wait for us to fix it. We?ll post a > minor release next week. Can you wait till then? I?d hate for your data to > get corrupted. > > Brian > > > > On Apr 2, 2015, at 5:17 PM, Levy, Michael wrote: > > Any suggestions on what I ought to try to work around this issue? Should I > try running the upgrade incrementally from the 1.0.9 instance I have > running to some other interim version(s) and then on to 1.2.0? > > In my initial posting I did not finish a sentence. I merely meant to say I > copied the data folder and configuration, and that I had not added any > plugins. > > On Thu, Apr 2, 2015 at 12:07 PM, Brian Hoffman > wrote: > >> Thank you! >> >> https://archivesspace.atlassian.net/browse/AR-1188 >> >> >> On Apr 2, 2015, at 12:02 PM, Levy, Michael wrote: >> >> > Starting with a small test instance with no modifications, under RHEL, >> using derby, from a working v1.0.9 instance (which had been stopped), and >> then attempting to upgrade to 1.2.0. I just copied the >> > >> > [www at saturn archivesspace-v1.2.0]$ scripts/setup-database.sh >> > Loading ArchivesSpace configuration file from path: >> /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb >> > Loading ArchivesSpace configuration file from path: >> /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb >> > Running migrations against >> jdbc:derby:/data/sites/apps/public/archivesspace-v1.2.0/data/archivesspace_demo_db;create=true;aspacedemo=true >> > Adding separate permissions for updating major record types >> > ... accession records >> > ... resource records >> > ... digital object records >> > ... running import jobs >> > ... managing vocabulary records >> > Updating groups to include the new permssions >> > Deleting update_archival_record permission >> > Adding 'Date Not Yet Determined' to resource 2/4 >> > Adding 'Date Not Yet Determined' to resource 2/23 >> > Adding 'Date Not Yet Determined' to resource 2/24 >> > >> > ............ >> > >> > Adding 'Date Not Yet Determined' to resource 2/52 >> > Adding 'Date Not Yet Determined' to resource 2/53 >> > *** ADDING SOME ENUMS >> > *** Genre Form to note_index_item_type enum list >> > Triggering reindex of resource >> > Triggering reindex of archival_object >> > Triggering reindex of digital_object >> > Making location_temporary list editble >> > {:id=>1, :import_type=>"marcxml_lcnaf_subjects_and_agents", >> :repo_id=>2, :lock_version=>5, :json_schema_version=>1, >> :filenames=>"[\"lcnaf_import_d2adf1d5-64f5-4577-b55a-2e00b3bac1d5\"]", >> :time_submitted=>2014-03-26 17:51:23 UTC, :time_started=>2014-03-26 >> 17:51:27 UTC, :time_finished=>2014-03-26 17:51:42 UTC, :owner_id=>1, >> :status=>"completed", :created_by=>"admin", :last_modified_by=>"admin", >> :create_time=>2014-03-26 17:51:23 UTC, :system_mtime=>2014-03-26 17:51:42 >> UTC, :user_mtime=>2014-03-26 17:51:23 UTC} >> > 1297 >> > NoMethodError: undefined method `to_sequel_blob' for >> # >> > blobify at >> /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/utils.rb:33 >> > (root) at >> /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:44 >> > each at org/jruby/RubyArray.java:1613 >> > (root) at >> /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:37 >> > instance_eval at org/jruby/RubyBasicObject.java:1533 >> > apply at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:100 >> > run at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:528 >> > _transaction at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134 >> > transaction at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108 >> > hold at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98 >> > hold at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87 >> > synchronize at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255 >> > transaction at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97 >> > checked_transaction at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:464 >> > run at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:527 >> > each at org/jruby/RubyArray.java:1613 >> > run at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:524 >> > run at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:391 >> > setup_database at >> file:/data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/db_migrator.rb:184 >> > (root) at ../scripts/rb/migrate_db.rb:43 >> > connect at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:69 >> > connect at >> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/core.rb:95 >> > (root) at ../scripts/rb/migrate_db.rb:28 >> > [www at saturn archivesspace-v1.2.0]$ >> > >> > _______________________________________________ >> > Archivesspace_Users_Group mailing list >> > Archivesspace_Users_Group at lyralists.lyrasis.org >> > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Thu Apr 2 17:30:37 2015 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 2 Apr 2015 21:30:37 +0000 Subject: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 In-Reply-To: References: <1F1E72103798F04D96C355B296D7C61B47B82A@mb2-uts.du.edu>, <1F1E72103798F04D96C355B296D7C61B47B995@mb2-uts.du.edu>, Message-ID: <1F1E72103798F04D96C355B296D7C61B47BD7A@mb2-uts.du.edu> Attached are the two things I noticed while testing. Glitch #1 appears when I edit an Archival Object. The publish checkbox aligns correctly in the Resource form; Firebug made it look like the label classes in the Archival Object form were still based on the 1.1.* stylesheets. Glitch #2 appears when a form is loading; the text isn't centered in the box. Not a big deal, it just looks off to me. thanks! -k ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Brad Westbrook [brad.westbrook at lyrasis.org] Sent: Thursday, April 02, 2015 7:04 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 Hi, Kevin, Please send the list along. And am glad you are able to locate the problem you experienced yesterday. Brad From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair Sent: Thursday, April 02, 2015 8:50 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 Hi Brad, Thanks for your reply. Hearing you couldn't replicate it made me think it might be an issue with my local plugins; turning them off solved the problem. Guess I have some cleaning up to do in there... thanks again! I've noticed a few other, more minor layout issues with the new stylesheets, if you happen to want a list of those. -k ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Brad Westbrook [brad.westbrook at lyrasis.org] Sent: Thursday, April 02, 2015 5:31 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 Hi, Kevin, Thanks for reporting this problem. Unfortunately, I have not been able to replicate it. I tried to using two resource records in the sandbox: http://sandbox.archivesspace.org/resources/6/edit#tree::resource_6 and http://sandbox.archivesspace.org/resources/13/edit#tree::resource_13. Perhaps there are some specific steps that trigger it. Can you provide any more details? From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair Sent: Wednesday, April 01, 2015 5:15 PM To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) Subject: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 Hello, I?ve been testing v1.2.0 this week and noticed while editing records that the columns aren?t aligning properly, with the result being that the shortcuts on the left hand side are overlaying the actual editing form and making it difficult to use. I?m attaching a screen shot to show what it looks like. So far I?ve noticed this with Resources and Archival Objects; not sure if it happens across the board or not. -k -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: layout glitch 2.png Type: image/png Size: 221091 bytes Desc: layout glitch 2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: layout glitch 1.png Type: image/png Size: 131567 bytes Desc: layout glitch 1.png URL: From robin_mcelheny at harvard.edu Thu Apr 2 17:21:23 2015 From: robin_mcelheny at harvard.edu (McElheny, Robin G.) Date: Thu, 2 Apr 2015 21:21:23 +0000 Subject: [Archivesspace_Users_Group] Question re new features In-Reply-To: References: Message-ID: Thanks, Brad. So does this mean that these reports will be integrated into the next release (June 30)? Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 From: Brad Westbrook [mailto:brad.westbrook at lyrasis.org] Sent: Thursday, April 02, 2015 2:39 PM To: McElheny, Robin G.; archivesspace_users_group at lyralists.lyrasis.org Cc: Carll, Johanna; Della Monica, Ilaria; Engelhart, Anne; Gustainis, Emily; Moloy, Edwin C.; Pyzynski, Susan C.; Vandermillen, Michael; Wendler, Robin King; Wise, Rachel A; Zalduendo, Ines Subject: RE: Question re new features Hi, Robin, Apparently there was a mix up with tagging issues for the release. All the reports listed in the v1.2 release passed a first test, but still must pass a subsequent test. If you are interested, you can test the reports listed for v.1.2, and others under development, using the aReports testing tool at https://github.com/archivesspace/aReports. Brad W. From: McElheny, Robin G. [mailto:robin_mcelheny at harvard.edu] Sent: Thursday, April 02, 2015 2:02 PM To: archivesspace_users_group at lyralists.lyrasis.org; Brad Westbrook Cc: Carll, Johanna; Della Monica, Ilaria; Engelhart, Anne; Gustainis, Emily; Moloy, Edwin C.; Pyzynski, Susan C.; Vandermillen, Michael; Wendler, Robin King; Wise, Rachel A; Zalduendo, Ines Subject: Question re new features Here at Harvard we were glad to see the list of new features in the latest release of ASpace, especially the following: * NEW FEATURE #AR-885 : Accession receipt * NEW FEATURE #AR-883 : Accession(s) acquired Now that we have installed the new version, we're eager to try these out - but where do we find them? We didn't see them under the list of reports, nor did we find them in Background Jobs. Are we misunderstanding what these features are? Can you help us out? Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lindsay-morecraft at uiowa.edu Thu Apr 2 18:14:04 2015 From: lindsay-morecraft at uiowa.edu (Morecraft, Lindsay M) Date: Thu, 2 Apr 2015 22:14:04 +0000 Subject: [Archivesspace_Users_Group] Who is live with ASpace? In-Reply-To: References: <96B305F061ED68428DDA721BECE2ED1551666866@ITSNT440.iowa.uiowa.edu> Message-ID: <96B305F061ED68428DDA721BECE2ED1551667A49@ITSNT440.iowa.uiowa.edu> Thank you all, this is very helpful! It is great to see all of the different styles of homepages - a great place to get ideas. Thank you, Lindsay Lindsay Moen (Morecraft) Processing Librarian Special Collections and University Archives The University of Iowa 319-335-5921 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Wednesday, April 01, 2015 9:15 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Who is live with ASpace? As you would imagine, seeing implementations of ArchivesSpace is of great interest to members and potential members of ArchivesSpace. If you have a public ArchivesSpace site and/or implementation blog or similar resource, we'd love to link to it from the ArchivesSpace members page (http://archivesspace.org/members). Please feel free to send your links directly to me, and I'll be glad to add them. Best, Christine Christine Di Bella Community Outreach and Support Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [cid:image003.png at 01CE734E.FD759D30] -------------- 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 Chris.Fitzpatrick at lyrasis.org Fri Apr 3 05:08:43 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Fri, 3 Apr 2015 09:08:43 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: References: <1427746077682.56800@lyrasis.org> <1427958850322.21749@lyrasis.org> <1427990098459.95963@lyrasis.org> <2D2C41A0-A716-4091-9357-1CC7A551790B@gmail.com>, Message-ID: <1428052123203.69615@lyrasis.org> Hi, Ah, ok. Sorry, I didn't understand what type of documentation or which links you were referring to. Let us know if you have any questions. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Danelle Moon Sent: Thursday, April 2, 2015 7:07 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released Thanks Brian. My IT staff is doing the work but they didn't want to upgrade wihout documentation. I will pass this on..... Danelle Moon Full Librarian Director SJSU Special Collections One Washington Square San Jose, CA 95192-0028 408/808-2061 office 408/808-2063 fax Danelle.Moon at sjsu.edu On Thu, Apr 2, 2015 at 9:58 AM, Brian Hoffman > wrote: Hi Danelle, That page documents the standard upgrade procedure from any version to any version. Some versions require special steps, and those have links at the top. If you are migrating ?through? one of those versions, for example from 1.0.9 to 1.2, you should still read the special instructions for the versions in between. Brian On Apr 2, 2015, at 12:53 PM, Danelle Moon > wrote: here is the body of your message with the links ...if you click on documentation it leads you to the info for 1 and 1.1 release not 1.2.0. All I need to know what should follow to install? The ArchivesSpace team is happy to release version v1.2.0. Please see the technical documentation for information on how to upgrade your ArchivesSpace installs. Please see the release page for a listing of all the new features and bug fixes included in this release. Of particular note: This release includes an upgrade to Bootstrap 3 for the staff interface. This version has significant changes to HTML, CSS, and Javascript components in the staff UI, so any plugins or custom templates will have to be modified to work with Bootstrap 3. Also included in this release is a Find-And-Replace background job, which allows users to bulk edit records. As this is a currently a beta-feature, it is recommended that users backup their database frequently if using this feature. Thanks to all the volunteers on the ArchivesSpace User Advisory and Technical Advisory Councils, who are vital to keeping ArchivesSpace development on track. Please let us know if you have any questions, comments, or concerns. Danelle Moon Full Librarian Director SJSU Special Collections One Washington Square San Jose, CA 95192-0028 408/808-2061 office 408/808-2063 fax Danelle.Moon at sjsu.edu On Thu, Apr 2, 2015 at 8:54 AM, Chris Fitzpatrick > wrote: Hi, Which links? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Danelle Moon > Sent: Thursday, April 2, 2015 5:52 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In your email announcing the new release the links you provide refer to the previous releases so we are looking for 1.2 instructions. Danelle Sent from my iPhone On Apr 2, 2015, at 12:14 AM, Chris Fitzpatrick > wrote: Hi Danelle, Which documentation are you referring to? The technical documentation is on http://archivesspace.github.io/archivesspace/doc/ and the User documentation is at https://docs.archivesspace.org/_help_proxy/login . B,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Danelle Moon > Sent: Wednesday, April 1, 2015 10:22 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released Chris Do you have updated documentation for v1.2.0? Or are we to following the documentation instructions for the two previous releases? Please send me the link to the updated documentation needed to proceed with this version Thanks Danelle Danelle Moon Full Librarian Director SJSU Special Collections One Washington Square San Jose, CA 95192-0028 408/808-2061 office 408/808-2063 fax Danelle.Moon at sjsu.edu On Mon, Mar 30, 2015 at 1:07 PM, Chris Fitzpatrick > wrote: The ArchivesSpace team is happy to release version v1.2.0. Please see the technical documentation for information on how to upgrade your ArchivesSpace installs. Please see the release page for a listing of all the new features and bug fixes included in this release. Of particular note: This release includes an upgrade to Bootstrap 3 for the staff interface. This version has significant changes to HTML, CSS, and Javascript components in the staff UI, so any plugins or custom templates will have to be modified to work with Bootstrap 3. Also included in this release is a Find-And-Replace background job, which allows users to bulk edit records. As this is a currently a beta-feature, it is recommended that users backup their database frequently if using this feature. Thanks to all the volunteers on the ArchivesSpace User Advisory and Technical Advisory Councils, who are vital to keeping ArchivesSpace development on track. Please let us know if you have any questions, comments, or concerns. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Fri Apr 3 08:49:00 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Fri, 3 Apr 2015 12:49:00 +0000 Subject: [Archivesspace_Users_Group] Problems with MARC export In-Reply-To: References: Message-ID: Hi, Sue, I filed a bug report (https://archivesspace.atlassian.net/browse/AR-1189?jql=) yesterday for the errant mapping you reported. Brad From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Thursday, April 02, 2015 12:39 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Problems with MARC export Thanks Brad! On a related note, there are other mapping issues with MARCXML export that I reported via Mark Cooper, but I wanted to check in as to their status. One of the ones I notice is still not fixed is the Preferred Citation note. AS exports it as a 534 and it should be 524 (see http://www.oclc.org/bibformats/en/5xx/524.html). Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brad Westbrook Sent: Thursday, April 02, 2015 7:22 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Problems with MARC export Hi, Sue, Thanks for catching and reporting this problem. It is, indeed, something new in v.1.2.0. I have filed a bug report (https://archivesspace.atlassian.net/browse/AR-1187?jql=) Brad From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Wednesday, April 01, 2015 7:20 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Problems with MARC export Hi programmers, I just exported a MARCXML record that included a Processing Information note. In the MARC record it mapped to a 520 $2 note, and included the header, but not the contents of the note (the note is set to publish). Can you guys look into fixing this? Thanks, Sue Luftschein Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianjhoffman at gmail.com Fri Apr 3 08:53:47 2015 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Fri, 3 Apr 2015 08:53:47 -0400 Subject: [Archivesspace_Users_Group] layout problems with edit forms in ASpace 1.2.0 In-Reply-To: <1F1E72103798F04D96C355B296D7C61B47BD7A@mb2-uts.du.edu> References: <1F1E72103798F04D96C355B296D7C61B47B82A@mb2-uts.du.edu>, <1F1E72103798F04D96C355B296D7C61B47B995@mb2-uts.du.edu>, <1F1E72103798F04D96C355B296D7C61B47BD7A@mb2-uts.du.edu> Message-ID: <9AEB3EDB-0610-47E6-8F39-EF6E181DC5C5@gmail.com> Thanks! https://archivesspace.atlassian.net/browse/AR-1192 On Apr 2, 2015, at 5:30 PM, Kevin Clair wrote: > Attached are the two things I noticed while testing. > > Glitch #1 appears when I edit an Archival Object. The publish checkbox aligns correctly in the Resource form; Firebug made it look like the label classes in the Archival Object form were still based on the 1.1.* stylesheets. > > Glitch #2 appears when a form is loading; the text isn't centered in the box. Not a big deal, it just looks off to me. > > thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Fri Apr 3 09:02:05 2015 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Fri, 3 Apr 2015 09:02:05 -0400 Subject: [Archivesspace_Users_Group] Display issues with instances/Digital Objects? Message-ID: Just wanted to bump this again. I saw some people having other display issues, but was wondering if anyone else had run into these. Thanks, Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 From: Galligan, Patrick Sent: Thursday, April 02, 2015 9:20 AM To: Archivesspace Users Group Subject: Display issues with instances/Digital Objects? We have installed 1.2.0 on our dev server, and I noticed a couple of weird display issues with the Instances and Digital objects screens. I've attached screenshots. Has anyone else seen these? We haven't made any plugins that would change these sections, so I assume it's an issue with the base code. Thanks, Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: File_Version_1.2.0.JPG Type: image/jpeg Size: 61627 bytes Desc: File_Version_1.2.0.JPG URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Instances_1.2.0.JPG Type: image/jpeg Size: 32914 bytes Desc: Instances_1.2.0.JPG URL: From brianjhoffman at gmail.com Fri Apr 3 09:13:01 2015 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Fri, 3 Apr 2015 09:13:01 -0400 Subject: [Archivesspace_Users_Group] Display issues with instances/Digital Objects? In-Reply-To: References: Message-ID: Thanks! https://archivesspace.atlassian.net/browse/AR-1192 On Apr 3, 2015, at 9:02 AM, Galligan, Patrick wrote: > Just wanted to bump this again. I saw some people having other display issues, but was wondering if anyone else had run into these. > > Thanks, > > Patrick Galligan > Rockefeller Archive Center > Assistant Digital Archivist > 914-366-6386 > > From: Galligan, Patrick > Sent: Thursday, April 02, 2015 9:20 AM > To: Archivesspace Users Group > Subject: Display issues with instances/Digital Objects? > > We have installed 1.2.0 on our dev server, and I noticed a couple of weird display issues with the Instances and Digital objects screens. > > I?ve attached screenshots. Has anyone else seen these? We haven?t made any plugins that would change these sections, so I assume it?s an issue with the base code. > > Thanks, > > Patrick Galligan > Rockefeller Archive Center > Assistant Digital Archivist > 914-366-6386 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Fri Apr 3 10:36:41 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Fri, 3 Apr 2015 10:36:41 -0400 Subject: [Archivesspace_Users_Group] Parallel Expressions in Extents In-Reply-To: <8F95A035-900D-4F1B-A727-6EF7DEAD3E08@dartmouth.edu> References: <8F95A035-900D-4F1B-A727-6EF7DEAD3E08@dartmouth.edu> Message-ID: Hmm, I suppose it would depend on how you want it formatted. I admit I'm no an archivist and so I'm not familiar with how thing 'should' look according to DACS. One option would be to keep the 'main' part of the extent as the extent label and then include the second part in a physical details note, although it doesn't seem that that note gets displayed on the public page. You could modify the display for that part of the page if you wanted it to show. The only other option I could think of would be to create a plugin that allows for a second parallel statement where things are displayed 1st Statement (2nd Statement). You'd have to modify a number of files -- I took a crack at it but I think I might have done something wrong as it doesn't appear to be rendering. Does anyone know if a plugin is incorrectly written do we get an error or does the system just load the defaults? If anyone wants to take a look feel free! I don't know ruby that well and also might be missing some files needed to make it happen. -Maura On Thu, Apr 2, 2015 at 9:59 AM, Joshua D. Shaw wrote: > Hi Maura- > > I should have been a bit clearer in my first post. The problem that I > see is that when you have one or more parallel expressions of extent > there's no obvious way to enter what are otherwise legal DACS extent > expressions. The best example I can come up with is: > > 1 transcript (782 pages) > 10 boxes (15 linear ft.) > > There's no container in the transcript expression, nor is there a > dimension or physical detail specified. That leaves us with two parallel > extents statements: a) 1 transcript & b) 782 pages. It appears that we > would have to enter these as two separate extent instances in AS. Now > that's fine if there are only these two statements and we mark both as > "whole" for the portion. However, what happens when you mix in the other > extent expression: 10 boxes (15 linear ft.)? There is no way to link the > extents that are parallel expressions since you would essentially have > something like: > > Extent 1: Portion, 1, transcript > Extent 2: Portion, 782, pages > Extent 3: Portion, 15, linear ft. with "container summary" set to: 25 > boxes > > Its impossible (at least from a scripting perspective and hence MARC > export) to be certain that Extent 1 & Extent 2 are parallel expressions. > Does that explain the issue more? I'm hoping I'm missing something simple! > > Thanks! > Joshua > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: parallel_plugin.zip Type: application/zip Size: 38059 bytes Desc: not available URL: From Kevin.Clair at du.edu Fri Apr 3 10:38:18 2015 From: Kevin.Clair at du.edu (Kevin Clair) Date: Fri, 3 Apr 2015 14:38:18 +0000 Subject: [Archivesspace_Users_Group] Display issues with instances/Digital Objects? In-Reply-To: References: Message-ID: <1F1E72103798F04D96C355B296D7C61B47BF08@mb2-uts.du.edu> I added a digital object on our test server to see if I could replicate this and had the same results. -k From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brian Hoffman Sent: Friday, April 03, 2015 7:13 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Display issues with instances/Digital Objects? Thanks! https://archivesspace.atlassian.net/browse/AR-1192 On Apr 3, 2015, at 9:02 AM, Galligan, Patrick > wrote: Just wanted to bump this again. I saw some people having other display issues, but was wondering if anyone else had run into these. Thanks, Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 From: Galligan, Patrick Sent: Thursday, April 02, 2015 9:20 AM To: Archivesspace Users Group Subject: Display issues with instances/Digital Objects? We have installed 1.2.0 on our dev server, and I noticed a couple of weird display issues with the Instances and Digital objects screens. I've attached screenshots. Has anyone else seen these? We haven't made any plugins that would change these sections, so I assume it's an issue with the base code. Thanks, Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Fri Apr 3 10:57:06 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Fri, 3 Apr 2015 14:57:06 +0000 Subject: [Archivesspace_Users_Group] Question re new features In-Reply-To: References: Message-ID: Hi, Robin, That's the plan. One barrier for now is to develop a more expeditious testing process for reports that is outside the 14 day sprint cycle. If we can do that, then we should be able to migrate most, if not, all of the reports in AT and to add some new ones for ArchivesSpace by June 30. Brad From: McElheny, Robin G. [mailto:robin_mcelheny at harvard.edu] Sent: Thursday, April 02, 2015 5:21 PM To: Brad Westbrook; archivesspace_users_group at lyralists.lyrasis.org Cc: Carll, Johanna; Della Monica, Ilaria; Engelhart, Anne; Gustainis, Emily; Moloy, Edwin C.; Pyzynski, Susan C.; Vandermillen, Michael; Wendler, Robin King; Wise, Rachel A; Zalduendo, Ines Subject: RE: Question re new features Thanks, Brad. So does this mean that these reports will be integrated into the next release (June 30)? Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 From: Brad Westbrook [mailto:brad.westbrook at lyrasis.org] Sent: Thursday, April 02, 2015 2:39 PM To: McElheny, Robin G.; archivesspace_users_group at lyralists.lyrasis.org Cc: Carll, Johanna; Della Monica, Ilaria; Engelhart, Anne; Gustainis, Emily; Moloy, Edwin C.; Pyzynski, Susan C.; Vandermillen, Michael; Wendler, Robin King; Wise, Rachel A; Zalduendo, Ines Subject: RE: Question re new features Hi, Robin, Apparently there was a mix up with tagging issues for the release. All the reports listed in the v1.2 release passed a first test, but still must pass a subsequent test. If you are interested, you can test the reports listed for v.1.2, and others under development, using the aReports testing tool at https://github.com/archivesspace/aReports. Brad W. From: McElheny, Robin G. [mailto:robin_mcelheny at harvard.edu] Sent: Thursday, April 02, 2015 2:02 PM To: archivesspace_users_group at lyralists.lyrasis.org; Brad Westbrook Cc: Carll, Johanna; Della Monica, Ilaria; Engelhart, Anne; Gustainis, Emily; Moloy, Edwin C.; Pyzynski, Susan C.; Vandermillen, Michael; Wendler, Robin King; Wise, Rachel A; Zalduendo, Ines Subject: Question re new features Here at Harvard we were glad to see the list of new features in the latest release of ASpace, especially the following: * NEW FEATURE #AR-885 : Accession receipt * NEW FEATURE #AR-883 : Accession(s) acquired Now that we have installed the new version, we're eager to try these out - but where do we find them? We didn't see them under the list of reports, nor did we find them in Background Jobs. Are we misunderstanding what these features are? Can you help us out? Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joshua.D.Shaw at dartmouth.edu Fri Apr 3 12:19:20 2015 From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw) Date: Fri, 3 Apr 2015 16:19:20 +0000 Subject: [Archivesspace_Users_Group] Parallel Expressions in Extents Message-ID: <88576F5C-0330-41F5-8171-4687F1FF7419@dartmouth.edu> Hi Maura- After talking it over, we think we'll probably just use the container summary to hold the parallel expression. That will be valid for most things and for the few it's not....well, we'll deal with that if it turns out to cause unexpected issues. It also simplifies our mapping by quite a bit! Thanks for taking a stab at the plugin as well - above and beyond! Joshua From: Maura Carbone Reply-To: Archivesspace Users Group Date: Friday, April 3, 2015 at 10:36 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Parallel Expressions in Extents Hmm, I suppose it would depend on how you want it formatted. I admit I'm no an archivist and so I'm not familiar with how thing 'should' look according to DACS. One option would be to keep the 'main' part of the extent as the extent label and then include the second part in a physical details note, although it doesn't seem that that note gets displayed on the public page. You could modify the display for that part of the page if you wanted it to show. The only other option I could think of would be to create a plugin that allows for a second parallel statement where things are displayed 1st Statement (2nd Statement). You'd have to modify a number of files -- I took a crack at it but I think I might have done something wrong as it doesn't appear to be rendering. Does anyone know if a plugin is incorrectly written do we get an error or does the system just load the defaults? If anyone wants to take a look feel free! I don't know ruby that well and also might be missing some files needed to make it happen. -Maura On Thu, Apr 2, 2015 at 9:59 AM, Joshua D. Shaw > wrote: Hi Maura- I should have been a bit clearer in my first post. The problem that I see is that when you have one or more parallel expressions of extent there's no obvious way to enter what are otherwise legal DACS extent expressions. The best example I can come up with is: 1 transcript (782 pages) 10 boxes (15 linear ft.) There's no container in the transcript expression, nor is there a dimension or physical detail specified. That leaves us with two parallel extents statements: a) 1 transcript & b) 782 pages. It appears that we would have to enter these as two separate extent instances in AS. Now that's fine if there are only these two statements and we mark both as "whole" for the portion. However, what happens when you mix in the other extent expression: 10 boxes (15 linear ft.)? There is no way to link the extents that are parallel expressions since you would essentially have something like: Extent 1: Portion, 1, transcript Extent 2: Portion, 782, pages Extent 3: Portion, 15, linear ft. with "container summary" set to: 25 boxes Its impossible (at least from a scripting perspective and hence MARC export) to be certain that Extent 1 & Extent 2 are parallel expressions. Does that explain the issue more? I'm hoping I'm missing something simple! Thanks! Joshua _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianjhoffman at gmail.com Fri Apr 3 12:24:32 2015 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Fri, 3 Apr 2015 12:24:32 -0400 Subject: [Archivesspace_Users_Group] Parallel Expressions in Extents In-Reply-To: References: <8F95A035-900D-4F1B-A727-6EF7DEAD3E08@dartmouth.edu> Message-ID: Hi Maura, You are on the right track, but your path should just be ?frontend/views? rather than ?frontend/app/views?. If you make that change your templates will take effect. There are some other issues with the plugin though - you?re trying to add a new field to the extent schema and to add a new enumeration ?extent_extent_type_parallel?. Both of those changes require corresponding changes to the database. You?ll need to write a migration that adds those two fields to the extent table, and that creates the enumeration. Here?s a plugin that has lots of migrations you can use as a guide: https://github.com/hudmol/yale_containers Brian On Apr 3, 2015, at 10:36 AM, Maura Carbone wrote: > Hmm, I suppose it would depend on how you want it formatted. I admit I'm no an archivist and so I'm not familiar with how thing 'should' look according to DACS. One option would be to keep the 'main' part of the extent as the extent label and then include the second part in a physical details note, although it doesn't seem that that note gets displayed on the public page. You could modify the display for that part of the page if you wanted it to show. > > The only other option I could think of would be to create a plugin that allows for a second parallel statement where things are displayed 1st Statement (2nd Statement). You'd have to modify a number of files -- I took a crack at it but I think I might have done something wrong as it doesn't appear to be rendering. Does anyone know if a plugin is incorrectly written do we get an error or does the system just load the defaults? If anyone wants to take a look feel free! I don't know ruby that well and also might be missing some files needed to make it happen. > > -Maura > > > > On Thu, Apr 2, 2015 at 9:59 AM, Joshua D. Shaw wrote: > Hi Maura- > > I should have been a bit clearer in my first post. The problem that I see is that when you have one or more parallel expressions of extent there's no obvious way to enter what are otherwise legal DACS extent expressions. The best example I can come up with is: > > 1 transcript (782 pages) > 10 boxes (15 linear ft.) > > There's no container in the transcript expression, nor is there a dimension or physical detail specified. That leaves us with two parallel extents statements: a) 1 transcript & b) 782 pages. It appears that we would have to enter these as two separate extent instances in AS. Now that's fine if there are only these two statements and we mark both as "whole" for the portion. However, what happens when you mix in the other extent expression: 10 boxes (15 linear ft.)? There is no way to link the extents that are parallel expressions since you would essentially have something like: > > Extent 1: Portion, 1, transcript > Extent 2: Portion, 782, pages > Extent 3: Portion, 15, linear ft. with "container summary" set to: 25 boxes > > Its impossible (at least from a scripting perspective and hence MARC export) to be certain that Extent 1 & Extent 2 are parallel expressions. Does that explain the issue more? I'm hoping I'm missing something simple! > > Thanks! > Joshua > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Fri Apr 3 13:45:35 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Fri, 3 Apr 2015 13:45:35 -0400 Subject: [Archivesspace_Users_Group] Parallel Expressions in Extents In-Reply-To: <88576F5C-0330-41F5-8171-4687F1FF7419@dartmouth.edu> References: <88576F5C-0330-41F5-8171-4687F1FF7419@dartmouth.edu> Message-ID: Yeah that's the easier way to go for sure, haha. And no problem! I've been trying to dig deeper into the code and it is easier for me when I have a task to try :-) -Maura On Fri, Apr 3, 2015 at 12:19 PM, Joshua D. Shaw wrote: > Hi Maura- > > After talking it over, we think we'll probably just use the container > summary to hold the parallel expression. That will be valid for most things > and for the few it's not....well, we'll deal with that if it turns out to > cause unexpected issues. It also simplifies our mapping by quite a bit! > > Thanks for taking a stab at the plugin as well - above and beyond! > > Joshua > > From: Maura Carbone > Reply-To: Archivesspace Users Group > Date: Friday, April 3, 2015 at 10:36 AM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Parallel Expressions in Extents > > Hmm, I suppose it would depend on how you want it formatted. I admit > I'm no an archivist and so I'm not familiar with how thing 'should' look > according to DACS. One option would be to keep the 'main' part of the > extent as the extent label and then include the second part in a physical > details note, although it doesn't seem that that note gets displayed on the > public page. You could modify the display for that part of the page if you > wanted it to show. > > The only other option I could think of would be to create a plugin that > allows for a second parallel statement where things are displayed 1st > Statement (2nd Statement). You'd have to modify a number of files -- I took > a crack at it but I think I might have done something wrong as it doesn't > appear to be rendering. Does anyone know if a plugin is incorrectly written > do we get an error or does the system just load the defaults? If anyone > wants to take a look feel free! I don't know ruby that well and also might > be missing some files needed to make it happen. > > -Maura > > > > On Thu, Apr 2, 2015 at 9:59 AM, Joshua D. Shaw < > Joshua.D.Shaw at dartmouth.edu> wrote: > >> Hi Maura- >> >> I should have been a bit clearer in my first post. The problem that I >> see is that when you have one or more parallel expressions of extent >> there's no obvious way to enter what are otherwise legal DACS extent >> expressions. The best example I can come up with is: >> >> 1 transcript (782 pages) >> 10 boxes (15 linear ft.) >> >> There's no container in the transcript expression, nor is there a >> dimension or physical detail specified. That leaves us with two parallel >> extents statements: a) 1 transcript & b) 782 pages. It appears that we >> would have to enter these as two separate extent instances in AS. Now >> that's fine if there are only these two statements and we mark both as >> "whole" for the portion. However, what happens when you mix in the other >> extent expression: 10 boxes (15 linear ft.)? There is no way to link the >> extents that are parallel expressions since you would essentially have >> something like: >> >> Extent 1: Portion, 1, transcript >> Extent 2: Portion, 782, pages >> Extent 3: Portion, 15, linear ft. with "container summary" set to: 25 >> boxes >> >> Its impossible (at least from a scripting perspective and hence MARC >> export) to be certain that Extent 1 & Extent 2 are parallel expressions. >> Does that explain the issue more? I'm hoping I'm missing something simple! >> >> Thanks! >> Joshua >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From robin_mcelheny at harvard.edu Fri Apr 3 15:31:36 2015 From: robin_mcelheny at harvard.edu (McElheny, Robin G.) Date: Fri, 3 Apr 2015 19:31:36 +0000 Subject: [Archivesspace_Users_Group] Question re new features In-Reply-To: References: Message-ID: Thanks for the update, Brad. We are preparing to launch at the end of June/early July. When can you let us know whether the AT reports will be in the next release? We depend on those reports so we need some advance notice if we have to figure out some kind of temporary solution. Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 From: Brad Westbrook [mailto:brad.westbrook at lyrasis.org] Sent: Friday, April 03, 2015 10:57 AM To: McElheny, Robin G.; archivesspace_users_group at lyralists.lyrasis.org Cc: Carll, Johanna; Della Monica, Ilaria; Engelhart, Anne; Gustainis, Emily; Moloy, Edwin C.; Pyzynski, Susan C.; Vandermillen, Michael; Wendler, Robin King; Wise, Rachel A; Zalduendo, Ines Subject: RE: Question re new features Hi, Robin, That's the plan. One barrier for now is to develop a more expeditious testing process for reports that is outside the 14 day sprint cycle. If we can do that, then we should be able to migrate most, if not, all of the reports in AT and to add some new ones for ArchivesSpace by June 30. Brad From: McElheny, Robin G. [mailto:robin_mcelheny at harvard.edu] Sent: Thursday, April 02, 2015 5:21 PM To: Brad Westbrook; archivesspace_users_group at lyralists.lyrasis.org Cc: Carll, Johanna; Della Monica, Ilaria; Engelhart, Anne; Gustainis, Emily; Moloy, Edwin C.; Pyzynski, Susan C.; Vandermillen, Michael; Wendler, Robin King; Wise, Rachel A; Zalduendo, Ines Subject: RE: Question re new features Thanks, Brad. So does this mean that these reports will be integrated into the next release (June 30)? Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 From: Brad Westbrook [mailto:brad.westbrook at lyrasis.org] Sent: Thursday, April 02, 2015 2:39 PM To: McElheny, Robin G.; archivesspace_users_group at lyralists.lyrasis.org Cc: Carll, Johanna; Della Monica, Ilaria; Engelhart, Anne; Gustainis, Emily; Moloy, Edwin C.; Pyzynski, Susan C.; Vandermillen, Michael; Wendler, Robin King; Wise, Rachel A; Zalduendo, Ines Subject: RE: Question re new features Hi, Robin, Apparently there was a mix up with tagging issues for the release. All the reports listed in the v1.2 release passed a first test, but still must pass a subsequent test. If you are interested, you can test the reports listed for v.1.2, and others under development, using the aReports testing tool at https://github.com/archivesspace/aReports. Brad W. From: McElheny, Robin G. [mailto:robin_mcelheny at harvard.edu] Sent: Thursday, April 02, 2015 2:02 PM To: archivesspace_users_group at lyralists.lyrasis.org; Brad Westbrook Cc: Carll, Johanna; Della Monica, Ilaria; Engelhart, Anne; Gustainis, Emily; Moloy, Edwin C.; Pyzynski, Susan C.; Vandermillen, Michael; Wendler, Robin King; Wise, Rachel A; Zalduendo, Ines Subject: Question re new features Here at Harvard we were glad to see the list of new features in the latest release of ASpace, especially the following: * NEW FEATURE #AR-885 : Accession receipt * NEW FEATURE #AR-883 : Accession(s) acquired Now that we have installed the new version, we're eager to try these out - but where do we find them? We didn't see them under the list of reports, nor did we find them in Background Jobs. Are we misunderstanding what these features are? Can you help us out? Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mary.caldera at yale.edu Mon Apr 6 10:20:17 2015 From: mary.caldera at yale.edu (mary.caldera at yale.edu) Date: Mon, 6 Apr 2015 07:20:17 -0700 (PDT) Subject: [Archivesspace_Users_Group] Editing hover instructions in staff interface In-Reply-To: <1427830860612.67068@lyrasis.org> References: <97bac5c5-990a-457c-9a26-2054ae646e01@googlegroups.com> <1427830860612.67068@lyrasis.org> Message-ID: <4dc22bb2-cf9a-4f69-bb78-64c9ede798c0@googlegroups.com> Thanks Chris! On Tuesday, March 31, 2015 at 3:41:05 PM UTC-4, Chris Fitzpatrick wrote: > > Hi, > > > You mean "tooltips"? > > > > https://github.com/archivesspace/archivesspace/tree/master/common/locales#tooltips > > > So, for example you want to change the one for the repository > shortname ( actually called a the "repo code" ) field in the new repository > form... > > > Edit the locales/en.yml file and find the repo_code_tooltip > . > Change that text ( not the in YAML multi-line text starts with a "|" but > you'll need to keep indention, which is how the value-pair hierarchy is > ordered ). > > > What to change the resource title tooltip? Find the "title_tooltip" > > in the "resource" section and change that text. > > > Let me know if you have any questions...b,chris. > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > > on behalf of mary.c... at yale.edu < > mary.c... at yale.edu > > *Sent:* Tuesday, March 31, 2015 3:01 PM > *To:* archiv... at googlegroups.com > *Cc:* archivesspac... at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] Editing hover instructions in > staff interface > > Hi, > > How can I edit the staff interface hover instructions? I have been > unable to locate any documentation on how to do this. > > Thanks, > Mary Caldera > Yale University Library > -------------- next part -------------- An HTML attachment was scrubbed... URL: From psuda1 at tulane.edu Mon Apr 6 11:42:50 2015 From: psuda1 at tulane.edu (Suda, Phillip J) Date: Mon, 6 Apr 2015 15:42:50 +0000 Subject: [Archivesspace_Users_Group] Public DevServer and Records/Results Message-ID: Good morning, Forgive my idiocy, but how can I get results to show up when I am working on the public:devserver build? I am working on display customizations, but I want to look at how results/records show up on public interface. Do I connect this to the mysql db somehow? 1. Ran build/run backend:devserver 2. Ran build/run public:devserver 3. Editing public/assets/themes/default.less (renamed) 4. No records are showing up. How do I get to see example results on devserver? Thanks for any help. Thank you, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 -------------- next part -------------- An HTML attachment was scrubbed... URL: From megan.mummey at uky.edu Mon Apr 6 13:08:06 2015 From: megan.mummey at uky.edu (Mummey, Megan) Date: Mon, 6 Apr 2015 17:08:06 +0000 Subject: [Archivesspace_Users_Group] Repository usage Message-ID: <61DF82E43FF6684FBA238273601C90A15925CE56@ex10mb01.ad.uky.edu> Hi all, At UK we're currently trying to decide if we are going to use the repository function in ArchivesSpace. We have three administrative units within Special Collections, but we only have one reference point. We're trying to build a list of pros and cons, so we'd like to hear how other institutions are using repositories. If your institution has decided how to structure your installation of ArchivesSpace and feel like sharing, please send me an email. Thanks, Megan Mummey Collections Management Archivist Special Collections Research Center University of Kentucky Libraries Margaret I. King Library Lexington, KY 40506-0039 megan.mummey at uky.edu|859.257.6942 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mang.sun at rice.edu Mon Apr 6 13:14:38 2015 From: mang.sun at rice.edu (Mang Sun) Date: Mon, 06 Apr 2015 12:14:38 -0500 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: <551D6503.8000500@rice.edu> References: <551D6503.8000500@rice.edu> Message-ID: <5522BEFE.6090502@rice.edu> Can somebody or the development team confirm whether the public_formats_resource_links plugin still works with AS 1.2? Mang Sun Rice U. On 4/2/2015 10:49 AM, Mang Sun wrote: > When clicking the ead_pdf link turned on by the > public_formats_resource_links plugin does not work with AS 1.2 > throwing the error message as follows. -Mang Sun Rice U. > > > EOFError in PublicFormatsController#generate > > |Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public > > | > > > Request > > *Parameters*: > > {"repo_id"=>"2", > "type"=>"resources", > "id"=>"116", > "format"=>"ead_pdf"} > > Show session dump > > > _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" > session_id: "c419289cb412f46af571004e4b0c0830" > > Show env dump > > > GATEWAY_INTERFACE: "CGI/1.2" > HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" > HTTP_ACCEPT_ENCODING: "gzip, deflate" > HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" > REMOTE_ADDR: "10.xx.xx.xx" > SERVER_NAME: "10.xx.22.xx" > SERVER_PROTOCOL: "HTTP/1.1" > > > Response > > *Headers*: > > None > ----------------- > The Full trace is pasted as below. > > |org/jruby/RubyIO.java:2858:in `read_nonblock' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request' > org/jruby/RubyKernel.java:1270:in `catch' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start' > /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request' > /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle' > /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate' > actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action' > actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action' > actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action' > actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action' > activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks' > activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' > activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks' > activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' > actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action' > actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action' > actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action' > activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' > activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument' > activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument' > activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' > actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action' > actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action' > actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process' > actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process' > actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch' > actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch' > actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action' > org/jruby/RubyProc.java:271:in `call' > actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch' > actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call' > journey (1.0.4) lib/journey/router.rb:68:in `call' > org/jruby/RubyArray.java:1613:in `each' > journey (1.0.4) lib/journey/router.rb:56:in `call' > actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call' > actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call' > rack (1.4.5) lib/rack/etag.rb:23:in `call' > rack (1.4.5) lib/rack/conditionalget.rb:25:in `call' > actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call' > actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call' > actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call' > rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context' > rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call' > actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call' > actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call' > activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks' > activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' > activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks' > activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' > actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call' > actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call' > actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call' > actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call' > actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' > railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app' > railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' > activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged' > railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' > actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call' > rack (1.4.5) lib/rack/methodoverride.rb:21:in `call' > rack (1.4.5) lib/rack/runtime.rb:17:in `call' > activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call' > rack (1.4.5) lib/rack/lock.rb:15:in `call' > actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call' > railties (3.2.19) lib/rails/engine.rb:484:in `call' > railties (3.2.19) lib/rails/application.rb:231:in `call' > rack (1.4.5) lib/rack/content_length.rb:14:in `call' > railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call' > puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request' > puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request' > puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client' > puma-2.8.2 (java) lib/puma/server.rb:254:in `run' > org/jruby/RubyProc.java:271:in `call' > puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread'| > > > > _______________________________________________ > 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 mark.custer at yale.edu Mon Apr 6 13:15:37 2015 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 6 Apr 2015 17:15:37 +0000 Subject: [Archivesspace_Users_Group] Public DevServer and Records/Results In-Reply-To: References: Message-ID: Phil, I might be completely misunderstanding, but if you have everything set up and the public interface is running (and you haven't changed the default port or URL), then you should see the public version at port 8081. Example: http://test.archivesspace.org:8081 If you have data in the database, it should display in the public interface. Also, once the data has been indexed by Solr, you should be able to see those records by searching / browsing the interface (whether public or staff). The URLs in the staff and public interface currently use primary keys from the database - e.g. the 2 and the 15 in the following URL are primary keys in the database, http://test.archivesspace.org:8081/repositories/2/archival_objects/15. So, even if an index hasn't caught up, you should be able to test URLs in the public interface immediately by looking at the database backend and creating a list of URLs to check out. Does that help at all, or did I completely misread your email (which is an easy thing for me to do right after lunchtime)? Mark P.S. I'd love to hear more about the display customizations that you're making to the public interface! From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Suda, Phillip J Sent: Monday, April 06, 2015 11:43 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Public DevServer and Records/Results Good morning, Forgive my idiocy, but how can I get results to show up when I am working on the public:devserver build? I am working on display customizations, but I want to look at how results/records show up on public interface. Do I connect this to the mysql db somehow? 1. Ran build/run backend:devserver 2. Ran build/run public:devserver 3. Editing public/assets/themes/default.less (renamed) 4. No records are showing up. How do I get to see example results on devserver? Thanks for any help. Thank you, Phil Phillip Suda Systems Librarian Howard-Tilton Memorial Library Tulane University psuda1 at tulane.edu 504-865-5607 -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Mon Apr 6 13:47:35 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Mon, 6 Apr 2015 17:47:35 +0000 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: <5522BEFE.6090502@rice.edu> References: <551D6503.8000500@rice.edu> <5522BEFE.6090502@rice.edu> Message-ID: Hi, Mang I just successfully tested the public formats plugin for all three options. I tested it in a localhost install using the embedded Derby database. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mang Sun Sent: Monday, April 06, 2015 1:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 Can somebody or the development team confirm whether the public_formats_resource_links plugin still works with AS 1.2? Mang Sun Rice U. On 4/2/2015 10:49 AM, Mang Sun wrote: When clicking the ead_pdf link turned on by the public_formats_resource_links plugin does not work with AS 1.2 throwing the error message as follows. -Mang Sun Rice U. EOFError in PublicFormatsController#generate Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public Request Parameters: {"repo_id"=>"2", "type"=>"resources", "id"=>"116", "format"=>"ead_pdf"} Show session dump _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" session_id: "c419289cb412f46af571004e4b0c0830" Show env dump GATEWAY_INTERFACE: "CGI/1.2" HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" HTTP_ACCEPT_ENCODING: "gzip, deflate" HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" REMOTE_ADDR: "10.xx.xx.xx" SERVER_NAME: "10.xx.22.xx" SERVER_PROTOCOL: "HTTP/1.1" Response Headers: None ----------------- The Full trace is pasted as below. org/jruby/RubyIO.java:2858:in `read_nonblock' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request' org/jruby/RubyKernel.java:1270:in `catch' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request' /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle' /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate' actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action' actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action' actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action' actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action' activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action' actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action' actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action' activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument' activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument' activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action' actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action' actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process' actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process' actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch' actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch' actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action' org/jruby/RubyProc.java:271:in `call' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call' journey (1.0.4) lib/journey/router.rb:68:in `call' org/jruby/RubyArray.java:1613:in `each' journey (1.0.4) lib/journey/router.rb:56:in `call' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call' rack (1.4.5) lib/rack/etag.rb:23:in `call' rack (1.4.5) lib/rack/conditionalget.rb:25:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call' rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context' rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call' activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app' railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged' railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call' rack (1.4.5) lib/rack/methodoverride.rb:21:in `call' rack (1.4.5) lib/rack/runtime.rb:17:in `call' activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call' rack (1.4.5) lib/rack/lock.rb:15:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call' railties (3.2.19) lib/rails/engine.rb:484:in `call' railties (3.2.19) lib/rails/application.rb:231:in `call' rack (1.4.5) lib/rack/content_length.rb:14:in `call' railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call' puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request' puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request' puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client' puma-2.8.2 (java) lib/puma/server.rb:254:in `run' org/jruby/RubyProc.java:271:in `call' puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread' _______________________________________________ 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 mang.sun at rice.edu Mon Apr 6 14:18:24 2015 From: mang.sun at rice.edu (Mang Sun) Date: Mon, 06 Apr 2015 13:18:24 -0500 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: References: <551D6503.8000500@rice.edu> <5522BEFE.6090502@rice.edu> Message-ID: <5522CDF0.5030905@rice.edu> Thank you very much Brad. Now we need to figure out why the ead_pdf option of this plugin does not work with our AS 1.2 instance in development mode. Mang On 4/6/2015 12:47 PM, Brad Westbrook wrote: > > Hi, Mang > > I just successfully tested the public formats plugin for all three > options. I tested it in a localhost install using the embedded Derby > database. > > Brad W. > > *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org > [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] *On > Behalf Of *Mang Sun > *Sent:* Monday, April 06, 2015 1:15 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] The ead_pdf link generated > by plugin public_formats_resource_links does not work with AS 1.2 > > Can somebody or the development team confirm whether the > public_formats_resource_links plugin still works with AS 1.2? > > Mang Sun > Rice U. > > On 4/2/2015 10:49 AM, Mang Sun wrote: > > When clicking the ead_pdf link turned on by the > public_formats_resource_links plugin does not work with AS 1.2 > throwing the error message as follows. -Mang Sun Rice U. > > > EOFError in PublicFormatsController#generate > > |Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public| > > > Request > > *Parameters*: > > {"repo_id"=>"2", > > "type"=>"resources", > > "id"=>"116", > > "format"=>"ead_pdf"} > > Show session dump > > > _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" > > session_id: "c419289cb412f46af571004e4b0c0830" > > Show env dump > > > GATEWAY_INTERFACE: "CGI/1.2" > > HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" > > HTTP_ACCEPT_ENCODING: "gzip, deflate" > > HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" > > REMOTE_ADDR: "10.xx.xx.xx" > > SERVER_NAME: "10.xx.22.xx" > > SERVER_PROTOCOL: "HTTP/1.1" > > > Response > > *Headers*: > > None > > ----------------- > > The Full trace is pasted as below. > > > > |org/jruby/RubyIO.java:2858:in `read_nonblock'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request'| > > |org/jruby/RubyKernel.java:1270:in `catch'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request'| > > |/opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle'| > > |/opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate'| > > |actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action'| > > |actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action'| > > |actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action'| > > |actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks'| > > |actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action'| > > |actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action'| > > |actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action'| > > |activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument'| > > |activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument'| > > |activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument'| > > |activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument'| > > |actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action'| > > |actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action'| > > |actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process'| > > |actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process'| > > |actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch'| > > |actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch'| > > |actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action'| > > |org/jruby/RubyProc.java:271:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch'| > > |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call'| > > |journey (1.0.4) lib/journey/router.rb:68:in `call'| > > |org/jruby/RubyArray.java:1613:in `each'| > > |journey (1.0.4) lib/journey/router.rb:56:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call'| > > |rack (1.4.5) lib/rack/etag.rb:23:in `call'| > > |rack (1.4.5) lib/rack/conditionalget.rb:25:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call'| > > |rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context'| > > |rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'| > > |railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app'| > > |railties (3.2.19) lib/rails/rack/logger.rb:16:in `call'| > > |activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged'| > > |railties (3.2.19) lib/rails/rack/logger.rb:16:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call'| > > |rack (1.4.5) lib/rack/methodoverride.rb:21:in `call'| > > |rack (1.4.5) lib/rack/runtime.rb:17:in `call'| > > |activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call'| > > |rack (1.4.5) lib/rack/lock.rb:15:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call'| > > |railties (3.2.19) lib/rails/engine.rb:484:in `call'| > > |railties (3.2.19) lib/rails/application.rb:231:in `call'| > > |rack (1.4.5) lib/rack/content_length.rb:14:in `call'| > > |railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call'| > > |puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request'| > > |puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request'| > > |puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client'| > > |puma-2.8.2 (java) lib/puma/server.rb:254:in `run'| > > |org/jruby/RubyProc.java:271:in `call'| > > |puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread'| > > > > > > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From akroeger at unomaha.edu Mon Apr 6 14:47:23 2015 From: akroeger at unomaha.edu (Angela Kroeger) Date: Mon, 6 Apr 2015 18:47:23 +0000 Subject: [Archivesspace_Users_Group] Repository usage In-Reply-To: <61DF82E43FF6684FBA238273601C90A15925CE56@ex10mb01.ad.uky.edu> References: <61DF82E43FF6684FBA238273601C90A15925CE56@ex10mb01.ad.uky.edu> Message-ID: Hi, Megan, We use a sort of hybrid approach with repositories and classifications. We have two repositories, and the reason for this relates to the origin of the metadata in each of them. One was populated via import data from Archivists Toolkit. The other was populated from an Excel spreadsheet. From an organizational standpoint, they were structured so differently that we didn't want to mix them in the same repository. Within the repository that started life as a spreadsheet, we use classifications to distinguish between three different collecting areas (different units within our department). If the finding aids of your three administrative units are presently mingled in Archivists Toolkit, Archon, or some other shared system, they may migrate well into a single repository. If your units have significantly different metadata practices, you might consider different repositories. Hope that helps! --Angela Angela Kroeger akroeger at unomaha.edu Archives and Special Collections Associate Dr. C.C. and Mabel L. Criss Library University of Nebraska at Omaha (402) 554-4159 -------------- next part -------------- An HTML attachment was scrubbed... URL: From djpillen at umich.edu Mon Apr 6 15:08:55 2015 From: djpillen at umich.edu (Dallas Pillen) Date: Mon, 6 Apr 2015 15:08:55 -0400 Subject: [Archivesspace_Users_Group] Import EAD via the API? Message-ID: Hello all, I was curious if anyone has had any success starting EAD import jobs via the API? I was thinking this could be done using POST /repositories/:repo_id/jobs_with_files described here: http://archivesspace.github.io/archivesspace/doc/file.API.html#post-repositoriesrepoidjobswithfiles However, I am not entirely sure how the job and file parameters should be sent in the POST request, and I haven't seen anyone ask this question before or give an example of how it might work. I've tried sending the POST request several different ways and each time I am met with: {"error":{"job":["Parameter required but no value provided"],"files":["Parameter required but no value provided"]}}. I suppose it's worth mentioning that the reason I want to do this is that, at some point, we will be importing several thousand EADs into ArchivesSpace. We're doing a lot of preliminary work to make our EADs import successfully, but know there will likely be some that will fail. Right now, the only way to do a batch import of EADs is to do a batch as a single import job. If one EAD in that job has an error, the entire job fails. For that reason, I would like to be able to import each EAD as a separate job so that the EADs that will import successfully will do so without being impacted by the EADs with errors. However, starting several thousand individual import jobs would be very tedious, and I'm looking for a way to automate that process. If anyone else has come up with any creative solutions or knows of a better way to do that than the API, I would be very interested to know. The end goal would be to have a script that would batch start the import jobs, get the ID for each job, check up on the jobs every so often and, once there are no longer any active jobs, output some information about each of the jobs that failed. I've figured out how to do most of that using the API, but I'm stumped on how to get the whole process started. Thanks! Dallas -- *Dallas Pillen*Project Archivist Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Mon Apr 6 15:25:21 2015 From: noah.huffman at duke.edu (Noah Huffman) Date: Mon, 6 Apr 2015 19:25:21 +0000 Subject: [Archivesspace_Users_Group] Import EAD via the API? In-Reply-To: References: Message-ID: Dallas, This doesn?t directly answer your question, but you might consider batch importing your EADs into Archivists Toolkit and then running the AT to ASpace migration tool to migrate the data to ArchivesSpace. I have found that the EAD batch import process for AT is a bit more forgiving. Also, running the AT to ArchivesSpace migration script is much more efficient than importing EAD directly into ArchivesSpace. Still, I?d be interested in hearing how to batch import EAD into ASpace through the API. -Noah ================ Noah Huffman Archivist for Metadata and Encoding David M. Rubenstein Rare Book & Manuscript Library Duke University From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Dallas Pillen Sent: Monday, April 06, 2015 3:09 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Import EAD via the API? Hello all, I was curious if anyone has had any success starting EAD import jobs via the API? I was thinking this could be done using POST /repositories/:repo_id/jobs_with_files described here: http://archivesspace.github.io/archivesspace/doc/file.API.html#post-repositoriesrepoidjobswithfiles However, I am not entirely sure how the job and file parameters should be sent in the POST request, and I haven't seen anyone ask this question before or give an example of how it might work. I've tried sending the POST request several different ways and each time I am met with: {"error":{"job":["Parameter required but no value provided"],"files":["Parameter required but no value provided"]}}. I suppose it's worth mentioning that the reason I want to do this is that, at some point, we will be importing several thousand EADs into ArchivesSpace. We're doing a lot of preliminary work to make our EADs import successfully, but know there will likely be some that will fail. Right now, the only way to do a batch import of EADs is to do a batch as a single import job. If one EAD in that job has an error, the entire job fails. For that reason, I would like to be able to import each EAD as a separate job so that the EADs that will import successfully will do so without being impacted by the EADs with errors. However, starting several thousand individual import jobs would be very tedious, and I'm looking for a way to automate that process. If anyone else has come up with any creative solutions or knows of a better way to do that than the API, I would be very interested to know. The end goal would be to have a script that would batch start the import jobs, get the ID for each job, check up on the jobs every so often and, once there are no longer any active jobs, output some information about each of the jobs that failed. I've figured out how to do most of that using the API, but I'm stumped on how to get the whole process started. Thanks! Dallas -- Dallas Pillen Project Archivist [https://webapps.lsa.umich.edu/dean/lsa_emails/bentley-sig-em.png] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Mon Apr 6 15:35:55 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Mon, 6 Apr 2015 15:35:55 -0400 Subject: [Archivesspace_Users_Group] Accession CSV Subject Import In-Reply-To: References: <1427830174945.5955@lyrasis.org> Message-ID: Hi Chris, Any progress on that example? I actually tried to work on it myself, but I'm not entirely sure which files need to be altered (aside from accession_converter). Ideally, I want to be able to import multiple subjects and multiple agents -- I was hoping to copy the date setup (where there are multiple dates date1 date2 etc.) but I haven't found the file where the terms (such as date_label_1) are mapped to the date object (and so on for subject and agents etc.) Thanks! Maura On Tue, Mar 31, 2015 at 4:03 PM, Maura Carbone wrote: > What I was doing was: > subject_source,subject_term_type,subject_term,subject_source,subject_term_type,subject_term, Unspecified > ingested source,Topical,Pepperoni,Unspecified ingested > source,Topical,Cheese. Then only Cheese gets created and imported. > > Yeah, and I can take a look at how the importer works now as well, I just > wasn't sure if it was a known issue, or if there was a specific reason for > it. > > Thanks! > Maura > > On Tue, Mar 31, 2015 at 3:29 PM, Chris Fitzpatrick < > Chris.Fitzpatrick at lyrasis.org> wrote: > >> Hi Maura, >> >> >> So, you're just adding more subject columns to the CSV? Yes, what you >> describe about overwriting is exactly what's happening...the CSV importer >> only allows for one subject per row. >> >> >> I have a plugin example I started working on last week to show how to >> tweak the CSV importer...I'll try and finish that up tomorrow and send it >> out for people to have a look... >> >> >> b,chris. >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> ------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >> Maura Carbone >> *Sent:* Tuesday, March 31, 2015 7:06 PM >> *To:* Archivesspace Users Group >> *Subject:* [Archivesspace_Users_Group] Accession CSV Subject Import >> >> Hi all, >> I've been working on importing accessions with CSV files, but I've >> noticed that on import only one subject ever gets brought in (the last >> one). Is this a bug, or just a current limitation? I'm not getting an >> error, it just appears that the subject field keeps being over-written >> until the last subject, then imported. >> >> Thanks, >> Maura >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.cooper at lyrasis.org Mon Apr 6 15:50:40 2015 From: mark.cooper at lyrasis.org (Mark Cooper) Date: Mon, 6 Apr 2015 19:50:40 +0000 Subject: [Archivesspace_Users_Group] Import EAD via the API? In-Reply-To: References: Message-ID: <1428349840325.99287@lyrasis.org> Hi Dallas, What you describe is along the lines of what I had in mind with this plugin: https://github.com/mark-cooper/aspace-jsonmodel-from-format It adds an endpoint to get an AS jsonmodel from a "raw" file (like an EAD xml file). You can then fire it back at the imports endpoint to get it into ArchivesSpace. In terms of validation, if the jsonmodel conversion fails then you wouldn't have anything to import and can log that. Use your preferred scripting language to do something like the examples for batch imports (in effect scripting a file by file import, rather than pushing a job which may fail part way through). However, I haven't tested it with 1.2.0 so it may not be compatible with that version as is (but is probably ok). Best, Mark Mark Cooper Technical Lead, Hosting and Support LYRASIS email: mark.cooper at lyrasis.org skype: mark_c_cooper? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dallas Pillen Sent: Monday, April 6, 2015 12:08 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Import EAD via the API? Hello all, I was curious if anyone has had any success starting EAD import jobs via the API? I was thinking this could be done using POST /repositories/:repo_id/jobs_with_files described here: http://archivesspace.github.io/archivesspace/doc/file.API.html#post-repositoriesrepoidjobswithfiles However, I am not entirely sure how the job and file parameters should be sent in the POST request, and I haven't seen anyone ask this question before or give an example of how it might work. I've tried sending the POST request several different ways and each time I am met with: {"error":{"job":["Parameter required but no value provided"],"files":["Parameter required but no value provided"]}}. I suppose it's worth mentioning that the reason I want to do this is that, at some point, we will be importing several thousand EADs into ArchivesSpace. We're doing a lot of preliminary work to make our EADs import successfully, but know there will likely be some that will fail. Right now, the only way to do a batch import of EADs is to do a batch as a single import job. If one EAD in that job has an error, the entire job fails. For that reason, I would like to be able to import each EAD as a separate job so that the EADs that will import successfully will do so without being impacted by the EADs with errors. However, starting several thousand individual import jobs would be very tedious, and I'm looking for a way to automate that process. If anyone else has come up with any creative solutions or knows of a better way to do that than the API, I would be very interested to know. The end goal would be to have a script that would batch start the import jobs, get the ID for each job, check up on the jobs every so often and, once there are no longer any active jobs, output some information about each of the jobs that failed. I've figured out how to do most of that using the API, but I'm stumped on how to get the whole process started. Thanks! Dallas -- Dallas Pillen Project Archivist [https://webapps.lsa.umich.edu/dean/lsa_emails/bentley-sig-em.png] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Mon Apr 6 16:35:13 2015 From: sdm7g at virginia.edu (Steven Majewski) Date: Mon, 6 Apr 2015 16:35:13 -0400 Subject: [Archivesspace_Users_Group] Import EAD via the API? In-Reply-To: References: Message-ID: What I had been doing was running EADConverter locally on a batch of files, saving the JSON output if successful, and posting those JSON files to http://archivesspace.github.io/archivesspace/doc/file.API.html#post-repositoriesrepoidbatchimports ( This two stage process was also very useful in earlier versions when the error reporting was missing the context: ArchivesSpace would tell you what was missing, but it didn?t point to where it was missing from. It was possible to inspect the JSON and look for the null or missing value. ) You want to: converter = EADConverter.new( eadxml ) converter.run and then do something (move, copy or sent directly to batch_imports API) with: converter.get_output_path and if you wrap it in a begin/rescue block, you can catch and report the errors. I?ve experimented with a couple of variations on the error catching and processing. For example, if you move the JSON output in the ensure clause ( begin/rescue/ensure ), you can save the JSON to inspect even if it?s not complete enough to successfully import with /batch_imports, but you might not want to mix ?good? and ?bad? JSON in your output files. More recently, I?ve been experimenting with using an alternate EAD importer with looser schema validation rules. One problem with importing thousands of EAD files by this batch method is that we have had problems with ?namespace pollution? of the controlled vocab lists for extents and containers. These values are controlled from the webapp and editor, but importing from EAD adds to the values in the database. If you import a few EAD files at a time, it?s not difficult to merge and clean up these values, but importing several thousand EAD files that aren?t very controlled for those values led to an explosion that makes the drop down lists of those values unusable. See a previous message about this: http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2015-March/001216.html ? Steve Majewski / UVA Alderman Library On Apr 6, 2015, at 3:08 PM, Dallas Pillen wrote: > Hello all, > > I was curious if anyone has had any success starting EAD import jobs via the API? > > I was thinking this could be done using POST /repositories/:repo_id/jobs_with_files described here: http://archivesspace.github.io/archivesspace/doc/file.API.html#post-repositoriesrepoidjobswithfiles > > However, I am not entirely sure how the job and file parameters should be sent in the POST request, and I haven't seen anyone ask this question before or give an example of how it might work. I've tried sending the POST request several different ways and each time I am met with: {"error":{"job":["Parameter required but no value provided"],"files":["Parameter required but no value provided"]}}. > > I suppose it's worth mentioning that the reason I want to do this is that, at some point, we will be importing several thousand EADs into ArchivesSpace. We're doing a lot of preliminary work to make our EADs import successfully, but know there will likely be some that will fail. Right now, the only way to do a batch import of EADs is to do a batch as a single import job. If one EAD in that job has an error, the entire job fails. For that reason, I would like to be able to import each EAD as a separate job so that the EADs that will import successfully will do so without being impacted by the EADs with errors. However, starting several thousand individual import jobs would be very tedious, and I'm looking for a way to automate that process. If anyone else has come up with any creative solutions or knows of a better way to do that than the API, I would be very interested to know. > > The end goal would be to have a script that would batch start the import jobs, get the ID for each job, check up on the jobs every so often and, once there are no longer any active jobs, output some information about each of the jobs that failed. I've figured out how to do most of that using the API, but I'm stumped on how to get the whole process started. > > Thanks! > > Dallas > > > -- > Dallas Pillen > Project Archivist > > > Bentley Historical Library > 1150 Beal Avenue > Ann Arbor, Michigan 48109-2113 > 734.647.3559 > Twitter Facebook > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: From mark.custer at yale.edu Mon Apr 6 16:35:37 2015 From: mark.custer at yale.edu (Custer, Mark) Date: Mon, 6 Apr 2015 20:35:37 +0000 Subject: [Archivesspace_Users_Group] Schematron file to test for ASpace compatibility of EAD files prior to import Message-ID: All, In case anyone might find this useful, I just started work on a Schematron file, https://github.com/fordmadox/schematrons/blob/master/ArchivesSpace-EAD-validator.sch, to test for common EAD incompatibilities with the ASpace JSON model. For instance, this file will make sure that a yet-to-be ArchivesSpace resource record has the following, required pieces of data, none of which are required by the EAD 2002 schema: ? @level attribute ? title ? date ? identifier (or archdesc/did/unitid, in EAD-speak) ? extent statement (though I still have to add a rule that will enforce that the resource-level extent statement has both an extent number and an extent type) Honestly, I haven?t really tested ASpace?s EAD importer just yet, but if I were batch importing EAD files, I?d imagine that I?d do the following: 1. validate the files according to the EAD 2002 schema 2. validate the files according to a schematron file (or something similar) 3. If the files failed either validation step, then I would look at the reported errors, including file names and line numbers, to see what needs to be fixed (or, better yet, automate everything so that I could tie specific fixes to specific errors; e.g., if there?s no resource-level identifier in the EAD file, then assign an identifier based on the current timestamp and send it off for import.) 4. Upload the valid files 5. Repeat All of that said, I?ve never written a schematron file before, so at this point I just wanted to get a rough draft of most of the ASpace requirements. So far, this file is not exhaustive (for instance, it won?t report that you?ve put more than 255 characters in your container_1 indicator, if you?ve done such a thing!), but all of those rules could be added pretty easily. Is anyone else already doing something like this? I seem to remember that some folks had scripts for updating their EAD files to be compliant with ASpace prior to import, but I wasn?t sure if anyone had already created their own validation scenarios. All my best, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL: From mang.sun at rice.edu Mon Apr 6 18:11:26 2015 From: mang.sun at rice.edu (Mang Sun) Date: Mon, 06 Apr 2015 17:11:26 -0500 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: References: <551D6503.8000500@rice.edu> <5522BEFE.6090502@rice.edu> Message-ID: <5523048E.9060801@rice.edu> By the way, under which OS is your AS 1.2 running ? Mine is Redhat 6.4. Mang On 4/6/2015 12:47 PM, Brad Westbrook wrote: > > Hi, Mang > > I just successfully tested the public formats plugin for all three > options. I tested it in a localhost install using the embedded Derby > database. > > Brad W. > > *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org > [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] *On > Behalf Of *Mang Sun > *Sent:* Monday, April 06, 2015 1:15 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] The ead_pdf link generated > by plugin public_formats_resource_links does not work with AS 1.2 > > Can somebody or the development team confirm whether the > public_formats_resource_links plugin still works with AS 1.2? > > Mang Sun > Rice U. > > On 4/2/2015 10:49 AM, Mang Sun wrote: > > When clicking the ead_pdf link turned on by the > public_formats_resource_links plugin does not work with AS 1.2 > throwing the error message as follows. -Mang Sun Rice U. > > > EOFError in PublicFormatsController#generate > > |Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public| > > > Request > > *Parameters*: > > {"repo_id"=>"2", > > "type"=>"resources", > > "id"=>"116", > > "format"=>"ead_pdf"} > > Show session dump > > > _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" > > session_id: "c419289cb412f46af571004e4b0c0830" > > Show env dump > > > GATEWAY_INTERFACE: "CGI/1.2" > > HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" > > HTTP_ACCEPT_ENCODING: "gzip, deflate" > > HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" > > REMOTE_ADDR: "10.xx.xx.xx" > > SERVER_NAME: "10.xx.22.xx" > > SERVER_PROTOCOL: "HTTP/1.1" > > > Response > > *Headers*: > > None > > ----------------- > > The Full trace is pasted as below. > > > > |org/jruby/RubyIO.java:2858:in `read_nonblock'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request'| > > |org/jruby/RubyKernel.java:1270:in `catch'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request'| > > |/opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle'| > > |/opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate'| > > |actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action'| > > |actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action'| > > |actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action'| > > |actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks'| > > |actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action'| > > |actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action'| > > |actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action'| > > |activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument'| > > |activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument'| > > |activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument'| > > |activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument'| > > |actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action'| > > |actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action'| > > |actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process'| > > |actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process'| > > |actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch'| > > |actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch'| > > |actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action'| > > |org/jruby/RubyProc.java:271:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch'| > > |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call'| > > |journey (1.0.4) lib/journey/router.rb:68:in `call'| > > |org/jruby/RubyArray.java:1613:in `each'| > > |journey (1.0.4) lib/journey/router.rb:56:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call'| > > |rack (1.4.5) lib/rack/etag.rb:23:in `call'| > > |rack (1.4.5) lib/rack/conditionalget.rb:25:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call'| > > |rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context'| > > |rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'| > > |railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app'| > > |railties (3.2.19) lib/rails/rack/logger.rb:16:in `call'| > > |activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged'| > > |railties (3.2.19) lib/rails/rack/logger.rb:16:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call'| > > |rack (1.4.5) lib/rack/methodoverride.rb:21:in `call'| > > |rack (1.4.5) lib/rack/runtime.rb:17:in `call'| > > |activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call'| > > |rack (1.4.5) lib/rack/lock.rb:15:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call'| > > |railties (3.2.19) lib/rails/engine.rb:484:in `call'| > > |railties (3.2.19) lib/rails/application.rb:231:in `call'| > > |rack (1.4.5) lib/rack/content_length.rb:14:in `call'| > > |railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call'| > > |puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request'| > > |puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request'| > > |puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client'| > > |puma-2.8.2 (java) lib/puma/server.rb:254:in `run'| > > |org/jruby/RubyProc.java:271:in `call'| > > |puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread'| > > > > > > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianjhoffman at gmail.com Mon Apr 6 21:11:37 2015 From: brianjhoffman at gmail.com (brian) Date: Mon, 06 Apr 2015 21:11:37 -0400 Subject: [Archivesspace_Users_Group] Accession CSV Subject Import Message-ID: <8heo94nsml7lmaxk4k2o66fi.1428369097757@email.android.com> Hi Maura, Here's the base converter file for accession csv. https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/accession_converter.rb Brian Sent from my T-Mobile 4G LTE Device
-------- Original message --------
From: Maura Carbone
Date:04/06/2015 3:35 PM (GMT-05:00)
To: Archivesspace Users Group
Cc:
Subject: Re: [Archivesspace_Users_Group] Accession CSV Subject Import
Hi Chris, Any progress on that example? I actually tried to work on it myself, but I'm not entirely sure which files need to be altered (aside from accession_converter). Ideally, I want to be able to import multiple subjects and multiple agents -- I was hoping to copy the date setup (where there are multiple dates date1 date2 etc.) but I haven't found the file where the terms (such as date_label_1) are mapped to the date object (and so on for subject and agents etc.) Thanks! Maura On Tue, Mar 31, 2015 at 4:03 PM, Maura Carbone wrote: What I was doing was: subject_source,subject_term_type,subject_term,subject_source,subject_term_type,subject_term, Unspecified ingested source,Topical,Pepperoni,Unspecified ingested source,Topical,Cheese. Then only Cheese gets created and imported. Yeah, and I can take a look at how the importer works now as well, I just wasn't sure if it was a known issue, or if there was a specific reason for it. Thanks! Maura On Tue, Mar 31, 2015 at 3:29 PM, Chris Fitzpatrick wrote: Hi Maura, So, you're just adding more subject columns to the CSV? Yes, what you describe about overwriting is exactly what's happening...the CSV importer only allows for one subject per row. I have a plugin example I started working on last week to show how to tweak the CSV importer...I'll try and finish that up tomorrow and send it out for people to have a look... b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Maura Carbone Sent: Tuesday, March 31, 2015 7:06 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Accession CSV Subject Import Hi all, I've been working on importing accessions with CSV files, but I've noticed that on import only one subject ever gets brought in (the last one). Is this a bug, or just a current limitation? I'm not getting an error, it just appears that the subject field keeps being over-written until the last subject, then imported. Thanks, Maura -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Tue Apr 7 07:15:51 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Tue, 7 Apr 2015 11:15:51 +0000 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: <5523048E.9060801@rice.edu> References: <551D6503.8000500@rice.edu> <5522BEFE.6090502@rice.edu> <5523048E.9060801@rice.edu> Message-ID: Windows 7, Mang. Brad From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mang Sun Sent: Monday, April 06, 2015 6:11 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 By the way, under which OS is your AS 1.2 running ? Mine is Redhat 6.4. Mang On 4/6/2015 12:47 PM, Brad Westbrook wrote: Hi, Mang I just successfully tested the public formats plugin for all three options. I tested it in a localhost install using the embedded Derby database. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mang Sun Sent: Monday, April 06, 2015 1:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 Can somebody or the development team confirm whether the public_formats_resource_links plugin still works with AS 1.2? Mang Sun Rice U. On 4/2/2015 10:49 AM, Mang Sun wrote: When clicking the ead_pdf link turned on by the public_formats_resource_links plugin does not work with AS 1.2 throwing the error message as follows. -Mang Sun Rice U. EOFError in PublicFormatsController#generate Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public Request Parameters: {"repo_id"=>"2", "type"=>"resources", "id"=>"116", "format"=>"ead_pdf"} Show session dump _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" session_id: "c419289cb412f46af571004e4b0c0830" Show env dump GATEWAY_INTERFACE: "CGI/1.2" HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" HTTP_ACCEPT_ENCODING: "gzip, deflate" HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" REMOTE_ADDR: "10.xx.xx.xx" SERVER_NAME: "10.xx.22.xx" SERVER_PROTOCOL: "HTTP/1.1" Response Headers: None ----------------- The Full trace is pasted as below. org/jruby/RubyIO.java:2858:in `read_nonblock' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request' org/jruby/RubyKernel.java:1270:in `catch' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request' /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle' /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate' actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action' actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action' actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action' actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action' activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action' actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action' actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action' activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument' activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument' activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action' actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action' actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process' actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process' actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch' actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch' actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action' org/jruby/RubyProc.java:271:in `call' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call' journey (1.0.4) lib/journey/router.rb:68:in `call' org/jruby/RubyArray.java:1613:in `each' journey (1.0.4) lib/journey/router.rb:56:in `call' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call' rack (1.4.5) lib/rack/etag.rb:23:in `call' rack (1.4.5) lib/rack/conditionalget.rb:25:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call' rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context' rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call' activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app' railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged' railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call' rack (1.4.5) lib/rack/methodoverride.rb:21:in `call' rack (1.4.5) lib/rack/runtime.rb:17:in `call' activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call' rack (1.4.5) lib/rack/lock.rb:15:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call' railties (3.2.19) lib/rails/engine.rb:484:in `call' railties (3.2.19) lib/rails/application.rb:231:in `call' rack (1.4.5) lib/rack/content_length.rb:14:in `call' railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call' puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request' puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request' puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client' puma-2.8.2 (java) lib/puma/server.rb:254:in `run' org/jruby/RubyProc.java:271:in `call' puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread' _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Tue Apr 7 10:45:06 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Tue, 7 Apr 2015 10:45:06 -0400 Subject: [Archivesspace_Users_Group] Accession CSV Subject Import In-Reply-To: <8heo94nsml7lmaxk4k2o66fi.1428369097757@email.android.com> References: <8heo94nsml7lmaxk4k2o66fi.1428369097757@email.android.com> Message-ID: Hi Brian, I found that one all right, but is there another file that would have to be edited? Looking at that file I can't see where the 'labels' are linked to the data types, so I was assuming there was another file that does that. For example, the first half has labels for date_1: 'date_1_label' => 'date_1.label', 'date_1_expression' => 'date_1.expression', 'date_1_begin' => 'date_1.begin', 'date_1_end' => 'date_1.end', 'date_1_type' => 'date_1.date_type', and then the date object creator is: :date_1 => { :record_type => :date, :defaults => date_defaults, :on_row_complete => Proc.new { |queue, date| queue.select {|obj| obj.class.record_type == 'accession'}.each do |accession| accession.dates << date end } so I thought there must be a file mapping the date_1 labels to the date object fields in the schema? Thanks, Maura On Mon, Apr 6, 2015 at 9:11 PM, brian wrote: > Hi Maura, > > Here's the base converter file for accession csv. > > > https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/accession_converter.rb > > > Brian > > > > Sent from my T-Mobile 4G LTE Device > > > -------- Original message -------- > From: Maura Carbone > Date:04/06/2015 3:35 PM (GMT-05:00) > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > Cc: > Subject: Re: [Archivesspace_Users_Group] Accession CSV Subject Import > > Hi Chris, > Any progress on that example? I actually tried to work on it myself, but > I'm not entirely sure which files need to be altered (aside from > accession_converter). Ideally, I want to be able to import multiple > subjects and multiple agents -- I was hoping to copy the date setup (where > there are multiple dates date1 date2 etc.) but I haven't found the file > where the terms (such as date_label_1) are mapped to the date object (and > so on for subject and agents etc.) > > Thanks! > Maura > > On Tue, Mar 31, 2015 at 4:03 PM, Maura Carbone > wrote: > >> What I was doing was: >> subject_source,subject_term_type,subject_term,subject_source,subject_term_type,subject_term, Unspecified >> ingested source,Topical,Pepperoni,Unspecified ingested >> source,Topical,Cheese. Then only Cheese gets created and imported. >> >> Yeah, and I can take a look at how the importer works now as well, I just >> wasn't sure if it was a known issue, or if there was a specific reason for >> it. >> >> Thanks! >> Maura >> >> On Tue, Mar 31, 2015 at 3:29 PM, Chris Fitzpatrick < >> Chris.Fitzpatrick at lyrasis.org> wrote: >> >>> Hi Maura, >>> >>> >>> So, you're just adding more subject columns to the CSV? Yes, what you >>> describe about overwriting is exactly what's happening...the CSV importer >>> only allows for one subject per row. >>> >>> >>> I have a plugin example I started working on last week to show how to >>> tweak the CSV importer...I'll try and finish that up tomorrow and send it >>> out for people to have a look... >>> >>> >>> b,chris. >>> >>> >>> Chris Fitzpatrick | Developer, ArchivesSpace >>> Skype: chrisfitzpat | Phone: 918.236.6048 >>> http://archivesspace.org/ >>> ------------------------------ >>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >>> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >>> Maura Carbone >>> *Sent:* Tuesday, March 31, 2015 7:06 PM >>> *To:* Archivesspace Users Group >>> *Subject:* [Archivesspace_Users_Group] Accession CSV Subject Import >>> >>> Hi all, >>> I've been working on importing accessions with CSV files, but I've >>> noticed that on import only one subject ever gets brought in (the last >>> one). Is this a bug, or just a current limitation? I'm not getting an >>> error, it just appears that the subject field keeps being over-written >>> until the last subject, then imported. >>> >>> Thanks, >>> Maura >>> >>> -- >>> Maura Carbone >>> Digital Initiatives Librarian >>> Brandeis University >>> Library and Technology Services >>> (781) 736-4659 >>> 415 South Street, (MS 017/P.O. Box 549110) >>> Waltham, MA 02454-9110 >>> email: mauraa at brandeis.edu >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >> >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> > > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From djpillen at umich.edu Tue Apr 7 12:09:08 2015 From: djpillen at umich.edu (Dallas Pillen) Date: Tue, 7 Apr 2015 12:09:08 -0400 Subject: [Archivesspace_Users_Group] Import EAD via the API? In-Reply-To: References: Message-ID: Thanks for the replies! Noah: we have talked about first importing our EADs into AT and then migrating to ArchivesSpace, but we're trying to do a lot of preliminary data cleanup and have made some modifications to the AS EAD importer in an attempt to make our legacy data as clean and AS-friendly as possible before migrating. Ideally, we'll account for most of the errors we've identified during our EAD cleanup and won't need to rely on the more forgiving nature of the AT importer. But it's something we're open to taking a look at at some point, at least as a supplemental error discovery/identification tool. Mark and Steve: Something along those lines just might work. As part of our EAD cleanup we are going through our extents, subjects, and other potential sources of namespace pollution so those sorts of issues will be controlled for in our EADs before our actual migration to AS. This should also make a pre-migration conversion to the AS JSONModel more feasible since, when we are ready to do so, our EADs will theoretically convert to the AS JSONModel with minimal errors. Mark, I tried your plugin on a batch of EADs and there were a few cases in which the conversion failed due to something like the following: (UndefinedConversionError) ""\xC3\xA9"" from UTF-8 to US-ASCII The EAD that threw this particular error has some '?' characters that the AS EAD converter imports without issue. Any thoughts on that? Other than that, converting our EADs to JSON and then bulk importing each of the JSON files would essentially accomplish what I was thinking of doing by importing EAD through the API. Still, like Noah, I'd still be interested in knowing if anyone else has figured out how to start EAD import jobs through the API, partially out of curiosity and also to be able to compare some of these potential conversion/import strategies. Thanks again for all the helpful suggestion! Dallas On Mon, Apr 6, 2015 at 4:35 PM, Steven Majewski wrote: > > What I had been doing was running EADConverter locally on a batch of > files, saving the JSON > output if successful, and posting those JSON files to > > http://archivesspace.github.io/archivesspace/doc/file.API.html#post-repositoriesrepoidbatchimports > > ( This two stage process was also very useful in earlier versions when the > error reporting > was missing the context: ArchivesSpace would tell you what was missing, > but it didn?t point > to where it was missing from. It was possible to inspect the JSON and > look for the null or > missing value. ) > > You want to: > > converter = EADConverter.new( eadxml ) > converter.run > and then do something (move, copy or sent directly to batch_imports API) > with: > converter.get_output_path > > and if you wrap it in a begin/rescue block, you can catch and report the > errors. > > > I?ve experimented with a couple of variations on the error catching and > processing. > For example, if you move the JSON output in the ensure clause ( > begin/rescue/ensure ), > you can save the JSON to inspect even if it?s not complete enough to > successfully > import with /batch_imports, but you might not want to mix ?good? and ?bad? > JSON in > your output files. > > More recently, I?ve been experimenting with using an alternate EAD > importer with > looser schema validation rules. > > One problem with importing thousands of EAD files by this batch method is > that > we have had problems with ?namespace pollution? of the controlled vocab > lists > for extents and containers. These values are controlled from the webapp > and editor, > but importing from EAD adds to the values in the database. If you import a > few > EAD files at a time, it?s not difficult to merge and clean up these > values, but > importing several thousand EAD files that aren?t very controlled for those > values > led to an explosion that makes the drop down lists of those values > unusable. > > See a previous message about this: > > http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2015-March/001216.html > > > > ? Steve Majewski / UVA Alderman Library > > > On Apr 6, 2015, at 3:08 PM, Dallas Pillen wrote: > > Hello all, > > I was curious if anyone has had any success starting EAD import jobs via > the API? > > I was thinking this could be done using POST > /repositories/:repo_id/jobs_with_files described here: > http://archivesspace.github.io/archivesspace/doc/file.API.html#post-repositoriesrepoidjobswithfiles > > However, I am not entirely sure how the job and file parameters should be > sent in the POST request, and I haven't seen anyone ask this question > before or give an example of how it might work. I've tried sending the POST > request several different ways and each time I am met with: > {"error":{"job":["Parameter required but no value > provided"],"files":["Parameter required but no value provided"]}}. > > I suppose it's worth mentioning that the reason I want to do this is that, > at some point, we will be importing several thousand EADs into > ArchivesSpace. We're doing a lot of preliminary work to make our EADs > import successfully, but know there will likely be some that will fail. > Right now, the only way to do a batch import of EADs is to do a batch as a > single import job. If one EAD in that job has an error, the entire job > fails. For that reason, I would like to be able to import each EAD as a > separate job so that the EADs that will import successfully will do so > without being impacted by the EADs with errors. However, starting several > thousand individual import jobs would be very tedious, and I'm looking for > a way to automate that process. If anyone else has come up with any > creative solutions or knows of a better way to do that than the API, I > would be very interested to know. > > The end goal would be to have a script that would batch start the import > jobs, get the ID for each job, check up on the jobs every so often and, > once there are no longer any active jobs, output some information about > each of the jobs that failed. I've figured out how to do most of that using > the API, but I'm stumped on how to get the whole process started. > > Thanks! > > Dallas > > > -- > > *Dallas Pillen*Project Archivist > > > Bentley Historical Library > 1150 Beal Avenue > Ann Arbor, Michigan 48109-2113 > 734.647.3559 > Twitter Facebook > > _______________________________________________ > 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 > > -- *Dallas Pillen*Project Archivist Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From mang.sun at rice.edu Tue Apr 7 12:26:28 2015 From: mang.sun at rice.edu (Mang Sun) Date: Tue, 07 Apr 2015 11:26:28 -0500 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: References: <551D6503.8000500@rice.edu> <5522BEFE.6090502@rice.edu> <5523048E.9060801@rice.edu> Message-ID: <55240534.1010502@rice.edu> Thank you again Brad. I also have tested this version on MAC OS X and still see the same issue with the ead_pdf link of this plugin. Mang On 4/7/2015 6:15 AM, Brad Westbrook wrote: > > Windows 7, Mang. > > Brad > > *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org > [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] *On > Behalf Of *Mang Sun > *Sent:* Monday, April 06, 2015 6:11 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] The ead_pdf link generated > by plugin public_formats_resource_links does not work with AS 1.2 > > By the way, under which OS is your AS 1.2 running ? Mine is Redhat 6.4. > > Mang > > On 4/6/2015 12:47 PM, Brad Westbrook wrote: > > Hi, Mang > > I just successfully tested the public formats plugin for all three > options. I tested it in a localhost install using the embedded > Derby database. > > Brad W. > > *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org > > [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] > *On Behalf Of *Mang Sun > *Sent:* Monday, April 06, 2015 1:15 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] The ead_pdf link > generated by plugin public_formats_resource_links does not work > with AS 1.2 > > Can somebody or the development team confirm whether the > public_formats_resource_links plugin still works with AS 1.2? > > Mang Sun > Rice U. > > On 4/2/2015 10:49 AM, Mang Sun wrote: > > When clicking the ead_pdf link turned on by the > public_formats_resource_links plugin does not work with AS 1.2 > throwing the error message as follows. -Mang Sun Rice U. > > > EOFError in PublicFormatsController#generate > > |Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public| > > > Request > > *Parameters*: > > {"repo_id"=>"2", > > "type"=>"resources", > > "id"=>"116", > > "format"=>"ead_pdf"} > > Show session dump > > > _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" > > session_id: "c419289cb412f46af571004e4b0c0830" > > Show env dump > > > GATEWAY_INTERFACE: "CGI/1.2" > > HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" > > HTTP_ACCEPT_ENCODING: "gzip, deflate" > > HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" > > REMOTE_ADDR: "10.xx.xx.xx" > > SERVER_NAME: "10.xx.22.xx" > > SERVER_PROTOCOL: "HTTP/1.1" > > > Response > > *Headers*: > > None > > ----------------- > > The Full trace is pasted as below. > > > > |org/jruby/RubyIO.java:2858:in `read_nonblock'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request'| > > |org/jruby/RubyKernel.java:1270:in `catch'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start'| > > |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request'| > > |/opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle'| > > |/opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate'| > > |actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action'| > > |actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action'| > > |actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action'| > > |actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks'| > > |actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action'| > > |actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action'| > > |actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action'| > > |activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument'| > > |activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument'| > > |activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument'| > > |activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument'| > > |actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action'| > > |actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action'| > > |actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process'| > > |actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process'| > > |actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch'| > > |actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch'| > > |actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action'| > > |org/jruby/RubyProc.java:271:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch'| > > |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call'| > > |journey (1.0.4) lib/journey/router.rb:68:in `call'| > > |org/jruby/RubyArray.java:1613:in `each'| > > |journey (1.0.4) lib/journey/router.rb:56:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call'| > > |rack (1.4.5) lib/rack/etag.rb:23:in `call'| > > |rack (1.4.5) lib/rack/conditionalget.rb:25:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call'| > > |rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context'| > > |rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks'| > > |activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'| > > |railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app'| > > |railties (3.2.19) lib/rails/rack/logger.rb:16:in `call'| > > |activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged'| > > |railties (3.2.19) lib/rails/rack/logger.rb:16:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call'| > > |rack (1.4.5) lib/rack/methodoverride.rb:21:in `call'| > > |rack (1.4.5) lib/rack/runtime.rb:17:in `call'| > > |activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call'| > > |rack (1.4.5) lib/rack/lock.rb:15:in `call'| > > |actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call'| > > |railties (3.2.19) lib/rails/engine.rb:484:in `call'| > > |railties (3.2.19) lib/rails/application.rb:231:in `call'| > > |rack (1.4.5) lib/rack/content_length.rb:14:in `call'| > > |railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call'| > > |puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request'| > > |puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request'| > > |puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client'| > > |puma-2.8.2 (java) lib/puma/server.rb:254:in `run'| > > |org/jruby/RubyProc.java:271:in `call'| > > |puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread'| > > > > > > > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > _______________________________________________ > > Archivesspace_Users_Group mailing list > > Archivesspace_Users_Group at lyralists.lyrasis.org > > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mang.sun at rice.edu Tue Apr 7 12:36:09 2015 From: mang.sun at rice.edu (Mang Sun) Date: Tue, 07 Apr 2015 11:36:09 -0500 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: <1427746077682.56800@lyrasis.org> References: <1427746077682.56800@lyrasis.org> Message-ID: <55240779.6020209@rice.edu> Hi Christ, Though I posted this question as an independent thread, I figure I'd better directly draw your attention to this issue. The issue is with the ead_pdf link of plugin aspace-public-formats of AS 1.2.0 . When this link is clicked, the following error message will be thrown. I run into the same issue on REDHAT 6.4 and OS X, but Brad does not have any problem with this plugin on Windows 7. -Mang Sun, Rice U. EOFError in PublicFormatsController#generate End of file reached |Rails.root: /Users/ms20/Applications/archivesspace/public| Application Trace | Framework Trace | Full Trace || Request *Parameters*: {"repo_id"=>"2", "type"=>"resources", "id"=>"1", "format"=>"ead_pdf"} Show session dump Show env dump Response *Headers*: None On 3/30/2015 3:07 PM, Chris Fitzpatrick wrote: > The ArchivesSpace team is happy to release version v1.2.0 > . > > Please see the technical documentation > for > information on how to upgrade your ArchivesSpace installs. > > Please see the release page > for a > listing of all the new features and bug fixes included in this release. > > Of particular note: This release includes an upgrade to Bootstrap 3 > for the staff interface. This version has > significant changes to HTML, CSS, and Javascript components in the > staff UI, so any plugins or custom templates will have to be modified > to work with Bootstrap 3. > > Also included in this release is a Find-And-Replace background job, > which allows users to bulk edit records. As this is a currently a > beta-feature, it is recommended that users backup their database > frequently if using this feature. > > Thanks to all the volunteers on the ArchivesSpace User Advisory and > Technical Advisory Councils, who are vital to keeping ArchivesSpace > development on track. > Please let us know if you have any questions, comments, or concerns. > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmg17 at psu.edu Tue Apr 7 12:57:09 2015 From: bmg17 at psu.edu (Ben Goldman) Date: Tue, 7 Apr 2015 12:57:09 -0400 (EDT) Subject: [Archivesspace_Users_Group] digital object import questions In-Reply-To: References: <5509AD61.3030202@uga.edu> <5509B9E9.6030203@uga.edu> <713009522.595649.1426772526934.JavaMail.zimbra@psu.edu> <1037746823.671088.1426779552408.JavaMail.zimbra@psu.edu> Message-ID: <553120613.199809.1428425829868.JavaMail.zimbra@psu.edu> Hello everyone, I'm testing the digital object import option in ASpace and am encountering an issue. I am trying to import a group of digital objects and make them components of a parent digital object record. I've set this up according to the import mappings, which seem to indicate I should use the parent digital_object_id for the each row's digital_object_id, then use digital_object_component_id for the component level identifier values. Even so, I get an error on import (see attached screenshot). More generally, I am wondering if there is a way to relate these digital objects with archival objects on ingest. A use case might be we digitize 100 audio cassettes related to a collection, and then import a modified metadata spreadsheet (somewhat unsatisfying, obviously) to create digital objects. I don't think it will be feasible for us to move through these 100 new digital objects one by one attaching them to archival objects. By the way, we are still in v1.1.2, so if the error noted is addressed in 1.2, great! Best, 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 -------------- A non-text attachment was scrubbed... Name: Sheet1.csv Type: text/csv Size: 432 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2015-04-07 at 12.52.31 PM.png Type: image/png Size: 11347 bytes Desc: not available URL: From brianjhoffman at gmail.com Tue Apr 7 13:04:42 2015 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Tue, 7 Apr 2015 13:04:42 -0400 Subject: [Archivesspace_Users_Group] Accession CSV Subject Import In-Reply-To: References: <8heo94nsml7lmaxk4k2o66fi.1428369097757@email.android.com> Message-ID: <104689F7-34DD-4270-8B7D-4FA79E020368@gmail.com> Hi Maura, No, there?s nothing else. Generally the keys in the callbacks section (:date_1 => etc) are used to tie things together with the schema. Where there are multiple objects created per row, there?s an optional :record_type key in the callback config that does the mapping (:record_type => :date). Does that make sense? Brian On Apr 7, 2015, at 10:45 AM, Maura Carbone wrote: > Hi Brian, > I found that one all right, but is there another file that would have to be edited? Looking at that file I can't see where the 'labels' are linked to the data types, so I was assuming there was another file that does that. For example, the first half has labels for date_1: > > 'date_1_label' => 'date_1.label', > 'date_1_expression' => 'date_1.expression', > 'date_1_begin' => 'date_1.begin', > 'date_1_end' => 'date_1.end', > 'date_1_type' => 'date_1.date_type', > > and then the date object creator is: > > :date_1 => { > :record_type => :date, > :defaults => date_defaults, > :on_row_complete => Proc.new { |queue, date| > queue.select {|obj| obj.class.record_type == 'accession'}.each do |accession| > accession.dates << date > end > } > > so I thought there must be a file mapping the date_1 labels to the date object fields in the schema? > > > Thanks, > Maura > > On Mon, Apr 6, 2015 at 9:11 PM, brian wrote: > Hi Maura, > > Here's the base converter file for accession csv. > > https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/accession_converter.rb > > > Brian > > > > Sent from my T-Mobile 4G LTE Device > > > -------- Original message -------- > From: Maura Carbone > Date:04/06/2015 3:35 PM (GMT-05:00) > To: Archivesspace Users Group > Cc: > Subject: Re: [Archivesspace_Users_Group] Accession CSV Subject Import > > Hi Chris, > Any progress on that example? I actually tried to work on it myself, but I'm not entirely sure which files need to be altered (aside from accession_converter). Ideally, I want to be able to import multiple subjects and multiple agents -- I was hoping to copy the date setup (where there are multiple dates date1 date2 etc.) but I haven't found the file where the terms (such as date_label_1) are mapped to the date object (and so on for subject and agents etc.) > > Thanks! > Maura > > On Tue, Mar 31, 2015 at 4:03 PM, Maura Carbone wrote: > What I was doing was: > subject_source,subject_term_type,subject_term,subject_source,subject_term_type,subject_term, Unspecified ingested source,Topical,Pepperoni,Unspecified ingested source,Topical,Cheese. Then only Cheese gets created and imported. > > Yeah, and I can take a look at how the importer works now as well, I just wasn't sure if it was a known issue, or if there was a specific reason for it. > > Thanks! > Maura > > On Tue, Mar 31, 2015 at 3:29 PM, Chris Fitzpatrick wrote: > Hi Maura, > > > So, you're just adding more subject columns to the CSV? Yes, what you describe about overwriting is exactly what's happening...the CSV importer only allows for one subject per row. > > > I have a plugin example I started working on last week to show how to tweak the CSV importer...I'll try and finish that up tomorrow and send it out for people to have a look... > > > b,chris. > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Maura Carbone > Sent: Tuesday, March 31, 2015 7:06 PM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] Accession CSV Subject Import > > Hi all, > I've been working on importing accessions with CSV files, but I've noticed that on import only one subject ever gets brought in (the last one). Is this a bug, or just a current limitation? I'm not getting an error, it just appears that the subject field keeps being over-written until the last subject, then imported. > > Thanks, > Maura > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Tue Apr 7 13:07:02 2015 From: sdm7g at virginia.edu (Steven Majewski) Date: Tue, 7 Apr 2015 13:07:02 -0400 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: <55240779.6020209@rice.edu> References: <1427746077682.56800@lyrasis.org> <55240779.6020209@rice.edu> Message-ID: I?m not seeing any problems on OSX. Do you get any errors from the EAD (xml) export on the same page ? ? Steve Majewski / UVA Alderman Library On Apr 7, 2015, at 12:36 PM, Mang Sun wrote: > Hi Christ, > > Though I posted this question as an independent thread, I figure I'd better directly draw your attention to this issue. > The issue is with the ead_pdf link of plugin aspace-public-formats of AS 1.2.0 . When this link is clicked, the following error message will be thrown. > I run into the same issue on REDHAT 6.4 and OS X, but Brad does not have any problem with this plugin on Windows 7. -Mang Sun, Rice U. > EOFError in PublicFormatsController#generate > > End of file reached > Rails.root: /Users/ms20/Applications/archivesspace/public > Application Trace | Framework Trace | Full Trace > Request > > Parameters: > {"repo_id"=>"2", > "type"=>"resources", > "id"=>"1", > "format"=>"ead_pdf"} > Show session dump > Show env dump > Response > > Headers: > None > > > > On 3/30/2015 3:07 PM, Chris Fitzpatrick wrote: >> The ArchivesSpace team is happy to release version v1.2.0. >> >> Please see the technical documentation for information on how to upgrade your ArchivesSpace installs. >> >> Please see the release page for a listing of all the new features and bug fixes included in this release. >> >> Of particular note: This release includes an upgrade to Bootstrap 3 for the staff interface. This version has significant changes to HTML, CSS, and Javascript components in the staff UI, so any plugins or custom templates will have to be modified to work with Bootstrap 3. >> >> Also included in this release is a Find-And-Replace background job, which allows users to bulk edit records. As this is a currently a beta-feature, it is recommended that users backup their database frequently if using this feature. >> >> Thanks to all the volunteers on the ArchivesSpace User Advisory and Technical Advisory Councils, who are vital to keeping ArchivesSpace development on track. >> >> Please let us know if you have any questions, comments, or concerns. >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: From brianjhoffman at gmail.com Tue Apr 7 13:16:19 2015 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Tue, 7 Apr 2015 13:16:19 -0400 Subject: [Archivesspace_Users_Group] digital object import questions In-Reply-To: <553120613.199809.1428425829868.JavaMail.zimbra@psu.edu> References: <5509AD61.3030202@uga.edu> <5509B9E9.6030203@uga.edu> <713009522.595649.1426772526934.JavaMail.zimbra@psu.edu> <1037746823.671088.1426779552408.JavaMail.zimbra@psu.edu> <553120613.199809.1428425829868.JavaMail.zimbra@psu.edu> Message-ID: <9572D64F-394C-4601-91EA-9787BCFDF685@gmail.com> Hi, You need to add a ?is_component? column with a value of ?true? for each row. Also, you need to add a row for the parent object (digital_object_id: pstsc_00084, is_component: false, digital_object_component_id: null) Brian On Apr 7, 2015, at 12:57 PM, Ben Goldman wrote: > Hello everyone, > > I'm testing the digital object import option in ASpace and am encountering an issue. I am trying to import a group of digital objects and make them components of a parent digital object record. I've set this up according to the import mappings, which seem to indicate I should use the parent digital_object_id for the each row's digital_object_id, then use digital_object_component_id for the component level identifier values. Even so, I get an error on import (see attached screenshot). > > More generally, I am wondering if there is a way to relate these digital objects with archival objects on ingest. A use case might be we digitize 100 audio cassettes related to a collection, and then import a modified metadata spreadsheet (somewhat unsatisfying, obviously) to create digital objects. I don't think it will be feasible for us to move through these 100 new digital objects one by one attaching them to archival objects. > > By the way, we are still in v1.1.2, so if the error noted is addressed in 1.2, great! > > Best, > 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 From smithkr at mit.edu Tue Apr 7 14:19:23 2015 From: smithkr at mit.edu (Kari R Smith) Date: Tue, 7 Apr 2015 18:19:23 +0000 Subject: [Archivesspace_Users_Group] Location for Digital instances? Message-ID: <29F559819ACA9A4FBF208407D4B63ABBBA59BFDD@OC11expo28.exchange.mit.edu> I want to note a digital location for files, without creating a digital object. For instance, an entire Bag of content, only being described at an aggregate. The first, required field, Building, implies a physical location - I'm interested in noting a file server as the base location. The location of the files won't be in an asset management system, so I won't have a URI, a URL or other click-able file/folder location. Thoughts? How are others doing this? Kari Smith From mang.sun at rice.edu Tue Apr 7 14:30:04 2015 From: mang.sun at rice.edu (Mang Sun) Date: Tue, 07 Apr 2015 13:30:04 -0500 Subject: [Archivesspace_Users_Group] ArchivesSpace v1.2.0 released In-Reply-To: References: <1427746077682.56800@lyrasis.org> <55240779.6020209@rice.edu> Message-ID: <5524222C.8020002@rice.edu> Steve, I don't see any problem with the EAD link and the MARCXML link except the EAD_PDF link of this plugin. Mang On 4/7/2015 12:07 PM, Steven Majewski wrote: > > I?m not seeing any problems on OSX. > Do you get any errors from the EAD (xml) export on the same page ? > > ? Steve Majewski / UVA Alderman Library > > > > > On Apr 7, 2015, at 12:36 PM, Mang Sun > wrote: > >> Hi Christ, >> >> Though I posted this question as an independent thread, I figure I'd >> better directly draw your attention to this issue. >> The issue is with the ead_pdf link of plugin aspace-public-formats of >> AS 1.2.0 . When this link is clicked, the following error message >> will be thrown. >> I run into the same issue on REDHAT 6.4 and OS X, but Brad does not >> have any problem with this plugin on Windows 7. -Mang Sun, Rice U. >> >> >> EOFError in PublicFormatsController#generate >> >> End of file reached >> |Rails.root: /Users/ms20/Applications/archivesspace/public| >> Application Trace >> |Framework >> Trace >> |Full >> Trace >> >> || >> >> >> Request >> >> *Parameters*: >> {"repo_id"=>"2", >> "type"=>"resources", >> "id"=>"1", >> "format"=>"ead_pdf"} >> Show session dump >> >> Show env dump >> >> >> >> Response >> >> *Headers*: >> None >> >> >> >> On 3/30/2015 3:07 PM, Chris Fitzpatrick wrote: >>> The ArchivesSpace team is happy to release version v1.2.0 >>> . >>> >>> Please see the technicaldocumentation >>> for >>> information on how to upgrade your ArchivesSpace installs. >>> >>> Please see therelease page >>> for >>> a listing of all the new features and bug fixes included in this >>> release. >>> >>> Of particular note: This release includes an upgrade toBootstrap 3 >>> for the staff interface. This version has >>> significant changes to HTML, CSS, and Javascript components in the >>> staff UI, so any plugins or custom templates will have to >>> be modified to work with Bootstrap 3. >>> >>> Also included in this release is a Find-And-Replace background job, >>> which allows users to bulk edit records. As this is a currently a >>> beta-feature, it is recommended that users backup their database >>> frequently if using this feature. >>> >>> Thanks to all the volunteers on the ArchivesSpace User Advisory and >>> Technical Advisory Councils, who are vital to keeping ArchivesSpace >>> development on track. >>> Please let us know if you have any questions, comments, or concerns. >>> >>> >>> Chris Fitzpatrick | Developer, ArchivesSpace >>> Skype: chrisfitzpat | Phone: 918.236.6048 >>> http://archivesspace.org/ >>> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Wed Apr 8 03:59:53 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Wed, 8 Apr 2015 07:59:53 +0000 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: <55240534.1010502@rice.edu> References: <551D6503.8000500@rice.edu> <5522BEFE.6090502@rice.edu> <5523048E.9060801@rice.edu> , <55240534.1010502@rice.edu> Message-ID: <1428479992653.18332@lyrasis.org> Hi Everyone, It looks like the generate PDF as a background job in version 1.2.0 broke the aspace-public-formats plugin PDF export feature. I've fixed the plugin here : https://github.com/archivesspace/aspace-public-formats If you need this feature, please remove the version of the plugin you have currently installed and replace it with the version on github and restart ASpace. Also, please note that the public-format plugin PDF feature will not work for large resources. Sorry about the inconvenience. Let us know if you have other issues or questions... b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mang Sun Sent: Tuesday, April 7, 2015 6:26 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 Thank you again Brad. I also have tested this version on MAC OS X and still see the same issue with the ead_pdf link of this plugin. Mang On 4/7/2015 6:15 AM, Brad Westbrook wrote: Windows 7, Mang. Brad From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mang Sun Sent: Monday, April 06, 2015 6:11 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 By the way, under which OS is your AS 1.2 running ? Mine is Redhat 6.4. Mang On 4/6/2015 12:47 PM, Brad Westbrook wrote: Hi, Mang I just successfully tested the public formats plugin for all three options. I tested it in a localhost install using the embedded Derby database. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mang Sun Sent: Monday, April 06, 2015 1:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 Can somebody or the development team confirm whether the public_formats_resource_links plugin still works with AS 1.2? Mang Sun Rice U. On 4/2/2015 10:49 AM, Mang Sun wrote: When clicking the ead_pdf link turned on by the public_formats_resource_links plugin does not work with AS 1.2 throwing the error message as follows. -Mang Sun Rice U. EOFError in PublicFormatsController#generate Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public Request Parameters: {"repo_id"=>"2", "type"=>"resources", "id"=>"116", "format"=>"ead_pdf"} Show session dump _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" session_id: "c419289cb412f46af571004e4b0c0830" Show env dump GATEWAY_INTERFACE: "CGI/1.2" HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" HTTP_ACCEPT_ENCODING: "gzip, deflate" HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" REMOTE_ADDR: "10.xx.xx.xx" SERVER_NAME: "10.xx.22.xx" SERVER_PROTOCOL: "HTTP/1.1" Response Headers: None ----------------- The Full trace is pasted as below. org/jruby/RubyIO.java:2858:in `read_nonblock' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request' org/jruby/RubyKernel.java:1270:in `catch' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request' /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle' /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate' actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action' actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action' actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action' actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action' activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action' actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action' actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action' activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument' activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument' activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action' actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action' actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process' actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process' actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch' actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch' actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action' org/jruby/RubyProc.java:271:in `call' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call' journey (1.0.4) lib/journey/router.rb:68:in `call' org/jruby/RubyArray.java:1613:in `each' journey (1.0.4) lib/journey/router.rb:56:in `call' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call' rack (1.4.5) lib/rack/etag.rb:23:in `call' rack (1.4.5) lib/rack/conditionalget.rb:25:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call' rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context' rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call' activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app' railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged' railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call' rack (1.4.5) lib/rack/methodoverride.rb:21:in `call' rack (1.4.5) lib/rack/runtime.rb:17:in `call' activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call' rack (1.4.5) lib/rack/lock.rb:15:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call' railties (3.2.19) lib/rails/engine.rb:484:in `call' railties (3.2.19) lib/rails/application.rb:231:in `call' rack (1.4.5) lib/rack/content_length.rb:14:in `call' railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call' puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request' puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request' puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client' puma-2.8.2 (java) lib/puma/server.rb:254:in `run' org/jruby/RubyProc.java:271:in `call' puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread' _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Wed Apr 8 09:29:41 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Wed, 8 Apr 2015 13:29:41 +0000 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: <55240534.1010502@rice.edu> References: <551D6503.8000500@rice.edu> <5522BEFE.6090502@rice.edu> <5523048E.9060801@rice.edu> , <55240534.1010502@rice.edu> Message-ID: <1428499780370.12790@lyrasis.org> Hi Everyone, It looks like the generate PDF as a background job in version 1.2.0 broke the aspace-public-formats plugin PDF export feature. I've fixed the plugin here : https://github.com/archivesspace/aspace-public-formats If you need this feature, please remove the version of the plugin you have currently installed and replace it with the version on github and restart ASpace. Also, please note that the public-format plugin PDF feature will not work for large resources. Sorry about the inconvenience. Let us know if you have other issues or questions... b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mang Sun Sent: Tuesday, April 7, 2015 6:26 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 Thank you again Brad. I also have tested this version on MAC OS X and still see the same issue with the ead_pdf link of this plugin. Mang On 4/7/2015 6:15 AM, Brad Westbrook wrote: Windows 7, Mang. Brad From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mang Sun Sent: Monday, April 06, 2015 6:11 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 By the way, under which OS is your AS 1.2 running ? Mine is Redhat 6.4. Mang On 4/6/2015 12:47 PM, Brad Westbrook wrote: Hi, Mang I just successfully tested the public formats plugin for all three options. I tested it in a localhost install using the embedded Derby database. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mang Sun Sent: Monday, April 06, 2015 1:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 Can somebody or the development team confirm whether the public_formats_resource_links plugin still works with AS 1.2? Mang Sun Rice U. On 4/2/2015 10:49 AM, Mang Sun wrote: When clicking the ead_pdf link turned on by the public_formats_resource_links plugin does not work with AS 1.2 throwing the error message as follows. -Mang Sun Rice U. EOFError in PublicFormatsController#generate Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public Request Parameters: {"repo_id"=>"2", "type"=>"resources", "id"=>"116", "format"=>"ead_pdf"} Show session dump _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" session_id: "c419289cb412f46af571004e4b0c0830" Show env dump GATEWAY_INTERFACE: "CGI/1.2" HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" HTTP_ACCEPT_ENCODING: "gzip, deflate" HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" REMOTE_ADDR: "10.xx.xx.xx" SERVER_NAME: "10.xx.22.xx" SERVER_PROTOCOL: "HTTP/1.1" Response Headers: None ----------------- The Full trace is pasted as below. org/jruby/RubyIO.java:2858:in `read_nonblock' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request' org/jruby/RubyKernel.java:1270:in `catch' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request' /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle' /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate' actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action' actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action' actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action' actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action' activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action' actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action' actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action' activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument' activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument' activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action' actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action' actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process' actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process' actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch' actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch' actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action' org/jruby/RubyProc.java:271:in `call' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call' journey (1.0.4) lib/journey/router.rb:68:in `call' org/jruby/RubyArray.java:1613:in `each' journey (1.0.4) lib/journey/router.rb:56:in `call' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call' rack (1.4.5) lib/rack/etag.rb:23:in `call' rack (1.4.5) lib/rack/conditionalget.rb:25:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call' rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context' rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call' activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app' railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged' railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call' rack (1.4.5) lib/rack/methodoverride.rb:21:in `call' rack (1.4.5) lib/rack/runtime.rb:17:in `call' activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call' rack (1.4.5) lib/rack/lock.rb:15:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call' railties (3.2.19) lib/rails/engine.rb:484:in `call' railties (3.2.19) lib/rails/application.rb:231:in `call' rack (1.4.5) lib/rack/content_length.rb:14:in `call' railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call' puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request' puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request' puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client' puma-2.8.2 (java) lib/puma/server.rb:254:in `run' org/jruby/RubyProc.java:271:in `call' puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread' _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Wed Apr 8 10:24:14 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Wed, 8 Apr 2015 10:24:14 -0400 Subject: [Archivesspace_Users_Group] Accession CSV Subject Import In-Reply-To: <104689F7-34DD-4270-8B7D-4FA79E020368@gmail.com> References: <8heo94nsml7lmaxk4k2o66fi.1428369097757@email.android.com> <104689F7-34DD-4270-8B7D-4FA79E020368@gmail.com> Message-ID: Hi Brian, Hmm, somewhat, but working on that base doesn't seem to work? If I wanted to copy how date is set up it seems it would look something like this: 'subject_1_source' => 'subject_1.source', 'subject_1_term' => 'subject_1.term', 'subject_1_term_type' => 'subject_1.term_type', 'subject_2_source' => 'subject_2.source', 'subject_2_term' => 'subject_2.term', 'subject_2_term_type' => 'subject_2.term_type', 'subject_3_source' => 'subject_3.source', 'subject_3_term' => 'subject_3.term', 'subject_3_term_type' => 'subject_3.term_type', and then :subject_1 => { :record_type => :subject, :on_create => Proc.new {|data, obj| obj.terms = [{:term => data['term'], :term_type => data['term_type'], :vocabulary => '/vocabularies/1'}] obj.vocabulary = '/vocabularies/1' }, :on_row_complete => Proc.new {|cache, this| digital_object = cache.find {|obj| obj.class.record_type == 'accession'} digital_object.subjects << {'ref' => this.uri} } }, :subject_2 => { :record_type => :subject, :on_create => Proc.new {|data, obj| obj.terms = [{:term => data['term'], :term_type => data['term_type'], :vocabulary => '/vocabularies/1'}] obj.vocabulary = '/vocabularies/1' }, :on_row_complete => Proc.new {|cache, this| digital_object = cache.find {|obj| obj.class.record_type == 'accession'} digital_object.subjects << {'ref' => this.uri} } }, :subject_3 => { :record_type => :subject, :on_create => Proc.new {|data, obj| obj.terms = [{:term => data['term'], :term_type => data['term_type'], :vocabulary => '/vocabularies/1'}] obj.vocabulary = '/vocabularies/1' }, :on_row_complete => Proc.new {|cache, this| digital_object = cache.find {|obj| obj.class.record_type == 'accession'} digital_object.subjects << {'ref' => this.uri} } }, Although I admit I'm not sure if I'd have to change some of the inner working of the subject_# fields in part two (it seems like on_create is building the subject object, and the on_row is then connecting it to the record so I shouldn't but I could be wrong). When I make the changes above and implement the plugin, subjects just stop being imported at all (although no errors, they're just ignored). -Maura On Tue, Apr 7, 2015 at 1:04 PM, Brian Hoffman wrote: > Hi Maura, > > No, there?s nothing else. Generally the keys in the callbacks section > (:date_1 => etc) are used to tie things together with the schema. Where > there are multiple objects created per row, there?s an optional > :record_type key in the callback config that does the mapping (:record_type > => :date). > > Does that make sense? > > Brian > > > > > > On Apr 7, 2015, at 10:45 AM, Maura Carbone wrote: > > Hi Brian, > I found that one all right, but is there another file that would have to > be edited? Looking at that file I can't see where the 'labels' are linked > to the data types, so I was assuming there was another file that does that. > For example, the first half has labels for date_1: > > 'date_1_label' => 'date_1.label', > 'date_1_expression' => 'date_1.expression', > 'date_1_begin' => 'date_1.begin', > 'date_1_end' => 'date_1.end', > 'date_1_type' => 'date_1.date_type', > > and then the date object creator is: > > :date_1 => { > :record_type => :date, > :defaults => date_defaults, > :on_row_complete => Proc.new { |queue, date| > queue.select {|obj| obj.class.record_type == 'accession'}.each > do |accession| > accession.dates << date > end > } > > so I thought there must be a file mapping the date_1 labels to the date > object fields in the schema? > > > Thanks, > Maura > > On Mon, Apr 6, 2015 at 9:11 PM, brian wrote: > >> Hi Maura, >> >> Here's the base converter file for accession csv. >> >> >> https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/accession_converter.rb >> >> >> Brian >> >> >> >> Sent from my T-Mobile 4G LTE Device >> >> >> -------- Original message -------- >> From: Maura Carbone >> Date:04/06/2015 3:35 PM (GMT-05:00) >> To: Archivesspace Users Group < >> archivesspace_users_group at lyralists.lyrasis.org> >> Cc: >> Subject: Re: [Archivesspace_Users_Group] Accession CSV Subject Import >> >> Hi Chris, >> Any progress on that example? I actually tried to work on it myself, but >> I'm not entirely sure which files need to be altered (aside from >> accession_converter). Ideally, I want to be able to import multiple >> subjects and multiple agents -- I was hoping to copy the date setup (where >> there are multiple dates date1 date2 etc.) but I haven't found the file >> where the terms (such as date_label_1) are mapped to the date object (and >> so on for subject and agents etc.) >> >> Thanks! >> Maura >> >> On Tue, Mar 31, 2015 at 4:03 PM, Maura Carbone >> wrote: >> >>> What I was doing was: >>> subject_source,subject_term_type,subject_term,subject_source,subject_term_type,subject_term, Unspecified >>> ingested source,Topical,Pepperoni,Unspecified ingested >>> source,Topical,Cheese. Then only Cheese gets created and imported. >>> >>> Yeah, and I can take a look at how the importer works now as well, I >>> just wasn't sure if it was a known issue, or if there was a specific reason >>> for it. >>> >>> Thanks! >>> Maura >>> >>> On Tue, Mar 31, 2015 at 3:29 PM, Chris Fitzpatrick < >>> Chris.Fitzpatrick at lyrasis.org> wrote: >>> >>>> Hi Maura, >>>> >>>> >>>> So, you're just adding more subject columns to the CSV? Yes, what you >>>> describe about overwriting is exactly what's happening...the CSV importer >>>> only allows for one subject per row. >>>> >>>> >>>> I have a plugin example I started working on last week to show how to >>>> tweak the CSV importer...I'll try and finish that up tomorrow and send it >>>> out for people to have a look... >>>> >>>> >>>> b,chris. >>>> >>>> >>>> Chris Fitzpatrick | Developer, ArchivesSpace >>>> Skype: chrisfitzpat | Phone: 918.236.6048 >>>> http://archivesspace.org/ >>>> ------------------------------ >>>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >>>> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >>>> Maura Carbone >>>> *Sent:* Tuesday, March 31, 2015 7:06 PM >>>> *To:* Archivesspace Users Group >>>> *Subject:* [Archivesspace_Users_Group] Accession CSV Subject Import >>>> >>>> Hi all, >>>> I've been working on importing accessions with CSV files, but I've >>>> noticed that on import only one subject ever gets brought in (the last >>>> one). Is this a bug, or just a current limitation? I'm not getting an >>>> error, it just appears that the subject field keeps being over-written >>>> until the last subject, then imported. >>>> >>>> Thanks, >>>> Maura >>>> >>>> -- >>>> Maura Carbone >>>> Digital Initiatives Librarian >>>> Brandeis University >>>> Library and Technology Services >>>> (781) 736-4659 >>>> 415 South Street, (MS 017/P.O. Box 549110) >>>> Waltham, MA 02454-9110 >>>> email: mauraa at brandeis.edu >>>> >>>> _______________________________________________ >>>> Archivesspace_Users_Group mailing list >>>> Archivesspace_Users_Group at lyralists.lyrasis.org >>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>>> >>>> >>> >>> >>> -- >>> Maura Carbone >>> Digital Initiatives Librarian >>> Brandeis University >>> Library and Technology Services >>> (781) 736-4659 >>> 415 South Street, (MS 017/P.O. Box 549110) >>> Waltham, MA 02454-9110 >>> email: mauraa at brandeis.edu >>> >> >> >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From lindsay-morecraft at uiowa.edu Wed Apr 8 11:01:21 2015 From: lindsay-morecraft at uiowa.edu (Morecraft, Lindsay M) Date: Wed, 8 Apr 2015 15:01:21 +0000 Subject: [Archivesspace_Users_Group] Rapid Data Entry Message-ID: <96B305F061ED68428DDA721BECE2ED15516689C6@ITSNT440.iowa.uiowa.edu> Hello, I was wondering as to why the Label field for the Date section is not included in the Rapid Data Entry. My colleagues and I have discovered that each archival object entered in RDE will autofill that section with Other, when we need Creation, Publication, etc. As a result, we have to go in and manually change each Label Date field, which has been defeating the purpose of the rapid entry. Is this a new change that has occurred with the new update? Am I missing something? Thanks so much for the help, Lindsay Lindsay Moen (Morecraft) Processing Librarian Special Collections and University Archives The University of Iowa 319-335-5921 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmg17 at psu.edu Wed Apr 8 11:03:05 2015 From: bmg17 at psu.edu (Ben Goldman) Date: Wed, 8 Apr 2015 11:03:05 -0400 (EDT) Subject: [Archivesspace_Users_Group] digital object import questions In-Reply-To: <9572D64F-394C-4601-91EA-9787BCFDF685@gmail.com> References: <5509AD61.3030202@uga.edu> <713009522.595649.1426772526934.JavaMail.zimbra@psu.edu> <1037746823.671088.1426779552408.JavaMail.zimbra@psu.edu> <553120613.199809.1428425829868.JavaMail.zimbra@psu.edu> <9572D64F-394C-4601-91EA-9787BCFDF685@gmail.com> Message-ID: <1094760050.158227.1428505385533.JavaMail.zimbra@psu.edu> Hi Brian, Thanks for the tip. That did the trick. I'm still wondering, however, whether there's any way to identify a related archival object on import, rather than attaching each of these manually after import. Thanks, Ben ----- Original Message ----- From: "Brian Hoffman" To: "Archivesspace Users Group" Sent: Tuesday, April 7, 2015 1:16:19 PM Subject: Re: [Archivesspace_Users_Group] digital object import questions Hi, You need to add a ?is_component? column with a value of ?true? for each row. Also, you need to add a row for the parent object (digital_object_id: pstsc_00084, is_component: false, digital_object_component_id: null) Brian On Apr 7, 2015, at 12:57 PM, Ben Goldman wrote: > Hello everyone, > > I'm testing the digital object import option in ASpace and am encountering an issue. I am trying to import a group of digital objects and make them components of a parent digital object record. I've set this up according to the import mappings, which seem to indicate I should use the parent digital_object_id for the each row's digital_object_id, then use digital_object_component_id for the component level identifier values. Even so, I get an error on import (see attached screenshot). > > More generally, I am wondering if there is a way to relate these digital objects with archival objects on ingest. A use case might be we digitize 100 audio cassettes related to a collection, and then import a modified metadata spreadsheet (somewhat unsatisfying, obviously) to create digital objects. I don't think it will be feasible for us to move through these 100 new digital objects one by one attaching them to archival objects. > > By the way, we are still in v1.1.2, so if the error noted is addressed in 1.2, great! > > Best, > 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 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From brianjhoffman at gmail.com Wed Apr 8 12:18:06 2015 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Wed, 8 Apr 2015 12:18:06 -0400 Subject: [Archivesspace_Users_Group] digital object import questions In-Reply-To: <1094760050.158227.1428505385533.JavaMail.zimbra@psu.edu> References: <5509AD61.3030202@uga.edu> <713009522.595649.1426772526934.JavaMail.zimbra@psu.edu> <1037746823.671088.1426779552408.JavaMail.zimbra@psu.edu> <553120613.199809.1428425829868.JavaMail.zimbra@psu.edu> <9572D64F-394C-4601-91EA-9787BCFDF685@gmail.com> <1094760050.158227.1428505385533.JavaMail.zimbra@psu.edu> Message-ID: <524AA27D-C6CE-4660-A7D6-749C1F1BB4CE@gmail.com> Hi Ben, No, with the current digital object importer, you can?t do that. Brian On Apr 8, 2015, at 11:03 AM, Ben Goldman wrote: > Hi Brian, > > Thanks for the tip. That did the trick. > > I'm still wondering, however, whether there's any way to identify a related archival object on import, rather than attaching each of these manually after import. > > Thanks, > Ben > > ----- Original Message ----- > From: "Brian Hoffman" > To: "Archivesspace Users Group" > Sent: Tuesday, April 7, 2015 1:16:19 PM > Subject: Re: [Archivesspace_Users_Group] digital object import questions > > Hi, > > You need to add a ?is_component? column with a value of ?true? for each row. > > Also, you need to add a row for the parent object (digital_object_id: pstsc_00084, is_component: false, digital_object_component_id: null) > > Brian > > > On Apr 7, 2015, at 12:57 PM, Ben Goldman wrote: > >> Hello everyone, >> >> I'm testing the digital object import option in ASpace and am encountering an issue. I am trying to import a group of digital objects and make them components of a parent digital object record. I've set this up according to the import mappings, which seem to indicate I should use the parent digital_object_id for the each row's digital_object_id, then use digital_object_component_id for the component level identifier values. Even so, I get an error on import (see attached screenshot). >> >> More generally, I am wondering if there is a way to relate these digital objects with archival objects on ingest. A use case might be we digitize 100 audio cassettes related to a collection, and then import a modified metadata spreadsheet (somewhat unsatisfying, obviously) to create digital objects. I don't think it will be feasible for us to move through these 100 new digital objects one by one attaching them to archival objects. >> >> By the way, we are still in v1.1.2, so if the error noted is addressed in 1.2, great! >> >> Best, >> 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 > > _______________________________________________ > 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 brianjhoffman at gmail.com Wed Apr 8 12:25:06 2015 From: brianjhoffman at gmail.com (Brian Hoffman) Date: Wed, 8 Apr 2015 12:25:06 -0400 Subject: [Archivesspace_Users_Group] Accession CSV Subject Import In-Reply-To: References: <8heo94nsml7lmaxk4k2o66fi.1428369097757@email.android.com> <104689F7-34DD-4270-8B7D-4FA79E020368@gmail.com> Message-ID: <856AE80E-D8B5-455F-8268-18490D2F9B6B@gmail.com> What you have looks right to me. If you want to send me a sample CSV with a few rows filled in I?ll see if I can figure it out. Brian On Apr 8, 2015, at 10:24 AM, Maura Carbone wrote: > Hi Brian, > > Hmm, somewhat, but working on that base doesn't seem to work? > > If I wanted to copy how date is set up it seems it would look something like this: > > 'subject_1_source' => 'subject_1.source', > 'subject_1_term' => 'subject_1.term', > 'subject_1_term_type' => 'subject_1.term_type', > > 'subject_2_source' => 'subject_2.source', > 'subject_2_term' => 'subject_2.term', > 'subject_2_term_type' => 'subject_2.term_type', > > 'subject_3_source' => 'subject_3.source', > 'subject_3_term' => 'subject_3.term', > 'subject_3_term_type' => 'subject_3.term_type', > > and then > > :subject_1 => { > :record_type => :subject, > :on_create => Proc.new {|data, obj| > obj.terms = [{:term => data['term'], :term_type => data['term_type'], :vocabulary => '/vocabularies/1'}] > obj.vocabulary = '/vocabularies/1' > }, > :on_row_complete => Proc.new {|cache, this| > digital_object = cache.find {|obj| obj.class.record_type == 'accession'} > digital_object.subjects << {'ref' => this.uri} > } > }, > > :subject_2 => { > :record_type => :subject, > :on_create => Proc.new {|data, obj| > obj.terms = [{:term => data['term'], :term_type => data['term_type'], :vocabulary => '/vocabularies/1'}] > obj.vocabulary = '/vocabularies/1' > }, > :on_row_complete => Proc.new {|cache, this| > digital_object = cache.find {|obj| obj.class.record_type == 'accession'} > digital_object.subjects << {'ref' => this.uri} > } > }, > > :subject_3 => { > :record_type => :subject, > :on_create => Proc.new {|data, obj| > obj.terms = [{:term => data['term'], :term_type => data['term_type'], :vocabulary => '/vocabularies/1'}] > obj.vocabulary = '/vocabularies/1' > }, > :on_row_complete => Proc.new {|cache, this| > digital_object = cache.find {|obj| obj.class.record_type == 'accession'} > digital_object.subjects << {'ref' => this.uri} > } > }, > > Although I admit I'm not sure if I'd have to change some of the inner working of the subject_# fields in part two (it seems like on_create is building the subject object, and the on_row is then connecting it to the record so I shouldn't but I could be wrong). > > When I make the changes above and implement the plugin, subjects just stop being imported at all (although no errors, they're just ignored). > > -Maura > > > On Tue, Apr 7, 2015 at 1:04 PM, Brian Hoffman wrote: > Hi Maura, > > No, there?s nothing else. Generally the keys in the callbacks section (:date_1 => etc) are used to tie things together with the schema. Where there are multiple objects created per row, there?s an optional :record_type key in the callback config that does the mapping (:record_type => :date). > > Does that make sense? > > Brian > > > > > > On Apr 7, 2015, at 10:45 AM, Maura Carbone wrote: > >> Hi Brian, >> I found that one all right, but is there another file that would have to be edited? Looking at that file I can't see where the 'labels' are linked to the data types, so I was assuming there was another file that does that. For example, the first half has labels for date_1: >> >> 'date_1_label' => 'date_1.label', >> 'date_1_expression' => 'date_1.expression', >> 'date_1_begin' => 'date_1.begin', >> 'date_1_end' => 'date_1.end', >> 'date_1_type' => 'date_1.date_type', >> >> and then the date object creator is: >> >> :date_1 => { >> :record_type => :date, >> :defaults => date_defaults, >> :on_row_complete => Proc.new { |queue, date| >> queue.select {|obj| obj.class.record_type == 'accession'}.each do |accession| >> accession.dates << date >> end >> } >> >> so I thought there must be a file mapping the date_1 labels to the date object fields in the schema? >> >> >> Thanks, >> Maura >> >> On Mon, Apr 6, 2015 at 9:11 PM, brian wrote: >> Hi Maura, >> >> Here's the base converter file for accession csv. >> >> https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/accession_converter.rb >> >> >> Brian >> >> >> >> Sent from my T-Mobile 4G LTE Device >> >> >> -------- Original message -------- >> From: Maura Carbone >> Date:04/06/2015 3:35 PM (GMT-05:00) >> To: Archivesspace Users Group >> Cc: >> Subject: Re: [Archivesspace_Users_Group] Accession CSV Subject Import >> >> Hi Chris, >> Any progress on that example? I actually tried to work on it myself, but I'm not entirely sure which files need to be altered (aside from accession_converter). Ideally, I want to be able to import multiple subjects and multiple agents -- I was hoping to copy the date setup (where there are multiple dates date1 date2 etc.) but I haven't found the file where the terms (such as date_label_1) are mapped to the date object (and so on for subject and agents etc.) >> >> Thanks! >> Maura >> >> On Tue, Mar 31, 2015 at 4:03 PM, Maura Carbone wrote: >> What I was doing was: >> subject_source,subject_term_type,subject_term,subject_source,subject_term_type,subject_term, Unspecified ingested source,Topical,Pepperoni,Unspecified ingested source,Topical,Cheese. Then only Cheese gets created and imported. >> >> Yeah, and I can take a look at how the importer works now as well, I just wasn't sure if it was a known issue, or if there was a specific reason for it. >> >> Thanks! >> Maura >> >> On Tue, Mar 31, 2015 at 3:29 PM, Chris Fitzpatrick wrote: >> Hi Maura, >> >> >> So, you're just adding more subject columns to the CSV? Yes, what you describe about overwriting is exactly what's happening...the CSV importer only allows for one subject per row. >> >> >> I have a plugin example I started working on last week to show how to tweak the CSV importer...I'll try and finish that up tomorrow and send it out for people to have a look... >> >> >> b,chris. >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Maura Carbone >> Sent: Tuesday, March 31, 2015 7:06 PM >> To: Archivesspace Users Group >> Subject: [Archivesspace_Users_Group] Accession CSV Subject Import >> >> Hi all, >> I've been working on importing accessions with CSV files, but I've noticed that on import only one subject ever gets brought in (the last one). Is this a bug, or just a current limitation? I'm not getting an error, it just appears that the subject field keeps being over-written until the last subject, then imported. >> >> Thanks, >> Maura >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> >> >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Wed Apr 8 14:08:05 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Wed, 8 Apr 2015 14:08:05 -0400 Subject: [Archivesspace_Users_Group] Accession CSV Subject Import In-Reply-To: <856AE80E-D8B5-455F-8268-18490D2F9B6B@gmail.com> References: <8heo94nsml7lmaxk4k2o66fi.1428369097757@email.android.com> <104689F7-34DD-4270-8B7D-4FA79E020368@gmail.com> <856AE80E-D8B5-455F-8268-18490D2F9B6B@gmail.com> Message-ID: Here's the sample file; it worked before the changes (i.e. when the subjects were just over-written until the last), but now when I import I just get no subjects created. If I can figure it out I thought it would be nice to implement for subjects and agents since our accessions often have multiple of both. Thanks! On Wed, Apr 8, 2015 at 12:25 PM, Brian Hoffman wrote: > What you have looks right to me. If you want to send me a sample CSV with > a few rows filled in I?ll see if I can figure it out. > > Brian > > > On Apr 8, 2015, at 10:24 AM, Maura Carbone wrote: > > Hi Brian, > > Hmm, somewhat, but working on that base doesn't seem to work? > > If I wanted to copy how date is set up it seems it would look something > like this: > > 'subject_1_source' => 'subject_1.source', > 'subject_1_term' => 'subject_1.term', > 'subject_1_term_type' => 'subject_1.term_type', > > 'subject_2_source' => 'subject_2.source', > 'subject_2_term' => 'subject_2.term', > 'subject_2_term_type' => 'subject_2.term_type', > > 'subject_3_source' => 'subject_3.source', > 'subject_3_term' => 'subject_3.term', > 'subject_3_term_type' => 'subject_3.term_type', > > and then > > :subject_1 => { > :record_type => :subject, > :on_create => Proc.new {|data, obj| > obj.terms = [{:term => data['term'], :term_type => > data['term_type'], :vocabulary => '/vocabularies/1'}] > obj.vocabulary = '/vocabularies/1' > }, > :on_row_complete => Proc.new {|cache, this| > digital_object = cache.find {|obj| obj.class.record_type == > 'accession'} > digital_object.subjects << {'ref' => this.uri} > } > }, > > :subject_2 => { > :record_type => :subject, > :on_create => Proc.new {|data, obj| > obj.terms = [{:term => data['term'], :term_type => > data['term_type'], :vocabulary => '/vocabularies/1'}] > obj.vocabulary = '/vocabularies/1' > }, > :on_row_complete => Proc.new {|cache, this| > digital_object = cache.find {|obj| obj.class.record_type == > 'accession'} > digital_object.subjects << {'ref' => this.uri} > } > }, > > :subject_3 => { > :record_type => :subject, > :on_create => Proc.new {|data, obj| > obj.terms = [{:term => data['term'], :term_type => > data['term_type'], :vocabulary => '/vocabularies/1'}] > obj.vocabulary = '/vocabularies/1' > }, > :on_row_complete => Proc.new {|cache, this| > digital_object = cache.find {|obj| obj.class.record_type == > 'accession'} > digital_object.subjects << {'ref' => this.uri} > } > }, > > Although I admit I'm not sure if I'd have to change some of the inner > working of the subject_# fields in part two (it seems like on_create is > building the subject object, and the on_row is then connecting it to the > record so I shouldn't but I could be wrong). > > When I make the changes above and implement the plugin, subjects just stop > being imported at all (although no errors, they're just ignored). > > -Maura > > > On Tue, Apr 7, 2015 at 1:04 PM, Brian Hoffman > wrote: > >> Hi Maura, >> >> No, there?s nothing else. Generally the keys in the callbacks section >> (:date_1 => etc) are used to tie things together with the schema. Where >> there are multiple objects created per row, there?s an optional >> :record_type key in the callback config that does the mapping (:record_type >> => :date). >> >> Does that make sense? >> >> Brian >> >> >> >> >> >> On Apr 7, 2015, at 10:45 AM, Maura Carbone wrote: >> >> Hi Brian, >> I found that one all right, but is there another file that would have to >> be edited? Looking at that file I can't see where the 'labels' are linked >> to the data types, so I was assuming there was another file that does that. >> For example, the first half has labels for date_1: >> >> 'date_1_label' => 'date_1.label', >> 'date_1_expression' => 'date_1.expression', >> 'date_1_begin' => 'date_1.begin', >> 'date_1_end' => 'date_1.end', >> 'date_1_type' => 'date_1.date_type', >> >> and then the date object creator is: >> >> :date_1 => { >> :record_type => :date, >> :defaults => date_defaults, >> :on_row_complete => Proc.new { |queue, date| >> queue.select {|obj| obj.class.record_type == 'accession'}.each >> do |accession| >> accession.dates << date >> end >> } >> >> so I thought there must be a file mapping the date_1 labels to the date >> object fields in the schema? >> >> >> Thanks, >> Maura >> >> On Mon, Apr 6, 2015 at 9:11 PM, brian wrote: >> >>> Hi Maura, >>> >>> Here's the base converter file for accession csv. >>> >>> >>> https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/accession_converter.rb >>> >>> >>> Brian >>> >>> >>> >>> Sent from my T-Mobile 4G LTE Device >>> >>> >>> -------- Original message -------- >>> From: Maura Carbone >>> Date:04/06/2015 3:35 PM (GMT-05:00) >>> To: Archivesspace Users Group < >>> archivesspace_users_group at lyralists.lyrasis.org> >>> Cc: >>> Subject: Re: [Archivesspace_Users_Group] Accession CSV Subject Import >>> >>> Hi Chris, >>> Any progress on that example? I actually tried to work on it myself, but >>> I'm not entirely sure which files need to be altered (aside from >>> accession_converter). Ideally, I want to be able to import multiple >>> subjects and multiple agents -- I was hoping to copy the date setup (where >>> there are multiple dates date1 date2 etc.) but I haven't found the file >>> where the terms (such as date_label_1) are mapped to the date object (and >>> so on for subject and agents etc.) >>> >>> Thanks! >>> Maura >>> >>> On Tue, Mar 31, 2015 at 4:03 PM, Maura Carbone >>> wrote: >>> >>>> What I was doing was: >>>> subject_source,subject_term_type,subject_term,subject_source,subject_term_type,subject_term, Unspecified >>>> ingested source,Topical,Pepperoni,Unspecified ingested >>>> source,Topical,Cheese. Then only Cheese gets created and imported. >>>> >>>> Yeah, and I can take a look at how the importer works now as well, I >>>> just wasn't sure if it was a known issue, or if there was a specific reason >>>> for it. >>>> >>>> Thanks! >>>> Maura >>>> >>>> On Tue, Mar 31, 2015 at 3:29 PM, Chris Fitzpatrick < >>>> Chris.Fitzpatrick at lyrasis.org> wrote: >>>> >>>>> Hi Maura, >>>>> >>>>> >>>>> So, you're just adding more subject columns to the CSV? Yes, what you >>>>> describe about overwriting is exactly what's happening...the CSV importer >>>>> only allows for one subject per row. >>>>> >>>>> >>>>> I have a plugin example I started working on last week to show how to >>>>> tweak the CSV importer...I'll try and finish that up tomorrow and send it >>>>> out for people to have a look... >>>>> >>>>> >>>>> b,chris. >>>>> >>>>> >>>>> Chris Fitzpatrick | Developer, ArchivesSpace >>>>> Skype: chrisfitzpat | Phone: 918.236.6048 >>>>> http://archivesspace.org/ >>>>> ------------------------------ >>>>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >>>>> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >>>>> Maura Carbone >>>>> *Sent:* Tuesday, March 31, 2015 7:06 PM >>>>> *To:* Archivesspace Users Group >>>>> *Subject:* [Archivesspace_Users_Group] Accession CSV Subject Import >>>>> >>>>> Hi all, >>>>> I've been working on importing accessions with CSV files, but I've >>>>> noticed that on import only one subject ever gets brought in (the last >>>>> one). Is this a bug, or just a current limitation? I'm not getting an >>>>> error, it just appears that the subject field keeps being over-written >>>>> until the last subject, then imported. >>>>> >>>>> Thanks, >>>>> Maura >>>>> >>>>> -- >>>>> Maura Carbone >>>>> Digital Initiatives Librarian >>>>> Brandeis University >>>>> Library and Technology Services >>>>> (781) 736-4659 >>>>> 415 South Street, (MS 017/P.O. Box 549110) >>>>> Waltham, MA 02454-9110 >>>>> email: mauraa at brandeis.edu >>>>> >>>>> _______________________________________________ >>>>> Archivesspace_Users_Group mailing list >>>>> Archivesspace_Users_Group at lyralists.lyrasis.org >>>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>>>> >>>>> >>>> >>>> >>>> -- >>>> Maura Carbone >>>> Digital Initiatives Librarian >>>> Brandeis University >>>> Library and Technology Services >>>> (781) 736-4659 >>>> 415 South Street, (MS 017/P.O. Box 549110) >>>> Waltham, MA 02454-9110 >>>> email: mauraa at brandeis.edu >>>> >>> >>> >>> >>> -- >>> Maura Carbone >>> Digital Initiatives Librarian >>> Brandeis University >>> Library and Technology Services >>> (781) 736-4659 >>> 415 South Street, (MS 017/P.O. Box 549110) >>> Waltham, MA 02454-9110 >>> email: mauraa at brandeis.edu >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >> >> >> -- >> Maura Carbone >> Digital Initiatives Librarian >> Brandeis University >> Library and Technology Services >> (781) 736-4659 >> 415 South Street, (MS 017/P.O. Box 549110) >> Waltham, MA 02454-9110 >> email: mauraa at brandeis.edu >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: example_accession.csv Type: text/csv Size: 996 bytes Desc: not available URL: From mark.cooper at lyrasis.org Wed Apr 8 15:05:04 2015 From: mark.cooper at lyrasis.org (Mark Cooper) Date: Wed, 8 Apr 2015 19:05:04 +0000 Subject: [Archivesspace_Users_Group] Import EAD via the API? In-Reply-To: References: , Message-ID: <1428519903997.78136@lyrasis.org> Hi Dallas, Have you tried adding "charset=utf-8" to the content-type headers? Also feel free to send me an EAD file that produces the error and I'll try to look into it over the weekend. Best, Mark Mark Cooper Technical Lead, Hosting and Support LYRASIS email: mark.cooper at lyrasis.org skype: mark_c_cooper? ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Dallas Pillen Sent: Tuesday, April 7, 2015 9:09 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import EAD via the API? Thanks for the replies! Noah: we have talked about first importing our EADs into AT and then migrating to ArchivesSpace, but we're trying to do a lot of preliminary data cleanup and have made some modifications to the AS EAD importer in an attempt to make our legacy data as clean and AS-friendly as possible before migrating. Ideally, we'll account for most of the errors we've identified during our EAD cleanup and won't need to rely on the more forgiving nature of the AT importer. But it's something we're open to taking a look at at some point, at least as a supplemental error discovery/identification tool. Mark and Steve: Something along those lines just might work. As part of our EAD cleanup we are going through our extents, subjects, and other potential sources of namespace pollution so those sorts of issues will be controlled for in our EADs before our actual migration to AS. This should also make a pre-migration conversion to the AS JSONModel more feasible since, when we are ready to do so, our EADs will theoretically convert to the AS JSONModel with minimal errors. Mark, I tried your plugin on a batch of EADs and there were a few cases in which the conversion failed due to something like the following: (UndefinedConversionError) ""\xC3\xA9"" from UTF-8 to US-ASCII The EAD that threw this particular error has some '?' characters that the AS EAD converter imports without issue. Any thoughts on that? Other than that, converting our EADs to JSON and then bulk importing each of the JSON files would essentially accomplish what I was thinking of doing by importing EAD through the API. Still, like Noah, I'd still be interested in knowing if anyone else has figured out how to start EAD import jobs through the API, partially out of curiosity and also to be able to compare some of these potential conversion/import strategies. Thanks again for all the helpful suggestion! Dallas On Mon, Apr 6, 2015 at 4:35 PM, Steven Majewski > wrote: What I had been doing was running EADConverter locally on a batch of files, saving the JSON output if successful, and posting those JSON files to http://archivesspace.github.io/archivesspace/doc/file.API.html#post-repositoriesrepoidbatchimports ( This two stage process was also very useful in earlier versions when the error reporting was missing the context: ArchivesSpace would tell you what was missing, but it didn?t point to where it was missing from. It was possible to inspect the JSON and look for the null or missing value. ) You want to: converter = EADConverter.new( eadxml ) converter.run and then do something (move, copy or sent directly to batch_imports API) with: converter.get_output_path and if you wrap it in a begin/rescue block, you can catch and report the errors. I?ve experimented with a couple of variations on the error catching and processing. For example, if you move the JSON output in the ensure clause ( begin/rescue/ensure ), you can save the JSON to inspect even if it?s not complete enough to successfully import with /batch_imports, but you might not want to mix ?good? and ?bad? JSON in your output files. More recently, I?ve been experimenting with using an alternate EAD importer with looser schema validation rules. One problem with importing thousands of EAD files by this batch method is that we have had problems with ?namespace pollution? of the controlled vocab lists for extents and containers. These values are controlled from the webapp and editor, but importing from EAD adds to the values in the database. If you import a few EAD files at a time, it?s not difficult to merge and clean up these values, but importing several thousand EAD files that aren?t very controlled for those values led to an explosion that makes the drop down lists of those values unusable. See a previous message about this: http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2015-March/001216.html ? Steve Majewski / UVA Alderman Library On Apr 6, 2015, at 3:08 PM, Dallas Pillen > wrote: Hello all, I was curious if anyone has had any success starting EAD import jobs via the API? I was thinking this could be done using POST /repositories/:repo_id/jobs_with_files described here: http://archivesspace.github.io/archivesspace/doc/file.API.html#post-repositoriesrepoidjobswithfiles However, I am not entirely sure how the job and file parameters should be sent in the POST request, and I haven't seen anyone ask this question before or give an example of how it might work. I've tried sending the POST request several different ways and each time I am met with: {"error":{"job":["Parameter required but no value provided"],"files":["Parameter required but no value provided"]}}. I suppose it's worth mentioning that the reason I want to do this is that, at some point, we will be importing several thousand EADs into ArchivesSpace. We're doing a lot of preliminary work to make our EADs import successfully, but know there will likely be some that will fail. Right now, the only way to do a batch import of EADs is to do a batch as a single import job. If one EAD in that job has an error, the entire job fails. For that reason, I would like to be able to import each EAD as a separate job so that the EADs that will import successfully will do so without being impacted by the EADs with errors. However, starting several thousand individual import jobs would be very tedious, and I'm looking for a way to automate that process. If anyone else has come up with any creative solutions or knows of a better way to do that than the API, I would be very interested to know. The end goal would be to have a script that would batch start the import jobs, get the ID for each job, check up on the jobs every so often and, once there are no longer any active jobs, output some information about each of the jobs that failed. I've figured out how to do most of that using the API, but I'm stumped on how to get the whole process started. Thanks! Dallas -- Dallas Pillen Project Archivist [https://webapps.lsa.umich.edu/dean/lsa_emails/bentley-sig-em.png] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook _______________________________________________ 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 -- Dallas Pillen Project Archivist [https://webapps.lsa.umich.edu/dean/lsa_emails/bentley-sig-em.png] Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From mang.sun at rice.edu Wed Apr 8 15:35:00 2015 From: mang.sun at rice.edu (Mang Sun) Date: Wed, 08 Apr 2015 14:35:00 -0500 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: <1428479992653.18332@lyrasis.org> References: <551D6503.8000500@rice.edu> <5522BEFE.6090502@rice.edu> <5523048E.9060801@rice.edu> , <55240534.1010502@rice.edu> <1428479992653.18332@lyrasis.org> Message-ID: <552582E4.4090305@rice.edu> Thank you Chris. I need to clarify that the problem I ever reported is only with the development application (public interface) running at 3001. For the compiled, built and deployed applications, i don't see any problem with this link. Today, I also cloned the newest plugin to replace the existing one from GitHub, restarted all the development applications and the problem is still there with the development server (Public Interface) running at 3001. But again once the applications got built and deployed (using "archivesspace.sh start"), the problem is gone. Mang. On 4/8/2015 2:59 AM, Chris Fitzpatrick wrote: > > Hi Everyone, > > > It looks like the generate PDF as a background job in version 1.2.0 > broke the aspace-public-formats plugin PDF export feature. > > I've fixed the plugin here : > https://github.com/archivesspace/aspace-public-formats > > If you need this feature, please remove the version of the plugin you > have currently installed and replace it with the version on github and > restart ASpace. > > > Also, please note that the public-format plugin PDF feature will not > work for large resources. > > > Sorry about the inconvenience. Let us know if you have other issues or > questions... > > b,chris. > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ------------------------------------------------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Mang Sun > *Sent:* Tuesday, April 7, 2015 6:26 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] The ead_pdf link generated > by plugin public_formats_resource_links does not work with AS 1.2 > > Thank you again Brad. I also have tested this version on MAC OS X and > still see the same issue with the ead_pdf link of this plugin. > > Mang > > > On 4/7/2015 6:15 AM, Brad Westbrook wrote: >> >> Windows 7, Mang. >> >> Brad >> >> *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org >> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] *On >> Behalf Of *Mang Sun >> *Sent:* Monday, April 06, 2015 6:11 PM >> *To:* Archivesspace Users Group >> *Subject:* Re: [Archivesspace_Users_Group] The ead_pdf link generated >> by plugin public_formats_resource_links does not work with AS 1.2 >> >> By the way, under which OS is your AS 1.2 running ? Mine is Redhat 6.4. >> >> Mang >> >> On 4/6/2015 12:47 PM, Brad Westbrook wrote: >> >> Hi, Mang >> >> I just successfully tested the public formats plugin for all >> three options. I tested it in a localhost install using the >> embedded Derby database. >> >> Brad W. >> >> *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org >> >> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] >> *On Behalf Of *Mang Sun >> *Sent:* Monday, April 06, 2015 1:15 PM >> *To:* Archivesspace Users Group >> *Subject:* Re: [Archivesspace_Users_Group] The ead_pdf link >> generated by plugin public_formats_resource_links does not work >> with AS 1.2 >> >> Can somebody or the development team confirm whether the >> public_formats_resource_links plugin still works with AS 1.2? >> >> Mang Sun >> Rice U. >> >> On 4/2/2015 10:49 AM, Mang Sun wrote: >> >> When clicking the ead_pdf link turned on by the >> public_formats_resource_links plugin does not work with AS >> 1.2 throwing the error message as follows. -Mang Sun >> Rice U. >> >> >> EOFError in PublicFormatsController#generate >> >> |Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public| >> >> >> Request >> >> *Parameters*: >> >> {"repo_id"=>"2", >> >> "type"=>"resources", >> >> "id"=>"116", >> >> "format"=>"ead_pdf"} >> >> Show session dump >> >> >> _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" >> >> session_id: "c419289cb412f46af571004e4b0c0830" >> >> Show env dump >> >> >> GATEWAY_INTERFACE: "CGI/1.2" >> >> HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" >> >> HTTP_ACCEPT_ENCODING: "gzip, deflate" >> >> HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" >> >> REMOTE_ADDR: "10.xx.xx.xx" >> >> SERVER_NAME: "10.xx.22.xx" >> >> SERVER_PROTOCOL: "HTTP/1.1" >> >> >> Response >> >> *Headers*: >> >> None >> >> ----------------- >> >> The Full trace is pasted as below. >> >> >> >> |org/jruby/RubyIO.java:2858:in `read_nonblock'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request'| >> >> |org/jruby/RubyKernel.java:1270:in `catch'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle'| >> >> |/opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate'| >> >> |actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action'| >> >> |actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action'| >> >> |actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action'| >> >> |actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action'| >> >> |activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks'| >> >> |activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback'| >> >> |activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks'| >> >> |activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks'| >> >> |actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action'| >> >> |actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action'| >> >> |actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action'| >> >> |activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument'| >> >> |activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument'| >> >> |activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument'| >> >> |activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument'| >> >> |actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action'| >> >> |actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action'| >> >> |actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process'| >> >> |actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process'| >> >> |actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch'| >> >> |actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch'| >> >> |actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action'| >> >> |org/jruby/RubyProc.java:271:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch'| >> >> |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call'| >> >> |journey (1.0.4) lib/journey/router.rb:68:in `call'| >> >> |org/jruby/RubyArray.java:1613:in `each'| >> >> |journey (1.0.4) lib/journey/router.rb:56:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call'| >> >> |rack (1.4.5) lib/rack/etag.rb:23:in `call'| >> >> |rack (1.4.5) lib/rack/conditionalget.rb:25:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call'| >> >> |rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context'| >> >> |rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call'| >> >> |activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks'| >> >> |activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback'| >> >> |activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks'| >> >> |activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'| >> >> |railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app'| >> >> |railties (3.2.19) lib/rails/rack/logger.rb:16:in `call'| >> >> |activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged'| >> >> |railties (3.2.19) lib/rails/rack/logger.rb:16:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call'| >> >> |rack (1.4.5) lib/rack/methodoverride.rb:21:in `call'| >> >> |rack (1.4.5) lib/rack/runtime.rb:17:in `call'| >> >> |activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call'| >> >> |rack (1.4.5) lib/rack/lock.rb:15:in `call'| >> >> |actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call'| >> >> |railties (3.2.19) lib/rails/engine.rb:484:in `call'| >> >> |railties (3.2.19) lib/rails/application.rb:231:in `call'| >> >> |rack (1.4.5) lib/rack/content_length.rb:14:in `call'| >> >> |railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call'| >> >> |puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request'| >> >> |puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request'| >> >> |puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client'| >> >> |puma-2.8.2 (java) lib/puma/server.rb:254:in `run'| >> >> |org/jruby/RubyProc.java:271:in `call'| >> >> |puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread'| >> >> >> >> >> >> >> >> _______________________________________________ >> >> Archivesspace_Users_Group mailing list >> >> Archivesspace_Users_Group at lyralists.lyrasis.org >> >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> >> _______________________________________________ >> >> Archivesspace_Users_Group mailing list >> >> Archivesspace_Users_Group at lyralists.lyrasis.org >> >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From PGalligan at rockarch.org Wed Apr 8 16:36:54 2015 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Wed, 8 Apr 2015 16:36:54 -0400 Subject: [Archivesspace_Users_Group] Note audience in EAD impor Message-ID: Hi all, I've been experimenting with EAD import into AS for a collection of about 50,000 components, and I had a few questions about having the system publish notes. Each component has a few notes attached to it, some that we want published, and some that we don't. I assumed that AS would default to publishing notes without audience="internal," but that does not appear to be the case. Some guidance on how to get the system to publish specific notes through EAD import would be appreciated if anyone has experience with that. We don't do much EAD importing into the system here, so I don't have tons of experience getting this to work. Thanks! Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Wed Apr 8 16:57:49 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Wed, 8 Apr 2015 16:57:49 -0400 Subject: [Archivesspace_Users_Group] Note audience in EAD impor In-Reply-To: References: Message-ID: Hi Patrick, I believe you'd have to modify the ead_converter.rb and add: :publish => att('audience') != 'internal' in the relevant sections of the converter that deal with the types of notes you're bringing in and load it as a plugin. If these are all general notes (), you'd need to do something like: %w(accessrestrict accessrestrict/legalstatus \ accruals acqinfo altformavail appraisal arrangement \ bioghist custodhist dimensions \ fileplan odd otherfindaid originalsloc phystech \ prefercite processinfo relatedmaterial scopecontent \ separatedmaterial userestrict ).each do |note| with note do |node| content = inner_xml.tap {|xml| xml.sub!(/.*?<\/head>/m, '') # xml.sub!(/]*>.*?<\/list>/m, '') # xml.sub!(/]*>.*<\/chronlist>/m, '') } make :note_multipart, { :type => node.name, :persistent_id => att('id'), :publish => att('audience') != 'internal' <---- add this at line 324 in the file. :subnotes => { 'jsonmodel_type' => 'note_text', 'content' => format_content( content ) } } do |note| set ancestor(:resource, :archival_object), :notes, note end end end I did something like this for agent creation and it worked so you can try it with the notes and see if it helps! -Maura On Wed, Apr 8, 2015 at 4:36 PM, Galligan, Patrick wrote: > Hi all, > > > > I?ve been experimenting with EAD import into AS for a collection of about > 50,000 components, and I had a few questions about having the system > publish notes. > > > > Each component has a few notes attached to it, some that we want > published, and some that we don?t. I assumed that AS would default to > publishing notes without audience=?internal,? but that does not appear to > be the case. > > > > Some guidance on how to get the system to publish specific notes through > EAD import would be appreciated if anyone has experience with that. We > don?t do much EAD importing into the system here, so I don?t have tons of > experience getting this to work. > > > > Thanks! > > > > Patrick Galligan > > Rockefeller Archive Center > > Assistant Digital Archivist > > 914-366-6386 > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From sdm7g at virginia.edu Wed Apr 8 21:24:23 2015 From: sdm7g at virginia.edu (Steven Majewski) Date: Wed, 8 Apr 2015 21:24:23 -0400 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: <552582E4.4090305@rice.edu> References: <551D6503.8000500@rice.edu> <5522BEFE.6090502@rice.edu> <5523048E.9060801@rice.edu> , <55240534.1010502@rice.edu> <1428479992653.18332@lyrasis.org> <552582E4.4090305@rice.edu> Message-ID: Sorry: I didn?t catch that distinction the first time. Running the development server, it also does not work for me under OSX. I can?t say that I totally understand what?s going on and why it would work in one environment and not another, but changing this one line made it work for me under devserver: diff --git a/backend/app/lib/AS_fop.rb b/backend/app/lib/AS_fop.rb index 9b95762..a042cd9 100644 --- a/backend/app/lib/AS_fop.rb +++ b/backend/app/lib/AS_fop.rb @@ -44,7 +44,7 @@ class ASFop res = SAXResult.new(fop.getDefaultHandler) transformer.transform(StreamSource.new(fo), res) ensure - @output.close + @output.rewind end @output end On Apr 8, 2015, at 3:35 PM, Mang Sun wrote: > Thank you Chris. I need to clarify that the problem I ever reported is only with the development application (public interface) running at 3001. > For the compiled, built and deployed applications, i don't see any problem with this link. Today, I also cloned the newest plugin to replace the existing one from GitHub, restarted all the development applications and the problem is still there with the development server (Public Interface) running at 3001. But again once the applications got built and deployed (using "archivesspace.sh start"), the problem is gone. > Mang. > > On 4/8/2015 2:59 AM, Chris Fitzpatrick wrote: >> Hi Everyone, >> >> It looks like the generate PDF as a background job in version 1.2.0 broke the aspace-public-formats plugin PDF export feature. >> I've fixed the plugin here : https://github.com/archivesspace/aspace-public-formats >> If you need this feature, please remove the version of the plugin you have currently installed and replace it with the version on github and restart ASpace. >> >> Also, please note that the public-format plugin PDF feature will not work for large resources. >> >> Sorry about the inconvenience. Let us know if you have other issues or questions... >> b,chris. >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mang Sun >> Sent: Tuesday, April 7, 2015 6:26 PM >> To: Archivesspace Users Group >> Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 >> >> >> Thank you again Brad. I also have tested this version on MAC OS X and still see the same issue with the ead_pdf link of this plugin. >> >> Mang >> >> >> On 4/7/2015 6:15 AM, Brad Westbrook wrote: >>> Windows 7, Mang. >>> >>> Brad >>> >>> >>> From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mang Sun >>> Sent: Monday, April 06, 2015 6:11 PM >>> To: Archivesspace Users Group >>> Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 >>> >>> By the way, under which OS is your AS 1.2 running ? Mine is Redhat 6.4. >>> >>> Mang >>> On 4/6/2015 12:47 PM, Brad Westbrook wrote: >>> Hi, Mang >>> >>> I just successfully tested the public formats plugin for all three options. I tested it in a localhost install using the embedded Derby database. >>> >>> Brad W. >>> >>> From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mang Sun >>> Sent: Monday, April 06, 2015 1:15 PM >>> To: Archivesspace Users Group >>> Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 >>> >>> Can somebody or the development team confirm whether the public_formats_resource_links plugin still works with AS 1.2? >>> >>> Mang Sun >>> Rice U. >>> On 4/2/2015 10:49 AM, Mang Sun wrote: >>> When clicking the ead_pdf link turned on by the public_formats_resource_links plugin does not work with AS 1.2 throwing the error message as follows. -Mang Sun Rice U. >>> EOFError in PublicFormatsController#generate >>> >>> Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public >>> >>> >>> Request >>> >>> Parameters: >>> {"repo_id"=>"2", >>> "type"=>"resources", >>> "id"=>"116", >>> "format"=>"ead_pdf"} >>> Show session dump >>> _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" >>> session_id: "c419289cb412f46af571004e4b0c0830" >>> Show env dump >>> GATEWAY_INTERFACE: "CGI/1.2" >>> HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" >>> HTTP_ACCEPT_ENCODING: "gzip, deflate" >>> HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" >>> REMOTE_ADDR: "10.xx.xx.xx" >>> SERVER_NAME: "10.xx.22.xx" >>> SERVER_PROTOCOL: "HTTP/1.1" >>> Response >>> >>> Headers: >>> None >>> ----------------- >>> The Full trace is pasted as below. >>> >>> org/jruby/RubyIO.java:2858:in `read_nonblock' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request' >>> org/jruby/RubyKernel.java:1270:in `catch' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start' >>> /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request' >>> /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle' >>> /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate' >>> actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action' >>> actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action' >>> actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action' >>> actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action' >>> activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks' >>> activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' >>> activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks' >>> activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' >>> actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action' >>> actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action' >>> actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action' >>> activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' >>> activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument' >>> activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument' >>> activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' >>> actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action' >>> actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action' >>> actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process' >>> actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process' >>> actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch' >>> actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch' >>> actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action' >>> org/jruby/RubyProc.java:271:in `call' >>> actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch' >>> actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call' >>> journey (1.0.4) lib/journey/router.rb:68:in `call' >>> org/jruby/RubyArray.java:1613:in `each' >>> journey (1.0.4) lib/journey/router.rb:56:in `call' >>> actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call' >>> actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call' >>> rack (1.4.5) lib/rack/etag.rb:23:in `call' >>> rack (1.4.5) lib/rack/conditionalget.rb:25:in `call' >>> actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call' >>> actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call' >>> actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call' >>> rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context' >>> rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call' >>> actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call' >>> actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call' >>> activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks' >>> activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' >>> activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks' >>> activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' >>> actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call' >>> actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call' >>> actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call' >>> actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call' >>> actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' >>> railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app' >>> railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' >>> activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged' >>> railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' >>> actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call' >>> rack (1.4.5) lib/rack/methodoverride.rb:21:in `call' >>> rack (1.4.5) lib/rack/runtime.rb:17:in `call' >>> activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call' >>> rack (1.4.5) lib/rack/lock.rb:15:in `call' >>> actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call' >>> railties (3.2.19) lib/rails/engine.rb:484:in `call' >>> railties (3.2.19) lib/rails/application.rb:231:in `call' >>> rack (1.4.5) lib/rack/content_length.rb:14:in `call' >>> railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call' >>> puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request' >>> puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request' >>> puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client' >>> puma-2.8.2 (java) lib/puma/server.rb:254:in `run' >>> org/jruby/RubyProc.java:271:in `call' >>> puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread' >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4943 bytes Desc: not available URL: From Chris.Fitzpatrick at lyrasis.org Thu Apr 9 08:41:46 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 9 Apr 2015 12:41:46 +0000 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: <552582E4.4090305@rice.edu> References: <551D6503.8000500@rice.edu> <5522BEFE.6090502@rice.edu> <5523048E.9060801@rice.edu> , <55240534.1010502@rice.edu> <1428479992653.18332@lyrasis.org>,<552582E4.4090305@rice.edu> Message-ID: <1428583305170.49413@lyrasis.org> Hi Mang, Ah, ok...so can you try and do a pull from the archivesspace git repo? I think the fix for running it in devserver mode should be in my last commit. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mang Sun Sent: Wednesday, April 8, 2015 9:35 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 Thank you Chris. I need to clarify that the problem I ever reported is only with the development application (public interface) running at 3001. For the compiled, built and deployed applications, i don't see any problem with this link. Today, I also cloned the newest plugin to replace the existing one from GitHub, restarted all the development applications and the problem is still there with the development server (Public Interface) running at 3001. But again once the applications got built and deployed (using "archivesspace.sh start"), the problem is gone. Mang. On 4/8/2015 2:59 AM, Chris Fitzpatrick wrote: Hi Everyone, It looks like the generate PDF as a background job in version 1.2.0 broke the aspace-public-formats plugin PDF export feature. I've fixed the plugin here : https://github.com/archivesspace/aspace-public-formats If you need this feature, please remove the version of the plugin you have currently installed and replace it with the version on github and restart ASpace. Also, please note that the public-format plugin PDF feature will not work for large resources. Sorry about the inconvenience. Let us know if you have other issues or questions... b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Mang Sun Sent: Tuesday, April 7, 2015 6:26 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 Thank you again Brad. I also have tested this version on MAC OS X and still see the same issue with the ead_pdf link of this plugin. Mang On 4/7/2015 6:15 AM, Brad Westbrook wrote: Windows 7, Mang. Brad From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mang Sun Sent: Monday, April 06, 2015 6:11 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 By the way, under which OS is your AS 1.2 running ? Mine is Redhat 6.4. Mang On 4/6/2015 12:47 PM, Brad Westbrook wrote: Hi, Mang I just successfully tested the public formats plugin for all three options. I tested it in a localhost install using the embedded Derby database. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Mang Sun Sent: Monday, April 06, 2015 1:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 Can somebody or the development team confirm whether the public_formats_resource_links plugin still works with AS 1.2? Mang Sun Rice U. On 4/2/2015 10:49 AM, Mang Sun wrote: When clicking the ead_pdf link turned on by the public_formats_resource_links plugin does not work with AS 1.2 throwing the error message as follows. -Mang Sun Rice U. EOFError in PublicFormatsController#generate Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public Request Parameters: {"repo_id"=>"2", "type"=>"resources", "id"=>"116", "format"=>"ead_pdf"} Show session dump _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" session_id: "c419289cb412f46af571004e4b0c0830" Show env dump GATEWAY_INTERFACE: "CGI/1.2" HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" HTTP_ACCEPT_ENCODING: "gzip, deflate" HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" REMOTE_ADDR: "10.xx.xx.xx" SERVER_NAME: "10.xx.22.xx" SERVER_PROTOCOL: "HTTP/1.1" Response Headers: None ----------------- The Full trace is pasted as below. org/jruby/RubyIO.java:2858:in `read_nonblock' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request' org/jruby/RubyKernel.java:1270:in `catch' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start' /opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request' /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle' /opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate' actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action' actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action' actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action' actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action' activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action' actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action' actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action' activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument' activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument' activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument' actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action' actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action' actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process' actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process' actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch' actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch' actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action' org/jruby/RubyProc.java:271:in `call' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call' journey (1.0.4) lib/journey/router.rb:68:in `call' org/jruby/RubyArray.java:1613:in `each' journey (1.0.4) lib/journey/router.rb:56:in `call' actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call' rack (1.4.5) lib/rack/etag.rb:23:in `call' rack (1.4.5) lib/rack/conditionalget.rb:25:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call' rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context' rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call' activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback' activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks' activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks' actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call' railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app' railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged' railties (3.2.19) lib/rails/rack/logger.rb:16:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call' rack (1.4.5) lib/rack/methodoverride.rb:21:in `call' rack (1.4.5) lib/rack/runtime.rb:17:in `call' activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call' rack (1.4.5) lib/rack/lock.rb:15:in `call' actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call' railties (3.2.19) lib/rails/engine.rb:484:in `call' railties (3.2.19) lib/rails/application.rb:231:in `call' rack (1.4.5) lib/rack/content_length.rb:14:in `call' railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call' puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request' puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request' puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client' puma-2.8.2 (java) lib/puma/server.rb:254:in `run' org/jruby/RubyProc.java:271:in `call' puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread' _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From mang.sun at rice.edu Thu Apr 9 10:23:50 2015 From: mang.sun at rice.edu (Mang Sun) Date: Thu, 09 Apr 2015 09:23:50 -0500 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: <1428583305170.49413@lyrasis.org> References: <551D6503.8000500@rice.edu> <5522BEFE.6090502@rice.edu> <5523048E.9060801@rice.edu> , <55240534.1010502@rice.edu> <1428479992653.18332@lyrasis.org>, <552582E4.4090305@rice.edu> <1428583305170.49413@lyrasis.org> Message-ID: <55268B76.2000604@rice.edu> I will try this. Thank you very much Chris. Mang On 4/9/2015 7:41 AM, Chris Fitzpatrick wrote: > > Hi Mang, > > > Ah, ok...so can you try and do a pull from the archivesspace git repo? > > I think the fix for running it in devserver mode should be in my last > commit. > > > b,chris. > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ------------------------------------------------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of > Mang Sun > *Sent:* Wednesday, April 8, 2015 9:35 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] The ead_pdf link generated > by plugin public_formats_resource_links does not work with AS 1.2 > Thank you Chris. I need to clarify that the problem I ever reported > is only with the development application (public interface) running at > 3001. > For the compiled, built and deployed applications, i don't see any > problem with this link. Today, I also cloned the newest plugin to > replace the existing one from GitHub, restarted all the development > applications and the problem is still there with the development > server (Public Interface) running at 3001. But again once the > applications got built and deployed (using "archivesspace.sh start"), > the problem is gone. > Mang. > > On 4/8/2015 2:59 AM, Chris Fitzpatrick wrote: >> >> Hi Everyone, >> >> >> It looks like the generate PDF as a background job in version 1.2.0 >> broke the aspace-public-formats plugin PDF export feature. >> >> I've fixed the plugin here : >> https://github.com/archivesspace/aspace-public-formats >> >> If you need this feature, please remove the version of the plugin you >> have currently installed and replace it with the version on github >> and restart ASpace. >> >> >> Also, please note that the public-format plugin PDF feature will not >> work for large resources. >> >> >> Sorry about the inconvenience. Let us know if you have other issues >> or questions... >> >> b,chris. >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> ------------------------------------------------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org >> on behalf >> of Mang Sun >> *Sent:* Tuesday, April 7, 2015 6:26 PM >> *To:* Archivesspace Users Group >> *Subject:* Re: [Archivesspace_Users_Group] The ead_pdf link generated >> by plugin public_formats_resource_links does not work with AS 1.2 >> >> Thank you again Brad. I also have tested this version on MAC OS X >> and still see the same issue with the ead_pdf link of this plugin. >> >> Mang >> >> >> On 4/7/2015 6:15 AM, Brad Westbrook wrote: >>> >>> Windows 7, Mang. >>> >>> Brad >>> >>> *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org >>> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] *On >>> Behalf Of *Mang Sun >>> *Sent:* Monday, April 06, 2015 6:11 PM >>> *To:* Archivesspace Users Group >>> *Subject:* Re: [Archivesspace_Users_Group] The ead_pdf link >>> generated by plugin public_formats_resource_links does not work with >>> AS 1.2 >>> >>> By the way, under which OS is your AS 1.2 running ? Mine is Redhat 6.4. >>> >>> Mang >>> >>> On 4/6/2015 12:47 PM, Brad Westbrook wrote: >>> >>> Hi, Mang >>> >>> I just successfully tested the public formats plugin for all >>> three options. I tested it in a localhost install using the >>> embedded Derby database. >>> >>> Brad W. >>> >>> *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org >>> >>> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] >>> *On Behalf Of *Mang Sun >>> *Sent:* Monday, April 06, 2015 1:15 PM >>> *To:* Archivesspace Users Group >>> *Subject:* Re: [Archivesspace_Users_Group] The ead_pdf link >>> generated by plugin public_formats_resource_links does not work >>> with AS 1.2 >>> >>> Can somebody or the development team confirm whether the >>> public_formats_resource_links plugin still works with AS 1.2? >>> >>> Mang Sun >>> Rice U. >>> >>> On 4/2/2015 10:49 AM, Mang Sun wrote: >>> >>> When clicking the ead_pdf link turned on by the >>> public_formats_resource_links plugin does not work with AS >>> 1.2 throwing the error message as follows. -Mang Sun >>> Rice U. >>> >>> >>> EOFError in PublicFormatsController#generate >>> >>> |Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public| >>> >>> >>> Request >>> >>> *Parameters*: >>> >>> {"repo_id"=>"2", >>> >>> "type"=>"resources", >>> >>> "id"=>"116", >>> >>> "format"=>"ead_pdf"} >>> >>> Show session dump >>> >>> >>> _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" >>> >>> session_id: "c419289cb412f46af571004e4b0c0830" >>> >>> Show env dump >>> >>> >>> GATEWAY_INTERFACE: "CGI/1.2" >>> >>> HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" >>> >>> HTTP_ACCEPT_ENCODING: "gzip, deflate" >>> >>> HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" >>> >>> REMOTE_ADDR: "10.xx.xx.xx" >>> >>> SERVER_NAME: "10.xx.22.xx" >>> >>> SERVER_PROTOCOL: "HTTP/1.1" >>> >>> >>> Response >>> >>> *Headers*: >>> >>> None >>> >>> ----------------- >>> >>> The Full trace is pasted as below. >>> >>> >>> >>> |org/jruby/RubyIO.java:2858:in `read_nonblock'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request'| >>> >>> |org/jruby/RubyKernel.java:1270:in `catch'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle'| >>> >>> |/opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate'| >>> >>> |actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action'| >>> >>> |actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action'| >>> >>> |actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action'| >>> >>> |actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action'| >>> >>> |activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks'| >>> >>> |activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback'| >>> >>> |activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks'| >>> >>> |activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks'| >>> >>> |actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action'| >>> >>> |actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action'| >>> >>> |actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action'| >>> >>> |activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument'| >>> >>> |activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument'| >>> >>> |activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument'| >>> >>> |activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument'| >>> >>> |actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action'| >>> >>> |actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action'| >>> >>> |actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process'| >>> >>> |actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process'| >>> >>> |actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch'| >>> >>> |actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch'| >>> >>> |actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action'| >>> >>> |org/jruby/RubyProc.java:271:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call'| >>> >>> |journey (1.0.4) lib/journey/router.rb:68:in `call'| >>> >>> |org/jruby/RubyArray.java:1613:in `each'| >>> >>> |journey (1.0.4) lib/journey/router.rb:56:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call'| >>> >>> |rack (1.4.5) lib/rack/etag.rb:23:in `call'| >>> >>> |rack (1.4.5) lib/rack/conditionalget.rb:25:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call'| >>> >>> |rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context'| >>> >>> |rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call'| >>> >>> |activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks'| >>> >>> |activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback'| >>> >>> |activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks'| >>> >>> |activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'| >>> >>> |railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app'| >>> >>> |railties (3.2.19) lib/rails/rack/logger.rb:16:in `call'| >>> >>> |activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged'| >>> >>> |railties (3.2.19) lib/rails/rack/logger.rb:16:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call'| >>> >>> |rack (1.4.5) lib/rack/methodoverride.rb:21:in `call'| >>> >>> |rack (1.4.5) lib/rack/runtime.rb:17:in `call'| >>> >>> |activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call'| >>> >>> |rack (1.4.5) lib/rack/lock.rb:15:in `call'| >>> >>> |actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call'| >>> >>> |railties (3.2.19) lib/rails/engine.rb:484:in `call'| >>> >>> |railties (3.2.19) lib/rails/application.rb:231:in `call'| >>> >>> |rack (1.4.5) lib/rack/content_length.rb:14:in `call'| >>> >>> |railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call'| >>> >>> |puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request'| >>> >>> |puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request'| >>> >>> |puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client'| >>> >>> |puma-2.8.2 (java) lib/puma/server.rb:254:in `run'| >>> >>> |org/jruby/RubyProc.java:271:in `call'| >>> >>> |puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread'| >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> Archivesspace_Users_Group mailing list >>> >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> >>> >>> _______________________________________________ >>> >>> Archivesspace_Users_Group mailing list >>> >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > 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 mang.sun at rice.edu Thu Apr 9 11:22:08 2015 From: mang.sun at rice.edu (Mang Sun) Date: Thu, 09 Apr 2015 10:22:08 -0500 Subject: [Archivesspace_Users_Group] The ead_pdf link generated by plugin public_formats_resource_links does not work with AS 1.2 In-Reply-To: References: <551D6503.8000500@rice.edu> <5522BEFE.6090502@rice.edu> <5523048E.9060801@rice.edu> , <55240534.1010502@rice.edu> <1428479992653.18332@lyrasis.org> <552582E4.4090305@rice.edu> Message-ID: <55269920.8000606@rice.edu> Yes, Steven, by following your way, I changed line 47 from @output.close to @output.rewind and now I see the problem is gone. Good catch. Thank you very much. Mang On 4/8/2015 8:24 PM, Steven Majewski wrote: > > Sorry: I didn?t catch that distinction the first time. > Running the development server, it also does not work for me under OSX. > > I can?t say that I totally understand what?s going on and why it would > work > in one environment and not another, but changing this one line made it > work > for me under devserver: > > *diff --git a/backend/app/lib/AS_fop.rb b/backend/app/lib/AS_fop.rb* > *index 9b95762..a042cd9 100644* > *--- a/backend/app/lib/AS_fop.rb* > *+++ b/backend/app/lib/AS_fop.rb* > @@ -44,7 +44,7 @@class ASFop > res = SAXResult.new(fop.getDefaultHandler) > transformer.transform(StreamSource.new(fo), res) > ensure > - @output.close > + @output.rewind > end > @output > end > > > > On Apr 8, 2015, at 3:35 PM, Mang Sun > wrote: > >> Thank you Chris. I need to clarify that the problem I ever reported >> is only with the development application (public interface) running >> at 3001. >> For the compiled, built and deployed applications, i don't see any >> problem with this link. Today, I also cloned the newest plugin to >> replace the existing one from GitHub, restarted all the development >> applications and the problem is still there with the development >> server (Public Interface) running at 3001. But again once the >> applications got built and deployed (using "archivesspace.sh start"), >> the problem is gone. >> Mang. >> >> On 4/8/2015 2:59 AM, Chris Fitzpatrick wrote: >>> Hi Everyone, >>> >>> It looks like the generate PDF as a background job in version 1.2.0 >>> broke the aspace-public-formats plugin PDF export feature. >>> I've fixed the plugin here >>> :https://github.com/archivesspace/aspace-public-formats >>> If you need this feature, please remove the version of the plugin >>> you have currently installed and replace it with the version on >>> github and restart ASpace. >>> >>> Also, please note that the public-format plugin PDF feature will not >>> work for large resources. >>> >>> Sorry about the inconvenience. Let us know if you have other issues >>> or questions... >>> b,chris. >>> >>> Chris Fitzpatrick | Developer, ArchivesSpace >>> Skype: chrisfitzpat | Phone: 918.236.6048 >>> http://archivesspace.org/ >>> ------------------------------------------------------------------------ >>> *From:*archivesspace_users_group-bounces at lyralists.lyrasis.orgon >>> behalf of Mang Sun >>> *Sent:*Tuesday, April 7, 2015 6:26 PM >>> *To:*Archivesspace Users Group >>> *Subject:*Re: [Archivesspace_Users_Group] The ead_pdf link generated >>> by plugin public_formats_resource_links does not work with AS 1.2 >>> >>> Thank you again Brad. I also have tested this version on MAC OS X >>> and still see the same issue with the ead_pdf link of this plugin. >>> >>> Mang >>> >>> >>> On 4/7/2015 6:15 AM, Brad Westbrook wrote: >>>> Windows 7, Mang. >>>> >>>> Brad >>>> >>>> *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org[mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org]*On >>>> Behalf Of*Mang Sun >>>> *Sent:*Monday, April 06, 2015 6:11 PM >>>> *To:*Archivesspace Users Group >>>> *Subject:*Re: [Archivesspace_Users_Group] The ead_pdf link >>>> generated by plugin public_formats_resource_links does not work >>>> with AS 1.2 >>>> >>>> By the way, under which OS is your AS 1.2 running ? Mine is Redhat >>>> 6.4. >>>> >>>> Mang >>>> On 4/6/2015 12:47 PM, Brad Westbrook wrote: >>>> >>>> Hi, Mang >>>> >>>> I just successfully tested the public formats plugin for all >>>> three options. I tested it in a localhost install using the >>>> embedded Derby database. >>>> >>>> Brad W. >>>> >>>> *From:*archivesspace_users_group-bounces at lyralists.lyrasis.org >>>> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org]*On >>>> Behalf Of*Mang Sun >>>> *Sent:*Monday, April 06, 2015 1:15 PM >>>> *To:*Archivesspace Users Group >>>> *Subject:*Re: [Archivesspace_Users_Group] The ead_pdf link >>>> generated by plugin public_formats_resource_links does not work >>>> with AS 1.2 >>>> >>>> Can somebody or the development team confirm whether the >>>> public_formats_resource_links plugin still works with AS 1.2? >>>> >>>> Mang Sun >>>> Rice U. >>>> On 4/2/2015 10:49 AM, Mang Sun wrote: >>>> >>>> When clicking the ead_pdf link turned on by the >>>> public_formats_resource_links plugin does not work with AS >>>> 1.2 throwing the error message as follows. -Mang Sun >>>> Rice U. >>>> >>>> >>>> EOFError in PublicFormatsController#generate >>>> >>>> |Rails.root: /opt/download/ASpace/archivesspace-1.2.0/public| >>>> >>>> >>>> Request >>>> >>>> *Parameters*: >>>> >>>> {"repo_id"=>"2", >>>> >>>> "type"=>"resources", >>>> >>>> "id"=>"116", >>>> >>>> "format"=>"ead_pdf"} >>>> >>>> Show session dump >>>> >>>> >>>> _csrf_token: "PSHg/+xWc6vsA3SkFp5yNu544UvTf9agbMpz6ZY3ir0=" >>>> >>>> session_id: "c419289cb412f46af571004e4b0c0830" >>>> >>>> Show env dump >>>> >>>> >>>> GATEWAY_INTERFACE: "CGI/1.2" >>>> >>>> HTTP_ACCEPT: "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8" >>>> >>>> HTTP_ACCEPT_ENCODING: "gzip, deflate" >>>> >>>> HTTP_ACCEPT_LANGUAGE: "en-US,en;q=0.5" >>>> >>>> REMOTE_ADDR: "10.xx.xx.xx" >>>> >>>> SERVER_NAME: "10.xx.22.xx" >>>> >>>> SERVER_PROTOCOL: "HTTP/1.1" >>>> >>>> >>>> Response >>>> >>>> *Headers*: >>>> >>>> None >>>> >>>> ----------------- >>>> >>>> The Full trace is pasted as below. >>>> >>>> >>>> >>>> |org/jruby/RubyIO.java:2858:in `read_nonblock'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:141:in `rbuf_fill'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:122:in `readuntil'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/protocol.rb:132:in `readline'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2779:in `read_chunked'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2759:in `read_body_0'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2719:in `read_body'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2744:in `body'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:2681:in `reading_body'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1330:in `transport_request'| >>>> >>>> |org/jruby/RubyKernel.java:1270:in `catch'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1325:in `transport_request'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1302:in `request'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1295:in `request'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:746:in `start'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/build/jruby-complete-1.7.18.jar!/META-INF/jruby.home/lib/ruby/1.9/net/http.rb:1293:in `request'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:18:in `handle'| >>>> >>>> |/opt/download/ASpace/archivesspace-1.2.0/plugins/aspace-public-formats/public/controllers/public_formats_controller.rb:5:in `generate'| >>>> >>>> |actionpack (3.2.19) lib/action_controller/metal/implicit_render.rb:4:in `send_action'| >>>> >>>> |actionpack (3.2.19) lib/abstract_controller/base.rb:167:in `process_action'| >>>> >>>> |actionpack (3.2.19) lib/action_controller/metal/rendering.rb:10:in `process_action'| >>>> >>>> |actionpack (3.2.19) lib/abstract_controller/callbacks.rb:18:in `process_action'| >>>> >>>> |activesupport (3.2.19) lib/active_support/callbacks.rb:439:in `_run__487387345__process_action__240924115__callbacks'| >>>> >>>> |activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback'| >>>> >>>> |activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_process_action_callbacks'| >>>> >>>> |activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks'| >>>> >>>> |actionpack (3.2.19) lib/abstract_controller/callbacks.rb:17:in `process_action'| >>>> >>>> |actionpack (3.2.19) lib/action_controller/metal/rescue.rb:29:in `process_action'| >>>> >>>> |actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:30:in `process_action'| >>>> >>>> |activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument'| >>>> >>>> |activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:20:in `instrument'| >>>> >>>> |activesupport (3.2.19) lib/active_support/notifications/instrumenter.rb:19:in `instrument'| >>>> >>>> |activesupport (3.2.19) lib/active_support/notifications.rb:123:in `instrument'| >>>> >>>> |actionpack (3.2.19) lib/action_controller/metal/instrumentation.rb:29:in `process_action'| >>>> >>>> |actionpack (3.2.19) lib/action_controller/metal/params_wrapper.rb:207:in `process_action'| >>>> >>>> |actionpack (3.2.19) lib/abstract_controller/base.rb:121:in `process'| >>>> >>>> |actionpack (3.2.19) lib/abstract_controller/rendering.rb:45:in `process'| >>>> >>>> |actionpack (3.2.19) lib/action_controller/metal.rb:203:in `dispatch'| >>>> >>>> |actionpack (3.2.19) lib/action_controller/metal/rack_delegation.rb:14:in `dispatch'| >>>> >>>> |actionpack (3.2.19) lib/action_controller/metal.rb:246:in `action'| >>>> >>>> |org/jruby/RubyProc.java:271:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:73:in `dispatch'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:36:in `call'| >>>> >>>> |journey (1.0.4) lib/journey/router.rb:68:in `call'| >>>> >>>> |org/jruby/RubyArray.java:1613:in `each'| >>>> >>>> |journey (1.0.4) lib/journey/router.rb:56:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/routing/route_set.rb:608:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/best_standards_support.rb:17:in `call'| >>>> >>>> |rack (1.4.5) lib/rack/etag.rb:23:in `call'| >>>> >>>> |rack (1.4.5) lib/rack/conditionalget.rb:25:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/head.rb:14:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/params_parser.rb:21:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/flash.rb:242:in `call'| >>>> >>>> |rack (1.4.5) lib/rack/session/abstract/id.rb:210:in `context'| >>>> >>>> |rack (1.4.5) lib/rack/session/abstract/id.rb:205:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/cookies.rb:341:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:28:in `call'| >>>> >>>> |activesupport (3.2.19) lib/active_support/callbacks.rb:408:in `_run__1026630806__call__1019491275__callbacks'| >>>> >>>> |activesupport (3.2.19) lib/active_support/callbacks.rb:405:in `__run_callback'| >>>> >>>> |activesupport (3.2.19) lib/active_support/callbacks.rb:390:in `_run_call_callbacks'| >>>> >>>> |activesupport (3.2.19) lib/active_support/callbacks.rb:81:in `run_callbacks'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/callbacks.rb:27:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/reloader.rb:65:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/remote_ip.rb:31:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/debug_exceptions.rb:16:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/show_exceptions.rb:56:in `call'| >>>> >>>> |railties (3.2.19) lib/rails/rack/logger.rb:32:in `call_app'| >>>> >>>> |railties (3.2.19) lib/rails/rack/logger.rb:16:in `call'| >>>> >>>> |activesupport (3.2.19) lib/active_support/tagged_logging.rb:22:in `tagged'| >>>> >>>> |railties (3.2.19) lib/rails/rack/logger.rb:16:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/request_id.rb:22:in `call'| >>>> >>>> |rack (1.4.5) lib/rack/methodoverride.rb:21:in `call'| >>>> >>>> |rack (1.4.5) lib/rack/runtime.rb:17:in `call'| >>>> >>>> |activesupport (3.2.19) lib/active_support/cache/strategy/local_cache.rb:72:in `call'| >>>> >>>> |rack (1.4.5) lib/rack/lock.rb:15:in `call'| >>>> >>>> |actionpack (3.2.19) lib/action_dispatch/middleware/static.rb:63:in `call'| >>>> >>>> |railties (3.2.19) lib/rails/engine.rb:484:in `call'| >>>> >>>> |railties (3.2.19) lib/rails/application.rb:231:in `call'| >>>> >>>> |rack (1.4.5) lib/rack/content_length.rb:14:in `call'| >>>> >>>> |railties (3.2.19) lib/rails/rack/log_tailer.rb:17:in `call'| >>>> >>>> |puma-2.8.2 (java) lib/puma/server.rb:490:in `handle_request'| >>>> >>>> |puma-2.8.2 (java) lib/puma/server.rb:488:in `handle_request'| >>>> >>>> |puma-2.8.2 (java) lib/puma/server.rb:361:in `process_client'| >>>> >>>> |puma-2.8.2 (java) lib/puma/server.rb:254:in `run'| >>>> >>>> |org/jruby/RubyProc.java:271:in `call'| >>>> >>>> |puma-2.8.2 (java) lib/puma/thread_pool.rb:92:in `spawn_thread'| >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> >>>> Archivesspace_Users_Group mailing list >>>> >>>> Archivesspace_Users_Group at lyralists.lyrasis.org >>>> >>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> >>>> Archivesspace_Users_Group mailing list >>>> >>>> Archivesspace_Users_Group at lyralists.lyrasis.org >>>> >>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>>> >>>> >>>> >>>> _______________________________________________ >>>> Archivesspace_Users_Group mailing list >>>> Archivesspace_Users_Group at lyralists.lyrasis.org >>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From noah.huffman at duke.edu Thu Apr 9 12:02:18 2015 From: noah.huffman at duke.edu (Noah Huffman) Date: Thu, 9 Apr 2015 16:02:18 +0000 Subject: [Archivesspace_Users_Group] Customizing advanced search? Message-ID: Hi all, I've been trying to tweak the advanced search functionality in the staff interface through a local plugin and had some questions. 1. I've successfully added some user-defined fields to the advanced search dropdowns by adding a search_definitions.rb file to archivesspace\plugins\local. However, nothing I search for in the added fields yields any results. Is there something else I need to do to index these added fields? 2. When adding a controlled value (enum) field to the search dropdowns, is it necessary to also provide translations for every single value in the controlled value list to the locales\enums\en.yml file? It seems that if I don't specify a translation here for every single controlled value term, those terms appear in the advanced search drop-down like this: "translation missing: en.enumerations.user_defined_enum_1.[name of controlled value term]". Is this the intended behavior? If so, it seems like a real pain to have to keep your controlled value lists and your en.yml file in sync all the time. For example, every time I add a value to a user-defined controlled value list in the application, I then have to add an entry for that term in en.yml like "My Name: My Name" and restart the application. If I don't, I get the "translation missing" error in the advanced search drop-down. Thanks for any help or clarification. -Noah ================ Noah Huffman Archivist for Metadata and Encoding David M. Rubenstein Rare Book & Manuscript Library Duke University -------------- next part -------------- An HTML attachment was scrubbed... URL: From djpillen at umich.edu Thu Apr 9 13:33:13 2015 From: djpillen at umich.edu (Dallas Pillen) Date: Thu, 9 Apr 2015 13:33:13 -0400 Subject: [Archivesspace_Users_Group] Import EAD via the API? In-Reply-To: <1428519903997.78136@lyrasis.org> References: <1428519903997.78136@lyrasis.org> Message-ID: Hi Mark, Adding "charset=utf-8" did the trick! This plugin + batch_imports will allow me to do essentially what I was hoping to do by batch importing EADs. Thanks so much for the help, and for offering to take a further look into the error. Thanks, Dallas On Wed, Apr 8, 2015 at 3:05 PM, Mark Cooper wrote: > Hi Dallas, > > > Have you tried adding "charset=utf-8" to the content-type headers? Also > feel free to send me an EAD file that produces the error and I'll try to > look into it over the weekend. > > > Best, > > Mark > > > Mark Cooper > Technical Lead, Hosting and Support > LYRASIS > email: mark.cooper at lyrasis.org > skype: mark_c_cooper? > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Dallas Pillen > *Sent:* Tuesday, April 7, 2015 9:09 AM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Import EAD via the API? > > Thanks for the replies! > > Noah: we have talked about first importing our EADs into AT and then > migrating to ArchivesSpace, but we're trying to do a lot of preliminary > data cleanup and have made some modifications to the AS EAD importer in an > attempt to make our legacy data as clean and AS-friendly as possible before > migrating. Ideally, we'll account for most of the errors we've identified > during our EAD cleanup and won't need to rely on the more forgiving nature > of the AT importer. But it's something we're open to taking a look at at > some point, at least as a supplemental error discovery/identification tool. > > Mark and Steve: Something along those lines just might work. As part of > our EAD cleanup we are going through our extents, subjects, and other > potential sources of namespace pollution so those sorts of issues will be > controlled for in our EADs before our actual migration to AS. This should > also make a pre-migration conversion to the AS JSONModel more feasible > since, when we are ready to do so, our EADs will theoretically convert to > the AS JSONModel with minimal errors. > > Mark, I tried your plugin on a batch of EADs and there were a few cases > in which the conversion failed due to something like the following: > > (UndefinedConversionError) ""\xC3\xA9"" from UTF-8 to US-ASCII > > The EAD that threw this particular error has some '?' characters that > the AS EAD converter imports without issue. Any thoughts on that? Other > than that, converting our EADs to JSON and then bulk importing each of the > JSON files would essentially accomplish what I was thinking of doing by > importing EAD through the API. > > Still, like Noah, I'd still be interested in knowing if anyone else has > figured out how to start EAD import jobs through the API, partially out of > curiosity and also to be able to compare some of these potential > conversion/import strategies. > > Thanks again for all the helpful suggestion! > > Dallas > > On Mon, Apr 6, 2015 at 4:35 PM, Steven Majewski > wrote: > >> >> What I had been doing was running EADConverter locally on a batch of >> files, saving the JSON >> output if successful, and posting those JSON files to >> >> http://archivesspace.github.io/archivesspace/doc/file.API.html#post-repositoriesrepoidbatchimports >> >> ( This two stage process was also very useful in earlier versions when >> the error reporting >> was missing the context: ArchivesSpace would tell you what was missing, >> but it didn?t point >> to where it was missing from. It was possible to inspect the JSON and >> look for the null or >> missing value. ) >> >> You want to: >> >> converter = EADConverter.new( eadxml ) >> converter.run >> and then do something (move, copy or sent directly to batch_imports >> API) with: >> converter.get_output_path >> >> and if you wrap it in a begin/rescue block, you can catch and report >> the errors. >> >> >> I?ve experimented with a couple of variations on the error catching and >> processing. >> For example, if you move the JSON output in the ensure clause ( >> begin/rescue/ensure ), >> you can save the JSON to inspect even if it?s not complete enough to >> successfully >> import with /batch_imports, but you might not want to mix ?good? and >> ?bad? JSON in >> your output files. >> >> More recently, I?ve been experimenting with using an alternate EAD >> importer with >> looser schema validation rules. >> >> One problem with importing thousands of EAD files by this batch method >> is that >> we have had problems with ?namespace pollution? of the controlled vocab >> lists >> for extents and containers. These values are controlled from the webapp >> and editor, >> but importing from EAD adds to the values in the database. If you import >> a few >> EAD files at a time, it?s not difficult to merge and clean up these >> values, but >> importing several thousand EAD files that aren?t very controlled for >> those values >> led to an explosion that makes the drop down lists of those values >> unusable. >> >> See a previous message about this: >> >> http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2015-March/001216.html >> >> >> >> ? Steve Majewski / UVA Alderman Library >> >> >> On Apr 6, 2015, at 3:08 PM, Dallas Pillen wrote: >> >> Hello all, >> >> I was curious if anyone has had any success starting EAD import jobs >> via the API? >> >> I was thinking this could be done using POST >> /repositories/:repo_id/jobs_with_files described here: >> http://archivesspace.github.io/archivesspace/doc/file.API.html#post-repositoriesrepoidjobswithfiles >> >> However, I am not entirely sure how the job and file parameters should >> be sent in the POST request, and I haven't seen anyone ask this question >> before or give an example of how it might work. I've tried sending the POST >> request several different ways and each time I am met with: >> {"error":{"job":["Parameter required but no value >> provided"],"files":["Parameter required but no value provided"]}}. >> >> I suppose it's worth mentioning that the reason I want to do this is >> that, at some point, we will be importing several thousand EADs into >> ArchivesSpace. We're doing a lot of preliminary work to make our EADs >> import successfully, but know there will likely be some that will fail. >> Right now, the only way to do a batch import of EADs is to do a batch as a >> single import job. If one EAD in that job has an error, the entire job >> fails. For that reason, I would like to be able to import each EAD as a >> separate job so that the EADs that will import successfully will do so >> without being impacted by the EADs with errors. However, starting several >> thousand individual import jobs would be very tedious, and I'm looking for >> a way to automate that process. If anyone else has come up with any >> creative solutions or knows of a better way to do that than the API, I >> would be very interested to know. >> >> The end goal would be to have a script that would batch start the >> import jobs, get the ID for each job, check up on the jobs every so often >> and, once there are no longer any active jobs, output some information >> about each of the jobs that failed. I've figured out how to do most of that >> using the API, but I'm stumped on how to get the whole process started. >> >> Thanks! >> >> Dallas >> >> >> -- >> >> *Dallas Pillen *Project Archivist >> >> >> Bentley Historical Library >> 1150 Beal Avenue >> Ann Arbor, Michigan 48109-2113 >> 734.647.3559 >> Twitter Facebook >> >> _______________________________________________ >> 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 >> >> > > > -- > > *Dallas Pillen *Project Archivist > > > Bentley Historical Library > 1150 Beal Avenue > Ann Arbor, Michigan 48109-2113 > 734.647.3559 > Twitter Facebook > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- *Dallas Pillen*Project Archivist Bentley Historical Library 1150 Beal Avenue Ann Arbor, Michigan 48109-2113 734.647.3559 Twitter Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From carrie.daniels at louisville.edu Thu Apr 9 15:04:59 2015 From: carrie.daniels at louisville.edu (carrie.daniels at louisville.edu) Date: Thu, 9 Apr 2015 19:04:59 +0000 Subject: [Archivesspace_Users_Group] Dates issue Message-ID: <9A1D5C806D42B64E857CE93DFE714EF1CE641C32@EXMBX04.ad.louisville.edu> I'm working version 1.2.0 and finding that in many (if not all) instances, date fields are being forced to YYYY-MM-DD, even if YYYY is stated as an acceptable format. For example, in an Accession record, if I want to enter specific Begin and End dates for Inclusive dates, ArchivesSpace pops up a calendar and will not allow me to enter "2010" in the Begin field. Am I missing something? If not, is this intentional? Thanks, Carrie Carrie Daniels University Archivist Director, Archives and Special Collections University of Louisville (502) 852-6676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From buschedw at msu.edu Thu Apr 9 15:14:46 2015 From: buschedw at msu.edu (Busch, Ed) Date: Thu, 9 Apr 2015 19:14:46 +0000 Subject: [Archivesspace_Users_Group] Dates issue In-Reply-To: <9A1D5C806D42B64E857CE93DFE714EF1CE641C32@EXMBX04.ad.louisville.edu> References: <9A1D5C806D42B64E857CE93DFE714EF1CE641C32@EXMBX04.ad.louisville.edu> Message-ID: <35E2A8E8997F6C48A5D5FC21602BDEB68DDB55A4@CAD-EX1.campusad.msu.edu> I reported this last week and is recorded as AR-1191. Ed Busch Electronic Records Archivist University Archives & Historical Collections Michigan State University 517.884.6438. buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of carrie.daniels at louisville.edu Sent: Thursday, April 09, 2015 3:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Dates issue I'm working version 1.2.0 and finding that in many (if not all) instances, date fields are being forced to YYYY-MM-DD, even if YYYY is stated as an acceptable format. For example, in an Accession record, if I want to enter specific Begin and End dates for Inclusive dates, ArchivesSpace pops up a calendar and will not allow me to enter "2010" in the Begin field. Am I missing something? If not, is this intentional? Thanks, Carrie Carrie Daniels University Archivist Director, Archives and Special Collections University of Louisville (502) 852-6676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From brianjhoffman at gmail.com Thu Apr 9 15:36:48 2015 From: brianjhoffman at gmail.com (brian) Date: Thu, 09 Apr 2015 15:36:48 -0400 Subject: [Archivesspace_Users_Group] Dates issue Message-ID: Yes, you are right. Will be fixed in next release:?https://github.com/archivesspace/archivesspace/pull/173 Sent from my T-Mobile 4G LTE Device
-------- Original message --------
From: carrie.daniels at louisville.edu
Date:04/09/2015 3:04 PM (GMT-05:00)
To: archivesspace_users_group at lyralists.lyrasis.org
Cc:
Subject: [Archivesspace_Users_Group] Dates issue
I?m working version 1.2.0 and finding that in many (if not all) instances, date fields are being forced to YYYY-MM-DD, even if YYYY is stated as an acceptable format. For example, in an Accession record, if I want to enter specific Begin and End dates for Inclusive dates, ArchivesSpace pops up a calendar and will not allow me to enter ?2010? in the Begin field. Am I missing something? If not, is this intentional? Thanks, Carrie Carrie Daniels University Archivist Director, Archives and Special Collections University of Louisville (502) 852-6676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From carrie.daniels at louisville.edu Thu Apr 9 15:46:54 2015 From: carrie.daniels at louisville.edu (carrie.daniels at louisville.edu) Date: Thu, 9 Apr 2015 19:46:54 +0000 Subject: [Archivesspace_Users_Group] Dates issue In-Reply-To: <35E2A8E8997F6C48A5D5FC21602BDEB68DDB55A4@CAD-EX1.campusad.msu.edu> References: <9A1D5C806D42B64E857CE93DFE714EF1CE641C32@EXMBX04.ad.louisville.edu> <35E2A8E8997F6C48A5D5FC21602BDEB68DDB55A4@CAD-EX1.campusad.msu.edu> Message-ID: <9A1D5C806D42B64E857CE93DFE714EF1CE641EAE@EXMBX04.ad.louisville.edu> Wonderful! Sorry I overlooked that. Thanks - Carrie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Thursday, April 09, 2015 3:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Dates issue I reported this last week and is recorded as AR-1191. Ed Busch Electronic Records Archivist University Archives & Historical Collections Michigan State University 517.884.6438. buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of carrie.daniels at louisville.edu Sent: Thursday, April 09, 2015 3:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Dates issue I'm working version 1.2.0 and finding that in many (if not all) instances, date fields are being forced to YYYY-MM-DD, even if YYYY is stated as an acceptable format. For example, in an Accession record, if I want to enter specific Begin and End dates for Inclusive dates, ArchivesSpace pops up a calendar and will not allow me to enter "2010" in the Begin field. Am I missing something? If not, is this intentional? Thanks, Carrie Carrie Daniels University Archivist Director, Archives and Special Collections University of Louisville (502) 852-6676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From robin_mcelheny at harvard.edu Thu Apr 9 17:56:43 2015 From: robin_mcelheny at harvard.edu (McElheny, Robin G.) Date: Thu, 9 Apr 2015 21:56:43 +0000 Subject: [Archivesspace_Users_Group] Harvard Library ArchivesSpace Working Group report of system issues Message-ID: Hi there, Brad and the ArchivesSpace development team - In our last round of testing, we identified system issues relating to three areas, each of which is detailed in the attached report: - System functionality - Data display - User Interface Please let us know if you need further explanations about these issues. We look forward to your feedback. Robin McElheny Associate University Archivist for Collections and Public Services Harvard University Archives Pusey Library Cambridge, MA 02138 Email: robin_mcelheny at harvard.edu Phone: 617-495-2461 Fax: 617-495-8011 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Report_to_Lyrasis_ArchivesSpaceDevelopmentTeam_4_9_2015.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 47457 bytes Desc: Report_to_Lyrasis_ArchivesSpaceDevelopmentTeam_4_9_2015.docx URL: From jrm7qy at gmail.com Thu Apr 9 16:07:31 2015 From: jrm7qy at gmail.com (Jaime Mears) Date: Thu, 9 Apr 2015 16:07:31 -0400 Subject: [Archivesspace_Users_Group] Importing agent information through accession CSV Message-ID: Hi everyone! We're operating v1.2.0 here at Maryland, and when I include information in the agent_ fields for an accession, I get this message in the log: Error: # and nothing imports. If I leave out any agent information, I'm able to import without any problems. Does anyone have a suggestion? I'm using the given .csv template. -Jaime -- *Jaime Mears* GA for Access, Special Collections 2216 Hornbake Library University of Maryland, College Park Tel: 301-405-9124 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Fri Apr 10 05:32:27 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Fri, 10 Apr 2015 09:32:27 +0000 Subject: [Archivesspace_Users_Group] Dates issue In-Reply-To: <9A1D5C806D42B64E857CE93DFE714EF1CE641EAE@EXMBX04.ad.louisville.edu> References: <9A1D5C806D42B64E857CE93DFE714EF1CE641C32@EXMBX04.ad.louisville.edu> <35E2A8E8997F6C48A5D5FC21602BDEB68DDB55A4@CAD-EX1.campusad.msu.edu>, <9A1D5C806D42B64E857CE93DFE714EF1CE641EAE@EXMBX04.ad.louisville.edu> Message-ID: <1428658346781.23538@lyrasis.org> Hi everyone, You should be able to fix this right now by adding this file to plugins/local/frontend/controllers/form_fix_controller.rb and restarting Aspace. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of carrie.daniels at louisville.edu Sent: Thursday, April 9, 2015 9:46 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Dates issue Wonderful! Sorry I overlooked that. Thanks - Carrie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Thursday, April 09, 2015 3:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Dates issue I reported this last week and is recorded as AR-1191. Ed Busch Electronic Records Archivist University Archives & Historical Collections Michigan State University 517.884.6438. buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of carrie.daniels at louisville.edu Sent: Thursday, April 09, 2015 3:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Dates issue I'm working version 1.2.0 and finding that in many (if not all) instances, date fields are being forced to YYYY-MM-DD, even if YYYY is stated as an acceptable format. For example, in an Accession record, if I want to enter specific Begin and End dates for Inclusive dates, ArchivesSpace pops up a calendar and will not allow me to enter "2010" in the Begin field. Am I missing something? If not, is this intentional? Thanks, Carrie Carrie Daniels University Archivist Director, Archives and Special Collections University of Louisville (502) 852-6676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Fri Apr 10 07:09:32 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Fri, 10 Apr 2015 11:09:32 +0000 Subject: [Archivesspace_Users_Group] ArchivesSpace Development and Support JIRAs Message-ID: Hello ArchivesSpace members, In early January 2015, we migrated the ArchivesSpace catalog of user stories from Pivotal Tracker to JIRA in order to enable you to 1. Play a more integral role in our development planning process through voting, 2. More easily track development activities, and 3. Submit bug reports, feature requests, and comments to issues of importance to you and your institution's implementation. We now have 2 active JIRA instances that we encourage you to bookmark and to visit often. * Development JIRA (http://development.archivesspace.org) o A living catalog of all user stories for the ArchivesSpace application since the beginning of the ArchivesSpace program in 2011, including those completed, those currently being implemented, those prioritized for development, and those not yet prioritized. You can browse the catalog using labels and other attributes such as type, status, etc. * Support JIRA (http://support.archivesspace.org) o For filing bug reports and feature requests. In order for us to follow-up with you directly, all submissions require the email address of the submitter. All issues will be checked for duplication and bug reports will be verified for accuracy before being transferred into the Development JIRA where they will be prioritized for implementation. Very soon, we will be inviting you, through your member representative, to vote on individual user stories to help inform the development prioritization process as we move closer to defining a roadmap for version 2.0. Member Representatives, please keep an eye out for an email from Christine DiBella with additional details. Thank you very much for your continuing support. Brad W. Bradley D. Westbrook Program Manager brad.westbrook at lyrasis.org 800.999.8558 x2910 678.235.2910 bradley_d_westbrook (Skype) [cid:image001.png at 01D07356.AA09B910] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7646 bytes Desc: image001.png URL: From smithkr at mit.edu Fri Apr 10 10:13:05 2015 From: smithkr at mit.edu (Kari R Smith) Date: Fri, 10 Apr 2015 14:13:05 +0000 Subject: [Archivesspace_Users_Group] Question re: post-release fixes Message-ID: <29F559819ACA9A4FBF208407D4B63ABBBA59D742@OC11expo28.exchange.mit.edu> Question for Chris F. If we have not yet installed AcrhivesSpace 1.2.0, will all of the small fixes and patches that have been reported and dealt with (like in this email message below) be included in the code? Or will we need to install the code and then go to the email messages to find and then install the fixes? Thank you for clarifying how this works! Kari Smith From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Friday, April 10, 2015 5:32 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Dates issue Hi everyone, You should be able to fix this right now by adding this file to plugins/local/frontend/controllers/form_fix_controller.rb and restarting Aspace. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of carrie.daniels at louisville.edu > Sent: Thursday, April 9, 2015 9:46 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Dates issue Wonderful! Sorry I overlooked that. Thanks - Carrie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Busch, Ed Sent: Thursday, April 09, 2015 3:15 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Dates issue I reported this last week and is recorded as AR-1191. Ed Busch Electronic Records Archivist University Archives & Historical Collections Michigan State University 517.884.6438. buschedw at msu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of carrie.daniels at louisville.edu Sent: Thursday, April 09, 2015 3:05 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Dates issue I'm working version 1.2.0 and finding that in many (if not all) instances, date fields are being forced to YYYY-MM-DD, even if YYYY is stated as an acceptable format. For example, in an Accession record, if I want to enter specific Begin and End dates for Inclusive dates, ArchivesSpace pops up a calendar and will not allow me to enter "2010" in the Begin field. Am I missing something? If not, is this intentional? Thanks, Carrie Carrie Daniels University Archivist Director, Archives and Special Collections University of Louisville (502) 852-6676 -------------- next part -------------- An HTML attachment was scrubbed... URL: From library at princeofpeaceabbey.org Fri Apr 10 11:48:55 2015 From: library at princeofpeaceabbey.org (library at princeofpeaceabbey.org) Date: Fri, 10 Apr 2015 15:48:55 +0000 Subject: [Archivesspace_Users_Group] Dates issue In-Reply-To: <1428658346781.23538@lyrasis.org> References: <9A1D5C806D42B64E857CE93DFE714EF1CE641C32@EXMBX04.ad.louisville.edu> <35E2A8E8997F6C48A5D5FC21602BDEB68DDB55A4@CAD-EX1.campusad.msu.edu> <9A1D5C806D42B64E857CE93DFE714EF1CE641EAE@EXMBX04.ad.louisville.edu> <1428658346781.23538@lyrasis.org> Message-ID: <20150410154855.Horde.sQFZgYDyg1SpMzDp4D4oAA7@gator3088.hostgator.com> Chris, Tried the date fix but got this instead: can not load translations from C:\archivesspace/plugins/local/frontend/locales/form_fix_controller.rb: expects it to return a hash, but does not from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/base.rb:167:in `load_file' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/base.rb:15:in `load_translations' from org/jruby/RubyArray.java:1613:in `each' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/base.rb:15:in `load_translations' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/simple.rb:57:in `init_translations' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/simple.rb:40:in `available_locales' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/config.rb:43:in `available_locales' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/config.rb:49:in `available_locales_set' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n.rb:278:in `locale_available?' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n.rb:284:in `enforce_available_locales!' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/config.rb:34:in `default_locale=' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n.rb:43:in `default_locale=' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/i18n_railtie.rb:60:in `initialize_i18n' from org/jruby/RubyHash.java:1341:in `each' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/i18n_railtie.rb:53:in `initialize_i18n' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/i18n_railtie.rb:40:in `Railtie' from org/jruby/RubyProc.java:271:in `call' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/lazy_load_hooks.rb:34:in `execute_hook' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/lazy_load_hooks.rb:43:in `run_load_hooks' from org/jruby/RubyArray.java:1613:in `each' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/lazy_load_hooks.rb:42:in `run_load_hooks' from C:/archivesspace/gems/gems/railties-3.2.19/lib/rails/application/finisher.rb:52:in `Finisher' from org/jruby/RubyBasicObject.java:1562:in `instance_exec' from C:/archivesspace/gems/gems/railties-3.2.19/lib/rails/initializable.rb:30:in `run' from C:/archivesspace/gems/gems/railties-3.2.19/lib/rails/initializable.rb:55:in `run_initializers' from org/jruby/RubyArray.java:1613:in `each' from C:/archivesspace/gems/gems/railties-3.2.19/lib/rails/initializable.rb:54:in `run_initializers' from file:/C:/archivesspace/lib/common.jar!/rails_config_bug_workaround.rb:11:in `initialize!' from C:/archivesspace/gems/gems/railties-3..2.19/lib/rails/railtie/configurable.rb:30:in `method_missing' from C:/archivesspace/data/tmp/jetty-0.0.0.0-8080-frontend.war-_-any-/webapp/WEB-INF/config/environment.rb:29:in `(root)' from org/jruby/RubyKernel.java:1071:in `require' from file:/C:/archivesspace/gems/gems/jruby-rack-1.1.18/lib/jruby-rack-1.1.18.jar!/jruby/rack/rails/environment3.rb:1:in `(root)' from file:/C:/archivesspace/gems/gems/jruby-rack-1.1.18/lib/jruby-rack-1.1.18.jar!/jruby/rack/rails/environment3.rb:25:in `load_environment' from file:/C:/archivesspace/gems/gems/jruby-rack-1.1.18/lib/jruby-rack-1.1.18.jar!/jruby/rack/rails_booter.rb:83:in `load_environment' from launcher/launcher.rb:86:in `start_server' from launcher/launcher.rb:158:in `main' from launcher/launcher.rb:230:in `(root)' Back to me: Did I do something wrong? Using Windows 8.1 Br Raphael Quoting Chris Fitzpatrick : > Hi everyone, > > > You should be able to fix this right now by adding this file > to > plugins/local/frontend/controllers/form_fix_controller.rb and > restarting Aspace. > > > b,chris. > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ________________________________ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf > of carrie.daniels at louisville.edu > Sent: Thursday, April 9, 2015 9:46 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Dates issue > > Wonderful! Sorry I overlooked that. > Thanks - > Carrie > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On > Behalf Of Busch, Ed > Sent: Thursday, April 09, 2015 3:15 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Dates issue > > I reported this last week and is recorded as AR-1191. > > Ed Busch > Electronic Records Archivist > University Archives & Historical Collections > Michigan State University > 517.884.6438. > buschedw at msu.edu > > > From: > archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of > carrie.daniels at louisville.edu > Sent: Thursday, April 09, 2015 3:05 PM > To: > archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] Dates issue > > I'm working version 1.2.0 and finding that in many (if not all) > instances, date fields are being forced to YYYY-MM-DD, even if YYYY > is stated as an acceptable format. For example, in an Accession > record, if I want to enter specific Begin and End dates for > Inclusive dates, ArchivesSpace pops up a calendar and will not allow > me to enter "2010" in the Begin field. Am I missing something? If > not, is this intentional? > Thanks, > Carrie > > > Carrie Daniels > University Archivist > Director, Archives and Special Collections > University of Louisville > (502) 852-6676 Br Raphael Meyer osb Prince of Peace Abbey From mark.cooper at lyrasis.org Fri Apr 10 14:10:03 2015 From: mark.cooper at lyrasis.org (Mark Cooper) Date: Fri, 10 Apr 2015 18:10:03 +0000 Subject: [Archivesspace_Users_Group] Dates issue In-Reply-To: <20150410154855.Horde.sQFZgYDyg1SpMzDp4D4oAA7@gator3088.hostgator.com> References: <9A1D5C806D42B64E857CE93DFE714EF1CE641C32@EXMBX04.ad.louisville.edu> <35E2A8E8997F6C48A5D5FC21602BDEB68DDB55A4@CAD-EX1.campusad.msu.edu> <9A1D5C806D42B64E857CE93DFE714EF1CE641EAE@EXMBX04.ad.louisville.edu> <1428658346781.23538@lyrasis.org>, <20150410154855.Horde.sQFZgYDyg1SpMzDp4D4oAA7@gator3088.hostgator.com> Message-ID: <1428689402412.2592@lyrasis.org> Hi Raphael, The file needs to go in: plugins/local/frontend/controllers/form_fix_controller.rb Not: plugins/local/frontend/locales/form_fix_controller.rb Mark Mark Cooper Technical Lead, Hosting and Support LYRASIS email: mark.cooper at lyrasis.org skype: mark_c_cooper? ________________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of library at princeofpeaceabbey.org Sent: Friday, April 10, 2015 8:48 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Dates issue Chris, Tried the date fix but got this instead: can not load translations from C:\archivesspace/plugins/local/frontend/locales/form_fix_controller.rb: expects it to return a hash, but does not from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/base.rb:167:in `load_file' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/base.rb:15:in `load_translations' from org/jruby/RubyArray.java:1613:in `each' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/base.rb:15:in `load_translations' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/simple.rb:57:in `init_translations' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/simple.rb:40:in `available_locales' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/config.rb:43:in `available_locales' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/config.rb:49:in `available_locales_set' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n.rb:278:in `locale_available?' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n.rb:284:in `enforce_available_locales!' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/config.rb:34:in `default_locale=' from C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n.rb:43:in `default_locale=' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/i18n_railtie.rb:60:in `initialize_i18n' from org/jruby/RubyHash.java:1341:in `each' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/i18n_railtie.rb:53:in `initialize_i18n' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/i18n_railtie.rb:40:in `Railtie' from org/jruby/RubyProc.java:271:in `call' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/lazy_load_hooks.rb:34:in `execute_hook' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/lazy_load_hooks.rb:43:in `run_load_hooks' from org/jruby/RubyArray.java:1613:in `each' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/lazy_load_hooks.rb:42:in `run_load_hooks' from C:/archivesspace/gems/gems/railties-3.2.19/lib/rails/application/finisher.rb:52:in `Finisher' from org/jruby/RubyBasicObject.java:1562:in `instance_exec' from C:/archivesspace/gems/gems/rail ties-3.2.19/lib/rails/initializable.rb:30:in `run' from C:/archivesspace/gems/gems/railties-3.2.19/lib/rails/initializable.rb:55:in `run_initializers' from org/jruby/RubyArray.java:1613:in `each' from C:/archivesspace/gems/gems/railties-3.2.19/lib/rails/initializable.rb:54:in `run_initializers' from file:/C:/archivesspace/lib/common.jar!/rails_config_bug_workaround.rb:11:in `initialize!' from C:/archivesspace/gems/gems/railties-3..2.19/lib/rails/railtie/configurable.rb:30:in `method_missing' from C:/archivesspace/data/tmp/jetty-0.0.0.0-8080-frontend.war-_-any-/webapp/WEB-INF/config/environment.rb:29:in `(root)' from org/jruby/RubyKernel.java:1071:in `require' from file:/C:/archivesspace/gems/gems/jruby-rack-1.1.18/lib/jruby-rack-1.1.18.jar!/jruby/rack/rails/environment3.rb:1:in `(root)' from file:/C:/archivesspace/gems/gems/jruby-rack-1.1.18/lib/jruby-rack-1.1.18.jar!/jruby/rack/rails/environment3.rb:25:in `load_environment' from file:/C:/archivesspace/gems/gems/jruby-rack-1 .1.18/lib/jruby-rack-1.1.18.jar!/jruby/rack/rails_booter.rb:83:in `load_environment' from launcher/launcher.rb:86:in `start_server' from launcher/launcher.rb:158:in `main' from launcher/launcher.rb:230:in `(root)' Back to me: Did I do something wrong? Using Windows 8.1 Br Raphael Quoting Chris Fitzpatrick : > Hi everyone, > > > You should be able to fix this right now by adding this file > to > plugins/local/frontend/controllers/form_fix_controller.rb and > restarting Aspace. > > > b,chris. > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ________________________________ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf > of carrie.daniels at louisville.edu > Sent: Thursday, April 9, 2015 9:46 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Dates issue > > Wonderful! Sorry I overlooked that. > Thanks - > Carrie > > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On > Behalf Of Busch, Ed > Sent: Thursday, April 09, 2015 3:15 PM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Dates issue > > I reported this last week and is recorded as AR-1191. > > Ed Busch > Electronic Records Archivist > University Archives & Historical Collections > Michigan State University > 517.884.6438. > buschedw at msu.edu > > > From: > archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of > carrie.daniels at louisville.edu > Sent: Thursday, April 09, 2015 3:05 PM > To: > archivesspace_users_group at lyralists.lyrasis.org > Subject: [Archivesspace_Users_Group] Dates issue > > I'm working version 1.2.0 and finding that in many (if not all) > instances, date fields are being forced to YYYY-MM-DD, even if YYYY > is stated as an acceptable format. For example, in an Accession > record, if I want to enter specific Begin and End dates for > Inclusive dates, ArchivesSpace pops up a calendar and will not allow > me to enter "2010" in the Begin field. Am I missing something? If > not, is this intentional? > Thanks, > Carrie > > > Carrie Daniels > University Archivist > Director, Archives and Special Collections > University of Louisville > (502) 852-6676 Br Raphael Meyer osb Prince of Peace Abbey _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From library at princeofpeaceabbey.org Fri Apr 10 16:46:45 2015 From: library at princeofpeaceabbey.org (library at princeofpeaceabbey.org) Date: Fri, 10 Apr 2015 20:46:45 +0000 Subject: [Archivesspace_Users_Group] Dates issue In-Reply-To: <1428689402412.2592@lyrasis.org> References: <9A1D5C806D42B64E857CE93DFE714EF1CE641C32@EXMBX04.ad.louisville.edu> <35E2A8E8997F6C48A5D5FC21602BDEB68DDB55A4@CAD-EX1.campusad.msu.edu> <9A1D5C806D42B64E857CE93DFE714EF1CE641EAE@EXMBX04.ad.louisville.edu> <1428658346781.23538@lyrasis.org> <20150410154855.Horde.sQFZgYDyg1SpMzDp4D4oAA7@gator3088.hostgator.com> <1428689402412.2592@lyrasis.org> Message-ID: <20150410204645.Horde.68ae9-HvQIqM_8THn8nRDQ9@gator3088.hostgator.com> Mark, Thanks for finding my error. The plugin seems to be working. While the program was down I had to try and find some minutes that was supposed to be in three black binders. I reality they were in one black binder and two white ones. I am also the librarian and sometimes monks cannot remember the name of the book or its author but they do remember its color. No help what so ever. Br Raphael Quoting Mark Cooper : > Hi Raphael, > > The file needs to go in: > > plugins/local/frontend/controllers/form_fix_controller.rb > > Not: > > plugins/local/frontend/locales/form_fix_controller.rb > > Mark > > Mark Cooper > Technical Lead, Hosting and Support > LYRASIS > email: mark.cooper at lyrasis.org > skype: mark_c_cooper? > > ________________________________________ > From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf > of library at princeofpeaceabbey.org > Sent: Friday, April 10, 2015 8:48 AM > To: Archivesspace Users Group > Subject: Re: [Archivesspace_Users_Group] Dates issue > > Chris, > > Tried the date fix but got this instead: > > can not load translations from > C:\archivesspace/plugins/local/frontend/locales/form_fix_controller.rb: > expects it to return a hash, but does not from > C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/base.rb:167:in > `load_file' from > C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/base.rb:15:in > `load_translations' from org/jruby/RubyArray.java:1613:in `each' from > C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/base.rb:15:in > `load_translations' from > C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/simple.rb:57:in > `init_translations' from > C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/backend/simple.rb:40:in > `available_locales' from > C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/config.rb:43:in > `available_locales' from > C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/config.rb:49:in > `available_locales_set' from > C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n.rb:278:in > `locale_available?' from > C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n.rb:284:in > `enforce_available_locales!' from > C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n/config.rb:34:in > `default_locale=' from > C:/archivesspace/gems/gems/i18n-0.7.0/lib/i18n.rb:43:in > `default_locale=' from > C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/i18n_railtie.rb:60:in `initialize_i18n' from org/jruby/RubyHash.java:1341:in `each' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/i18n_railtie.rb:53:in `initialize_i18n' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/i18n_railtie.rb:40:in `Railtie' from org/jruby/RubyProc.java:271:in `call' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/lazy_load_hooks.rb:34:in `execute_hook' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/lazy_load_hooks.rb:43:in `run_load_hooks' from org/jruby/RubyArray.java:1613:in `each' from C:/archivesspace/gems/gems/activesupport-3.2.19/lib/active_support/lazy_load_hooks.rb:42:in `run_load_hooks' from C:/archivesspace/gems/gems/railties-3.2.19/lib/rails/application/finisher.rb:52:in `Finisher' from org/jruby/RubyBasicObject.java:1562:in `instance_exec' from > C:/archivesspace/gems/gems/rail > ties-3.2.19/lib/rails/initializable.rb:30:in `run' from > C:/archivesspace/gems/gems/railties-3.2.19/lib/rails/initializable.rb:55:in > `run_initializers' from org/jruby/RubyArray.java:1613:in `each' from > C:/archivesspace/gems/gems/railties-3.2.19/lib/rails/initializable.rb:54:in > `run_initializers' from > file:/C:/archivesspace/lib/common.jar!/rails_config_bug_workaround.rb:11:in > `initialize!' from > C:/archivesspace/gems/gems/railties-3..2.19/lib/rails/railtie/configurable.rb:30:in `method_missing' from C:/archivesspace/data/tmp/jetty-0.0.0.0-8080-frontend.war-_-any-/webapp/WEB-INF/config/environment.rb:29:in `(root)' from org/jruby/RubyKernel.java:1071:in `require' from file:/C:/archivesspace/gems/gems/jruby-rack-1.1.18/lib/jruby-rack-1.1.18.jar!/jruby/rack/rails/environment3.rb:1:in `(root)' from file:/C:/archivesspace/gems/gems/jruby-rack-1.1.18/lib/jruby-rack-1.1.18.jar!/jruby/rack/rails/environment3.rb:25:in `load_environment' from > file:/C:/archivesspace/gems/gems/jruby-rack-1 > .1.18/lib/jruby-rack-1.1.18.jar!/jruby/rack/rails_booter.rb:83:in > `load_environment' from launcher/launcher.rb:86:in `start_server' > from launcher/launcher.rb:158:in `main' from > launcher/launcher.rb:230:in > `(root)' > > Back to me: Did I do something wrong? Using Windows 8.1 > > Br Raphael > Quoting Chris Fitzpatrick : > >> Hi everyone, >> >> >> You should be able to fix this right now by adding this file >> to >> plugins/local/frontend/controllers/form_fix_controller.rb and >> restarting Aspace. >> >> >> b,chris. >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> ________________________________ >> From: archivesspace_users_group-bounces at lyralists.lyrasis.org >> on behalf >> of carrie.daniels at louisville.edu >> Sent: Thursday, April 9, 2015 9:46 PM >> To: Archivesspace Users Group >> Subject: Re: [Archivesspace_Users_Group] Dates issue >> >> Wonderful! Sorry I overlooked that. >> Thanks - >> Carrie >> >> From: archivesspace_users_group-bounces at lyralists.lyrasis.org >> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On >> Behalf Of Busch, Ed >> Sent: Thursday, April 09, 2015 3:15 PM >> To: Archivesspace Users Group >> Subject: Re: [Archivesspace_Users_Group] Dates issue >> >> I reported this last week and is recorded as AR-1191. >> >> Ed Busch >> Electronic Records Archivist >> University Archives & Historical Collections >> Michigan State University >> 517.884.6438. >> buschedw at msu.edu >> >> >> From: >> archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf >> Of >> carrie.daniels at louisville.edu >> Sent: Thursday, April 09, 2015 3:05 PM >> To: >> archivesspace_users_group at lyralists.lyrasis.org >> Subject: [Archivesspace_Users_Group] Dates issue >> >> I'm working version 1.2.0 and finding that in many (if not all) >> instances, date fields are being forced to YYYY-MM-DD, even if YYYY >> is stated as an acceptable format. For example, in an Accession >> record, if I want to enter specific Begin and End dates for >> Inclusive dates, ArchivesSpace pops up a calendar and will not allow >> me to enter "2010" in the Begin field. Am I missing something? If >> not, is this intentional? >> Thanks, >> Carrie >> >> >> Carrie Daniels >> University Archivist >> Director, Archives and Special Collections >> University of Louisville >> (502) 852-6676 > > > Br Raphael Meyer osb > Prince of Peace Abbey > > _______________________________________________ > 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 Br Raphael Meyer osb Prince of Peace Abbey From ljdavis at colgate.edu Fri Apr 10 17:11:33 2015 From: ljdavis at colgate.edu (Lora Davis) Date: Fri, 10 Apr 2015 17:11:33 -0400 Subject: [Archivesspace_Users_Group] Finding Aid Date redux Message-ID: Collective wisdom, Back in October I wrote (partial e-mail thread below) to note that "Finding Aid Date" was not exporting into as we expected upon EAD export (it actually wasn't being exported at all). By the end of the month this error had been corrected as reported by Chris Fitzpatrick below and confirmed by myself. Following our update to 1.2 last night (we're Lyrasis hosted) the is again no longer exporting. I'm writing to confirm that this isn't just a local issue. Have others found that "Finding Aid Date" isn't making it into their exported EAD? I find it hard to believe that no one else has reported what seems like a pretty obvious bug... Best, Lora ---------- Forwarded message ---------- From: Chris Fitzpatrick Date: Mon, Oct 20, 2014 at 11:07 AM Subject: Re: [Archivesspace_Users_Group] Finding aid date To: Archivesspace Users Group < archivesspace_users_group at lyralists.lyrasis.org> Hi Mark, Good memory. Looking back at this, the problem was "fixed" ( https://github.com/archivesspace/archivesspace/commit/a5ca7afd61c5b2d7eb7a3d437892dc6d48e4a920#diff-e585b4901bb0498d8c559d38bf448ea8R529 ) back on Jul 8 but then this was removed because it was later removed because it was not according to the spec ( http://archivesspace.org/importexport ) which doesn't have the finding_aid_date in the titlestmt. The problem is that the finding_aid_date was never actually added to the publicationstmt, which is were the spec says it should go. I've added the finding_aid_date to the publicationstmt, as the EAD export map indicates it should go. Hopefully this will resolve the matter? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ------------------------------ *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Custer, Mark *Sent:* Monday, October 20, 2014 3:01 PM *To:* Archivesspace Users Group *Subject:* Re: [Archivesspace_Users_Group] Finding aid date I reported this issue earlier in the year. Here?s the snippet from the Word file, which was later added to Pivotal Tracker: ? ?Finding Aid Title? field is not exported (instead, the collection ?Title? is repeated in its place). ? ?Finding Aid Note? is not exported as part of the eadheader. ? ?Finding Aid Date? is not exported as part of the eadheader. And here?s the ticket in Pivotal Tracker for that last one: https://www.pivotaltracker.com/story/show/72331992 (which was broken out from the original ticket) Are the Finding Aid Note and Finding Aid Title fields exporting now? Mark P.S. I also added a feature request to include a separate field for subtitles, but I don?t know how many people would actually require that ( https://www.pivotaltracker.com/story/show/69651562). If that field was used in the AT, I can confirm that the subtitle is still migrated over to ArchivesSpace since the AT-to-ASpace migration tool will append that value to the finding aid title field. I haven?t tested ASpace?s EAD importer to confirm that it does the same, though. *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Chris Fitzpatrick *Sent:* Monday, October 20, 2014 6:34 AM *To:* Archivesspace Users Group *Subject:* Re: [Archivesspace_Users_Group] Finding aid date Hi Laura, Well, it's not in Pivotal, so it was not a known bug. I've added them here: https://www.pivotaltracker.com/story/show/81000628 Kind of amazed nobody has noticed this sooner. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ------------------------------ *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Lora Davis *Sent:* Friday, October 17, 2014 9:17 PM *To:* Archivesspace Users Group *Subject:* [Archivesspace_Users_Group] Finding aid date Apologies if this has already been noted, but I - like many others I'm sure - have been eagerly awaiting 1.1.0 so have been putting rc8 through its paces in our sandbox today. The one pesky outstanding issue that does not appear to be resolved is that the contents of "Finding Aid Date" are still not being exported at all, let alone into where we'd expect to find it. Our stylesheets draw on this date to generate an authorship statement along the lines of "Finding aid prepared by , ." Since the finding aid date is not ending up anywhere in the exported XML we're left with "Finding aid prepared by John Smith, ." Minor inconvenience, but annoying. On the other hand, I'm pleased to report that other failure to export issues we've had with things like are now working beautifully. Are others finding that is not exporting? Is this a known bug? Is there a reason why this is not being exported? Any fix in the works? (I checked the PivotalTracker, but found nada.) Thanks in advance, Lora -- Lora J. Davis Assistant Archivist Colgate University Libraries 13 Oak Drive Hamilton, NY 13346 Tel: (315) 228-6376 Fax: (315) 228-7934 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Lora J. Davis Collections Archivist Colgate University Libraries 13 Oak Drive Hamilton, NY 13346 Tel: (315) 228-6376 Fax: (315) 228-7934 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mkottman at ku.edu Fri Apr 10 17:56:42 2015 From: mkottman at ku.edu (Kottman, Miloche) Date: Fri, 10 Apr 2015 21:56:42 +0000 Subject: [Archivesspace_Users_Group] Finding Aid Date redux In-Reply-To: References: Message-ID: <220B4CB68E19834D965E60AC94D69BD826D941F2@EXCH10-MBX-03.home.ku.edu> I just downloaded one of our resource records and can confirm that the finding aid date is no longer exporting into the in version 1.2 --Miloche From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lora Davis Sent: Friday, April 10, 2015 4:12 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Finding Aid Date redux Collective wisdom, Back in October I wrote (partial e-mail thread below) to note that "Finding Aid Date" was not exporting into as we expected upon EAD export (it actually wasn't being exported at all). By the end of the month this error had been corrected as reported by Chris Fitzpatrick below and confirmed by myself. Following our update to 1.2 last night (we're Lyrasis hosted) the is again no longer exporting. I'm writing to confirm that this isn't just a local issue. Have others found that "Finding Aid Date" isn't making it into their exported EAD? I find it hard to believe that no one else has reported what seems like a pretty obvious bug... Best, Lora ---------- Forwarded message ---------- From: Chris Fitzpatrick > Date: Mon, Oct 20, 2014 at 11:07 AM Subject: Re: [Archivesspace_Users_Group] Finding aid date To: Archivesspace Users Group > Hi Mark, Good memory. Looking back at this, the problem was "fixed" ( https://github.com/archivesspace/archivesspace/commit/a5ca7afd61c5b2d7eb7a3d437892dc6d48e4a920#diff-e585b4901bb0498d8c559d38bf448ea8R529 ) back on Jul 8 but then this was removed because it was later removed because it was not according to the spec ( http://archivesspace.org/importexport ) which doesn't have the finding_aid_date in the titlestmt. The problem is that the finding_aid_date was never actually added to the publicationstmt, which is were the spec says it should go. I've added the finding_aid_date to the publicationstmt, as the EAD export map indicates it should go. Hopefully this will resolve the matter? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Custer, Mark > Sent: Monday, October 20, 2014 3:01 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Finding aid date I reported this issue earlier in the year. Here?s the snippet from the Word file, which was later added to Pivotal Tracker: ? ?Finding Aid Title? field is not exported (instead, the collection ?Title? is repeated in its place). ? ?Finding Aid Note? is not exported as part of the eadheader. ? ?Finding Aid Date? is not exported as part of the eadheader. And here?s the ticket in Pivotal Tracker for that last one: https://www.pivotaltracker.com/story/show/72331992 (which was broken out from the original ticket) Are the Finding Aid Note and Finding Aid Title fields exporting now? Mark P.S. I also added a feature request to include a separate field for subtitles, but I don?t know how many people would actually require that (https://www.pivotaltracker.com/story/show/69651562). If that field was used in the AT, I can confirm that the subtitle is still migrated over to ArchivesSpace since the AT-to-ASpace migration tool will append that value to the finding aid title field. I haven?t tested ASpace?s EAD importer to confirm that it does the same, though. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Monday, October 20, 2014 6:34 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Finding aid date Hi Laura, Well, it's not in Pivotal, so it was not a known bug. I've added them here: https://www.pivotaltracker.com/story/show/81000628 Kind of amazed nobody has noticed this sooner. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Lora Davis > Sent: Friday, October 17, 2014 9:17 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Finding aid date Apologies if this has already been noted, but I - like many others I'm sure - have been eagerly awaiting 1.1.0 so have been putting rc8 through its paces in our sandbox today. The one pesky outstanding issue that does not appear to be resolved is that the contents of "Finding Aid Date" are still not being exported at all, let alone into where we'd expect to find it. Our stylesheets draw on this date to generate an authorship statement along the lines of "Finding aid prepared by , ." Since the finding aid date is not ending up anywhere in the exported XML we're left with "Finding aid prepared by John Smith, ." Minor inconvenience, but annoying. On the other hand, I'm pleased to report that other failure to export issues we've had with things like are now working beautifully. Are others finding that is not exporting? Is this a known bug? Is there a reason why this is not being exported? Any fix in the works? (I checked the PivotalTracker, but found nada.) Thanks in advance, Lora -- Lora J. Davis Assistant Archivist Colgate University Libraries 13 Oak Drive Hamilton, NY 13346 Tel: (315) 228-6376 Fax: (315) 228-7934 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Lora J. Davis Collections Archivist Colgate University Libraries 13 Oak Drive Hamilton, NY 13346 Tel: (315) 228-6376 Fax: (315) 228-7934 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Sat Apr 11 02:51:30 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Sat, 11 Apr 2015 06:51:30 +0000 Subject: [Archivesspace_Users_Group] Finding Aid Date redux In-Reply-To: <220B4CB68E19834D965E60AC94D69BD826D941F2@EXCH10-MBX-03.home.ku.edu> References: , <220B4CB68E19834D965E60AC94D69BD826D941F2@EXCH10-MBX-03.home.ku.edu> Message-ID: <1428735090415.74811@lyrasis.org> Hi, It looks like for some reason the finding aid date will only appear in the EAD export if you Repo has an image url associated to it. I'm not sure about the reasons for that, but if you add a "Branding Image URL" to your repository, the finding aid date will be exported. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Kottman, Miloche Sent: Friday, April 10, 2015 11:56 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Finding Aid Date redux I just downloaded one of our resource records and can confirm that the finding aid date is no longer exporting into the in version 1.2 --Miloche From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lora Davis Sent: Friday, April 10, 2015 4:12 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Finding Aid Date redux Collective wisdom, Back in October I wrote (partial e-mail thread below) to note that "Finding Aid Date" was not exporting into as we expected upon EAD export (it actually wasn't being exported at all). By the end of the month this error had been corrected as reported by Chris Fitzpatrick below and confirmed by myself. Following our update to 1.2 last night (we're Lyrasis hosted) the is again no longer exporting. I'm writing to confirm that this isn't just a local issue. Have others found that "Finding Aid Date" isn't making it into their exported EAD? I find it hard to believe that no one else has reported what seems like a pretty obvious bug... Best, Lora ---------- Forwarded message ---------- From: Chris Fitzpatrick > Date: Mon, Oct 20, 2014 at 11:07 AM Subject: Re: [Archivesspace_Users_Group] Finding aid date To: Archivesspace Users Group > Hi Mark, Good memory. Looking back at this, the problem was "fixed" ( https://github.com/archivesspace/archivesspace/commit/a5ca7afd61c5b2d7eb7a3d437892dc6d48e4a920#diff-e585b4901bb0498d8c559d38bf448ea8R529 ) back on Jul 8 but then this was removed because it was later removed because it was not according to the spec ( http://archivesspace.org/importexport ) which doesn't have the finding_aid_date in the titlestmt. The problem is that the finding_aid_date was never actually added to the publicationstmt, which is were the spec says it should go. I've added the finding_aid_date to the publicationstmt, as the EAD export map indicates it should go. Hopefully this will resolve the matter? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Custer, Mark > Sent: Monday, October 20, 2014 3:01 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Finding aid date I reported this issue earlier in the year. Here?s the snippet from the Word file, which was later added to Pivotal Tracker: ? ?Finding Aid Title? field is not exported (instead, the collection ?Title? is repeated in its place). ? ?Finding Aid Note? is not exported as part of the eadheader. ? ?Finding Aid Date? is not exported as part of the eadheader. And here?s the ticket in Pivotal Tracker for that last one: https://www.pivotaltracker.com/story/show/72331992 (which was broken out from the original ticket) Are the Finding Aid Note and Finding Aid Title fields exporting now? Mark P.S. I also added a feature request to include a separate field for subtitles, but I don?t know how many people would actually require that (https://www.pivotaltracker.com/story/show/69651562). If that field was used in the AT, I can confirm that the subtitle is still migrated over to ArchivesSpace since the AT-to-ASpace migration tool will append that value to the finding aid title field. I haven?t tested ASpace?s EAD importer to confirm that it does the same, though. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Monday, October 20, 2014 6:34 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Finding aid date Hi Laura, Well, it's not in Pivotal, so it was not a known bug. I've added them here: https://www.pivotaltracker.com/story/show/81000628 Kind of amazed nobody has noticed this sooner. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Lora Davis > Sent: Friday, October 17, 2014 9:17 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Finding aid date Apologies if this has already been noted, but I - like many others I'm sure - have been eagerly awaiting 1.1.0 so have been putting rc8 through its paces in our sandbox today. The one pesky outstanding issue that does not appear to be resolved is that the contents of "Finding Aid Date" are still not being exported at all, let alone into where we'd expect to find it. Our stylesheets draw on this date to generate an authorship statement along the lines of "Finding aid prepared by , ." Since the finding aid date is not ending up anywhere in the exported XML we're left with "Finding aid prepared by John Smith, ." Minor inconvenience, but annoying. On the other hand, I'm pleased to report that other failure to export issues we've had with things like are now working beautifully. Are others finding that is not exporting? Is this a known bug? Is there a reason why this is not being exported? Any fix in the works? (I checked the PivotalTracker, but found nada.) Thanks in advance, Lora -- Lora J. Davis Assistant Archivist Colgate University Libraries 13 Oak Drive Hamilton, NY 13346 Tel: (315) 228-6376 Fax: (315) 228-7934 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Lora J. Davis Collections Archivist Colgate University Libraries 13 Oak Drive Hamilton, NY 13346 Tel: (315) 228-6376 Fax: (315) 228-7934 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ljdavis at colgate.edu Sat Apr 11 11:21:46 2015 From: ljdavis at colgate.edu (Lora Davis) Date: Sat, 11 Apr 2015 11:21:46 -0400 Subject: [Archivesspace_Users_Group] Finding Aid Date redux In-Reply-To: <1428735090415.74811@lyrasis.org> References: <220B4CB68E19834D965E60AC94D69BD826D941F2@EXCH10-MBX-03.home.ku.edu> <1428735090415.74811@lyrasis.org> Message-ID: How odd, but, sure enough, this does the trick. Many thanks! Lora On Sat, Apr 11, 2015 at 2:51 AM, Chris Fitzpatrick < Chris.Fitzpatrick at lyrasis.org> wrote: > Hi, > > > It looks like for some reason the finding aid date will only appear in > the EAD export if you Repo has an image url associated to it. > > I'm not sure about the reasons for that, but if you add a "Branding Image > URL" to your repository, the finding aid date will be exported. > > > b,chris. > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Kottman, Miloche > *Sent:* Friday, April 10, 2015 11:56 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Finding Aid Date redux > > > I just downloaded one of our resource records and can confirm that the > finding aid date is no longer exporting into the in > version 1.2 > > > > --Miloche > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Lora > Davis > *Sent:* Friday, April 10, 2015 4:12 PM > *To:* Archivesspace Users Group > *Subject:* [Archivesspace_Users_Group] Finding Aid Date redux > > > > Collective wisdom, > > > > Back in October I wrote (partial e-mail thread below) to note that > "Finding Aid Date" was not exporting into as we expected > upon EAD export (it actually wasn't being exported at all). By the end of > the month this error had been corrected as reported by Chris Fitzpatrick > below and confirmed by myself. Following our update to 1.2 last night > (we're Lyrasis hosted) the is again no longer exporting. I'm > writing to confirm that this isn't just a local issue. Have others found > that "Finding Aid Date" isn't making it into their exported EAD? I find it > hard to believe that no one else has reported what seems like a pretty > obvious bug... > > > > Best, > > > > Lora > > > > ---------- Forwarded message ---------- > From: *Chris Fitzpatrick* > Date: Mon, Oct 20, 2014 at 11:07 AM > Subject: Re: [Archivesspace_Users_Group] Finding aid date > To: Archivesspace Users Group < > archivesspace_users_group at lyralists.lyrasis.org> > > Hi Mark, > > > > Good memory. Looking back at this, the problem was "fixed" ( > > > https://github.com/archivesspace/archivesspace/commit/a5ca7afd61c5b2d7eb7a3d437892dc6d48e4a920#diff-e585b4901bb0498d8c559d38bf448ea8R529 ) > back on Jul 8 but then this was removed because it was later removed > because it was not according to the spec ( > > http://archivesspace.org/importexport ) which doesn't have the > finding_aid_date in the titlestmt. > > > > The problem is that the finding_aid_date was never actually added to the > publicationstmt, which is were the spec says it should go. > > > > I've added the finding_aid_date to the publicationstmt, as the EAD export > map indicates it should go. Hopefully this will resolve the matter? > > > > b,chris. > > > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ------------------------------ > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Custer, Mark > *Sent:* Monday, October 20, 2014 3:01 PM > *To:* Archivesspace Users Group > > > *Subject:* Re: [Archivesspace_Users_Group] Finding aid date > > > > I reported this issue earlier in the year. Here?s the snippet from the > Word file, which was later added to Pivotal Tracker: > > > > ? ?Finding Aid Title? field is not exported (instead, the > collection ?Title? is repeated in its place). > > ? ?Finding Aid Note? is not exported as part of the eadheader. > > ? ?Finding Aid Date? is not exported as part of the eadheader. > > And here?s the ticket in Pivotal Tracker for that last one: > https://www.pivotaltracker.com/story/show/72331992 (which was broken out > from the original ticket) > > > > Are the Finding Aid Note and Finding Aid Title fields exporting now? > > > > Mark > > > > P.S. I also added a feature request to include a separate field for > subtitles, but I don?t know how many people would actually require that ( > https://www.pivotaltracker.com/story/show/69651562). If that field was > used in the AT, I can confirm that the subtitle is still migrated over to > ArchivesSpace since the AT-to-ASpace migration tool will append that value > to the finding aid title field. I haven?t tested ASpace?s EAD importer to > confirm that it does the same, though. > > > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Chris > Fitzpatrick > *Sent:* Monday, October 20, 2014 6:34 AM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Finding aid date > > > > Hi Laura, > > > > Well, it's not in Pivotal, so it was not a known bug. I've added them > here: > > https://www.pivotaltracker.com/story/show/81000628 > > > > Kind of amazed nobody has noticed this sooner. > > > > b,chris. > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ------------------------------ > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Lora Davis > *Sent:* Friday, October 17, 2014 9:17 PM > *To:* Archivesspace Users Group > *Subject:* [Archivesspace_Users_Group] Finding aid date > > > > Apologies if this has already been noted, but I - like many others I'm > sure - have been eagerly awaiting 1.1.0 so have been putting rc8 through > its paces in our sandbox today. > > > > The one pesky outstanding issue that does not appear to be resolved is > that the contents of "Finding Aid Date" are still not being exported at > all, let alone into where we'd expect to find it. Our > stylesheets draw on this date to generate an authorship statement along the > lines of "Finding aid prepared by , ." Since the finding aid > date is not ending up anywhere in the exported XML we're left with "Finding > aid prepared by John Smith, ." Minor inconvenience, but annoying. > > > > On the other hand, I'm pleased to report that other failure to export > issues we've had with things like are now working > beautifully. > > > > Are others finding that is not exporting? Is this a known bug? Is > there a reason why this is not being exported? Any fix in the works? (I > checked the PivotalTracker, but found nada.) > > > > Thanks in advance, > > > > Lora > > > > -- > Lora J. Davis > Assistant Archivist > Colgate University Libraries > 13 Oak Drive > Hamilton, NY 13346 > > Tel: (315) 228-6376 > Fax: (315) 228-7934 > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > > -- > > Lora J. Davis > Collections Archivist > Colgate University Libraries > 13 Oak Drive > Hamilton, NY 13346 > > Tel: (315) 228-6376 > Fax: (315) 228-7934 > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Lora J. Davis Collections Archivist Colgate University Libraries 13 Oak Drive Hamilton, NY 13346 Tel: (315) 228-6376 Fax: (315) 228-7934 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Sun Apr 12 09:40:08 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Sun, 12 Apr 2015 13:40:08 +0000 Subject: [Archivesspace_Users_Group] Finding Aid Date redux In-Reply-To: References: <220B4CB68E19834D965E60AC94D69BD826D941F2@EXCH10-MBX-03.home.ku.edu> <1428735090415.74811@lyrasis.org>, Message-ID: <1428846009873.16765@lyrasis.org> Yes, I'm 90% sure that is not intended. I've made a ticket for this here: https://archivesspace.atlassian.net/browse/AR-1202 b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Lora Davis Sent: Saturday, April 11, 2015 5:21 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Finding Aid Date redux How odd, but, sure enough, this does the trick. Many thanks! Lora On Sat, Apr 11, 2015 at 2:51 AM, Chris Fitzpatrick > wrote: Hi, It looks like for some reason the finding aid date will only appear in the EAD export if you Repo has an image url associated to it. I'm not sure about the reasons for that, but if you add a "Branding Image URL" to your repository, the finding aid date will be exported. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Kottman, Miloche > Sent: Friday, April 10, 2015 11:56 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Finding Aid Date redux I just downloaded one of our resource records and can confirm that the finding aid date is no longer exporting into the in version 1.2 --Miloche From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lora Davis Sent: Friday, April 10, 2015 4:12 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Finding Aid Date redux Collective wisdom, Back in October I wrote (partial e-mail thread below) to note that "Finding Aid Date" was not exporting into as we expected upon EAD export (it actually wasn't being exported at all). By the end of the month this error had been corrected as reported by Chris Fitzpatrick below and confirmed by myself. Following our update to 1.2 last night (we're Lyrasis hosted) the is again no longer exporting. I'm writing to confirm that this isn't just a local issue. Have others found that "Finding Aid Date" isn't making it into their exported EAD? I find it hard to believe that no one else has reported what seems like a pretty obvious bug... Best, Lora ---------- Forwarded message ---------- From: Chris Fitzpatrick > Date: Mon, Oct 20, 2014 at 11:07 AM Subject: Re: [Archivesspace_Users_Group] Finding aid date To: Archivesspace Users Group > Hi Mark, Good memory. Looking back at this, the problem was "fixed" ( https://github.com/archivesspace/archivesspace/commit/a5ca7afd61c5b2d7eb7a3d437892dc6d48e4a920#diff-e585b4901bb0498d8c559d38bf448ea8R529 ) back on Jul 8 but then this was removed because it was later removed because it was not according to the spec ( http://archivesspace.org/importexport ) which doesn't have the finding_aid_date in the titlestmt. The problem is that the finding_aid_date was never actually added to the publicationstmt, which is were the spec says it should go. I've added the finding_aid_date to the publicationstmt, as the EAD export map indicates it should go. Hopefully this will resolve the matter? b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Custer, Mark > Sent: Monday, October 20, 2014 3:01 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Finding aid date I reported this issue earlier in the year. Here?s the snippet from the Word file, which was later added to Pivotal Tracker: ? ?Finding Aid Title? field is not exported (instead, the collection ?Title? is repeated in its place). ? ?Finding Aid Note? is not exported as part of the eadheader. ? ?Finding Aid Date? is not exported as part of the eadheader. And here?s the ticket in Pivotal Tracker for that last one: https://www.pivotaltracker.com/story/show/72331992 (which was broken out from the original ticket) Are the Finding Aid Note and Finding Aid Title fields exporting now? Mark P.S. I also added a feature request to include a separate field for subtitles, but I don?t know how many people would actually require that (https://www.pivotaltracker.com/story/show/69651562). If that field was used in the AT, I can confirm that the subtitle is still migrated over to ArchivesSpace since the AT-to-ASpace migration tool will append that value to the finding aid title field. I haven?t tested ASpace?s EAD importer to confirm that it does the same, though. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick Sent: Monday, October 20, 2014 6:34 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Finding aid date Hi Laura, Well, it's not in Pivotal, so it was not a known bug. I've added them here: https://www.pivotaltracker.com/story/show/81000628 Kind of amazed nobody has noticed this sooner. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org > on behalf of Lora Davis > Sent: Friday, October 17, 2014 9:17 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Finding aid date Apologies if this has already been noted, but I - like many others I'm sure - have been eagerly awaiting 1.1.0 so have been putting rc8 through its paces in our sandbox today. The one pesky outstanding issue that does not appear to be resolved is that the contents of "Finding Aid Date" are still not being exported at all, let alone into where we'd expect to find it. Our stylesheets draw on this date to generate an authorship statement along the lines of "Finding aid prepared by , ." Since the finding aid date is not ending up anywhere in the exported XML we're left with "Finding aid prepared by John Smith, ." Minor inconvenience, but annoying. On the other hand, I'm pleased to report that other failure to export issues we've had with things like are now working beautifully. Are others finding that is not exporting? Is this a known bug? Is there a reason why this is not being exported? Any fix in the works? (I checked the PivotalTracker, but found nada.) Thanks in advance, Lora -- Lora J. Davis Assistant Archivist Colgate University Libraries 13 Oak Drive Hamilton, NY 13346 Tel: (315) 228-6376 Fax: (315) 228-7934 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Lora J. Davis Collections Archivist Colgate University Libraries 13 Oak Drive Hamilton, NY 13346 Tel: (315) 228-6376 Fax: (315) 228-7934 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Lora J. Davis Collections Archivist Colgate University Libraries 13 Oak Drive Hamilton, NY 13346 Tel: (315) 228-6376 Fax: (315) 228-7934 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rho at folkartmuseum.org Mon Apr 13 10:48:19 2015 From: rho at folkartmuseum.org (Richard Ho) Date: Mon, 13 Apr 2015 10:48:19 -0400 Subject: [Archivesspace_Users_Group] Fwd: AFAM follow-up In-Reply-To: References: Message-ID: Hello all, After following a youtube tutorial by Chris Fitzpatrick, I came across this error while running the tomcat script bat file. Does anyone have any suggestions on how to fix this issue? Thank you for your time. -Richard Ho [image: Inline image 1] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 66083 bytes Desc: not available URL: From mang.sun at rice.edu Mon Apr 13 11:47:10 2015 From: mang.sun at rice.edu (Mang Sun) Date: Mon, 13 Apr 2015 10:47:10 -0500 Subject: [Archivesspace_Users_Group] Fwd: AFAM follow-up In-Reply-To: References: Message-ID: <552BE4FE.9080502@rice.edu> Changing the port value of the public interface in the config.rb from 8080 to another port say 8079 should help Mang Sun Rice U. On 4/13/2015 9:48 AM, Richard Ho wrote: > Hello all, > > After following a youtube tutorial by Chris Fitzpatrick, I came across > this error while running the tomcat script bat file. Does anyone have > any suggestions on how to fix this issue? Thank you for your time. > > -Richard Ho > > Inline image 1 > > > _______________________________________________ > 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: not available Type: image/png Size: 66083 bytes Desc: not available URL: From luftsche at usc.edu Mon Apr 13 13:00:42 2015 From: luftsche at usc.edu (Susan Luftschein) Date: Mon, 13 Apr 2015 17:00:42 +0000 Subject: [Archivesspace_Users_Group] RDE screen problems Message-ID: Hi Chris and developers, Our hosted instance was upgraded to the latest version last Thursday and on Friday we noticed this: [cid:image001.jpg at 01D075D0.B4A16DB0] The headers on the columns are clearly being compressed in some way. This is only happening in Firefox; Chrome is okay. However, Firefox is the browser that our IT department supports so we need to get this resolved asap. Can you guys look into it? Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 57810 bytes Desc: image001.jpg URL: From smithkr at mit.edu Mon Apr 13 13:19:32 2015 From: smithkr at mit.edu (Kari R Smith) Date: Mon, 13 Apr 2015 17:19:32 +0000 Subject: [Archivesspace_Users_Group] RDE screen problems - Supported Browsers Message-ID: <29F559819ACA9A4FBF208407D4B63ABBBA59E06F@OC11expo28.exchange.mit.edu> Hi Sue, You might want to take a look at the Supported Browser information. It looks like Firefox 8+ is fully supported by the application, but Firefox 7 is not. This might be helpful information for your institutional IT department. https://github.com/archivesspace/archivesspace/wiki/Supported-browsers Kari Smith MIT Institute Archives and Special Collections From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Monday, April 13, 2015 1:01 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] RDE screen problems Hi Chris and developers, Our hosted instance was upgraded to the latest version last Thursday and on Friday we noticed this: [cid:image001.jpg at 01D075EC.79C8AA70] The headers on the columns are clearly being compressed in some way. This is only happening in Firefox; Chrome is okay. However, Firefox is the browser that our IT department supports so we need to get this resolved asap. Can you guys look into it? Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 57810 bytes Desc: image001.jpg URL: From luftsche at usc.edu Mon Apr 13 13:57:17 2015 From: luftsche at usc.edu (Susan Luftschein) Date: Mon, 13 Apr 2015 17:57:17 +0000 Subject: [Archivesspace_Users_Group] RDE screen problems - Supported Browsers In-Reply-To: <29F559819ACA9A4FBF208407D4B63ABBBA59E06F@OC11expo28.exchange.mit.edu> References: <29F559819ACA9A4FBF208407D4B63ABBBA59E06F@OC11expo28.exchange.mit.edu> Message-ID: Hi Kari, We are running the latest version of Firefox, which is actually 31.6.0, so not sure what that supported browser info refers to! Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kari R Smith Sent: Monday, April 13, 2015 10:20 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] RDE screen problems - Supported Browsers Hi Sue, You might want to take a look at the Supported Browser information. It looks like Firefox 8+ is fully supported by the application, but Firefox 7 is not. This might be helpful information for your institutional IT department. https://github.com/archivesspace/archivesspace/wiki/Supported-browsers Kari Smith MIT Institute Archives and Special Collections From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Monday, April 13, 2015 1:01 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] RDE screen problems Hi Chris and developers, Our hosted instance was upgraded to the latest version last Thursday and on Friday we noticed this: [cid:image001.jpg at 01D075D8.9CEDCBC0] The headers on the columns are clearly being compressed in some way. This is only happening in Firefox; Chrome is okay. However, Firefox is the browser that our IT department supports so we need to get this resolved asap. Can you guys look into it? Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 57810 bytes Desc: image001.jpg URL: From brad.westbrook at lyrasis.org Mon Apr 13 15:21:11 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Mon, 13 Apr 2015 19:21:11 +0000 Subject: [Archivesspace_Users_Group] RDE screen problems - Supported Browsers In-Reply-To: References: <29F559819ACA9A4FBF208407D4B63ABBBA59E06F@OC11expo28.exchange.mit.edu> Message-ID: Hi, Sue, I have filed a bug report for this: https://archivesspace.atlassian.net/browse/AR-1211?jql=. Thanks for catching it. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Monday, April 13, 2015 1:57 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] RDE screen problems - Supported Browsers Hi Kari, We are running the latest version of Firefox, which is actually 31.6.0, so not sure what that supported browser info refers to! Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kari R Smith Sent: Monday, April 13, 2015 10:20 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] RDE screen problems - Supported Browsers Hi Sue, You might want to take a look at the Supported Browser information. It looks like Firefox 8+ is fully supported by the application, but Firefox 7 is not. This might be helpful information for your institutional IT department. https://github.com/archivesspace/archivesspace/wiki/Supported-browsers Kari Smith MIT Institute Archives and Special Collections From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Monday, April 13, 2015 1:01 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] RDE screen problems Hi Chris and developers, Our hosted instance was upgraded to the latest version last Thursday and on Friday we noticed this: [cid:image001.jpg at 01D075FD.99F8F5F0] The headers on the columns are clearly being compressed in some way. This is only happening in Firefox; Chrome is okay. However, Firefox is the browser that our IT department supports so we need to get this resolved asap. Can you guys look into it? Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 57810 bytes Desc: image001.jpg URL: From jmargalo at udel.edu Mon Apr 13 15:54:48 2015 From: jmargalo at udel.edu (Jaime Margalotti) Date: Mon, 13 Apr 2015 15:54:48 -0400 Subject: [Archivesspace_Users_Group] Multiple Inclusive Dates at Collection Level? Message-ID: Just curious how people are dealing with broken date ranges (ex: 1919, 1978-1995). Would you make two seperate inclusive dates (one for 1919 and one for 1978-1995) or would you have a single inclusive date range with the expression 1919, 1978-1995 and normalized as 1919/1995? Thanks, Jaime -- Jaime L. Margalotti Senior Assistant Librarian Manuscripts and Archives Department University of Delaware Library Newark, DE 19717-5267 302-831-0554jmargalo at udel.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From luftsche at usc.edu Mon Apr 13 16:32:56 2015 From: luftsche at usc.edu (Susan Luftschein) Date: Mon, 13 Apr 2015 20:32:56 +0000 Subject: [Archivesspace_Users_Group] RDE screen problems - Supported Browsers In-Reply-To: References: <29F559819ACA9A4FBF208407D4B63ABBBA59E06F@OC11expo28.exchange.mit.edu> Message-ID: Thanks Brad. I've noticed some other wonky spacing issues since the upgrade. See attached screenshot. Notice the dots in the left hand nav menu, and the date instructions. These all used to be flush and inline. Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brad Westbrook Sent: Monday, April 13, 2015 12:21 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] RDE screen problems - Supported Browsers Hi, Sue, I have filed a bug report for this: https://archivesspace.atlassian.net/browse/AR-1211?jql=. Thanks for catching it. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Monday, April 13, 2015 1:57 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] RDE screen problems - Supported Browsers Hi Kari, We are running the latest version of Firefox, which is actually 31.6.0, so not sure what that supported browser info refers to! Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kari R Smith Sent: Monday, April 13, 2015 10:20 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] RDE screen problems - Supported Browsers Hi Sue, You might want to take a look at the Supported Browser information. It looks like Firefox 8+ is fully supported by the application, but Firefox 7 is not. This might be helpful information for your institutional IT department. https://github.com/archivesspace/archivesspace/wiki/Supported-browsers Kari Smith MIT Institute Archives and Special Collections From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Monday, April 13, 2015 1:01 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] RDE screen problems Hi Chris and developers, Our hosted instance was upgraded to the latest version last Thursday and on Friday we noticed this: [cid:image001.jpg at 01D075EE.5ADB4490] The headers on the columns are clearly being compressed in some way. This is only happening in Firefox; Chrome is okay. However, Firefox is the browser that our IT department supports so we need to get this resolved asap. Can you guys look into it? Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 57810 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture.JPG Type: image/jpeg Size: 85305 bytes Desc: Capture.JPG URL: From Kevin.Clair at du.edu Thu Apr 16 12:42:50 2015 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 16 Apr 2015 16:42:50 +0000 Subject: [Archivesspace_Users_Group] subjects with the same label from different sources? Message-ID: <1F1E72103798F04D96C355B296D7C61B4811BE@mb2-uts.du.edu> Hello, I'm curious if anyone on the list has encountered the issue of having two separate terms in the Subjects table, labelled the same, but drawn from different sources. At DU, we have a few instances where (for example) the LCSH term for "Yearbooks" was migrated over as a topical term, and the LCGFT term for "Yearbooks" was migrated over as a form/genre term, and we've historically used them for different purposes so they can't easily be merged into a single record. Disambiguating between them when adding terms to a record is confusing for our catalogers, since they would need to click through to view each term to make sure it's the type they want. Have others dealt with this issue? How did you go about it? thanks! -k -------------- next part -------------- An HTML attachment was scrubbed... URL: From luftsche at usc.edu Fri Apr 17 14:59:14 2015 From: luftsche at usc.edu (Susan Luftschein) Date: Fri, 17 Apr 2015 18:59:14 +0000 Subject: [Archivesspace_Users_Group] Inability to create conference names Message-ID: Hi all, It seems ArchivesSpace, like AT, does not allow for the creation of conference names as controlled access headings. Is this something that is on the developer's radar? Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gregory.Farr at AustenRiggs.net Fri Apr 17 16:01:09 2015 From: Gregory.Farr at AustenRiggs.net (Gregory.Farr at AustenRiggs.net) Date: Fri, 17 Apr 2015 16:01:09 -0400 Subject: [Archivesspace_Users_Group] AUTO: Gregory Farr is out of the office (returning 04/21/2015) Message-ID: I am out of the office until 04/21/2015. Note: This is an automated response to your message "[Archivesspace_Users_Group] Inability to create conference names" sent on 4/17/2015 2:59:14 PM. This is the only notification you will receive while this person is away. From luftsche at usc.edu Fri Apr 17 16:20:53 2015 From: luftsche at usc.edu (Susan Luftschein) Date: Fri, 17 Apr 2015 20:20:53 +0000 Subject: [Archivesspace_Users_Group] FW: Inability to create conference names In-Reply-To: References: Message-ID: Mistakenly sent this to the wrong address! Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Susan Luftschein Sent: Friday, April 17, 2015 11:59 AM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Inability to create conference names Hi all, It seems ArchivesSpace, like AT, does not allow for the creation of conference names as controlled access headings. Is this something that is on the developer's radar? Thanks, Sue Sue Luftschein Archival and Metadata Librarian USC Libraries Special Collections University of Southern California Doheny Memorial Library 3550 Trousdale Parkway, Room 207 Los Angeles, CA 90089-0189 tel:213-740-4046 fax:213-740-2343 luftsche at usc.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From lindsay-morecraft at uiowa.edu Fri Apr 17 17:12:20 2015 From: lindsay-morecraft at uiowa.edu (Morecraft, Lindsay M) Date: Fri, 17 Apr 2015 21:12:20 +0000 Subject: [Archivesspace_Users_Group] Accession Records Notes Field Message-ID: <96B305F061ED68428DDA721BECE2ED155166A50F@ITSNT440.iowa.uiowa.edu> Hi everyone, We are just starting to explore the accession records module in ArchivesSpace, and we noticed that there is no notes field in this section. We think that this section could really benefit from the notes field, especially with dealing with accruals. Ideally, we would like to add accruals to a single accession record rather than make each accrual its own record. Has anyone else been creating accrual records or has any thoughts on this matter? Thank you! Lindsay Moen (Morecraft) Processing Librarian Special Collections and University Archives The University of Iowa 319-335-5921 -------------- next part -------------- An HTML attachment was scrubbed... URL: From shallcro at umich.edu Mon Apr 20 11:06:28 2015 From: shallcro at umich.edu (Michael Shallcross) Date: Mon, 20 Apr 2015 11:06:28 -0400 Subject: [Archivesspace_Users_Group] ArchivesSpace-Archivematica-DSpace Workflow Integration Project Blog Message-ID: *****With sincere apologies for cross-posting***** Greetings, all; the Bentley Historical Library is excited to announce the launch of a blog for the "ArchivesSpace-Archivematica-DSpace Workflow Integration" project, a collaboration between the Bentley and the University of Michigan Library made possible by a generous grant from the Andrew W. Mellon Foundation. Project staff are working closely with Artefactual Systems , the developers of the Archivematica digital preservation system, to develop new features and/or functionality for these systems to: - streamline the ingest, arrangement, description, and deposit of archives in a digital repository and - facilitate the creation and reuse of descriptive, administrative, and rights metadata across platforms. All development work and associated documentation will be made freely available to the archives and digital preservation communities. In addition, ArchivesSpace-Archivematica interaction will function independently of DSpace; integration with the repository will employ open and widely-used standards so that other systems (such as Hydra) could be employed with additional development. For more information on the project (and regular updates on our status), please visit the blog: http://archival-integration.blogspot.com/ Additional information and documentation will be made available on the Archivematica wiki . Please feel free to contact project staff at bhl-mellon-grant at umich.edu. Best regards, Mike Shallcross -- *Michael Shallcross, CA* *Lead Archivist for Curation* Bentley Historical Library 1150 Beal Ave. Ann Arbor, MI 48109-2113 734.936.1344 http://bentley.umich.edu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Apr 21 09:04:46 2015 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 21 Apr 2015 13:04:46 +0000 Subject: [Archivesspace_Users_Group] Accession Records Notes Field In-Reply-To: <96B305F061ED68428DDA721BECE2ED155166A50F@ITSNT440.iowa.uiowa.edu> References: <96B305F061ED68428DDA721BECE2ED155166A50F@ITSNT440.iowa.uiowa.edu> Message-ID: Hi Lindsay, Hopefully others will jump in to give you some ideas of how they're recording accruals in ArchivesSpace, but I wanted to point out that, by default, accession records in ArchivesSpace include a General Note field. The contents only display on the finished record if there is something in the field, but it is available at any time during the creation and editing process. If you create a new accession record or edit an existing record, you'll see it after Retention Rule and before Acquisition Type. Is this what you had in mind, or are you looking for something else? (On your other question, in my previous life as the manager of a small archival repository using Archivists' Toolkit, typically I would create a new accession record for each accrual and link them to a single Resource record. New to ArchivesSpace, there is also the possibility of linking accessions together using the Related Accessions area, as well as the ability to spawn a new Accession from an existing Accession to save time if much of the information is repeated.) Best, Christine Christine Di Bella Community Outreach and Support Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [cid:image003.png at 01CE734E.FD759D30] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Morecraft, Lindsay M Sent: Friday, April 17, 2015 5:12 PM To: 'Archivesspace Users Group' Subject: [Archivesspace_Users_Group] Accession Records Notes Field Hi everyone, We are just starting to explore the accession records module in ArchivesSpace, and we noticed that there is no notes field in this section. We think that this section could really benefit from the notes field, especially with dealing with accruals. Ideally, we would like to add accruals to a single accession record rather than make each accrual its own record. Has anyone else been creating accrual records or has any thoughts on this matter? Thank you! Lindsay Moen (Morecraft) Processing Librarian Special Collections and University Archives The University of Iowa 319-335-5921 -------------- 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 PGalligan at rockarch.org Wed Apr 22 11:13:40 2015 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Wed, 22 Apr 2015 11:13:40 -0400 Subject: [Archivesspace_Users_Group] EAD Importer crashed? Message-ID: This is a long shot, but I'm wondering if anyone has had any issues with the EAD importer seemingly crashing before? I just tried to import a large EAD file into our production machine (import worked fine on development machine), and after waiting for about 20 minutes the EAD importer still hadn't started the process of reading JSON records or creating anything. I figured something must have happened with the import, so I cancelled the job. However, 30 minutes later I'm still receiving log messages like these: D, [2015-04-22T11:08:29.428000 #14668] DEBUG -- : Thread-2743470: Import running for job 31 I, [2015-04-22T11:08:29.429000 #14668] INFO -- : Thread-2743470: Received cancel request for import job 31 Additionally, AS won't start any new imports now, they just go straight into the queue and never start. Any thoughts on what could be causing this? Have we in fact caused the importer to hang? Thanks! Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Wed Apr 22 11:17:21 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Wed, 22 Apr 2015 11:17:21 -0400 Subject: [Archivesspace_Users_Group] EAD Importer crashed? In-Reply-To: References: Message-ID: We had this problem, and yes the importer did just freeze. It seemed to happen with very large files; you can try getting a beefier processor and more ram, or you can split the collection up and use the merge function (need 1.1.2+ for ASpace). -Maura On Wed, Apr 22, 2015 at 11:13 AM, Galligan, Patrick wrote: > This is a long shot, but I?m wondering if anyone has had any issues with the > EAD importer seemingly crashing before? I just tried to import a large EAD > file into our production machine (import worked fine on development > machine), and after waiting for about 20 minutes the EAD importer still > hadn?t started the process of reading JSON records or creating anything. > > > > I figured something must have happened with the import, so I cancelled the > job. However, 30 minutes later I?m still receiving log messages like these: > > > > D, [2015-04-22T11:08:29.428000 #14668] DEBUG -- : Thread-2743470: Import > running for job 31 > > I, [2015-04-22T11:08:29.429000 #14668] INFO -- : Thread-2743470: Received > cancel request for import job 31 > > > > Additionally, AS won?t start any new imports now, they just go straight into > the queue and never start. Any thoughts on what could be causing this? Have > we in fact caused the importer to hang? > > > > Thanks! > > > > Patrick Galligan > > Rockefeller Archive Center > > Assistant Digital Archivist > > 914-366-6386 > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu From maureen.callahan at yale.edu Wed Apr 22 11:52:18 2015 From: maureen.callahan at yale.edu (Callahan, Maureen) Date: Wed, 22 Apr 2015 15:52:18 +0000 Subject: [Archivesspace_Users_Group] Accession Records Notes Field In-Reply-To: References: <96B305F061ED68428DDA721BECE2ED155166A50F@ITSNT440.iowa.uiowa.edu> Message-ID: Just to piggyback onto Christine's second paragraph (and since you asked), the practice I've followed everywhere I've worked has been to create a new accession record for each accrual. This way, you have lots of good data about when it came in, what you did to it, whether it's governed by the same deed of gift, etc. It can be really helpful to have this for when donors have questions about what they sent and when they sent it! And I really like that ArchivesSpace has a more structured way of linking accessions to each other - very helpful! Maureen Maureen Callahan Archivist, Metadata Specialist Manuscripts & Archives Yale University Library maureen.callahan at yale.edu 203.432.3627 Webpage: web.library.yale.edu/mssa Collections: drs.library.yale.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Tuesday, April 21, 2015 9:05 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Accession Records Notes Field Hi Lindsay, Hopefully others will jump in to give you some ideas of how they're recording accruals in ArchivesSpace, but I wanted to point out that, by default, accession records in ArchivesSpace include a General Note field. The contents only display on the finished record if there is something in the field, but it is available at any time during the creation and editing process. If you create a new accession record or edit an existing record, you'll see it after Retention Rule and before Acquisition Type. Is this what you had in mind, or are you looking for something else? (On your other question, in my previous life as the manager of a small archival repository using Archivists' Toolkit, typically I would create a new accession record for each accrual and link them to a single Resource record. New to ArchivesSpace, there is also the possibility of linking accessions together using the Related Accessions area, as well as the ability to spawn a new Accession from an existing Accession to save time if much of the information is repeated.) Best, Christine Christine Di Bella Community Outreach and Support Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [cid:image003.png at 01CE734E.FD759D30] From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Morecraft, Lindsay M Sent: Friday, April 17, 2015 5:12 PM To: 'Archivesspace Users Group' Subject: [Archivesspace_Users_Group] Accession Records Notes Field Hi everyone, We are just starting to explore the accession records module in ArchivesSpace, and we noticed that there is no notes field in this section. We think that this section could really benefit from the notes field, especially with dealing with accruals. Ideally, we would like to add accruals to a single accession record rather than make each accrual its own record. Has anyone else been creating accrual records or has any thoughts on this matter? Thank you! Lindsay Moen (Morecraft) Processing Librarian Special Collections and University Archives The University of Iowa 319-335-5921 -------------- 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 schelby.1 at osu.edu Thu Apr 23 11:07:37 2015 From: schelby.1 at osu.edu (Schelby, Russell) Date: Thu, 23 Apr 2015 15:07:37 +0000 Subject: [Archivesspace_Users_Group] Restoring deleted record gotchas - deleted_records Message-ID: <1FFC028E0D679147BD07ECFBE1D5C4570DD217@CIO-TNC-D2MBX04.osuad.osu.edu> Hello, We are planning on restoring a record and archival objects that were accidentally deleted, and I was wondering if anyone had any words of wisdom about the process. I was going to just (carefully) poke it in via the database, best-practices be darned :-) So far the only outstanding question that I have is the deleted_records table in the database. Each of the items removed was recorded there, and as far as I can tell, then the records deleted from the resource and archival_object tables. If I poke the records back in the database, should I remove the corresponding lines from deleted_records or just leave well enough alone? Anyone have experience with this, or know when and where deleted_records is used later in the system? Thanks! Russell ________________________________ Russell Schelby Project Manager, Business Analyst Applications, Development & Support, OSU Libraries Schelby.1 at osu.edu, 614.292.0961 -------------- next part -------------- An HTML attachment was scrubbed... URL: From whelman at ubalt.edu Thu Apr 23 14:02:36 2015 From: whelman at ubalt.edu (William Helman) Date: Thu, 23 Apr 2015 18:02:36 +0000 Subject: [Archivesspace_Users_Group] help using Shibboleth for staff-side authentication Message-ID: Hi all, I was wondering if any other campuses out there have experience implementing Shibboleth to authenticate the admin portion of ArchivesSpace? The University of Baltimore is starting phase two of implementation, moving our ArchivesSpace instance out of on-campus-network-only access to open Internet access. To make this move, our campus IT would like (if possible) to enable Shibboleth single sign on for the admin portion interface. We looked around a little and the most recent discussions on the topic seem to be from 2013 (here), which point towards this GitHub documentation. Our IT folks are hoping that they could speak with someone who has experience implementing Shibboleth in ArchivesSpace, in order to help us move forward here. Thanks, -Bill -- Head of Digital Services. The University of Baltimore, Langsdale Library whelman at ubalt.edu | 410-837-4209 | http://whelman.com | @thinkpol -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Thu Apr 23 16:45:03 2015 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 23 Apr 2015 20:45:03 +0000 Subject: [Archivesspace_Users_Group] FW: Clarification on MARCXML JIRA tickets In-Reply-To: <7fb0d35005eb4fd086f78c52c0d703db@ESGMTWEX12.win.ad.jhu.edu> References: <7fb0d35005eb4fd086f78c52c0d703db@ESGMTWEX12.win.ad.jhu.edu> Message-ID: Forwarded on behalf of Valerie Addonizio. The ArchivesSpace team will answer about what's in JIRA and future development plans in this area, but it would be great if others would talk about their experiences importing MARCXML into ArchivesSpace to give Valerie some ideas about options currently. -- Christine From: Valerie Addonizio [mailto:vaddoniz at jhu.edu] Sent: Thursday, April 23, 2015 4:32 PM To: archivesspace_users_group-bounces at lyralists.lyrasis.org Subject: Clarification on MARCXML JIRA tickets Greetings! As a relatively novice AS user I am still familiarizing myself with the varied ways information about AS is presented. On that front, I have a question regarding the tickets currently tagged "MARCXML." Hopefully this link works: https://archivesspace.atlassian.net/browse/AR-986?jql=project%20%3D%2010000%20AND%20labels%20%3D%20marcxml Specifically I am interested in these three tickets: AR-924 - Review and revise import of MARCXML for resources AR-914 - Review and revise import of agents headings from MARCXML AR-913 - Review and revise import of subjects from MARCXML Each of these is very broad, and each is slated for 2015_Track_Three. My roundabout question really is: does this mean a concentrated effort will be applied to the MARC XML imports, so much so that you are not creating individual tickets for individual issues, and when can we expect those reviews (i.e. what is 2015_Track_Three)? The reason I ask is that Hopkins is very much interested in importing our robust MARC XML records into AS as resources, then importing our container lists in EAD and merging the two. Without much knowledge of MARC XML, my tech services colleagues have already highlighted a number of issues with imports/exports, potentially making the plan unfeasible. I am personally wondering if I should just wait until the functionality is at its best, which is why I'm asking what we could expect as a result of those tickets, and when. Thank you! -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Thu Apr 23 17:01:55 2015 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Thu, 23 Apr 2015 21:01:55 +0000 Subject: [Archivesspace_Users_Group] Recent email In-Reply-To: <34e761c1b2af49af810179a72f04d3c3@ESGMTWEX12.win.ad.jhu.edu> References: <34e761c1b2af49af810179a72f04d3c3@ESGMTWEX12.win.ad.jhu.edu> Message-ID: Hi Valerie, Yes, you emailed the bounce address (which, somewhat confusingly, is what appears in the from: line when you see messages from the list!), rather than the address to send messages, which is archivesspace_users_group at lyralists.lyrasis.org (that's what appears in the to: line). People do that occasionally, and I typically just forward them so that they get to the right place. If you need anything else, please just let me know. Christine Christine Di Bella Community Outreach and Support Manager christine.dibella at lyrasis.org 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [cid:image003.png at 01CE734E.FD759D30] From: Valerie Addonizio [mailto:vaddoniz at jhu.edu] Sent: Thursday, April 23, 2015 4:52 PM To: Christine Di Bella Subject: Recent email Christine, Thank you very much for forwarding my recent email. Did I have the address wrong? I wouldn't want to repeat the same mistake. Thanks! -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7645 bytes Desc: image001.png URL: From kate_bowers at harvard.edu Thu Apr 23 17:56:39 2015 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Thu, 23 Apr 2015 21:56:39 +0000 Subject: [Archivesspace_Users_Group] Documentation of mapping of EAD attribute values on ingest to ArchivesSpace Message-ID: Can anyone point me to documentation of what happens to EAD attribute values on EAD ingest to ArchivesSpace? The only map I know of (http://www.archivesspace.org/sites/default/files/EAD-Import-Export-Mapping-20130831.xlsx) was ?Last updated: 8/31/13? and does not make any mention of attributes on some elements (for example, extent). Is there a newer map? Thanks, Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Fri Apr 24 09:34:46 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Fri, 24 Apr 2015 13:34:46 +0000 Subject: [Archivesspace_Users_Group] Documentation of mapping of EAD attribute values on ingest to ArchivesSpace In-Reply-To: References: Message-ID: <1429882486033.56859@lyrasis.org> Hi Kate, The EAD importer doesn't do anything with the extent attributes, which is why they're not mentioned in the spreadsheet. Instead, extent is formed by looking at the content ( like 3 boxes ), capturing the "amount" and the label. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Bowers, Kate A. Sent: Thursday, April 23, 2015 11:56 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Documentation of mapping of EAD attribute values on ingest to ArchivesSpace Can anyone point me to documentation of what happens to EAD attribute values on EAD ingest to ArchivesSpace? The only map I know of (http://www.archivesspace.org/sites/default/files/EAD-Import-Export-Mapping-20130831.xlsx) was "Last updated: 8/31/13" and does not make any mention of attributes on some elements (for example, extent). Is there a newer map? Thanks, Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers -------------- next part -------------- An HTML attachment was scrubbed... URL: From FPitaro at ap.org Fri Apr 24 10:48:53 2015 From: FPitaro at ap.org (Pitaro, Francesca) Date: Fri, 24 Apr 2015 14:48:53 +0000 Subject: [Archivesspace_Users_Group] Date Label in RDE Message-ID: <213B97E293CEAF4EA0383FF5B29E66ED817D1E83@CTCXMBX10.ap.org> Hello, Is there some way to set a default for the date label when using Rapid Data Entry? When I enter archival objects individually, my chosen default ("creation") pops into the field, but when I use the RDE to create the record, the date label field appears as "Other". It's very time consuming to then go back in and change the label for each archival object individually to "creation". Thanks, Francesca [cid:image001.jpg at 01D07E7A.F89441C0] [signature-96] Francesca Pitaro Processing Archivist AP Corporate Archives fpitaro at ap.org www.ap.org 450 W 33rd St New York, NY 10001 T 212.621.7446 The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1898 and delete this email. Thank you. [IP_US_DISC] msk dccc60c6d2c3a6438f0cf467d9a4938 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13756 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 14637 bytes Desc: image002.jpg URL: From lindsay-morecraft at uiowa.edu Fri Apr 24 10:51:43 2015 From: lindsay-morecraft at uiowa.edu (Morecraft, Lindsay M) Date: Fri, 24 Apr 2015 14:51:43 +0000 Subject: [Archivesspace_Users_Group] Date Label in RDE In-Reply-To: <213B97E293CEAF4EA0383FF5B29E66ED817D1E83@CTCXMBX10.ap.org> References: <213B97E293CEAF4EA0383FF5B29E66ED817D1E83@CTCXMBX10.ap.org> Message-ID: <96B305F061ED68428DDA721BECE2ED155166C306@ITSNT440.iowa.uiowa.edu> I asked about this a few weeks ago, and also agree with Francesca that it is very time consuming. It would be very helpful if there was a date label option in Rapid Data Entry. Thanks, Lindsay Moen (Morecraft) Processing Librarian Special Collections and University Archives The University of Iowa 319-335-5921 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Pitaro, Francesca Sent: Friday, April 24, 2015 9:49 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Date Label in RDE Hello, Is there some way to set a default for the date label when using Rapid Data Entry? When I enter archival objects individually, my chosen default ("creation") pops into the field, but when I use the RDE to create the record, the date label field appears as "Other". It's very time consuming to then go back in and change the label for each archival object individually to "creation". Thanks, Francesca [cid:image001.jpg at 01D07E74.447C0930] [signature-96] Francesca Pitaro Processing Archivist AP Corporate Archives fpitaro at ap.org www.ap.org 450 W 33rd St New York, NY 10001 T 212.621.7446 The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1898 and delete this email. Thank you. [IP_US_DISC] msk dccc60c6d2c3a6438f0cf467d9a4938 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13756 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 14637 bytes Desc: image002.jpg URL: From eckardm at umich.edu Fri Apr 24 13:29:53 2015 From: eckardm at umich.edu (Max Eckard) Date: Fri, 24 Apr 2015 13:29:53 -0400 Subject: [Archivesspace_Users_Group] Subject headings for type of material Message-ID: Hello everyone, We're currently working through how to clean up and import our 2800+ legacy EAD finding aids into ArchivesSpace, and making good progress! We've run across a bit of a tricky issue, however, that we don't quite know how to overcome. Our current practice is to divide our collection-level subjects into different headings for type of material, such as Visual Materials or Manuscripts (see this example , and there are a few other categories as well). We do this frequently. Note: You'll see that we've also included Genre Terms, but I think we have a good idea of how to handle these (perhaps by designating them by source or type in ArchivesSpace). If it helps these are tags before the subjects inside of the tag in the EAD. For example: Subjects - Visual Materials: etc. How are people handling these categories for type of material (not to be confused with Type of subject term), upon import? ASpace doesn't recognize the field. We thought about using the Scope Note or External Source field, but neither of those seem quite right, especially going forward. We thought about indicating category based on source of subject term, but that won't always work because of overlap. We also thought about moving subjects for Visual Materials to the appropriate component, but there won't always be a clear cut relationship between these subjects and a particular component. These divisions are important for us to maintain, but just don't know how to do it. I've searched the list archive without a lot of luck. We'd be happy to hear how other people are handling this, or any ideas they might have for how to import this information into ArchivesSpace (even if all it did was visually replicate what we're doing). Thanks! Max -- *Max Eckard* *Assistant Archivist for Digital Curation* Bentley Historical Library 1150 Beal Ave. Ann Arbor, MI 48109-2113 734/763-7518 <734.763.7518> http://bentley.umich.edu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Fri Apr 24 13:46:56 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Fri, 24 Apr 2015 13:46:56 -0400 Subject: [Archivesspace_Users_Group] Subject headings for type of material In-Reply-To: References: Message-ID: Hi Max, I'm not sure I have any ideas (we don't currently utilize something like this), but just to clarify, you basically want your subjects grouped into categories? Do you want the categories to be searchable as well? Or you would just like for every subject that there be a label including what it's 'category' is? Is the important thing the mimicking of the structure, or just that the information is there? -Maura On Fri, Apr 24, 2015 at 1:29 PM, Max Eckard wrote: > Hello everyone, > > We're currently working through how to clean up and import our 2800+ > legacy EAD finding aids into ArchivesSpace, and making good progress! > > We've run across a bit of a tricky issue, however, that we don't quite > know how to overcome. Our current practice is to divide our > collection-level subjects into different headings for type of material, > such as Visual Materials or Manuscripts (see this example > , > and there are a few other categories as well). We do this frequently. > > Note: You'll see that we've also included Genre Terms, but I think we have > a good idea of how to handle these (perhaps by designating them by source > or type in ArchivesSpace). > > If it helps these are tags before the subjects inside of the > tag in the EAD. For example: > > > Subjects - Visual Materials: > > > > etc. > > > How are people handling these categories for type of material (not to be > confused with Type of subject term), upon import? ASpace doesn't recognize > the field. > > We thought about using the Scope Note or External Source field, but > neither of those seem quite right, especially going forward. We thought > about indicating category based on source of subject term, but that won't > always work because of overlap. We also thought about moving subjects for > Visual Materials to the appropriate component, but there won't always be a > clear cut relationship between these subjects and a particular component. > > These divisions are important for us to maintain, but just don't know how > to do it. I've searched the list archive without a lot of luck. We'd be > happy to hear how other people are handling this, or any ideas they might > have for how to import this information into ArchivesSpace (even if all it > did was visually replicate what we're doing). > > Thanks! > Max > > > -- > *Max Eckard* > *Assistant Archivist for Digital Curation* > > > Bentley Historical Library > 1150 Beal Ave. > Ann Arbor, MI 48109-2113 > 734/763-7518 <734.763.7518> > http://bentley.umich.edu/ > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From eckardm at umich.edu Fri Apr 24 13:59:10 2015 From: eckardm at umich.edu (Max Eckard) Date: Fri, 24 Apr 2015 13:59:10 -0400 Subject: [Archivesspace_Users_Group] Subject headings for type of material In-Reply-To: References: Message-ID: Hi Maura, Good question. I think we'd settle for the information just being there (at the very least that would replicate what we're currently doing), but I think we'd also be interested in mimicking the structure to see if we could make better use of these categories. Thanks! Max On Fri, Apr 24, 2015 at 1:46 PM, Maura Carbone wrote: > Hi Max, > I'm not sure I have any ideas (we don't currently utilize something like > this), but just to clarify, you basically want your subjects grouped into > categories? Do you want the categories to be searchable as well? Or you > would just like for every subject that there be a label including what it's > 'category' is? Is the important thing the mimicking of the structure, or > just that the information is there? > > -Maura > > On Fri, Apr 24, 2015 at 1:29 PM, Max Eckard wrote: > >> Hello everyone, >> >> We're currently working through how to clean up and import our 2800+ >> legacy EAD finding aids into ArchivesSpace, and making good progress! >> >> We've run across a bit of a tricky issue, however, that we don't quite >> know how to overcome. Our current practice is to divide our >> collection-level subjects into different headings for type of material, >> such as Visual Materials or Manuscripts (see this example >> , >> and there are a few other categories as well). We do this frequently. >> >> Note: You'll see that we've also included Genre Terms, but I think we >> have a good idea of how to handle these (perhaps by designating them by >> source or type in ArchivesSpace). >> >> If it helps these are tags before the subjects inside of the >> tag in the EAD. For example: >> >> >> Subjects - Visual Materials: >> >> >> >> etc. >> >> >> How are people handling these categories for type of material (not to be >> confused with Type of subject term), upon import? ASpace doesn't recognize >> the field. >> >> We thought about using the Scope Note or External Source field, but >> neither of those seem quite right, especially going forward. We thought >> about indicating category based on source of subject term, but that won't >> always work because of overlap. We also thought about moving subjects for >> Visual Materials to the appropriate component, but there won't always be a >> clear cut relationship between these subjects and a particular component. >> >> These divisions are important for us to maintain, but just don't know how >> to do it. I've searched the list archive without a lot of luck. We'd be >> happy to hear how other people are handling this, or any ideas they might >> have for how to import this information into ArchivesSpace (even if all it >> did was visually replicate what we're doing). >> >> Thanks! >> Max >> >> >> -- >> *Max Eckard* >> *Assistant Archivist for Digital Curation* >> >> >> Bentley Historical Library >> 1150 Beal Ave. >> Ann Arbor, MI 48109-2113 >> 734/763-7518 <734.763.7518> >> http://bentley.umich.edu/ >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Maura Carbone > Digital Initiatives Librarian > Brandeis University > Library and Technology Services > (781) 736-4659 > 415 South Street, (MS 017/P.O. Box 549110) > Waltham, MA 02454-9110 > email: mauraa at brandeis.edu > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- *Max Eckard* *Assistant Archivist for Digital Curation* Bentley Historical Library 1150 Beal Ave. Ann Arbor, MI 48109-2113 734/763-7518 <734.763.7518> http://bentley.umich.edu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From putirskis.1 at osu.edu Fri Apr 24 17:28:06 2015 From: putirskis.1 at osu.edu (Putirskis, Crystal E. (Cate)) Date: Fri, 24 Apr 2015 21:28:06 +0000 Subject: [Archivesspace_Users_Group] FW: Clarification on MARCXML JIRA tickets In-Reply-To: References: <7fb0d35005eb4fd086f78c52c0d703db@ESGMTWEX12.win.ad.jhu.edu> Message-ID: <782EFBE964BFC34E893C7FF255B5F20F36443E18@CIO-TNC-D2MBX06.osuad.osu.edu> Valerie, At Ohio State University, we will be pursuing what sounds like a similar ingest project to the one you're investigating: ingesting MARC records to create Resources in ASpace, and then subsequently attaching EAD-encoded container lists for those resources in a follow-up ingest project. We're very near, time-wise, to looking closely at how we'll do this, and we would definitely appreciate the opportunity to pool resources or share ideas, if possible. (Please contact me, if this is of interest at your end.) We, too, are wondering if any other institutions out there are looking at a similar ingest strategy? Cate [The Ohio State University] Cate Putirskis Special Collections Processing Coordinator University Libraries - Special Collections Description & Access 016 Thompson Library | 1858 Neil Ave Mall, Columbus, OH 43210 614-292-8114 putirskis.1 at osu.edu From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella Sent: Thursday, April 23, 2015 4:45 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] FW: Clarification on MARCXML JIRA tickets Forwarded on behalf of Valerie Addonizio. The ArchivesSpace team will answer about what's in JIRA and future development plans in this area, but it would be great if others would talk about their experiences importing MARCXML into ArchivesSpace to give Valerie some ideas about options currently. -- Christine From: Valerie Addonizio [mailto:vaddoniz at jhu.edu] Sent: Thursday, April 23, 2015 4:32 PM To: archivesspace_users_group-bounces at lyralists.lyrasis.org Subject: Clarification on MARCXML JIRA tickets Greetings! As a relatively novice AS user I am still familiarizing myself with the varied ways information about AS is presented. On that front, I have a question regarding the tickets currently tagged "MARCXML." Hopefully this link works: https://archivesspace.atlassian.net/browse/AR-986?jql=project%20%3D%2010000%20AND%20labels%20%3D%20marcxml Specifically I am interested in these three tickets: AR-924 - Review and revise import of MARCXML for resources AR-914 - Review and revise import of agents headings from MARCXML AR-913 - Review and revise import of subjects from MARCXML Each of these is very broad, and each is slated for 2015_Track_Three. My roundabout question really is: does this mean a concentrated effort will be applied to the MARC XML imports, so much so that you are not creating individual tickets for individual issues, and when can we expect those reviews (i.e. what is 2015_Track_Three)? The reason I ask is that Hopkins is very much interested in importing our robust MARC XML records into AS as resources, then importing our container lists in EAD and merging the two. Without much knowledge of MARC XML, my tech services colleagues have already highlighted a number of issues with imports/exports, potentially making the plan unfeasible. I am personally wondering if I should just wait until the functionality is at its best, which is why I'm asking what we could expect as a result of those tickets, and when. Thank you! -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 3605 bytes Desc: image001.png URL: From brad.westbrook at lyrasis.org Mon Apr 27 08:37:15 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Mon, 27 Apr 2015 12:37:15 +0000 Subject: [Archivesspace_Users_Group] FW: Clarification on MARCXML JIRA tickets In-Reply-To: References: <7fb0d35005eb4fd086f78c52c0d703db@ESGMTWEX12.win.ad.jhu.edu> Message-ID: Hi, Valerie, During 2015, the ArchivesSpace migration team (members of the Technical and User Advisory Councils) will be conducting reviews of all formatted data import / exports, and, if problems are revealed via those reviews, they will adjust the importers appropriately. I encourage you to share to this list the issues with MARC imports / exports that your colleagues have noted. They will then be reviewed and, if appropriate, added to one of the MARCXML tickets you list in your note below. Best, 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 Christine Di Bella Sent: Thursday, April 23, 2015 4:45 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] FW: Clarification on MARCXML JIRA tickets Forwarded on behalf of Valerie Addonizio. The ArchivesSpace team will answer about what's in JIRA and future development plans in this area, but it would be great if others would talk about their experiences importing MARCXML into ArchivesSpace to give Valerie some ideas about options currently. -- Christine From: Valerie Addonizio [mailto:vaddoniz at jhu.edu] Sent: Thursday, April 23, 2015 4:32 PM To: archivesspace_users_group-bounces at lyralists.lyrasis.org Subject: Clarification on MARCXML JIRA tickets Greetings! As a relatively novice AS user I am still familiarizing myself with the varied ways information about AS is presented. On that front, I have a question regarding the tickets currently tagged "MARCXML." Hopefully this link works: https://archivesspace.atlassian.net/browse/AR-986?jql=project%20%3D%2010000%20AND%20labels%20%3D%20marcxml Specifically I am interested in these three tickets: AR-924 - Review and revise import of MARCXML for resources AR-914 - Review and revise import of agents headings from MARCXML AR-913 - Review and revise import of subjects from MARCXML Each of these is very broad, and each is slated for 2015_Track_Three. My roundabout question really is: does this mean a concentrated effort will be applied to the MARC XML imports, so much so that you are not creating individual tickets for individual issues, and when can we expect those reviews (i.e. what is 2015_Track_Three)? The reason I ask is that Hopkins is very much interested in importing our robust MARC XML records into AS as resources, then importing our container lists in EAD and merging the two. Without much knowledge of MARC XML, my tech services colleagues have already highlighted a number of issues with imports/exports, potentially making the plan unfeasible. I am personally wondering if I should just wait until the functionality is at its best, which is why I'm asking what we could expect as a result of those tickets, and when. Thank you! -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7640 bytes Desc: image001.png URL: From ns96 at nyu.edu Mon Apr 27 08:54:15 2015 From: ns96 at nyu.edu (Nathan Stevens) Date: Mon, 27 Apr 2015 08:54:15 -0400 Subject: [Archivesspace_Users_Group] Anyone experience AT to ASpace migration error concerning empty notes in Resource record? Message-ID: Hi, We are in the process of trying to resolve a bug in the AT migration tool in which empty notes are being copied and causing the migration of that particular Resource record to fail. As such, we need a real dataset to test thst the fix we have in place works. So if your institution has seen this error, please contact me at ns96 at nyu.edu so we can get a copy of the AT database to work with. P.S I believe it was reported once on this list, but now I can't find the relevant message. -------------- next part -------------- An HTML attachment was scrubbed... URL: From vaddoniz at jhu.edu Mon Apr 27 14:19:09 2015 From: vaddoniz at jhu.edu (Valerie Addonizio) Date: Mon, 27 Apr 2015 18:19:09 +0000 Subject: [Archivesspace_Users_Group] Bulk publish of agents? Message-ID: Greetings everyone, I have searched through the listserv for any information on the ability to bulk publish or set publish as a default for agents, and I am uncertain if this has been addressed in the current release. I am importing MARC XML for resource records and find that every agent defaults to unpublished. Is there a way for me to select-all and publish all agents? I did not see it in JIRA, but as you may already have realized, I'm new to these parts. -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Mon Apr 27 14:50:24 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Mon, 27 Apr 2015 18:50:24 +0000 Subject: [Archivesspace_Users_Group] Bulk publish of agents? In-Reply-To: References: Message-ID: Hi, Valerie, In "My Global Preferences", [cid:image001.jpg at 01D080F9.A5B2B9B0] You can set the "Publish" option to True (checkmark): [cid:image002.jpg at 01D080F9.A5B2B9B0] All new records, imported or newly created in your application will be set to publish. You can then turn publish off for any records you do not want sent to the public interface. Let us know if you have additional questions. 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 Valerie Addonizio Sent: Monday, April 27, 2015 2:19 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Bulk publish of agents? Greetings everyone, I have searched through the listserv for any information on the ability to bulk publish or set publish as a default for agents, and I am uncertain if this has been addressed in the current release. I am importing MARC XML for resource records and find that every agent defaults to unpublished. Is there a way for me to select-all and publish all agents? I did not see it in JIRA, but as you may already have realized, I'm new to these parts. -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4649 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 16833 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7640 bytes Desc: image003.png URL: From morinj at usc.edu Mon Apr 27 14:56:40 2015 From: morinj at usc.edu (Jacqueline Morin) Date: Mon, 27 Apr 2015 18:56:40 +0000 Subject: [Archivesspace_Users_Group] Note Labels in RDE? Message-ID: Not sure if I am just missing something obvious, but when trying to add "notes" such as a General note in RDE, there doesn't seem to be a field for "note label." There's just the "note type" and the "content." In the "slow data entry" mode, adding the note label lets the note be displayed as "General Note." Without the label, the default is the note type and it will just be displayed as "Gneral." Is there a way to get that note label in Rapid Data Entry? Thanks for any help! ---Jackie Morin Jacqueline Morin, M.L.I.S. Processing Archivist, Special Collections Doheny Memorial Library University of Southern California 3550 Trousdale Parkway Los Angeles, CA 90089-0182 Tel: 213-821-0488 Fax: 213-740-6668 -------------- next part -------------- An HTML attachment was scrubbed... URL: From vaddoniz at jhu.edu Mon Apr 27 15:26:43 2015 From: vaddoniz at jhu.edu (Valerie Addonizio) Date: Mon, 27 Apr 2015 19:26:43 +0000 Subject: [Archivesspace_Users_Group] Bulk publish of agents? In-Reply-To: References: Message-ID: Excellent, thank you for the explanation! -Valerie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brad Westbrook Sent: Monday, April 27, 2015 2:50 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Bulk publish of agents? Hi, Valerie, In "My Global Preferences", [cid:image001.jpg at 01D080FE.909D49A0] You can set the "Publish" option to True (checkmark): [cid:image002.jpg at 01D080FE.909D49A0] All new records, imported or newly created in your application will be set to publish. You can then turn publish off for any records you do not want sent to the public interface. Let us know if you have additional questions. 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 Valerie Addonizio Sent: Monday, April 27, 2015 2:19 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Bulk publish of agents? Greetings everyone, I have searched through the listserv for any information on the ability to bulk publish or set publish as a default for agents, and I am uncertain if this has been addressed in the current release. I am importing MARC XML for resource records and find that every agent defaults to unpublished. Is there a way for me to select-all and publish all agents? I did not see it in JIRA, but as you may already have realized, I'm new to these parts. -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 4649 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 16833 bytes Desc: image002.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 7640 bytes Desc: image003.png URL: From mlevy at ushmm.org Mon Apr 27 16:52:46 2015 From: mlevy at ushmm.org (Levy, Michael) Date: Mon, 27 Apr 2015 16:52:46 -0400 Subject: [Archivesspace_Users_Group] Database migration from 1.0.9 to 1.2.0 produces NoMethodError: undefined method `to_sequel_blob' for # In-Reply-To: References: <4080B059-CCA9-4D05-BEDD-D064C23288EE@gmail.com> <28D3226C-2186-48CA-AE97-14D9D3581082@gmail.com> Message-ID: Working on the same situation as previously with some sample data entered in a 1.0.9 version which I'm trying to upgrade. I ran git clone today, got the current head version, built the zip file in a development environment, put the zip file where I wanted it, unzipped it, copied the data directory from the 1.0.9 version replacing the data directory from the zipped version, and modified config.rb just to have it run on a set of 5 unused ports (the older version on 1.0.9 is using the default ports). Starting, I got a number of errors that seem to relate to attempts to run migrations. Any tips? Should I use one of the tagged versions instead of head? I'd be happy to share the entire log file but I think the first part of the log is showing that it is having trouble running a database migration. I have not tried to set resequence_on_startup (which doesn't seem to relate to startup errors). Thanks for any help. Loading ArchivesSpace configuration file from path: /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/config/config.rb Loading ArchivesSpace configuration file from path: /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/config/config.rb 2015-04-27 15:24:39.585:INFO:oejs.Server:jetty-8.1.5.v20120716 2015-04-27 15:24:40.059:INFO:/:INFO: jruby 1.7.18 (1.9.3p551) 2014-12-22 625381c on Java HotSpot(TM) 64-Bit Server VM 1.6.0_26-b03 +jit [linux-amd64] 2015-04-27 15:24:40.061:INFO:/:INFO: using a shared (threadsafe!) runtime Loading ArchivesSpace configuration file from path: /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/config/config.rb Running database migrations for demo database 2015-04-27 15:25:00.901:INFO:/:An exception happened during JRuby-Rack startup|Java::JavaSql::SQLException: Failed to start database '/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/archivesspace_demo_db' with class loader org.jruby.util.JRubyClassLoader at 1f72e08e, see the next exception for details.|--- System|jruby 1.7.18 (1.9.3p551) 2014-12-22 625381c on Java HotSpot(TM) 64-Bit Server VM 1.6.0_26-b03 +jit [linux-amd64]|Time: 2015-04-27 15:25:00 -0400|Server: jetty/8.1.5.v20120716|jruby.home: file:/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home||--- Context Init Parameters:|jruby.compat.version = 1.9|jruby.max.runtimes = 1|jruby.min.runtimes = 1|public.root = /|rack.env = production||--- Backtrace|Sequel::DatabaseConnectionError: Java::JavaSql::SQLException: Failed to start database '/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/archivesspace_demo_db' with class loader org.jruby.util.JRubyClassLoader at 1f72e08e, see the next exception for details.| make_new at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool.rb:110| make_new at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:160| available at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:137| acquire at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:127| sync at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:201| synchronize at org/jruby/ext/thread/Mutex.java:149| sync at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:201| acquire at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:126| hold at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:88| synchronize at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255| execute at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244| execute_ddl at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:270| create_table_from_generator at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/schema_methods.rb:641| create_table at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/schema_methods.rb:195| create_table? at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/schema_methods.rb:223| schema_dataset at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:584| initialize at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:444| initialize at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:506| run at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:391| setup_database at file:/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/lib/common.jar!/db/db_migrator.rb:184| prepare_database at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap.rb:64| connect at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:69| connect at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/core.rb:95| prepare_database at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap.rb:62| init at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap.rb:40| (root) at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/main.rb:10| require at org/jruby/RubyKernel.java:1071| require at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:55| require at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:53| (root) at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/config.ru:1| instance_eval at org/jruby/RubyBasicObject.java:1533| (root) at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/config.ru:4| initialize at /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-rack-1.1.18/lib/jruby-rack-1.1.18.jar!/vendor/rack-1.5.2/rack/builder.rb:55| start_server at launcher/launcher.rb:86| main at launcher/launcher.rb:147| (root) at launcher/launcher.rb:230||--- RubyGems|Gem.dir: /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems|Gem.path:|/home/www/.gem/jruby/1.9|file:/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/gems/shared|/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems|Activated gems:| json-1.8.0-java| bundler-1.7.12| rake-10.4.2| i18n-0.7.0| multi_json-1.11.0| activesupport-3.2.19| atomic-1.0.1-java| htmlentities-4.3.3| nokogiri-1.6.6.2-java| rubyzip-1.0.0| axlsx-2.0.1| backports-3.6.4| bcrypt-3.1.7-java| diff-lcs-1.1.3| eventmachine-1.0.7-java| factory_girl-4.1.0| jdbc-derby-10.6.2.1-java| jdbc-mysql-5.1.13| jruby-jars-1.7.18| jruby-rack-1.1.18| json-schema-1.0.10| ladle-0.2.0-java| multipart-post-1.2.0| net-http-persistent-2.8| net-ldap-0.6.1| rack-1.4.5| puma-2.8.2-java| rack-protection-1.5.3| sequel-4.20.0| rack-session-sequel-0.0.1| rack-test-0.6.3| rjack-jackson-1.8.11.0-java| rspec-core-2.12.1| rspec-expectations-2.12.1| rspec-mocks-2.12.2| rspec-2.12.0| rufus-lru-1.0.5| tzinfo-0.3.39| rufus-scheduler-2.0.24| saxerator-0.9.5| saxon-xslt-0.5.1-java| simplecov-html-0.7.1| simplecov-0.7.1| tilt-1.4.1| sinatra-1.3.6| sinatra-contrib-1.3.2| sinatra-reloader-1.0| warbler-1.4.2| zip-zip-0.3||--- Bundler|Bundler.bundle_path: /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems|Bundler.root: /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF|Gemfile: /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/Gemfile|Settings:| bin_path = /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/bundler-1.7.12/bin/bundle| gemfile = /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/Gemfile||--- JRuby-Rack Config|compat_version = RUBY1_9|default_logger = org.jruby.rack.logging.StandardOutLogger at 6724e231|equals = |err = java.io.PrintStream at 15335332|filter_adds_html = true|filter_verifies_resource = false|ignore_environment = false|initial_memory_buffer_size = |initial_runtimes = 1|jms_connection_factory = |jms_jndi_properties = |logger = org.jruby.rack.logging.ServletContextLogger at 3d2a07c9|logger_class_name = servlet_context|logger_name = jruby.rack|maximum_memory_buffer_size = |maximum_runtimes = 1|num_initializer_threads = |out = java.io.PrintStream at 34c1efe7|rackup = |rackup_path = |rewindable = true|runtime_arguments = |runtime_environment = |runtime_timeout_seconds = |serial_initialization = false|servlet_context = ServletContext at o.e.j.w.WebAppContext{/,file:/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/},/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/wars/backend.war|throw_init_exception = false| 2015-04-27 15:25:00.905:WARN:/:ERROR: initialization failed org.jruby.rack.RackInitializationException: Java::JavaSql::SQLException: Failed to start database '/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/archivesspace_demo_db' with class loader org.jruby.util.JRubyClassLoader at 1f72e08e, see the next exception for details.|?from java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:597)|?from RUBY.connect(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:219)|?from RUBY.make_new(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool.rb:101)|?from RUBY.make_new(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:160)|?from RUBY.available(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:137)|?from RUBY.acquire(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:127)|?from RUBY.sync(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:201)|?from org.jruby.ext.thread.Mutex.synchronize(org/jruby/ext/thread/Mutex.java:149)|?from RUBY.sync(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:201)|?from RUBY.acquire(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:126)|?from RUBY.hold(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:88)|?from RUBY.synchronize(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255)|?from RUBY.execute(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244)|?from RUBY.execute_ddl(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:270)|?from RUBY.create_table_from_generator(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/schema_methods.rb:641)|?from RUBY.create_table(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/schema_methods.rb:195)|?from RUBY.create_table?(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/schema_methods.rb:223)|?from RUBY.schema_dataset(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:584)|?from RUBY.initialize(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:444)|?from RUBY.initialize(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:506)|?from RUBY.run(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:391)|?from RUBY.setup_database(file:/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/lib/common.jar!/db/db_migrator.rb:184)|?from RUBY.prepare_database(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap.rb:64)|?from RUBY.connect(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:69)|?from RUBY.connect(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/core.rb:95)|?from RUBY.prepare_database(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap.rb:62)|?from RUBY.init(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap.rb:40)|?from RUBY.(root)(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/main.rb:10)|?from org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1071)|?from Kernel.require(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:55)|?from Kernel.require(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:55)|?from Kernel.require(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:53)|?from Kernel.require(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:53)|?from RUBY.(root)(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/config.ru:1)|?from org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1533)|?from RUBY.(root)(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/config.ru:4)|?from RUBY.initialize(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-rack-1.1.18/lib/jruby-rack-1.1.18.jar!/vendor/rack-1.5.2/rack/builder.rb:55)|?from org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(org/eclipse/jetty/server/handler/ContextHandler.java:766)|?from org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(org/eclipse/jetty/servlet/ServletContextHandler.java:406)|?from org.eclipse.jetty.server.handler.ContextHandler.startContext(org/eclipse/jetty/server/handler/ContextHandler.java:758)|?from org.eclipse.jetty.servlet.ServletContextHandler.startContext(org/eclipse/jetty/servlet/ServletContextHandler.java:242)|?from org.eclipse.jetty.webapp.WebAppContext.startContext(org/eclipse/jetty/webapp/WebAppContext.java:1233)|?from org.eclipse.jetty.server.handler.ContextHandler.doStart(org/eclipse/jetty/server/handler/ContextHandler.java:701)|?from org.eclipse.jetty.webapp.WebAppContext.doStart(org/eclipse/jetty/webapp/WebAppContext.java:475)|?from org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)|?from org.eclipse.jetty.server.handler.HandlerCollection.doStart(org/eclipse/jetty/server/handler/HandlerCollection.java:224)|?from org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(org/eclipse/jetty/server/handler/ContextHandlerCollection.java:167)|?from org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)|?from org.eclipse.jetty.server.handler.HandlerWrapper.doStart(org/eclipse/jetty/server/handler/HandlerWrapper.java:90)|?from org.eclipse.jetty.server.Server.doStart(org/eclipse/jetty/server/Server.java:272)|?from org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)|?from java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:597)|?from launcher.launcher.start_server(launcher/launcher.rb:86)|?from launcher.launcher.start_server(launcher/launcher/launcher.rb:86)|?from launcher.launcher.main(launcher/launcher.rb:147)|?from launcher.launcher.main(launcher/launcher/launcher.rb:147)|?from launcher.launcher.(root)(launcher/launcher.rb:230)|?from launcher.launcher.(root)(launcher/launcher/launcher.rb:230)| at org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) at org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) at org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) at org.eclipse.jetty.server.Server.doStart(Server.java:272) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:440) at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:304) at org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:52) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:306) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:136) at launcher.launcher.method__1$RUBY$start_server(launcher/launcher.rb:86) at launcher$launcher$method__1$RUBY$start_server.call(launcher$launcher$method__1$RUBY$start_server) at org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:218) at org.jruby.internal.runtime.methods.CompiledMethod.call(CompiledMethod.java:268) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:346) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:204) at launcher.launcher.chained_4_rescue_1$RUBY$SYNTHETICmain(launcher/launcher.rb:147) at launcher.launcher.method__3$RUBY$main(launcher/launcher.rb:145) at launcher$launcher$method__3$RUBY$main.call(launcher$launcher$method__3$RUBY$main) at launcher$launcher$method__3$RUBY$main.call(launcher$launcher$method__3$RUBY$main) at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:306) at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:136) at launcher.launcher.__file__(launcher/launcher.rb:230) at launcher.launcher.load(launcher/launcher.rb) at org.jruby.Ruby.runScript(Ruby.java:866) at org.jruby.Ruby.runScript(Ruby.java:859) at org.jruby.Ruby.runNormally(Ruby.java:728) at org.jruby.Ruby.runFromMain(Ruby.java:577) at org.jruby.Main.doRunFromMain(Main.java:395) at org.jruby.Main.internalRun(Main.java:290) at org.jruby.Main.run(Main.java:217) at org.jruby.Main.main(Main.java:197) Caused by: org.jruby.exceptions.RaiseException: (DatabaseConnectionError) Java::JavaSql::SQLException: Failed to start database '/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/archivesspace_demo_db' with class loader org.jruby.util.JRubyClassLoader at 1f72e08e, see the next exception for details. On Thu, Apr 2, 2015 at 5:22 PM, Levy, Michael wrote: > We'll be happy to wait for a fix. Thanks Brian. > > On Thu, Apr 2, 2015 at 5:20 PM, Brian Hoffman > wrote: > >> Hi Michael, >> >> I think the best thing would be to wait for us to fix it. We?ll post a >> minor release next week. Can you wait till then? I?d hate for your data to >> get corrupted. >> >> Brian >> >> >> >> On Apr 2, 2015, at 5:17 PM, Levy, Michael wrote: >> >> Any suggestions on what I ought to try to work around this issue? Should >> I try running the upgrade incrementally from the 1.0.9 instance I have >> running to some other interim version(s) and then on to 1.2.0? >> >> In my initial posting I did not finish a sentence. I merely meant to say >> I copied the data folder and configuration, and that I had not added any >> plugins. >> >> On Thu, Apr 2, 2015 at 12:07 PM, Brian Hoffman >> wrote: >> >>> Thank you! >>> >>> https://archivesspace.atlassian.net/browse/AR-1188 >>> >>> >>> On Apr 2, 2015, at 12:02 PM, Levy, Michael wrote: >>> >>> > Starting with a small test instance with no modifications, under RHEL, >>> using derby, from a working v1.0.9 instance (which had been stopped), and >>> then attempting to upgrade to 1.2.0. I just copied the >>> > >>> > [www at saturn archivesspace-v1.2.0]$ scripts/setup-database.sh >>> > Loading ArchivesSpace configuration file from path: >>> /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb >>> > Loading ArchivesSpace configuration file from path: >>> /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb >>> > Running migrations against >>> jdbc:derby:/data/sites/apps/public/archivesspace-v1.2.0/data/archivesspace_demo_db;create=true;aspacedemo=true >>> > Adding separate permissions for updating major record types >>> > ... accession records >>> > ... resource records >>> > ... digital object records >>> > ... running import jobs >>> > ... managing vocabulary records >>> > Updating groups to include the new permssions >>> > Deleting update_archival_record permission >>> > Adding 'Date Not Yet Determined' to resource 2/4 >>> > Adding 'Date Not Yet Determined' to resource 2/23 >>> > Adding 'Date Not Yet Determined' to resource 2/24 >>> > >>> > ............ >>> > >>> > Adding 'Date Not Yet Determined' to resource 2/52 >>> > Adding 'Date Not Yet Determined' to resource 2/53 >>> > *** ADDING SOME ENUMS >>> > *** Genre Form to note_index_item_type enum list >>> > Triggering reindex of resource >>> > Triggering reindex of archival_object >>> > Triggering reindex of digital_object >>> > Making location_temporary list editble >>> > {:id=>1, :import_type=>"marcxml_lcnaf_subjects_and_agents", >>> :repo_id=>2, :lock_version=>5, :json_schema_version=>1, >>> :filenames=>"[\"lcnaf_import_d2adf1d5-64f5-4577-b55a-2e00b3bac1d5\"]", >>> :time_submitted=>2014-03-26 17:51:23 UTC, :time_started=>2014-03-26 >>> 17:51:27 UTC, :time_finished=>2014-03-26 17:51:42 UTC, :owner_id=>1, >>> :status=>"completed", :created_by=>"admin", :last_modified_by=>"admin", >>> :create_time=>2014-03-26 17:51:23 UTC, :system_mtime=>2014-03-26 17:51:42 >>> UTC, :user_mtime=>2014-03-26 17:51:23 UTC} >>> > 1297 >>> > NoMethodError: undefined method `to_sequel_blob' for >>> # >>> > blobify at >>> /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/utils.rb:33 >>> > (root) at >>> /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:44 >>> > each at org/jruby/RubyArray.java:1613 >>> > (root) at >>> /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:37 >>> > instance_eval at org/jruby/RubyBasicObject.java:1533 >>> > apply at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:100 >>> > run at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:528 >>> > _transaction at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134 >>> > transaction at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108 >>> > hold at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98 >>> > hold at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87 >>> > synchronize at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255 >>> > transaction at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97 >>> > checked_transaction at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:464 >>> > run at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:527 >>> > each at org/jruby/RubyArray.java:1613 >>> > run at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:524 >>> > run at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:391 >>> > setup_database at >>> file:/data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/db_migrator.rb:184 >>> > (root) at ../scripts/rb/migrate_db.rb:43 >>> > connect at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:69 >>> > connect at >>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/core.rb:95 >>> > (root) at ../scripts/rb/migrate_db.rb:28 >>> > [www at saturn archivesspace-v1.2.0]$ >>> > >>> > _______________________________________________ >>> > Archivesspace_Users_Group mailing list >>> > Archivesspace_Users_Group at lyralists.lyrasis.org >>> > >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvb at sfasu.edu Mon Apr 27 17:16:13 2015 From: jvb at sfasu.edu (Johna L Von Behrens) Date: Mon, 27 Apr 2015 21:16:13 +0000 Subject: [Archivesspace_Users_Group] Database migration from 1.0.9 to 1.2.0 produces NoMethodError: undefined method `to_sequel_blob' for # In-Reply-To: References: <4080B059-CCA9-4D05-BEDD-D064C23288EE@gmail.com> <28D3226C-2186-48CA-AE97-14D9D3581082@gmail.com> Message-ID: Does anyone know why it might be ?better? to put your locations in the Instances under the main Resource or to add the Location to the Instances under each Box or Item (whatever level you are describing to). I am wondering what the benefits are to having the locations in either or both places???? Johna Von Behrens, MLIS, MSED Archives and Repository Librarian East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.4117 asketrc at sfasu.edu The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvb at sfasu.edu Mon Apr 27 17:17:06 2015 From: jvb at sfasu.edu (Johna L Von Behrens) Date: Mon, 27 Apr 2015 21:17:06 +0000 Subject: [Archivesspace_Users_Group] Locations Message-ID: Sorry I forgot to change the Subject ? Does anyone know why it might be ?better? to put your locations in the Instances under the main Resource or to add the Location to the Instances under each Box or Item (whatever level you are describing to). I am wondering what the benefits are to having the locations in either or both places???? Johna Von Behrens, MLIS, MSED Archives and Repository Librarian East Texas Research Center Stephen F. Austin State University PO Box 13055 SFA Station Nacogdoches, TX 75962 Phone 936.468.1536 Fax 936.468.4117 asketrc at sfasu.edu The views and opinions expressed in this message are my own and do not necessarily reflect the views and opinions of Stephen F. Austin State University, its Board of Regents, or the State of Texas. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexanderduryee at nypl.org Mon Apr 27 17:24:49 2015 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Mon, 27 Apr 2015 17:24:49 -0400 Subject: [Archivesspace_Users_Group] API Querying of Names Message-ID: We're developing a migration tool to import records from our database into ArchivesSpace via the API. For each controlled access name in each collection, our tool needs to know if a name record exists in ArchivesSpace, and if so, query its ID in order to build the collection-name link. However, the only method that I've found to discover agent/family/corp records (knowing only the type and title string) via the API is GET /search/. Using GET /search/ for discovering name records is proving unwieldy, as there is a long delay (~30 seconds on localhost) between POSTing a new name record and having it return in the index. When generating many records at once, this leads to frequent false negatives. It also makes for slow discovery, as a full search query has to be run, then some number of the results iterated through, for every name. Is there a more direct way to query ArchivesSpace for name records, ideally bypassing search altogether? If not, how are other API users developing methods to match name records to ArchivesSpace objects? Many thanks, --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Tue Apr 28 15:10:56 2015 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Tue, 28 Apr 2015 19:10:56 +0000 Subject: [Archivesspace_Users_Group] FW: LYRASIS Offering classes on metadata, digital curation, and disaster planning In-Reply-To: References: Message-ID: Forwarded on behalf of Alix Bentrud of LYRASIS. From: Alix Bentrud Sent: Tuesday, April 28, 2015 2:39 PM To: Christine Di Bella; Brad Westbrook Subject: LYRASIS Offering classes on metadata, digital curation, and disaster planning This May and June, LYRASIS is offering online classes including "Digital Stewardship Fundamentals," "Introduction to Outsourcing for Digitization," and "Using MODS to Describe Cultural Heritage Resources." To register or to see the full LYRASIS class schedule go to https://www.lyrasis.org/Pages/Events.aspx Follow the links for more information on each class. Advanced Preservation Metadata: How to Make it Happen 4/29 & 30/2015 2:00 PM - 4:00 PM EST http://www.lyrasis.org/Pages/EventDetail.aspx?Eid=0B46B248-2AB2-E411-88A4-002219586F0D Digital Stewardship Fundamentals 5/6/2015 11:00 AM - 1:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=2C77A807-EDA0-E411-88A4-002219586F0D Introduction to Outsourcing for Digitization: Who, What, When, Where, Why and How 5/7/2015 2:00 PM - 4:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=8F575E49-8EA1-E411-88A4-002219586F0D Developing a Disaster Plan 5/7, 14, 28/ 2015 2:00PM - 4:00PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=CFFE5ABE-8F9A-E411-88A4-002219586F0D Grant Writing for Digitization and Preservation Projects 5/11 & 12/2015 2:00 PM - 4:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=A4A8DCA8-0F9C-E411-88A4-002219586F0D Caring for Originals during Scanning Projects 5/13/2015 10:00 AM - 12:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=635CF982-8F9A-E411-88A4-002219586F0D Metadata for Digitization and Preservation 5/20 & 21/2015 10:00 AM - 12:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=FB33C1D0-2AB2-E411-88A4-002219586F0D Starting Right: Introduction to Digital Project Management Planning 5/21 & 22/2015 3:00 PM - 5:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=F40712D7-EBA0-E411-88A4-002219586F0D All History is Local: Find Preserve, and Digitize Collections that Tell the Story 5/27/2015 2:00PM - 4:00PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=AA5EB225-109C-E411-88A4-002219586F0D Managing Oversized Materials: Care, Handling, and Preservation of Posters, Maps, and Other Large Pages in Our Collections 5/28/2015 10:00AM - 12:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=B3D3E456-969A-E411-88A4-002219586F0D Promotion and Outreach for Preservation 6/2/2015 4:00PM - 6:00PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=30D0C8C0-909A-E411-88A4-002219586F0D Project Management and Workflow for Digitization Projects 6/4/2015 11:00 AM - 1:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=EABDD770-ECA0-E411-88A4-002219586F0D Going Digital Free Webinar 6/8/2015 12:00 PM - 1:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=346E6696-ECA0-E411-88A4-002219586F0D Security in and with Collections in Libraries, Archives, and Museum 6/9/2015 2:00PM - 4:00PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=47CDB5CD-F4B6-E411-88A4-002219586F0D Oral Histories: Care and Preservation from the Start 6/10/2015 2:00PM - 4:00PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=5C6FEADC-969A-E411-88A4-002219586F0D Digital Curation Workflow and Tools 6/10/2015 3:00 PM - 5:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=5F43D5DE-E3DE-E411-88A4-002219586F0D Audiovisual Preservation 6/11/2015 2:00PM - 4:00PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=71827524-929A-E411-88A4-002219586F0D Picture This: Introduction to Digital Imaging 6/23 & 24/2015 11:00AM - 1:00PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=8F3075C3-CCDE-E411-88A4-002219586F0D Using MODS to Describe Cultural Heritage Resources 6/24/2015 10:00 AM - 12:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=797EEADE-86E7-E411-88A4-002219586F0D Introduction to Audio Visual Digitization 6/25/2015 11:00 AM - 1:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=B5237264-CDDE-E411-88A4-002219586F0D Introduction to Dublin Core Metadata 6/29/2015 3:00 PM - 5:00 PM EST https://www.lyrasis.org/Pages/EventDetail.aspx?Eid=189AAE8A-CDDE-E411-88A4-002219586F0D To register or to see the full LYRASIS class schedule go to https://www.lyrasis.org/Pages/Events.aspx Alix Bentrud Preservation Services Librarian alix.bentrud at lyrasis.org 800.999.8558 x 4875 Main 404.387.4853 Cell alix.bentrud Skype [cid:image001.png at 01CE5568.2AF76860] Check lyrasisnow.org for news and feature articles. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10337 bytes Desc: image001.png URL: From Chris.Fitzpatrick at lyrasis.org Wed Apr 29 04:31:33 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Wed, 29 Apr 2015 08:31:33 +0000 Subject: [Archivesspace_Users_Group] API Querying of Names In-Reply-To: References: Message-ID: <1430296293575.56541@lyrasis.org> Hi Alex, There's a few ways you could do this, but it also probably has to do with your data. The problem is that records added to the database need to be indexed in Solr, so when you're batch loading a lot of records the indexer will lag. I might suggest loading your agents in first, which would allow for the index to finish. Another option would be to reduce the period the indexer runs ( the default is 30 seconds ) , as well as the number of threads it's using in the config.rb. However, this would require you to have more processors and memory available, so if you do this, you'll need to run it on a multi-processor machine and increase the java heap space. If you're having issues with the search api, you can also just access Solr's search API directly, which would give you a lot of options for term searching. Lastly, you could also write controller and include it as a plugin to search the database directly, by passing the need for the solr index to be populated. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Alexander Duryee Sent: Monday, April 27, 2015 11:24 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] API Querying of Names We're developing a migration tool to import records from our database into ArchivesSpace via the API. For each controlled access name in each collection, our tool needs to know if a name record exists in ArchivesSpace, and if so, query its ID in order to build the collection-name link. However, the only method that I've found to discover agent/family/corp records (knowing only the type and title string) via the API is GET /search/. Using GET /search/ for discovering name records is proving unwieldy, as there is a long delay (~30 seconds on localhost) between POSTing a new name record and having it return in the index. When generating many records at once, this leads to frequent false negatives. It also makes for slow discovery, as a full search query has to be run, then some number of the results iterated through, for every name. Is there a more direct way to query ArchivesSpace for name records, ideally bypassing search altogether? If not, how are other API users developing methods to match name records to ArchivesSpace objects? Many thanks, --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From schelby.1 at osu.edu Wed Apr 29 08:50:38 2015 From: schelby.1 at osu.edu (Schelby, Russell) Date: Wed, 29 Apr 2015 12:50:38 +0000 Subject: [Archivesspace_Users_Group] API Querying of Names In-Reply-To: <1430296293575.56541@lyrasis.org> References: , <1430296293575.56541@lyrasis.org> Message-ID: <1FFC028E0D679147BD07ECFBE1D5C4570DE060@CIO-TNC-D2MBX04.osuad.osu.edu> Not sure if you keep up on this list, so here is the response, some good ideas if not workarounds :-) ________________________________ Russell Schelby Project Manager, Business Analyst Applications, Development & Support, OSU Libraries Schelby.1 at osu.edu, 614.292.0961 ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Chris Fitzpatrick [Chris.Fitzpatrick at lyrasis.org] Sent: Wednesday, April 29, 2015 4:31 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: Re: [Archivesspace_Users_Group] API Querying of Names Hi Alex, There's a few ways you could do this, but it also probably has to do with your data. The problem is that records added to the database need to be indexed in Solr, so when you're batch loading a lot of records the indexer will lag. I might suggest loading your agents in first, which would allow for the index to finish. Another option would be to reduce the period the indexer runs ( the default is 30 seconds ) , as well as the number of threads it's using in the config.rb. However, this would require you to have more processors and memory available, so if you do this, you'll need to run it on a multi-processor machine and increase the java heap space. If you're having issues with the search api, you can also just access Solr's search API directly, which would give you a lot of options for term searching. Lastly, you could also write controller and include it as a plugin to search the database directly, by passing the need for the solr index to be populated. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Alexander Duryee Sent: Monday, April 27, 2015 11:24 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] API Querying of Names We're developing a migration tool to import records from our database into ArchivesSpace via the API. For each controlled access name in each collection, our tool needs to know if a name record exists in ArchivesSpace, and if so, query its ID in order to build the collection-name link. However, the only method that I've found to discover agent/family/corp records (knowing only the type and title string) via the API is GET /search/. Using GET /search/ for discovering name records is proving unwieldy, as there is a long delay (~30 seconds on localhost) between POSTing a new name record and having it return in the index. When generating many records at once, this leads to frequent false negatives. It also makes for slow discovery, as a full search query has to be run, then some number of the results iterated through, for every name. Is there a more direct way to query ArchivesSpace for name records, ideally bypassing search altogether? If not, how are other API users developing methods to match name records to ArchivesSpace objects? Many thanks, --Alex -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From vaddoniz at jhu.edu Wed Apr 29 11:35:21 2015 From: vaddoniz at jhu.edu (Valerie Addonizio) Date: Wed, 29 Apr 2015 15:35:21 +0000 Subject: [Archivesspace_Users_Group] Import accessions only? Message-ID: <7eacb1ea46d0469ca008294243df05b6@ESGMTWEX12.win.ad.jhu.edu> This is a very basic newbie question: I want to confirm whether it is possible to import only accessions with the AT to AS migrator? And if not, confirm that the only way to isolate the accessions would be to export them from AT as CSV, and then import into AS? Thanks! -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ns96 at nyu.edu Wed Apr 29 11:39:55 2015 From: ns96 at nyu.edu (Nathan Stevens) Date: Wed, 29 Apr 2015 11:39:55 -0400 Subject: [Archivesspace_Users_Group] Import accessions only? In-Reply-To: <7eacb1ea46d0469ca008294243df05b6@ESGMTWEX12.win.ad.jhu.edu> References: <7eacb1ea46d0469ca008294243df05b6@ESGMTWEX12.win.ad.jhu.edu> Message-ID: Hi, you are correct. It not possible to just import Accessions with the AT to AS migration tool. On Wed, Apr 29, 2015 at 11:35 AM, Valerie Addonizio wrote: > This is a very basic newbie question: > > > > I want to confirm whether it is possible to import only accessions with > the AT to AS migrator? > > > > And if not, confirm that the only way to isolate the accessions would be > to export them from AT as CSV, and then import into AS? > > > > Thanks! > > > > -Valerie > > > > > > -------------------------------- > > Valerie Addonizio > > Archivist > > The Sheridan Libraries > > Johns Hopkins University > > vaddoniz at jhu.edu > > 410-516-5261 > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- 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 vaddoniz at jhu.edu Wed Apr 29 11:50:23 2015 From: vaddoniz at jhu.edu (Valerie Addonizio) Date: Wed, 29 Apr 2015 15:50:23 +0000 Subject: [Archivesspace_Users_Group] Import accessions only? In-Reply-To: References: <7eacb1ea46d0469ca008294243df05b6@ESGMTWEX12.win.ad.jhu.edu> Message-ID: <0b99a8b29cc24305bfccc78c6af799b8@ESGMTWEX12.win.ad.jhu.edu> Nathan, Thank you. Is my second assumption also correct? -Valerie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Nathan Stevens Sent: Wednesday, April 29, 2015 11:40 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import accessions only? Hi, you are correct. It not possible to just import Accessions with the AT to AS migration tool. On Wed, Apr 29, 2015 at 11:35 AM, Valerie Addonizio > wrote: This is a very basic newbie question: I want to confirm whether it is possible to import only accessions with the AT to AS migrator? And if not, confirm that the only way to isolate the accessions would be to export them from AT as CSV, and then import into AS? Thanks! -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- 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 Wed Apr 29 11:59:04 2015 From: bmg17 at psu.edu (Ben Goldman) Date: Wed, 29 Apr 2015 11:59:04 -0400 (EDT) Subject: [Archivesspace_Users_Group] Import accessions only? In-Reply-To: <0b99a8b29cc24305bfccc78c6af799b8@ESGMTWEX12.win.ad.jhu.edu> References: <7eacb1ea46d0469ca008294243df05b6@ESGMTWEX12.win.ad.jhu.edu> <0b99a8b29cc24305bfccc78c6af799b8@ESGMTWEX12.win.ad.jhu.edu> Message-ID: <309293263.456875.1430323144943.JavaMail.zimbra@psu.edu> Nathan and Valerie, Just a quick note to clarify (in case it helps). It's possible to exclude certain records from migrating with some adjustments to the migration script, correct? At Penn State we filtered some 200,000 archival object level notes from migration (for complicated reasons), but I am not certain if the same strategy might be applied to filter out all non-accession records. -Ben ----- Original Message ----- From: "Valerie Addonizio" To: "Archivesspace Users Group" Sent: Wednesday, April 29, 2015 11:50:23 AM Subject: Re: [Archivesspace_Users_Group] Import accessions only? Nathan, Thank you. Is my second assumption also correct? -Valerie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Nathan Stevens Sent: Wednesday, April 29, 2015 11:40 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import accessions only? Hi, you are correct. It not possible to just import Accessions with the AT to AS migration tool. On Wed, Apr 29, 2015 at 11:35 AM, Valerie Addonizio < vaddoniz at jhu.edu > wrote: This is a very basic newbie question: I want to confirm whether it is possible to import only accessions with the AT to AS migrator? And if not, confirm that the only way to isolate the accessions would be to export them from AT as CSV, and then import into AS? Thanks! -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nathan Stevens Programmer/Analyst Digital Library Technology Services New York University 1212-998-2653 ns96 at nyu.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -------------- next part -------------- An HTML attachment was scrubbed... URL: From maureen.callahan at yale.edu Wed Apr 29 11:59:55 2015 From: maureen.callahan at yale.edu (Callahan, Maureen) Date: Wed, 29 Apr 2015 15:59:55 +0000 Subject: [Archivesspace_Users_Group] Import accessions only? In-Reply-To: <0b99a8b29cc24305bfccc78c6af799b8@ESGMTWEX12.win.ad.jhu.edu> References: <7eacb1ea46d0469ca008294243df05b6@ESGMTWEX12.win.ad.jhu.edu> <0b99a8b29cc24305bfccc78c6af799b8@ESGMTWEX12.win.ad.jhu.edu> Message-ID: <4F276297-055E-4BF9-93D2-B2BFFAEB8666@yale.edu> You could also clone your AT database, delete everything else from the database except accession records, and then just migrate those. You could also migrate everything to AS and use the API to batch delete everything you don?t want. Maureen On Apr 29, 2015, at 11:50 AM, Valerie Addonizio > wrote: Nathan, Thank you. Is my second assumption also correct? -Valerie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Nathan Stevens Sent: Wednesday, April 29, 2015 11:40 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import accessions only? Hi, you are correct. It not possible to just import Accessions with the AT to AS migration tool. On Wed, Apr 29, 2015 at 11:35 AM, Valerie Addonizio > wrote: This is a very basic newbie question: I want to confirm whether it is possible to import only accessions with the AT to AS migrator? And if not, confirm that the only way to isolate the accessions would be to export them from AT as CSV, and then import into AS? Thanks! -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nathan Stevens Programmer/Analyst Digital Library Technology Services New York University 1212-998-2653 ns96 at nyu.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=18hoCacgQPRkGWmD7Rp1vha5NbrBDgRYlx0DytyR-nk&s=zmtnF80nx5UJsQsKsQETqTeNYHtRjdVTVxLoum3WZZo&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Wed Apr 29 12:03:35 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Wed, 29 Apr 2015 12:03:35 -0400 Subject: [Archivesspace_Users_Group] Import accessions only? In-Reply-To: <4F276297-055E-4BF9-93D2-B2BFFAEB8666@yale.edu> References: <7eacb1ea46d0469ca008294243df05b6@ESGMTWEX12.win.ad.jhu.edu> <0b99a8b29cc24305bfccc78c6af799b8@ESGMTWEX12.win.ad.jhu.edu> <4F276297-055E-4BF9-93D2-B2BFFAEB8666@yale.edu> Message-ID: The batch delete is a good option, although you then might have to clear out a whole bunch of agents and subjects, so the clone of AT might be a cleaner option in the long run. On Wed, Apr 29, 2015 at 11:59 AM, Callahan, Maureen < maureen.callahan at yale.edu> wrote: > You could also clone your AT database, delete everything else from the > database except accession records, and then just migrate those. You could > also migrate everything to AS and use the API to batch delete everything > you don?t want. > > Maureen > > > On Apr 29, 2015, at 11:50 AM, Valerie Addonizio wrote: > > Nathan, > > Thank you. Is my second assumption also correct? > > -Valerie > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] *On Behalf Of *Nathan > Stevens > *Sent:* Wednesday, April 29, 2015 11:40 AM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Import accessions only? > > Hi, you are correct. It not possible to just import Accessions with the > AT to AS migration tool. > > On Wed, Apr 29, 2015 at 11:35 AM, Valerie Addonizio > wrote: > This is a very basic newbie question: > > I want to confirm whether it is possible to import only accessions with > the AT to AS migrator? > > And if not, confirm that the only way to isolate the accessions would be > to export them from AT as CSV, and then import into AS? > > Thanks! > > -Valerie > > > -------------------------------- > Valerie Addonizio > Archivist > The Sheridan Libraries > Johns Hopkins University > vaddoniz at jhu.edu > 410-516-5261 > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > -- > Nathan Stevens > Programmer/Analyst > Digital Library Technology Services > New York University > > 1212-998-2653 > ns96 at nyu.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=18hoCacgQPRkGWmD7Rp1vha5NbrBDgRYlx0DytyR-nk&s=zmtnF80nx5UJsQsKsQETqTeNYHtRjdVTVxLoum3WZZo&e= > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From vaddoniz at jhu.edu Wed Apr 29 12:42:55 2015 From: vaddoniz at jhu.edu (Valerie Addonizio) Date: Wed, 29 Apr 2015 16:42:55 +0000 Subject: [Archivesspace_Users_Group] Import accessions only? In-Reply-To: References: <7eacb1ea46d0469ca008294243df05b6@ESGMTWEX12.win.ad.jhu.edu> <0b99a8b29cc24305bfccc78c6af799b8@ESGMTWEX12.win.ad.jhu.edu> <4F276297-055E-4BF9-93D2-B2BFFAEB8666@yale.edu> Message-ID: Thank you, I hadn?t thought of those two options. I like the AT clone idea?. -Valerie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maura Carbone Sent: Wednesday, April 29, 2015 12:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import accessions only? The batch delete is a good option, although you then might have to clear out a whole bunch of agents and subjects, so the clone of AT might be a cleaner option in the long run. On Wed, Apr 29, 2015 at 11:59 AM, Callahan, Maureen > wrote: You could also clone your AT database, delete everything else from the database except accession records, and then just migrate those. You could also migrate everything to AS and use the API to batch delete everything you don?t want. Maureen On Apr 29, 2015, at 11:50 AM, Valerie Addonizio > wrote: Nathan, Thank you. Is my second assumption also correct? -Valerie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Nathan Stevens Sent: Wednesday, April 29, 2015 11:40 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import accessions only? Hi, you are correct. It not possible to just import Accessions with the AT to AS migration tool. On Wed, Apr 29, 2015 at 11:35 AM, Valerie Addonizio > wrote: This is a very basic newbie question: I want to confirm whether it is possible to import only accessions with the AT to AS migrator? And if not, confirm that the only way to isolate the accessions would be to export them from AT as CSV, and then import into AS? Thanks! -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nathan Stevens Programmer/Analyst Digital Library Technology Services New York University 1212-998-2653 ns96 at nyu.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=18hoCacgQPRkGWmD7Rp1vha5NbrBDgRYlx0DytyR-nk&s=zmtnF80nx5UJsQsKsQETqTeNYHtRjdVTVxLoum3WZZo&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From ns96 at nyu.edu Wed Apr 29 12:43:44 2015 From: ns96 at nyu.edu (Nathan Stevens) Date: Wed, 29 Apr 2015 12:43:44 -0400 Subject: [Archivesspace_Users_Group] Import accessions only? In-Reply-To: <0b99a8b29cc24305bfccc78c6af799b8@ESGMTWEX12.win.ad.jhu.edu> References: <7eacb1ea46d0469ca008294243df05b6@ESGMTWEX12.win.ad.jhu.edu> <0b99a8b29cc24305bfccc78c6af799b8@ESGMTWEX12.win.ad.jhu.edu> Message-ID: Yes that correct On Wed, Apr 29, 2015 at 11:50 AM, Valerie Addonizio wrote: > Nathan, > > > > Thank you. Is my second assumption also correct? > > > > -Valerie > > > > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto: > archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Nathan > Stevens > *Sent:* Wednesday, April 29, 2015 11:40 AM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] Import accessions only? > > > > Hi, you are correct. It not possible to just import Accessions with the AT > to AS migration tool. > > > > On Wed, Apr 29, 2015 at 11:35 AM, Valerie Addonizio > wrote: > > This is a very basic newbie question: > > > > I want to confirm whether it is possible to import only accessions with > the AT to AS migrator? > > > > And if not, confirm that the only way to isolate the accessions would be > to export them from AT as CSV, and then import into AS? > > > > Thanks! > > > > -Valerie > > > > > > -------------------------------- > > Valerie Addonizio > > Archivist > > The Sheridan Libraries > > Johns Hopkins University > > vaddoniz at jhu.edu > > 410-516-5261 > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > > > > -- > > Nathan Stevens > Programmer/Analyst > Digital Library Technology Services > New York University > > 1212-998-2653 > ns96 at nyu.edu > > _______________________________________________ > 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 mlevy at ushmm.org Wed Apr 29 12:51:51 2015 From: mlevy at ushmm.org (Levy, Michael) Date: Wed, 29 Apr 2015 12:51:51 -0400 Subject: [Archivesspace_Users_Group] Database migration from 1.0.9 to 1.2.0 produces NoMethodError: undefined method `to_sequel_blob' for # In-Reply-To: References: <4080B059-CCA9-4D05-BEDD-D064C23288EE@gmail.com> <28D3226C-2186-48CA-AE97-14D9D3581082@gmail.com> Message-ID: Please ignore my posting here. I have retried this same operation and it works fine. This time I shut down the old ArchivesSpace instance (1.0.9) prior to copying the /data/ directory. This time I made sure to stop the 1.0.9 instance before copying the /data/ direcdtory. On Mon, Apr 27, 2015 at 4:52 PM, Levy, Michael wrote: > Working on the same situation as previously with some sample data entered > in a 1.0.9 version which I'm trying to upgrade. I ran git clone today, got > the current head version, built the zip file in a development environment, > put the zip file where I wanted it, unzipped it, copied the data directory > from the 1.0.9 version replacing the data directory from the zipped > version, and modified config.rb just to have it run on a set of 5 unused > ports (the older version on 1.0.9 is using the default ports). > > Starting, I got a number of errors that seem to relate to attempts to run > migrations. Any tips? Should I use one of the tagged versions instead of > head? I'd be happy to share the entire log file but I think the first part > of the log is showing that it is having trouble running a database > migration. I have not tried to set resequence_on_startup (which doesn't > seem to relate to startup errors). Thanks for any help. > > Loading ArchivesSpace configuration file from path: > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/config/config.rb > Loading ArchivesSpace configuration file from path: > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/config/config.rb > 2015-04-27 15:24:39.585:INFO:oejs.Server:jetty-8.1.5.v20120716 > 2015-04-27 15:24:40.059:INFO:/:INFO: jruby 1.7.18 (1.9.3p551) 2014-12-22 > 625381c on Java HotSpot(TM) 64-Bit Server VM 1.6.0_26-b03 +jit [linux-amd64] > 2015-04-27 15:24:40.061:INFO:/:INFO: using a shared (threadsafe!) runtime > Loading ArchivesSpace configuration file from path: > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/config/config.rb > Running database migrations for demo database > 2015-04-27 15:25:00.901:INFO:/:An exception happened during JRuby-Rack > startup|Java::JavaSql::SQLException: Failed to start database > '/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/archivesspace_demo_db' > with class loader org.jruby.util.JRubyClassLoader at 1f72e08e, see the next > exception for details.|--- System|jruby 1.7.18 (1.9.3p551) 2014-12-22 > 625381c on Java HotSpot(TM) 64-Bit Server VM 1.6.0_26-b03 +jit > [linux-amd64]|Time: 2015-04-27 15:25:00 -0400|Server: > jetty/8.1.5.v20120716|jruby.home: > file:/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home||--- > Context Init Parameters:|jruby.compat.version = 1.9|jruby.max.runtimes = > 1|jruby.min.runtimes = 1|public.root = /|rack.env = production||--- > Backtrace|Sequel::DatabaseConnectionError: Java::JavaSql::SQLException: > Failed to start database > '/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/archivesspace_demo_db' > with class loader org.jruby.util.JRubyClassLoader at 1f72e08e, see the next > exception for details.| make_new at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool.rb:110| > make_new at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:160| > available at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:137| > acquire at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:127| > sync at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:201| > synchronize at org/jruby/ext/thread/Mutex.java:149| > sync at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:201| > acquire at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:126| > hold at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:88| > synchronize at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255| > execute at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244| > execute_ddl at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:270| > create_table_from_generator at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/schema_methods.rb:641| > create_table at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/schema_methods.rb:195| > create_table? at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/schema_methods.rb:223| > schema_dataset at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:584| > initialize at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:444| > initialize at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:506| > run at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:391| > setup_database at > file:/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/lib/common.jar!/db/db_migrator.rb:184| > prepare_database at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap.rb:64| > connect at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:69| > connect at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/core.rb:95| > prepare_database at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap.rb:62| > init at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap.rb:40| > (root) at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/main.rb:10| > require at org/jruby/RubyKernel.java:1071| > require at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:55| > require at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:53| > (root) at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/config.ru:1| > instance_eval at org/jruby/RubyBasicObject.java:1533| > (root) at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/config.ru:4| > initialize at > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-rack-1.1.18/lib/jruby-rack-1.1.18.jar!/vendor/rack-1.5.2/rack/builder.rb:55| > start_server at launcher/launcher.rb:86| > main at launcher/launcher.rb:147| (root) at > launcher/launcher.rb:230||--- RubyGems|Gem.dir: > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems|Gem.path:|/home/www/.gem/jruby/1.9|file:/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/gems/shared|/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems|Activated > gems:| json-1.8.0-java| bundler-1.7.12| rake-10.4.2| i18n-0.7.0| > multi_json-1.11.0| activesupport-3.2.19| atomic-1.0.1-java| > htmlentities-4.3.3| nokogiri-1.6.6.2-java| rubyzip-1.0.0| axlsx-2.0.1| > backports-3.6.4| bcrypt-3.1.7-java| diff-lcs-1.1.3| > eventmachine-1.0.7-java| factory_girl-4.1.0| jdbc-derby-10.6.2.1-java| > jdbc-mysql-5.1.13| jruby-jars-1.7.18| jruby-rack-1.1.18| > json-schema-1.0.10| ladle-0.2.0-java| multipart-post-1.2.0| > net-http-persistent-2.8| net-ldap-0.6.1| rack-1.4.5| puma-2.8.2-java| > rack-protection-1.5.3| sequel-4.20.0| rack-session-sequel-0.0.1| > rack-test-0.6.3| rjack-jackson-1.8.11.0-java| rspec-core-2.12.1| > rspec-expectations-2.12.1| rspec-mocks-2.12.2| rspec-2.12.0| > rufus-lru-1.0.5| tzinfo-0.3.39| rufus-scheduler-2.0.24| > saxerator-0.9.5| saxon-xslt-0.5.1-java| simplecov-html-0.7.1| > simplecov-0.7.1| tilt-1.4.1| sinatra-1.3.6| sinatra-contrib-1.3.2| > sinatra-reloader-1.0| warbler-1.4.2| zip-zip-0.3||--- > Bundler|Bundler.bundle_path: > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems|Bundler.root: > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF|Gemfile: > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/Gemfile|Settings:| > bin_path = > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/bundler-1.7.12/bin/bundle| > gemfile = > /data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/Gemfile||--- > JRuby-Rack Config|compat_version = RUBY1_9|default_logger = > org.jruby.rack.logging.StandardOutLogger at 6724e231|equals = |err > = java.io.PrintStream at 15335332|filter_adds_html = > true|filter_verifies_resource = false|ignore_environment = > false|initial_memory_buffer_size = |initial_runtimes = > 1|jms_connection_factory = |jms_jndi_properties = |logger = > org.jruby.rack.logging.ServletContextLogger at 3d2a07c9|logger_class_name = > servlet_context|logger_name = jruby.rack|maximum_memory_buffer_size = > |maximum_runtimes = 1|num_initializer_threads = |out = > java.io.PrintStream at 34c1efe7|rackup = |rackup_path = |rewindable = > true|runtime_arguments = |runtime_environment = |runtime_timeout_seconds = > |serial_initialization = false|servlet_context = > ServletContext at o.e.j.w.WebAppContext{/,file:/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/},/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/wars/backend.war|throw_init_exception > = false| > 2015-04-27 15:25:00.905:WARN:/:ERROR: initialization failed > org.jruby.rack.RackInitializationException: Java::JavaSql::SQLException: > Failed to start database > '/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/archivesspace_demo_db' > with class loader org.jruby.util.JRubyClassLoader at 1f72e08e, see the next > exception for details.|?from > java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:597)|?from > RUBY.connect(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:219)|?from > RUBY.make_new(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool.rb:101)|?from > RUBY.make_new(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:160)|?from > RUBY.available(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:137)|?from > RUBY.acquire(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:127)|?from > RUBY.sync(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:201)|?from > org.jruby.ext.thread.Mutex.synchronize(org/jruby/ext/thread/Mutex.java:149)|?from > RUBY.sync(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:201)|?from > RUBY.acquire(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:126)|?from > RUBY.hold(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:88)|?from > RUBY.synchronize(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255)|?from > RUBY.execute(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:244)|?from > RUBY.execute_ddl(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/adapters/jdbc.rb:270)|?from > RUBY.create_table_from_generator(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/schema_methods.rb:641)|?from > RUBY.create_table(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/schema_methods.rb:195)|?from > RUBY.create_table?(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/schema_methods.rb:223)|?from > RUBY.schema_dataset(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:584)|?from > RUBY.initialize(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:444)|?from > RUBY.initialize(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:506)|?from > RUBY.run(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:391)|?from > RUBY.setup_database(file:/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/lib/common.jar!/db/db_migrator.rb:184)|?from > RUBY.prepare_database(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap.rb:64)|?from > RUBY.connect(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:69)|?from > RUBY.connect(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/sequel-4.20.0/lib/sequel/core.rb:95)|?from > RUBY.prepare_database(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap.rb:62)|?from > RUBY.init(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap.rb:40)|?from > RUBY.(root)(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/app/main.rb:10)|?from > org.jruby.RubyKernel.require(org/jruby/RubyKernel.java:1071)|?from > Kernel.require(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:55)|?from > Kernel.require(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:55)|?from > Kernel.require(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:53)|?from > Kernel.require(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-jars-1.7.18/lib/jruby-stdlib-1.7.18.jar!/META-INF/jruby.home/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:53)|?from > RUBY.(root)(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/config.ru:1)|?from > org.jruby.RubyBasicObject.instance_eval(org/jruby/RubyBasicObject.java:1533)|?from > RUBY.(root)(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/tmp/jetty-0.0.0.0-8289-backend.war-_-any-/webapp/WEB-INF/config.ru:4)|?from > RUBY.initialize(/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/gems/gems/jruby-rack-1.1.18/lib/jruby-rack-1.1.18.jar!/vendor/rack-1.5.2/rack/builder.rb:55)|?from > org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(org/eclipse/jetty/server/handler/ContextHandler.java:766)|?from > org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(org/eclipse/jetty/servlet/ServletContextHandler.java:406)|?from > org.eclipse.jetty.server.handler.ContextHandler.startContext(org/eclipse/jetty/server/handler/ContextHandler.java:758)|?from > org.eclipse.jetty.servlet.ServletContextHandler.startContext(org/eclipse/jetty/servlet/ServletContextHandler.java:242)|?from > org.eclipse.jetty.webapp.WebAppContext.startContext(org/eclipse/jetty/webapp/WebAppContext.java:1233)|?from > org.eclipse.jetty.server.handler.ContextHandler.doStart(org/eclipse/jetty/server/handler/ContextHandler.java:701)|?from > org.eclipse.jetty.webapp.WebAppContext.doStart(org/eclipse/jetty/webapp/WebAppContext.java:475)|?from > org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)|?from > org.eclipse.jetty.server.handler.HandlerCollection.doStart(org/eclipse/jetty/server/handler/HandlerCollection.java:224)|?from > org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(org/eclipse/jetty/server/handler/ContextHandlerCollection.java:167)|?from > org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)|?from > org.eclipse.jetty.server.handler.HandlerWrapper.doStart(org/eclipse/jetty/server/handler/HandlerWrapper.java:90)|?from > org.eclipse.jetty.server.Server.doStart(org/eclipse/jetty/server/Server.java:272)|?from > org.eclipse.jetty.util.component.AbstractLifeCycle.start(org/eclipse/jetty/util/component/AbstractLifeCycle.java:59)|?from > java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:597)|?from > launcher.launcher.start_server(launcher/launcher.rb:86)|?from > launcher.launcher.start_server(launcher/launcher/launcher.rb:86)|?from > launcher.launcher.main(launcher/launcher.rb:147)|?from > launcher.launcher.main(launcher/launcher/launcher.rb:147)|?from > launcher.launcher.(root)(launcher/launcher.rb:230)|?from > launcher.launcher.(root)(launcher/launcher/launcher.rb:230)| > at > org.jruby.rack.RackInitializationException.wrap(RackInitializationException.java:29) > at > org.jruby.rack.RackApplicationFactoryDecorator.init(RackApplicationFactoryDecorator.java:104) > at > org.jruby.rack.RackServletContextListener.contextInitialized(RackServletContextListener.java:50) > at > org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:766) > at > org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406) > at > org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:758) > at > org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:242) > at > org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1233) > at > org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:701) > at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) > at > org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) > at > org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:90) > at org.eclipse.jetty.server.Server.doStart(Server.java:272) > at > org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(JavaMethod.java:440) > at org.jruby.javasupport.JavaMethod.invokeDirect(JavaMethod.java:304) > at > org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:52) > at > org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:306) > at > org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:136) > at launcher.launcher.method__1$RUBY$start_server(launcher/launcher.rb:86) > at > launcher$launcher$method__1$RUBY$start_server.call(launcher$launcher$method__1$RUBY$start_server) > at > org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:218) > at > org.jruby.internal.runtime.methods.CompiledMethod.call(CompiledMethod.java:268) > at > org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:346) > at > org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:204) > at > launcher.launcher.chained_4_rescue_1$RUBY$SYNTHETICmain(launcher/launcher.rb:147) > at launcher.launcher.method__3$RUBY$main(launcher/launcher.rb:145) > at > launcher$launcher$method__3$RUBY$main.call(launcher$launcher$method__3$RUBY$main) > at > launcher$launcher$method__3$RUBY$main.call(launcher$launcher$method__3$RUBY$main) > at > org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:306) > at > org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:136) > at launcher.launcher.__file__(launcher/launcher.rb:230) > at launcher.launcher.load(launcher/launcher.rb) > at org.jruby.Ruby.runScript(Ruby.java:866) > at org.jruby.Ruby.runScript(Ruby.java:859) > at org.jruby.Ruby.runNormally(Ruby.java:728) > at org.jruby.Ruby.runFromMain(Ruby.java:577) > at org.jruby.Main.doRunFromMain(Main.java:395) > at org.jruby.Main.internalRun(Main.java:290) > at org.jruby.Main.run(Main.java:217) > at org.jruby.Main.main(Main.java:197) > Caused by: > org.jruby.exceptions.RaiseException: (DatabaseConnectionError) > Java::JavaSql::SQLException: Failed to start database > '/data/sites/apps/public/archivesspace-20150427-1447/archivesspace/data/archivesspace_demo_db' > with class loader org.jruby.util.JRubyClassLoader at 1f72e08e, see the next > exception for details. > > > On Thu, Apr 2, 2015 at 5:22 PM, Levy, Michael wrote: > >> We'll be happy to wait for a fix. Thanks Brian. >> >> On Thu, Apr 2, 2015 at 5:20 PM, Brian Hoffman >> wrote: >> >>> Hi Michael, >>> >>> I think the best thing would be to wait for us to fix it. We?ll post a >>> minor release next week. Can you wait till then? I?d hate for your data to >>> get corrupted. >>> >>> Brian >>> >>> >>> >>> On Apr 2, 2015, at 5:17 PM, Levy, Michael wrote: >>> >>> Any suggestions on what I ought to try to work around this issue? Should >>> I try running the upgrade incrementally from the 1.0.9 instance I have >>> running to some other interim version(s) and then on to 1.2.0? >>> >>> In my initial posting I did not finish a sentence. I merely meant to say >>> I copied the data folder and configuration, and that I had not added any >>> plugins. >>> >>> On Thu, Apr 2, 2015 at 12:07 PM, Brian Hoffman >>> wrote: >>> >>>> Thank you! >>>> >>>> https://archivesspace.atlassian.net/browse/AR-1188 >>>> >>>> >>>> On Apr 2, 2015, at 12:02 PM, Levy, Michael wrote: >>>> >>>> > Starting with a small test instance with no modifications, under >>>> RHEL, using derby, from a working v1.0.9 instance (which had been stopped), >>>> and then attempting to upgrade to 1.2.0. I just copied the >>>> > >>>> > [www at saturn archivesspace-v1.2.0]$ scripts/setup-database.sh >>>> > Loading ArchivesSpace configuration file from path: >>>> /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb >>>> > Loading ArchivesSpace configuration file from path: >>>> /data/sites/apps/public/archivesspace-v1.2.0/config/config.rb >>>> > Running migrations against >>>> jdbc:derby:/data/sites/apps/public/archivesspace-v1.2.0/data/archivesspace_demo_db;create=true;aspacedemo=true >>>> > Adding separate permissions for updating major record types >>>> > ... accession records >>>> > ... resource records >>>> > ... digital object records >>>> > ... running import jobs >>>> > ... managing vocabulary records >>>> > Updating groups to include the new permssions >>>> > Deleting update_archival_record permission >>>> > Adding 'Date Not Yet Determined' to resource 2/4 >>>> > Adding 'Date Not Yet Determined' to resource 2/23 >>>> > Adding 'Date Not Yet Determined' to resource 2/24 >>>> > >>>> > ............ >>>> > >>>> > Adding 'Date Not Yet Determined' to resource 2/52 >>>> > Adding 'Date Not Yet Determined' to resource 2/53 >>>> > *** ADDING SOME ENUMS >>>> > *** Genre Form to note_index_item_type enum list >>>> > Triggering reindex of resource >>>> > Triggering reindex of archival_object >>>> > Triggering reindex of digital_object >>>> > Making location_temporary list editble >>>> > {:id=>1, :import_type=>"marcxml_lcnaf_subjects_and_agents", >>>> :repo_id=>2, :lock_version=>5, :json_schema_version=>1, >>>> :filenames=>"[\"lcnaf_import_d2adf1d5-64f5-4577-b55a-2e00b3bac1d5\"]", >>>> :time_submitted=>2014-03-26 17:51:23 UTC, :time_started=>2014-03-26 >>>> 17:51:27 UTC, :time_finished=>2014-03-26 17:51:42 UTC, :owner_id=>1, >>>> :status=>"completed", :created_by=>"admin", :last_modified_by=>"admin", >>>> :create_time=>2014-03-26 17:51:23 UTC, :system_mtime=>2014-03-26 17:51:42 >>>> UTC, :user_mtime=>2014-03-26 17:51:23 UTC} >>>> > 1297 >>>> > NoMethodError: undefined method `to_sequel_blob' for >>>> # >>>> > blobify at >>>> /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/utils.rb:33 >>>> > (root) at >>>> /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:44 >>>> > each at org/jruby/RubyArray.java:1613 >>>> > (root) at >>>> /data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/migrations/037_generalized_job_table.rb:37 >>>> > instance_eval at org/jruby/RubyBasicObject.java:1533 >>>> > apply at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:100 >>>> > run at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:528 >>>> > _transaction at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:134 >>>> > transaction at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:108 >>>> > hold at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:98 >>>> > hold at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/connection_pool/threaded.rb:87 >>>> > synchronize at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:255 >>>> > transaction at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/transactions.rb:97 >>>> > checked_transaction at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:464 >>>> > run at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:527 >>>> > each at org/jruby/RubyArray.java:1613 >>>> > run at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:524 >>>> > run at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/extensions/migration.rb:391 >>>> > setup_database at >>>> file:/data/sites/apps/public/archivesspace-v1.2.0/lib/common.jar!/db/db_migrator.rb:184 >>>> > (root) at ../scripts/rb/migrate_db.rb:43 >>>> > connect at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/database/connecting.rb:69 >>>> > connect at >>>> /data/sites/apps/public/archivesspace-v1.2.0/gems/gems/sequel-4.20.0/lib/sequel/core.rb:95 >>>> > (root) at ../scripts/rb/migrate_db.rb:28 >>>> > [www at saturn archivesspace-v1.2.0]$ >>>> > >>>> > _______________________________________________ >>>> > Archivesspace_Users_Group mailing list >>>> > Archivesspace_Users_Group at lyralists.lyrasis.org >>>> > >>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>>> >>>> _______________________________________________ >>>> Archivesspace_Users_Group mailing list >>>> Archivesspace_Users_Group at lyralists.lyrasis.org >>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>>> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >>> >>> _______________________________________________ >>> Archivesspace_Users_Group mailing list >>> Archivesspace_Users_Group at lyralists.lyrasis.org >>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From christine.dibella at lyrasis.org Wed Apr 29 14:02:27 2015 From: christine.dibella at lyrasis.org (Christine Di Bella) Date: Wed, 29 Apr 2015 18:02:27 +0000 Subject: [Archivesspace_Users_Group] FW: EAD ingest default values In-Reply-To: References: Message-ID: Forwarded on behalf of Kate Bowers. From: Bowers, Kate A. [mailto:kate_bowers at harvard.edu] Sent: Wednesday, April 29, 2015 12:57 PM To: archivesspace_users_group-bounces at lyralists.lyrasis.org Subject: EAD ingest default values What are other repositories doing about default values added by ArchivesSpace upon ingest? For example, if I am reading the EAD ingest map accurately, all instances are asserted to be ?mixed_materials? which of course is not right if I?m ingesting EAD describing a photographic collection. And, of course, any collection that is genuinely of mixed materials is frequently made up of components that are a single medium. Is there a way to assign a value of ?unspecified? (or some other value) so that we can distinguish between values that have been purposefully assigned and those that are merely blanket values created by the ingest process? Thanks, Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers -------------- next part -------------- An HTML attachment was scrubbed... URL: From bmg17 at psu.edu Wed Apr 29 14:04:45 2015 From: bmg17 at psu.edu (Ben Goldman) Date: Wed, 29 Apr 2015 14:04:45 -0400 (EDT) Subject: [Archivesspace_Users_Group] Yale container plug-ins In-Reply-To: <1921921560.588047.1430329857737.JavaMail.zimbra@psu.edu> Message-ID: <1791491061.605733.1430330685468.JavaMail.zimbra@psu.edu> Dear Brad and ASpace team: Penn State has been talking to Maureen Callahan and her colleagues at Yale about the work they've been doing to enhance management of location, container, extent and restrictions data in ArchivesSpace through their Container Management Plug-Ins. Maureen recently posted about this work at https://groups.google.com/forum/#!topic/archivesspace/-7HBTipV0Ts, and more information is available at http://guides.library.yale.edu/ASpaceContainerManagement . We recently got to see some of these plug-ins in action, and were really impressed with these features. We understand that Lyrasis/ArchivesSpace is considering making these plug-ins part of the core code of ArchivesSpace, and would like to enthusiastically support this proposal. Also copying the ASpace User Group to help increase awareness of this important work. Best, 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 brad.westbrook at lyrasis.org Wed Apr 29 14:17:50 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Wed, 29 Apr 2015 18:17:50 +0000 Subject: [Archivesspace_Users_Group] Yale container plug-ins In-Reply-To: <1791491061.605733.1430330685468.JavaMail.zimbra@psu.edu> References: <1921921560.588047.1430329857737.JavaMail.zimbra@psu.edu> <1791491061.605733.1430330685468.JavaMail.zimbra@psu.edu> Message-ID: Thanks, Ben. We agree that is this is very important work and work that many in the ArchivesSpace community would like to see implemented. We are now working on a strategy for doing that. Yours, 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 Ben Goldman Sent: Wednesday, April 29, 2015 2:05 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Yale container plug-ins Dear Brad and ASpace team: Penn State has been talking to Maureen Callahan and her colleagues at Yale about the work they've been doing to enhance management of location, container, extent and restrictions data in ArchivesSpace through their Container Management Plug-Ins. Maureen recently posted about this work at https://groups.google.com/forum/#!topic/archivesspace/-7HBTipV0Ts, and more information is available at http://guides.library.yale.edu/ASpaceContainerManagement. We recently got to see some of these plug-ins in action, and were really impressed with these features. We understand that Lyrasis/ArchivesSpace is considering making these plug-ins part of the core code of ArchivesSpace, and would like to enthusiastically support this proposal. Also copying the ASpace User Group to help increase awareness of this important work. Best, 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7625 bytes Desc: image001.png URL: From bmg17 at psu.edu Wed Apr 29 14:24:29 2015 From: bmg17 at psu.edu (Ben Goldman) Date: Wed, 29 Apr 2015 14:24:29 -0400 (EDT) Subject: [Archivesspace_Users_Group] Yale container plug-ins In-Reply-To: References: <1921921560.588047.1430329857737.JavaMail.zimbra@psu.edu> <1791491061.605733.1430330685468.JavaMail.zimbra@psu.edu> Message-ID: <974362845.626546.1430331869100.JavaMail.zimbra@psu.edu> Thanks, Brad! -Ben ----- Original Message ----- From: "Brad Westbrook" To: "Archivesspace Users Group" Sent: Wednesday, April 29, 2015 2:17:50 PM Subject: Re: [Archivesspace_Users_Group] Yale container plug-ins Thanks, Ben. We agree that is this is very important work and work that many in the ArchivesSpace community would like to see implemented. We are now working on a strategy for doing that. Yours, Brad W. 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 Ben Goldman Sent: Wednesday, April 29, 2015 2:05 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] Yale container plug-ins Dear Brad and ASpace team: Penn State has been talking to Maureen Callahan and her colleagues at Yale about the work they've been doing to enhance management of location, container, extent and restrictions data in ArchivesSpace through their Container Management Plug-Ins. Maureen recently posted about this work at https://groups.google.com/forum/#!topic/archivesspace/-7HBTipV0Ts, and more information is available at http://guides.library.yale.edu/ASpaceContainerManagement . We recently got to see some of these plug-ins in action, and were really impressed with these features. We understand that Lyrasis/ArchivesSpace is considering making these plug-ins part of the core code of ArchivesSpace, and would like to enthusiastically support this proposal. Also copying the ASpace User Group to help increase awareness of this important work. Best, 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7625 bytes Desc: image001.png URL: From alexanderduryee at nypl.org Wed Apr 29 14:41:30 2015 From: alexanderduryee at nypl.org (Alexander Duryee) Date: Wed, 29 Apr 2015 14:41:30 -0400 Subject: [Archivesspace_Users_Group] API Querying of Names In-Reply-To: <1430296293575.56541@lyrasis.org> References: <1430296293575.56541@lyrasis.org> Message-ID: Chris, Thanks for your reply. I'd like to bypass Solr as much as possible, so we'll look into developing a controller that takes a string and returns the matching agent object. Thanks again, --Alex On Wed, Apr 29, 2015 at 4:31 AM, Chris Fitzpatrick < Chris.Fitzpatrick at lyrasis.org> wrote: > > Hi Alex, > > > There's a few ways you could do this, but it also probably has to do > with your data. The problem is that records added to the database need to > be indexed in Solr, so when you're batch loading a lot of records the > indexer will lag. > > > I might suggest loading your agents in first, which would allow for the > index to finish. > > Another option would be to reduce the period the indexer runs ( the > default is 30 seconds ) , as well as the number of threads it's using in > the config.rb. However, this would require you to have more processors and > memory available, so if you do this, you'll need to run it on a > multi-processor machine and increase the java heap space. > > > If you're having issues with the search api, you can also just access > Solr's search API directly, which would give you a lot of options for term > searching. > > > Lastly, you could also write controller and include it as a plugin to > search the database directly, by passing the need for the solr index to be > populated. > > > b,chris. > > > > > > Chris Fitzpatrick | Developer, ArchivesSpace > Skype: chrisfitzpat | Phone: 918.236.6048 > http://archivesspace.org/ > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < > archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of > Alexander Duryee > *Sent:* Monday, April 27, 2015 11:24 PM > *To:* archivesspace_users_group at lyralists.lyrasis.org > *Subject:* [Archivesspace_Users_Group] API Querying of Names > > We're developing a migration tool to import records from our database > into ArchivesSpace via the API. For each controlled access name in each > collection, our tool needs to know if a name record exists in > ArchivesSpace, and if so, query its ID in order to build the > collection-name link. However, the only method that I've found to discover > agent/family/corp records (knowing only the type and title string) via the > API is GET /search/. > > Using GET /search/ for discovering name records is proving unwieldy, as > there is a long delay (~30 seconds on localhost) between POSTing a new name > record and having it return in the index. When generating many records at > once, this leads to frequent false negatives. It also makes for slow > discovery, as a full search query has to be run, then some number of the > results iterated through, for every name. > > Is there a more direct way to query ArchivesSpace for name records, > ideally bypassing search altogether? If not, how are other API users > developing methods to match name records to ArchivesSpace objects? > > Many thanks, > --Alex > > -- > Alexander Duryee > Metadata Archivist > New York Public Library > (917)-229-9590 > alexanderduryee at nypl.org > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Alexander Duryee Metadata Archivist New York Public Library (917)-229-9590 alexanderduryee at nypl.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From ns96 at nyu.edu Wed Apr 29 15:00:56 2015 From: ns96 at nyu.edu (Nathan Stevens) Date: Wed, 29 Apr 2015 15:00:56 -0400 Subject: [Archivesspace_Users_Group] API Querying of Names In-Reply-To: References: <1430296293575.56541@lyrasis.org> Message-ID: Hi There is already a feature request ( https://archivesspace.atlassian.net/browse/AR-795) to allow the backend not to throw an error when existing Names and Subjects are already in the database. Just contact the ASpace team to push for this issue to be added to a next release. On Wed, Apr 29, 2015 at 2:41 PM, Alexander Duryee wrote: > Chris, > > Thanks for your reply. I'd like to bypass Solr as much as possible, so > we'll look into developing a controller that takes a string and returns the > matching agent object. > > Thanks again, > --Alex > > On Wed, Apr 29, 2015 at 4:31 AM, Chris Fitzpatrick < > Chris.Fitzpatrick at lyrasis.org> wrote: > >> >> Hi Alex, >> >> >> There's a few ways you could do this, but it also probably has to do >> with your data. The problem is that records added to the database need to >> be indexed in Solr, so when you're batch loading a lot of records the >> indexer will lag. >> >> >> I might suggest loading your agents in first, which would allow for the >> index to finish. >> >> Another option would be to reduce the period the indexer runs ( the >> default is 30 seconds ) , as well as the number of threads it's using in >> the config.rb. However, this would require you to have more processors and >> memory available, so if you do this, you'll need to run it on a >> multi-processor machine and increase the java heap space. >> >> >> If you're having issues with the search api, you can also just access >> Solr's search API directly, which would give you a lot of options for term >> searching. >> >> >> Lastly, you could also write controller and include it as a plugin to >> search the database directly, by passing the need for the solr index to be >> populated. >> >> >> b,chris. >> >> >> >> >> >> Chris Fitzpatrick | Developer, ArchivesSpace >> Skype: chrisfitzpat | Phone: 918.236.6048 >> http://archivesspace.org/ >> ------------------------------ >> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org < >> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of >> Alexander Duryee >> *Sent:* Monday, April 27, 2015 11:24 PM >> *To:* archivesspace_users_group at lyralists.lyrasis.org >> *Subject:* [Archivesspace_Users_Group] API Querying of Names >> >> We're developing a migration tool to import records from our database >> into ArchivesSpace via the API. For each controlled access name in each >> collection, our tool needs to know if a name record exists in >> ArchivesSpace, and if so, query its ID in order to build the >> collection-name link. However, the only method that I've found to discover >> agent/family/corp records (knowing only the type and title string) via the >> API is GET /search/. >> >> Using GET /search/ for discovering name records is proving unwieldy, as >> there is a long delay (~30 seconds on localhost) between POSTing a new name >> record and having it return in the index. When generating many records at >> once, this leads to frequent false negatives. It also makes for slow >> discovery, as a full search query has to be run, then some number of the >> results iterated through, for every name. >> >> Is there a more direct way to query ArchivesSpace for name records, >> ideally bypassing search altogether? If not, how are other API users >> developing methods to match name records to ArchivesSpace objects? >> >> Many thanks, >> --Alex >> >> -- >> Alexander Duryee >> Metadata Archivist >> New York Public Library >> (917)-229-9590 >> alexanderduryee at nypl.org >> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group at lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> >> > > > -- > Alexander Duryee > Metadata Archivist > New York Public Library > (917)-229-9590 > alexanderduryee at nypl.org > > _______________________________________________ > 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 mauraa at brandeis.edu Wed Apr 29 15:04:36 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Wed, 29 Apr 2015 15:04:36 -0400 Subject: [Archivesspace_Users_Group] FW: EAD ingest default values In-Reply-To: References: Message-ID: Hi Kate, I think that might be a default if you don't give a label. I did a test import using this and I get the correct type (graphic materials not mixed): Test Item199912Subtitle

pizza is good

The only thing I did have to do is merge in the controlled value list "graphic materials" and "Graphic Materials" so that the label was not entirely lower case. Hope that helps. -Maura On Wed, Apr 29, 2015 at 2:02 PM, Christine Di Bella < christine.dibella at lyrasis.org> wrote: > Forwarded on behalf of Kate Bowers. > > > > *From:* Bowers, Kate A. [mailto:kate_bowers at harvard.edu] > *Sent:* Wednesday, April 29, 2015 12:57 PM > *To:* archivesspace_users_group-bounces at lyralists.lyrasis.org > *Subject:* EAD ingest default values > > > > What are other repositories doing about default values added by > ArchivesSpace upon ingest? > > > > For example, if I am reading the EAD ingest map accurately, all instances > are asserted to be ?mixed_materials? which of course is not right if I?m > ingesting EAD describing a photographic collection. And, of course, any > collection that is genuinely of mixed materials is frequently made up of > components that are a single medium. > > > > Is there a way to assign a value of ?unspecified? (or some other value) so > that we can distinguish between values that have been purposefully assigned > and those that are merely blanket values created by the ingest process? > > > > Thanks, > > > > Kate > > > > *Kate Bowers* > > Collections Services Archivist for Metadata, Systems, and Standards > > Harvard University Archives > > kate_bowers at harvard.edu > > 617.496.2713 > > voice: (617) 384-7787 > > fax: (617) 495-8011 > > web: http://nrs.harvard.edu/urn-3:hul.eresource:archives > > Twitter: @k8_bowers > > > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Wed Apr 29 18:03:23 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Wed, 29 Apr 2015 22:03:23 +0000 Subject: [Archivesspace_Users_Group] Note Labels in RDE? In-Reply-To: References: Message-ID: Hi, Jackie, I have entered a feature request for what you describe below. Please see https://archivesspace.atlassian.net/browse/AR-1217?jql=. Please add to the request any additional information you think necessary. Yrs, Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jacqueline Morin Sent: Monday, April 27, 2015 2:57 PM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Note Labels in RDE? Not sure if I am just missing something obvious, but when trying to add "notes" such as a General note in RDE, there doesn't seem to be a field for "note label." There's just the "note type" and the "content." In the "slow data entry" mode, adding the note label lets the note be displayed as "General Note." Without the label, the default is the note type and it will just be displayed as "Gneral." Is there a way to get that note label in Rapid Data Entry? Thanks for any help! ---Jackie Morin Jacqueline Morin, M.L.I.S. Processing Archivist, Special Collections Doheny Memorial Library University of Southern California 3550 Trousdale Parkway Los Angeles, CA 90089-0182 Tel: 213-821-0488 Fax: 213-740-6668 -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Wed Apr 29 18:11:03 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Wed, 29 Apr 2015 22:11:03 +0000 Subject: [Archivesspace_Users_Group] Date Label in RDE In-Reply-To: <96B305F061ED68428DDA721BECE2ED155166C306@ITSNT440.iowa.uiowa.edu> References: <213B97E293CEAF4EA0383FF5B29E66ED817D1E83@CTCXMBX10.ap.org> <96B305F061ED68428DDA721BECE2ED155166C306@ITSNT440.iowa.uiowa.edu> Message-ID: Hi, Lindsay and Francesca, I have entered a feature request for a date label in the RDE. The request is logged as https://archivesspace.atlassian.net/browse/AR-1218?jql=. Please add any other details you believe necessary. Thanks, Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Morecraft, Lindsay M Sent: Friday, April 24, 2015 10:52 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Date Label in RDE I asked about this a few weeks ago, and also agree with Francesca that it is very time consuming. It would be very helpful if there was a date label option in Rapid Data Entry. Thanks, Lindsay Moen (Morecraft) Processing Librarian Special Collections and University Archives The University of Iowa 319-335-5921 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Pitaro, Francesca Sent: Friday, April 24, 2015 9:49 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Date Label in RDE Hello, Is there some way to set a default for the date label when using Rapid Data Entry? When I enter archival objects individually, my chosen default ("creation") pops into the field, but when I use the RDE to create the record, the date label field appears as "Other". It's very time consuming to then go back in and change the label for each archival object individually to "creation". Thanks, Francesca [cid:image001.jpg at 01D082A8.03913930] [signature-96] Francesca Pitaro Processing Archivist AP Corporate Archives fpitaro at ap.org www.ap.org 450 W 33rd St New York, NY 10001 T 212.621.7446 The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1898 and delete this email. Thank you. [IP_US_DISC] msk dccc60c6d2c3a6438f0cf467d9a4938 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13756 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 14637 bytes Desc: image002.jpg URL: From kate_bowers at harvard.edu Wed Apr 29 19:11:44 2015 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Wed, 29 Apr 2015 23:11:44 +0000 Subject: [Archivesspace_Users_Group] FW: EAD ingest default values (still looking for accurate EAD to AS data mapping documentation) In-Reply-To: References: , Message-ID: <1430349104154.79827@harvard.edu> Wow! Thanks for that Maura. According to the only map I know of, http://www.archivesspace.org/sites/default/files/EAD-Import-Export-Mapping-20130831.xlsx, in which there is no mention of the label attribute--and that's supposed to mean it doesn't get ingested--I believe, or at least that's what I was told about no mention of attributes for extents in the same document. Yet, according to your experience, it maps to instance type. Can someone point me to move up-to-date or more accurate mapping documentation? Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Maura Carbone Sent: Wednesday, April 29, 2015 3:04:36 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] FW: EAD ingest default values Hi Kate, I think that might be a default if you don't give a label. I did a test import using this and I get the correct type (graphic materials not mixed): Test Item199912Subtitle

pizza is good

The only thing I did have to do is merge in the controlled value list "graphic materials" and "Graphic Materials" so that the label was not entirely lower case. Hope that helps. -Maura On Wed, Apr 29, 2015 at 2:02 PM, Christine Di Bella > wrote: Forwarded on behalf of Kate Bowers. From: Bowers, Kate A. [mailto:kate_bowers at harvard.edu] Sent: Wednesday, April 29, 2015 12:57 PM To: archivesspace_users_group-bounces at lyralists.lyrasis.org Subject: EAD ingest default values What are other repositories doing about default values added by ArchivesSpace upon ingest? For example, if I am reading the EAD ingest map accurately, all instances are asserted to be "mixed_materials" which of course is not right if I'm ingesting EAD describing a photographic collection. And, of course, any collection that is genuinely of mixed materials is frequently made up of components that are a single medium. Is there a way to assign a value of "unspecified" (or some other value) so that we can distinguish between values that have been purposefully assigned and those that are merely blanket values created by the ingest process? Thanks, Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chris.Fitzpatrick at lyrasis.org Thu Apr 30 08:13:53 2015 From: Chris.Fitzpatrick at lyrasis.org (Chris Fitzpatrick) Date: Thu, 30 Apr 2015 12:13:53 +0000 Subject: [Archivesspace_Users_Group] FW: EAD ingest default values (still looking for accurate EAD to AS data mapping documentation) In-Reply-To: <1430349104154.79827@harvard.edu> References: , , <1430349104154.79827@harvard.edu> Message-ID: <1430396033656.9847@lyrasis.org> Hi, The attribute label for is imported as the instance's instance_type property. If one is not present it's set as "mixed_material" See: https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L499 Looks like this was let off the EAD to ArchivesSpace document. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Bowers, Kate A. Sent: Thursday, April 30, 2015 1:11 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] FW: EAD ingest default values (still looking for accurate EAD to AS data mapping documentation) Wow! Thanks for that Maura. According to the only map I know of, http://www.archivesspace.org/sites/default/files/EAD-Import-Export-Mapping-20130831.xlsx, in which there is no mention of the label attribute--and that's supposed to mean it doesn't get ingested--I believe, or at least that's what I was told about no mention of attributes for extents in the same document. Yet, according to your experience, it maps to instance type. Can someone point me to move up-to-date or more accurate mapping documentation? Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Maura Carbone Sent: Wednesday, April 29, 2015 3:04:36 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] FW: EAD ingest default values Hi Kate, I think that might be a default if you don't give a label. I did a test import using this and I get the correct type (graphic materials not mixed): Test Item199912Subtitle

pizza is good

The only thing I did have to do is merge in the controlled value list "graphic materials" and "Graphic Materials" so that the label was not entirely lower case. Hope that helps. -Maura On Wed, Apr 29, 2015 at 2:02 PM, Christine Di Bella > wrote: Forwarded on behalf of Kate Bowers. From: Bowers, Kate A. [mailto:kate_bowers at harvard.edu] Sent: Wednesday, April 29, 2015 12:57 PM To: archivesspace_users_group-bounces at lyralists.lyrasis.org Subject: EAD ingest default values What are other repositories doing about default values added by ArchivesSpace upon ingest? For example, if I am reading the EAD ingest map accurately, all instances are asserted to be ?mixed_materials? which of course is not right if I?m ingesting EAD describing a photographic collection. And, of course, any collection that is genuinely of mixed materials is frequently made up of components that are a single medium. Is there a way to assign a value of ?unspecified? (or some other value) so that we can distinguish between values that have been purposefully assigned and those that are merely blanket values created by the ingest process? Thanks, Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From kate_bowers at harvard.edu Thu Apr 30 08:40:11 2015 From: kate_bowers at harvard.edu (Bowers, Kate A.) Date: Thu, 30 Apr 2015 12:40:11 +0000 Subject: [Archivesspace_Users_Group] FW: EAD ingest default values (still looking for accurate EAD to AS data mapping documentation) In-Reply-To: <1430396033656.9847@lyrasis.org> References: , , <1430349104154.79827@harvard.edu>,<1430396033656.9847@lyrasis.org> Message-ID: <1430397610966.37373@harvard.edu> Ah! Thank you! That is extremely helpful. We're trying to outline a project for ingest of about 6000 EAD. Archivists outlining the project at a high level need to be sure the project maps EAD successfully for our needs, and we've been left scratching our heads over what we see AS has done with our test EAD. Question of whether, or in what combination, to transform our EAD prior to ingest or change AS ingest itself. Looks like we need to say "some of each, probably" and leave specifics to the programmer, but archivists will have to review a data map produced by the project since the AS one is unreliable. Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Chris Fitzpatrick Sent: Thursday, April 30, 2015 8:13:53 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] FW: EAD ingest default values (still looking for accurate EAD to AS data mapping documentation) Hi, The attribute label for is imported as the instance's instance_type property. If one is not present it's set as "mixed_material" See: https://github.com/archivesspace/archivesspace/blob/master/backend/app/converters/ead_converter.rb#L499 Looks like this was let off the EAD to ArchivesSpace document. b,chris. Chris Fitzpatrick | Developer, ArchivesSpace Skype: chrisfitzpat | Phone: 918.236.6048 http://archivesspace.org/ ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Bowers, Kate A. Sent: Thursday, April 30, 2015 1:11 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] FW: EAD ingest default values (still looking for accurate EAD to AS data mapping documentation) Wow! Thanks for that Maura. According to the only map I know of, http://www.archivesspace.org/sites/default/files/EAD-Import-Export-Mapping-20130831.xlsx, in which there is no mention of the label attribute--and that's supposed to mean it doesn't get ingested--I believe, or at least that's what I was told about no mention of attributes for extents in the same document. Yet, according to your experience, it maps to instance type. Can someone point me to move up-to-date or more accurate mapping documentation? Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives Cambridge, Massachusetts, USA voice: (617) 384-7787 fax: (617) 495-8011 kate_bowers at harvard.edu ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org on behalf of Maura Carbone Sent: Wednesday, April 29, 2015 3:04:36 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] FW: EAD ingest default values Hi Kate, I think that might be a default if you don't give a label. I did a test import using this and I get the correct type (graphic materials not mixed): Test Item199912Subtitle

pizza is good

The only thing I did have to do is merge in the controlled value list "graphic materials" and "Graphic Materials" so that the label was not entirely lower case. Hope that helps. -Maura On Wed, Apr 29, 2015 at 2:02 PM, Christine Di Bella > wrote: Forwarded on behalf of Kate Bowers. From: Bowers, Kate A. [mailto:kate_bowers at harvard.edu] Sent: Wednesday, April 29, 2015 12:57 PM To: archivesspace_users_group-bounces at lyralists.lyrasis.org Subject: EAD ingest default values What are other repositories doing about default values added by ArchivesSpace upon ingest? For example, if I am reading the EAD ingest map accurately, all instances are asserted to be ?mixed_materials? which of course is not right if I?m ingesting EAD describing a photographic collection. And, of course, any collection that is genuinely of mixed materials is frequently made up of components that are a single medium. Is there a way to assign a value of ?unspecified? (or some other value) so that we can distinguish between values that have been purposefully assigned and those that are merely blanket values created by the ingest process? Thanks, Kate Kate Bowers Collections Services Archivist for Metadata, Systems, and Standards Harvard University Archives kate_bowers at harvard.edu 617.496.2713 voice: (617) 384-7787 fax: (617) 495-8011 web: http://nrs.harvard.edu/urn-3:hul.eresource:archives Twitter: @k8_bowers _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From vaddoniz at jhu.edu Thu Apr 30 11:02:22 2015 From: vaddoniz at jhu.edu (Valerie Addonizio) Date: Thu, 30 Apr 2015 15:02:22 +0000 Subject: [Archivesspace_Users_Group] Import accessions only? In-Reply-To: References: <7eacb1ea46d0469ca008294243df05b6@ESGMTWEX12.win.ad.jhu.edu> <0b99a8b29cc24305bfccc78c6af799b8@ESGMTWEX12.win.ad.jhu.edu> <4F276297-055E-4BF9-93D2-B2BFFAEB8666@yale.edu> Message-ID: Hopkins is going to move forward with testing the idea of migrating the accession from a cloned instance of AT, thanks to Maureen for the suggestion. I had a quick question: I only want to migrate the names and subjects that are associated with my accession records. If I delete all the Resources from AT, and migrate, will ALL names and subjects migrate, including those that are now unlinked? If so, is there a way for me to isolate only those that are linked to accession records? -Valerie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Valerie Addonizio Sent: Wednesday, April 29, 2015 12:43 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import accessions only? Thank you, I hadn?t thought of those two options. I like the AT clone idea?. -Valerie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maura Carbone Sent: Wednesday, April 29, 2015 12:04 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import accessions only? The batch delete is a good option, although you then might have to clear out a whole bunch of agents and subjects, so the clone of AT might be a cleaner option in the long run. On Wed, Apr 29, 2015 at 11:59 AM, Callahan, Maureen > wrote: You could also clone your AT database, delete everything else from the database except accession records, and then just migrate those. You could also migrate everything to AS and use the API to batch delete everything you don?t want. Maureen On Apr 29, 2015, at 11:50 AM, Valerie Addonizio > wrote: Nathan, Thank you. Is my second assumption also correct? -Valerie From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Nathan Stevens Sent: Wednesday, April 29, 2015 11:40 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Import accessions only? Hi, you are correct. It not possible to just import Accessions with the AT to AS migration tool. On Wed, Apr 29, 2015 at 11:35 AM, Valerie Addonizio > wrote: This is a very basic newbie question: I want to confirm whether it is possible to import only accessions with the AT to AS migrator? And if not, confirm that the only way to isolate the accessions would be to export them from AT as CSV, and then import into AS? Thanks! -Valerie -------------------------------- Valerie Addonizio Archivist The Sheridan Libraries Johns Hopkins University vaddoniz at jhu.edu 410-516-5261 _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Nathan Stevens Programmer/Analyst Digital Library Technology Services New York University 1212-998-2653 ns96 at nyu.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=18hoCacgQPRkGWmD7Rp1vha5NbrBDgRYlx0DytyR-nk&s=zmtnF80nx5UJsQsKsQETqTeNYHtRjdVTVxLoum3WZZo&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From lindsay-morecraft at uiowa.edu Thu Apr 30 11:38:15 2015 From: lindsay-morecraft at uiowa.edu (Morecraft, Lindsay M) Date: Thu, 30 Apr 2015 15:38:15 +0000 Subject: [Archivesspace_Users_Group] Date Label in RDE In-Reply-To: References: <213B97E293CEAF4EA0383FF5B29E66ED817D1E83@CTCXMBX10.ap.org> <96B305F061ED68428DDA721BECE2ED155166C306@ITSNT440.iowa.uiowa.edu> Message-ID: <96B305F061ED68428DDA721BECE2ED1551676553@ITSNT440.iowa.uiowa.edu> Thanks so much! It is appreciated. Lindsay Lindsay Moen (Morecraft) Processing Librarian Special Collections and University Archives The University of Iowa 319-335-5921 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brad Westbrook Sent: Wednesday, April 29, 2015 5:11 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Date Label in RDE Hi, Lindsay and Francesca, I have entered a feature request for a date label in the RDE. The request is logged as https://archivesspace.atlassian.net/browse/AR-1218?jql=. Please add any other details you believe necessary. Thanks, Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Morecraft, Lindsay M Sent: Friday, April 24, 2015 10:52 AM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Date Label in RDE I asked about this a few weeks ago, and also agree with Francesca that it is very time consuming. It would be very helpful if there was a date label option in Rapid Data Entry. Thanks, Lindsay Moen (Morecraft) Processing Librarian Special Collections and University Archives The University of Iowa 319-335-5921 From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Pitaro, Francesca Sent: Friday, April 24, 2015 9:49 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Date Label in RDE Hello, Is there some way to set a default for the date label when using Rapid Data Entry? When I enter archival objects individually, my chosen default ("creation") pops into the field, but when I use the RDE to create the record, the date label field appears as "Other". It's very time consuming to then go back in and change the label for each archival object individually to "creation". Thanks, Francesca [cid:image001.jpg at 01D08331.C3136A10] [signature-96] Francesca Pitaro Processing Archivist AP Corporate Archives fpitaro at ap.org www.ap.org 450 W 33rd St New York, NY 10001 T 212.621.7446 The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at +1-212-621-1898 and delete this email. Thank you. [IP_US_DISC] msk dccc60c6d2c3a6438f0cf467d9a4938 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 13756 bytes Desc: image001.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 14637 bytes Desc: image002.jpg URL: From jmargalo at udel.edu Thu Apr 30 11:39:50 2015 From: jmargalo at udel.edu (Jaime Margalotti) Date: Thu, 30 Apr 2015 11:39:50 -0400 Subject: [Archivesspace_Users_Group] Extent Type Message-ID: How are other people dealing with the singular/plural issues in Extent Type? What I mean by this is we might have 1 volume or 2 volumes in a collection. Do you have both "volume" and "volumes" in the Extent Type drop-down or do you force people to chose "volumes" even if they only have 1 item (and then manually fix the spawned finding aid/marc record)? This may sound silly, but is actually an incredibly important question for my cleanup and clarification of procedures going forward. Thanks! Jaime -- Jaime L. Margalotti Senior Assistant Librarian Manuscripts and Archives Department University of Delaware Library Newark, DE 19717-5267 302-831-0554jmargalo at udel.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Thu Apr 30 13:27:15 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Thu, 30 Apr 2015 17:27:15 +0000 Subject: [Archivesspace_Users_Group] Extent Type In-Reply-To: References: Message-ID: Hi, Jaime, One thing I have done in the past is to use the ?parenthetical plural,? for lack of a better phrase, i.e., ?volume(s)?, ?image(s), etc. Thus, 1 volume(s) or 4 volume(s). This does not work for foot/feet obviously. That?s just one suggestion. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jaime Margalotti Sent: Thursday, April 30, 2015 11:40 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Extent Type How are other people dealing with the singular/plural issues in Extent Type? What I mean by this is we might have 1 volume or 2 volumes in a collection. Do you have both "volume" and "volumes" in the Extent Type drop-down or do you force people to chose "volumes" even if they only have 1 item (and then manually fix the spawned finding aid/marc record)? This may sound silly, but is actually an incredibly important question for my cleanup and clarification of procedures going forward. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From maureen.callahan at yale.edu Thu Apr 30 13:33:49 2015 From: maureen.callahan at yale.edu (Callahan, Maureen) Date: Thu, 30 Apr 2015 17:33:49 +0000 Subject: [Archivesspace_Users_Group] Extent Type In-Reply-To: References: Message-ID: Another way to go would be to just pick one, and have your XML -> HTML stylesheet take care of plurals. It would look for values greater than one and change it to ?boxes?, for instance. Maureen On Apr 30, 2015, at 1:27 PM, Brad Westbrook > wrote: Hi, Jaime, One thing I have done in the past is to use the ?parenthetical plural,? for lack of a better phrase, i.e., ?volume(s)?, ?image(s), etc. Thus, 1 volume(s) or 4 volume(s). This does not work for foot/feet obviously. That?s just one suggestion. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jaime Margalotti Sent: Thursday, April 30, 2015 11:40 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Extent Type How are other people dealing with the singular/plural issues in Extent Type? What I mean by this is we might have 1 volume or 2 volumes in a collection. Do you have both "volume" and "volumes" in the Extent Type drop-down or do you force people to chose "volumes" even if they only have 1 item (and then manually fix the spawned finding aid/marc record)? This may sound silly, but is actually an incredibly important question for my cleanup and clarification of procedures going forward. 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 https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=vVka-ToL-w1pt7M2x8kzhbCHHJivg-8KKZ6lcJFr4t0&s=fDTmaDRaEvdg4Y45Wi2HRRXBzqqu8IvZVdX1sesCgck&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From maureen.callahan at yale.edu Thu Apr 30 13:38:28 2015 From: maureen.callahan at yale.edu (Callahan, Maureen) Date: Thu, 30 Apr 2015 17:38:28 +0000 Subject: [Archivesspace_Users_Group] updating the enumerations file Message-ID: <59292598-AB5C-4F1F-85FA-9FFA43150B90@yale.edu> Hi everyone, Have you ever updated the archivesspace/locales/enums/en.yml file? We?re trying to do so, and while I?ve been able to get the file to successfully load (it doesn?t throw an error, which is what happens if the formatting is improper), it also doesn?t, like, *stick*. I still see the default values. Is this a cacheing/indexing/whatever problem? Is there a step beyond updating the file that I should know? Thanks for your help with what is probably a dumb question. Maureen Maureen Callahan Archivist, Metadata Specialist Manuscripts & Archives Yale University Library maureen.callahan at yale.edu 203.432.3627 Webpage: web.library.yale.edu/mssa Collections: drs.library.yale.edu From maureen.callahan at yale.edu Thu Apr 30 13:39:40 2015 From: maureen.callahan at yale.edu (Callahan, Maureen) Date: Thu, 30 Apr 2015 17:39:40 +0000 Subject: [Archivesspace_Users_Group] Extent Type In-Reply-To: References: Message-ID: This, of course, assumes that you?re publishing elsewhere as HTML and not using the public interface of ASpace? MC On Apr 30, 2015, at 1:33 PM, Callahan, Maureen > wrote: Another way to go would be to just pick one, and have your XML -> HTML stylesheet take care of plurals. It would look for values greater than one and change it to ?boxes?, for instance. Maureen On Apr 30, 2015, at 1:27 PM, Brad Westbrook > wrote: Hi, Jaime, One thing I have done in the past is to use the ?parenthetical plural,? for lack of a better phrase, i.e., ?volume(s)?, ?image(s), etc. Thus, 1 volume(s) or 4 volume(s). This does not work for foot/feet obviously. That?s just one suggestion. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jaime Margalotti Sent: Thursday, April 30, 2015 11:40 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Extent Type How are other people dealing with the singular/plural issues in Extent Type? What I mean by this is we might have 1 volume or 2 volumes in a collection. Do you have both "volume" and "volumes" in the Extent Type drop-down or do you force people to chose "volumes" even if they only have 1 item (and then manually fix the spawned finding aid/marc record)? This may sound silly, but is actually an incredibly important question for my cleanup and clarification of procedures going forward. 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 https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=vVka-ToL-w1pt7M2x8kzhbCHHJivg-8KKZ6lcJFr4t0&s=fDTmaDRaEvdg4Y45Wi2HRRXBzqqu8IvZVdX1sesCgck&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=9uZdyUw-XqsG0gl8w8g2OoYUJWCd7XfMXO2wr1yg8i0&s=g47NgUAosP9m04t-bwOxcQReM3fCSeKItgWEEq6UbOg&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad.westbrook at lyrasis.org Thu Apr 30 13:40:40 2015 From: brad.westbrook at lyrasis.org (Brad Westbrook) Date: Thu, 30 Apr 2015 17:40:40 +0000 Subject: [Archivesspace_Users_Group] updating the enumerations file In-Reply-To: <59292598-AB5C-4F1F-85FA-9FFA43150B90@yale.edu> References: <59292598-AB5C-4F1F-85FA-9FFA43150B90@yale.edu> Message-ID: Hi, Maureen, Did you close ASpace, edit the file, and then restart Aspace? b -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Callahan, Maureen Sent: Thursday, April 30, 2015 1:38 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] updating the enumerations file Hi everyone, Have you ever updated the archivesspace/locales/enums/en.yml file? We?re trying to do so, and while I?ve been able to get the file to successfully load (it doesn?t throw an error, which is what happens if the formatting is improper), it also doesn?t, like, *stick*. I still see the default values. Is this a cacheing/indexing/whatever problem? Is there a step beyond updating the file that I should know? Thanks for your help with what is probably a dumb question. Maureen Maureen Callahan Archivist, Metadata Specialist Manuscripts & Archives Yale University Library maureen.callahan at yale.edu 203.432.3627 Webpage: web.library.yale.edu/mssa Collections: drs.library.yale.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From PGalligan at rockarch.org Thu Apr 30 13:41:49 2015 From: PGalligan at rockarch.org (Galligan, Patrick) Date: Thu, 30 Apr 2015 13:41:49 -0400 Subject: [Archivesspace_Users_Group] updating the enumerations file In-Reply-To: <59292598-AB5C-4F1F-85FA-9FFA43150B90@yale.edu> References: <59292598-AB5C-4F1F-85FA-9FFA43150B90@yale.edu> Message-ID: We've done it for small things, and it seems to stick for us. I can't think of any reason why it wouldn't stick, because it doesn't change when you start or stop the running instance. We have really only changed a couple of lines though. I've always made the edits while the AS instance was stopped. Patrick Galligan Rockefeller Archive Center Assistant Digital Archivist 914-366-6386 -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Callahan, Maureen Sent: Thursday, April 30, 2015 1:38 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] updating the enumerations file Hi everyone, Have you ever updated the archivesspace/locales/enums/en.yml file? We?re trying to do so, and while I?ve been able to get the file to successfully load (it doesn?t throw an error, which is what happens if the formatting is improper), it also doesn?t, like, *stick*. I still see the default values. Is this a cacheing/indexing/whatever problem? Is there a step beyond updating the file that I should know? Thanks for your help with what is probably a dumb question. Maureen Maureen Callahan Archivist, Metadata Specialist Manuscripts & Archives Yale University Library maureen.callahan at yale.edu 203.432.3627 Webpage: web.library.yale.edu/mssa Collections: drs.library.yale.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group From maureen.callahan at yale.edu Thu Apr 30 13:42:42 2015 From: maureen.callahan at yale.edu (Callahan, Maureen) Date: Thu, 30 Apr 2015 17:42:42 +0000 Subject: [Archivesspace_Users_Group] updating the enumerations file In-Reply-To: References: <59292598-AB5C-4F1F-85FA-9FFA43150B90@yale.edu> Message-ID: <49CFFE2A-F419-4A3F-A16F-432164605F14@yale.edu> Yes I did. I tried re-starting the application a couple of times, but no dice so far. I also had a colleague try this on her local instillation as well. Maureen On Apr 30, 2015, at 1:40 PM, Brad Westbrook > wrote: Hi, Maureen, Did you close ASpace, edit the file, and then restart Aspace? b -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Callahan, Maureen Sent: Thursday, April 30, 2015 1:38 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] updating the enumerations file Hi everyone, Have you ever updated the archivesspace/locales/enums/en.yml file? We?re trying to do so, and while I?ve been able to get the file to successfully load (it doesn?t throw an error, which is what happens if the formatting is improper), it also doesn?t, like, *stick*. I still see the default values. Is this a cacheing/indexing/whatever problem? Is there a step beyond updating the file that I should know? Thanks for your help with what is probably a dumb question. Maureen Maureen Callahan Archivist, Metadata Specialist Manuscripts & Archives Yale University Library maureen.callahan at yale.edu 203.432.3627 Webpage: web.library.yale.edu/mssa Collections: drs.library.yale.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwIGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=pBScezzUf_UPzb08UhVmNWd7iMH6O3IK4IPxOmqC2tA&s=U-B_SiTZZhkWQqCio-aCMBCG3J9bQjBurwyP5rCBQ54&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwIGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=pBScezzUf_UPzb08UhVmNWd7iMH6O3IK4IPxOmqC2tA&s=U-B_SiTZZhkWQqCio-aCMBCG3J9bQjBurwyP5rCBQ54&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From prom at illinois.edu Thu Apr 30 13:45:31 2015 From: prom at illinois.edu (Prom, Christopher John) Date: Thu, 30 Apr 2015 17:45:31 +0000 Subject: [Archivesspace_Users_Group] Extent Type In-Reply-To: References: Message-ID: <43D2739A-B90B-45DC-A49D-CDE551224541@illinois.edu> Since the filed is a number, it would be best if public interface views test the value and add plurals when necessary. Chris On Apr 30, 2015, at 12:39 PM, Callahan, Maureen > wrote: This, of course, assumes that you?re publishing elsewhere as HTML and not using the public interface of ASpace? MC On Apr 30, 2015, at 1:33 PM, Callahan, Maureen > wrote: Another way to go would be to just pick one, and have your XML -> HTML stylesheet take care of plurals. It would look for values greater than one and change it to ?boxes?, for instance. Maureen On Apr 30, 2015, at 1:27 PM, Brad Westbrook > wrote: Hi, Jaime, One thing I have done in the past is to use the ?parenthetical plural,? for lack of a better phrase, i.e., ?volume(s)?, ?image(s), etc. Thus, 1 volume(s) or 4 volume(s). This does not work for foot/feet obviously. That?s just one suggestion. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jaime Margalotti Sent: Thursday, April 30, 2015 11:40 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Extent Type How are other people dealing with the singular/plural issues in Extent Type? What I mean by this is we might have 1 volume or 2 volumes in a collection. Do you have both "volume" and "volumes" in the Extent Type drop-down or do you force people to chose "volumes" even if they only have 1 item (and then manually fix the spawned finding aid/marc record)? This may sound silly, but is actually an incredibly important question for my cleanup and clarification of procedures going forward. 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 https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=vVka-ToL-w1pt7M2x8kzhbCHHJivg-8KKZ6lcJFr4t0&s=fDTmaDRaEvdg4Y45Wi2HRRXBzqqu8IvZVdX1sesCgck&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=9uZdyUw-XqsG0gl8w8g2OoYUJWCd7XfMXO2wr1yg8i0&s=g47NgUAosP9m04t-bwOxcQReM3fCSeKItgWEEq6UbOg&e= _______________________________________________ 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 mark.custer at yale.edu Thu Apr 30 14:20:11 2015 From: mark.custer at yale.edu (Custer, Mark) Date: Thu, 30 Apr 2015 18:20:11 +0000 Subject: [Archivesspace_Users_Group] Extent Type In-Reply-To: <43D2739A-B90B-45DC-A49D-CDE551224541@illinois.edu> References: <43D2739A-B90B-45DC-A49D-CDE551224541@illinois.edu> Message-ID: I've always advocated for storing only a plural extent type ("X feet" is one of the default AT values, so in the past I've never added "X foot" to my database) , and then changing that value for the display when necessary. There aren't too many irregular plural nouns to consider, so it's not that much code to maintain. And I agree that the ASpace Public Interface should handle this. It's the most sensible default, in my opinion, but it could also be a configurable option in a future release of the public interface. Mark P.S. if you don't store plural or singular only, then you'll need to make sure that you combine the two when creating reports. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Prom, Christopher John Sent: Thursday, April 30, 2015 1:46 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] Extent Type Since the filed is a number, it would be best if public interface views test the value and add plurals when necessary. Chris On Apr 30, 2015, at 12:39 PM, Callahan, Maureen > wrote: This, of course, assumes that you're publishing elsewhere as HTML and not using the public interface of ASpace... MC On Apr 30, 2015, at 1:33 PM, Callahan, Maureen > wrote: Another way to go would be to just pick one, and have your XML -> HTML stylesheet take care of plurals. It would look for values greater than one and change it to "boxes", for instance. Maureen On Apr 30, 2015, at 1:27 PM, Brad Westbrook > wrote: Hi, Jaime, One thing I have done in the past is to use the "parenthetical plural," for lack of a better phrase, i.e., "volume(s)", "image(s), etc. Thus, 1 volume(s) or 4 volume(s). This does not work for foot/feet obviously. That's just one suggestion. Brad W. From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jaime Margalotti Sent: Thursday, April 30, 2015 11:40 AM To: archivesspace_users_group at lyralists.lyrasis.org Subject: [Archivesspace_Users_Group] Extent Type How are other people dealing with the singular/plural issues in Extent Type? What I mean by this is we might have 1 volume or 2 volumes in a collection. Do you have both "volume" and "volumes" in the Extent Type drop-down or do you force people to chose "volumes" even if they only have 1 item (and then manually fix the spawned finding aid/marc record)? This may sound silly, but is actually an incredibly important question for my cleanup and clarification of procedures going forward. 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 https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=vVka-ToL-w1pt7M2x8kzhbCHHJivg-8KKZ6lcJFr4t0&s=fDTmaDRaEvdg4Y45Wi2HRRXBzqqu8IvZVdX1sesCgck&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=9uZdyUw-XqsG0gl8w8g2OoYUJWCd7XfMXO2wr1yg8i0&s=g47NgUAosP9m04t-bwOxcQReM3fCSeKItgWEEq6UbOg&e= _______________________________________________ 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 maureen.callahan at yale.edu Thu Apr 30 14:29:24 2015 From: maureen.callahan at yale.edu (Callahan, Maureen) Date: Thu, 30 Apr 2015 18:29:24 +0000 Subject: [Archivesspace_Users_Group] updating the enumerations file In-Reply-To: <49CFFE2A-F419-4A3F-A16F-432164605F14@yale.edu> References: <59292598-AB5C-4F1F-85FA-9FFA43150B90@yale.edu> <49CFFE2A-F419-4A3F-A16F-432164605F14@yale.edu> Message-ID: I see in the readme: * "enums/en.yml" contains the entries for the dynamic enumeration codes - add your translations to this file after importing your enumeration codes What does it mean to import enumeration codes? Any insights? MC On Apr 30, 2015, at 1:42 PM, Callahan, Maureen > wrote: Yes I did. I tried re-starting the application a couple of times, but no dice so far. I also had a colleague try this on her local instillation as well. Maureen On Apr 30, 2015, at 1:40 PM, Brad Westbrook > wrote: Hi, Maureen, Did you close ASpace, edit the file, and then restart Aspace? b -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Callahan, Maureen Sent: Thursday, April 30, 2015 1:38 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] updating the enumerations file Hi everyone, Have you ever updated the archivesspace/locales/enums/en.yml file? We?re trying to do so, and while I?ve been able to get the file to successfully load (it doesn?t throw an error, which is what happens if the formatting is improper), it also doesn?t, like, *stick*. I still see the default values. Is this a cacheing/indexing/whatever problem? Is there a step beyond updating the file that I should know? Thanks for your help with what is probably a dumb question. Maureen Maureen Callahan Archivist, Metadata Specialist Manuscripts & Archives Yale University Library maureen.callahan at yale.edu 203.432.3627 Webpage: web.library.yale.edu/mssa Collections: drs.library.yale.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwIGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=pBScezzUf_UPzb08UhVmNWd7iMH6O3IK4IPxOmqC2tA&s=U-B_SiTZZhkWQqCio-aCMBCG3J9bQjBurwyP5rCBQ54&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwIGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=pBScezzUf_UPzb08UhVmNWd7iMH6O3IK4IPxOmqC2tA&s=U-B_SiTZZhkWQqCio-aCMBCG3J9bQjBurwyP5rCBQ54&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=86rKvCIfA0ydGkkfLYMcqOUfGLFrvrJp_E9-OrzYb6s&s=GouRUlAccTHzg4bZ4NTkaliZeroCAjw65yxOr_0-FPs&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From Kevin.Clair at du.edu Thu Apr 30 14:38:36 2015 From: Kevin.Clair at du.edu (Kevin Clair) Date: Thu, 30 Apr 2015 18:38:36 +0000 Subject: [Archivesspace_Users_Group] updating the enumerations file In-Reply-To: References: <59292598-AB5C-4F1F-85FA-9FFA43150B90@yale.edu> <49CFFE2A-F419-4A3F-A16F-432164605F14@yale.edu>, Message-ID: <1F1E72103798F04D96C355B296D7C61B4847D3@mb2-uts.du.edu> Hello, Not sure if you've tried this yet, but you can do that from the "Manage Controlled Value Lists" link in the System drop-down menu. I don't know about importing more than one at a time; I usually just add the codes one by one from there, and then edit the en.yml file afterward to add the translations. -k ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Callahan, Maureen [maureen.callahan at yale.edu] Sent: Thursday, April 30, 2015 12:29 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] updating the enumerations file I see in the readme: * "enums/en.yml" contains the entries for the dynamic enumeration codes - add your translations to this file after importing your enumeration codes What does it mean to import enumeration codes? Any insights? MC On Apr 30, 2015, at 1:42 PM, Callahan, Maureen > wrote: Yes I did. I tried re-starting the application a couple of times, but no dice so far. I also had a colleague try this on her local instillation as well. Maureen On Apr 30, 2015, at 1:40 PM, Brad Westbrook > wrote: Hi, Maureen, Did you close ASpace, edit the file, and then restart Aspace? b -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Callahan, Maureen Sent: Thursday, April 30, 2015 1:38 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] updating the enumerations file Hi everyone, Have you ever updated the archivesspace/locales/enums/en.yml file? We?re trying to do so, and while I?ve been able to get the file to successfully load (it doesn?t throw an error, which is what happens if the formatting is improper), it also doesn?t, like, *stick*. I still see the default values. Is this a cacheing/indexing/whatever problem? Is there a step beyond updating the file that I should know? Thanks for your help with what is probably a dumb question. Maureen Maureen Callahan Archivist, Metadata Specialist Manuscripts & Archives Yale University Library maureen.callahan at yale.edu 203.432.3627 Webpage: web.library.yale.edu/mssa Collections: drs.library.yale.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwIGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=pBScezzUf_UPzb08UhVmNWd7iMH6O3IK4IPxOmqC2tA&s=U-B_SiTZZhkWQqCio-aCMBCG3J9bQjBurwyP5rCBQ54&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwIGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=pBScezzUf_UPzb08UhVmNWd7iMH6O3IK4IPxOmqC2tA&s=U-B_SiTZZhkWQqCio-aCMBCG3J9bQjBurwyP5rCBQ54&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=86rKvCIfA0ydGkkfLYMcqOUfGLFrvrJp_E9-OrzYb6s&s=GouRUlAccTHzg4bZ4NTkaliZeroCAjw65yxOr_0-FPs&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Thu Apr 30 14:43:44 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Thu, 30 Apr 2015 14:43:44 -0400 Subject: [Archivesspace_Users_Group] updating the enumerations file In-Reply-To: <1F1E72103798F04D96C355B296D7C61B4847D3@mb2-uts.du.edu> References: <59292598-AB5C-4F1F-85FA-9FFA43150B90@yale.edu> <49CFFE2A-F419-4A3F-A16F-432164605F14@yale.edu> <1F1E72103798F04D96C355B296D7C61B4847D3@mb2-uts.du.edu> Message-ID: Unfortunately, there are some things you can't edit from the System drop-down. I've also tried modifying the en.yml file to add a new date_label but to no avail (stopped and restarted). I'm on version 1.1.2 if that matters at all. -Maura On Thu, Apr 30, 2015 at 2:38 PM, Kevin Clair wrote: > Hello, > > Not sure if you've tried this yet, but you can do that from the "Manage > Controlled Value Lists" link in the System drop-down menu. I don't know > about importing more than one at a time; I usually just add the codes one > by one from there, and then edit the en.yml file afterward to add the > translations. -k > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of > Callahan, Maureen [maureen.callahan at yale.edu] > *Sent:* Thursday, April 30, 2015 12:29 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] updating the enumerations file > > I see in the readme: > > * "enums/en.yml" contains the entries for the dynamic enumeration > codes - add your translations to this file after importing your enumeration > codes > > What does it mean to import enumeration codes? Any insights? > > MC > > On Apr 30, 2015, at 1:42 PM, Callahan, Maureen < > maureen.callahan at yale.edu> wrote: > > Yes I did. I tried re-starting the application a couple of times, but no > dice so far. I also had a colleague try this on her local instillation as > well. > > Maureen > > On Apr 30, 2015, at 1:40 PM, Brad Westbrook > wrote: > > Hi, Maureen, > > Did you close ASpace, edit the file, and then restart Aspace? > > b > > -----Original Message----- > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] On Behalf Of > Callahan, Maureen > Sent: Thursday, April 30, 2015 1:38 PM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] updating the enumerations file > > Hi everyone, > > Have you ever updated the archivesspace/locales/enums/en.yml file? We?re > trying to do so, and while I?ve been able to get the file to successfully > load (it doesn?t throw an error, which is what happens if the formatting is > improper), it also doesn?t, like, *stick*. I still see the default values. > Is this a cacheing/indexing/whatever problem? Is there a step beyond > updating the file that I should know? > > Thanks for your help with what is probably a dumb question. > > Maureen > > Maureen Callahan > Archivist, Metadata Specialist > Manuscripts & Archives > Yale University Library > maureen.callahan at yale.edu > 203.432.3627 > > Webpage: web.library.yale.edu/mssa > Collections: drs.library.yale.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwIGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=pBScezzUf_UPzb08UhVmNWd7iMH6O3IK4IPxOmqC2tA&s=U-B_SiTZZhkWQqCio-aCMBCG3J9bQjBurwyP5rCBQ54&e= > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwIGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=pBScezzUf_UPzb08UhVmNWd7iMH6O3IK4IPxOmqC2tA&s=U-B_SiTZZhkWQqCio-aCMBCG3J9bQjBurwyP5rCBQ54&e= > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=86rKvCIfA0ydGkkfLYMcqOUfGLFrvrJp_E9-OrzYb6s&s=GouRUlAccTHzg4bZ4NTkaliZeroCAjw65yxOr_0-FPs&e= > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From maureen.callahan at yale.edu Thu Apr 30 14:45:20 2015 From: maureen.callahan at yale.edu (Callahan, Maureen) Date: Thu, 30 Apr 2015 18:45:20 +0000 Subject: [Archivesspace_Users_Group] updating the enumerations file In-Reply-To: <1F1E72103798F04D96C355B296D7C61B4847D3@mb2-uts.du.edu> References: <59292598-AB5C-4F1F-85FA-9FFA43150B90@yale.edu> <49CFFE2A-F419-4A3F-A16F-432164605F14@yale.edu> <,> <1F1E72103798F04D96C355B296D7C61B4847D3@mb2-uts.du.edu> Message-ID: <8461C2B3-79F8-480B-819F-93ABF3950DCB@yale.edu> That?s the conclusion that I?m coming to ? I had somehow (erroneously) hoped that the en.yml file both loaded the configurations and provided the translation values, but I now see that it?s just providing a translation. I suppose that I could do them in batch using the API ? http://archivesspace.github.io/archivesspace/doc/file.API.html#post-configenumerations Thanks for taking this journey with me, everyone. Maureen On Apr 30, 2015, at 2:38 PM, Kevin Clair > wrote: Hello, Not sure if you've tried this yet, but you can do that from the "Manage Controlled Value Lists" link in the System drop-down menu. I don't know about importing more than one at a time; I usually just add the codes one by one from there, and then edit the en.yml file afterward to add the translations. -k ________________________________ From: archivesspace_users_group-bounces at lyralists.lyrasis.org [archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of Callahan, Maureen [maureen.callahan at yale.edu] Sent: Thursday, April 30, 2015 12:29 PM To: Archivesspace Users Group Subject: Re: [Archivesspace_Users_Group] updating the enumerations file I see in the readme: * "enums/en.yml" contains the entries for the dynamic enumeration codes - add your translations to this file after importing your enumeration codes What does it mean to import enumeration codes? Any insights? MC On Apr 30, 2015, at 1:42 PM, Callahan, Maureen > wrote: Yes I did. I tried re-starting the application a couple of times, but no dice so far. I also had a colleague try this on her local instillation as well. Maureen On Apr 30, 2015, at 1:40 PM, Brad Westbrook > wrote: Hi, Maureen, Did you close ASpace, edit the file, and then restart Aspace? b -----Original Message----- From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Callahan, Maureen Sent: Thursday, April 30, 2015 1:38 PM To: Archivesspace Users Group Subject: [Archivesspace_Users_Group] updating the enumerations file Hi everyone, Have you ever updated the archivesspace/locales/enums/en.yml file? We?re trying to do so, and while I?ve been able to get the file to successfully load (it doesn?t throw an error, which is what happens if the formatting is improper), it also doesn?t, like, *stick*. I still see the default values. Is this a cacheing/indexing/whatever problem? Is there a step beyond updating the file that I should know? Thanks for your help with what is probably a dumb question. Maureen Maureen Callahan Archivist, Metadata Specialist Manuscripts & Archives Yale University Library maureen.callahan at yale.edu 203.432.3627 Webpage: web.library.yale.edu/mssa Collections: drs.library.yale.edu _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwIGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=pBScezzUf_UPzb08UhVmNWd7iMH6O3IK4IPxOmqC2tA&s=U-B_SiTZZhkWQqCio-aCMBCG3J9bQjBurwyP5rCBQ54&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwIGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=pBScezzUf_UPzb08UhVmNWd7iMH6O3IK4IPxOmqC2tA&s=U-B_SiTZZhkWQqCio-aCMBCG3J9bQjBurwyP5rCBQ54&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=86rKvCIfA0ydGkkfLYMcqOUfGLFrvrJp_E9-OrzYb6s&s=GouRUlAccTHzg4bZ4NTkaliZeroCAjw65yxOr_0-FPs&e= _______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group at lyralists.lyrasis.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=N06BtJ0l0NWCnHIyPqvGnSGwJP69r0zW0UbvSvRDYXE&s=lBHEFRDSgrsWfrHsrS3SerzPjLMpH9jSOqJEKlEO7Zo&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauraa at brandeis.edu Thu Apr 30 15:27:08 2015 From: mauraa at brandeis.edu (Maura Carbone) Date: Thu, 30 Apr 2015 15:27:08 -0400 Subject: [Archivesspace_Users_Group] updating the enumerations file In-Reply-To: <8461C2B3-79F8-480B-819F-93ABF3950DCB@yale.edu> References: <59292598-AB5C-4F1F-85FA-9FFA43150B90@yale.edu> <49CFFE2A-F419-4A3F-A16F-432164605F14@yale.edu> <1F1E72103798F04D96C355B296D7C61B4847D3@mb2-uts.du.edu> <8461C2B3-79F8-480B-819F-93ABF3950DCB@yale.edu> Message-ID: Didn't want to start a new thread since this is so closely related but I keep getting "error: Access denied" when I try to do an update through the API. I am logged in as an admin. Any ideas? On Thu, Apr 30, 2015 at 2:45 PM, Callahan, Maureen < maureen.callahan at yale.edu> wrote: > That?s the conclusion that I?m coming to ? I had somehow (erroneously) > hoped that the en.yml file both loaded the configurations and provided the > translation values, but I now see that it?s just providing a translation. I > suppose that I could do them in batch using the API ? > http://archivesspace.github.io/archivesspace/doc/file.API.html#post-configenumerations > > Thanks for taking this journey with me, everyone. > > Maureen > > > On Apr 30, 2015, at 2:38 PM, Kevin Clair wrote: > > Hello, > > Not sure if you've tried this yet, but you can do that from the "Manage > Controlled Value Lists" link in the System drop-down menu. I don't know > about importing more than one at a time; I usually just add the codes one > by one from there, and then edit the en.yml file afterward to add the > translations. -k > ------------------------------ > *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [ > archivesspace_users_group-bounces at lyralists.lyrasis.org] on behalf of > Callahan, Maureen [maureen.callahan at yale.edu] > *Sent:* Thursday, April 30, 2015 12:29 PM > *To:* Archivesspace Users Group > *Subject:* Re: [Archivesspace_Users_Group] updating the enumerations file > > I see in the readme: > > * "enums/en.yml" contains the entries for the dynamic enumeration > codes - add your translations to this file after importing your enumeration > codes > > What does it mean to import enumeration codes? Any insights? > > MC > > On Apr 30, 2015, at 1:42 PM, Callahan, Maureen < > maureen.callahan at yale.edu> wrote: > > Yes I did. I tried re-starting the application a couple of times, but no > dice so far. I also had a colleague try this on her local instillation as > well. > > Maureen > > On Apr 30, 2015, at 1:40 PM, Brad Westbrook > wrote: > > Hi, Maureen, > > Did you close ASpace, edit the file, and then restart Aspace? > > b > > -----Original Message----- > From: archivesspace_users_group-bounces at lyralists.lyrasis.org [ > mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org > ] On Behalf Of > Callahan, Maureen > Sent: Thursday, April 30, 2015 1:38 PM > To: Archivesspace Users Group > Subject: [Archivesspace_Users_Group] updating the enumerations file > > Hi everyone, > > Have you ever updated the archivesspace/locales/enums/en.yml file? We?re > trying to do so, and while I?ve been able to get the file to successfully > load (it doesn?t throw an error, which is what happens if the formatting is > improper), it also doesn?t, like, *stick*. I still see the default values. > Is this a cacheing/indexing/whatever problem? Is there a step beyond > updating the file that I should know? > > Thanks for your help with what is probably a dumb question. > > Maureen > > Maureen Callahan > Archivist, Metadata Specialist > Manuscripts & Archives > Yale University Library > maureen.callahan at yale.edu > 203.432.3627 > > Webpage: web.library.yale.edu/mssa > Collections: drs.library.yale.edu > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwIGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=pBScezzUf_UPzb08UhVmNWd7iMH6O3IK4IPxOmqC2tA&s=U-B_SiTZZhkWQqCio-aCMBCG3J9bQjBurwyP5rCBQ54&e= > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwIGaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=pBScezzUf_UPzb08UhVmNWd7iMH6O3IK4IPxOmqC2tA&s=U-B_SiTZZhkWQqCio-aCMBCG3J9bQjBurwyP5rCBQ54&e= > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=86rKvCIfA0ydGkkfLYMcqOUfGLFrvrJp_E9-OrzYb6s&s=GouRUlAccTHzg4bZ4NTkaliZeroCAjw65yxOr_0-FPs&e= > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=AwICAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=JgH2YCQ8D3P9-Lm_x4bv3d2CZBYlbx6hxnLFHtfovi8&m=N06BtJ0l0NWCnHIyPqvGnSGwJP69r0zW0UbvSvRDYXE&s=lBHEFRDSgrsWfrHsrS3SerzPjLMpH9jSOqJEKlEO7Zo&e= > > > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group at lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > -- Maura Carbone Digital Initiatives Librarian Brandeis University Library and Technology Services (781) 736-4659 415 South Street, (MS 017/P.O. Box 549110) Waltham, MA 02454-9110 email: mauraa at brandeis.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From mlester at folkartmuseum.org Thu Apr 30 16:52:49 2015 From: mlester at folkartmuseum.org (Mimi Lester) Date: Thu, 30 Apr 2015 16:52:49 -0400 Subject: [Archivesspace_Users_Group] one instance splitting into two Message-ID: Hello all- We've exported a resource record in EAD from AS 1.1 using the derby test database into AS 1.2 using MySQL. One issue that came up is instances with Container 1 and Container 2 fields filled in were split so that there are now two instances each with Container 1 filled (so the first instance Container 1 is box #, and the second instance Container 1 is folder #). Is there a way to bulk correct this issue? Mimi Lester Rapaport Archivist American Folk Art Museum Administrative Office 47-29 32nd Place Long Island City, NY 11101-2409 tel. 646-856-8914 March 26 - July 5, 2015 -------------- next part -------------- An HTML attachment was scrubbed... URL: