Hi Jerry, I haven't seen an up-to-date ER diagram for ArchivesSpace (there were some early architecture documents), but you can reverse engineer one using MySQL workbench.
Workbench: https://www.mysql.com/products/workbench/ Directions: https://medium.com/@tushar0618/how-to-create-er-diagram-of-a-database-in-mysql-workbench-209fbf63fd03 I'd recommend doing it on a fresh database rather than your production database. --Rachel -- The information contained in this e-mail message is confidential. If you are not the intended recipient, any dissemination or copying is strictly prohibited. If you think that you have received this e-mail message in error, please contact the sender. On Mon, Dec 2, 2019 at 4:14 PM Boggio, Jerry <gbog...@mitre.org> wrote: > Hi ArchivesSpace Users; > > > > It appears we have found the answer to our question on > https://archivesspace.github.io/archivesspace/user/re-creating-indexes/. > By rebuilding the index files all records are now found from the MySQL > database. The issues seems to be related to refreshing the database in a > test environment from production, but the index files not picking up the > new records. Rebuilding the index files also appears to address the issue > we outlined in our eMail “Error browsing Resources in version 2.6”. > > > > One other observation we made when refreshing the database is that the > script archivesspace/scripts/setup-database.sh does not appear to work on > later refreshes. The firs time we ran the script, the beginning of the > output was as follows: > > > > [scripts]$ ./setup-database.sh > > Loading ArchivesSpace configuration file from path: > /apps/archivesspace/config/config.rb > > Loading ArchivesSpace configuration file from path: > /apps/archivesspace/config/config.rb > > Loading ArchivesSpace configuration file from path: > /apps/archivesspace/config/config.rb > > Running migrations against jdbc:mysql:// > mysqldev-a.mitre.org:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&autoReconnect=true > > I, [2019-10-18T13:24:53.944292 #48098] INFO -- : Begin applying migration > version 98, direction: up > > I, [2019-10-18T13:24:54.123838 #48098] INFO -- : Finished applying > migration version 98, direction: up, took 0.179616 seconds > > I, [2019-10-18T13:24:54.124897 #48098] INFO -- : Begin applying migration > version 99, direction: up > > I, [2019-10-18T13:24:54.290539 #48098] INFO -- : Finished applying > migration version 99, direction: up, took 0.165550 seconds > > I, [2019-10-18T13:24:54.291407 #48098] INFO -- : Begin applying migration > version 100, direction: up > > I, [2019-10-18T13:25:01.935442 #48098] INFO -- : Finished applying > migration version 100, direction: up, took 7.643832 seconds > > I, [2019-10-18T13:25:01.936657 #48098] INFO -- : Begin applying migration > version 101, direction: up > > I, [2019-10-18T13:25:02.357509 #48098] INFO -- : Finished applying > migration version 101, direction: up, took 0.420813 seconds > > I, [2019-10-18T13:25:02.358205 #48098] INFO -- : Begin applying migration > version 102, direction: up > > I, [2019-10-18T13:25:02.706000 #48098] INFO -- : Finished applying > migration version 102, direction: up, took 0.347575 seconds > > I, [2019-10-18T13:25:02.707015 #48098] INFO -- : Begin applying migration > version 103, direction: up > > Updating qaa-qtz to und > > Deleting enumeration_id for qaa-qtz > > I, [2019-10-18T13:25:03.059206 #48098] INFO -- : Finished applying > migration version 103, direction: up, took 0.352167 seconds > > : > > : > > > > After later refreshes, the output contained only these messages: > > > > [logs]$ more setup-database.log_20191202_1504 > > Loading ArchivesSpace configuration file from path: > /apps/archivesspace/config/config.rb > > Loading ArchivesSpace configuration file from path: > /apps/archivesspace/config/config.rb > > Loading ArchivesSpace configuration file from path: > /apps/archivesspace/config/config.rb > > Running migrations against jdbc:mysql:// > mysqldev-a.mitre.org:3306/archivesspace?user=[REDACTED]&password=[REDACTED]&useUnicode=true&characterEncoding=UTF-8&autoReconnect=true > > All done. > > [m91981@archspcdev1 logs]$ > > > > Does something need to be “reset” in a file or someplace else to allow the > database conversion to happen again? > > > > We would also still be interested in seeing document that identifies the > relationships between tables, if available. > > > > Please advise. > > > > Thank you! > > *Gerard (Jerry) Boggio* | *MITRE Corporation* | R504 - Collaboration & > Info Management | 781-271-2719 | Bedford, MA | 2K132 > > > > *From:* Boggio, Jerry <gbog...@mitre.org> > *Sent:* Wednesday, November 27, 2019 12:01 PM > *To:* archivesspace_users_group@lyralists.lyrasis.org > *Subject:* Accessions Query > > > > Hi ArchivesSpace Users; > > > > We are seeing an issue in our Linux based installation of version 2.6 > where we are not seeing all of my Accession records when selecting Browse > > Accessions. Could you please provide the SQL query used to populate that > page so that we may see if there is selection criteria being applied? With > that information we can compare to our SQL query going directly against the > database to identify differences. > > > > Is there also a document that identifies the relationships between tables > in ArchivesSpace? > > > > Thank you! > > *Gerard (Jerry) Boggio* | *MITRE Corporation* | R504 - Collaboration & > Info Management | 781-271-2719 | Bedford, MA | 2K132 > > > _______________________________________________ > 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