Support for award amounts in DataCite metadata

[KellyStathis]

What is the problem that your suggestion solves?

When registering a DOI for an award, DataCite’s current recommendation is to record the award amount in the “Size” property:

Where applicable, include a quantity of resources provided by the award, including the numerical value + unit (e.g. EUR 10,000.00).

Size can be used for monetary awards or other types of quantifiable resources, such as computing time.

We’ve heard from funders and metadata harvesters that:

• It isn’t always intuitive to think of the award amount as the “size” of the award; and
• Because the Size property is unstructured free text, the amount and unit are combined in the same field, which is difficult to parse.

For awards, the size could be monetary (currency) or non-monetary (e.g., time). For example:

<sizes>
<size>1,000 CAD</size>
</sizes>

<sizes>
<size>40 hours</size>
</sizes>

What solution might meet your needs?

One possibility is introducing a “unit” attribute on the size property to help with parsing. For example, in XML:

<sizes>
<size unit="CAD">1000</size>
</sizes>

<sizes>
<size unit="hours">40</size>
</sizes>

This addition would need to be accompanied with guidance on what terms to use in the “unit” attribute. For example, when registering DOIs for monetary awards, standardized values for currency codes could be sourced from ISO 4217.

Your name

Kelly Stathis

Your organization

DataCite

What alternatives have you tried or considered?

No response

Is there anything else you would like to share?

No response

What group(s) would benefit from your suggestion?

• DataCite members registering DOIs and metadata and administering accounts
• Developers building integrations with DataCite services
• Harvesters who index DataCite DOIs and metadata
• Individuals or institutions analyzing DataCite DOIs and metadata
• DataCite staff
• Other

If other group(s), please describe.

No response

[Zack-83]

Thanks for starting this discussion!
We also possibly need a field for the funding budget in our project database (but would rather keep it confidential).
Working at a metrology institute, I would say that a unit is not enough to define the kind of quantity ;-) so I'd suggest to abandon the field "size", replacing it with more specific specifications: budget, time duration, output count etc., each one with the own unit.

[NOAAMetadataLib]

I have brought this up to DataCite myself here is my input

Your name
Jennifer Devine

Your organization
NOAA

What alternatives have you tried or considered?
We've been using Size with USD

Is there anything else you would like to share?
We would prefer a more intuitive field something along the lines of amount possibly?

What group(s) would benefit from your suggestion?

• [ Y ] DataCite members registering DOIs and metadata and administering accounts
• [ Y ] Developers building integrations with DataCite services
• [ Y ] Harvesters who index DataCite DOIs and metadata
• [ Y ] Individuals or institutions analyzing DataCite DOIs and metadata
• [ ? ] DataCite staff
• [ Y ] Other

If other group(s), please describe.
NOAA and others looking up Funding/Award DOIs.

Thanks, for binging this up Kelly!

[borsna]

In addition to a free text unit-property it would be nice to add a optional unitUri for the unit similar to other fields in DataCite where a vocabulary is used e.g:

<sizes>
  <size unitUri="http://qudt.org/vocab/currency/CAD" unitCode="CAD">1000</size>
</sizes>

<sizes>
  <size unitUri="http://qudt.org/vocab/unit/BYTE" unitCode="B">1000</size>
</sizes>

<sizes>
  <size unitUri="http://dbpedia.org/resource/Hour" unitCode="Hour">40</size>
</sizes>