Re: [Archivesspace_Users_Group] Offsite boxes and ASpace

[James Bullen]

Hi Sarit,

Just a quick word on maintenance of plugins we develop ...

We usually fix bugs quickly when they are reported. Ongoing development is done 
on a project basis - if someone funds the work, we’ll do it. This includes 
extending functionality and upgrading for new versions of ArchivesSpace.

We recently did a project with Yale to upgrade all of their plugins for 
compatibility with AS v3.3.x. The fact that this one didn’t get touched 
suggests that it didn’t need any modification for the upgrade.


Cheers,
James



> On May 12, 2023, at 6:24 AM, Hand, Sarit  wrote:
> 
> Hi Mark,
>  
> I was just wondering if this plugin is still operational and/or further 
> development has been made. I want to create an offsite location record so I 
> can give it as a location to our top containers. Ultimately, I would like to 
> be able to generate a report based on what is at the offsite storage AND 
> calculate the extent.
>  
> There is one other issue with regard to the extent, I would like to be able 
> to select the extent record based on the type, i.e. Linear ft, rather than 
> just get all the extent regards mixed in for those records that may have 
> linear ft calculated as well as number of items or GB, etc. Does that make 
> sense? I am trying to figure out how to handle locations with offsite 
> storage. I also don’t see how to add an address to a location, i.e. the 
> building address.
>  
> Anyone have thoughts on this?
>  
> Thank you!
> Cheers
>  
> 
>  
> Sarit Hand
> Digital Archivist
> AP Corporate Archives
> 
> 200 Liberty Street
> New York, NY 10281
> T 212.621.7035
>  
> sh...@ap.org 
> ap.org 
> 
>  
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  
>  > On Behalf 
> Of Custer, Mark
> Sent: Thursday, January 28, 2021 11:27 AM
> To: Archivesspace Users Group 
>  >
> Subject: Re: [Archivesspace_Users_Group] Offsite boxes and ASpace
>  
> [EXTERNAL]
> 
> Adrienne,
>  
> Here's a link to the plugin that Hudson Molonglo developed, which we've been 
> using for about the past six months in production:  
> https://github.com/hudmol/yale_onsite_locations  If you have any questions 
> about it, let us know.
>  
> I would love to see this in the ArchivesSpace core code, but we went with a 
> plugin approach last year so that we could get this feature added ASAP to our 
> instance and so that we could test out how it performs (so far, so great!).  
> The plugin adds an "Onsite?" checkbox to every location, with the default 
> value being set to True.  And once you start flipping some locations to 
> Onsite = False, then information is stored in the index to indicate whether 
> the Resource and Archival Object and Top Container records are stored onsite 
> or offsite.  And since Resource and Archival Objects can be linked to 
> multiple top containers, those records can have a hybrid status.  So, that's 
> why we now have a facet for "Storage Location", as seen in the attached 
> image.  We haven't really highlighted this new feature to users yet, but I am 
> very interested in seeing how it gets used over time.   
>  
> We also talked about adding a feature in the staff interface to calculate a 
> note for the collection to indicate which boxes were onsite vs. offsite based 
> on this information, like the "Calculate Date / Extent" function, but didn't 
> wind up adding that to the plugin, although I still like the idea.  
>  
> And Olivia, since I was still interested in adding such a note to our EAD, 
> even after all these years (has it been over three years? ), I did update 
> our EAD3 export option to include the location information in our EAD files. 
> I did not go with a physloc note, since I agree with you that it would look 
> horrible having that information repeat everywhere if it were to display in 
> the finding aid, so I went with an option of adding the location URI fragment 
> into an attribute on each container element that is associated with an ASpace 
> location record.  Then, since we know which locations that we consider to be 
> onsite vs. offsite, our nightly export process will add a note to each 
> finding aid in the EAD3 control section.  Here's an example:  
> https://github.com/YaleArchivesSpace/Archives-at-Yale-EAD3/blob/5734391e95a954a99cb03ee54282fd14d028c8e3/brbl-ead/10764.xml#L34-L41
>   We aren't using that note for anything right now, but I think that it could 
> be useful for creating our MARC holdings records, as well as for adding to 
> our PDF finding aids, etc.  But right now, it's just there so that staff 
> could potentially use it to review and see if it looks like things are 
> assigned as expected.
>  
> Mark
>  
>  
>  
>  
>  
>  
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
> 

Re: [Archivesspace_Users_Group] Audit changes (through API)

[James Bullen]

Hi Joshua and all,

The public version of as_history probably won’t work outside of the QSA context 
- very heavily customized AS.

We do have a generalized version that works on vanilla AS, but it isn’t open.

Feel free to get in touch if you’re interested in trying it out. It gives full 
version tracking with diffs etc through the staff UI.


Cheers,
James


> On May 3, 2023, at 3:30 AM, Dan Michelson  wrote:
> 
> Hi All,
> 
> Something related to this issue that I learned today from Brian Hoffman is 
> that whenever ArchivesSpace saves a top-level record, all the subrecords are 
> actually deleted and recreated.  This means that it is not possible to 
> reliably track when notes or other subrecords are created or modified.
> 
> All the best,
> 
> Dan
> 
> On Tue, May 2, 2023 at 12:12 PM Joshua D. Shaw  > wrote:
>> There is an extensive set of changes for the Queensland State Archives that 
>> includes functionality like this. I have not used or tested this, so not 
>> sure how customized it is to QSA's needs, but it was developed by Hudson 
>> Molonglo, so it should be good stuff! 
>> https://gitlab.gaiaresources.com.au/qsa/as_history It may or may not work 
>> with the latest version of AS.
>> 
>> Best,
>> Joshua
>> 
>> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>>  
>> > > on behalf 
>> of Corey Schmidt mailto:corey.schm...@uga.edu>>
>> Sent: Tuesday, May 2, 2023 11:44 AM
>> To: Archivesspace Users Group 
>> > >
>> Subject: Re: [Archivesspace_Users_Group] Audit changes (through API)
>>  
>> Hey Scott,
>> 
>> >From my understanding, you are correct that besides a last modified 
>> >timestamp, that’s as deep as ASpace goes in tracking changes to data. We’ve 
>> >had colleagues here express similar interest in wanting to track more 
>> >detailed changes to records, such as when an archivist publishes a record 
>> >or edits a note, but that functionality doesn’t exist as far as I’m aware.
>> 
>> If your local practice is to track changes to records using events, then 
>> it’s possible the user could access the “Get a list of Events for a 
>> Repository 
>> ”
>>  API endpoint (if they are a user in your ArchivesSpace instance) and filter 
>> the results based on records related to a specific resource. That requires 
>> your ArchivesSpace users to be using events in that way to work.
>> 
>> The only other methods that I can think of is possibly using something like 
>> the WayBack Machine  or a web scraper like 
>> BeautifulSoup  with 
>> Python to track changes to any public facing websites you have. WayBack 
>> would only be good for occasional captures and BeautifulSoup would need to 
>> scrape your public-facing website for any updates/newly published records. I 
>> did something like that in grad school, but it was with a blog website and 
>> not finding aids.
>>  
>> I hope this was helpful. Anyone here, please correct me if I’m wrong or 
>> forgetting anything.
>> 
>> Sincerely,
>> 
>> Corey
>> Corey Schmidt 
>> Special Collections Libraries | Project Management Librarian/Archivist
>> 
>> corey.schm...@uga.edu 
>>  
>> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>>  
>> > > On Behalf 
>> Of Scott Renton
>> Sent: Friday, April 28, 2023 5:55 AM
>> To: archivesspace_users_group@lyralists.lyrasis.org 
>> 
>> Subject: [Archivesspace_Users_Group] Audit changes (through API)
>>  
>> [EXTERNAL SENDER - PROCEED CAUTIOUSLY]
>> 
>> Hi there folks
>>  
>> We've had a user request to see if we can extract lists of records that have 
>> changed and what the change is (eg list of records that have changed from 
>> unpublished to publish- part of their work is working through an unpublished 
>> repository and tracking how much they're making available periodically). 
>> They'd like to be able to build something round the API for this.
>>  
>> I didn't think AS went down to that level- we'd see a last modified 
>> timestamp, but I didn't think there was anything deeper. Is that correct? I 
>> know "event" is accessible through the API, but I still couldn't see how 
>> that would get down to a specific data change.
>>  
>> Cheers
>> Scott
>>  
>>  
>> ==
>> 
>> Scott Renton
>> 
>> Digital Library Development & Systems
>> 
>> Floor F East
>> 
>> Argyle House
>> 
>> 515219
>> 
>> The University of Edinburgh is a charitable body, registered in Scotland, 
>> with registration 

Re: [Archivesspace_Users_Group] Adding Resource ID to CSV Download of Search Results in ASpace

[James Bullen]

Hi Aimee and all,

It seems the fields are hardcoded. It is a trivial change to add the 
identifier, at this line:
https://github.com/archivesspace/archivesspace/blob/master/frontend/app/controllers/top_containers_controller.rb#L47

Something like this:
params[:fields].prepend('collection_identifier_stored_u_sstr', 
'collection_display_string_u_sstr', 'series_title_u_sstr')

Perhaps one of the AS developers can sneak this in ;)

And while they’re at it, it would be nice if the column headers were human 
friendly, rather than those solr field names.


Cheers,
James



> On Apr 18, 2023, at 2:23 AM, Leah Tams  wrote:
> 
> I wonder if creating a custom report might get around this issue for you and 
> others? (Disclaimer: I’ve never created a custom report before.)
>  
> Leah
>  
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  
>  > On Behalf 
> Of Aimee Truitt
> Sent: Monday, April 17, 2023 11:52 AM
> To: Archivesspace Users Group 
>  >
> Subject: [Archivesspace_Users_Group] Adding Resource ID to CSV Download of 
> Search Results in ASpace
>  
> Hello Everyone,
> 
> I sent this question out last week, but am sharing again, with some examples, 
> in case that helps my query.
>  
> When I work in ASpace, I use the "Manage Top Containers" search frequently. 
> Sometimes it's helpful to download the CSV of the search, but it doesn't 
> include the Resource ID in the CSV, even though it does in the search 
> results. Is there a setting somewhere in the backend that dictates which 
> fields get printed for the CSV and has anyone successfully added Resource ID?
>  
> Below is a visual of the problem:
>  
> The fields that show on the screen are:
> 
>  
>  
> And the ones I get when I "download CSV" are:
>  
> collection_display_string_u_sstr
> series_title_u_sstr
> container_profile_display_string_u_sstr
> location_display_string_u_sstr
> type_enum_s 
> indicator_u_icusort
> barcode_u_sstr 
>  
> Abstracts of Clothing and Equipment Vol.
> 1 Stacks\, 4\, Track 01\, Range 004 [F04 T01 R004 V01 H10]
> volume 
> BV 02035 
> 34072001270056.00
>  
> Having the SAS # (or whatever Resource ID) in the download, would be a big 
> asset. Seems like a there should be a place to be able to specify which 
> fields are showing and which fields download. I would appreciate any 
> tips/tricks/suggestions! Thank you for your time and help.
>  
> Best Wishes,
>  
> Aimee
>  
> Aimee Truitt (she/her) | Catalog and Metadata Coordinator
> Ohio History Connection | 800 E. 17th Ave., Columbus, OH 43211
> p. 614.297.2589  | f. 614.297.2546 | atru...@ohiohistory.org 
> 
>  
> The Ohio History Connection’s mission 
> 
>  is to spark discovery of Ohio’s stories. Embrace the present, share the past 
> and transform the future. Support the Ohio History Connection: 
> www.ohiohistory.org/give 
> .
>  
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Bulk updater plug-in

[James Bullen]

Hi again Mariam,

It turns out this bug was fixed in version 1.4.1 of the plugin.

We recommend using the latest version - currently 1.5.1:
https://github.com/hudmol/as_spreadsheet_bulk_updater/releases/tag/v1.5.1 
<https://github.com/hudmol/as_spreadsheet_bulk_updater/releases/tag/v1.5.1>

Please get in touch if upgrading doesn’t fix it for you.


Cheers,
James



> On Jul 21, 2022, at 10:35 AM, James Bullen  wrote:
> 
> 
> Hi Mariam,
> 
> That sounds like a bug. We’ll take a look.
> 
> 
> Cheers,
> James
> 
> 
> 
> —
> James Bullen
> Director/Developer
> Hudson Molonglo
> —
> 
> 
>> On Jul 21, 2022, at 1:25 AM, Mariam Yamin > <mailto:m.ya...@sheffield.ac.uk>> wrote:
>> 
>> Hi all,
>> 
>> We've been having problems with using the bulk updater plug-in to add more 
>> than one Top Container to an archival object and wondered if anyone else had 
>> experienced this issue?
>> 
>> We want to use the bulk updater to add top containers to archival objects, 
>> creating the top containers as part of the process. This works perfectly 
>> when adding just one container to an archival object. However, when we try 
>> to add two top containers to one archival object by completing details in 
>> the instance 2 fields in the spreadsheet, the import creates two instances 
>> of the same Top Container (for the top container details in the field 
>> instance 2 rather than instance 1). The Top Container from the instance 1 
>> field in the spreadsheet is created but is not attached to the Resource. 
>> 
>> We're using 2.8.1 but we've tried this on a test instance on 3.0.1 and 
>> encountered the same problem. 
>> 
>> Any help or advice on this would be much appreciated!
>> 
>> Many thanks,
>> 
>> Mariam 
>> 
>> -- 
>> Mariam Yamin
>> Project Archivist 
>> University of Sheffield | Western Bank Library | Sheffield | S10 2TN 
>> 0114 222 7236
>> m.ya...@sheffield.ac.uk <mailto:m.ya...@sheffield.ac.uk>
>> 
>> https://www.sheffield.ac.uk/library/special-collections-heritage-and-archives
>>  
>> <https://www.sheffield.ac.uk/library/special-collections-heritage-and-archives>
>> 
>> Discover Our Archives - https://archives.shef.ac.uk/ 
>> <https://archives.shef.ac.uk/> 
>> 
>> My usual days of work are Mondays to Thursdays and I am currently splitting 
>> my working hours between on campus and remote working. 
>> ___
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group@lyralists.lyrasis.org 
>> <mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Bulk updater plug-in

[James Bullen]

Hi Mariam,

That sounds like a bug. We’ll take a look.


Cheers,
James



—
James Bullen
Director/Developer
Hudson Molonglo
—


> On Jul 21, 2022, at 1:25 AM, Mariam Yamin  wrote:
> 
> Hi all,
> 
> We've been having problems with using the bulk updater plug-in to add more 
> than one Top Container to an archival object and wondered if anyone else had 
> experienced this issue?
> 
> We want to use the bulk updater to add top containers to archival objects, 
> creating the top containers as part of the process. This works perfectly when 
> adding just one container to an archival object. However, when we try to add 
> two top containers to one archival object by completing details in the 
> instance 2 fields in the spreadsheet, the import creates two instances of the 
> same Top Container (for the top container details in the field instance 2 
> rather than instance 1). The Top Container from the instance 1 field in the 
> spreadsheet is created but is not attached to the Resource. 
> 
> We're using 2.8.1 but we've tried this on a test instance on 3.0.1 and 
> encountered the same problem. 
> 
> Any help or advice on this would be much appreciated!
> 
> Many thanks,
> 
> Mariam 
> 
> -- 
> Mariam Yamin
> Project Archivist 
> University of Sheffield | Western Bank Library | Sheffield | S10 2TN 
> 0114 222 7236
> m.ya...@sheffield.ac.uk <mailto:m.ya...@sheffield.ac.uk>
> 
> https://www.sheffield.ac.uk/library/special-collections-heritage-and-archives 
> <https://www.sheffield.ac.uk/library/special-collections-heritage-and-archives>
> 
> Discover Our Archives - https://archives.shef.ac.uk/ 
> <https://archives.shef.ac.uk/> 
> 
> My usual days of work are Mondays to Thursdays and I am currently splitting 
> my working hours between on campus and remote working. 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Problem attaching digital objects to resources in ArchivesSpace 3.1.1

[James Bullen]

Hi,

Since functionality depends on this value being there, it really should be 
readonly. Here’s a PR that does that:
https://github.com/archivesspace/archivesspace/pull/2726 
<https://github.com/archivesspace/archivesspace/pull/2726>


Cheers,
James


> On Jun 19, 2022, at 11:46 AM, James Bullen  wrote:
> 
> 
> Hi Scott,
> 
> When you create a digital object instance on a resource (or archival object) 
> it sets instance_type to digital_object behind the scenes (when you create a 
> container instance you are presented with a dropdown to set the instance_type 
> - excluding the digital_object value as an option).
> 
> Somehow your instance_type enumeration has lost its digital_object value, so 
> when it tries to set that value you get the validation error you’re seeing. 
> In fact the values listed in the error look more like values for 
> container_type than instance_type, so there might be something deeper going 
> on.
> 
> Regardless, you should be able to fix this by adding a digital_object value 
> back into your instance_type enumeration (called instance_instance_type in 
> the 'Manage Controlled Value Lists' dropdown.
> 
> Hope that helps.
> 
> 
> Cheers,
> James
> 
> 
>> On Jun 18, 2022, at 11:50 PM, Blake Carver > <mailto:blake.car...@lyrasis.org>> wrote:
>> 
>> translation missing: 
>> validation_errors.protected_read-only_list_#/instances/0/instance_type._invalid_value__digital_object_.__must_be_one_of__box__volume__oversize_folder__reel__audio__disc__film__video__computer_disk__box-folder__reel-frame__side__sc__package__wcftr__roll__map_case__drawer__aa__ab__ac__ad__ae__baa__ca__cb__cc__cd__da__db__dc__dd__de__df__dg__ea__fe__ff__fg__fh__ga__hb__hc__vbb__vbc__vea__vfa__vha__vhb__vhc__oversize_box__folder__fa__electronic__microfilm__ph_box__video_box__dvd__fb__fc__fd__fi__gb__ha__hd__vpa__vta__box__album__ph_box__disc__video__oversize_folder__box-folder__tape__film_box__tape_box__box/folder__audio__vha
>> 
>> Take a look at the Digital Objects Controlled Value lists 
>> (/staff/enumerations?id=12) I think you're missing something there. 
>> "instance_type._invalid_value__digital_object_.__must_be_one_of__box" is 
>> saying "you're trying to add something that's not in this list, here's 
>> what's in that list"
>> 
>> 
>> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> 
>> > <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> on behalf 
>> of Scott Prater mailto:scott.pra...@wisc.edu>>
>> Sent: Friday, June 17, 2022 6:05 PM
>> To: archivesspace_users_group@lyralists.lyrasis.org 
>> <mailto:archivesspace_users_group@lyralists.lyrasis.org> 
>> > <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
>> Subject: [Archivesspace_Users_Group] Problem attaching digital objects to 
>> resources in ArchivesSpace 3.1.1
>>  
>> Hello,
>> 
>> We have recently begun testing out attaching digital object Instances to our 
>> resources in ArchivesSpace, version 3.1.1.  So far we have no success:  we 
>> can create a digital objects, and we can select one and add it to a resource 
>> in the Resource edit view, but when we then attempt to save the resource, we 
>> get the unhelpful "Validation Error" message with no other information.  The 
>> resource is not updated.
>> 
>> I poked around the code, and temporarily disabled the frontend code where 
>> validation error exceptions are swallowed 
>> (https://github.com/archivesspace/archivesspace/blob/v3.1.1/frontend/app/controllers/application_controller.rb#L366-L388
>>  
>> <https://github.com/archivesspace/archivesspace/blob/v3.1.1/frontend/app/controllers/application_controller.rb#L366-L388>).
>>   I then tried to save the resource with the attached digital object again, 
>> and this time saw the swallowed error:
>> 
>> translation missing: 
>> validation_errors.protected_read-only_list_#/instances/0/instance_type._invalid_value__digital_object_.__must_be_one_of__box__volume__oversize_folder__reel__audio__disc__film__video__computer_disk__box-folder__reel-frame__side__sc__package__wcftr__roll__map_case__drawer__aa__ab__ac__ad__ae__baa__ca__cb__cc__cd__da__db__dc__dd__de__df__dg__ea__fe__ff__fg__fh__ga__hb__hc__vbb__vbc__vea__vfa__vha__vhb__vhc__oversize_box__folder__fa__electronic__microfilm__ph_box__video_box__dvd__fb__fc__fd__fi__gb__ha__hd__vpa__vta__box__album__ph_box__disc__video__oversize_folder__box-folder__tape__film_box__tape_box__box/folder__audio__vha
>> 
>> It looks like somehow a type is not getting set, or th

Re: [Archivesspace_Users_Group] Problem attaching digital objects to resources in ArchivesSpace 3.1.1

[James Bullen]

Hi Scott,

When you create a digital object instance on a resource (or archival object) it 
sets instance_type to digital_object behind the scenes (when you create a 
container instance you are presented with a dropdown to set the instance_type - 
excluding the digital_object value as an option).

Somehow your instance_type enumeration has lost its digital_object value, so 
when it tries to set that value you get the validation error you’re seeing. In 
fact the values listed in the error look more like values for container_type 
than instance_type, so there might be something deeper going on.

Regardless, you should be able to fix this by adding a digital_object value 
back into your instance_type enumeration (called instance_instance_type in the 
'Manage Controlled Value Lists' dropdown.

Hope that helps.


Cheers,
James


> On Jun 18, 2022, at 11:50 PM, Blake Carver  wrote:
> 
> translation missing: 
> validation_errors.protected_read-only_list_#/instances/0/instance_type._invalid_value__digital_object_.__must_be_one_of__box__volume__oversize_folder__reel__audio__disc__film__video__computer_disk__box-folder__reel-frame__side__sc__package__wcftr__roll__map_case__drawer__aa__ab__ac__ad__ae__baa__ca__cb__cc__cd__da__db__dc__dd__de__df__dg__ea__fe__ff__fg__fh__ga__hb__hc__vbb__vbc__vea__vfa__vha__vhb__vhc__oversize_box__folder__fa__electronic__microfilm__ph_box__video_box__dvd__fb__fc__fd__fi__gb__ha__hd__vpa__vta__box__album__ph_box__disc__video__oversize_folder__box-folder__tape__film_box__tape_box__box/folder__audio__vha
> 
> Take a look at the Digital Objects Controlled Value lists 
> (/staff/enumerations?id=12) I think you're missing something there. 
> "instance_type._invalid_value__digital_object_.__must_be_one_of__box" is 
> saying "you're trying to add something that's not in this list, here's what's 
> in that list"
> 
> 
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  on behalf of Scott 
> Prater 
> Sent: Friday, June 17, 2022 6:05 PM
> To: archivesspace_users_group@lyralists.lyrasis.org 
> 
> Subject: [Archivesspace_Users_Group] Problem attaching digital objects to 
> resources in ArchivesSpace 3.1.1
>  
> Hello,
> 
> We have recently begun testing out attaching digital object Instances to our 
> resources in ArchivesSpace, version 3.1.1.  So far we have no success:  we 
> can create a digital objects, and we can select one and add it to a resource 
> in the Resource edit view, but when we then attempt to save the resource, we 
> get the unhelpful "Validation Error" message with no other information.  The 
> resource is not updated.
> 
> I poked around the code, and temporarily disabled the frontend code where 
> validation error exceptions are swallowed 
> (https://github.com/archivesspace/archivesspace/blob/v3.1.1/frontend/app/controllers/application_controller.rb#L366-L388
>  
> ).
>   I then tried to save the resource with the attached digital object again, 
> and this time saw the swallowed error:
> 
> translation missing: 
> validation_errors.protected_read-only_list_#/instances/0/instance_type._invalid_value__digital_object_.__must_be_one_of__box__volume__oversize_folder__reel__audio__disc__film__video__computer_disk__box-folder__reel-frame__side__sc__package__wcftr__roll__map_case__drawer__aa__ab__ac__ad__ae__baa__ca__cb__cc__cd__da__db__dc__dd__de__df__dg__ea__fe__ff__fg__fh__ga__hb__hc__vbb__vbc__vea__vfa__vha__vhb__vhc__oversize_box__folder__fa__electronic__microfilm__ph_box__video_box__dvd__fb__fc__fd__fi__gb__ha__hd__vpa__vta__box__album__ph_box__disc__video__oversize_folder__box-folder__tape__film_box__tape_box__box/folder__audio__vha
> 
> It looks like somehow a type is not getting set, or the backend is mistakenly 
> requiring a type on the digital object.  There is no place I could see in the 
> digital object edit interface where I can select any of those types.  I did 
> select a "Moving image" type on my test digital object, but that did not 
> change the error.
> 
> We've upgraded over the years from ArchivesSpace 2.5.1 to 3.1.1, following 
> the upgrade steps for each new release.  Up to now, we haven't had any 
> problems, but perhaps something has been left behind from previous versions?  
> Or a table is missing in our latest version?  We are running ArchivesSpace 
> locally on our own server;  we have not made any changes to default 
> distributions.
> 
> Any help or insight is appreciated (and yes, we did run a full reindex, to no 
> avail).
> 
> Thanks in advance,
> 
> -- Scott
> 
> -- 
> Scott Prater
> Digital Library Architect
> UW Digital Collections Center
> University of Wisconsin - Madison
> 
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 

Re: [Archivesspace_Users_Group] Create directories for branding resources?

[James Bullen]

Hi,

If you want it in the  then you can include a file called 
public/views/layout_head.html.erb. This file will be included in the head. This 
has the advantage of avoiding having to override a template.


Cheers,
James


> On Jun 11, 2022, at 12:59 AM, Rees, John (NIH/NLM) [E] 
>  wrote:
> 
> Kyle,
>  
> We stick ours in /local/public 
> <https://github.com/John-Rees/nlm-aspace-customizations/tree/main/public>/views
>  
> <https://github.com/John-Rees/nlm-aspace-customizations/tree/main/public/views>/layouts
>  
> <https://github.com/John-Rees/nlm-aspace-customizations/tree/main/public/views/layouts>/application.html.erb
>  
> https://github.com/John-Rees/nlm-aspace-customizations/blob/main/public/views/layouts/application.html.erb
>  
> <https://github.com/John-Rees/nlm-aspace-customizations/blob/main/public/views/layouts/application.html.erb>
>  
>  
> John P. Rees
> Archivist and Digital Resources Manager
> History of Medicine Division
> National Library of Medicine
> 301-827-4510
> Teleworking M-F 8:00AM – 4:30PM Eastern Time each day until further notice
>  
>  
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> 
>  <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> On Behalf 
> Of Kyle Breneman
> Sent: Friday, June 10, 2022 10:24 AM
> To: Archivesspace Users Group 
>  <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] Create directories for 
> branding resources?
>  
> Dear James,
>  
> Yes, this is very helpful!  Thank you for taking the time to reply to my 
> question. 
>  
> I’ve now got my branding changes in place under the /local plugin directory.
>  
> How do I go about including our Google Tag Manager tracking snippet?  I need 
> to insert code in the  of each page, and also right after the opening 
>  tag.  Should that also be done via the /local plugin files?  If so, 
> which file(s)?  I couldn’t find documentation on this.
>  
> Regards,
>  
> Kyle Breneman
> Integrated Digital Services Librarian
> The University of Baltimore
> kbrene...@ubalt.edu <mailto:kbrene...@ubalt.edu>
> I believe in freedom of thought and
> freedom of speech. Do you?
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> 
>  <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> On Behalf 
> Of James Bullen
> Sent: Thursday, June 9, 2022 7:49 PM
> To: Archivesspace Users Group 
>  <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: Re: [Archivesspace_Users_Group] Create directories for branding 
> resources?
>  
> [EXTERNAL EMAIL: This message originated from a non-UBalt email system. Hover 
> over any links before clicking and use caution when opening attachments.]
>  
>  
> Hi Kyle, 
>  
> Those directions are written assuming you’re working on a development 
> instance. When you’re running from a distribution the file paths referred to 
> are contained in war files, so you don’t see them.
>  
> You do not need to create public/app/views/shared/_header.html.erb - that 
> exists within wars/public.war
>  
> To override that file you would place your new version in 
> plugins/yourplugin/public/views/shared/_header.html.erb
>  
> Hope that helps.
>  
>  
> Cheers,
> James
>  
>  
> 
> On Jun 10, 2022, at 3:05 AM, Kyle Breneman  <mailto:kbrene...@ubalt.edu>> wrote:
>  
> I’m trying to follow these directions 
> <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.github.io%2Ftech-docs%2Fcustomization%2Ftheming.html=05%7C01%7Creesj%40mail.nlm.nih.gov%7Ce3c44a56698940eab47e08da4aecda70%7C14b77578977342d58507251ca2dc2b06%7C0%7C0%7C637904678387804526%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=qozHeE%2Fe02MZBVTUWioy9h9zBbTS29qJEV0UGEa8NHg%3D=0>
>  for customizing our ArchivesSpace 3.2.0 instance.
>  
> While the directions clearly state that some/all of the directories in the 
> path to store a branding image will need to be created, I was not expecting 
> to need to create the public/app/views/shared/_header.html.erb file, or those 
> directories, yet they do not seem to exist in my installation (below). Should 
> I proceed to create these directories, along with the _header.html.erb file?
>  
> 
>  
> Kyle Breneman
> Integrated Digital Services Librarian
> The University of Baltimore
> kbrene...@ubalt.edu <mailto:kbrene...@

Re: [Archivesspace_Users_Group] Create directories for branding resources?

[James Bullen]

Hi Kyle,

Those directions are written assuming you’re working on a development instance. 
When you’re running from a distribution the file paths referred to are 
contained in war files, so you don’t see them.

You do not need to create public/app/views/shared/_header.html.erb - that 
exists within wars/public.war

To override that file you would place your new version in 
plugins/yourplugin/public/views/shared/_header.html.erb

Hope that helps.


Cheers,
James


> On Jun 10, 2022, at 3:05 AM, Kyle Breneman  wrote:
> 
> I’m trying to follow these directions 
>  for 
> customizing our ArchivesSpace 3.2.0 instance.
>  
> While the directions clearly state that some/all of the directories in the 
> path to store a branding image will need to be created, I was not expecting 
> to need to create the public/app/views/shared/_header.html.erb file, or those 
> directories, yet they do not seem to exist in my installation (below). Should 
> I proceed to create these directories, along with the _header.html.erb file?
>  
> 
>  
> Kyle Breneman
> Integrated Digital Services Librarian
> The University of Baltimore
> kbrene...@ubalt.edu 
> I believe in freedom of thought and
> freedom of speech. Do you?
>  
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Frontend specific hooks

[James Bullen]

Hi Andrew,

Thanks Joshua. Yes, some of those hooks were introduced as part of our work for 
QSA - the most heavily customized instance of ArchivesSpace we’ve done. Here is 
an example of register_plugin_section being used:
https://gitlab.gaiaresources.com.au/qsa/as_runcorn/-/blob/develop/frontend/plugin_init.rb#L36
 


I hope that helps.


Cheers,
James



> On Jun 10, 2022, at 4:01 AM, Joshua D. Shaw  
> wrote:
> 
> Ooooh! Not examples off the top of my head, but I'm definitely gonna make a 
> lot of use of these! You might take a look at the HM repos 
> (https://github.com/hudmol ) or 
> here:https://gitlab.gaiaresources.com.au/qsa 
>  (also a lot of HM work) since I'm 
> pretty sure they added those plugin hooks.
> 
> jds
> 
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  
>  > on behalf 
> of Andrew Morrison  >
> Sent: Thursday, June 9, 2022 12:35 PM
> To: archivesspace_users_group@lyralists.lyrasis.org 
>  
>  >
> Subject: [Archivesspace_Users_Group] Frontend specific hooks
>  
> Hello,
> 
> Does anybody know of any example code which demonstrates use of the new 
> frontend specific hooks which were introduced, I believe, in 3.1.0:
> 
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.github.io%2Ftech-docs%2Fcustomization%2Fplugins.html%23frontend-specific-hooksdata=05%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7C42f703ebc2f1459840d408da4a361ba7%7C995b093648d640e5a31ebf689ec9446f%7C0%7C0%7C637903893500581190%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=JMcChTi%2Bimp9qr%2FgiLocScgwJ6hrjBgH6D9wftx2kQo%3Dreserved=0
>  
> 
> 
> Thanks,
> 
> Andrew.
> 
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_groupdata=05%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7C42f703ebc2f1459840d408da4a361ba7%7C995b093648d640e5a31ebf689ec9446f%7C0%7C0%7C637903893500581190%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=plnv%2F7BsK15G9Z095WA8lAbZmhKCFBsuQB79iVpu3LM%3Dreserved=0
>  
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Sharing/previewing Accession Records

[James Bullen]

That’s great news thanks Megan.

As you can tell, this was never intended to be useful beyond Yale’s context, so 
the fact that it is potential useful to you and others is a bonus.


Cheers,
James



—
James Bullen
Director/Developer
Hudson Molonglo
—


> On Apr 23, 2022, at 2:58 AM, Schanz, Megan  wrote:
> 
> Thanks James, that did resolve that error for us.
> 
> There was another error after that one, so I ended up making a fork of the 
> repository in case it went down a rabbit hole. Luckily it was only one more 
> error away from working in our instance! The final error was an 
> incompatibility issue between the code and versions of ArchivesSpace greater 
> than v2.8.1 when they updated the FOP library 
> <https://github.com/archivesspace/archivesspace/commit/4a4b1429ad534463c5a291deede1f790f1a6fed5>.
>  I used that same commit 
> <https://github.com/archivesspace/archivesspace/commit/4a4b1429ad534463c5a291deede1f790f1a6fed5>
>  to update the plugin with similar syntax; only needing to update a few lines 
> <https://github.com/MSU-Libraries/accession_slips/commit/9171fd007642e27cf83d5c0ef5490dafd89d6b22>.
> 
> I didn't submit a pull request since you're still on the version that 
> requires the original syntax, but thought I'd still share here in case it 
> helps when you do upgrade, or if others run into this issue as well.
> 
> https://github.com/MSU-Libraries/accession_slips 
> <https://github.com/MSU-Libraries/accession_slips>
> 
> Thanks again for helping us get this set up!
> 
> - Megan
> 
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  on behalf of James 
> Bullen 
> Sent: Thursday, April 21, 2022 8:13 PM
> To: Archivesspace Users Group 
> 
> Subject: Re: [Archivesspace_Users_Group] Sharing/previewing Accession Records
>  
> 
> Hi Megan,
> 
> Yep, thanks - I’ve now dealt with that one too.
> 
> 
> Cheers,
> James
> 
> 
>> On Apr 21, 2022, at 11:48 PM, Schanz, Megan > <mailto:schan...@msu.edu>> wrote:
>> 
>> Thanks, that did fix that error. The next one appears to be a similar issue; 
>> likely a dependency on the payments_module 
>> <https://urldefense.com/v3/__https://github.com/hudmol/payments_module__;!!HXCxUKc!hrp8dQdzPter6vNqdqUTFBxmh0AR7-sBuTSwlygdcAwGjpoTZR6G8oK8i9dZtXk$>.
>> 
>> I, [2022-04-21T09:44:25.024165 #60]  INFO -- :   Rendered 
>> /archivesspace/plugins/yale_accession_slips/frontend/views/accessions/_non_print_slip.fo.erb
>>  (49.5ms)
>> I, [2022-04-21T09:44:25.025783 #60]  INFO -- : Completed 500 Internal Server 
>> Error in 299ms
>> F, [2022-04-21T09:44:25.031882 #60] FATAL -- :   
>> F, [2022-04-21T09:44:25.032270 #60] FATAL -- : ActionView::Template::Error 
>> (undefined method `payment_summary' for #):
>> F, [2022-04-21T09:44:25.033019 #60] FATAL -- : 219:   
>> 220: 
>> 221:   <% end %>
>> 222:   <% if @accession.payment_summary %>
>> 223: 
>> 224:   PAYMENT SUMMARY
>> 225:   <% 
>> render_print_item(I18n.t("payment_summary.total_price"), 
>> @accession.payment_summary['total_price']) %>
>> 
>> 
>> 
>> - Megan
>>   
>> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> 
>> > <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> on behalf 
>> of Rush, Michael mailto:michael.r...@yale.edu>>
>> Sent: Wednesday, April 20, 2022 1:59 PM
>> To: Archivesspace Users Group 
>> > <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
>> Subject: Re: [Archivesspace_Users_Group] Sharing/previewing Accession Records
>>  
>> Excellent! 
>>  
>> Cheers James!
>>  
>> Mike
>>  
>> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> 
>> > <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> On Behalf 
>> Of James Bullen
>> Sent: Tuesday, April 19, 2022 7:49 PM
>> To: Archivesspace Users Group 
>> > <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
>> Subject: Re: [Archivesspace_Users_Group] Sharing/previewing Accession Records
>>  
>>  
>> Thanks Mike - I just pushed a commit that should fix the hard dependency on 
>> material_types:
>> https://github.com/hudmol/yale_accession_slips/commit/9dbd43b 
>> <https://urldefense.com/v3/__https://nam12.safelinks.protection.outlook.com/?url=https*3A

Re: [Archivesspace_Users_Group] Sharing/previewing Accession Records

[James Bullen]

Hi Megan,

Yep, thanks - I’ve now dealt with that one too.


Cheers,
James


> On Apr 21, 2022, at 11:48 PM, Schanz, Megan  wrote:
> 
> Thanks, that did fix that error. The next one appears to be a similar issue; 
> likely a dependency on the payments_module 
> <https://github.com/hudmol/payments_module>.
> 
> I, [2022-04-21T09:44:25.024165 #60]  INFO -- :   Rendered 
> /archivesspace/plugins/yale_accession_slips/frontend/views/accessions/_non_print_slip.fo.erb
>  (49.5ms)
> I, [2022-04-21T09:44:25.025783 #60]  INFO -- : Completed 500 Internal Server 
> Error in 299ms
> F, [2022-04-21T09:44:25.031882 #60] FATAL -- :   
> F, [2022-04-21T09:44:25.032270 #60] FATAL -- : ActionView::Template::Error 
> (undefined method `payment_summary' for #):
> F, [2022-04-21T09:44:25.033019 #60] FATAL -- : 219:   
> 220: 
> 221:   <% end %>
> 222:   <% if @accession.payment_summary %>
> 223: 
> 224:   PAYMENT SUMMARY
> 225:   <% 
> render_print_item(I18n.t("payment_summary.total_price"), 
> @accession.payment_summary['total_price']) %>
> 
> 
> 
> - Megan
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  on behalf of Rush, 
> Michael 
> Sent: Wednesday, April 20, 2022 1:59 PM
> To: Archivesspace Users Group 
> 
> Subject: Re: [Archivesspace_Users_Group] Sharing/previewing Accession Records
>  
> Excellent! 
>  
> Cheers James!
>  
> Mike
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  On Behalf Of James 
> Bullen
> Sent: Tuesday, April 19, 2022 7:49 PM
> To: Archivesspace Users Group 
> 
> Subject: Re: [Archivesspace_Users_Group] Sharing/previewing Accession Records
>  
>  
> Thanks Mike - I just pushed a commit that should fix the hard dependency on 
> material_types:
> https://github.com/hudmol/yale_accession_slips/commit/9dbd43b 
> <https://urldefense.com/v3/__https://nam12.safelinks.protection.outlook.com/?url=https*3A*2F*2Fgithub.com*2Fhudmol*2Fyale_accession_slips*2Fcommit*2F9dbd43b=05*7C01*7Cmichael.rush*40yale.edu*7C387b00eca62043dbc83608da225f3c47*7Cdd8cbebb21394df8b4114e3e87abeb5c*7C0*7C0*7C637860090288574289*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C=54tGB7akhR36o4weCPP30ZguuXEhok6eaBTAQ45MS4w*3D=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!HXCxUKc!lSHf4esGckJ5j5Ikx5C6BNSsgbHp5HMSlQsNR3YudNtoE1l1-0KqWU91Qz55RKU$>
>  
> I haven’t tested it, but it should be fine ;)
>  
>  
>  
> Cheers,
> James
>  
> 
> 
> On Apr 20, 2022, at 1:22 AM, Rush, Michael  <mailto:michael.r...@yale.edu>> wrote:
>  
> From the error log it seems that our print accession record plugin is 
> dependent on the material types plugin 
> <https://urldefense.com/v3/__https://nam12.safelinks.protection.outlook.com/?url=https*3A*2F*2Fgithub.com*2Fhudmol*2Fmaterial_types=05*7C01*7Cmichael.rush*40yale.edu*7C387b00eca62043dbc83608da225f3c47*7Cdd8cbebb21394df8b4114e3e87abeb5c*7C0*7C0*7C637860090288574289*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C=qcOo8tASJNEF7QmRvARRIheGlfP0V2FTzC7uwBhpids*3D=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUl!!HXCxUKc!lSHf4esGckJ5j5Ikx5C6BNSsgbHp5HMSlQsNR3YudNtoE1l1-0KqWU91qvqNdG0$>
>  HM also developed for us. So I don’t think it’s a problem with the ASpace 
> version, rather the mutual dependency between our plugins.
>  
> If you are comfortable forking and mucking about in the code, It probably 
> wouldn’t been too hard to remove the references to that plugin.
>  
> Mike
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>  <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> On Behalf 
> Of Schanz, Megan
> Sent: Tuesday, April 19, 2022 11:11 AM
> To: Archivesspace Users Group 
>  <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: Re: [Archivesspace_Users_Group] Sharing/previewing Accession Records
>  
> Hi all,
>  
> We just tested the plugin with v3.1.1 and it doesn't appear to be compatible 
> with that version. This is the error that was logged:
>  
> I, [2022-04-19T11:06:07.887728 #60]  INFO -- :   Rendered 
> /archivesspace/plugins/yale_accession_slips/frontend/views/accessions/_non_print_slip.fo.erb
>  (21.5ms)
> I, [2022-04-19T11:06:07.889132 #60]  INFO -- : Completed 500 Internal Server 
> Error in 292ms
> F, [2022-04-19T11:06:07.890814 #60] FATAL -- :  
> F, [2022-04-19T11:06:07.890989 #60] FATAL -- : ActionView::Template::Error 
> (undefined method `material_types' for #):
> F, [2022-04-19T11:06:07.8

Re: [Archivesspace_Users_Group] Sharing/previewing Accession Records

[James Bullen]

Thanks Mike - I just pushed a commit that should fix the hard dependency on 
material_types:
https://github.com/hudmol/yale_accession_slips/commit/9dbd43b

I haven’t tested it, but it should be fine ;)



Cheers,
James


> On Apr 20, 2022, at 1:22 AM, Rush, Michael  wrote:
> 
> From the error log it seems that our print accession record plugin is 
> dependent on the material types plugin 
>  HM also developed for us. So I 
> don’t think it’s a problem with the ASpace version, rather the mutual 
> dependency between our plugins.
>  
> If you are comfortable forking and mucking about in the code, It probably 
> wouldn’t been too hard to remove the references to that plugin.
>  
> Mike
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  On Behalf Of 
> Schanz, Megan
> Sent: Tuesday, April 19, 2022 11:11 AM
> To: Archivesspace Users Group 
> 
> Subject: Re: [Archivesspace_Users_Group] Sharing/previewing Accession Records
>  
> Hi all,
>  
> We just tested the plugin with v3.1.1 and it doesn't appear to be compatible 
> with that version. This is the error that was logged:
>  
> I, [2022-04-19T11:06:07.887728 #60]  INFO -- :   Rendered 
> /archivesspace/plugins/yale_accession_slips/frontend/views/accessions/_non_print_slip.fo.erb
>  (21.5ms)
> I, [2022-04-19T11:06:07.889132 #60]  INFO -- : Completed 500 Internal Server 
> Error in 292ms
> F, [2022-04-19T11:06:07.890814 #60] FATAL -- :  
> F, [2022-04-19T11:06:07.890989 #60] FATAL -- : ActionView::Template::Error 
> (undefined method `material_types' for #):
> F, [2022-04-19T11:06:07.891767 #60] FATAL -- : 206:   <% end %>
> 207: 
> 208:   <% end %>
> 209:   <% if @accession.material_types %>
> 210: 
> 211:   MATERIAL TYPES
> 212:   
> F, [2022-04-19T11:06:07.891879 #60] FATAL -- :  
> F, [2022-04-19T11:06:07.892240 #60] FATAL -- : 
> app/controllers/application_controller.rb:797:in `set_locale'
> 
> 
> 
> 
> 
> 
> - Megan
> 
> 
> 
> 
>  
> _
>  
> Megan Schanz
> Application Developer & Systems Administrator
> Michigan State University Libraries
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  
>  > on behalf 
> of Busch, Ed mailto:busch...@msu.edu>>
> Sent: Tuesday, April 19, 2022 10:54 AM
> To: Archivesspace Users Group 
>  >
> Subject: Re: [Archivesspace_Users_Group] Sharing/previewing Accession Records
>  
> Well, darn, something broke in it. Apparently not tested with newer versions 
> of ASpace. What version are we on? Can you see if anything popped up in the 
> log? It added a “Print Accession Record” button under More in the Accession 
> functions.
>  
> The author wanted to know if it worked so I might as well share the debug if 
> any.
>  
> Thanks!
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  
>  > On Behalf 
> Of Rush, Michael
> Sent: Tuesday, April 19, 2022 8:36 AM
> To: Archivesspace Users Group 
>  >
> Subject: Re: [Archivesspace_Users_Group] Sharing/previewing Accession Records
>  
> Hi Bri,
>  
> We have a similar use case at Yale. We often print our accession records to 
> accompany new acquisitions through the processing and cataloging workflow. In 
> order to save paper and print out reasonably formatted copies of accession 
> records we contracted with Hudson Molonglo to develop a plugin. See 
> https://github.com/hudmol/yale_accession_slips 
> .
>  
>  
> The plugin adds a “Print accession record” option under the “More” menu in 
> the accession record view. This creates a PDF of the accession record.
>  
> We make use of a number of user-defined fields in our accession records, and 
> the layout of the PDF incorporates those, so this plugin might not work 
> perfectly for your local implementation. But you could give it a try, or fork 
> it and tweak it to meet your needs.
>  
> Best,
>  
> Mike
> 
> Michael Rush
> Assistant Head of the Manuscript Unit
> Beinecke Rare Book and Manuscript Library
> Yale University

Re: [Archivesspace_Users_Group] Location/Container Profile Questions

[James Bullen]

Hi David,

Space calculations are based on container profiles and location profiles.

I think the only way to handle modular location profiles would be to create a 
new profile for each shelf configuration in use. Not ideal, but the space 
calculator was not designed with this requirement in mind.

We did this work over five years ago so others may have more current knowledge, 
but a quick check suggests that this remains the case.


Cheers,
James



> On Dec 9, 2021, at 7:54 AM, Mendoza, David  wrote:
> 
> Hi All, I have a multipart question, apologies for any cross posts.  New to 
> the forum, so excuse the length of the questions.
>  
> Regarding linear footage, are calculations in ArchivesSpace based on Location 
> or Container profile entries?  And how does this affect location profiles 
> that are modular?  I.e., we have filing units where shelves can be added or 
> taken away.  If linear footage is based on location profiles, how would the 
> addition or subtraction of shelves, or a change in the stacking limit, be 
> dealt with in location profiles? 
>  
> Thanks
> This message, and any attachments, is for the intended recipient(s) only, may 
> contain information that is privileged, confidential and/or proprietary and 
> subject to important terms and conditions available at 
> http://www.bankofamerica.com/emaildisclaimer 
> . If you are not the intended 
> recipient, please delete this message.
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Error setting parent of Archival Object via API

[James Bullen]

Hi again Tommy,

It looks like this ends up at this line:
https://github.com/archivesspace/archivesspace/blob/master/backend/app/model/mixins/tree_nodes.rb#L63
 
<https://github.com/archivesspace/archivesspace/blob/master/backend/app/model/mixins/tree_nodes.rb#L63>

Where, if you give it a large value for position (ie more than the maximum 
number of siblings you would expect in your data) it will end up being the last 
in the list.

It wouldn’t be too much work for someone to honor the optional position 
declaration in the endpoint and trace it down to here where it would default to 
siblings_count - 1. That is, if you don’t specify a position it gets added to 
the end - seems like a reasonable default behavior.


Cheers,
James


> On Aug 25, 2021, at 2:02 AM, Keswick, Thomas (Tommy)  
> wrote:
> 
> Thanks, James. Adding the position parameter does seem to work.
> 
> Does anyone know of a way to add an item to the end of the children list 
> without having to count the number of existing children? Using -1 (negative 
> one) does not work as “Offsets must be greater than or equal to 0”.
> 
> Cheers,
> Tommy
> 
>> On Aug 23, 2021, at 5:46 PM, James Bullen > <mailto:ja...@hudmol.com>> wrote:
>> 
>> 
>> Hi Tommy,
>> 
>> I’m ready to be wrong on this, but just had a quick look and it seems like 
>> the position param is required even though the endpoint declares it as 
>> optional.
>> 
>> 
>> Cheers,
>> James
>> 
>> 
>>> On Aug 24, 2021, at 9:30 AM, Keswick, Thomas (Tommy) >> <mailto:tkesw...@caltech.edu>> wrote:
>>> 
>>> Greetings.
>>> 
>>> I’m trying to use the Set the parent/position of an Archival Object in a 
>>> tree 
>>> <https://archivesspace.github.io/archivesspace/api/#set-the-parent-position-of-an-archival-object-in-a-tree>
>>>  API endpoint but I am getting an error when I supply both the archival 
>>> object ID and the parent ID in what should be the correct way. The Archival 
>>> Object is an item-level record and the parent is a series-level record, 
>>> both under the same Resource.
>>> 
>>> The error is:
>>> {
>>> "error": "comparison of Integer with nil failed"
>>> }
>>> 
>>> Here is some sample Python code that fails:
>>> ```
>>> import json
>>> 
>>> from asnake.client import ASnakeClient
>>> 
>>> asnake_client = ASnakeClient()
>>> asnake_client.authorize()
>>> 
>>> parent_post_response = asnake_client.post(
>>> "/repositories/2/archival_objects/96413/parent?parent=96414"
>>> )
>>> print(json.dumps(parent_post_response.json(), sort_keys=True, indent=4))
>>> ```
>>> 
>>> The locally installed ArchivesSpace version that I am testing on is 2.8.1 
>>> currently.
>>> 
>>> Thanks for any help.
>>> 
>>> Cheers,
>>> Tommy
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Error setting parent of Archival Object via API

[James Bullen]

Hi Tommy,

I’m ready to be wrong on this, but just had a quick look and it seems like the 
position param is required even though the endpoint declares it as optional.


Cheers,
James


> On Aug 24, 2021, at 9:30 AM, Keswick, Thomas (Tommy)  
> wrote:
> 
> Greetings.
> 
> I’m trying to use the Set the parent/position of an Archival Object in a tree 
> 
>  API endpoint but I am getting an error when I supply both the archival 
> object ID and the parent ID in what should be the correct way. The Archival 
> Object is an item-level record and the parent is a series-level record, both 
> under the same Resource.
> 
> The error is:
> {
> "error": "comparison of Integer with nil failed"
> }
> 
> Here is some sample Python code that fails:
> ```
> import json
> 
> from asnake.client import ASnakeClient
> 
> asnake_client = ASnakeClient()
> asnake_client.authorize()
> 
> parent_post_response = asnake_client.post(
> "/repositories/2/archival_objects/96413/parent?parent=96414"
> )
> print(json.dumps(parent_post_response.json(), sort_keys=True, indent=4))
> ```
> 
> The locally installed ArchivesSpace version that I am testing on is 2.8.1 
> currently.
> 
> Thanks for any help.
> 
> Cheers,
> Tommy
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Hudson Molonglo: Extended Advanced Search Plugin NoMethodError

[James Bullen]

Thanks Joshua - I just pushed out a release from the current master:
https://github.com/hudmol/extended_advanced_search/releases/tag/v1.0 



Cheers,
James



> On Aug 6, 2021, at 4:02 AM, Corinne Chatnik  wrote:
> 
> Thank you! This helps a lot.
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  On Behalf Of Joshua 
> D. Shaw
> Sent: Thursday, August 5, 2021 1:58 PM
> To: Archivesspace Users Group 
> 
> Subject: Re: [Archivesspace_Users_Group] Hudson Molonglo: Extended Advanced 
> Search Plugin NoMethodError
>  
> The release package looks like it was created before the class name change 
> from CommonIndexer to IndexerCommon. That name change was for AS v2.2.2+, so 
> the release won't work with 2.7.0. You could try cloning the master branch of 
> the repo, though that may also flail with 2.7.0. And I'd definitely test it 
> against test data, *not* production.
>  
> jds
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  
>  > on behalf 
> of Corinne Chatnik  >
> Sent: Thursday, August 5, 2021 1:46 PM
> To: archivesspace_users_group@lyralists.lyrasis.org 
>  
>  >
> Subject: [Archivesspace_Users_Group] Hudson Molonglo: Extended Advanced 
> Search Plugin NoMethodError
>  
> Hi,
>  
> I’m trying to implement Release 0.6 of the Extended Advanced search plugin 
> with Archivesspace 2.7.0 and I get the NoMethodError: undefined method no 
> matter what I do. I’ve followed all installation instructions on this page: 
> https://github.com/hudmol/extended_advanced_search 
> .
>  
>  
> Using the exact source code from github I get the following error in the log:
> --- Backtrace
> NoMethodError: undefined method `add_attribute_to_resolve' for 
> CommonIndexer:Class
>  method_missing at org/jruby/RubyBasicObject.java:1657
>at 
> archivesspace/plugins/extended_advanced_search/indexer/common_indexer.rb:5
>   at 
> archivesspace/plugins/extended_advanced_search/indexer/common_indexer.rb:3
>  
> Am I missing necessary data in the database or something in the code?
>  
> Thanks!
>  
> Corinne Chatnik
> New York State Archives
> corinne.chat...@nysed.gov 
>  
> 
> Confidentiality Notice
> This email including all attachments is confidential and intended solely for 
> the use of the individual or entity to which it is addressed. This 
> communication may contain information that is protected from disclosure under 
> State and/or Federal law. Please notify the sender immediately if you have 
> received this communication in error and delete this email from your system. 
> If you are not the intended recipient you are notified that disclosing, 
> copying, distributing or taking any action in reliance on the contents of 
> this information is strictly prohibited.
> 
>  
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Spreadsheet imports locking up database

[James Bullen]

Hi Peter,

I’m not familiar with the spreadsheet importer, but it sounds like you’ve done 
the analysis to be in a position to fix it. :)

Here’s a commit for the “run tonight” feature implemented in a plugin:
https://gitlab.gaiaresources.com.au/qsa/as_runcorn/-/commit/8a2bd97 
<https://gitlab.gaiaresources.com.au/qsa/as_runcorn/-/commit/8a2bd97>

It was refined in a few subsequent commits (4369dd0, 800ac1c, 5f1207e).


Cheers,
James


> On Jun 6, 2021, at 6:02 PM, Peter Heiner  wrote:
> 
> James Bullen wrote on 2021-06-06 11:35:03:
> 
>> Bulk update operations usually run in database transactions. This is great 
>> because it guarantees that the database will be in a consistent state when 
>> the job completes - if it succeeds then all of the updates are applied, if 
>> it fails then none of the updates are applied.
>> 
>> The price for this guarantee is that any affected records are locked until 
>> the job completes.
> 
> Thanks for your response. I generally agree with your points but have mine to 
> make.
> One is that the consistency unit here need not be the entire job, it is 
> sufficient to isolate a single line, and I would normally expect the database 
> to cope fine with such a workload.
> Secondly, if I read my database output correctly, in this case the problem is 
> not a wholly isolated bulk update but unnecessary table scans occurring for 
> each line that make the database hold a lock for several seconds instead of 
> milliseconds. I've yet to understand the purpose of the subnote_metadata 
> table and why the delete is taking place, but we did notice that the query 
> tried IDs that were not in the database.
> In any case, it should be possible to unroll the subquery or provide 
> optimiser hints for the bottleneck to go away.
> 
>> We recently implemented the ability to submit import jobs to be run after 
>> hours for a client to work around this.
> 
> We were thinking of a similar workaround, do you have anything you could 
> share with us?
> 
> Thanks,
> p
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Spreadsheet imports locking up database

[James Bullen]

Hi Peter and Nancy,

Bulk update operations usually run in database transactions. This is great 
because it guarantees that the database will be in a consistent state when the 
job completes - if it succeeds then all of the updates are applied, if it fails 
then none of the updates are applied.

The price for this guarantee is that any affected records are locked until the 
job completes.

We recently implemented the ability to submit import jobs to be run after hours 
for a client to work around this.

Ideally, there would be some indication in the UI that a record is locked 
(maybe hiding the edit button and a helpful message), but we haven’t 
investigated this.

Hope that helps.


Cheers,
James



> On Jun 5, 2021, at 1:43 AM, Kennedy, Nancy  wrote:
> 
> Hi Peter –
> We also see issues with concurrent database access.  If one user initiates a 
> large delete or import, other users can experience long delays and timeouts.  
> We’ve also noticed that Edit save times are especially long when there is a 
> language subrecord. (An archival_object with a lang_material can take 30 
> seconds to save, whereas records without a lang_material save much more 
> quickly).
>  
> We are in v 2.71 and we also use MariaDB. We see the same issue in our test 
> 2.8.1 instance. I’d be very interested to hear if MySQL offers a better 
> experience for Cambridge,
>  
> Thanks, 
> Nancy
>  
> kenne...@si.edu 
> Nancy Kennedy
> Smithsonian Institution
>  
>  
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  
>  > On Behalf 
> Of Peter Heiner
> Sent: Friday, June 4, 2021 11:20 AM
> To: archivesspace_users_group@lyralists.lyrasis.org 
> 
> Subject: [Archivesspace_Users_Group] Spreadsheet imports locking up database
>  
> External Email - Exercise Caution
> Dear list users,
>  
> The Cambridge University Library AS instance has recently been hit with 
> severe performance issues while users were running spreadsheet imports to add 
> archival objects, details are in 
> https://github.com/archivesspace/archivesspace/issues/2275 
> ;
>  the summary is that a DELETE query with a dependent subquery running for 
> every line of the spreadsheet input seems to make concurrent database access 
> near impossible.
>  
> Has anyone else experienced anything similar? Us using MariaDB instead of 
> MySQL might well be the cause, but I'd like confirmation before work is 
> scheduled to migrate the database that this will indeed help. If you're using 
> spreadsheet imports, we'd be grateful if you could let us know either on or 
> off list whether you use MySQL or MariaDB and if you had any problems with 
> the migration queries hogging the database.
>  
> Thanks,
> p
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Disappeared Accession Record

[James Bullen]

Hi Katie,

That looks suspiciously like a bug I’ve seen on v2.8.1 - not sure if it 
afflicts any earlier versions. I assume it has been noted elsewhere and 
documented because it’s pretty nasty.

If an accession has an instance with a linked top container, its json looks 
like this:

"top_container":
{
  "ref":
  [
"SubContainer",
"TopContainer"
  ]
}

That ref value should be the uri of the top container (not an array of strings 
- classnames?). When the indexer retrieves such an accession it tries to 
resolve the top container and blows up because it is not expecting an array.

The test would be to remove the instance and see if it re-appears in search 
results.

I assume this will be fixed in the next release.


Cheers,
James



> On Mar 23, 2021, at 7:51 AM, Katie Nash  wrote:
> 
> Hello colleagues,
> 
> We've been creating accession records for several years now, and had the 
> strangest thing happen recently. We created an accession record, added an 
> instance, and saved it. When we went to search for it using the identifier, 
> we received a message that "No Records Found", and the same thing happened 
> when we searched the barcode for the top container. When we tried to create a 
> new accession record using the same identifier, the system said the 
> identifier is already in use. We've been unable to locate this accession 
> record! Any idea where it could be hiding? I've been using ASpace for several 
> years and never had this happen, so I'm at a loss. 
> 
> Thanks for any guidance! Worst case scenario we simply create a new accession 
> record (for this one box collection!) with a new identifier. 
> 
> Best wishes,
> Katie 
> 
> Katie Nash | University Archivist and Head of UW Archives
> University of Wisconsin-Madison Libraries
> 425 Steenbock Library | 550 Babcock Dr.
> Madison, WI 53706
> 1-608-265-1988 
> Pronouns: she/her/hers 
> Tell us your COVID-19 story! 
> 
>  
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3

[James Bullen]

Many thanks Megan for the lead. I just poked around and found a few things out.

It turns out to be interesting in at least three bad ways.

1.  User records are updated every time they authenticate. This is unnecessary 
because it is just updating their authentication source, which usually never 
changes. So this line could be made conditional on the source being different:

https://github.com/archivesspace/archivesspace/blob/master/backend/app/model/authentication_manager.rb#L40

2.  The search_indexer user is being re-authenticated a lot. This shouldn’t 
happen because it should be a non-expiring session. I haven’t looked into this 
one, but I did check the lock_version on the search_inxdexer user on a 
large-ish AS db I have lying around, that has been in production for less than 
a year and it is over 100,000. That’s nuts. Actually I just took a quick look 
and saw this:

https://github.com/archivesspace/archivesspace/blob/master/indexer/app/lib/periodic_indexer.rb#L285
The session is reset if there is an error during an indexing round. So that 
could be the culprit.

3.  There is clearly a bug somewhere in the stack, probably in the Sequel 
layer, because it shouldn’t crash the system just because you have a whacky 
datetime somewhere. This bug may well have been fixed in a more recent version 
of that component.


Dealing with 1 will likely fix the problem, but 2 and 3 should also be 
investigated.


Cheers,
James



> On Mar 16, 2021, at 1:24 AM, Tom Hanstra  wrote:
> 
> Thanks, Megan. That update did fix things.
> 
> So, is this not something that can be addressed at the software fix level? Do 
> other sites simply stop indexing or turn something else off when we hit DST 
> in March?
> 
> Tom
> 
> On Mon, Mar 15, 2021 at 10:12 AM Schanz, Megan  <mailto:schan...@msu.edu>> wrote:
> I run across this every March for daylight savings. This is what I have in my 
> notes to do each time if the indexer is running. Luckily it seems like I 
> didn't have this scenario this year.
> 
> java.lang.IllegalArgumentException: HOUR_OF_DAY: 2 -> 
> 3:Java::JavaLang::IllegalArgumentException:
> 
> This error will appear in the logs when trying to start ArchivesSpace after 
> daylight savings time. 
> Reference:http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2019-March/006652.html
>  
> <http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2019-March/006652.html>
> Basically, the indexer user is being updated in the database with a time that 
> does not exist due to daylight savings time.
> 
> To verify:
> 
> SELECT * FROM user WHERE (user_mtime >= '2021-03-14 02:00:00' and user_mtime 
> <= '2021-03-14 03:00:00') OR (system_mtime >= '2021-03-04 02:00:00' and 
> system_mtime <= '2021-03-14 03:00:00');
> The record that should come back is the search_indexer user.
> 
> To resolve:
> 
> UPDATE user set user_mtime = NOW(), system_mtime=NOW() where 
> username='search_indexer';
> 
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> 
>  <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> on behalf 
> of Tom Hanstra mailto:hans...@nd.edu>>
> Sent: Monday, March 15, 2021 9:10 AM
> To: Archivesspace Users Group 
>  <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: Re: [Archivesspace_Users_Group] Java error - 
> Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3
>  
> Any suggestion on what ArchivesSpace might have changed?  I had the server 
> running but indexing was complete. What might it have been changing and in 
> what database table would I look for that change?
> 
> Alternately, since this is still test data, should I just overlay a backup 
> copy of the database from earlier than the EDT cutover time?  I don't know 
> what affect that might have on other portions of ArchivesSpace.
> 
> Finally, what is the overall fix for this issue. If others have seen it, what 
> can be done to make sure to avoid it in the future?
> 
> Thanks,
> Tom
> 
> On Mon, Mar 15, 2021 at 9:03 AM Blake Carver  <mailto:blake.car...@lyrasis.org>> wrote:
> https://gist.github.com/Blake-/d493da28be5554a49a3a3835bbd98f05 
> <https://urldefense.com/v3/__https://gist.github.com/Blake-/d493da28be5554a49a3a3835bbd98f05__;!!HXCxUKc!lsrL41tXx-WGwpdlFWm60sfuIbz0DRfuyn4RvaCAka7R1eaKVNkWL7PbhWHEm8g$>
> 
> You'll want to find the date more like '2021-03-14 02:00%' or would it be 
> 03-13? Whatever the date was this year.
> Find any date with a time between 2-3am and just change it to any real hour.
> ArchivesSpace did "something" (probably restarted?) at a bad time on Sunday 
> morning and wrot

Re: [Archivesspace_Users_Group] Java error - Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3

[James Bullen]

Oh gee, I’ve seen that horror. And, yes, it is caused by records having times 
in that non-existent hour. From memory the only fix I could find was to delete 
the offending rows, or update their times.


Cheers,
James



> On Mar 15, 2021, at 1:59 PM, Tom Hanstra  wrote:
> 
> I don't seem to be able to win with ArchivesSpace.
> 
> After having indexing again finally give up because of another Java heap 
> error, I restarted archivesspace again with some different java settings. I 
> believe it actually got through the indexing, at least of the first 
> repository.
> 
> But tonight, looking at the logs, there is another error that seems to have 
> something to do with, perhaps, daylight savings time?  I'm seeing this Java 
> error in the logs, even after a restart:
> 
> 
> INFO: An exception happened during JRuby-Rack startup
> Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3
> --- System
> jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 
> 25.272-b10 on 1.8.0_272-b10 +jit [linux-x86_64]
> Time: 2021-03-14 22:46:48 -0400
> Server: jetty/8.1.5.v20120716
> jruby.home: uri:classloader://META-INF/jruby.home
> 
> --- Context Init Parameters:
> jruby.max.runtimes = 1
> jruby.min.runtimes = 1
> public.root = /
> rack.env = production
> 
> --- Backtrace
> Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 2 -> 3
> 
> 
> 
> Did something get corrupted in the database?  What might be happening to 
> result in this error?
> How do I fix it?
> 
> Thanks,
> Tom
> 
> -- 
> Tom Hanstra
> Sr. Systems Administrator
> hans...@nd.edu 
> 
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Local plugin disabled and aspace_diagnostic not present

[James Bullen]

Hi David,

Not sure what’s going on, but a few points to note:

-  The absence of an aspace_diagnostic file is a good sign because it only gets 
written if something goes wrong during start up.
-  There is no need to run 'initialize-plugin.sh local' unless you are using 
gems in your local plugin. That message is just noting that there is no 
plugins/local/Gemfile, so there is nothing to do.
-  Check that you have ‘local’ in AppConfig[:plugins].
-  You mention ‘plugin/local/…’, I guess this is a typo, but make sure the 
directory is ‘plugins/local/…'
-  From memory, that gear icon only appears if you have a plugin that has a 
config.yml that specifies a menu item.


Cheers,
James



> On Feb 20, 2021, at 4:11 AM, Tenenholtz, David  wrote:
> 
> Hello!
>  
> I’m standing up the v.2.8.1 release in production, and am running into a 
> persistent issue that keeps the local plugin from being enabled. I have not 
> been able to identify if this is related to the prior bug in older releases 
> having to do with the gem bundler, but I suspect that a gem (or the bundler?) 
> is being blocked here. Although I have the same content in 
> plugin/local/frontend and plugin/local/public running happily on a test 
> server on matching infrastructure, I’m not having any luck getting the local 
> plugin to initialize on prod. Under /data/tmp there is also no 
> aspace_diagnostic text file to interrogate. In the staff GUI I’m not seeing 
> the Plug-ins list item within the dropdown under the gear icon.
>  
> Tech specs (matching on test server and production server):
> RHEL7.9 VM
> openjdk 1.8.0_282
> mysql Ver 15.1 distrib 5.5.68-MariaDB
> Apache/2.4.6
>  
> During the building of the production application, I noticed the issue, and 
> so I ran ‘initialize-plugin.sh local’ from within the scripts folder, but got 
> an error related to a Gemfile not being present within the ‘local’ folder.
>  
> If anyone has any pointers on how to get the aspace_diagnostic to generate 
> under /data/tmp, or any other avenues for me to pursue here with initializing 
> the local plugin properly, I’d be so grateful!
>  
> Kind regards,
> David
>  
> --
> David Tenenholtz (he/him)
> Digital Archivist, RAND Corporation
> 1776 Main Street
> P.O. Box 2138
> Santa Monica, CA 90407-2138
> (310) 393-0411 x6188
> dtene...@rand.org 
>  
>  
>  
>  
> 
> __
> 
> This email message is for the sole use of the intended recipient(s) and
> may contain information that is sensitive, proprietary, and/or privileged.
> Any unauthorized review, use, disclosure or distribution is prohibited. If
> you are not the intended recipient, please contact the sender by reply
> email and destroy all copies of the original message.
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Indexer Thread Counts

[James Bullen]

Hi Joshua,

1) Yes, additive
2) The public index was considered less time critical

There’s no problem with increasing the PUI indexer thread count if you have the 
resources.


Cheers,
James


> On Jan 6, 2021, at 1:41 AM, Joshua D. Shaw  
> wrote:
> 
> Hey all-
> 
> Couple of questions about indexer thread counts
> 
> 1) Before I dive too deeply into the code to figure this out, I'm wondering 
> if anyone knows if the setting for AppConfig[:pui_indexer_thread_count] is 
> counted as part of AppConfig[:indexer_thread_count] or if its additive? IE if 
> the stock config setting amounts to 5 threads (4+1) or 4 threads.
> 
> 2) Is there a reason that the PUI indexer thread count is set so much lower 
> than the staff side?
> 
> I'm thinking of upping the PUI thread count to something closer to the staff 
> side since we have the cores to support that, but I'm wondering if there 
> might be some unforeseen negative side effects.
> 
> Thanks!
> Joshua
> 
> ___
> Joshua Shaw (he, him)
> Technology Coordinator
> Rauner Special Collections Library & Digital Library Technologies Group
> Dartmouth College
> 603.646.0405
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] help with API route for archival object notes

[James Bullen]

Hi Karen,

No worries. Chris’ help was more to the point anyway ;)

From your example, you should be able to reference the content with the bad tag 
like this:

[’notes’][0][‘content’][0]


Cheers,
James


> On Jul 2, 2020, at 1:23 AM, Karen Miller  wrote:
> 
> Hello, James.
>  
> Sorry, I just realized I addressed you as Chris instead of as James! My 
> apologies! I was so thrilled to get some assistance that I skimmed through 
> the signatures too quickly.
>  
> Best,
> Karen
>  
> From: Karen Miller 
> Sent: Wednesday, July 01, 2020 9:50 AM
> To: 'Archivesspace Users Group' 
>  <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: RE: [Archivesspace_Users_Group] help with API route for archival 
> object notes
>  
> Hi Chris.
>  
> I’ve been able to successfully retrieve & update nested elements from the 
> Agent record, just not from the archival object notes record. But your 
> description of them as “repeating parts” of that record is helpful. Thanks!
>  
> Karen
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> 
>  <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> On Behalf 
> Of James Bullen
> Sent: Tuesday, June 30, 2020 6:35 PM
> To: Archivesspace Users Group 
>  <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: Re: [Archivesspace_Users_Group] help with API route for archival 
> object notes
>  
>  
> Hi Karen,
>  
> The general rule is that anything you can GET from a uri can be modified and 
> POSTed back to update it.
>  
> So, GET the JSON for the archival_object as you are doing. Then modify the 
> JSON (in this case the notes bit of it) to look how you want. Then POST it 
> back to the same uri.
>  
> Notes are nested subrecords (as are dates and others). These don’t have a 
> life of their own, they are really just repeating parts of the top level 
> record that they are contained within.
>  
> Hope that helps..
>  
>  
> Cheers,
> James
>  
>  
> 
> On Jul 1, 2020, at 8:22 AM, Karen Miller  <mailto:k-mill...@northwestern.edu>> wrote:
>  
> Good morning, ArchivesSpace users.
>  
> I am a cataloger (*not* a developer) using the API to update ArchivesSpace. 
> So far I’ve figured out how to add LCCNs to the authority_Id of Agent records 
> and do a couple more updates that, in retrospect, were pretty simple. 
>  
> The next task I’d like to tackle, however, just seems like maybe it can’t be 
> done. We’ve got a lot of notes with html tags in them and I would like to 
> update those to valid tags. I can get the JSON for the notes in any 
> particular archival object, but I don’t know how to specify the route to the 
> note to change it. The JSON looks like this:
>  
> 'notes': [{'content': ['This is a note with a bad tag'],
> 'jsonmodel_type': 'note_singlepart',
> 'persistent_id': '75ba0ec57e374b8b154551a69b4c311f',
> 'publish': True,
> 'type': 'abstract'},
>{'jsonmodel_type': 'note_multipart',
> 'persistent_id': '66afa07b3214260078123236bbe1ff27',
> 'publish': True,
> 'subnotes': [{'content': 'This is a dippy note.',
>   'jsonmodel_type': 'note_text',
>   'publish': True}],
> 'type': 'scopecontent'}],
>  
> I got this using the route ‘repositories/10/archival_objects/489763’, but I 
> don’t know how to specify the note that I want in the JSON. For the agent 
> authority_id I used the route ‘‘/agents/people/ and specified the 
> field like this:
>  
> ['names'][0]['authority_id']
>  
> I’m hoping this is an easy question for somebody with more experience with 
> the API and (especially) with JSON than I. I’m a little afraid the answer is 
> that it can’t be done. Any advice will be appreciated! 
>  
> Karen
>  
> Karen D. Miller
> Monographic Cataloger/Metadata Specialist
> Northwestern University Libraries
> Northwestern University
> 1970 Campus Drive
> Evanston, IL 60208
> www.library.northwestern.edu <http://www.library.northwestern.edu/>
> k-mill...@northwestern.edu <mailto:k-mill...@northwestern.edu>
> 874.467.3462
>  
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> <mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> <https://urldefense.com/v3/__http:/lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!D

Re: [Archivesspace_Users_Group] help with API route for archival object notes

[James Bullen]

Hi Karen,

The general rule is that anything you can GET from a uri can be modified and 
POSTed back to update it.

So, GET the JSON for the archival_object as you are doing. Then modify the JSON 
(in this case the notes bit of it) to look how you want. Then POST it back to 
the same uri.

Notes are nested subrecords (as are dates and others). These don’t have a life 
of their own, they are really just repeating parts of the top level record that 
they are contained within.

Hope that helps..


Cheers,
James


> On Jul 1, 2020, at 8:22 AM, Karen Miller  wrote:
> 
> Good morning, ArchivesSpace users.
>  
> I am a cataloger (*not* a developer) using the API to update ArchivesSpace. 
> So far I’ve figured out how to add LCCNs to the authority_Id of Agent records 
> and do a couple more updates that, in retrospect, were pretty simple. 
>  
> The next task I’d like to tackle, however, just seems like maybe it can’t be 
> done. We’ve got a lot of notes with html tags in them and I would like to 
> update those to valid tags. I can get the JSON for the notes in any 
> particular archival object, but I don’t know how to specify the route to the 
> note to change it. The JSON looks like this:
>  
> 'notes': [{'content': ['This is a note with a bad tag'],
> 'jsonmodel_type': 'note_singlepart',
> 'persistent_id': '75ba0ec57e374b8b154551a69b4c311f',
> 'publish': True,
> 'type': 'abstract'},
>{'jsonmodel_type': 'note_multipart',
> 'persistent_id': '66afa07b3214260078123236bbe1ff27',
> 'publish': True,
> 'subnotes': [{'content': 'This is a dippy note.',
>   'jsonmodel_type': 'note_text',
>   'publish': True}],
> 'type': 'scopecontent'}],
>  
> I got this using the route ‘repositories/10/archival_objects/489763’, but I 
> don’t know how to specify the note that I want in the JSON. For the agent 
> authority_id I used the route ‘‘/agents/people/ and specified the 
> field like this:
>  
> ['names'][0]['authority_id']
>  
> I’m hoping this is an easy question for somebody with more experience with 
> the API and (especially) with JSON than I. I’m a little afraid the answer is 
> that it can’t be done. Any advice will be appreciated! 
>  
> Karen
>  
> Karen D. Miller
> Monographic Cataloger/Metadata Specialist
> Northwestern University Libraries
> Northwestern University
> 1970 Campus Drive
> Evanston, IL 60208
> www.library.northwestern.edu 
> k-mill...@northwestern.edu 
> 874.467.3462
>  
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Error updating resource records through API

[James Bullen]

You can just send back the lock_version you got with the get. No need to bump 
it - that happens on a successful update. The response to the update will 
include the new lock_version, like this:

{
  "status": "Updated",
  "id": 2,
  "lock_version": 23,
  "stale": NULL,
  "uri": "/repositories/2",
  "warnings": []
}

This is implemented via a sequel plugin:
https://sequel.jeremyevans.net/rdoc-plugins/classes/Sequel/Plugins/OptimisticLocking.html



> On Apr 18, 2020, at 12:53 AM, Peter Heiner  wrote:
> 
> Huebschen, Alan M wrote on 2020-04-17 14:26:24:
>> I've been attempting to update existing resource records through the API, 
>> the records already exist and I'm trying to upload modified versions of the 
>> JSON but I'm getting an error in response.
>> 
>> 'error': 'The record you tried to update has been modified since you fetched 
>> it.'
> 
> To update a record, you first need to fetch it to get its lock_version.
> The API will only allow updates to a resource with a lock_version
> greater than the one stored in the database, so you'll need to post your
> data including lock_version+1.
> 
> Hope that helps,
> p
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> !DSPAM:5e99c2e335501411550710!

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Odd data modifications during aspace updates.

[James Bullen]

Hi Don,

Nested subrecords get recreated on every update. They arguably shouldn’t have 
those audit fields.


Cheers,
James


> On Mar 11, 2020, at 8:45 AM, Donald Mennerich  wrote:
> 
> Hello, 
> 
> While testing a script that was updating a resource's ead_id via the api I 
> noticed that the timestamps for  most sub-records of the resource, e.g. 
> instances, extents, langmaterials, etc., that wern't part of the update were 
> havign their timesstamps, includeing create_time and created_by, updated as 
> well. I naturally assumed there was something wrong with my code, but when we 
> tested updating a resource record from the staff interface the same thing 
> happening was observed. 
> 
> For example, the fields belonging to the Resource model updated as expected, 
> the creation_time and created_by were not modified, while the 
> last_modified_by and mtimes were:
> 
> Before
> {
>   "lock_version": 1,
>   "title": "Test Collection",
>   "publish": true,
>   "restrictions": false,
>   "created_by": "admin",
>   "last_modified_by": "user1",
>   "create_time": "2016-07-14T23:50:37Z",
>   "system_mtime": "2018-03-29T22:05:59Z",
>   "user_mtime": "2017-02-02T18:15:58Z",
>  ...
> 
> After
> {
>   "lock_version": 2,
>   "title": "Test Collection",
>   "publish": true,
>   "restrictions": false,
>   "ead_id": "test_999",
>   "created_by": "admin",
>   "last_modified_by": "user2",
>   "create_time": "2016-07-14T23:50:37Z",
>   "system_mtime": "2020-03-10T17:29:46Z",
>   "user_mtime": "2020-03-10T17:29:46Z",
> ...
> 
> 
> But in most of the subrecords of the resource the timestamps have all updated 
> to the time of the update of the resource record. In this case the only thing 
> that was updated was in the resource record was the eadid, but the instance 
> subrecords had their timestamps updated even though not at all part of the 
> update. Note that while data was changed in the sub record the lock_version 
> is still at 0. Again, this was done with an update via the staff interface.
> 
> Before
> "instances": [
>   {
> "lock_version": 0,
> "created_by": "user1",
> "last_modified_by": "user1",
> "create_time": "2017-02-02T18:15:58Z",
> "system_mtime": "2017-02-02T18:15:58Z",
> "user_mtime": "2017-02-02T18:15:58Z",
> "instance_type": "mixed_materials",
> "jsonmodel_type": "instance",
> "is_representative": false,
> "sub_container": {
>   "lock_version": 0,
>   "created_by": "user1",
>   "last_modified_by": "user1",
>   "create_time": "2017-02-02T18:15:58Z",
>   "system_mtime": "2017-02-02T18:15:58Z",
>   "user_mtime": "2017-02-02T18:15:58Z",
>   "jsonmodel_type": "sub_container",
> 
> After
> "instances": [
>   {
> "lock_version": 0,
> "created_by": "user2",
> "last_modified_by": "user2",
> "create_time": "2020-03-10T17:29:47Z",
> "system_mtime": "2020-03-10T17:29:47Z",
> "user_mtime": "2020-03-10T17:29:47Z",
> "instance_type": "mixed_materials",
> "jsonmodel_type": "instance",
> "is_representative": false,
> "sub_container": {
>   "lock_version": 0,
>   "created_by": "user2",
>   "last_modified_by": "user2",,
>   "create_time": "2020-03-10T17:29:47Z",
>   "system_mtime": "2020-03-10T17:29:47Z",
>   "user_mtime": "2020-03-10T17:29:47Z",
>   "jsonmodel_type": "sub_container",
> 
> 
> I'm trying to determine if this is a local problem or if this is just 
> normally how aspace manages updates, and if so is it a bug. Would someone 
> with access to the API of their ArchivesSpace instance see if they could 
> reproduce this? I've tested this on installations of v2.7.0 and v2.7.1.
> 
> Thanks, 
> 
> Don
> !DSPAM:5e680a81236307999538416! 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> 
> !DSPAM:5e680a81236307999538416!

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Errors trying to upgrade to 2.7.1 from 2.5.2

[James Bullen]

Hi Alan,

You shouldn’t need to be fiddling with gems if you’re just upgrading. The 
distribution should contain all of the gems.


Cheers,
James


> On Feb 28, 2020, at 3:26 PM, Alan Manifold  wrote:
> 
> I was hoping someone might have responded about these problems overnight, but 
> since they didn’t, I did some more investigation myself.
>  
> Having looked at these problems more, they seem to be distribution problems. 
> The sassc gem appears not to have its extensions pre-built. We don’t really 
> have a ruby development environment, and it looks like we would have to in 
> order to build the extensions. Is that right? Is there a way to install it 
> with pre-built extensions?
>  
> The ContextAction problem seems to be related to some incompatibility between 
> the version of therubyrhino, therubyrhino_jar, and perhaps some javascript 
> library somewhere. It seems to be complaining about not being able to find 
> the ContextAction.class from org.mozilla.javascript. Is that something we’re 
> supposed to already have or is the upgrade supposed to install it or is there 
> something else going on.
>  
> We could really use some expert help on this, if anyone has any thoughts. 
> Thanks!
>  
> Regards,
> Alan
>  
>  
> 
> Alan Manifold | Library Systems & Digital Preservation Manager | Collection 
> Development & Description 
> State Library Victoria | 328 Swanston Street | Melbourne VIC 3000 
> T +61 3 8664 7122 | amanif...@slv.vic.gov.au 
>  
> slv.vic.gov.au 
> 
>    
> 
>  
> 
>  
>   
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  
> [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org 
> ] On Behalf 
> Of Alan Manifold
> Sent: Thursday, 27 February 2020 2:43 PM
> To: archivesspace_users_group@lyralists.lyrasis.org 
> 
> Subject: [Archivesspace_Users_Group] Errors trying to upgrade to 2.7.1 from 
> 2.5.2
>  
> Hi ArchivesSpacers,
> We’re trying to upgrade our installation from 2.5.2 to 2.7.1. We’ve run into 
> a number of problems, some of which we’ve solved already by adjusting 
> Gemfiles.
>  
> But we’ve got two problems that we haven’t been able to figure out so far. 
> One is a “missing dependency” for “ContextAction” and the other is some kind 
> of problem with the sassc-2.2.1 gem.
>  
> The first is a missing dependency:
>  
> ContextAction not found in packages org.mozilla.javascript; last error: 
> cannot link Java class org.mozilla.javascript.ContextAction, probable missing 
> dependency: org/mozilla/javascript/ContextAction : Unsupported major.minor 
> version 52.0
>  
> const_missing at uri:classloader:/jruby/java/core_ext/module.rb:45
>at 
> /usr/local/archivesspace-v2.7.1/gems/gems/therubyrhino-2.1.2/lib/rhino/context.rb:99
> at 
> /usr/local/archivesspace-v2.7.1/gems/gems/therubyrhino-2.1.2/lib/rhino/context.rb:36
> at 
> /usr/local/archivesspace-v2.7.1/gems/gems/therubyrhino-2.1.2/lib/rhino/context.rb:3
>   require at org/jruby/RubyKernel.java:956
> at 
> /usr/local/archivesspace-v2.7.1/gems/gems/therubyrhino-2.1.2/lib/rhino.rb:1
>   require at org/jruby/RubyKernel.java:956
>(root) at 
> /usr/local/archivesspace-v2.7.1/gems/gems/therubyrhino-2.1.2/lib/rhino.rb:61
>  find at org/jruby/RubyEnumerable.java:643
>(root) at 
> /usr/local/archivesspace-v2.7.1/gems/gems/execjs-2.7.0/lib/execjs/ruby_rhino_runtime.rb:1
>available? at 
> /usr/local/archivesspace-v2.7.1/gems/gems/execjs-2.7.0/lib/execjs/ruby_rhino_runtime.rb:91
>at 
> /usr/local/archivesspace-v2.7.1/gems/gems/execjs-2.7.0/lib/execjs/runtimes.rb:63
> at 
> /usr/local/archivesspace-v2.7.1/gems/gems/execjs-2.7.0/lib/execjs/runtimes.rb:57
>   require at org/jruby/RubyKernel.java:956
> at 
> /usr/local/archivesspace-v2.7.1/gems/gems/execjs-2.7.0/lib/execjs.rb:5
>   require at org/jruby/RubyKernel.java:956
> at 
> /usr/local/archivesspace-v2.7.1/gems/gems/execjs-2.7.0/lib/execjs.rb:4
>   require at org/jruby/RubyKernel.java:956
> at 
> /usr/local/archivesspace-v2.7.1/gems/gems/coffee-script-2.4.1/lib/coffee_script.rb:1
>   require at org/jruby/RubyKernel.java:956
>   block in (root) at 
> 

Re: [Archivesspace_Users_Group] Automated Tests for Plugins?

[James Bullen]

Hi,

You can put backend tests in plugins/your_plugin/backend/spec

Any files in there called *_spec.rb will be run on build/run backend:test


Cheers,
James



> On Feb 26, 2020, at 8:26 AM, Alexander Duryee  
> wrote:
> 
> Christina,
> 
> I'm unaware of any way to implement plugin tests into ASpace's existing test 
> infrastructure.  What we did was write RSpec tests outside of the ASpace 
> release, which start the application (with our plugins), populate it with 
> data via the API, and check the outputs of common tasks against fixtures.  
> There's probably a better way of doing this (e.g. packaging the tests in the 
> plugin directory, and having RSpec pull them out, instead of having them all 
> in a big spec directory), but so far this has worked for us.
> 
> Thanks,
> --Alex
> 
> On Tue, Feb 25, 2020 at 1:56 PM Cortland, Christina Rosalie 
> mailto:crosa...@live.unc.edu>> wrote:
> Hi all,
> 
> We wanted to explore adding automated tests for our locally developed plugins 
> and were curious how other institutions approached this. I know ArchivesSpace 
> has its own test suite that folks who develop on ArchivesSpace can use, but 
> how do institutions who develop their own plugins test their custom 
> functionality, especially when upgrading to a new ASpace release?
> 
> Thanks,
> 
> Christina Cortland
> Software Development
> UNC-Chapel Hill Libraries
> Pronouns: she/her
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 
> 
> 
> -- 
> Alexander Duryee
> Metadata Archivist
> New York Public Library
> (917)-229-9590
> alexanderdur...@nypl.org 
> !DSPAM:5e559112206501143616535! 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> 
> !DSPAM:5e559112206501143616535!

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] PUI inheritance configuration

[James Bullen]

Hi Cory,

It’s been some years since this was in my head, but it looks good.

The :inherit_if on the first rule should be selecting all subjects that have at 
least one term with a ‘genreform’ type.


Cheers,
James


> On Feb 20, 2020, at 1:37 AM, Cory Nimer  wrote:
> 
> James,
>  
> To my knowledge, a complete reindex was done following the changes (other 
> changes in note inheritance did appear as anticipated). However, the subject 
> inheritance did not seem to work. Are the inheritance statements below 
> structured correctly, or are there other reasons that these elements would 
> not be visible in the interface?
>  
> Best,
>  
> Cory
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> 
>  <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> On Behalf 
> Of James Bullen
> Sent: Tuesday, February 18, 2020 6:49 PM
> To: Archivesspace Users Group 
>  <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: Re: [Archivesspace_Users_Group] PUI inheritance configuration
>  
>  
> Hi Cory,
>  
> Have you reindexed?
>  
> The PUI runs exclusively from the PUI index so these changes won’t take 
> effect until the relevant records have been reindexed.
>  
>  
> Cheers,
> James
>  
> 
> 
> On Feb 19, 2020, at 2:26 AM, Cory Nimer  <mailto:cory_ni...@byu.edu>> wrote:
>  
> We are continuing to tweak our PUI configuration, and are interested in 
> testing inclusion of subject terms. Based on the configuration template, our 
> IT staff have attempted to add the code below but it does not appear to be 
> working after a restart and reindex: 
>  
> {
>   :property => 'subjects',
>   :inherit_if => proc {|json| json.select {|j| ! 
> j['_resolved']['terms'].select { |t| t['term_type'] == 'genreform'}.empty? } 
> },
>   :inherit_directly => true
> }, 
> {
>   :property => 'subjects',
>   :skip_if => proc {|json| ['file', 'item'].include?(json['level']) },
>   :inherit_if => proc {|json| json.select {|j| ! 
> j['_resolved']['terms'].select { |t| t['term_type'] == 'topical'}.empty? } },
>   :inherit_directly => true
> }, 
> {
>   :property => 'subjects',
>   :skip_if => proc {|json| ['file', 'item'].include?(json['level']) },
>   :inherit_if => proc {|json| json.select {|j| ! 
> j['_resolved']['terms'].select { |t| t['term_type'] == 'title'}.empty? } },
>   :inherit_directly => true
> }, 
> {
>   :property => 'subjects',
>   :skip_if => proc {|json| ['file', 'item'].include?(json['level']) },
>   :inherit_if => proc {|json| json.select {|j| ! 
> j['_resolved']['terms'].select { |t| t['term_type'] == 'geogname'}.empty? } },
>   :inherit_directly => true
> }, 
>  
> Has anyone else successfully included subject terms in their PUI inheritance 
> configuration, or have suggestions for what might be wrong? We are currently 
> running version 2.5.1.
>  
> Thanks,
>  
> Cory Nimer
> University Archivist
> Brigham Young University
> 801-422-6091
>  
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> <mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
> 
> 
> !DSPAM:5e4c053f111932459259872!
>  
> !DSPAM:5e4d482a179227770718730! 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> <mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
> 
> 
> !DSPAM:5e4d482a179227770718730!

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] PUI inheritance configuration

[James Bullen]

Hi Cory,

Have you reindexed?

The PUI runs exclusively from the PUI index so these changes won’t take effect 
until the relevant records have been reindexed.


Cheers,
James


> On Feb 19, 2020, at 2:26 AM, Cory Nimer  wrote:
> 
> We are continuing to tweak our PUI configuration, and are interested in 
> testing inclusion of subject terms. Based on the configuration template, our 
> IT staff have attempted to add the code below but it does not appear to be 
> working after a restart and reindex: 
>  
> {
>   :property => 'subjects',
>   :inherit_if => proc {|json| json.select {|j| ! 
> j['_resolved']['terms'].select { |t| t['term_type'] == 'genreform'}.empty? } 
> },
>   :inherit_directly => true
> }, 
> {
>   :property => 'subjects',
>   :skip_if => proc {|json| ['file', 'item'].include?(json['level']) },
>   :inherit_if => proc {|json| json.select {|j| ! 
> j['_resolved']['terms'].select { |t| t['term_type'] == 'topical'}.empty? } },
>   :inherit_directly => true
> }, 
> {
>   :property => 'subjects',
>   :skip_if => proc {|json| ['file', 'item'].include?(json['level']) },
>   :inherit_if => proc {|json| json.select {|j| ! 
> j['_resolved']['terms'].select { |t| t['term_type'] == 'title'}.empty? } },
>   :inherit_directly => true
> }, 
> {
>   :property => 'subjects',
>   :skip_if => proc {|json| ['file', 'item'].include?(json['level']) },
>   :inherit_if => proc {|json| json.select {|j| ! 
> j['_resolved']['terms'].select { |t| t['term_type'] == 'geogname'}.empty? } },
>   :inherit_directly => true
> }, 
>  
> Has anyone else successfully included subject terms in their PUI inheritance 
> configuration, or have suggestions for what might be wrong? We are currently 
> running version 2.5.1.
>  
> Thanks,
>  
> Cory Nimer
> University Archivist
> Brigham Young University
> 801-422-6091
>  
> !DSPAM:5e4c053f111932459259872! 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 
> 
> 
> !DSPAM:5e4c053f111932459259872!

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Agent Relationship Associative Relator

[James Bullen]

Hi Peter,

A few years ago I wrote a script for this purpose:
https://gist.github.com/jambun/553434b0e81644a53229

May be useful.

A couple of caveats:
  - The uneditable enumerations are generally uneditable for good reason.
  - Things may have changed.


Cheers,
James



> On Nov 26, 2019, at 4:03 PM, Collopy, Peter S.  wrote:
> 
> Hi all. Here at Caltech we’re experimenting with using ArchivesSpace agent 
> records in order to link together our information and holdings related to 
> Caltech people across several digital and tangible repositories. One key 
> piece of information is what relationship each individual had to Caltech 
> (typically one or more of faculty, student, staff, trustee). It makes sense 
> to us to do this using Related Agents subrecords of the agent, with an 
> associative relationship between each individual and a Corporate Entity agent 
> record representing Caltech as an organization. It also makes sense to us to 
> use the Relationship Type field as a controlled vocabulary of these specific 
> relationships individuals have with Caltech.
> 
> The agent_relationship_associative_relator controlled value list, though, is 
> one of the ones which is configured to be uneditable in ArchivesSpace. I 
> understand from past emails in this list (specifically Adam Jazairi and 
> Alexander Duryee’s emails on March 8, 2018) that it’s possible to make these 
> uneditable lists editable. I have two questions I’d appreciate help with from 
> anyone knowledgable, then:
> 
> 1. How does one make these lists editable? I don’t see anything in config.rb. 
> Does it require more direct interaction with the database? Am I overlooking 
> something?
> 
> 2. Would extending this particular controlled value list cause any problems 
> for exports to standard formats? Agents only export to EAC-CPF. It looks like 
> the exporter puts the relator (currently the default, “is_associative_with”) 
> in cpfRelationType, which doesn’t look right from the EAC-CPF spec to me, but 
> it doesn’t seem like it would cause problems to put “is_faculty_of” or the 
> link there instead—if we even have a reason to export EAC-CPF.
> 
> Thanks for any thoughts!
> 
> Peter
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> 
> !DSPAM:5ddd9318170751320666540!

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Help using AS Restful API to query

[James Bullen]

There is only one index for staff and pui.

From memory the ids of the pui docs have #pui appended.



> On Nov 8, 2019, at 11:13 AM, Seth Shaw  wrote:
> 
> That might be it. We don't use the PUI for patron access; but we do still 
> have it left on as the staff occasionally look at it. Certainly something to 
> investigate.
> 
> Regardless, either the API should use one index consistently, have a 
> documented filter (I don't see one there) and/or give some other obvious 
> indication as to where a result came from.
> 
> On Fri, Nov 8, 2019 at 8:02 AM James Bullen  <mailto:ja...@hudmol.com>> wrote:
> 
> Hi Seth,
> 
> I’m not seeing that. Could it be you’re seeing pui docs as well - the 
> instance I’m testing on has the pui turned off.
> 
> 
> Cheers,
> James
> 
> 
>> On Nov 8, 2019, at 10:51 AM, Seth Shaw > <mailto:seth.s...@unlv.edu>> wrote:
>> 
>> James, I was hoping using the filter as you described would remove the 
>> duplicate results issue I was having by using the advanced query compound 
>> search; but I'm seeing the same thing as before. 
>> 
>> Running the search via the API: 
>> 'archivestest:8089/search?type[]=archival_object=1={"query":{"comparator":"greater_than","field":"system_mtime","value":"2019-10-02","jsonmodel_type":"date_field_query"}}'
>>  returns, in part, 
>> `{"page_size":10,"first_page":1,"last_page":874,"this_page":1,"offset_first":1,"offset_last":10,"total_hits":8732,`
>>  ...
>> 
>> Whereas the SQL query `SELECT count(*) FROM archival_object WHERE 
>> system_mtime > '2019-10-02';` is returning "4369" (half the results of the 
>> REST query).
>> 
>> Have you run into this issue before?
>> 
>> 
>> 
>> On Fri, Nov 8, 2019 at 7:34 AM James Bullen > <mailto:ja...@hudmol.com>> wrote:
>> 
>> Something like this works for me:
>> 
>> /search type[]=resource type[]=archival_object page=1 
>> filter={"query":{"comparator":"greater_than","field":"system_mtime","value":"2019-10-02","jsonmodel_type":"date_field_query"}}
>> 
>> 
>> 
>> 
>>> On Nov 8, 2019, at 10:24 AM, Seth Shaw >> <mailto:seth.s...@unlv.edu>> wrote:
>>> 
>>> To do this you need to use the advanced query parameter which, 
>>> unfortunately, is not well documented. There are a few email threads that 
>>> describe using the advanced search though:
>>> 
>>> http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2015-June/001734.html
>>>  
>>> <http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2015-June/001734.html>
>>> 
>>> I've formulated queries like you describe before (I'll have to dig through 
>>> my notes to see if I can find it again); but the result set was 
>>> consistently giving me back duplicate results for some unknown reason; so I 
>>> stopped using it. 
>>> 
>>> Ideally, we would be able to add a 'modified_since' parameter to each 
>>> entity's endpoint to get the most recent set. The capability exists in the 
>>> code, but hasn't been exposed to the REST end-point. I've submitted a 
>>> ticket that will hopefully lead to this being resolved: 
>>> https://archivesspace.atlassian.net/browse/ANW-962?filter=-2 
>>> <https://archivesspace.atlassian.net/browse/ANW-962?filter=-2>.
>>> 
>>> 
>>> On Fri, Nov 8, 2019 at 7:07 AM Steve Mattison >> <mailto:smatt...@nd.edu>> wrote:
>>>  
>>> <https://mail.google.com/mail/?view=cm=1=1=archivesspace_users_group@lyralists.lyrasis.org>Community,
>>> 
>>> I'm new to using ArchivesSpace, and new to using the AS API.  I need to use 
>>> the API to search within a given repository to find records that have been 
>>> modified after a particular time (e.g. modified within the last 48 hours).  
>>> (We then want to export metadata related to those resources or 
>>> archival_objects for a project we're working on.)
>>> 
>>> I have found the documentation for search-this-repository 
>>> <http://archivesspace.github.io/archivesspace/api/?shell#search-this-repository>,
>>>  but don't know how to formulate a query to find all resources and/or 
>>> archival_objects wh

Re: [Archivesspace_Users_Group] Help using AS Restful API to query

[James Bullen]

Hi Seth,

I’m not seeing that. Could it be you’re seeing pui docs as well - the instance 
I’m testing on has the pui turned off.


Cheers,
James


> On Nov 8, 2019, at 10:51 AM, Seth Shaw  wrote:
> 
> James, I was hoping using the filter as you described would remove the 
> duplicate results issue I was having by using the advanced query compound 
> search; but I'm seeing the same thing as before. 
> 
> Running the search via the API: 
> 'archivestest:8089/search?type[]=archival_object=1={"query":{"comparator":"greater_than","field":"system_mtime","value":"2019-10-02","jsonmodel_type":"date_field_query"}}'
>  returns, in part, 
> `{"page_size":10,"first_page":1,"last_page":874,"this_page":1,"offset_first":1,"offset_last":10,"total_hits":8732,`
>  ...
> 
> Whereas the SQL query `SELECT count(*) FROM archival_object WHERE 
> system_mtime > '2019-10-02';` is returning "4369" (half the results of the 
> REST query).
> 
> Have you run into this issue before?
> 
> 
> 
> On Fri, Nov 8, 2019 at 7:34 AM James Bullen  <mailto:ja...@hudmol.com>> wrote:
> 
> Something like this works for me:
> 
> /search type[]=resource type[]=archival_object page=1 
> filter={"query":{"comparator":"greater_than","field":"system_mtime","value":"2019-10-02","jsonmodel_type":"date_field_query"}}
> 
> 
> 
> 
>> On Nov 8, 2019, at 10:24 AM, Seth Shaw > <mailto:seth.s...@unlv.edu>> wrote:
>> 
>> To do this you need to use the advanced query parameter which, 
>> unfortunately, is not well documented. There are a few email threads that 
>> describe using the advanced search though:
>> 
>> http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2015-June/001734.html
>>  
>> <http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2015-June/001734.html>
>> 
>> I've formulated queries like you describe before (I'll have to dig through 
>> my notes to see if I can find it again); but the result set was consistently 
>> giving me back duplicate results for some unknown reason; so I stopped using 
>> it. 
>> 
>> Ideally, we would be able to add a 'modified_since' parameter to each 
>> entity's endpoint to get the most recent set. The capability exists in the 
>> code, but hasn't been exposed to the REST end-point. I've submitted a ticket 
>> that will hopefully lead to this being resolved: 
>> https://archivesspace.atlassian.net/browse/ANW-962?filter=-2 
>> <https://archivesspace.atlassian.net/browse/ANW-962?filter=-2>.
>> 
>> 
>> On Fri, Nov 8, 2019 at 7:07 AM Steve Mattison > <mailto:smatt...@nd.edu>> wrote:
>>  
>> <https://mail.google.com/mail/?view=cm=1=1=archivesspace_users_group@lyralists.lyrasis.org>Community,
>> 
>> I'm new to using ArchivesSpace, and new to using the AS API.  I need to use 
>> the API to search within a given repository to find records that have been 
>> modified after a particular time (e.g. modified within the last 48 hours).  
>> (We then want to export metadata related to those resources or 
>> archival_objects for a project we're working on.)
>> 
>> I have found the documentation for search-this-repository 
>> <http://archivesspace.github.io/archivesspace/api/?shell#search-this-repository>,
>>  but don't know how to formulate a query to find all resources and/or 
>> archival_objects where the system_mtime is after a particular time.  I would 
>> be fine with performing two searches, one for resources and one for 
>> archival_objects, if that is required.
>> 
>> Any help with the syntax for the query would be much appreciated.
>> 
>> Thanks for your help.
>> 
>> -- 
>> Steve Mattison
>> Lead Software Engineer, Digital Library Technologies
>> Hesburgh Libraries
>> 
>> University of Notre Dame
>> 271 Hesburgh Library
>> Notre Dame, IN 46556-5629
>> o: 574-631-8559
>> e: steve.matti...@nd.edu <mailto:steve.matti...@nd.edu>
>> 
>> ___
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group@lyralists.lyrasis.org 
>> <mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
>> <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_grou

Re: [Archivesspace_Users_Group] Help using AS Restful API to query

[James Bullen]

Something like this works for me:

/search type[]=resource type[]=archival_object page=1 
filter={"query":{"comparator":"greater_than","field":"system_mtime","value":"2019-10-02","jsonmodel_type":"date_field_query"}}




> On Nov 8, 2019, at 10:24 AM, Seth Shaw  wrote:
> 
> To do this you need to use the advanced query parameter which, unfortunately, 
> is not well documented. There are a few email threads that describe using the 
> advanced search though:
> 
> http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2015-June/001734.html
>  
> 
> 
> I've formulated queries like you describe before (I'll have to dig through my 
> notes to see if I can find it again); but the result set was consistently 
> giving me back duplicate results for some unknown reason; so I stopped using 
> it. 
> 
> Ideally, we would be able to add a 'modified_since' parameter to each 
> entity's endpoint to get the most recent set. The capability exists in the 
> code, but hasn't been exposed to the REST end-point. I've submitted a ticket 
> that will hopefully lead to this being resolved: 
> https://archivesspace.atlassian.net/browse/ANW-962?filter=-2 
> .
> 
> 
> On Fri, Nov 8, 2019 at 7:07 AM Steve Mattison  > wrote:
>  
> Community,
> 
> I'm new to using ArchivesSpace, and new to using the AS API.  I need to use 
> the API to search within a given repository to find records that have been 
> modified after a particular time (e.g. modified within the last 48 hours).  
> (We then want to export metadata related to those resources or 
> archival_objects for a project we're working on.)
> 
> I have found the documentation for search-this-repository 
> ,
>  but don't know how to formulate a query to find all resources and/or 
> archival_objects where the system_mtime is after a particular time.  I would 
> be fine with performing two searches, one for resources and one for 
> archival_objects, if that is required.
> 
> Any help with the syntax for the query would be much appreciated.
> 
> Thanks for your help.
> 
> -- 
> Steve Mattison
> Lead Software Engineer, Digital Library Technologies
> Hesburgh Libraries
> 
> University of Notre Dame
> 271 Hesburgh Library
> Notre Dame, IN 46556-5629
> o: 574-631-8559
> e: steve.matti...@nd.edu 
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 
> !DSPAM:5dc588a9250937848916637! 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> 
> !DSPAM:5dc588a9250937848916637!

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI?

[James Bullen]

Hi Kara,

Yes, there is no need to initialize this plugin.

And, sorry, I have no idea how you might request this as an enhancement.


Cheers,
James


> On Nov 1, 2019, at 3:33 PM, Majewski, Steven Dennis (sdm7g) 
>  wrote:
> 
> 
> 
>> On Nov 1, 2019, at 3:06 PM, Kara Hart > <mailto:kstro...@wellesley.edu>> wrote:
>> 
>> Thank you James!! and Andrew!   
>> I wasn't sure if I needed to run initialize-plugin.sh on this, so I did and 
>> got this.
>> 
>> Fetching: bundler-1.16.1.gem (100%)
>> Successfully installed bundler-1.16.1
>> 1 gem installed
>> 
>> [!] There was an error parsing `Gemfile`: No such file or directory - 
>> /var/local/archivesspace/plugins/static_pages/Gemfile. Bundler cannot 
>> continue.
>> 
>> I figure I didn't need to initialize and this error doesn't matter, but just 
>> checking.
>> 
> 
> 
> Correct. You only have to run that script if the plugin requires some Gems 
> that aren’t already included in that web app core.
> That there isn’t a Gemfile in the plugin directory indicates that it doesn’t 
> need to bundle any additional Gems. 
> And when you run the Bundler, it’s telling you that there is no Gemfile.  
> 
> — Steve. 
> 
> 
> 
>> Also, if I want to put this in as a request for an enhancement for the core 
>> code, should I put create a new feature request in Jira the project ANW?  Is 
>> that the proper channel?  
>> Thanks again! 
>> Kara
>> 
>> ~~~ Kara S. Hart 
>> Systems Librarian - Library & Technology Services - Wellesley College
>> 
>> 
>> 
>> 
>> On Tue, Oct 29, 2019 at 2:19 PM Mike McDermott > <mailto:mmcde...@bowdoin.edu>> wrote:
>> Nice – looks good. Thanks!
>> 
>>  
>> 
>> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> 
>> > <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> On Behalf 
>> Of James Bullen
>> Sent: Tuesday, October 29, 2019 1:05 PM
>> To: Archivesspace Users Group 
>> > <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
>> Subject: Re: [Archivesspace_Users_Group] Add a static web page to 
>> ArchivesSpace PUI?
>> 
>>  
>> 
>>  
>> 
>> That’s funny - shows how much testing I did.
>> 
>>  
>> 
>> Should be good now.
>> 
>>  
>> 
>> 
>> 
>> 
>> On Oct 29, 2019, at 1:00 PM, Mike McDermott > <mailto:mmcde...@bowdoin.edu>> wrote:
>> 
>>  
>> 
>> This looks really cool.
>> 
>> But – What am I doing wrong. 
>> 
>> When I put html in the file to be included, it comes out on the page looking 
>> like this:
>> 
>>  
>> 
>> div class=row
>> 
>> h2This is a test/h2
>> 
>> pThis is always a test/p
>> 
>> pTests are what I do./p
>> 
>> h3here is a heading/h3
>> 
>> pThis is always a test/p
>> 
>> pTests are what I do./p
>> 
>> h3here is a heading/h3
>> 
>> pThis is always a test/p
>> 
>> pTests are what I do./p  
>> 
>> /div
>> 
>>  
>> 
>> So it is rendered on the page as looking like html code instead of the page 
>> elements.
>> 
>>  
>> 
>> Mike McDermott
>> 
>>  
>> 
>> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> 
>> > <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> On Behalf 
>> Of Andrew Morrison
>> Sent: Tuesday, October 29, 2019 10:55 AM
>> To: Archivesspace Users Group 
>> > <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
>> Subject: Re: [Archivesspace_Users_Group] Add a static web page to 
>> ArchivesSpace PUI?
>> 
>>  
>> 
>> Hi James,
>> 
>>  
>> 
>> Your original version will be useful to us, because we're probably going to 
>> want to add extra help pages to our staff interface for cataloguers 
>> transferring over from Archivists' Toolkit. And reading the static HTML from 
>> a file instead of building from ERB templates means they can be updated 
>> without restarting the service.
>> 
>>  
>> 
>> Andrew.
>> 
>>  
>> 
>>  
>> 
>> On Tue, 2019-10-29 at 09:35 -0400, James Bullen wrote:
>> 
>>  
>> 
>> Just a quick follow up on this, 
>> 
>>  
&g

Re: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI?

[James Bullen]

That’s funny - shows how much testing I did.

Should be good now.


> On Oct 29, 2019, at 1:00 PM, Mike McDermott  wrote:
> 
> This looks really cool.
> But – What am I doing wrong. 
> When I put html in the file to be included, it comes out on the page looking 
> like this:
>  
> div class=row
> h2This is a test/h2
> pThis is always a test/p
> pTests are what I do./p
> h3here is a heading/h3
> pThis is always a test/p
> pTests are what I do./p
> h3here is a heading/h3
> pThis is always a test/p
> pTests are what I do./p  
> /div
>  
> So it is rendered on the page as looking like html code instead of the page 
> elements.
>  
> Mike McDermott
>  
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org> 
>  <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> On Behalf 
> Of Andrew Morrison
> Sent: Tuesday, October 29, 2019 10:55 AM
> To: Archivesspace Users Group 
>  <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: Re: [Archivesspace_Users_Group] Add a static web page to 
> ArchivesSpace PUI?
>  
> Hi James,
>  
> Your original version will be useful to us, because we're probably going to 
> want to add extra help pages to our staff interface for cataloguers 
> transferring over from Archivists' Toolkit. And reading the static HTML from 
> a file instead of building from ERB templates means they can be updated 
> without restarting the service.
>  
> Andrew.
>  
>  
> On Tue, 2019-10-29 at 09:35 -0400, James Bullen wrote:
>  
> Just a quick follow up on this, 
>  
> I had misread the spec and only provided the static page facility on the 
> staff interface - should have been on the PUI. Andrew Morrison noticed my 
> oops and corrected it, so now it should work on both.
>  
>  
> Cheers,
> James
>  
> 
> 
> On Oct 28, 2019, at 6:02 PM, James Bullen  <mailto:ja...@hudmol.com>> wrote:
>  
> 
> Hi Kara,
>  
> This seemed like a useful thing that I don’t think exists yet, so I made a 
> plugin to do it:
>  
> https://github.com/hudmol/static_pages 
> <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhudmol%2Fstatic_pages=02%7C01%7Cmmcderm2%40bowdoin.edu%7C0ecce92cdd1440de521708d75c7ff030%7C984e32e5f98a4600aa3227c3f948abe3%7C1%7C0%7C637079576880523489=Sa2ItRFCDaOmsovi3KCfXPus5ax6CzQOUWX%2FizUzXQ0%3D=0>
>  
> Maybe it can be a useful starting point.
>  
>  
> Cheers,
> James
>  
>  
> 
> 
> On Oct 28, 2019, at 3:52 PM, Kara Hart  <mailto:kstro...@wellesley.edu>> wrote:
>  
> Hi all,
> I want to be able to add static web pages to ArchivesSpace.  I'd like to 
> incorporate the header, top nav, and footer and be able to just add what I 
> want in the middle.  I'm basically hoping to create general FAQ, search help, 
> about pages that live in my ArchivesSpace local plugin.  Is this possible? 
>  
> I did find a way to add a page by putting a .html doc into 
> /archivesspace/plugins/local/public/assets, but I have to manually copy in 
> the head, navigation, header, and footer, which is obviously not ideal for 
> updating and probably other reasons.  
>  
> If there isn't a way to do this, where is the proper place to suggest this 
> enhancement?  Should I create a new feature request in Jira the project ANW? 
> (https://archivesspace.atlassian.net/projects/ANW/issues/?filter=allissues&= 
> <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fprojects%2FANW%2Fissues%2F%3Ffilter%3Dallissues%26%3D=02%7C01%7Cmmcderm2%40bowdoin.edu%7C0ecce92cdd1440de521708d75c7ff030%7C984e32e5f98a4600aa3227c3f948abe3%7C1%7C0%7C637079576880533482=qcQNoE8PClS8cRShKKCSTKU6bhpY4vG72bH1h%2FXsr%2Bk%3D=0>)
>  
> Thanks for any help,
> Kara
>  
>  
> ~~~ Kara S. Hart 
> Systems Librarian - Library & Technology Services 
> - 
> Wellesley College
>  
>  
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> <mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> <https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group=02%7C01%7Cmmcderm2%40bowdoin.edu%7C0ecce92cdd1440de521708d75c7ff030%7C984e32e5f98a4600aa3227c3f948abe3%7C1%7C0%7C637079576880533482=pI8hr65hm2FcgeZ6d9oxFYbBw31s55LrdUKGmkQMKc4%3D=0>
> 
> 
>  
> !DSPAM:5db76577327211158617254! 
> ___
>

Re: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI?

[James Bullen]

Just a quick follow up on this,

I had misread the spec and only provided the static page facility on the staff 
interface - should have been on the PUI. Andrew Morrison noticed my oops and 
corrected it, so now it should work on both.


Cheers,
James


> On Oct 28, 2019, at 6:02 PM, James Bullen  wrote:
> 
> 
> Hi Kara,
> 
> This seemed like a useful thing that I don’t think exists yet, so I made a 
> plugin to do it:
> 
> https://github.com/hudmol/static_pages 
> <https://github.com/hudmol/static_pages>
> 
> Maybe it can be a useful starting point.
> 
> 
> Cheers,
> James
> 
> 
> 
>> On Oct 28, 2019, at 3:52 PM, Kara Hart > <mailto:kstro...@wellesley.edu>> wrote:
>> 
>> Hi all,
>> I want to be able to add static web pages to ArchivesSpace.  I'd like to 
>> incorporate the header, top nav, and footer and be able to just add what I 
>> want in the middle.  I'm basically hoping to create general FAQ, search 
>> help, about pages that live in my ArchivesSpace local plugin.  Is this 
>> possible? 
>> 
>> I did find a way to add a page by putting a .html doc into 
>> /archivesspace/plugins/local/public/assets, but I have to manually copy in 
>> the head, navigation, header, and footer, which is obviously not ideal for 
>> updating and probably other reasons.  
>> 
>> If there isn't a way to do this, where is the proper place to suggest this 
>> enhancement?  Should I create a new feature request in Jira the project ANW? 
>> (https://archivesspace.atlassian.net/projects/ANW/issues/?filter=allissues&= 
>> <https://archivesspace.atlassian.net/projects/ANW/issues/?filter=allissues&=>)
>> 
>> Thanks for any help,
>> Kara
>> 
>> 
>> ~~~ Kara S. Hart 
>> Systems Librarian - Library & Technology Services - Wellesley College
>> 
>> 
>> ___
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group@lyralists.lyrasis.org 
>> <mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
>> <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
>> 
>> 
>> !DSPAM:5db7471d288581084719066!
> 
> !DSPAM:5db76577327211158617254! 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> <mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
> 
> 
> !DSPAM:5db76577327211158617254!

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI?

[James Bullen]

Hi Kara,

This seemed like a useful thing that I don’t think exists yet, so I made a 
plugin to do it:

https://github.com/hudmol/static_pages 

Maybe it can be a useful starting point.


Cheers,
James



> On Oct 28, 2019, at 3:52 PM, Kara Hart  wrote:
> 
> Hi all,
> I want to be able to add static web pages to ArchivesSpace.  I'd like to 
> incorporate the header, top nav, and footer and be able to just add what I 
> want in the middle.  I'm basically hoping to create general FAQ, search help, 
> about pages that live in my ArchivesSpace local plugin.  Is this possible? 
> 
> I did find a way to add a page by putting a .html doc into 
> /archivesspace/plugins/local/public/assets, but I have to manually copy in 
> the head, navigation, header, and footer, which is obviously not ideal for 
> updating and probably other reasons.  
> 
> If there isn't a way to do this, where is the proper place to suggest this 
> enhancement?  Should I create a new feature request in Jira the project ANW? 
> (https://archivesspace.atlassian.net/projects/ANW/issues/?filter=allissues&= 
> )
> 
> Thanks for any help,
> Kara
> 
> 
> ~~~ Kara S. Hart 
> Systems Librarian - Library & Technology Services - Wellesley College
> 
> 
> !DSPAM:5db7471d288581084719066! 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> 
> !DSPAM:5db7471d288581084719066!

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Extent Calculation

[James Bullen]

Hi Ed,

Here are the config options.

# :report_volume if true the report will show the cubic volume,
#   otherwise linear based on extent dimension
# :unit values = :inches, :feet, :centimeters, :meters
#defaults to the first unit it finds when calculating extent
# :decimal_places = the number of decimal places to show in the extent value
#   defaults to 2
AppConfig[:container_management_extent_calculator] = {
  :report_volume => false,
  :unit => :feet,
  :decimal_places => 3
}

So, just set :report_volume to true and you should be good.


Cheers,
James


> On Jun 21, 2018, at 6:50 AM, Busch, Ed  wrote:
> 
> Does the ASpace Extent Calculation only do linear feet or can it do cubic 
> feet? I've tried changing the Extent Dimension but that doesn't seem to 
> effect the units.
> 
> Ed Busch
> Electronic Records Archivist
> MSU Archives
> 
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> !DSPAM:5b2abe8f522559955512038!

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ArchivesSpace developers in Portland

[James Bullen]

Hello ArchivesSpace developers,

Are you interested in getting together in Portland? Mark Triggs and I will be 
there and would love to meet up with other people developing with ArchivesSpace.

If you’re interested, please contact me off list.


Cheers,
James


—
James Bullen
Director/Developer, Hudson Molonglo
ArchivesSpace Development Partner

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Indexer erroring in 1.5.2

[James Bullen]

Hi Brent,

Sorry for the slow reply. From memory this is caused by bad instance records 
left around after certain operations on  digital objects. The bug that caused 
this has been fixed, but you may still have some of these bad records lying 
around.

The problem records are digital object type instances that don’t have a link to 
a digital object. This SQL will return any such records:

select i.* from instance i
left join instance_do_link_rlshp r on i.id = r.instance_id
left join enumeration_value e on i.instance_type_id = e.id
where instance_type_id = 349 and r.id is null
and e.value = 'digital_object';

If that query returns any rows, then just delete them. Hopefully that will fix 
the problem.


Cheers,
James



> On Mar 23, 2017, at 9:00 AM, Brent Ellingson <brent_elling...@byu.edu> wrote:
> 
> We are in the process of upgrading our site from 1.4.2 to 1.5.3 and we are 
> seeing a similar error as has been described in this thread. We are seeing 
> the error below and continued looping of the indexer trying to index the 
> archival objects.
>  
> ~~~ Indexed 1225 of 67886 archival_object records in repository 2 ( added 25 
> records in  6399.0ms ) ~~~
> ~~~ Indexed 1250 of 67886 archival_object records in repository 2 ( added 25 
> records in  5488.0ms ) ~~~
> E, [2017-03-16T16:53:51.425000 #779] ERROR -- : Thread-2392462: Unhandled 
> exception!
> E, [2017-03-16T16:53:51.425000 #779] ERROR -- :
> undefined method `related_records' for nil:NilClass
> /opt/archivesspace-1.5.3/archivesspace/data/tmp/jetty-0.0.0.0-9089-backend.war-_-any-/webapp/WEB-INF/app/lib/subcontainer_to_aspace_json_mapper.rb:64:in
>  `top_container'
> /opt/archivesspace-1.5.3/archivesspace/data/tmp/jetty-0.0.0.0-9089-backend.war-_-any-/webapp/WEB-INF/app/lib/subcontainer_to_aspace_json_mapper.rb:24:in
>  `type_1'
> /opt/archivesspace-1.5.3/archivesspace/data/tmp/jetty-0.0.0.0-9089-backend.war-_-any-/webapp/WEB-INF/app/lib/subcontainer_to_aspace_json_mapper.rb:14:in
>  `to_hash'
> org/jruby/RubyHash.java:1341:in `each'
> org/jruby/RubyEnumerable.java:757:in `map'
>  
> Does a resolution to this issue exist?
> How do I find what the offending set of data is causing the problem?
> How do I proceed?
>  
> Thank you for your help.
>  
> Regards,
> __
> Brent Ellingson
> Sr. Software Engineer
> BYU Library
> 801-422-6148
>  
>  
> Date: Mon, 23 Jan 2017 19:54:53 +
> From: "Majewski, Steven Dennis (sdm7g)" <sd...@eservices.virginia.edu 
> <mailto:sd...@eservices.virginia.edu>>
> To: Archivesspace Users Group
> <archivesspace_users_group@lyralists.lyrasis.org 
> <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: Re: [Archivesspace_Users_Group] Indexer erroring in 1.5.2
> Message-ID:
> <1b0ea75c-ee19-492a-b057-fbaefbbfb...@eservices.virginia.edu 
> <mailto:1b0ea75c-ee19-492a-b057-fbaefbbfb...@eservices.virginia.edu>>
> Content-Type: text/plain; charset="utf-8"
>  
>  
> The first two issues appear to be due to trailing spaces in some of the 
> container barcodes.
> Top containers have already been created for barcodes without trailing space, 
> and so it appears that the barcodes don?t match.
>  
>  
>  
> On Jan 20, 2017, at 3:49 PM, Majewski, Steven Dennis (sdm7g) 
> <sd...@eservices.virginia.edu<mailto:sd...@eservices.virginia.edu 
> <mailto:sd...@eservices.virginia.edu%3cmailto:sd...@eservices.virginia.edu>>> 
> wrote:
>  
>  
> On Jan 13, 2017, at 6:15 PM, James Bullen 
> <ja...@hudmol.com<mailto:ja...@hudmol.com 
> <mailto:ja...@hudmol.com%3cmailto:ja...@hudmol.com>>> wrote:
>  
>  
> Hi Steve,
>  
> That fits the pattern I?m seeing in John?s data. Have you checked the 
> container conversion log for any errors relating to that record?
>  
>  
> Cheers,
> James
>  
>  
>  
> Just re-did migration from 1.4.2 to 1.5.1 again, and I?m inspecting the logs.
>  
> Yes, archival_objects/255 is on that list.
>  
> error,message,url
> JSONModel::ValidationException,barcode_1 -- Mismatch when mapping between 
> barcode and 
> barcode_1,http://UL-sdm7g-mbp.local/resolve/readonly?uri=/repositories/3/archival_objects/331<http://ul-sdm7g-mbp.local/resolve/readonly?uri=/repositories/3/archival_objects/331
>  
> <http://ul-sdm7g-mbp.local/resolve/readonly?uri=/repositories/3/archival_objects/331>>
> JSONModel::ValidationException,barcode_1 -- Mismatch when mapping between 
> barcode and 
> barcode_1,http://UL-sdm7g-mbp.local/resolve/readonly?uri=/repositories/3/archival_objects/2059<http://ul-sdm7g-mbp.local/resolve/readonly?uri=/repositories/3/archival_objects/2059
>  
> <http

Re: [Archivesspace_Users_Group] PUI & ArchivesSpace

[James Bullen]

Hi again Steve!

Actually, we just did a big merge to pull together a number of development 
strands for the March release. So now the latest pui code will be in:
https://github.com/archivesspace/archivesspace/tree/march-release


Cheers,
James


> On Feb 22, 2017, at 8:20 AM, James Bullen <ja...@hudmol.com> wrote:
> 
> 
> Hi Steve,
> 
> The development branch for the new public UI is called pui:
> https://github.com/archivesspace/archivesspace/tree/pui 
> <https://github.com/archivesspace/archivesspace/tree/pui>
> 
> To enable the new version, set this environment variable:
> export ASPACE_PUBLIC_NEW=true
> 
> 
> Cheers,
> James
> 
> 
>> On Feb 22, 2017, at 4:18 AM, Majewski, Steven Dennis (sdm7g) 
>> <sd...@eservices.virginia.edu> wrote:
>> 
>> 
>> Sorry: I was asking about running public-new. 
>> It seems to want to use features of the backend /search API that are not 
>> supported in 1.5.3 . 
>> Is there a different branch of archivesspace that matches up with the new 
>> PUI ? 
>> 
>> — Steve. 
>> 
>> 
>>> On Feb 20, 2017, at 6:59 PM, Majewski, Steven Dennis (sdm7g) 
>>> <sd...@eservices.virginia.edu> wrote:
>>> 
>>> What branch or version of ArchivesSpace does the PUI require ? 
>>> I can get it to sort of run, but all of the searches fail. 
>>> 
>>> 
>>> ___
>>> Archivesspace_Users_Group mailing list
>>> Archivesspace_Users_Group@lyralists.lyrasis.org
>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>> 
>> ___
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group@lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>> 
>> 
>> 
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> <mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
> 
> 
> !DSPAM:58acaf3551392126911598!

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Indexer erroring in 1.5.2

[James Bullen]

Hi Steve,

Yes that’s how it looks to me too. It should really be able to handle that case 
so I would consider this to be a bug.


Cheers,
James


> On Jan 24, 2017, at 6:54 AM, Majewski, Steven Dennis (sdm7g) 
> <sd...@eservices.virginia.edu> wrote:
> 
> 
> The first two issues appear to be due to trailing spaces in some of the 
> container barcodes.
> Top containers have already been created for barcodes without trailing space, 
> and so it appears that the barcodes don’t match. 
> 
> 
> 
>> On Jan 20, 2017, at 3:49 PM, Majewski, Steven Dennis (sdm7g) 
>> <sd...@eservices.virginia.edu <mailto:sd...@eservices.virginia.edu>> wrote:
>> 
>>> 
>>> On Jan 13, 2017, at 6:15 PM, James Bullen <ja...@hudmol.com 
>>> <mailto:ja...@hudmol.com>> wrote:
>>> 
>>> 
>>> Hi Steve,
>>> 
>>> That fits the pattern I’m seeing in John’s data. Have you checked the 
>>> container conversion log for any errors relating to that record?
>>> 
>>> 
>>> Cheers,
>>> James
>>> 
>> 
>> 
>> Just re-did migration from 1.4.2 to 1.5.1 again, and I’m inspecting the logs.
>> 
>> Yes, archival_objects/255 is on that list. 
>> 
>> error,message,url
>> JSONModel::ValidationException,barcode_1 -- Mismatch when mapping between 
>> barcode and 
>> barcode_1,http://UL-sdm7g-mbp.local/resolve/readonly?uri=/repositories/3/archival_objects/331
>>  
>> <http://ul-sdm7g-mbp.local/resolve/readonly?uri=/repositories/3/archival_objects/331>
>> JSONModel::ValidationException,barcode_1 -- Mismatch when mapping between 
>> barcode and 
>> barcode_1,http://UL-sdm7g-mbp.local/resolve/readonly?uri=/repositories/3/archival_objects/2059
>>  
>> <http://ul-sdm7g-mbp.local/resolve/readonly?uri=/repositories/3/archival_objects/2059>
>> JSONModel::ValidationException,indicator_1 -- Mismatch when mapping between 
>> indicator and 
>> indicator_1,http://UL-sdm7g-mbp.local/resolve/readonly?uri=/repositories/3/archival_objects/255
>>  
>> <http://ul-sdm7g-mbp.local/resolve/readonly?uri=/repositories/3/archival_objects/255>
>> 
>> 
>> 
>> I need to inspect the other repo logs and see if all of the ones that break 
>> are getting caught, but it looks likely.
>> 
>> I’m trying to interpret what exactly those messages are complaining about. 
>> Do those error messages and object dumps mean anything to you off the bat? 
>> 
>> — Steve. 
>> 
>> 
>>>> On Jan 14, 2017, at 8:37 AM, Majewski, Steven Dennis (sdm7g) 
>>>> <sd...@eservices.virginia.edu <mailto:sd...@eservices.virginia.edu>> wrote:
>>>> 
>>>> 
>>>> It looks like the indexer gives and error because the backend is getting 
>>>> an error turning the SQL model into a JSON model. 
>>>> 
>>>> For some of the archival objects that are failing to index, the 
>>>> significant difference is that they do not have a sub_container in their 
>>>> instance. Trying to access the json from the backend in 1.5.2 just yields 
>>>> an error message, but going back to test 1.5.1 migration:
>>>> 
>>>> [ This is json from the same screen capture in my previous message. ] 
>>>> 
>>>> archival_object 255 ( which causes error on index )
>>>> 
>>>> {
>>>>   "lock_version": 0,
>>>>   "position": 17,
>>>>   "publish": true,
>>>>   "ref_id": "aspace_22a35d6a6ee59ac454ca8f35232b0b40",
>>>>   "title": "Buttons and uniform parts, souvenirs, and medals",
>>>>   "display_string": "Buttons and uniform parts, souvenirs, and medals, 
>>>> undated",
>>>>   "restrictions_apply": false,
>>>>   "created_by": "admin",
>>>>   "last_modified_by": "admin",
>>>>   "create_time": "2015-08-11T21:43:55Z",
>>>>   "system_mtime": "2017-01-06T22:25:38Z",
>>>>   "user_mtime": "2015-08-11T21:43:55Z",
>>>>   "suppressed": false,
>>>>   "level": "file",
>>>>   "jsonmodel_type": "archival_object",
>>>>   "external_ids": [],
>>>>   "subjects": [],
>>>>   "linked_events": [],
>>>>   "extents": [],
>>>>   &quo

Re: [Archivesspace_Users_Group] Event Creation Error

[James Bullen]

Hi Elizabeth,

I wasn’t able to reproduce this. Can you provide any more context?


Cheers,
James


> On Dec 21, 2016, at 4:51 AM, Elizabeth Dunham  
> wrote:
> 
> Hello,
>  
> We upgraded to ArchivesSpace version 1.5.2  about a week ago, and have been 
> getting an error titled “NoMethodError in 
> ResolverController#resolve_readonly” when we create new events of any type 
> since (screenshot attached).  The event itself is saved, so this issue is 
> primarily a nuisance.
>  
> Has anyone else run into this problem and, if so, were you able to resolve it?
>  
> Thanks for your help!
>  
> Best,
> Elizabeth Dunham
>  
> 
> Assistant Archivist
> Arizona State University Libraries
> Archives and Special Collections
> Tempe, AZ 85287-1006
> elizabeth.dun...@asu.edu 
> !DSPAM:58597005270904288115691! 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 
> 
> 
> !DSPAM:58597005270904288115691!

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Database troubles upgrading from 1.4.2 to 1.5.1

[James Bullen]

Hi Brent,

It’s hard to be sure what’s going on here, but my guess is that at some point 
your 1.4.2 instance was running the container management plugin, but that it 
isn’t currently. That would explain what you’re seeing.

If my guess is right then a fix would be to add container management to your 
list of plugins just while you run setup-database.sh, something like this in 
config.rb:

AppConfig[:plugins] = [‘other’, ’stuff’, ‘container_management']

That would cause it to skip the container management migration - which would 
have run when the plugin was installed. It’s blowing up on trying to add a 
duplicate entry to the enumeration table (name has a unique constraint).

You can confirm this by looking at the tables in your database. If you see 
‘top_container’ then the container management migration has been run.

It’s possible you’ve landed in a bad state, so if it continues to fail, try 
starting again and just do the AppConfig tweak just before running 
setup-database.sh, and then remove it after.

Here’s the relevant migration:
https://github.com/archivesspace/archivesspace/blob/master/common/db/migrations/060_top_container_migration.rb

If this doesn't fix it then my guess is wrong - entirely possible! - and we’ll 
need to dig a little deeper.


Good luck!


Cheers,
James


> On Dec 2, 2016, at 7:27 AM, Brent Ellingson  wrote:
> 
> We are trying to upgrade a test instance of ArchivesSpace from 1.4.2 to 1.5.1 
> and we have run into some SQL errors that have prevented the upgrade. We are 
> using a copy of the production data.
>  
> Some help or suggestions would be greatly appreciated.
>  
> Here is basically what we have done.
> * Get a MySQL dump of the production DB
> * Copy the DB to a new server (now running MariaDB)
> * Installed ArchivesSpace 1.4.2
> * Started & indexed the 1.4.2 instance
> * Tested the 1.4.2 instance and it was running fine
> * Started the upgrade process for 1.5.1
> * Stopped the 1.4.2 instance
> * Unzipped the 1.5.1 archive to a new place
> * Copied the data files to the 1.5.1/data directory
> * Copied the config.rb
> * Copied the mysql jdbc jar to lib
> * Copied the plugins (we don't have any that I know of)
> * Checked the en.yml files
> * Ran the setup-database.sh script
> * Setup stopped due to a Database error
>  
> Here is the text of the error we are seeing from the log file:
>  Begin error log output 
> Loading ArchivesSpace configuration file from path: 
> /opt/archivesspace-1.5.1/archivesspace/config/config.rb
> Loading ArchivesSpace configuration file from path: 
> /opt/archivesspace-1.5.1/archivesspace/config/config.rb
> Running migrations against 
> jdbc:mysql://[DB_SERVER]:3306/[DB_NAME]?user=[REDACTED]=[REDACTED]=true=UTF-8
>  
> 
> 
> 
> 
> 
> 
> 
>  
>  3 
>  
>  
>  Database migration error. 
>  Your upgrade has encountered a problem. 
>  You must resolve these issues before the database migration can complete.
>  
>  
>  Error: 
>  # Java::ComMysqlJdbcExceptionsJdbc4::MySQLIntegrityConstraintViolationException:
>  Duplicate entry 'restriction_type' for key 'name'>
>  
> Java::ComMysqlJdbcExceptionsJdbc4::MySQLIntegrityConstraintViolationException:
>  Duplicate entry 'restriction_type' for key 'name'
>  
> java.lang.reflect.Constructor.newInstance(java/lang/reflect/Constructor.java:423)
> com.mysql.jdbc.Util.handleNewInstance(com/mysql/jdbc/Util.java:425)
> com.mysql.jdbc.Util.getInstance(com/mysql/jdbc/Util.java:408)
> com.mysql.jdbc.SQLError.createSQLException(com/mysql/jdbc/SQLError.java:935)
> com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3970)
> com.mysql.jdbc.MysqlIO.checkErrorPacket(com/mysql/jdbc/MysqlIO.java:3906)
> com.mysql.jdbc.MysqlIO.sendCommand(com/mysql/jdbc/MysqlIO.java:2524)
> com.mysql.jdbc.MysqlIO.sqlQueryDirect(com/mysql/jdbc/MysqlIO.java:2677)
> com.mysql.jdbc.ConnectionImpl.execSQL(com/mysql/jdbc/ConnectionImpl.java:2545)
> com.mysql.jdbc.StatementImpl.executeUpdateInternal(com/mysql/jdbc/StatementImpl.java:1540)
> com.mysql.jdbc.StatementImpl.executeLargeUpdate(com/mysql/jdbc/StatementImpl.java:2603)
> com.mysql.jdbc.StatementImpl.executeUpdate(com/mysql/jdbc/StatementImpl.java:1604)
> java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)
> 

Re: [Archivesspace_Users_Group] Problems working with archival object with large number of direct children

[James Bullen]

That could be useful thanks Jason.  Cheers — James


> On Nov 16, 2016, at 1:10 PM, Jason Loeffler <j...@minorscience.com> wrote:
> 
> 
> Thanks, James. Just wondering if there's a load test battery for a large 
> dataset. I can generate a large dataset if you think it is useful for your 
> work. 
> 
> 
> 
> 
> On Tue, Nov 15, 2016 at 6:56 PM -0500, "James Bullen" <ja...@hudmol.com 
> <mailto:ja...@hudmol.com>> wrote:
> 
> 
> Hi Jason - I’m not aware of a script like this.  Cheers — James
> 
> 
>> On Nov 16, 2016, at 10:28 AM, Jason Loeffler <j...@minorscience.com 
>> <mailto:j...@minorscience.com>> wrote:
>> 
>> Thanks so much, James. Can you tell me if there's a script available for 
>> generating an arbitrary number of test records? Something similar to 
>> Drupal's devel generate <https://api.drupal.org/api/devel/functions/8.x-1.x> 
>> hooks?
>> 
>> Jason Loeffler
>> Technology Consultant | The American Academy in Rome
>> Minor Science | Application Development & Metadata Strategy
>> Brooklyn, New York
>> ja...@minorscience.com <mailto:ja...@minorscience.com>
>> (347) 405-0826
>> minorscience (Skype)
>> 
>> 
>> 
>> On Tue, Nov 15, 2016 at 6:17 PM, James Bullen <ja...@hudmol.com 
>> <mailto:ja...@hudmol.com>> wrote:
>> 
>> Hi all,
>> 
>> As part of our new role as ArchivesSpace development partner, we will be 
>> addressing issues like this as a priority.
>> 
>> It is still early days and we’re working with the folks at the ArchivesSpace 
>> program on a release schedule, so we can’t make any definitive statements 
>> yet, but please know that we are aware of this issue and will address it as 
>> soon as we are able.
>> 
>> 
>> Cheers,
>> James
>> 
>> 
>> —
>> James Bullen
>> Hudson Molonglo
>> 
>> 
>> 
>>> On Nov 16, 2016, at 7:46 AM, Joshua D. Shaw <joshua.d.s...@dartmouth.edu 
>>> <mailto:joshua.d.s...@dartmouth.edu>> wrote:
>>> 
>>> Hi all –
>>>  
>>> We at Dartmouth have experienced similar issues. We have some large 
>>> resources as well (one has 60K+ objects in the tree) and anything that 
>>> involves a save or rearrangement (moving a file around, etc) can take a 
>>> *lot* of time (many minutes) and may cause an error – typically of the 
>>> “another user is modifying this record” type.
>>>  
>>> If we have to do any modifications to a resource of that size, we a) budget 
>>> a lot of time and b) do things in small increments – ie don’t move more 
>>> than a couple of files around at a time. It’s not a great solution, but it 
>>> does minimize some of the headache.
>>>  
>>> I *think* (but haven’t had the time to really dig into this) that one 
>>> reason the error comes about is because the indexer steps on/collides with 
>>> the process that the save/arrangement kicked off. We are still running 1.3 
>>> and hope that some of our issues will be mitigated when we move to 1.5.1, 
>>> though we know that not all of them have been resolved yet.
>>>  
>>> One other data point is that we’ve got a plugin that runs as a background 
>>> job doing a bunch of importing. This background job touches some of the 
>>> larger resources, but does *not* cause the errors and long save times, 
>>> which leads me to believe that a lot of the problem is in the frontend – 
>>> perhaps with the way the tree is populated - as Jason pointed out.
>>>  
>>> Best,
>>> Joshua
>>>  
>>> From: <archivesspace_users_group-boun...@lyralists.lyrasis.org 
>>> <mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>> on behalf 
>>> of Jason Loeffler <j...@minorscience.com <mailto:j...@minorscience.com>>
>>> Reply-To: Archivesspace Users Group 
>>> <archivesspace_users_group@lyralists.lyrasis.org 
>>> <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
>>> Date: Tuesday, November 15, 2016 at 3:25 PM
>>> To: Archivesspace Users Group 
>>> <archivesspace_users_group@lyralists.lyrasis.org 
>>> <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
>>> Cc: "archivessp...@googlegroups.com 
>>> <mailto:archivessp...@googlegroups.com>" <archivessp...@googlegroups.com 
>>> <mailto:archivessp...@googlegroups.com>>
>>> Subject: Re: [Archivesspace_Users_Group] Problems workin