See
This is a (mostly) parallel universe built for testing:
- All database queries, inserts, deletes, and updates use a new database user (glcp) and database (GLCP_1) (the ‘production environment uses database user "perkins" and database "PERKINS" . The landscape -specific database tables are combined with the Perkins Museum rock collection tables — not an ideal commingling. I propose moving the GLCP tables out of PERKINS, using database GLCP for production and GLCP_1 for testing)
- database tables updated to include new metadata
- existing image files are drawn from production /:/perkins/ landscape ; newly added files go to test /:/perkins/ landscape_new_for_switch
- new temp files go to test /:/perkins/landscape_new_for_switch/TEMP
- all entry forms accessible from https://www.uvm.edu/perkins/ landscape_new_for_switch/submitting/submit_options.htm now include new metadata entry fields
- many items accessible from https://www.uvm.edu/perkins/ landscape_new_for_switch/WORKING_FOLDER/ include new metadata fields
- a good deal of code has been "modularized" such that the same code snippets can be used in several different scripts
- lots of other code was cleaned up and reorganized
- the total number of scripts needed has probably been cut in half
Still to do:
- glcp needs to test, test, test using TEST database
- when that is complete, test using PROD database and filesystem
- when THAT is complete, figure out how to elegantly move TEST code into PROD environment.
