-
Notifications
You must be signed in to change notification settings - Fork 493
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
Cannot use default metadata configuration after having datasets with custom metadata blocks #8471
Comments
For Dataverse 5.8 that line is a comment so I don't see how a NPE could be thrown: https://github.com/IQSS/dataverse/blob/v5.8/src/main/java/edu/harvard/iq/dataverse/DatasetPage.java#L1698 Are you running a fork? Thanks for participating in the community call just now. I wanted to give you this quick feedback but I'll try to circle back to this soon. |
I tested this on our Dataverse v5.8 installation and on a clean fork of the IQSS v5.9 repo using vagrant. The behaviour is the same. Below are the steps I performed to implement the custom metadata blocks. Perhaps this could give a hint for debugging or highlight an error in our deployment (I aggregated data from IQSS/dataverse/releases/tag/v5.8 > Upgrade Instructions and https://guides.dataverse.org/en/latest/admin/metadatacustomization.html:
NOTE: Some org.postgresql.util.PSQLException messages related to foreign keys already existing may be displayed
|
@j-n-c it's been on my list to test this and I'm sorry I haven't gotten to it yet. Thanks for testing 5.9. Would you be able to test the "develop" branch? Pull request #8454 was merged recently and it makes changes to the citation.tsv block. Basically, I'm simply wondering if you're seeing the same behavior or not. If you're able to test on develop, please mention the commit you're on when you reply. Thanks! |
@j-n-c I'm only now realizing that I should have asked you for your tsv file, the one that shows as "Custom Citation Metadata" in your screenshot? Can you please attach it in a comment? You'll probably have to rename it to end with .txt to upload it. Also, have you had a chance to try this on the "develop" branch? |
@pdurbin I have made more tests and have not had an issue adding new metadata fields or inserting fields into exiting ones. I think that the error I got was because I copied the citation.tsv file and added new fields with may have caused some issues due to duplicated identifiers for fields metadataBlock and datasetField. If you agree I will close this issue and open a new one if I ever come across any issues in the future. |
@j-n-c sounds great. I'm glad you're all set. Please do feel free to close this issue. I'm not surprised if you have trouble with two citation metadata blocks. You should probably change the new one enough to be a completely different block. |
@pdurbin both adding new fields to citation.tsv (making sure there are no repeated identifiers and that the display order field values are consiste) and creating a new metadata block worked for me. |
@j-n-c ok. Better to create a new block than to edit citation.tsv because we reserve the right to update the later. (We'll mention in release notes when to reload citation.tsv.) |
What steps does it take to reproduce the issue?
Which page(s) does it occurs on?
<dataverse_host>:8080/dataset.xhtml?ownerId=2
What happens?
To whom does it occur (all users, curators, superusers)?
Superuser
What did you expect to happen?
Which version of Dataverse are you using?
v5.8
Any related open or closed issues to this bug report?
Not that I coud find
Screenshots:
No matter the issue, screenshots are always welcome.
To add a screenshot, please use one of the following formats and/or methods described here:
The text was updated successfully, but these errors were encountered: