-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add secondary table to hold Data Dictionary #101
Comments
I have not decided on the field names yet, but this is an example of a Data Dictionary |
Here is another. I would make the column headers standardized before upload.btaa-e776f983-39be-4417-81f4-9e91a6501c75.csv |
Just a note to say let's lock down the initial fields/schema for this table. Should be relatively simple to implement. |
Use these fields:
These will all be strings. Is it possible for the "values" field to be multivalued in some way? |
Yes, the values field can be an array — PostgreSQL supports that well.
…On Thu, Nov 14, 2024 at 4:57 PM Karen Majewicz ***@***.***> wrote:
Use these fields:
- label
- type
- values
- definition
- definition_source
These will all be strings. Is it possible for the "values" field to be
multivalued in some way?
—
Reply to this email directly, view it on GitHub
<#101 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAARBQ3YXKMYNIXBAAITW7T2AUTF5AVCNFSM6AAAAABQR4FDAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZXGU3TINBYGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
This proposal is for a simple table to hold the Data Dictionary for datasets. Features:
The text was updated successfully, but these errors were encountered: