Your SlideShare is downloading. ×
0

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Introduction to CrossRef for Publishers Webinar

4,888

Published on

This presentation has been superseded. Please see http://www.slideshare.net/CrossRef/introduction-to-crossref-webinar-17423381 for the latest information

This presentation has been superseded. Please see http://www.slideshare.net/CrossRef/introduction-to-crossref-webinar-17423381 for the latest information

1 Comment
1 Like
Statistics
Notes
  • A recording of this webinar can be viewed here:
    http://www.crossref.org/08downloads/webinars/intro_to_crossref_for_publishers_webinar_122011.arf

    May require a webex player which you can download here: http://www.webex.com/play-webex-recording.html
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
4,888
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
92
Comments
1
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • What is it? Digital Object Identifier, alphanumeric string that uniquely identifies an item and where it lives online DOIs can be used to identify things online, basically anything that you can link to (html pages, images, audio, raw data, programs, etc.) Once a DOI has been assigned to an item, the DOI URL (if properly maintained) can remain a consistent locator for the item.
  • Why are DOIs important? They solve the problem of ‘link rot’ i.e. broken links. (image) Broken links are a big problem with online content – titles move from publisher to publisher, publishers upgrade their sites regularly, which usually involves changing URLs.
  • A CrossRef DOI reliably identifies content. If you follow a DOI to an article you’re assure that the page you view is the publisher maintained version of an article. This is very important, because research articles are corrected, retracted, enhanced regularly.
  • 1. A DOI link consists of two parts: the DOI resolver URL, and the DOI itself.  2. When combined, the DOI is ‘made actionable’, that is, made into a link. 3. When you click on the link, you’re taken to the current URL of the item.The URL for the DOI in this example has been updated 5 times since it was initially deposited in June 2004.  4. We updated our DOI display guidelines in early August – we now ask that DOIs be represented as a link with the http://dx.doi.org prefix
  • There are a number of DOI RAs, all overseen by the International DOI Foundation. CrossRef is the largest RA – we registered over 90% of the DOIs – at last count the percentage was 96%. We register DOIs for scholarly and professional materials, other RAs assign DOIs to different materials, or use the DOI differently.
  • The majority of CrossRef content is journals but as we grow we’re seeing increases in deposits of other content types, particularly books. The main content types we accept are journals, books, conference proceedings, reports, standards, dissertations, and supplementary materials, but we do have some flexibility so if you want to assign DOIs to a content type not listed here, please ask.
  • Our range is broad chronologically as well – we of course have a significant amount of current content but deposits range back as far as 1665.
  • Publisher members: What does it mean to be a ‘CrossRef Member’ – member obligations outbound reference linking :  Members are required to create outbound DOI links within their references, meaning members must add DOI links (when available) to the reference list for journal articles deposited with CrossRef . deposit all current journal articles: no other content types are required, back files aren’t required, but we encourage themresolve any DOI conflicts: a ‘conflict’ happens when two DOIs share the same metadata, meaning more than one DOI has been assigned to a single item. This can happen for a number of reasons - we provide tools to identify and resolve conflicts.update metadata and URLs: a DOI is only as good as its most recent URL. If your URL changes, the DOI must be updated.Do not publicize CrossRef DOIs until links are liveMake plans for long term archiving: this is new, you need to decide what you’re going to do if you go out of business – there are a number of archiving organizations that are very willing to host journals that have ceased publications (Portico, CLOCKSS, KLB) 
  • We call the process of sending in metadata to the CR system ‘depositing’. We sometimes use the terms ‘deposit’ and ‘register’ interchangeably but they’re slightly different - when a publisher ‘deposits’ a DOI, the metadata is added to the CrossRef database, making the DOI retrievable. The DOI is also registered with the Handle resolver, meaning the DOI and URL only – no citation metadata is recorded by the Handle resolver. Immediately after the submission is processed, the system sends you a submission log. This is very important - data is often messy, and we try to keep the messy stuff out of our database, so there are many reasons your submission might fail.
  • . Once the DOI has been registered, it is resolvable and queryable, meaning it can be used for linking and can be retrieved from our system by end users, CrossRef Metadata Services subscribers, library link resolvers, and of course other members.
  • Submission methods vary from very robust complicated systems to one guy cutting and pasting stuff from Word into our web deposit form (which converts the data to XML). Most deposits are made via machine interfaces. Data is sent to us via HTTP POST – we do have a simple java-based tool that can be used for uploads, it’s available in our help documentation. Many publishers prefer to create their own tools. We do not currently accept FTP deposits.
  • We do have a public interface to our system which can be used to upload deposit and query files. This is where you’d go if you needed to resubmit an XML file generated by the web deposit form.
  • To use, cut-and-paste a list of citations into the form and…
  • Your list will be returned to you with any DOI matches.
  •  We also have a ‘guest query’ form which provides a number of single-DOI searches. It’s not a tool you’d want to use for bulk querying, but it’s an excellent resource for testing out queries. It’s a good practice to query for your own DOIs, just to make sure they are discoverable. The GQ has a ‘bibliographic metadata search’, which allows you to enter fielded metadata into the form  There’s also an author/title search, which can be useful if you don’t have full article metadata Next, there’s a formatted reference parser, you can enter a single reference here – for multiple references you’ll need to use the STQ There is a DOI-to-metadata query, you enter a DOI and get back the metadata  You’re also able to submit an XML query – this is quite handy for troubleshooting and testing, we’ve got several options for controlling query execution so it’s pretty easy to just cut and paste a query into the box and edit it on the fly.
  • After you’ve retrieved your reference DOIs, you need to include them in the reference lists on your website.
  • Here is another example of outbound linking - this publisher is including the full DOI url in their references, making it very easy to cut and paste etc. This is recommended in our new DOI guidelines…
  • If you have titles that have gone through name changes, you’ll need to pay attention to our title management policies.Titles in the CrossRef system are created from publisher metadata with the first deposit of a journal. Title and ISSN combinations are not verified with an external agency. A check digit validation is performed on every ISSN submitted in a deposit. Once a title or ISSN is introduced into the CrossRef system, a new publication with the same title or ISSN cannot be created without CrossRef intervention. The publisher determines the exact title and ISSN included in the deposit. At least one ISSN is required for each journal deposited with CrossRef, but publishers are encouraged to deposit all ISSN available for a title. If you are depositing a series that predates ISSNs, they can be assigned retroactively – there’s no charge for assigning ISSNs.The title / ISSN combination in your deposit must match the title / ISSN combination in our system. We do allow for minor variances, like Journal of… vs. The Journal of… or mixing and and &Publishers requesting significant changes to a title are instructed to request a new ISSN from the appropriate agency. This isn’t a CrossRef policy, it’s an ISSN Centre policy and is actively supported by the Library of Congress (for those of you in the US)5. Journals should be deposited with the correct title – sometimes journals appear online under the most current title. We really need to make sure that the title in our database is the original title, since that title will be used in citations, which turn into CrossRef queries. We can add multiple versions of a title to a title record to help with querying, but it’s important that DOIs be attached to the correct title.
  • First is the resolution report. It is sent out monthly to the business contact we have on file. This report is comprised of statistics we extract from DOI resolution logs and contains data about how many times your DOIs have been clicked and your overall resolution failure rate (successes vs. failures) There’s a lot of interesting data here – it has a.) how many resolutions you have per month – and lists the previous 12 months as well, so you can compareb.) it also includes info on resolution attempts (that is, how many times someone tries to resolve one of your DOIs. c.) also has a list of your top ten DOIsd.) this is important – the report lists your overall resolution failure rate, as well as the overall failure percentage for all members. The resolution failure rate is the percentage of DOI resolution attempts that have failed. This rate often gives members a heads up about potential problems, whether it be someone creating bad links to your content, or you failing to deposit DOIs that have been published.e.) there is a .csv file attached to your report that lists all failed DOI resolution attempts. Some of these are garbage – users make errors, especially when they are cutting and pasting, but if you have a high failure rate you should look at these DOIs closely.
  • This report is emailed as needed to the technical contact. These alerts are compiled from complaints about unresolving DOIs submitted to us by end users. If an end user tries to resolve a DOI that has not been registered, they are delivered to a form that they can submit to us with comments and their email address. When the DOI has been registered, we send them an alert. Any comments are passed on to publishers. 
  • We also have something called the Schematron report – Schematron is a validation language. These reports are used to identify messy metadata We need to be flexible and accommodate variances in data, so our deposit schema can’t keep all of the questionable data out without blocking good data as well, so we do a post-deposit review of metadata and pick out items that we think might be incorrect. These reports are emailed out weekly on Saturday, and we send out an average of 45 reports a week.
  • Cited-by linking: http://www.crossref.org/citedby/index.html CMS: http://www.crossref.org/metadata_services.htmlCrossCheck: http://www.crossref.org/crosscheck/index.html CrossMark: http://www.crossref.org/crossmark/index.html
  •  
  • Transcript

    • 1. Introduction tofor publishers Patricia Feeney Product Support Manager
    • 2. Agenda CrossRef overview Creating and working with CrossRef DOIs Maintaining your DOIs and metadata CrossRef services Resources
    • 3. mission statement:CrossRefs goal is to be a trusted collaborative organizationwith broad community connections; authoritative andinnovative in support of a persistent, sustainableinfrastructure for scholarly communication.
    • 4. Why do publishers join?  To get persistent identifiers for their content  To drive more traffic to their content  To turn references into hyperlinks  To pull in cited-by links (who cites this?)  Participate in other collaborative services (CrossCheck, CrossMark)
    • 5. DOI = Digital Object Identifier
    • 6. Broken links are a problem
    • 7. A DOI uniquelyidentifies a piece of electronic content
    • 8. http://dx.doi.org/ + DOI = persistent URL http://dx.doi.org/10.1577/H02-043http://dx.doi.org//10.1577/H02-043
    • 9. International DOI Foundation (IDF):oversees the central DOI system, promoteDOI as a standard, and provides anorganizational infrastructure that ensurespersistence and interoperability.Corporation for National ResearchInitiatives (CNRI):they (among other things)are responsible for the Handle system, whichis the technology that causes DOIs toresolve.Registration Agencies (RAs): RegisterDOIs on behalf of other organizations.CrossRef is a RA.
    • 10. DOI Registration agenciesEuropean Union Office of Copyright Agency Limited Publications (CAL)TIB mEDRA (TechnischeInformationsbi bliotek) Wanfang DataR.R. Bowker DataCiteNielsen Bookdata CrossRef
    • 11. 0.1016/j.lwt.2008.02.010 10.3113/FAI.2008.0185 10.1037/07357028.38.4.338.supp 10.1016/j.diabet.2007.11.004 10.1139/Z07-115 10.1016/j.forec0.1016/j.coph.2008.01.007 10.1109/ISBI.2007.357057 10.1016/j.jcis.2008.01.049 10.1016/j.aorn.2007.12.029 10.1097/HJR.0b013e3282f29aa60.1016/j.jmatprotec.2007.12.144 10.1016/j.biopsycho.2008.02.009 10.1016/j.jfs.2007.12.003 10.1177/0278364907085562 10.1016/j.jip.2008.02.010.1016/j.resuscitation.2007.10.008 10.1016/j.talanta.2008.02.043 10.1080/1055678031000152079 10.1111/j.1538-7836.2008.02908.x 10.1016/j.ce0.1016/j.physletb.2008.03.004 10.1016/j.cytogfr.2008.01.004 10.1006/S0003-2670(03)00575-0 10.1061/(ASCE)0733-9445(1993)119:12(3537)0.1016/j.orggeochem.2008.03.001 10.1016/j.jce.2008.03.001 10.1097/YIC.0b013e3282f2d42c 10.1016/j.jmmm.2008.02.146 10.2223/JPED.17580.1109/ISBI.2007.356995 10.1007/3-540-48311-X 10.1016/S0168-583X(97)00553-3 10.1029/2007GL090712 10.1016/j.biombioe.2008.02.002 10.0.1111/j.1600-0714.2007.00624.x 10.1016/j.jchemneu.2008.02.007 10.1016/S0021-8502(97)00109-2 10.1016/j.tet.2008.02.077 10.1016/j.yhbeh.20.1029/2007SW000355 10.1016/j.forsciint.2008.01.009 10.1111/j.1365-2044.2007.05319. 10.1016/j.csr.2008.02.009 10.1016/j.physleta.2008.02.00.1016/j.poly.2007.12.031 10.1016/j.biocon.2007.12.030 10.1016/j.eurpsy.2007.11.005 10.3390/molecules130100 10.1016/j.cam.2008.02.0150.1016/j.nuclphysbps.2007.11.105 10.1007/s12282-008-0037-0 10.1016/j.colsurfa.2008.02.018 10.1016/j.colsurfa.2008.02.018 10.1111/j.1399-6570.1021/la7032753 10.1111/j.1432-0436.2007.00257.x 10.1109/QSIC.2007.4385520 10.1016/j.nimb.2008.03.025 10.1016/j.nimb.2008.03.028 10.100.1017/SO266467405003056 10.1016/j.agrformet.2008.01.004 10.1016/j.agee.2008.01.003 10.1016/j.cortex.2008.03.001 10.1016/j.jtbi.2008.02.00.1016/j.jmatprotec.2008.03.003 10.1016/j.actamat.2007.12.057 10.1016/j.paed.2007.12.008 10.1016/j.canlet.2008.01.034 10.1016/j.molcata.2000.1016/j.apenergy.2008.01.002 10.1111/j.1365-2044.2007.05262.x 10.1016/j.seares.2008.02.004 10.1016/j.expneurol.2008.02.013 10.1016/j.ica.20.1080/10242420701379866 10.1016/j.trstmh.2008.01.002 10.1043/0012-9658(1975)056[0511:TMGS]2.0.CO;2 10.1016/j.biortech.2008.01.0060.1016/j.pedex.2008.01.005 10.1016/j.jsv.2007.07.090 10.1016/j.jomh.2007.11.003 10.1016/j.brainresrev.2008.02.004 10.1016/j.ecolmodel.2008.0 =621.2006.01425.x 10.1080/87565640701376151 10.1016/j.jcpa.2007.11.004 10.1016/j.jala.2007.12.008 10.1016/j.smallrumres.2007.12.023 10.100.1002/(SICI)1096-8644(199708)103:4<507::AID-AJPA8>3.0.CO 10.1007/s12033-008-9055-6 10.1016/j.ijoa.2008.01.005 10.1016/j.rmed.2008.010.1016/j.compenvurbsys.2007.11.003 10.1016/j.atmosenv.2008.02.031 10.1021/b608262a 10.1016/j.jss.2007.04.049 10.1016/j.rbmret.2007.10.000.1097/01.CCM.0000298158.12101.41 10.1016/j.foodchem.2008.01.051 10.1016/j.irfa.2008.02.004 10.1016/j.csr.2008.02.013 10.1016/j.foodchem0.1007/978-3-8350-9310- 10.1016/j.nuclphysbps.2007.11.109 10.1146/annurev.celibio.22.011105.102609 10.1016/j.radphyschem.2008.02.0100.1016/j.chemgeo.2007.12.007 10.1016/j.smallrumres.2007.12.025 10.1016/j.mpdhp.2007.12.003 10.1038 10.1016/j.tiv.2008.01.013 10.1186/1470.1097/WNR.0b013e3282f3476f 10.1016/j.destud.2007.12.006 10.1013/j.bjps/2007.11.011 10.1016/j.fbp.2008.01.001 10.1016/j.jomh.2007.12.0040.1016/j.actamat.2007.12.036 10.1109/SECON.2007.342869 10.1016/j.ejmech.2008.02.027 10.1016/j.still.2008.01.009 10.1890/060162 10.1016/j0.2514/1.27866 10.1155/2008/483857 10.1016/j.measurement.2008.02.009 10.2466/PRO.101.3.970-978 10.1016/j.ab.2008.03.006 10.1213/01.an0.1017/S095410200600037X 10.1146/annurev.genom.7.0805.115737 10.1016/j.anl.2007.12.006 10.1016/j.aorl.2007.10.004 10.1016/j.cca.2008.00.1016/j.cplett.2008.03.001 10.1016/j.na.2008.02.061 10.1111/j.1365-2524.2007.00722.x 10.1016/j.molcata.2008.03.002 10.1016/j.cag.2005.05.010.1109/ICNSC.2007.372901 10.1111/j.1525-142X.2007.00195.x 10.1007/BF02845227 10.1016/j.landusepol.2008.01.001 10.1016/j.neuroimage.200.1016/j.atherosclerosis.2007.12.013 10.1007/s11450-008-2014-7 10.1002/(SICI)1097-0142(19990515)85:10<2114::AID-CNCR3>3.0.CO;2-U0.1016/j.archger.2008.01.009 10.1111/j.1552-6569.2007.00179.x 10.1016/j.postharvbio.2007.12.005 10.1016/j.clim.2007.12.010 10.1016/j.jhin.2000.1038/417304a 10.1016/j.jfluidstructs.2007.10.004 10.1016/j.apal.2008.01.001 10.1080/00497870701870285 10.1109/TMI.2007.906091 10.10420.1016/j.enggeo.2007.11.005 10.1016/j.tig.2008.01.005 10.1111/j.1750-3639.2007.00121.x 10.1016/j.cbi.2008.02.012 10.1016/j.mpdhp.2007.12.000.1016/j.tra.2007.12.002 10.1029/JD007393 10.1016/j.cpc.2008.02.013 10.1111/j.0022-202X.2005.23909.x 10.1016/j.aorn.2007.12.001 10.1111/j.10.1016/j.biocon.2008.01.011 10.1016/j.jmatprotec.2008.01.031 10.1016/j.freeradbiomed.2008.03.001 10.1016/j.indmarman.2008.01.001 10.1007/s0.1016/j.automatica.2007.12.010 10.1016/j.aorl.2007.11.003 10.1002/anie.200705516 10.1111/j.1745-7262.2008.00333.x 10.1016/j.nima.2008.02.0.1002/esq.1066 10.1016/j.ntt.2008.02.003 10.1016/j.jviromet.2008.01.025 10.1111/j.1708-8305.2007.00164.x 10.1016/j.tcs.2008.03.006 10.1016/0.1016/j.jspi.2008.02.007 10.1016/j.biocel.2008.02.021 10.1016/j.chemphyslip.2008.02.011 10.1016/j.biocel.2008.02.026 10.1016/j.critrevonc.20080.1016/j.biocel.2008.02.026 10.1163/156854088X00212 10.1043/E-21 10.1016/j.epsl.2008.02.035 10.1016/j.fluid.2008.01.021 10.1016/j.compag.20.1128/JCM.43.5.2274–2276.2005 10.1016/j.jeurceramsoc.2007.11.003 10.1016/j.enggeo.2008.02.005 10.1016/j.ode.2006.11.002 10.1002
    • 12. Content beyond journals…  Books 6% 6% 1%  Standards Journals  Proceedings Books  Images Conference Proceedings Components  Figures 87%  Datasets  Working papers  Dissertations
    • 13. Linking 5 centuries of content
    • 14. Member obligations:  outbound reference linking  deposit all current journal articles  resolve any DOI conflicts  update metadata and URLs  do not publicize CrossRef DOIs until links are live  make plans for long term archiving
    • 15. Step-by-step 1. Join CrossRef! 2. Publish 3. Deposit 4. Query 5. Outbound linking 6. Maintain DOIs and Metadata
    • 16. After you join… Prefix: Suffix:  Unique within a prefix  Assigned to members – a DOI can only be assigned to one item  Format is 10.XXXX  Consistent  Identifies who intially  Logical created the DOI  Easily documented  Prefix does not identify  Readily implemented the current owner of the DOI
    • 17. Creating a DOI Suffix Keep it simple: 10.5664/sleep.1000 10.3183/NPPRJ-1986-01-03-p004-013 10.3103/S0005105507050032 10.4260/BJFT20094508 10.1632/074069503X85526 Allowed characters: "a-z", "A-Z", "0-9" and "-._;()/”
    • 18. Publish Response page must include:  bibliographic information about the item  means to access full text  the DOI New DOI Display guidelines! http://www.crossref.org/02publishers/doi_display_guidelines.html CrossRef DOIs should always be displayed as permanent URLs in the online environment. YES: http://dx.doi.org/10.5555/imadoi NO: doi: 10.5555/imadoi
    • 19. DOIs are required on the responsepage, recommended on other pages: Tables of contents  Abstracts  Full text HTML and PDF articles and other scholarly documents  Citation downloads to reference management systems  Metadata feeds to third parties  “How to Cite This” instructions on content pages  Social networking links Anywhere users are directed to a permanent, stable, or persistent link to the content
    • 20. DOIs for books
    • 21. Submissio n report
    • 22. Submissio n report <?xml version="1.0" encoding="UTF-8"?> <doi_batch_diagnostic status="completed" sp="cr6.crossref.org"> <submission_id>426240380</submission_id> <batch_id>12009_DOIs_unreg_2007-09-21</batch_id><record_diagnostic status="Success"> <doi>10.1385/AO:38:1:8</doi> <msg>Success</msg> </record_diagnostic> <record_diagnostic status="Failure" msg_id="22"> <doi>all dois of the current journal element</doi> <msg>ISSN "15304086" has already been assigned to a different title/publisher/genre</msg> </record_diagnostic> <record_diagnostic status="Warning"> <doi>10.3386/w11255</doi> <msg>Addedwith conflict</msg> <conflict_id>354709</conflict_id> <dois_in_conflict> <doi>10.1596/1813-9450-3622</doi> </dois_in_conflict> </record_diagnostic> <batch_data> <record_count>3</record_count> <success_count>1</success_count> <warning_count>1</warning_count> <failure_count>1</failure_count> </batch_data> </doi_batch_diagnostic>
    • 23. Submissio n report
    • 24. Machine interfaces HTTP The vast majority of transactions are made via a machine interface
    • 25. Public interface Web deposit form http://www.crossref.org/we bDeposit/ 1. Enter data into form 2. Form generates XML and sends it to the system 3. DOI is deposited (or not, be sure to check your submission log)
    • 26. Web Deposit Format: http://www.crossref.org/webDeposit/Accepts deposits for: journals and articles books and book chapters conference proceedings and conference papers reports.
    • 27. CrossRef system public interface: http://doi.crossref.org
    • 28. http://www.crossref.org/SimpleTextQuery
    • 29. Guest Query formhttp://www.crossref.org/guestquery  Bibliographic metadata search  Author / title search  Formatted reference parsing  DOI-to-metadata Query  Build an XML Query
    • 30. Next – add outbound links to references
    • 31. New guidelineshttp://www.crossref.org/02publishers/doi_display_guidelines.html Ghosh, M.K., M.L. Harter. 2003. A viral mechanism for remodeling chromatin structure in G0 cells. Mol. Cell. 12:255–260, http://dx.doi.org/10.1016/S1097- 2765(03)00225-9 Ghosh, M.K., M.L. Harter. 2003. A viral mechanism for remodeling chromatin structure in G0 cells. Mol. Cell. 12:255–260, http://doi.org/bm6 Ghosh, M.K., M.L. Harter. 2003. A viral mechanism for remodeling chromatin structure in G0 cells. Mol. Cell. 12:255–260 http://dx.doi.org/10.1016/S1097- 2765(03)00225-9 Ghosh, M.K., M.L. Harter. 2003. A viral mechanism for remodeling chromatin structure in G0 cells. Mol. Cell. 12:255–260 Ghosh, M.K., M.L. Harter. 2003. A viral mechanism for remodeling chromatin structure in G0 cells. Mol. Cell. 12:255–260, CrossRef. Ghosh, M.K., M.L. Harter. 2003. A viral mechanism for remodeling chromatin structure in G0 cells. Mol. Cell. 12:255–260, Article.
    • 32. Maintaining DOIs and Metadata URL update H:email=pfeeney@crossref.org;fromPrefix=10.5555;toPrefix=10.5555 10.5555/doi1 http://www.yoururl.com/journal/art1 10.5555/doi2 http://www.yoururl.com/journal/art2 10.5555/doi2 http://www.yoururl.com/journal/art12
    • 33. Maintaining Journal Titles Title and ISSN combinations are determined by the publisher. A valid ISSN is required for all journal titles The title / ISSN combination in your deposit must match the title / ISSNcombination in our system. If a title changes, a new ISSN is required Journals should be deposited under the original titleTitle list: http://www.crossref.org/titleList/
    • 34. Maintaining DOIs and Metadata: Reports Recurring or static As-needed reports: reports: Conflict Resolution Report DOI Error Report Deposit Report Schematron Report Missing Metadata Report Coming soon: Status Report New system reports! Go-live report Title list
    • 35. Resolution Report (emailed monthly)
    • 36. Depositor Report (in Members Area) oror
    • 37. Deposit report detail
    • 38. Conflict reports (in Members Area)
    • 39. DOI Error report (emailed nightly as needed)     
    • 40. Schematron report (emailed weeklyas needed) Schematron reports notify depositors of non- fatal deposit issues  35-40 emails sent out weekly  Alerts are generated for < 1% of deposits  Tend to identify „messy‟ deposits  Rules updated periodically
    • 41. Services Cited-by linking Metadata feeds to third parties Plagiarism screeningPowered byiThenticate Version verification
    • 42. http://labs.crossref.org/Plugins for Moveable Type and Wordpress Experimental search interfaces PDF tools DOI QR code generator
    • 43. Where to find help:  Help documentation: http://www.crossref.org/help  CrossRef support: email support@crossref.org or visit http://support.crossref.org  Webinars: http://www.crossref.org/01company/webinars.htmlStaying up to date:  Announcements forum: http://support.crossref.org/forums/147622-announcements subscribe via RSS or email  CrossRef Quarterly: CrossRef newsletter  Annual Meetings and Workshops: more info
    • 44. Questions?Patricia Feeney pfeeney@crossref.orgTechnical support: support@crossref.orgMembership support: info@crossref.org

    ×