Latest blog posts
Kathleen Luschek
2020 October 13

Calling all 24-hour (PID) party people!

While we wish we could be together in person to celebrate the fifth PIDapalooza, there’s an upside to moving it online: now everyone can participate in the universe’s best PID party! With 24 hours of non-stop PID programming, you’ll be able to come to the party no matter where you happen to be. Send us your ideas for #PIDapalooza21 Now is your chance to share your work in the #PIDapalooza21 spotlight!

...Find out more
Rachael Lammey
2020 October 12

EASE Council Post: Rachael Lammey on the Research Nexus

This blog was initially posted on the European Association of Science Editors (EASE) blog: “EASE Council Post: Rachael Lammey on the Research Nexus”. EASE President Duncan Nicholas accurately introduces it as a whole lot of information and insights about metadata and communication standards into one post… I was given a wide brief to decide on the topic of my EASE blog, so I thought I’d write one that tries to encompass everything - I’ll explain what I mean by that.

...Find out more
Lucy Ofiesh
2020 September 28

2020 Board Election

This year, Crossref’s Nominating Committee assumed the task of developing a slate of candidates to fill six open board seats. We are grateful that in the midst of a challenging year, we received over 70 expressions of interest from all around the world, a 40% increase from last year’s response. It was an extraordinary pool of applicants and a testament to the strength of our membership community. There are six seats open for election (two large, four small), and the Nominating Committee is pleased to present the following slate.

...Find out more
Ludo Waltman
2020 September 25

Open Abstracts: Where are we?

The Initiative for Open Abstracts (I4OA) launched this week. The initiative calls on scholarly publishers to make the abstracts of their publications openly available. More specifically, publishers that work with Crossref to register DOIs for their publications are requested to include abstracts in the metadata they deposit in Crossref. These abstracts will then be made openly available by Crossref. 39 publishers have already agreed to join I4OA and to open their abstracts.

...Find out more
  • Menu
search

The Crossref Curriculum

Funding data overview

The funding data service lets members register funding source information for content items deposited with Crossref.

Things to understand before you deposit

  • Funding metadata must include the name of the funding organization and the funder identifier (where the funding organization is listed in the Registry), and should include an award/grant number. Funder names should only be deposited without the accompanying ID if the funder is not found in the Registry. These deposits will not be considered valid records until such a time as the funder is added to the database and they are redeposited (updated) with an ID.

  • Correct nesting of funder names and identifiers is essential as it significantly impacts how funders, funder identifiers, and award numbers are related to each other.

Correct: In this example, funder “National Science Foundation” is associated with the funder identifier https://0-doi-org.lib.rivier.edu/10.13039/100000001

<fr:assertion name="funder_name">National Science Foundation
     <fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039/10000001</fr:assertion>
 </fr:assertion>

Incorrect: Here, the funder name and funder identifier are not nested - these assertions will be indexed as separate funders.

<fr:assertion name="funder_name">National Science Foundation</assertion>
 <fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039/10000001</fr:assertion>
  • The purpose of funder groups is to establish relationships between funders and award numbers. A funder group assertion should only be used to associate funder names and identifiers with award numbers when multiple funders are present. Funding data deposit with one group of funders (no “fundgroup” needed):
One group of funders

Funding data deposit with two fundgroups:

Two fundgroups
  • Incorrect: Groups used to associate funder names with funder identifiers, these need to be nested as described above.
Groups not nested - incorrect
  • Deposits using a funder_identifier that is not taken from the Funder Registry will be rejected.
  • Deposits with only funder_name (no funder_identifier) are not considered valid funding data deposits and will not appear in funder search results in Funder Registry search or the REST API.

Funding data and Crossmark

If you participate in Crossmark, you should nest funding data within the <crossmark> element, for example:

<crossmark>
     <crossmark_version>1</crossmark_version>
     <crossmark_policy>10.5555/cm_1</crossmark_policy>
          <updates>
         <update type="correction" label="Correction" date="2011-04-10">10.5555/cm_test2.1</update>
     </updates>
     <custom_metadata>
         <assertion name="received" label="Received" group_name="publication_history" group_label="Publication History">2011-04-12</assertion>
         <fr:program name="fundref">
            <fr:assertion name="funder_name">IMA Funder
                    <fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039/xxxxxxxxxx</fr:assertion>              
              </fr:assertion>                    
              <fr:assertion name="award_number">HPC-227</fr:assertion>   </fr:program>
</custom_metadata>
 </crossmark>

If you do not participate in Crossmark, you may deposit funding metadata along with article metadata, for example:

<publication_date media_type="print">
​     <year>2011</year>
   </publication_date>
   <pages>
 	<first_page>15</first_page>
   </pages>
    <fr:program name="fundref">
      <fr:assertion name="funder_name">ABC Inc.
      <fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039/xxxxxxxxxx</fr:assertion>
          </fr:assertion>  
 <fr:assertion name="award_number">BXDFSDS</fr:assertion>
    </fr:program>
   <doi_data>
      <doi>10.5555/cm_test_1.1</doi>
      <resource>https://0-www-crossref-org.lib.rivier.edu/crossmark/index.html</resource>
	</doi_data>
  </journal_article>

Funding data schema section

The <fr:program> element in the deposit schema section (see documentation) supports the import of the fundref.xsd schema (see documentation). The fundref namespace (xmlns:fr=https://0-www-crossref-org.lib.rivier.edu/fundref.xsd) must be included in the schema declaration, for example:

<doi_batch xmlns="https://0-www-crossref-org.lib.rivier.edu/schema/4.3.6" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:fr="https://0-www-crossref-org.lib.rivier.edu/fundref.xsd"xsi:schemaLocation="https://0-www-crossref-org.lib.rivier.edu/schema/4.3.6 https://0-www-crossref-org.lib.rivier.edu/schemas/crossref4.3.6.xsd" version="4.3.1">

To accommodate integration with Crossmark, the fundref.xsd consists of a series of nested <fr:assertion> tags with enumerated name attributes. The name attributes are:

  • fundgroup: used to group a funder and its associated award number(s) for items with multiple funders.
  • funder_name: name of the funding agency as it appears in the funding Registry. Funder names that do not match those in the registry will be accepted to cover instances where the funding organization is not listed.
  • funder_identifier: funding agency identifier in the form of a DOI, must be nested within the funder_name assertion. The funder_identifier must be taken from the funding Registry and cannot be created by the member. Deposits without funder_identifier do not qualify as funding records.
  • award_number: grant number or other fund identifier
  • funder_name and funder_identifier must be present in a deposit where the funding body is listed in the Funder Registry. Multiple funder_name, funder_identifier, and award_number assertions may be included.

Funder and award number hierarchy

A relationship between funder_identifier and funder_name is established by nesting funder_identifier within funder_name. For example, this deposit has the funder National Science Foundation with its corresponding funder identifier in the funding Registry of https://0-doi-org.lib.rivier.edu/10.13039.10000001:

    <fr:assertion name="funder_name">National Science Foundation
         <fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039.10000001</fr:assertion>
      </fr:assertion>

A relationship between a single funder_name and/or funder_identifier and an award_number is established by including assertions with a <fr:program>. In this example, funder National Institute on Drug Abuse with funder identifier https://0-doi-org.lib.rivier.edu/10.13039/R01ZDA are associated with award number JQY0937263:

 <fr:program name="fundref">
      <fr:assertion name="funder_name">National Institute on Drug Abuse
         <fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039/R01ZDA</fr:assertion>
      </fr:assertion>
      <fr:assertion name="award_number">JQY0937263</fr:assertion>
   </fr:program>

If multiple funder and award combinations exist, each combination should be deposited within a fundgroup to ensure that the award number is associated with the appropriate funder(s). In this example, two funding groups exist:

  1. Funder National Science Foundation with funder identifier https://0-doi-org.lib.rivier.edu/10.13039/100000001 is associated with award numbers CBET-106 and CBET-106, and
  2. Funder Basic Energy Sciences, Office of Science, U.S. Department of Energy with funder identifier https://0-doi-org.lib.rivier.edu/10.13039/100006151 is associated with award number 1245-ABDS.
<fr:program name="fundref">
     <fr:assertion name="fundgroup">
        <fr:assertion name="funder_name">National Science Foundation
            <fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039/100000001</fr:assertion>
        </fr:assertion>
        <fr:assertion name="award_number">CBET-106</fr:assertion>
        <fr:assertion name="award_number">CBET-7259</fr:assertion>
     </fr:assertion>
    <fr:assertion name="fundgroup">
        <fr:assertion name="funder_name">Basic Energy Sciences, Office of Science, U.S. Department of Energy
            <fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039/100006151</fr:assertion>
        </fr:assertion>
        <fr:assertion name="award_number">1245-ABDS</fr:assertion>
     </fr:assertion>
</fr:program>

Items with multiple funder names but no award numbers may be deposited without a fundgroup.

At a minimum, a funding data deposit must contain a funder_name and funder_identifier assertion. Deposits with just an award_number assertion are not allowed. A funder_name, funder_identifier, and award_number should be included in deposits whenever possible.

If the funder name cannot be matched in the Registry, you may submit funder_name only, and the funding body will be reviewed and considered for addition to the official Registry. Until it is added to the Registry, the deposit will not be considered a valid funding record and will not appear in funding search or the REST API.

As demonstrated in Example 3 below, items with several award numbers associated with a single funding organization should be grouped together by enclosing the funder_name, funder_identifier, and award_number(s) within a fundgroup assertion.

Some rules will be enforced by the deposit logic, including:

  • Nesting of the <fr:assertion> elements: the schema allows infinite nesting of the assertion element to accommodate nesting of an element within itself. Deposit code will only allow 3 levels of nesting (with attribute values of fundgroup, funder_name, and funder_identifier)
  • Values of different <fr:assertion> elements: funder_name, funder_identifier, and award_number may have deposit rules imposed
  • Only valid funder identifiers will be accepted: the funder_identifier value will be compared against the Open Funder Registry file. If the funder_identifier is not found, the deposit will be rejected.

Deleting or updating funding metadata

If funding metadata is incorrect or out-of-date, it may be updated by redepositing the metadata. Be sure to redeposit all available metadata for an item, not just the elements being updated. A DOI may be updated without resubmitting funding metadata, as previously deposited funding metadata will remain associated with the DOI.

Funding metadata may be deleted by redepositing an item with an empty <fr:program name="fundref"> element:

Deleting non-Crossmark funding metadata

 <publication_date media_type="print">  	<year>2011</year>
   </publication_date>
   <pages>
 	<first_page>15</first_page>
   </pages>       
   <fr:program name="fundref" />
   <doi_data>
      <doi>10.5555/cm_test_1.1</doi>
      <resource>https://0-www-crossref-org.lib.rivier.edu/crossmark/index.html</resource>
	</doi_data>
  </journal_article>

Deleting Crossmark funding metadata

Submitting an empty Crossmark tag (<crossmark />) will delete all Crossmark data, including funding data. To delete only funding data, submit an empty <fr:program name="fundref"/> element:

<crossmark>
     <crossmark_version>1</crossmark_version>
     <crossmark_policy>10.5555/cm_1</crossmark_policy>
     <crossmark_domains>
         <crossmark_domain><domain>www.crossref.org</domain></crossmark_domain>
     </crossmark_domains>
     <crossmark_domain_exclusive>true</crossmark_domain_exclusive>
     <updates>
         <update type="correction" label="Correction" date="2011-04-10">10.5555/cm_test2.1</update>
         <update type="retraction" label="Retraction" date="2011-04-12">10.5555/cm_test2.2</update>
     </updates>
     <custom_metadata>
         <assertion name="received" label="Received" group_name="publication_history" group_label="Publication History">2011-04-12</assertion>
         <fr:program name="fundref" />
    </custom_metadata>
 </crossmark>

Funder metadata examples

Example 1: Funder information within a Crossmark deposit

The <fr:program> element captures funder data as <custom_metadata> within the <crossmark> element.

<crossmark>
    <crossmark_version>1</crossmark_version>
    <crossmark_policy>10.5555/crossmark_policy</crossmark_policy>
    <custom_metadata>
   	 <fr:program name="fundref">
   		 <fr:assertion name="funder_name">National Science Foundation
   			 <fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039/100000001</fr:assertion>
   		 </fr:assertion>
   		 <fr:assertion name="award_number">psychoceramics-1152342</fr:assertion>
   	 </fr:program>
    </custom_metadata>
</crossmark>

Example 2: Funder information outside of Crossmark

The <fr:program> element captures funding data. It should be placed before the <doi_data> element. This deposit contains minimal funding data - one funder_name or one funder_identifier must be present; both are recommended.

<fr:program name="fundref">
     <fr:assertion name="funder_name">National Science Foundation
<fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039/100000001</fr:assertion> </fr:assertion>
</fr:program>

Example 3: One funder, two grant numbers

This example contains one funder_name and one funder_identifier. Note that the funder_identifier is nested within the funder_name assertion, establishing https://0-doi-org.lib.rivier.edu/10.13039.100000001 as the funder identifier for funder name National Science Foundation. Two award numbers are present.

<fr:program name="fundref">
     <fr:assertion name="funder_name">National Science Foundation
       	<fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039/100000001</fr:assertion>
     </fr:assertion>
     <fr:assertion name="award_number">CBET-106</fr:assertion>
     <fr:assertion name="award_number">CBET-7259</fr:assertion>
</fr:program>

Example 4: Multiple funders and grant numbers

This example contains two funder_name/identifiers and two award_numbers for each funder. Each funding organization is within its own fundgroup.

<fr:program name="fundref">
     <fr:assertion name="fundgroup">
        <fr:assertion name="funder_name">National Science Foundation
            <fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039/00000001</fr:assertion>
        </fr:assertion>
        <fr:assertion name="award_number">CBET-106</fr:assertion>
        <fr:assertion name="award_number">CBET-7259</fr:assertion>
     </fr:assertion>
    <fr:assertion name="fundgroup">
        <fr:assertion name="funder_name">Basic Energy Sciences, Office of Science, U.S. Department of Energy
            <fr:assertion name="funder_identifier">https://0-doi-org.lib.rivier.edu/10.13039/100006151</fr:assertion>
        </fr:assertion>
        <fr:assertion name="award_number">1245-ABDS</fr:assertion>
        <fr:assertion name="award_number">98562-POIUB</fr:assertion>
     </fr:assertion>
</fr:program>

Page owner: Laura J. Wilkinson   |   Last updated 2020-April-08