Make customized metadata block as "Required"

[Yan Na Cheng]

Hi all!

We created customized metadata block (CityUHK Metadata)  , and we want to make it "Required" and disable users to uncheck it (as same as citation metadata)
I tried to edit dataverse.xhtml but it only can visually (not functionally) make it disabled for editing.  Could please advice how I can set it up? Thank you!

N.B.

1. Our Dataverse version is v. 6.8 build 1994-92d1ec8
2. Solr version is 9.8.0

Regards,

Joanna Cheng

[Julian Gautier]

Hi Joanna,

Could you share a copy of the CityUHK Metadata TSV file?

I'm wondering what you have in the "required" column, if adding TRUE in that column for all fields will help, or if there's anything unexpected about the TSV file that's not making it work how we would expect.

All best,

Julian

Julian Gautier (he/him)

Product Research Specialist, IQSS

Interested in helping test Dataverse? Sign up for user experience research

[Yan Na Cheng]

Hi Julian, 

Thank you for replying my message. You may find the screen cap of CityUHK Metadata tsv file below.  Actually not all fields were set as "Required = TRUE " because not all fields are mandatory in norm.

  

 For the datavese citation metadata block (below) , there are some fields which are set as "Required = FALSE" so i think it is not the root reasons to make citation metadata block disabled for checking.

Regards,

Joanna Cheng

[Julian Gautier]

Ah, I understand more now. Thanks!

You're right. It looks like in the design of the Dataverse TSV file, the "required" column more specifically means that users creating and editing datasets will have to fill the required field as long as the metadata block is enabled in the collection. And I think we've always assumed that if the metadata block contains any required fields, the person managing the collections will enable the metadata block, or won't disable it, since they'd want people to fill the required fields.

That seems to not be true in your case, right? Have folks who manage collections in the CUHK Research Data Repository disabled this metadata block? Or if that hasn't happened yet, do you think that they might disable it, and you want to prevent that from happening?