Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: daf_butler, dax_obscore
-
Labels:
-
Story Points:2
-
Epic Link:
-
Team:Ops Middleware
-
Urgent?:No
Description
While we are waiting to pgsphere installation at usdf-butler we can try to agree on what configuration is needed for obscore manager. The configuration determines the schema for obscore table, so it's best to try to nail it perfectly to avoid schema migrations later. A good starting point would be the configuration used for DP0.2 that was made to populate obscore table in QServ. Compared to that one, I expect few differences:
- I want to add few extra columns, in particular visit ID and exposure ID that are necessary for determining exposure region
- pg_sphere plugin configuration
- collection configuration, the CSV export tool could use any collection type, but manager configuration accepts RUN-type collection patterns (I think we are not ready for a single TAGGED collection case)
I think the main points in this exercise are:
- determine which repositories we want to obscore-ize
- for each repo define a list of collection names/patterns to include
- similarly dataset types
Once the configuration is settled, I can write migration script(s) to add it to the repositories.