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

Incorrect curl Example in Documentation Causes UI Fields to Disappear #11228

Open
ofahimIQSS opened this issue Feb 7, 2025 · 1 comment · May be fixed by #11229
Open

Incorrect curl Example in Documentation Causes UI Fields to Disappear #11228

ofahimIQSS opened this issue Feb 7, 2025 · 1 comment · May be fixed by #11229
Labels
Type: Bug a defect

Comments

@ofahimIQSS
Copy link
Contributor

Issue Summary:
On the guide CustomDatasetSummaryFields, the provided curl command example leads to unintended behavior. When executed, critical dataset fields such as Description, Subject, and License Agreement disappear from the UI on the dataset page.

Steps to Reproduce:
Navigate to the guide section: CustomDatasetSummaryFields. https://guides.dataverse.org/en/6.5/installation/config.html#customdatasetsummaryfields
Follow the provided curl command example:

curl http://localhost:8080/api/admin/settings/:CustomDatasetSummaryFields -X PUT -d 'producer,subtitle,alternativeTitle'

Refresh the dataset page.
Observe that fields like Description, Subject, and License Agreement are no longer visible on the UI.

Expected Behavior:
The curl command should only modify the fields displayed above the files table without removing critical dataset metadata (e.g., Description, Subject, License Agreement).

Actual Behavior:
Running the command results in the disappearance of essential dataset fields from the UI.

Image

@ofahimIQSS ofahimIQSS added the Type: Bug a defect label Feb 7, 2025
@qqmyers
Copy link
Member

qqmyers commented Feb 7, 2025

Looks like it is a bug that the license info disappears if there are no entries for any of the listed summary fields. I also noticed an inconvenience that the setting doesn't handle spaces after commas. Overall though, I think if you consider description and subject to be vital, you should add them to your list. The docs do say what the default is. I'll go ahead with a fix for the bug that removes the License field and support commas. If anyone thinks we should enforce a minimum set of fields beyond that, we can consider options.

@qqmyers qqmyers linked a pull request Feb 7, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug a defect
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants