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

Can not create a dataset, in a particular published dataverse #5936

Closed
Thanh-Thanh opened this issue Jun 12, 2019 · 6 comments
Closed

Can not create a dataset, in a particular published dataverse #5936

Thanh-Thanh opened this issue Jun 12, 2019 · 6 comments
Labels
Feature: Dataverse General Info Edit dataverse > "General Information" > Name, Alias, Email, Metadata Fields, et al... Feature: Metadata Type: Bug a defect

Comments

@Thanh-Thanh
Copy link
Contributor

Hi all,

We're upgrading to dataverse v4.10.1. We got 1 error when trying to create a dataset in a particular dataverse. And we've reproduced the bug on the demo website :

Within this dataverse https://demo.dataverse.org/dataverse/tests-ng-s123, we can not create any dataset, with the following error :

This page contains the following errors:
error on line 129 at column 17: AttValue: " or ' expected
Below is a rendering of the page up to the first error.

Thanks in advanced for any further information,

Best regards,
Thanh Thanh

@pdurbin
Copy link
Member

pdurbin commented Jun 12, 2019

Hi @Thanh-Thanh thanks for reporting this issue.

Last week this bit me as well. @pdante-ubc had reported a bug at #5929 about metadata blocks other than the citation block. It sounded like an annoying bug. So I went to the demo site to see if I could reproduce it. This is what I did:

  • Create new dataverse.
  • Turn on some extra metadata blocks besides just "citation" (under "Edit" then "General Information").
  • Save changes.

Then I went to create a dataset.

Click "New Dataset"

Screenshot from 2019-06-12 06-08-12

BOOM!!

Screenshot from 2019-06-12 06-08-17

This was very strange to me. I went back into "General Information" and the boxes I had checked for geospatial, social science, astronomy, etc were no longer checked. It looked like this:

Screenshot from 2019-06-12 06-09-08

I spoke with @kcondon and @sekmiller about it. The workaround (I think) is to check those boxes again (for geospatial or whatever) and click Save Changes. This issue seems to be related, if not the root cause of the bug: Add Dataset: Throws exception when on dataverse create, inherit metadata blocks is unchecked. #5613

@Thanh-Thanh
Copy link
Contributor Author

Thanks @pdurbin for the reference and the work-around. This is exactly what we have in fact. We have the same thing as #5613 in the server log...

@pdurbin
Copy link
Member

pdurbin commented Jun 12, 2019

@Thanh-Thanh ok, thanks for confirming this. Are you interested in working on a pull request? 😄

@Thanh-Thanh
Copy link
Contributor Author

@pdurbin :( I can not say yes this time. Actually we're busy to finish up others subjects that we've engaged. I'll come back on this later on if possible.
So sorry :(

@pdurbin
Copy link
Member

pdurbin commented Jun 13, 2019

@Thanh-Thanh no problem! You didn't introduce the bug! It's not your fault. 😄 Thank you for even considering fixing it for us!

I hope you or someone has time to take a look in the future. I'm happy to help find the right part of the code to look at.

@mheppler
Copy link
Contributor

I also saw locally on develop (v 4.15) the same problem that @Thanh-Thanh did. Confirmed it was related to the bug opened by @kcondon Add Dataset: Throws exception when on dataverse create, inherit metadata blocks is unchecked. #5613.

Closing this issue with the suggestion of following that older issue to track our progress resolving this bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Dataverse General Info Edit dataverse > "General Information" > Name, Alias, Email, Metadata Fields, et al... Feature: Metadata Type: Bug a defect
Projects
None yet
Development

No branches or pull requests

3 participants