Patricia Feeney
Metadata Quality Coordinator
Managing your
metadata quality
Agenda
I. Metadata quality audit
II. DOI registration
III. Conflicts overhaul (discussion)
IV. Metadata Quality tools
Best query ever -> bad metadata = match
Mediocre query -> bad metadata = match
Horrible query -> bad metadata = match
Best...
Current efforts include:
 Reports
Resolution report (emailed monthly)
depositor report (on website)
crawler (on website)
...
Metadata Quality Audit
A Metadata Quality Audit will:
 provide publishers with detailed feedback on the
quality of their ...
Audit Scope
I. DOI resolution
II. Conflicts
III. Overall metadata
quality
IV.Metadata
maintenance Hello, I’d
like to audit...
Level I: DOIs that have been distributed but not deposited
and resolve to the Handle error page. *
Level II: DOIs resolvin...
II. Conflicts
Conflicts occur when two (or more) DOIs are
deposited with identical metadata.
Level I: conflicts created be...
Quality of deposited metadata
I. Missing metadata: is all available metadata
deposited?
II. Accuracy: is metadata correct?...
Maintenance
I. Gaps in coverage - this usually indicates
undeposited DOIs (very very bad)
II. Currency of deposits - are d...
Actionable Areas
DOI Resolution:
Level I (Undeposited DOIs)
Level II (DOIs resolving to error page)
 If action is not tak...
