Re: [Archivesspace_Users_Group] Unable to edit / delete accessions or resources after upgrade to MySQL database

2021-07-15 Thread Andrew Morrison 
If the system isn't currently connected to the MySQL database, then it 
is likely it wasn't when the data migrations script 
 
was run. If so, that will need to be (re-)run once config.rb has been 
set up with the correct db_url. Once it has been, searching both PUI and 
staff interface won't find anything until a full re-index 
 
has been done.



Andrew.



On 14/07/2021 21:21, Blake Carver wrote:

It's hard to know for sure what's going on with this.
You were running 1.3 with MySQL and everything was fine?
They did the upgrade, you login and see everything is gone and it's 
running on Apache Derby... EEK!
You let them know, they connect it to MySQL again and now it's in this 
state.
So they probably hooked you up with your old 1.3 DB that has been 
upgraded to 2.8.1.
Or maybe it's set to talk to the wrong DB, and it's empty. If it's 
empty, maybe they have a backup of the old DB?
My guess is that they brought over the /data/ directory. That 
directory has all the solr stuff in it, and if they did bring that 
over, things are likely in this weird state.

I'd start by asking them a couple of questions

 1. Did they indeed hook you back to the old db that is now upgraded?
Are they sure the config is updated to talk to the right DB? They
should be able to search the DB directly to see what's in there.
 2. Did they copy over all the stuff in /data/ ? If so, you don't want
all that stuff. Tell them to empty that directory and restart it.


*From:* archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Merryman, Ann 

*Sent:* Wednesday, July 14, 2021 4:02 PM
*To:* Archivesspace Users Group 

*Subject:* [Archivesspace_Users_Group] Unable to edit / delete 
accessions or resources after upgrade to MySQL database


Good afternoon hive mind…long time lurker, first time writer. J  I’m 
going to try to make this question concise:


·I have just been upgraded to v2.8.1 (from v1.3.0…don’t judge!  Lol) 
on a locally-hosted instance of AS, managed by my university’s IT 
department.


·When my instance was upgraded, I got the following warning message:

*Database Warning:* You are currently using the embedded database 
(Apache Derby). The embedded database is for testing/demo purposes 
only. You should use MySQL for any data intended for production, 
including data in a test instance that you intend to move over to a 
production instance.


·The vendor let us know that there were not any upgrade paths from the 
demo database to MySQL, and the information would have to be 
re-entered (this is fine, as I had backed up everything and could 
re-enter)


·Once IT built the MySQL database, however, all the accession and 
resource records  actually showed up.  ???


The problem is, while I can **see** the records on the back end, I 
can’t edit or delete them. However, they are visible and searchable on 
the PUI.  I’ve attached a few images for reference.


I’m trying to determine what the best course of action might be before 
I go back to my IT department, as I’m going to have to explain what 
the issue is to them as best I can (they’re not really familiar with 
AS or archival processes, unfortunately).  I’m not clear on why the 
data pulled over if there wasn’t a path, and I’m not tech savvy enough 
to guess at what my IT department did.  I could also email AS tech 
support, but I thought I’d start here to see if anyone has seen this 
or has something to try first.


Any thoughts or suggestions from the group would be greatly 
appreciated, or even just sympathetic noises. J


Thanks so much,

Ann

“For the things we have to learn before we can do them, we learn by 
doing them.” ~ Aristotle


Ann E. Merryman, MLIS

Associate Librarian

Coordinator of Archives and Special Collections

USC Upstate, Library 263

800 University Way

Spartanburg, SC 29303

Office:  864-503-5275

merry...@uscupstate.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] Unable to edit / delete accessions or resources after upgrade to MySQL database

2021-07-14 Thread Blake Carver 
It's hard to know for sure what's going on with this.
You were running 1.3 with MySQL and everything was fine?
They did the upgrade, you login and see everything is gone and it's running on 
Apache Derby... EEK!
You let them know, they connect it to MySQL again and now it's in this state.
So they probably hooked you up with your old 1.3 DB that has been upgraded to 
2.8.1.
Or maybe it's set to talk to the wrong DB, and it's empty. If it's empty, maybe 
they have a backup of the old DB?
My guess is that they brought over the /data/ directory. That directory has all 
the solr stuff in it, and if they did bring that over, things are likely in 
this weird state.
I'd start by asking them a couple of questions

  1.  Did they indeed hook you back to the old db that is now upgraded? Are 
