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

Feature Request: Add Dataverse support for customizing placeholder text used by the external controlled vocabulary functionality #11109

Open
jggautier opened this issue Dec 18, 2024 · 1 comment
Labels
Feature: External Tool Feature: Metadata GREI 2 Consistent Metadata Requested SPA Improvement Desired improvement for SPA, do not duplicate JSF UI Type: Feature a feature request

Comments

@jggautier
Copy link
Contributor

jggautier commented Dec 18, 2024

Overview of the Feature Request
Dataverse itself needs to able to support the customization of the placeholder text (or watermarks) used by the external controlled vocabulary functionality, so that installations can more easily change the placeholder text, without having to fork the script used by the external controlled vocabulary functionality, and so that text can more easily be translated and displayed in other languages.

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Superuser, Sysadmin

What inspired the request?
The placeholder text was adjusted when the external controlled vocabulary functionality was used to change metadata fields on Demo Dataverse (see IQSS/dataverse.harvard.edu#327).

In that GitHub issue, @qqmyers wrote that the "ability to customize the placeholder dynamically is supported by the scripts, but evidently not in Dataverse itself," and that Dataverse will need to support customization of the placeholder text too so that Dataverse installation admins don't need to fork the script used by the external controlled vocabulary functionality, and so that the text can more easily be translated and displayed in other languages.

Any open or closed issues related to this feature request?
IQSS/dataverse.harvard.edu#327
IQSS/dataverse.harvard.edu#326

@cmbz
Copy link

cmbz commented Jan 13, 2025

2025/01/13: We'll discuss during the sprint planning meeting on 1/15.

@cmbz cmbz added SPA These changes are required for the Dataverse SPA Requested SPA Improvement Desired improvement for SPA, do not duplicate JSF UI and removed SPA These changes are required for the Dataverse SPA labels Jan 15, 2025
@cmbz cmbz removed the status in IQSS Dataverse Project Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: External Tool Feature: Metadata GREI 2 Consistent Metadata Requested SPA Improvement Desired improvement for SPA, do not duplicate JSF UI Type: Feature a feature request
Projects
Status: No status
Development

No branches or pull requests

2 participants