Metadata Best Practices Fund Ref license metadata others

Metadata Best Practices Fund. Ref, license metadata & others

Flow of Metadata Dashboard & Search Funder Registry Publisher Author (one way or another) Archive Publisher Society Funder OA Publisher SHARE Researcher

Metadata Collection and Distribution Collection 1. Determine funding of research 2. Determine licenses 3. Determine resources 4. Determine archive locations 5. Deposit with Cross. Ref Distribution 1. Deposit with Cross. Ref 1. Metadata distribution via Cross. Ref API to CHORUS aggregation services, funding agencies, others

Collection and Distribution Collection 1. Determine funding of research 2. Determine licenses 3. Determine resources 4. Determine archive locations 5. Deposit with Cross. Ref Distribution 1. Deposit with Cross. Ref 1. Metadata distribution via Cross. Ref API to CHORUS aggregation services, funders, others

Fund. Ref Funding Agency DOIs Cross. Ref Metadata Article DOIs Award Numbers

Fund. Ref <Concept rdf: about=". /501100001711"> <in. Scheme rdf: resource=". /Sci. Val. Funders"/> The Fund. Ref funder <skosxl: pref. Label> <skosxl: Label rdf: about=". /Label-8212"> registry <skosxl: literal. Form xml: lang="en"> • • • Around 6, 000 funder organizations and suborganizations Incomplete, growing International Swiss National Science Foundation </skosxl: literal. Form> </skosxl: Label> </skosxl: pref. Label> <svf: countryrdf: resource="http: //sws. geo names. org/2658434/"/> </Concept>

Fund. Ref <program name="fundref"> <assertion name="fundgroup"> Funding and award information in Cross. Ref metadata <assertion name="funder_name"> National Science Foundation </assertion> <assertion name="funder_identifier"> 10. 13039/100000001 </assertion> <assertion name="award_number"> DE-SC 0001091 </assertion> </program>

Fund. Ref Registry Updates • • Deposit of unknown funders can result in updates to the Fund. Ref funder registry Updates to Fund. Ref registry are published periodically

Fund. Ref Best Practice • Make best effort to collect and deposit funder DOIs Reconcile funder names with the funder registry o Fund. Ref reconciliation tool: http: //labs. crossref. org/fundref-reconciliation-service o Fund. Ref data entry example: http: //labs. crossref. org/fundref/widget o • Make best effort to collect and deposit award numbers

Collection of Fund. Ref Data Examine acknowledgements in manuscripts ● Author entry at manuscript submission Intramural funding for US federal agencies and / or

Using the Registry • Download and incorporate the registry http: //www. crossref. org/fundref • Query Cross. Ref’s API dynamically http: //api. crossref. org/funders? query=nsf

Fund. Ref - Technology Integration Vendor Implemented e. Journal. Press Yes Scholar. One Yes Aries Rolling out Atypon Imminent Publishing Technology At least one implementation Highwire Release imminent

Collection and Distribution Collection 1. Determine funding of research 2. Determine resources 3. Determine licenses 4. Determine archive locations 5. Deposit with Cross. Ref Distribution 1. Deposit with Cross. Ref 1. Metadata distribution via Cross. Ref API to CHORUS aggregation services, funders, others

Resource Links • • • Federal funding agencies want to ensure that content is publicly available for reading, textmining and indexing Deep links to full-texts on publisher sites No guarantee that the link is accessible

Resource Links • • Record a full-text link to a particular representation (mime type), JAV version (AM or VOR) Possible to provide an ‘intended use’ hint o text-mining, syndication, search engine crawling, any

Resource Link Examples • Version of record XML intended for text mining, version of record PDF intended for access under a syndication arrangement: <collection property=”text-mining”> <resource content_type=”text/xml” content_version=”vor”> http: //publisher. com/full-text/vor/10. 5555/12345678. xml </resource> </collection> <collection property=”syndication”> <resource content_type=”application/pdf” content_version=”vor”> http: //publisher. com/full-text/vor/10. 5555/12345678. pdf </resource> </collection>

Resource Link Examples • Accepted manuscript PDF without an intended use hint: <collection property=”any”> <resource content_type=”application/pdf” content_version=”am”> http: //publisher. com/full-text/am/10. 5555/12345678. pdf </resource> </collection>

Collection and Distribution Collection 1. Determine funding of research 2. Determine resources 3. Determine licenses 4. Determine archive locations 5. Deposit with Cross. Ref Distribution 1. Deposit with Cross. Ref 1. Metadata distribution via Cross. Ref API to CHORUS aggregation services, funders, others

