Datacite Schema 4.4

[Santiago Florez]

Hi everyone
I want to create a new personalization metadata block, but using the Datacite 4.4 schema, so I want to know your suggestions on that.
maybe you know what I have to do or keep in mind

[Julian Gautier]

Hey Santiago. 

Could you write more about what you mean by personalization? 

Are you the administrator of a planned or existing Dataverse installation or do you plan to work with an administrator to create this?

Have you seen the page and related links in the Dataverse Guides about metadata customization?

That page doesn't include everything that should be considered when creating a new metadata block. But broadly speaking it's important to be aware of the overlap between what metadata the DataCite schema asks for, what the Citation metadata block asks for, and why we suggest being cautious about making changes to the Citation metadata block, and how Dataverse tries to make certain metadata available in other metadata standards.

Lastly, folks at Harvard Dataverse are planning a series of webinars about Dataverse, and creating metadata blocks is a potential topic, so I plan on reaching out to you to learn more.

Regards,

Julian

[Santiago Florez]

Hi Julian
I mean to create a new metadata block following the datacite 4.4 schema or, maybe, update the metadata blocks, like citation.tvs, adding the new fields that are in the 4.4 schema.

[Julian Gautier]

Ah I see. Thanks!

We're happy to help more if you have more questions or comments about what I shared earlier. I'm hoping any follow up questions would help me think about what to focus on during those metadata webinars I mentioned.

[Santiago Florez]

I would like to know your opinion about updating the citation metadata blocks, adding the new fields in the 4.4 schema. And how can I do to change the export metadata with the 4.4 XML schema?

[Vaidas Morkevičius]

Santiago,

Have a look into materials produced by this project that we implemented: https://zenodo.org/communities/eosc_rda_project_framework.

--
Vaidas Morkevičius
https://lida.dataverse.lt

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/a670263a-1af8-4033-9811-19c46524ba1fn%40googlegroups.com.

[Julian Gautier]

Ooo, thanks for sharing, Vaidas.

Santiago, for changing the export metadata with the 4.4 XML schema, could you check out this section in the Dataverse guides about external exporters: 

https://guides.dataverse.org/en/latest/installation/advanced.html#installing-external-metadata-exporters. That's a new feature and from what I understand it should let you change the metadata that's included in that "DataCite" export.

My opinion about repositories changing the Citation metadata block is that it's fine. We know of at least a few Dataverse repositories that have changed things in their citation metadata blocks to include more information in the metadata that's included in the DataCite export and that's sent to DataCite, including the two repositories QDR and Repositorio de Datos del Consorcio Madroño. They and other repositories might also share their insights from making those changes and maintaining them as they update their forks of the Dataverse software.

Ideally the community works on changes that would ship with the software so that users' experiences describing, finding and using data is as similar as possible across Dataverse repositories, although each repository has different needs and users of course, so differences are understandable. I feel the same about deciding how the metadata is exported. We're working on finding the bandwidth for this kind of collaboration.

I think you might also find it helpful to review the conversations in the GitHub issues in the Dataverse repo about improving how Dataverse collects and distributes the kind of information DataCite asks for. Searching for "DataCite", like https://github.com/IQSS/dataverse/issues?q=is:issue+is:open+datacite, brings most or all of the issues up (plus other issues of course).

I guess the last thing I can say from my own experiences is that it's easier to make changes to the text that depositors and curators see in the user interface, like the names of fields and the tooltips, than it is to make other types of changes, like changing the structure of fields and adding new fields. But it can still be tricky. The Metadata text guidelines, referenced in that Metadata Customization page, should help.

Warm regards,

Julian

[Santiago Florez]

Thanks for everything, Julian and Vaidas
I am going to start experimenting with the guides you have provided. And I will keep you informed of my progress and doubts in the process.

--

You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/fa706e94-6404-4b6f-8016-c7724ebd86d1n%40googlegroups.com.

[Santiago Florez]

Hi Julian and Vaidas, me again

I have created a new metadatablock, but I want to create some selected fields, how can I do it?

These are the fields I want to convert to list.

Thanks Santiago Florez

[Gautier, Julian]

Hi Santiago Florez,

There are two ways to let others choose from a dropdown list when they're filling metadata fields. I'll try to summarize both.

For "locally controlled" lists

In this screenshot, I highlighted the parts of the citation metadata block's TSV file that are telling Dataverse to add a dropdown to the metadata block's "Subject" field so that depositors can choose from a list of subjects:

In the "allowControlledVocabulary" column that's highlighted in blue, you add TRUE. In the Metadata Customization guide, this column's called a "property" and is described in the #datafield (field) properties section.