they sure the config is updated to talk to the right DB? They should be able to 
search the DB directly to see what's in there.
  2.  Did they copy over all the stuff in /data/ ? If so, you don't want all 
that stuff. Tell them to empty that directory and restart it.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Merryman, Ann 
Sent: Wednesday, July 14, 2021 4:02 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Unable to edit / delete accessions or 
resources after upgrade to MySQL database


Good afternoon hive mind…long time lurker, first time writer.  :)  I’m going to 
try to make this question concise:



·I have just been upgraded to v2.8.1 (from v1.3.0…don’t judge!  Lol) on 
a locally-hosted instance of AS, managed by my university’s IT department.

·When my instance was upgraded, I got the following warning message:

Database Warning: You are currently using the embedded database (Apache Derby). 
The embedded database is for testing/demo purposes only. You should use MySQL 
for any data intended for production, including data in a test instance that 
you intend to move over to a production instance.



·The vendor let us know that there were not any upgrade paths from the 
demo database to MySQL, and the information would have to be re-entered (this 
is fine, as I had backed up everything and could re-enter)

·Once IT built the MySQL database, however, all the accession and 
resource records  actually showed up.  ???



The problem is, while I can *see* the records on the back end, I can’t edit or 
delete them.  However, they are visible and searchable on the PUI.  I’ve 
attached a few images for reference.



I’m trying to determine what the best course of action might be before I go 
back to my IT department, as I’m going to have to explain what the issue is to 
them as best I can (they’re not really familiar with AS or archival processes, 
unfortunately).  I’m not clear on why the data pulled over if there wasn’t a 
path, and I’m not tech savvy enough to guess at what my IT department did.  I 
could also email AS tech support, but I thought I’d start here to see if anyone 
has seen this or has something to try first.



Any thoughts or suggestions from the group would be greatly appreciated, or 
even just sympathetic noises.  :)



Thanks so much,



Ann



“For the things we have to learn before we can do them, we learn by doing 
them.” ~ Aristotle



Ann E. Merryman, MLIS

Associate Librarian

Coordinator of Archives and Special Collections

[cid:image002.png@01D778C9.9E3A4EE0]

USC Upstate, Library 263

800 University Way

Spartanburg, SC 29303

Office:  864-503-5275

merry...@uscupstate.edu


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

Re: [Archivesspace_Users_Group] Unable to edit / delete accessions or resources after upgrade to MySQL database

2021-07-14 Thread Majewski, Steven Dennis (sdm7g) 

If you switched to a new DB, but did not delete the solr indexes in 
data/solr_index/ or deleted the files in data/indexer_state/ and 
data/indexer_pui_state/ to trigger a reindex then the data in DB and SOLR will 
be out of sync. 

If this is the case, the PUI, which pulls data from SOLR rather than the DB 
will be incorrect. 
The staff interface pulls data from both sources, depending on the action, and 
so will sometimes show you something in the index that isn’t there when you 
attempt to edit it. 

The backend API calls usually pull from the DB for non search functions. 

