DataCite Blog
  • Support
  • DataCite homepage

Updating our metadata schema suggestions process

December 13, 2022December 14, 2022 Kelly Stathis
https://doi.org/10.5438/vacd-ve62

As a community-driven organization, we believe it is critical that our members shape the DataCite metadata schema. The Metadata Working Group consists of 10-16 community representatives, who work on improving the metadata schema based on what we learn from the DataCite community. For the upcoming metadata schema 4.5, we launched our first community feedback process this fall to gather your input on the draft metadata schema. We’ve also heard that our community would like more involvement in shaping the metadata schema before changes reach the proposal stage. 

As of today, we’re launching a streamlined process for sharing your metadata schema ideas with us. We are also introducing a way to help you see which suggestions are on track for consideration in future versions, and to join community discussions about these suggestions.

We’ve refreshed our metadata schema website and added a new page outlining the process. Below, we want to highlight some of the key aspects of this change and explain what it means for you.

DataCite Metadata Schema suggestions process

Suggesting metadata schema changes

If you have a new idea for a change to the DataCite Metadata Schema, please let us know through the Metadata Schema Change Suggestions form. This form asks a few metadata-specific questions to help us understand what you’re requesting and what problem the change would solve.

Previously, we had asked that you submit schema change suggestions through our Product Roadmap. If you’re not sure if something is a schema change suggestion or not, don’t worry! We’ll still get your suggestion.

What happens to suggestions

All suggestions are first reviewed by the DataCite team. We want to make sure that in addition to understanding the proposed change, we understand the underlying problem you’re trying to solve. This helps us evaluate whether updating the DataCite Metadata Schema is the right solution to the problem and to consider other approaches. 

If your suggestion seems like a good fit for the DataCite Metadata Schema, we’ll add it to the DataCite Metadata Schema Trello board in the Community Discussion section to start gathering input from the DataCite community.

We prioritize ideas that have the potential to solve problems for many users. As part of the evaluation process, we look for patterns across suggestions, support tickets, and other sources. This means that most suggestions won’t be added to the board right away, but we are working on them behind the scenes.

How we are processing suggestions submitted previously

Previously, we had asked that you submit metadata schema change suggestions through our Product Roadmap. We received many ideas this way, and we currently have dozens in our backlog. At present, we are in the process of reviewing them to help prioritize changes for metadata schema 5.0 (and beyond). As we review them and determine prioritization, you’ll start to see more suggestions appear on the DataCite Metadata Schema Trello board.

(If you happen to submit a metadata schema suggestion through the Product Roadmap after today, don’t worry! While we encourage you to use the new metadata-specific form, we’ll still review your suggestion.)

How the metadata schema development stages work

Each stage on the DataCite Metadata Schema Trello board contains ideas that we’ve received. Ideas can move forwards and backwards through the stages depending on the progress of each stage.

Community Discussion

For ideas in Community Discussion, we are actively seeking input from the DataCite community.

We use the DataCite Chat Room category of the PID Forum to encourage open discussion of the ideas under consideration. We also may invite you to present your ideas in a DataCite Open Hours session (or we can present on your behalf).

The DataCite team decides when to forward ideas to the next stage—Metadata Working Group Discussion—based on several factors, including the level of community support, feasibility, and resources. This means that while some changes will move to the next stage quickly, others may remain in community discussion for longer.

Once an idea is no longer under consideration—usually due to lack of community support—it may be removed from this board. If this changes, we can always resurface the idea.

Metadata Working Group Discussion

These ideas have been forwarded to the DataCite Metadata Working Group. In this stage, the DataCite Metadata Working Group is actively considering—or about to consider—how to adapt the DataCite Metadata Schema to solve the underlying problem.

During this stage, we’re still seeking input from the DataCite community, and you can continue to contribute to discussions.

Because each metadata schema version takes around one to two years to complete, ideas typically remain in this stage for at least one year. If the Metadata Working Group determines that the optimal solution involves breaking changes—changes which are incompatible with the previous version— the idea could stay here for even longer. This is because we can only introduce breaking changes in major versions (4.0, 5.0, etc.).

Once the Metadata Working Group has finalized a proposal for the next metadata schema version, ideas included in that proposal will be moved to the next stage: Proposed.

Proposed

Ideas with proposed changes are on track to be included in the next metadata schema release, pending community feedback.

During this stage, we’re looking for input on the proposed change, which may be different from the original idea. For this reason, we encourage you to follow the instructions on the card for participating in our community feedback process.

Released

Released ideas have corresponding changes that have been included in a recent metadata schema release. (Since the board is new, there’s nothing yet—you’ll see the metadata schema 4.5 changes move here as they are finalized.)

Help us shape metadata schema 5.0

If you have an idea for the metadata schema, please let us know through the Metadata Schema Change Suggestions form. We also encourage you to check out the DataCite Metadata Schema Trello board to see what we’re working on and participate in the linked community discussions on the PID Forum.

