Custom metadata block not displaying in dataset creation due to template issue

[Saixel]

What steps does it take to reproduce the issue?

1. Deploy a new custom metadata block in a collection.
2. Enable the metadata block in the collection (and its subcollections).
3. Create a dataset in a collection where a dataset template is applied by default.
4. The new metadata block appears in the dataset creation form but displays as empty instead of showing its fields.

When does this issue occur?

• When a new metadata block is deployed and enabled in a collection with an existing default dataset template.
• The issue happens when trying to create a dataset in that collection.

Which page(s) does it occur on?

• Dataset creation page.

What happens?

• The new metadata block appears in the dataset creation form but is empty (does not show its configured fields).
• This occurs in collections with an existing dataset template applied by default.

To whom does it occur (all users, curators, superusers)?

• Any user creating a dataset in a collection with an existing dataset template applied by default.

What did you expect to happen?

• New metadata blocks added to a collection should display their fields when creating a dataset, even if a dataset template is applied by default.

Which version of Dataverse are you using?

• Harvard Dataverse (Production) - v6.5

Any related open or closed issues to this bug report?

This issue appears to be related to how dataset templates handle new metadata blocks, preventing them from displaying correctly when a template is applied by default. A similar issue was reported in the past, indicating that this behavior might not be isolated.

• Discussion on metadata block creation, new block creation and deployment:
  • Issue #267 (Comment)
  • Create customCAFEAdditionalData metadata block with CCH Terms field dataverse.harvard.edu#318
  • Install customCAFEAdditionalData Metadata Block on Harvard Dataverse #11155
• Similar past issue: Issue #8704

Workaround (Temporary Solution)

• Editing the dataset template and adding a custom instruction to the new metadata field resolves the issue.
• Once saved, the metadata block starts displaying correctly.
• (Optional) The custom instruction can then be removed if not needed, and the metadata block remains functional.

Suggested Next Steps

Since this issue has affected multiple users, it may be worth investigating whether:

• Dataset templates should automatically refresh when a new metadata block is added.
• Or, clearer instructions should be provided on how to update templates when adding new metadata fields.

Are you thinking about creating a pull request for this issue?

Not at the moment, but I’m happy to assist with testing or providing further details if needed.

[cmbz]

• 2025/02/12: Sizing at 10 to conduct the investigation into exactly what is needed to create the fix. We can resize later once it's determined what is needed. There is a workaround at the moment for this bug.
• Talk to @Saixel for more details about reproducing the problem.