What steps does it take to reproduce the issue?
Create a dataset, and in the "Related Publication" section's URL enter "https://doi.org/10.1130/0016-7606(1981)92<448:praral>2.0.co;2" (without quotes). When you save the dataset, an error message will appear informs you that there is a validation error, the dataset can not be created (of modified). The error message near the data element says that the https://doi.org/10.1130/0016-7606(1981)92<448:praral>2.0.co;2 is not a valid URL.
This is a working URL, DOI is resolvable and points to an article published in The Geological Society of America's GSA Bulletin. The URL is strange, and maybe it does not fit the formal rules of URL according to W3C (I haven't check it), however DOI accepted it, and it is a resolvable one, so browsers, and tools can work with it.
To make it more stranger the problem occurred when the user wanted to modify the Terms, not the metadata, so I guess a previous version of Dataverse allowed to enter this data, but our current (5.10.1) doesn't. The general error message is irrelevant at this place, because it does not tell if the error occured in the metadata section, not in the terms section, and the terms section does not contain any further details. So the nature of error is not understandable at all from the user's perspective.
When does this issue occur?
The the user click on the save changes button.
Which page(s) does it occurs on?
On dataset metadata editing page and on dataset terms editing page.
What happens?
Dataset is not saved. The error is properly displayed in the metadata editing page, but not in the dataset terms editing page.
To whom does it occur (all users, curators, superusers)?
All users who can edit the dataset.
What did you expect to happen?
The software should not identify a URL as invalid, if in practice it is not, and is used by DOI.
The software should not disallow values if once it was allowed, unless it is properly explained with version changes. The software should be compatible with older data.
The editing of the dataset Terms should not be blocked by an existing data in the metadata section.
The if an edition is blocked by validation of some other section (here Terms edition is blocked by value in Metadata), then the error message should be clear, and direct the user to the place where the error occurs.
Which version of Dataverse are you using?
5.10.1
Any related open or closed issues to this bug report?
I am not aware of that.
What steps does it take to reproduce the issue? Create a dataset, and in the "Related Publication" section's URL enter "https://doi.org/10.1130/0016-7606(1981)92<448:praral>2.0.co;2" (without quotes). When you save the dataset, an error message will appear informs you that there is a validation error, the dataset can not be created (of modified). The error message near the data element says that the https://doi.org/10.1130/0016-7606(1981)92<448:praral>2.0.co;2 is not a valid URL.
This is a working URL, DOI is resolvable and points to an article published in The Geological Society of America's GSA Bulletin. The URL is strange, and maybe it does not fit the formal rules of URL according to W3C (I haven't check it), however DOI accepted it, and it is a resolvable one, so browsers, and tools can work with it.
To make it more stranger the problem occurred when the user wanted to modify the Terms, not the metadata, so I guess a previous version of Dataverse allowed to enter this data, but our current (5.10.1) doesn't. The general error message is irrelevant at this place, because it does not tell if the error occured in the metadata section, not in the terms section, and the terms section does not contain any further details. So the nature of error is not understandable at all from the user's perspective.
When does this issue occur? The the user click on the save changes button.
Which page(s) does it occurs on? On dataset metadata editing page and on dataset terms editing page.
What happens? Dataset is not saved. The error is properly displayed in the metadata editing page, but not in the dataset terms editing page.
To whom does it occur (all users, curators, superusers)? All users who can edit the dataset.
What did you expect to happen?
Which version of Dataverse are you using? 5.10.1
Any related open or closed issues to this bug report? I am not aware of that.