...
- Once you appear to have a working Metadb version of your query, it is important to test it
- Do the LDP and Metadb versions of your query produce the same results? (assuming you have production data going to both LDP and Metadb)
- Ask someone else on the reporting team to test your query
Document and Publish Your Query
- With the move to Metadb, we are taking the opportunity to make our naming conventions and query documentation better and more consistent
- LDP to Metadb Query Naming Convention Process
- 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
- Post the Metadb version of your LDP Query on the cul-folio-analytics GitHub repository
- log into GitHub and navigate to new metadb section at https://github.com/cul-it/cul-folio-analytics/tree/main/metadb