CrossRef DOIs in Use and Branding Guidelines

DOIs in use and Branding Guidelines Carol Anne Meyer Business Development & Marketing CrossRef Annual Meeting November 10, 2009 Thursday, November 12, 2009

What Scholars Know • Surveyed scholars from member websites • Preliminary Results • 900 Completed Responses Thursday, November 12, 2009

90% Read or Browse Online Scholarly Content Thursday, November 12, 2009

80% Use Reference Links Thursday, November 12, 2009

99% Find Reference Links Useful 1% 99% Thursday, November 12, 2009

Fewer Know about CrossRef or DOIs Know CrossRef? Know DOIs? 8% 7% 42% 48% 44% 50% YES NO NO RESPONSE Thursday, November 12, 2009

The good news? Awareness is growing Know CrossRef? Know DOIs? 48.7% 44.2% 34.7% 29.4% 2006 2009 2006 2009 Thursday, November 12, 2009

So What? Thursday, November 12, 2009

All DOIs are not CrossRef DOIs • DataCite • ISBN-A • Motion Pictures • Music Thursday, November 12, 2009

What can we do? Thursday, November 12, 2009

What can we do? •Branding Thursday, November 12, 2009

What can we do? •Branding •Branding Thursday, November 12, 2009

What can we do? •Branding •Branding •Branding Thursday, November 12, 2009

Thursday, November 12, 2009

Library awareness Thursday, November 12, 2009

Nice description of DOIs. But what’s CrossRef? Thursday, November 12, 2009

http://tinyurl.com/doivideo Thursday, November 12, 2009

Member Library Newsletters Thursday, November 12, 2009

What members can do... • Refer to DOIs deposited with Crossref as “CrossRef DOIs” • Maybe--Prepend a descriptive “http” preﬁx to every DOI displayed or printed. Thursday, November 12, 2009

Instead of THIS: doi:10.1126/science.170.3965.1358-d Maybe THIS: http://doi.crossref.org/10.1126/science.170.3965.1358-d Thursday, November 12, 2009

Why? • It says DOI • It says CrossRef • It’s a link Thursday, November 12, 2009

Branding Guidelines for Reference Linking Thursday, November 12, 2009

DOI Name and Information Guidelines www.crossref.org/02publishers/doi-guidelines.pdf Thursday, November 12, 2009

5.1 Structure Suf xes • A suﬃx may be used to re ect hierarchical information or levels of granularity depicted in delimited substrings of characters known as nodes. Thursday, November 12, 2009

5.1 Structured Suffixes + Thursday, November 12, 2009

5.1 Structured Suffixes + • 10.1126/science.325_140 Thursday, November 12, 2009

5.1 Structured Suffixes + • 10.1126/science.325_140 • 10.1071/WRv36n4_ED Thursday, November 12, 2009

5.1 Structured Suffixes + • 10.1126/science.325_140 • 10.1071/WRv36n4_ED • 10.1016/j.sleep.2007.11.017 Thursday, November 12, 2009

5.1 Structured Suffixes + • 10.1126/science.325_140 • 10.1071/WRv36n4_ED • 10.1016/j.sleep.2007.11.017 • 10.1109/TKDE.2008.185 Thursday, November 12, 2009

5.1 Structured Suffixes + • 10.1126/science.325_140 • 10.1071/WRv36n4_ED • 10.1016/j.sleep.2007.11.017 • 10.1109/TKDE.2008.185 • 10.1287/opre.1070.0463 Thursday, November 12, 2009

5.1 Structured Suffixes + • 10.1126/science.325_140 • 10.1071/WRv36n4_ED • 10.1016/j.sleep.2007.11.017 • 10.1109/TKDE.2008.185 • 10.1287/opre.1070.0463 • 10.1038/cr.2009.32 Thursday, November 12, 2009

5.1 Structured Suffixes + • 10.1126/science.325_140 • 10.1071/WRv36n4_ED • 10.1016/j.sleep.2007.11.017 • 10.1109/TKDE.2008.185 • 10.1287/opre.1070.0463 • 10.1038/cr.2009.32 • 10.1177/0363546509332253 Thursday, November 12, 2009

5.1 Structured Suffixes + • 10.1126/science.325_140 • 10.1071/WRv36n4_ED • 10.1016/j.sleep.2007.11.017 • 10.1109/TKDE.2008.185 • 10.1287/opre.1070.0463 • 10.1038/cr.2009.32 • 10.1177/0363546509332253 • 10.1525/jer.2009.4.2.27 Thursday, November 12, 2009

5.1 Structured Suffixes + • 10.1126/science.325_140 • 10.1071/WRv36n4_ED • 10.1016/j.sleep.2007.11.017 • 10.1109/TKDE.2008.185 • 10.1287/opre.1070.0463 • 10.1038/cr.2009.32 • 10.1177/0363546509332253 • 10.1525/jer.2009.4.2.27 • 10.1111/j.1468-1331.2009.02646.x Thursday, November 12, 2009

5.1 Structured Suffixes - • 10.1126/science.1175752 • 10.1145/1244408.1244421 • 10.1063/1.3116223 • 10.1155/2009/848943 • 10.1080/03091920802357742 • 10.1007/s00253-009-2042-4 • 10.1055/s-0028-1082061 Thursday, November 12, 2009

5.4 DOI Usability • DOIs should be as concise as possible, in consideration of human readability. Thursday, November 12, 2009

5.4 DOI Usability • Often, hierarichal DOIs are more usable. • The use of separators like “.” or “-” helps • Strings longer than 6 of arbitrary-looking numbers or letters interferes with usability, even if the DOI is structured. Thursday, November 12, 2009

5.4 Usability + • 10.1126/science.325_140 • 10.1016/j.sleep.2007.11.017 • 10.1109/TKDE.2008.185 • 10.1287/opre.1070.0463 • 10.1038/cr.2009.32 • 10.1525/jer.2009.4.2.27 Thursday, November 12, 2009

5.4 Usability - Thursday, November 12, 2009

5.4 Usability - • 10.1126/science.1175752 Thursday, November 12, 2009

5.4 Usability - • 10.1126/science.1175752 • 10.1145/1244408.1244421 Thursday, November 12, 2009

5.4 Usability - • 10.1126/science.1175752 • 10.1145/1244408.1244421 • 10.1063/1.3116223 Thursday, November 12, 2009

5.4 Usability - • 10.1126/science.1175752 • 10.1145/1244408.1244421 • 10.1063/1.3116223 • 10.1071/WRv36n4_ED Thursday, November 12, 2009

5.4 Usability - • 10.1126/science.1175752 • 10.1145/1244408.1244421 • 10.1063/1.3116223 • 10.1071/WRv36n4_ED • 10.1155/2009/848943 Thursday, November 12, 2009

5.4 Usability - • 10.1126/science.1175752 • 10.1080/03091920802357742 • 10.1145/1244408.1244421 • 10.1063/1.3116223 • 10.1071/WRv36n4_ED • 10.1155/2009/848943 Thursday, November 12, 2009

5.4 Usability - • 10.1126/science.1175752 • 10.1080/03091920802357742 • 10.1145/1244408.1244421 • 10.1177/0363546509332253 • 10.1063/1.3116223 • 10.1071/WRv36n4_ED • 10.1155/2009/848943 Thursday, November 12, 2009

5.4 Usability - • 10.1126/science.1175752 • 10.1080/03091920802357742 • 10.1145/1244408.1244421 • 10.1177/0363546509332253 • 10.1063/1.3116223 • 10.1007/s00253-009-2042-4 • 10.1071/WRv36n4_ED • 10.1155/2009/848943 Thursday, November 12, 2009

5.4 Usability - • 10.1126/science.1175752 • 10.1080/03091920802357742 • 10.1145/1244408.1244421 • 10.1177/0363546509332253 • 10.1063/1.3116223 • 10.1007/s00253-009-2042-4 • 10.1071/WRv36n4_ED • 10.1055/s-0028-1082061 • 10.1155/2009/848943 Thursday, November 12, 2009