Audit Process
1. Notification:
Auditees will be informed
of pending audit;
data collection begins (1-2
weeks for most memb...
Questions?
II. DOI Registration Pilot
DOIs should without exception be registered before
they are released to the public.
Most DOIs r...
DOI selection: At the moment, we will register DOIs
reported by end users, using the DOI error report as
a source.
DOI error report:
Implemented mid-2008
~4,000 DOI errors reported
monthly
> 1,400 fixed monthly through
publisher depos...
We will register DOIs that meet the following criteria:
 Have been distributed publicly by the
publisher/prefix owner
 H...
DOI Registration Process
1. DOI reported: a user reports an unresolving DOI
using the DOI error form
2. Technical contact ...
Questions?
Conflicts overhaul
Conflicts occur when two (or more) DOIs share
the same metadata, suggesting two DOIs are
assigned to a ...
Why are conflicts bad?
 Only one DOI should be assigned per item
 Queries will return multiple DOIs, causing
confusion
...
We currently have ~200,000+ conflicts in our
system. Not all of them are a problem:
 For some items, our schema only allo...
Legitimate conflicts
Conflict between 2 prefixes:
http://dx.doi.org/10.1639/0044-7447(2001)030[0037:IOPOFU]2.0.CO;2
http:/...
‘Bad’ conflicts
Conflicts with minimal metadata:
10.1002/ijc.11095
10.1002/ijc.11093
Conflict due to content type:
10.1520...
Elements considered during
conflict generation:
 Content type
 Journal, book and/or series
title
 Article title /conten...
Ideas?
What should our minimum set of metadata
be?
How should conflicts be
monitored/reported?
Managing your
metadata quality
Sample #1: incorrect metadata
Q: My link resolver is retrieving the wrong metadata for DOI
10.1002/rra.1288, causing our l...
Sample #2: messy metadata
Q: I know DOI 10.1068/p6742 exists, why doesn’t my query
work?
A: Let’s check the guest query fo...
Sample #3: duplicate authors
Q: Why does DOI 10.2307/1382491 have multiple versions of
the same author?
A: attempt to impr...
New(ish) tools for managing
metadata and deposit problems
Schema documentation:
http://www.crossref.org/schema/documentati...
Schematron update
Schematron reports notify depositors of non-fatal
deposit issues
 35-40 emails sent out weekly
 Alerts...
Schematron Warnings
page number
contains
underscore
2%
first page
contains dash
4%
last page
contains dash
7%
Jr.' in surn...
Questions?
support@crossref.org
pfeeney@crossref.org
Managing Your Metadata Quality 2010 CrossRef Workshops
Upcoming SlideShare
Loading in...5
×

Managing Your Metadata Quality 2010 CrossRef Workshops

1,143

Published on

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,143
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • …so we’re going to being auditing publishers, audit in the sense of providing a detailed, personalized, hopefully helpful review of a publisher’s metadata quality.We’re also welcoming the opportunity to improve our own processes, whether it be by refining reports or creating new tools to help with deposits.
  • Conflicts are identified:upon deposit in the submission logsin the monthly conflict report(We’ll discuss conflicts at length later) We have four levels of conflicts as well – Level I: conflicts created between members * These typically happen when a title is acquired by a new publisher and the publisher creates new DOIs for already-published content without checking first to see whether or not DOIs have already been created. In these cases the originally deposited DOIs are usually left untended and aren’t updated, leading to a ton of level II DOIs.Level II: conflicts within a publisher prefix(es) *Some members create conflicts with themselves – either they change their DOI suffix conventions and decide to apply the change retroactively, or through negligence, or ??? I’m not sure of other reasons but it happens fairly often so there must be some.These types of conflicts are most likely going away with the new system (more later):Level III: conflicts created due to insufficient metadata +Level IV: conflicts created due to item/content type +
  • We’re also going to review overall deposited metadata quality, which many members will find most useful.Missing metadata: is all available metadata deposited?One of the most common questions I get from new publishers is ‘I’ve deposited a few issues but can’t retrieve my what am I doing wrong? And the answer almost always is ‘deposit more metadata’ II. Accuracy – is metadata correct?This isn’t a big problem across our membership but when it’s a problem, it’s a problem. Again, it’s one of those things that’s hard to identify – we rely on reports from end users, usually librarians. Big accuracy problems include 1. incorrect ISSNsfor a title, different title variants(these will be managed differently in the new system, hooray), 2. depositing an item online then not updating to include print metadata and 3. author name spelling / order - this isn’t a rampant problem but we do hear from a lot of authors when their names are incorrectIII. Unusual metadata: again, not a huge problem, but some non-standard publications get shoehorned into our available content types. Sometimes it’s unavoidable, but we might have a better approachIV. Overall quality: is metadata messy?This means malformed special characters, non-essential markup in titles, dashes in page ranges, surnames in given name element, organization names in surname instead of <organization>, including ‘Jr.’ in the surname
  • The final category is maintenance – usually deposited metadata requires very little maintenance if it is sound to begin with, beyond updating URLs of course. There are a few things to cover, however:Gaps in coverage: Many of you have gaps in coverage – you submit an issue for deposit, the deposit fails, you don’t notice…usually the end result is long-term undepositedDOIsAgain, currency of deposits – are deposits made ahead of DOIs being released into the wild? These are usually short-term undepositedDOIs and are eventually deposited but they are damaging as wellTitle maintenance – this process will change with the new system but we’ll still need to do some curating of titles. One thing we’ll focus on in the audit is abbreviations attached to your titles as they help with query matching.Reference linking compliance
  • Our hope is that once systemic problems are pointed out to publishers these measures won’t be necessary, but we will take action if we have to.
  • (broken record) As mentioned previously, undepositedDOIs are increasingly becoming a problem. DOIs should without exception be registered before they are released to the public. An unregistered DOI is more than a string of characters – it’s a source of frustration for researchers, librarians, authors – anyone trying to link to your content.DOIsshould be registered before they’re released to the public. Most are, but most isn’t good enough, so we’re starting a pilot project to register DOIs that meet certain criteria.
  • End users find undepositedDOIs very frustrating.
  • All attempts to resolve unregistered DOIs resolve to this page. We worked with CNRI to create this page a few years ago – prior to that, the error page had CNRI’s email address – CNRI would forward DOI errors to us as they were reported, and we’d send them along to publishers. This form is a big improvement. Instead of emailing CNRI, users can just submit a form so instead of a few hundred complaints a week we get over a thousand. A user can submit just the DOI, but the form also collects the referring page (admittedly not always useful, depending on the page), any notes, and allows the user to enter their email address. We send them an alert when/if the DOI is registered.
  • The DOI error report is a big improvement over the past email-based method, and allowed us to compile data which made the unregistered DOI problem more obvious. Currently the DOI error report is the best source for data on unregistered DOIs.An average of 4,000 DOI errors are reported monthly. Less than 1,400 are fixed monthly through publisher deposits. Some of the unfixed DOIs aren’t legitimate DOIs, but many are - We don’t have specific data yet on what percentage of legitimate DOIs remain unregistered at the end of a month but we should once our project has been under way for a month or so.
  • We’ll only register DOIs that have been distributed publicly by the publisher/prefix owner – if for some strange reason someone is generating DOIs with your prefix then not depositing them (it happens, usually inadvertently – someone reverses digits in a prefix, for example) you won’t be liable. We likewise won’t register DOIs that have been misrepresented in areas beyond your control. Have an identifiable response page – we will verify that the DOI has been distributed, we won’t register something just because a user says it existsHave been reported to the publisher’s technical and business contacts – we notify you well in advance of registration
  • Things to note:This is a pilot project so we’re still refining the process – most of the refining should be on our end and not affect members. The initial email that went out to business contacts didn’t have the ‘final’ list of DOIs to be registered but any emails going out now do.There will ultimately be a charge for this process, and it will be significant enough that you wont’ want to use the DOI error form instead of the web deposit form to create DOIs – its not the most effective, efficient or accurate way to register DOIs.
  • ***this is a big problem
  • Despite our efforts the number of conflicts continues to grow.Conflicts as they are work well to identify conflicts between journal article DOIs and most book DOIs, but there are shortcomings in the process:a.) journal items such as letters to the editor, book reviews, erratum etc. often generate conflictsb.) book chapters, standards, and reports can generate bogus conflicts in some situationsOverall, it makes the conflict process not as useful as it should be.
  • Sample #1 – publisher has deposited all relevant metadata and DOIs are assigned to two distinct items, but a conflict was createdSample #2 – DOIs for standards can generate conflicts - they often have very similar metadata despite being distinct items
  • Note: We did offer for many years the option to include a flag in your metadata that would allow you to bypass conflict creation – this feature was revoked because some very large publishers were including the flag in *all* deposits, creating conflicts that couldn’t (and still can’t) be identified.Possible questions: minimum metadata set? (Do we require a certain amount of metadata to be present before generating a conflict?)How should these be monitored (in submission log, maintain current conflict reports?)Are ‘conflicts’ a valid concept? Should we reject deposits with conflicts (once we have refined our conflict identification methods obviously)Other ideas?
  • Note: the metadata for these DOIs will (hopefully) be corrected soon – once the metadata is corrected the queries used in these examples will resolve.
  • In this example, multiple versions of authors have been deposited to improve query matching. This creates problems when metadata is retrieved for display.Solution: CR will work on improving things on our end – our system does do some character matching already.
  • Managing Your Metadata Quality 2010 CrossRef Workshops

    1. 1. Patricia Feeney Metadata Quality Coordinator Managing your metadata quality
    2. 2. Agenda I. Metadata quality audit II. DOI registration III. Conflicts overhaul (discussion) IV. Metadata Quality tools
    3. 3. Best query ever -> bad metadata = match Mediocre query -> bad metadata = match Horrible query -> bad metadata = match Best query ever -> good metadata = match ✓+ Mediocre query -> good metadata = match (probably) ✓ Horrible query -> good metadata = match (maybe) ✓- Metadata Quality Audit: Overview Accurate and complete metadata is vital to querying and citation linking. If the metadata for a DOI is incorrect, incomplete, or messy, a match can't be made, regardless of the quality of a query.
    4. 4. Current efforts include:  Reports Resolution report (emailed monthly) depositor report (on website) crawler (on website) field report (on website) conflict report (on website, emailed monthly) schematron reports (emailed weekly) failed query report (on website) DOI error reports (emailed daily)  Contact members individually (as issues arise)  Documentation and communication
    5. 5. Metadata Quality Audit A Metadata Quality Audit will:  provide publishers with detailed feedback on the quality of their metadata by identifying problem areas  identify members who need attention  provide motivation and support to members with metadata issues The intent of the audit is to provide information, but there may be consequences for extreme abusers.
    6. 6. Audit Scope I. DOI resolution II. Conflicts III. Overall metadata quality IV.Metadata maintenance Hello, I’d like to audit you Great, lets get started! Hooray!
    7. 7. Level I: DOIs that have been distributed but not deposited and resolve to the Handle error page. * Level II: DOIs resolving to an error page * Level III: DOIs with response page blocked by access control Level IV: DOIs that resolve to an inadequate response page. I. DOI Resolution * actionable transgressions
    8. 8. II. Conflicts Conflicts occur when two (or more) DOIs are deposited with identical metadata. Level I: conflicts created between members * Level II: conflicts within a publisher prefix(es) * Level III: conflicts created due to insufficient metadata + Level IV: conflicts created due to item/content type + * actionable transgressions + this may change, more later
    9. 9. Quality of deposited metadata I. Missing metadata: is all available metadata deposited? II. Accuracy: is metadata correct? III. Unusual metadata: does metadata fit into the correct content type? IV. Overall quality: is metadata messy?
    10. 10. Maintenance I. Gaps in coverage - this usually indicates undeposited DOIs (very very bad) II. Currency of deposits - are deposits made ahead of DOIs being distributed? III. Title maintenance - less of a problem with recent title restrictions, but we still have problems, title abbreviations IV. Reference linking compliance
    11. 11. Actionable Areas DOI Resolution: Level I (Undeposited DOIs) Level II (DOIs resolving to error page)  If action is not taken within a reasonable time period (TBD), DOIs will be registered on behalf of the member (eventually for a fee)  Continual distribution of unregistered DOIs may affect membership Conflicts: Level I conflict created between members Level II conflicts within a publisher prefix  A $2 per DOI conflict penalty fee may be imposed for conflicts of this type if they are not resolved within a reasonable time period (TBD). Metadata Maintenance: Outbound linking compliance  members found to not be linking during the audit will be subject to non-linking penalties
    12. 12. Audit Process 1. Notification: Auditees will be informed of pending audit; data collection begins (1-2 weeks for most members) 2. Data delivery Audit document will be emailed to member for review 2 weeks prior to audit (longer if necessary); audit scheduled 3. Audit phone conference, follow-up scheduled (if necessary) 4. Response member/CR reconvene to discuss progress on audit findings 5. Follow-up (if necessary)
    13. 13. Questions?
    14. 14. II. DOI Registration Pilot DOIs should without exception be registered before they are released to the public. Most DOIs resolve, but the ones that don’t are a big problem. Solution: we’re going to register them* *(ideal solution: publisher registers them)
    15. 15. DOI selection: At the moment, we will register DOIs reported by end users, using the DOI error report as a source.
    16. 16. DOI error report: Implemented mid-2008 ~4,000 DOI errors reported monthly > 1,400 fixed monthly through publisher deposits Some of the unfixed DOIs are not ‘real’ DOIs, but many are.
    17. 17. We will register DOIs that meet the following criteria:  Have been distributed publicly by the publisher/prefix owner  Have an identifiable response page  Have been reported to the publisher’s technical and business contacts
    18. 18. DOI Registration Process 1. DOI reported: a user reports an unresolving DOI using the DOI error form 2. Technical contact notified (DOI error report email) 3. CrossRef review: CR staff reviews reported DOIs and expires DOIs that do not meet our registration criteria 4. Business contact notified: 2 weeks from the initial report, business contact is notified of remaining valid unregistered DOIs. 5. CR deposit: after 2 weeks have passed from business contact notification, CrossRef will register any undeposited DOIs.
    19. 19. Questions?
    20. 20. Conflicts overhaul Conflicts occur when two (or more) DOIs share the same metadata, suggesting two DOIs are assigned to a single item.
    21. 21. Why are conflicts bad?  Only one DOI should be assigned per item  Queries will return multiple DOIs, causing confusion  Some queries (OpenURL) may not return a DOI if multiple results are present  Conflicts between two DOIs often result in one of the DOIs being neglected***
    22. 22. We currently have ~200,000+ conflicts in our system. Not all of them are a problem:  For some items, our schema only allows minimal metadata  Some content types require matching metadata (standards and book chapters with minimal metadata (dictionaries) for example)
    23. 23. Legitimate conflicts Conflict between 2 prefixes: http://dx.doi.org/10.1639/0044-7447(2001)030[0037:IOPOFU]2.0.CO;2 http://dx.doi.org/10.1579/0044-7447-30.1.37 Sample query Conflict within 1 prefix: http://dx.doi.org/10.3724/SP.J.1006.2008.00070 http://dx.doi.org/10.3724/SP.J.1006.2008.00770 Journal Title Year Vol Issue Page Author Article Title AMBIO 2001 30 1 37 Köhlin Impact of Plantations on Forest Use a... Journal Title Year Vol Iss Page Author Article Title ACTA AGRONOMICA SINICA 2008 34 5 770 Zhang Differential Gene Expression in Upper…
    24. 24. ‘Bad’ conflicts Conflicts with minimal metadata: 10.1002/ijc.11095 10.1002/ijc.11093 Conflict due to content type: 10.1520/C0506-10 10.1520/C0506-10A 10.1520/C0506-10B Journal Title Year Vol Issue Page Author Article Title International Journal of Cancer 2003 104 6 798 Errata Book Title Year Editi on Page Author Title Specification for Reinforced Concrete... 2010 2010 C13 Committee
    25. 25. Elements considered during conflict generation:  Content type  Journal, book and/or series title  Article title /content_item title (book chapters)  Publication year  Volume  Issue  First page  Author  Edition If there is a match between all deposited elements, a conflict is generated. 2 Items with matching journal title, volume, issue, and article title will cause a conflict.
    26. 26. Ideas? What should our minimum set of metadata be? How should conflicts be monitored/reported?
    27. 27. Managing your metadata quality
    28. 28. Sample #1: incorrect metadata Q: My link resolver is retrieving the wrong metadata for DOI 10.1002/rra.1288, causing our links to break - here is my query*: http://www.crossref.org/openurl?pid=pfeeney@crossref.org&aulast=Null& title=River Research and Applications&volume=26&issue=6&page=663&year=2010 *query metadata matches the response page metadata A: Two problems with deposited metadata (DOI query): #1 <year media_type="print">2009</year> #2 <pages> <first_page>n/a</first_page> <last_page>n/a</last_page> </pages>
    29. 29. Sample #2: messy metadata Q: I know DOI 10.1068/p6742 exists, why doesn’t my query work? A: Let’s check the guest query form Metadata for article: Newport R, Preston C, 2010, "Pulling the finger off disrupts agency, embodiment and peripersonal space" Perception 39(9) 1296 – 1298 Problem is: author surname is deposited as: <person_name sequence="first" contributor_role="author"> <given_name>Roger</given_name></given_name> <surname><surname>Newport</surname></surname> </person_name>
    30. 30. Sample #3: duplicate authors Q: Why does DOI 10.2307/1382491 have multiple versions of the same author? A: attempt to improve query matching <contributors> <person_name sequence="first" contributor_role="author"> <given_name>Erling Johan</given_name> <surname>Solberg</surname> </person_name> <person_name sequence="additional" contributor_role="author"> <given_name>Bernt-Erik</given_name> <surname>Sæther</surname> </person_name> <person_name sequence="additional" contributor_role="author"> <given_name>Bernt-Erik</given_name> <surname>Saether</surname> </person_name> </contributors>
    31. 31. New(ish) tools for managing metadata and deposit problems Schema documentation: http://www.crossref.org/schema/documentation/ or linked from help doc Reporting problems / asking for help:  Help documentation (http://www.crossref.org/help/)  Support portal and forums (http://support.crossref.org)  Contact support@crossref.org
    32. 32. Schematron update 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
    33. 33. Schematron Warnings page number contains underscore 2% first page contains dash 4% last page contains dash 7% Jr.' in surname 61% punctuation in surname 26% Jr. in surname: Araújo Jr Prata Jr. Szezech Jr. Punctuation in surname: (Earven) Tribble Frederick (Frikkie) J. Arch Marin march@ub.edu Plauchu******** Other rules:  ‘ed’ ‘iss’ ‘vol’ in edition, issue, volume elements  Publication year exceeds current year by >2  Surname / title all upper case
    34. 34. Questions? support@crossref.org pfeeney@crossref.org
    1. ¿Le ha llamado la atención una diapositiva en particular?

      Recortar diapositivas es una manera útil de recopilar información importante para consultarla más tarde.

    ×