-
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 Data Dictionary Resource View #106
Comments
+1 @jqnatividad to having a standard structure for a data dictionary for all resources - perhaps starting with DataStore hosted resources -http://docs.ckan.org/en/ckan-2.2/datastore.html - in particular I am interested in making this data dictionary content easily searched to make it easier to discover resources that may share common keys for integration (mashups) purposes. Not as concerned with markdown, and data-types and statistics - but field names and descriptions would be great - especially making them easily searchable. |
+1 @jqnatividad We are working on an excel addin that assists users to do some basic data QA, and record metadata about their datatset, including creating a Data Dictionary as you describe. We are also working on enabling it to post the data into CKAN (as tab separated files (one for each worksheet), or as a complete xlsx). Once we have it working to our satisfaction we will release it to the community for others to use (we are hopefully pretty close now). It would be good if any work on a ckan-datadictionary extension tied in with the format of data dictionary that we are using e.g.
|
Did anyone ever get the dictionary working at the resource level? |
This is now available :) BTW @Aaron-M , did you finish the work on the Excel add-in? I think it will still be useful! |
It'd be nice if datasets have a "Data Dictionary" resource view. Basically, it will have:
Not only will it be a great reference for dataset users, it can even double as a facility for the admin to unambiguously declare datastore datatypes- e.g. the field "date_created" is epoch time so treat it as a date, not just a number; and conversely, this "value" field is a number, not a timestamp (see ckan/ckan#1964 and as per @amercader, with datastore guessed types ckan/ckan#1794).
A ckanext-datadictionary extension perhaps?
The text was updated successfully, but these errors were encountered: