Carver
Sent: Wednesday, October 16, 2019 9:35 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4
to 2.6.0
If you brought over the /data/ directory, try getting rid of everything in
there and restarting. Could just be an index issue
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4
to 2.6.0
Hi Alex,
Great ideas, thank you! We didn’t get any errors when we ran the upgrade. I
just took a look at this resource in the Java console. I didn’t see any
obvious errors
lto:sd...@virginia.edu>>
Sent: Wednesday, October 16, 2019 12:15 PM
To: Archivesspace Users Group
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4
to 2.6.0
Error messages/images are too compressed
lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of
> Majewski, Steven Dennis (sdm7g)
> *Sent:* Wednesday, October 16, 2019 12:15 PM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Sub
Error messages/images are too compressed or small to read. Just a blur. Can
you resend or else transcribe ? — Steve M.
> On Oct 16, 2019, at 2:52 PM, Michael G Olson wrote:
>
> Hi everyone,
>
> Here at Stanford Libraries we just ran an upgrade from 1.5.4 to version 2.6.0
> and noticed
Hi everyone,
Here at Stanford Libraries we just ran an upgrade from 1.5.4 to version 2.6.0
and noticed some odd behavior we’d like to validate with our peers. We
received no error messages while running the upgrade. That said, for one of
our repositories (we have many) we’ve noticed that by
