0
CHORUS and FundRef
Implementation at Elsevier
Chris Shillum
VP Product Management, Platform and Data Integration, Elsevier
CHORUS Implementation Workshop, 18 Dec 2014
1
Topics
1. FundRef Taxonomy Update Workflow
2. Gathering and Validating Article Funding Info
3. Author Manuscript User Experience
2
1. FundRef Taxonomy Update
Workflow
3
(Bi)monthly Updates of FundRef Taxonomy
Elsevier
Funding
Funding
Body record
Funding
Funding
Body record
Body
record
Body
Record
CrossRef
Elsevier
Funder
Taxonomy
Compilation
of all Funding
Bodies into
SKOS file
Metadata captured
• URI
• Full organization name
• Synonyms
• Abbreviations
• Website URL
• Relationships (inc. Hierarchial) with other
organizations
• Contact Details
• Country
• State
• Type of organization (government,
company, foundation, etc.)
• Description of organization
FundRef
Registry
Assignment and
Registration of
DOIs (by
CrossRef)
Distribution to
FundRef and CHORUS
participants under
CC0
Funding bodies in Taxonomy
10,000
9,000
8,000
7,000
6,000
5,000
4,000
3,000
2,000
1,000
0
4
Funding Body Taxonomy Update Workflow
New
Funding
Body
Record
Feedback from
CrossRef
Elsevier Journal
Articles
Scopus Records
Gather
Candidate
Funding
Bodies
Harvest
Funding
Body
Metadata
Decline
Notification
Funder
Websites
• Candidates are new (non-matched)
funding bodies encountered by FundRef
participants or in Elsevier internal
workflows
Sources used:
• Funder websites,
• Ringgold
• Internal databases
• Records created for
genuinely new funding
bodies
• Duplicates may add
synonym to existing record
• If organization does not
appear genuine, decline
notice sent
5
2. Gathering and Validating
Article Funding Info
6
Manuscript Workflow Changes
Manuscript
Submission
• Author is asked to
confirm all
funding
organizations are
mentioned in the
article
• Typically in the
Acknowledgment
section
XML Creation
Proofing
• Supplier tags
funding
organizations and
grant numbers in
XML file
• FundRef IDs of
“known” funding
bodies are
included in this
tagging
• Tagged funding
information is
extracted from
XML and listed on
author query form
• Author is
requested to verify
funding
organizations are
correctly captured
7
Challenges when Capturing Funding Body Information
• Dozens of ways to misspell or abbreviate organization names
-
U.S. DOE; US DOE; DOE; Department of Energy; Dept. of Energy; United States
Department of Energy
National Institute of Health (singular) versus correct National Institutes of Health
• Duplicate abbreviations
-
AAA can stand for American Accounting Association; American Anthropology
Association; American Association of Anatomists; American Academy of Audiology
• Same organization name in multiple countries
-
A National Science Foundation exists in the US, Denmark, Iran, Georgia (the country),
Switzerland, etc.
• Organizations emerge, get renamed, are merged with other organizations,
create spin-offs, get split, cease to exist
-
American Dietetic Association ► Academy of Nutrition and Dietetics
Lance Armstrong Foundation ► Livestrong Foundation
• Understanding how funding is organised internationally Requires local
expertise to assess relationships, help to translate organization names
-
-
Natural Science Foundation of Jiangsu Province
Jiangsu Provincial Natural Science Foundation
8
Elsevier CHORUS/FundRef Development Schedule
Funder Taxonomy Workflow
2008
2011
2013
June 2014
July 2014
Q1/Q2 2015
October 2015
Article Funding MetaData Workflow
• “Grant Warehouse” to capture funding
organizations and grants released –
initially only US organizations
• Workflow to asses funder validity and
harvest metadata created
• UK, Canadian, Australian and EU
organizations added to Grant Warehouse
• Asian and ROW organizations started
being added to Grant Warehouse
• SKOS Conversion Routines developed
• Monthly submission of FB taxonomy to
CrossRef started
• New funding metadata tagging workflow
deployed
• Submission of funding metadata to
CrossRef as part of DOI registration
started
• Capability to link to AAM from
ScienceDirect User Interface released
• First post-embargo AAM publically
available subject to agreements between
CHORUS and Funding Bodies
9
2. Author Manuscript User
Experience
10
Link on SD Abstract to CHORUS Public Version
Subscribed users
will not see the
ScienceDirect
Abstract page but
go straight to the
final version
11
Testing User Experience
Optimize version for
Public Access needs
• Page viewer format for
main use case, i.e.
reading
• Clear option to
download AAM PDF
• Link to VoR
• Ensure reader
understands version
options, end user
license, and how to cite
12
Questions?
c.shillum@elsevier.com
@cshillum
www.elsevier.com