10476 display on create field option #11224
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR introduces the
displayOnCreate
property to theDataverseFieldTypeInputLevel
class, allowing administrators to configure metadata fields to appear during dataset creation, even if they are not required.Previously, metadata fields selected for a collection would only appear during dataset creation if they were marked as required (or displayOnCreate by default). This change grants collection administrators control over metadata visibility, improving metadata completeness and discoverability.
Which issue(s) this PR closes:
Special notes for your reviewer:
This PR implements the functionality for
displayOnCreate
, but the UI implementation is not included yet.If you want to temporarily enable a checkbox for testing, you can manually add the following code snippet at line 384 of
dataverse.xhtml
. This will render a checkbox in the collection settings UI to toggle thedisplayOnCreate
property:Once the UI implementation is complete, this manual addition will no longer be necessary.
Suggestions on how to test this:
displayOnCreate
checkbox appears next to metadata fields.displayOnCreate
for a field and save the configuration.Does this PR introduce a user interface change? If mockups are available, please link/include them here:
No UI changes in this PR. A separate issue will track the UI implementation.
Additional documentation: