*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
-
Created by
Sharon Helen Markus, last updated on Jan 29, 2025
1 minute read
LDP = our current LDP reporting database
Metadb1 = our current Metadb Production reporting database
Metadb2 = a separate Metadb reporting database that does not become Metadb Production until updates, synchronization, and testing processes are complete (2-3 weeks)
| Date | Cornell Production Reporting Database | Environment Changes | Activity |
|---|---|---|---|
| February 3 - 7, 2025 | Metadb1 | LDP reporting database | Reporting Team sets up dashboards, automated reports, and other automation processes to use LDP as data source during cutover period |
| February 7, 2025 | LDP/Metadb1 | Metadb2 reporting database | Upgrade from PostgreSQL version 12 to version 16 |
| LDP/Metadb1 | Metadb2 reporting database | Update to folio-analytics v1.8.0-20241031174257 tagged release for derived tables | |
start February 7, 2025 end Feb 14 - 21, 2025 | LDP/Metadb1 | Metadb2 reporting database | Start data resynchronization process between FOLIO Production application server and Metadb reporting database |
for one week following synchronization end February 17-21 OR February 24-28 | LDP/Metadb1 | Metadb2 reporting database | Reporting Team tests data accuracy and performance on updated and resynchronized Metadb reporting database Reporting Team sets up dashboards, automated reports, and other automation processes to use Metadb as data source |
February 24-28 | LDP/Metadb1/Metadb2: depends on Go/No Go decision | LDP/Metadb1 is retired if decision is "Go" LDP/Metadb1 continues running if decision is "No Go" until Metadb2 is working properly | "Go/No Go" decision to use Metadb as Production Reporting Database and to retire LDP/ |