5.4 Usability - • 10.1126/science.1175752 • 10.1080/03091920802357742 • 10.1145/1244408.1244421 • 10.1177/0363546509332253 • 10.1063/1.3116223 • 10.1007/s00253-009-2042-4 • 10.1071/WRv36n4_ED • 10.1055/s-0028-1082061 • 10.1155/2009/848943 • 10.1111/j.1468-1331.2009.02646.x Thursday, November 12, 2009

6.3 The Response or Landing Page • A minimal response page must contain • a full bibliographic citation • some mechanism by which the user can gain access to the full text Thursday, November 12, 2009

But where’s the DOI? Thursday, November 12, 2009

7. Use and Display of DOIs • a DOI should be displayed as (for example) doi:10.1006/jmbi.1998.2354 • and the DOI identi er itself can be an active link as in http://dx.doi.org/10.1006/jmbi.1998.2354 Thursday, November 12, 2009

7.1 Resolution Via the DOI Proxy • The DOI Proxy server - http://dx.doi.org/ - resolves DOIs. The DOI Proxy is the de nitive resolution service for DOIs and should be used for all DOI links. Thursday, November 12, 2009

7.3 Display of DOIs • A DOI for a piece of content (article, book chapter, conference proceeding) should also be displayed in the header information for the online AND print versions of the content Thursday, November 12, 2009

7.3.1 Displaying DOIs in print • A DOI should be included in the header for the print version of that article. • Recommend listing the DOI -- for example -- as "doi:10.1006/jmbi.1998.2354". It is possible to have the DOI followed by: "available via http://dx.doi.org/". Thursday, November 12, 2009

? Thursday, November 12, 2009

7.3.2 DOIs in citations • DOIs are a very useful addition to citations. • The DOI should be the last element in the citation irrespective of the format used. • “doi:” should be lowercase with no space between “doi:” and the start of the DOI. • Publisher-speciﬁc URLs should not be used in citations since they may break if the journal changes ownership. (CrossRef Reference Guidelines, http://www.crossref.org/08downloads/CrossRef_Ref_Guide_1_0.pdf ) Thursday, November 12, 2009

7.3.3 DOIs in citation export services • Publishers should include DOIs in their Download Citation/Export References” services. • DOIs should be included as an identifier and as the URL link using the “http://dx.doi.org” resolver address. • The DOI should also be included as a key article identifier when such a field exists. http://www.crossref.org/02publishers/guidelines.html Thursday, November 12, 2009

7.3.4 DOI as a reference link • Use "CrossRef" as the display text for reference links. Thursday, November 12, 2009

7.3.5 Instructions for Authors • Publishers should include information about using DOIs in their instructions for authors. Thursday, November 12, 2009

Branding Guidelines for CrossRef Cited-by Linking Thursday, November 12, 2009

Bonus Round • Displaying DOIs on Tables of Contents Thursday, November 12, 2009

Miscellany • Links Thursday, November 12, 2009

More information http://www.crossref.org/02publishers/guidelines.html Thursday, November 12, 2009

Branding Guidelines for CrossCheck Thursday, November 12, 2009

Create an information page Thursday, November 12, 2009

Place depositor on home page of publications deposited in CrossCheck. Thursday, November 12, 2009

Place “deposited” logo on each article deposited Thursday, November 12, 2009

Take Aways • CrossRef DOIs aren’t just for publishers and geeks • The more visible CrossRef DOIs are, the more likely your investment will result in traﬃc • We’re considering simplifying the display guidelines--more later. Thursday, November 12, 2009

Thanks cmeyer@crossref.org cmeyer@crossref.org Thursday, November 12, 2009

http://crossref.org	3
http://www.slideshare.net	3
http://www.crossref.org	2
http://www.health.medicbd.com	1

CrossRef DOIs in Use and Branding Guidelines

by CrossRef on Nov 12, 2009

Accessibility

Categories

Upload Details

Usage Rights

4 Embeds 9

Statistics

CrossRef DOIs in Use and Branding Guidelines Presentation Transcript