License Metadata • • Funding agencies may wish to report on the public availability of articles and data arising from research they fund o Embargo period length and license terms Follows NISO access indicators proposal <license_ref/> and <free-to-read/> o Different licenses for AM and VOR o

License Link Best Practice • • • Create a web page and link for each version of a license Use canonical URLs for community licenses such as CC licenses or the STM licenses Optionally register DOIs for licenses o A ‘web page’ DOI type coming soon

License Metadata Example A publisher wants to express that some articles within a hybrid journal are licensed under a proprietary license but, after an embargo period of one year, the articles become available to the public under CC-BY. Articles in the same journal that receive an APC are immediately made available to the public under CC-BY.

Embargoed Articles <doi_data><doi>10. 5555/12345678</doi></doi_dat a> <license_ref> http: //publisher. com/license/v 1 </license_ref> <license_ref start_date=” 2015 -04 -28”> http: //creativecommons. org/licenses/by/3. 0 </license_ref>

Gold OA Articles <doi_data><doi>10. 5555/87654321</doi></doi_dat a> <license_ref> http: //creativecommons. org/licenses/by/3. 0 </license_ref>

Collection and Distribution Collection 1. Determine funding of research 2. Determine license 3. Determine resources 4. Determine archive locations 5. Deposit with Cross. Ref Distribution 1. Deposit with Cross. Ref 1. Metadata distribution via Cross. Ref API to CHORUS aggregation services, funders, others

Archive Locations • • Depositing Cross. Ref member asserts the archive location(s) of content. Not a guarantee of archiving but may be independently verified (by CHORUS, funders) <archive_locations> <archive name="DWT"/> <archive name="Portico"/> </archive_locations>

Collection and Distribution Collection 1. Determine funding of research 2. Determine licenses 3. Determine resources 4. Determine archive locations 5. Deposit with Cross. Ref Distribution 1. Deposit with Cross. Ref 1. Metadata distribution via Cross. Ref API to CHORUS aggregation services, funders, others

Cross. Ref Deposits - ORCIDs • • Allow funding agencies to connect researchers to funding Cross. Ref deposit metadata can include an ORCID for each contributor: <contributor role=”author”> <person_name> <given_name>Josiah</given_name> <surname>Carberry</surname> <ORCID>http: //orcid. org/0000 -0002 -1825 -0097</ORCID> </person_name> </contributor>

Cross. Ref Deposits - Abstracts • • Agencies may want to display abstracts in research portals Cross. Ref metadata can accept a plain abstract text or a JATS <abstract> element

Cross. Ref Deposits - References • • Has been possible to record under Cross. Ref Cited-By o Now possible to make references explicitly public Give funding agencies insight into what other research is important for the research they fund <reference_distribution_opts> any </reference_distribution_opts>

Cross. Ref Deposits • Resource (partial) deposits o • Fund. Ref, license and full-text links (and references) can be deposited separately Cross. Mark or not Cross. Mark? o Fund. Ref and license metadata o Recommended if you are planning to implement Cross. Mark

Cross. Mark Record Tab

Cross. Ref Deposits • All of the metadata discussed can be applied to datasets, proceedings, reports etc. that have Cross. Ref DOIs o Funding agencies would be able to track datasets as well as articles

Cross. Ref is agnostic. . . • about publishing business models o • OA publishers can participate in Fund. Ref, Cross. Ref Text and Data Mining, and deposit new forms of metadata about funder geographical location Fund. Ref registry covers funders across the world o Cross. Ref encourages CHORUS participants to deposit all funding, not just US federal agencies o

Implementation Recap 1. Determine funding of research output a. Implement Fund. Ref data collection on manuscript submission, or integrate into production phase 2. Select license and full-text links Create license pages b. Optionally register DOIs for licenses a. 3. Deposit with Cross. Ref a. Include funder DOIs, award numbers, license and full-text links, archive locations, (abstracts, ORCIDs, public references) in Cross. Ref metadata deposits

Cross. Ref Metadata Links Funder DOIs License URLs Resource URLs Contributor ORCIDs Article DOIs Award Numbers

Further Reading • • • Fund. Ref website o http: //www. crossref. org/fundref Geoff Bilder’s Best Practice Guide for Funder KPIs o http: //api. crossref. org/help/bestpractice Evan Owens’ CHORUS Implementation Guide