Ask them to delete the files in archivesspace/indexer*state/*  and wait for 
reindex to complete. 

— Steve Majewski


> On Jul 14, 2021, at 4:02 PM, Merryman, Ann  wrote:
> 
> Good afternoon hive mind…long time lurker, first time writer.  J  I’m going 
> to try to make this question concise:
>  
> ·I have just been upgraded to v2.8.1 (from v1.3.0…don’t judge!  Lol) 
> on a locally-hosted instance of AS, managed by my university’s IT department.
> ·When my instance was upgraded, I got the following warning message:
> Database Warning: You are currently using the embedded database (Apache 
> Derby). The embedded database is for testing/demo purposes only. You should 
> use MySQL for any data intended for production, including data in a test 
> instance that you intend to move over to a production instance.
>  
> ·The vendor let us know that there were not any upgrade paths from 
> the demo database to MySQL, and the information would have to be re-entered 
> (this is fine, as I had backed up everything and could re-enter)
> ·Once IT built the MySQL database, however, all the accession and 
> resource records  actually showed up.  ??? 
>  
> The problem is, while I can *see* the records on the back end, I can’t edit 
> or delete them.  However, they are visible and searchable on the PUI.  I’ve 
> attached a few images for reference. 
>  
> I’m trying to determine what the best course of action might be before I go 
> back to my IT department, as I’m going to have to explain what the issue is 
> to them as best I can (they’re not really familiar with AS or archival 
> processes, unfortunately).  I’m not clear on why the data pulled over if 
> there wasn’t a path, and I’m not tech savvy enough to guess at what my IT 
> department did.  I could also email AS tech support, but I thought I’d start 
> here to see if anyone has seen this or has something to try first.  
>  
> Any thoughts or suggestions from the group would be greatly appreciated, or 
> even just sympathetic noises.  J  
>  
> Thanks so much,
>  
> Ann
>  
> “For the things we have to learn before we can do them, we learn by doing 
> them.” ~ Aristotle
>  
> Ann E. Merryman, MLIS
> Associate Librarian
> Coordinator of Archives and Special Collections
> 
> USC Upstate, Library 263
> 800 University Way
> Spartanburg, SC 29303
> Office:  864-503-5275
> merry...@uscupstate.edu 
>  
>  1.JPG>___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org 
> 
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group 
> 


smime.p7s
Description: S/MIME cryptographic signature
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Unable to edit / delete accessions or resources after upgrade to MySQL database

2021-07-14 Thread Joshua D. Shaw 
I'm guessing your config file did not get updated to point to the new database. 
This line in the config needs to be uncommented and updated for your specific 
database setup:

## AppConfig[:db_url] = 
"jdbc:mysql://localhost:3306/archivesspace?user=as=as123=true=UTF-8"

You'll also need to add the mysql connector to /lib.

See: https://archivesspace.github.io/tech-docs/provisioning/mysql.html

Best,
Joshua


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Merryman, Ann 
Sent: Wednesday, July 14, 2021 4:02 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Unable to edit / delete accessions or 
resources after upgrade to MySQL database


Good afternoon hive mind…long time lurker, first time writer.  :)  I’m going to 
try to make this question concise:



·I have just been upgraded to v2.8.1 (from v1.3.0…don’t judge!  Lol) on 
a locally-hosted instance of AS, managed by my university’s IT department.

·When my instance was upgraded, I got the following warning message:

Database Warning: You are currently using the embedded database (Apache Derby). 
The embedded database is for testing/demo purposes only. You should use MySQL 
for any data intended for production, including data in a test instance that 
you intend to move over to a production instance.



·The vendor let us know that there were not any upgrade paths from the 
demo database to MySQL, and the information would have to be re-entered (this 
is fine, as I had backed up everything and could re-enter)

·Once IT built the MySQL database, however, all the accession and 
resource records  actually showed up.  ???



The problem is, while I can *see* the records on the back end, I can’t edit or 
delete them.  However, they are visible and searchable on the PUI.  I’ve 
attached a few images for reference.



I’m trying to determine what the best course of action might be before I go 
back to my IT department, as I’m going to have to explain what the issue is to 
them as best I can (they’re not really familiar with AS or archival processes, 
unfortunately).  I’m not clear on why the data pulled over if there wasn’t a 
path, and I’m not tech savvy enough to guess at what my IT department did.  I 
could also email AS tech support, but I thought I’d start here to see if anyone 
has seen this or has something to try first.



Any thoughts or suggestions from the group would be greatly appreciated, or 
even just sympathetic noises.  :)



Thanks so much,



Ann



“For the things we have to learn before we can do them, we learn by doing 
them.” ~ Aristotle



Ann E. Merryman, MLIS

Associate Librarian

Coordinator of Archives and Special Collections

[cid:image002.png@01D778C9.9E3A4EE0]

USC Upstate, Library 263

800 University Way

Spartanburg, SC 29303

Office:  864-503-5275

merry...@uscupstate.edu


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