Skip to content
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

Specific institute data fields (datapackage or table schema) #9

Open
cpina opened this issue Oct 27, 2020 · 0 comments
Open

Specific institute data fields (datapackage or table schema) #9

cpina opened this issue Oct 27, 2020 · 0 comments

Comments

@cpina
Copy link
Collaborator

cpina commented Oct 27, 2020

Some institutes might have extra fields to add outside the datapackage specification. For example see fields starting with "x_spi" in https://github.com/Swiss-Polar-Institute/frictionless-data-packages/blob/master/10.5281_zenodo.2636778/datapackage.json .

Fields in the datapackage

Example: x_spi_citation.

Two approaches:

  • An extension for the data package creator to pass field ids, field description and field label and to add them on the left hand side (after the keywords?) could be a solution to this. Supporting a list of options would be nice as well.
  • It could also be done 100% on the Django side: a new form asking for the extra, institution specific fields. This has the advantage of having more screen space and it's possibly easier to implement, validate, create templates, etc.

Fields in the table schema

Example: x_spi_cf_unit on each column table schema column.

Same as for the datapackage but for the Django side it might be hard for the user to understand on which column the data belongs to.

There should also be a way for the datamanager to specify the name, id and description, maybe the list of options for the fields. And if these fields belong to the tabular schema per column, tabular schema general information or the datapackage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant