Just to correct the record here ... Sorry, that wasn't PR 1822, it's 1882 that holds the change. Somehow I confused my numbers.
https://github.com/archivesspace/archivesspace/pull/1882 ________________________________ From: archivesspace_users_group-boun...@lyralists.lyrasis.org <archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Schanz, Megan <schan...@msu.edu> Sent: Tuesday, December 15, 2020 8:50 AM To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org> Subject: Re: [Archivesspace_Users_Group] Collection Organization not populating on v2.8.1 In case it helps anyone else, our issue was with the change to the default Solr query parameter in v2.8.0 (we were going to 2.8.1 from 2.7.1). The new default value: AppConfig[:solr_params] = { 'mm' => '100%' } Original value in 2.7.1: AppConfig[:solr_params] = { "q.op" => "AND" } The 'mm:100%' meant that when we had a query that OR'd a bunch of resources there would never be a record that had a 100% match on all of the criteria (one record couldn't have multiple IDs). Our understanding from PR 1882<https://urldefense.com/v3/__https://github.com/archivesspace/archivesspace/pull/1822__;!!HXCxUKc!ldN3U6NtcOocueWM76liwl7ZSJIP6agHL1Cj5kW74PFp4rEEl3iIERyAzn9mVVo$> (thanks for this link Blake), is that it is only for custom reporting. Since we're not doing anything with this we are just changing solr_params back to what worked for us in 2.7.1 and the collection organization is now populating as expected. - Megan ________________________________ From: archivesspace_users_group-boun...@lyralists.lyrasis.org <archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Schanz, Megan <schan...@msu.edu> Sent: Thursday, December 3, 2020 10:00 AM To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org> Subject: Re: [Archivesspace_Users_Group] Collection Organization not populating on v2.8.1 Thanks Blake. Unfortunately that doesn't seem to be our problem. We've tried a full re-index twice and they both completed without errors. I went into Solr and queried a sample resource and one of its archival objects; and both returned completed records. - Megan ________________________________ From: archivesspace_users_group-boun...@lyralists.lyrasis.org <archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Blake Carver <blake.car...@lyrasis.org> Sent: Wednesday, December 2, 2020 3:53 PM To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org> Subject: Re: [Archivesspace_Users_Group] Collection Organization not populating on v2.8.1 I'm not sure what to make of that JavaScript stuff, it might be related, though hopefully that's not the real problem. When you upgraded to 2.8, did you start over with a totally empty /data/ directory? If not, I'd suggest doing a full reindex. I know that indexing troubles can make those tabs empty when they should have stuff. Maybe it's looping or just not done yet, or something is wrong somehow. So... stop archivesspace rm -rf /data/* start archivesspace Let it run until the indexing is totally finished up, watch the logs for a loop and/or errors. ________________________________ From: archivesspace_users_group-boun...@lyralists.lyrasis.org <archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of Schanz, Megan <schan...@msu.edu> Sent: Wednesday, December 2, 2020 8:24 AM To: archivesspace_users_group@lyralists.lyrasis.org <archivesspace_users_group@lyralists.lyrasis.org> Subject: [Archivesspace_Users_Group] Collection Organization not populating on v2.8.1 Hi all, We've recently started testing v2.8.1 and are stuck on an issue on the public interface side. On the Collection Organization tab of a resource (i.e. repositories/4/resources/6423/collection_organization), the left-side pane is empty; whereas with v2.7.2 it contained the collection objects as you would expect. The data is identical between our test instance and our production instance so we are able to compare both versions side-by-side. When inspecting the page on the browser, we can see the top level object still populates with the correct data-urls, but there are no child objects underneath it: <div class="waypoint populated" data-waypoint-number="0" data-waypoint-size="20" data-uris="/repositories/4/resources/6423;/repositories/4/archival_objects/571053;/repositories/4/archival_objects/571055;/repositories/4/archival_objects/571057;/repositories/4/archival_objects/571061;/repositories/4/archival_objects/571063;/repositories/4/archival_objects/571065;/repositories/4/archival_objects/571067;/repositories/4/archival_objects/571069"> </div> Furthermore, the console is reporting errors coming from the Javascript code: Uncaught TypeError: Cannot read property 'replace' of undefined at Object.r.uri_to_parts (largetree-6541a51b3fceaac15ebc7b1a7f5155d473ee5cc35f3b337cb0ac844dd66f0666.js:1) at Object.r.uri_to_tree_id (largetree-6541a51b3fceaac15ebc7b1a7f5155d473ee5cc35f3b337cb0ac844dd66f0666.js:1) at e (treesync-0bcad7c81eb2991851e7ba2552a688032d6a805079546b7cb3cec080e69ed223.js:1) at treesync-0bcad7c81eb2991851e7ba2552a688032d6a805079546b7cb3cec080e69ed223.js:1 Uncaught TypeError: Cannot read property 'getBoundingClientRect' of undefined at n (infinite_scroll-16451f8d2fd84b07c84998a7bc75e9bad2276ca21b383c7098a623163ab40c66.js:1) at o.scrollToRecord (infinite_scroll-16451f8d2fd84b07c84998a7bc75e9bad2276ca21b383c7098a623163ab40c66.js:1) at infinite_scroll-16451f8d2fd84b07c84998a7bc75e9bad2276ca21b383c7098a623163ab40c66.js:1 No errors or warnings are being recorded in the logs on the server though. Has anyone else run into this issue or have ideas to further debug this? Thanks! Megan Schanz Developer and System Administrator Michigan State University Libraries
_______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
