We have hidden metadata when users are using a templetes.

[alejandratenorio]

What steps does it take to reproduce the issue?

As Admin user, choose the metadata fields to use in dataset templates and when adding a dataset, for example subtitle,

As admin user, we created a template and added custom instructions for subtitle,

As contributor user, create a dataset, select the template and subtitle metadata is hidden,

• When does this issue occur?

• When a contributor user create a dataset using o not a template.

• Which page(s) does it occurs on?

• Create a dataset

• What happens?

• When a contributor user create a dataset using o not a template.

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

• Each user that has contributor role.

• What did you expect to happen?

• When creating a dataset, the metadata fields configured for use in dataset templates or in templates should be displayed.

Which version of Dataverse are you using?
6.4

Any related open or closed issues to this bug report?
No

Screenshots:

No matter the issue, screenshots are always welcome.

To add a screenshot, please use one of the following formats and/or methods described here:

• https://help.github.com/en/articles/file-attachments-on-issues-and-pull-requests

Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?

[jggautier]

This is very interesting @alejandratenorio!

In your Dataverse installation, does the Subtitle field show up when first creating a dataset or only after editing a dataset that's already been created? Have you or your colleagues changed the citation.tsv file that ships with Dataverse so that for the subtitle field, the displayoncreate is TRUE? I'm wondering if that's related.

[qqmyers]

I think this is just because subtitle is not a field that is set to display on create. If you create the dataset and then go to edit metadata further, the subtitle field appears and will have the custom instructions of you're using the template. (tested on ~v6.5).

[pdurbin]

Right, I think you'd have to mark Subtitle as "required" to make it show up on the "create" page.

There's an open issue to avoid the need to mark a field as "required" to have it show up on the "create" page:

• Ensure Visibility of Non-Required Metadata Blocks on Dataset Creation #10476

[alejandratenorio]

citation.tsv

Hi @jggautier, the subtitle field appears after editing an already created dataset. We have the default citation.tsv.

[alejandratenorio]

Right, I think you'd have to mark Subtitle as "required" to make it show up on the "create" page.

Hi @pdurbin, yes we tested that, when Subtitle is marked as "required", it show up on the "create" page.

[alejandratenorio]

Ohhh, I have read, we should set it as true in displayoncreate.

[jggautier]

Ohhh, I have read, we should set it as true in displayoncreate.

Yeah. You could technically do either or both, right? I mean:

• In the TSV file, for the Subtitle field, if you set the displayoncreate column to TRUE, it will always appear on the "create" page and depositors won't need to fill it in in order to save the dataset.
• In the collection's General Information page, if you change the Subtitle field to required, it will appear on the "create" page because dataset versions can't be saved until all required fields are filled with valid metadata.

[alejandratenorio]

@jggautier Thanks! Now we can see the subtitle metadata when creating the dataset.

Something similar happens with a custom metadata block, even when the displayoncreate is set to true, they are not displayed until the dataset edit page. Has this happened to you?

[jggautier]

Hmmm, I've also helped work on new metadata blocks with certain fields whose displayoncreate is set to true, and those fields are displayed on the "create" page like we would expect.

When those fields aren't displayed on the "create" page, that sounds like a bug to me.

In your case, are the fields where displayoncreate is set to true not being displayed on the "create" page even when templates aren't used? I'm wondering if templates has anything to do with this unexpected behavior, too.

[qqmyers]

FYI: You might also be seeing #11214? That relates to existing templates after a new block is added. It also describes a work-around.

[alejandratenorio]

Dear @qqmyers, we applied the workaround and now the custom metadata block is being shown