(DRAFT) Metadb Rollout Plan

• hosting team sets up accounts for reporting team members
• reporting team members test and verify their connections to Metadb Test through DBeaver EE
• Virtual DBeaver connection configurations for Metadb are researched and tested

• hosting team sets up accounts for reporting users of specialized local schemas and those users test and verify their connections to Metadb Test
• hosting team sets up local schemas on Metadb Test, providing access to each of the users for those schemas
• schema users test access and writing data to their local schemas

• hosting team creates VGER schema and moves legacy system Voyager tables from LDP to Metadb
• reporting team tests tables in VGER schema on Metadb

• subset of reporting team creates training materials on Metadb to deliver to reporting users
• Metadb training delivered to reporting team for feedback

Metadb Test Rollout

Critical LDP reports only and Metadb user account setups

• January 1, 2024: Announcement to CUL that Reporting Team will be working on transition to Metadb, so only critical LDP queries or dashboards should be requested
• Metadb Test setup for reporting users researched and tested
• All user accounts in Metadb Test created 
• Metadb training delivered to RUG, then all CUL reporting users

• FOLIO Production moves to Poppy in February 2024
• Metadb Test moves to Poppy version of Folio Analytics
• Reporting Team configures FOLIO Reporting App to run basic reports against Metadb Test
• Reporting Team rewrites LDP queries for Metadb and updates dashboards to use Metadb queries
• Revise Reporting Tips and Tricks pages to cover Metadb

Reporting App Rollout

• Metadb Production is created using Metadb Test as a template
• Reporting Team tests queries and dashboards on Metadb Production
• Reporting Team configures FOLIO Reporting App to run reports with parameters against Metadb Production
• Reporting Users are trained in using Reporting App