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
category of a dataverse cannot be set via API #3371
Comments
Also, be more strict. Require ALL CAPS. We can always loosen this later.
I just created pull request #3373, tweaking the work by @bmckinney with a couple commits of my own. I moved this straight into QA at https://waffle.io/IQSS/dataverse because I don't feel like code review is necessary (Bill and I are happy with the code) and the change is small. The code is in the "sbgrid-json-migration" branch and here's how to test it:
I didn't document the possible values (maybe I should) but here they are (from the DataverseType enum in Dataverse.java):
|
I moved this issue straight to QA but the pull request itself I put in Code Review: #3373 |
@bmckinney can you please code review 203966f? For now I want the API to be more strict so I changed |
Thumbs, up. Thanks! |
@bmckinney great! I moved it to QA in https://waffle.io/IQSS/dataverse @kcondon instructions on how to test are at #3371 (comment) |
Please add json example to docs, thanks. |
Also expose database constraint violations via API.
@kcondon as we discussed I added a JSON example to the API Guide in 510b907 and while I was in there I improved the error reporting for when you don't send the right JSON to create a dataverse. I'm aware that a 500 error is still being thrown but at least you get a sense of which bean validation rules are not being obeyed. Passing back to you. |
Looks good, closing. |
In #3046 we introduced "Laboratory" as a dataverse category but it's impossible to set categories via API. This is an important feature for anyone migrating to Dataverse from another system, such as https://data.sbgrid.org which wants to set all dataverse categories to "Laboratory" during their migration.
The text was updated successfully, but these errors were encountered: