[Archivesspace_Users_Group] further info - 2.7.0 missing resources and unpublished repositories

[Walton, Donnelly]

Hi,

I believe we are having a similar problem with missing resources to the one this used had (thread below). I want to make sure before I proceed.

We noticed a few months ago when we were using 2.5.2 that a few resource records could not be retrieved with simple searches. They were all records that had been published and should have been available in both the staff and PUI version—there were in neither places. We eventually found them as linked resource records in accession records. We chose the “Publish All” function and this seemed to fix the problem.

Now in 2020 we have upgraded to 2.7.0. Unfortunately we just noticed that the same thing happened. This time it is not a published resource record.

Does this seem to be an issue with Java?

Thanks,
Donnelly

Donnelly Lancaster Walton
Archival Access Coordinator, Special Collections
University Libraries
The University of Alabama<https://www.ua.edu/>
W. S. Hoole Library, Mary Harmon Bryant Hall
Box 870266
Tuscaloosa, AL 35487
Office 205-348-0505<tel:205-348-0505>
dfwalton at ua.edu<mailto:dfwalton at ua.edu> | https://www.lib.ua.edu/libraries/hoole/
[The University of Alabama]<https://www.ua.edu/>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Kimberli Kelmor
Sent: Tuesday, November 19, 2019 7:39 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] further info - 2.7.0 missing resources and unpublished repositories

Final resolution of my issues for those following the issue:
1. - repositories missing: user error.
2. - mystery of the java version:
So on that Java Version... The Ruby Configuration is a collection of low-level information about your operating system, which gets created by mkconfig.rb when Ruby is compiled. It mostly contains compiler flags generated by Ruby’s compile scripts. Its exact contents depend on your system, and also on your Ruby implementation and version. All major Ruby implementations have a RbConfig.
I believe that is coming from the JRuby version we are using but only has to do with the java version for that JRuby version. Not with the version of java being built with or run with on your system. So it's just baked into the build when it's created.

So, we are in fact running 1.8 as the server indicated.

Thanks so much to Lyrasis support for  solving the mystery. (and for not making fun of the user error!)

Best regards,
Kimberli



On Mon, Nov 11, 2019 at 1:27 PM Kimberli Kelmor <kk1210 at georgetown.edu<mailto:kk1210 at georgetown.edu>> wrote:
Knowing that java version often impacts Aspace, I used java -version to check. It shows the server is running 1.8 (8). But, when I go to the Aspace backend, it lists java 1.7

Has anyone seen this before?
There is no Java_Home set, but alternatives --list also shows java 1.8

How do I tell Aspace to use java 8?
Thanks again!
Kim

--
Kimberli M. Kelmor
Head of Law Library Technology
Georgetown University Law Library
kk1210 at georgetown.edu<mailto:kk1210 at georgetown.edu>
202-662-9158


--
Kimberli M. Kelmor
Head of Law Library Technology
Georgetown University Law Library
kk1210 at georgetown.edu<mailto:kk1210 at georgetown.edu>
202-662-9158
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200129/a8a79252/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 6052 bytes
Desc: image001.gif
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20200129/a8a79252/attachment.gif>