LDP to Metadb Naming Conventions for CUL Report Queries

LDP to Metadb Query Naming Convention Process

Review and Prioritize queries by functional area
Archive queries no longer needed
Leave CR numbers in place, even if query is archived, to avoid confusion
To revise a CR or AHR query for LDP to Metadb format, use same CR or AHR number, but precede with M to maintain a connection between the 2 queries for testing purposes. For example, CR100 becomes MCR100, AHR120 becomes MAHR120
For new Metadb queries, we start in the 400 range, so MCR400 is the first metadb-only query
For new LDP report requests, revise to Metadb format as part of your report creation process, post both queries on cul-folio-analytics, connect LDP report only from Confluence (for now)
Reporting App – will create conventions for these queries later