I highlighted the "allowedMultiples" column in blue, too. Adding TRUE there lets depositors choose more than one option in the list.

Then in each row of the "#controlledVocabulary" section, highlighted in orange in that screenshot, you can add an option that depositors will see in the dropdown list and include a few other things about the option. The guide's #controlledVocabulary (enumerated) properties section describes the four columns or properties in this "#controlledVocabulary" section.

You'll also need to list the options in the .properties file for that metadata block. Here's what that looks like for that "Subject" field in the Citation metadata block:

This is described in the "#controlledVocabulary (enumerated) properties" section of the Metadata Customization guide.

I've read that what's described in the .properties file overrides what's in the TSV file, so I suppose for things like adding options to these dropdown lists, you need to edit only the .properties file. But I find it helpful to keep both files in sync.

For "externally controlled" lists

The Using External Vocabulary Services section of the Metadata Customization guide describes the Dataverse software's mechanism "to associate specific fields defined in metadata blocks with a vocabulary(ies) managed by external services". It also lists why you would want to use this mechanism instead of creating "locally controlled" lists (the first way I described).

I hope this helps!

ᐧ

[Santiago Florez]

Thanks Julian

I've maked the .properties file and modified the field's values of allowCntrolledVocabulary and allowmultiples. I execute all solar's comands and reboot payara5

This is my .tvs file

This is my .properties file

And this is like appear in the Dataverse installation 

I don't know what to do next

[Julian Gautier]

Ah great. I'm hoping others can hop in now. I haven't had success following the steps in the metadata customization guide for making these changes actually show up in the installation. But others who have often jump in to help.

[Santiago Florez]

Perhaps I was not clear. It does not appear as a selected type. I need something like this.

[Julian Gautier]

Ah right. When you wrote that you edited the TSV and .properties files, I figured that meant that you want a dropdown menu to appear when people click on those fields, although the type of dropdown menu will depend on the number of options in each list.

From what I can tell from your screenshots, it looks like everything is correct in your TSV and .properties files.

I assumed that you had taken the next steps in the Metadata Customization Guide in order to apply these changes in your Dataverse installation, such as the commands you need to run to update the metadata block and maybe do things related to SOLR indexing. But have you been able to follow those steps?

If you have tried but still aren't seeing dropdown menus, or if the guide isn't clear about what to do, then I'm hoping others in the community can join this conversation. I don't have experience with implementing the changes, such as running all of the commands. If we don't hear back from anyone, let's say by the end of the week, I can also try to ping specific people I know have been able to do this.

[Sherry Lake]

A few things to check:

Julian...... Looks like the metadataBlock "name" is the same as the datasetField "name. Shouldn't these be different? They are both:

linea_investigacion

linea_investigacion

It is hard to see if things (tabs) line up in your .tsv controlled vocabulary section. Do you have an empty column (extra tab between the "value" and "display order").

--

Sherry Lake

--

You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/6f773474-a2c7-4359-8ac6-52c8c6139554n%40googlegroups.com.

[Julian Gautier]

Thanks Sherry!

Is it a bit tough to see what's going on in the screenshots Santiago shared of the TSV file.  But yeah, the name of the metadata block can't be the same as the names of any of the metadata fields. The section of the guides that describes the #metadatablock-properties section of the TSV file says that the metadata block name can't "collide with a field of the same name in the same or any other #datasetField definition".

So maybe that's what's wrong, Santiago? You just need to change the name of the metadata block or the name of that one field?

[Philip Durbin]

Sherry and I helped Saniago out. All set: https://dataverse.zulipchat.com/#narrow/stream/378866-troubleshooting/topic/.E2.9C.94.20Custom.20metadata.20block

--

You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/801d290f-6d5c-4686-8f8f-7a9ee296b2f6n%40googlegroups.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Julian Gautier]

Ah very cool. Thanks for sharing that!

So to sum up, the issues were that the metadata block name was the same as the name of one of the fields and there were blank rows, and it doesn't help that Dataverse accepts TSV files that have these errors.

[Philip Durbin]

Yes, exactly. 😬

On Fri, Sep 29, 2023 at 2:18 PM Julian Gautier <julian...@g.harvard.edu> wrote:

Ah very cool. Thanks for sharing that!

So to sum up, the issues were that the metadata block name was the same as the name of one of the fields and there were blank rows, and it doesn't help that Dataverse accepts TSV files that have these errors.

--

You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/da2500f3-869e-48cc-9f39-dde8b2ec58f0n%40googlegroups.com.