Photo of Kelly Stathis
Kelly Stathis
Blog posts
  • Kelly Stathis
    https://blog.datacite.org/author/kelly-stathisdatacite-org/
    Welcome our new DataCite Committee Members
  • Kelly Stathis
    https://blog.datacite.org/author/kelly-stathisdatacite-org/
    Full API support for DataCite Metadata Schema 4.4
  • Kelly Stathis
    https://blog.datacite.org/author/kelly-stathisdatacite-org/
    Towards richer metadata - perspectives from three DataCite projects
  • Kelly Stathis
    https://blog.datacite.org/author/kelly-stathisdatacite-org/
    ConfIDent about PIDs: Using DataCite DOIs for Conferences

Share this:

  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
Metadata, Metadata Schema.

© 2022 Kelly Stathis. Distributed under the terms of the Creative Commons Attribution license.


Post navigation

Mind the gap – what to expect when practicing FAIR
DataCite Celebrate and Reflect on a Year of Global Community Collaboration

Recent Posts

  • New Release of Fabrica: Improvements Inspired by User Feedback
  • Welcome our new DataCite Committee Members
  • Wellcome Trust and the Chan Zuckerberg Initiative Partner with DataCite to Build the Open Global Data Citation Corpus
  • Full API support for DataCite Metadata Schema 4.4
  • DataCite Celebrate and Reflect on a Year of Global Community Collaboration

Tags

Anniversary (3) API (3) Bibliometrics (2) Citation (8) Conference (2) Content negotiation (2) Crossref (10) CSV (4) Data-level metrics (9) Data citation (7) Discovery (2) Docker (3) DOI (18) Dublin core (2) Fabrica (4) FAIR (5) FORCE11 (2) FREYA (8) Github (2) Google (2) GraphQL (7) IGSN (5) Impactstory (2) Infrastructure (13) MDC (7) Members (11) Metadata (34) Open hours (2) ORCID (17) Organization identifiers (4) PIDapalooza (5) PID graph (8) Policy (2) RDA (8) Re3data (11) React (2) ROR (5) Schema.org (3) Search (3) Services (5) Software (2) Software citation (5) Staff (6) Strategy (2) THOR (13)

Archives

  • January 2023 (4)
  • December 2022 (4)
  • November 2022 (3)
  • October 2022 (5)
  • September 2022 (6)
  • August 2022 (3)
  • July 2022 (1)
  • June 2022 (3)
  • May 2022 (1)
  • April 2022 (1)
  • March 2022 (2)
  • February 2022 (3)
  • January 2022 (1)
  • December 2021 (2)
  • November 2021 (3)
  • October 2021 (5)
  • August 2021 (2)
  • July 2021 (2)
  • June 2021 (1)
  • May 2021 (2)
  • April 2021 (2)
  • March 2021 (2)
  • February 2021 (3)
  • January 2021 (3)
  • December 2020 (1)
  • November 2020 (2)
  • October 2020 (4)
  • September 2020 (4)
  • August 2020 (3)
  • July 2020 (3)
  • June 2020 (2)
  • May 2020 (3)
  • April 2020 (2)
  • March 2020 (2)
  • February 2020 (4)
  • January 2020 (4)
  • December 2019 (3)
  • November 2019 (3)
  • October 2019 (5)
  • September 2019 (3)
  • August 2019 (3)
  • July 2019 (3)
  • June 2019 (2)
  • May 2019 (5)
  • April 2019 (6)
  • March 2019 (2)
  • February 2019 (5)
  • January 2019 (1)
  • December 2018 (4)
  • November 2018 (3)
  • October 2018 (4)
  • September 2018 (4)
  • August 2018 (4)
  • June 2018 (4)
  • May 2018 (4)
  • April 2018 (1)
  • February 2018 (3)
  • January 2018 (1)
  • November 2017 (2)
  • October 2017 (2)
  • August 2017 (4)
  • July 2017 (1)
  • June 2017 (1)
  • May 2017 (2)
  • April 2017 (5)
  • March 2017 (2)
  • January 2017 (1)
  • December 2016 (4)
  • November 2016 (2)
  • October 2016 (5)
  • September 2016 (3)
  • August 2016 (1)
  • July 2016 (3)
  • June 2016 (1)
  • May 2016 (6)
  • April 2016 (5)
  • March 2016 (5)
  • February 2016 (2)
  • January 2016 (2)
  • December 2015 (3)
  • November 2015 (3)
  • October 2015 (8)
  • September 2015 (5)
  • August 2015 (6)

About

  • What we do
  • Governance
  • Members
  • Steering groups
  • Team
  • Job opportunities

Services

  • Create DOIs with Fabrica
  • Discover metadata with Commons
  • Integrate with APIs
  • Partner services

Resources

  • Metadata schema
  • Support
  • Fee model

Community

  • Members
  • Partners
  • Steering groups
  • Service providers
  • Roadmap
  • FAIR Workflows

Contact us

  • Imprint
  • Terms and conditions
  • Privacy policy
  • Mail
  • RSS Feed
  • Twitter
  • Mastodon
  • GitHub
  • YouTube
  • LinkedIn
We use cookies on our website. Some are technically necessary, others help us improve your user experience. You can decline non-essential cookies by selecting “Reject”. Please see our Privacy Policy for further information about our privacy practices and use of cookies.
RejectAccept
Manage consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT