-
Notifications
You must be signed in to change notification settings - Fork 500
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
Decoupling TSV metadata schema parsing from API endpoint #8085
Comments
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 3, 2021
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 3, 2021
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 3, 2021
- Use the Univocity annotations on the model - Add proper validation restrictions - Make the column headers (or future mappings) part of the model by adding a proper enum, representing the (TSV column) order and the key values
Closed
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 3, 2021
- Use the Univocity annotations on the model - Add proper validation restrictions - Make the column headers (or future mappings) part of the model by adding a proper enum, representing the (TSV column) order and the key values
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 6, 2021
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 6, 2021
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 6, 2021
- Make column headers part of the model class in a reusable fashion by using an enum plus constants. The enum also represent order and key values for the parser. - Add Univocity parsing annotations to setter methods of the model class - Add validation annotations where necessary - Add tests for everything
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 6, 2021
- Make column headers part of the model class in a reusable fashion by using an enum plus constants. The enum also represent order and key values for the parser. - Add Univocity parsing annotations to setter methods of the model class - Add validation annotations where necessary - Add tests for everything
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 7, 2021
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 7, 2021
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 7, 2021
…QSS#8085 - Add headers enum like with MetadataBlock and DatasetFieldType - Add a placeholder for alternate values that need references to the dataset field this CVV is a part of - Make the alternatives come from a column with a header (This is undocumented behaviour in the docs currently!) - Proper validation as with the other data bindings - Includes lot's of tests to make sure we notice when it breaks.
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 9, 2021
poikilotherm
added a commit
to poikilotherm/dataverse
that referenced
this issue
Sep 9, 2021
Isn't @JR-1991 doing some nice parsing of the TSVs in https://github.com/gdcc/easyDataverse ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, any TSV file loaded into a Dataverse instance flows through
DatasetFieldServiceApi.loadDatasetFields()
.This method isn't just the endpoint, it also contains all the code to parse and convert the TSV into living model objects.
This needs to be torn apart:
The text was updated successfully, but these errors were encountered: