This webinar gives an overview of the content registration process, and is targeted towards members who are new to Crossref or existing members who want to learn more about getting your metadata in to our systems . When content is registered with Crossref, members send us a range of information about the content ( but not the content itself )- we also enable persistent linking through identifiers. I’ll go over what content you can register, what metadata you should send us, our persistent identifiers, and the process of crafting deposit files and sending them to us.
What content can you register? We split content into several defined content types. We currently support deposits for: Journals and journal articles Books and book chapters Conference proceedings and papers Reports / working papers Dissertations Standards Posted content (preprints) Datasets Components (supplemental materials)
You can send us other types of content that don’t fit into these categories, we’ll collect some basic metadata (usually as a dataset) and we’re hoping to provide more robust support for more content types in the future.
When you register your content, you must send us basic citation metadata for every item you register. This includes titles, authors, publication dates, issue numbers, issns, isbns, anything that describes the content you’re registering. We have minimal requirements because we need to support a range of publication practices, but we ask that you send us as much metadata as possible, and that it be accurate and clean – the more robust your metadata is, the more likely your DOIs will be discovered and disseminated.
When you register your content you’re creating a complete metadata record, so we go beyond the basics -
We also collect non-bibliographic data about the items being registered - we collect reference lists, funding data, ORCIDs, license data, clinical trial info, information about errata, retractions, updates and more through our Crossmark service, abstracts, data about relationships between items, and we’re always adding more.
When you register your content with Crossref you are also registering a persistent identifier. Crossref uses DOIs for identifiers. When you submit your content, we register the DOIs you’ve included, and you and everyone else can then build persistent links to the item, ensuring that the links stay viable.
We have some basic requirements for the syntax of your identifier. A DOI (digital object identifier) consists of a prefix and a suffix. We assign the prefix to you when you become a member, you come up with a suffix pattern. When your DOI is registered, it becomes a link when the DOI registry URL (doi.org) is added to the front of the DOI. Over time, if the content moves, you can update the URL registered for the identifier, and the identifier-based URL will continue to resolve. Our identifiers can and do change hands, so if your content moves to a different platform, or content moves to your platform, you can update the existing identifiers to ensure persistence.
We get a lot of questions from new members about creating a suffix for your DOIs - we have some guidelines for suffixes but here’s the important stuff: you want to keep your suffixes consistent, simple, and short. They should be consistent for your sake, you should establish a pattern that’s easy to maintain. They should be simple for the same reason, and you want them to be short so that they don't take up endless amounts of space when used in citations.
I’m going to go into more detail about registering your content - the basics are simple: you create Crossref XML either through systems on your end or some tools on our end, you send the XML to us, we process it, and you (or your systems) verify that everything’s registered.
Creating XML - Everything that comes to our system is ultimately in XML. We’ve got a few ways around that but first I’ll go over the basics of what we need from XML. Crossref has its own metadata schema for deposits, a schema is a set of rules defining what can be included and in what format. Our schema is fairly rigid but comprehensive.
We update the schema regularly to accommodate the evolution of our services and rarely do anything that isn’t backwards compatible. Our most recent schema version is 4.4.0 but we accept deposits with 4.3.0 - 4.4.0. We have a metadata schema that can be used to deposit everything, we also have what we call a resource schema that can be used to update or add select pieces of metadata for your registered content.
if you are not able to generate XML, we do have some options. we have a manual- entry form, the web deposit form. the form is very basic: you enter your data field by field, and it writes and submits XML for processing. it’s near the end of its life, we’re going to be rolling out a hopefully improved deposit tool in early 2017, we’ll be able to auto-populate fields and add some features like saving and editing deposits that are missing from the current form
if you have a system that produces JATS or NLM XML, we’ve written an XSLT transformation for that, you can also upload JATS/NLM formatted files article by article to our web form
if you want to expand your existing metadata records by adding license and funding information, we support submission of that type of data by uploading a .csv file
You’ve created your file, now you need to get it to us. Most deposits are made by http post, if you have any sort of automated system you will be doing that. we do have an interface for uploading files one by one, and the web deposit form mentioned earlier will submit files for you.
when your file has been uploaded it’s added to a queue. most files are processed within minutes but we can get bogged down if traffic is high. if you’ve submitted something and don’t see a log, you can always check to see if your deposit is still in the queue.
if your deposit is processed successfully, great! you’re done, your metadata record is in our massive database and you can start linking persistently.
if your deposit fails, you’ll need to review your logs and correct whatever issues exist.
here’s an example of a submission log. the important part is at the bottom, the ‘batch-data’ section is a summary of your log results. if the record count and success count match, you’re done, everything was processed successfully. if there are any failures, (flagged in failure-count) you’ll need to address them, a failure means your record was not added to our system. a warning means that the record was added and the identifiers are registered but something needs attention.
submissions do fail, there are some odd problems but most fall into 3 categories: 1. your XML is not valid - we only accept XML that parses, so if your xml is invalid, the entire submission is rejected. we also do some validation on the system side, we try to do as much validation in our schema so that you can pre-validate, but some things are not possible with XML schema. we make sure ISSN and ISBN are valid, for example 2. your file might fail because of an issue with your title 3. there may be permissions issues - journal titles change hands quite often, if you’ve added or sold a title, please make sure we know about it so that we can make the approprioate ownership changes on our end.
we have one type of warning - if the metadata in your record matches something that’s already in our system, we’ll put a conflict warning in your log. sometimes these aren’t problems but the majority of conflicts that we identify are for duplicate items, or for items with very sparse metadata. both are bad.
If you’ve omitted or fudged some of this data it’s OK, I’m going to go into how to update your existing records with corrections and enhancements. When you create a record with us, the most persistent part is the identifier you register, the DOI - the rest of the record can be updated and expanded continuously.
Why a DOI and not a URL? DOIs are better. And When DOIs are maintain this process works well. Lets say all of these journals reference one article using its URL, rather than a DOI.
But what happens when the content moves. That content is no longer at the URL that is referenced by those journals.
But lets say that instead of using a URL, the journals reference that article using a DOI. The DOI will direct the readers to the URL registered with Crossref. If the journal article should change URLs, the publisher only needs to update the URL in one place, with Crossref, and the readers will continue to access the content in its new location. The publisher doesn’t have to tell all other publishers that the content moved.
As I mentioned you can add some types of metadata to your record after it has been registered. These include reference deposits (for our cited-by service), funding data, components, which are supplemental material metadata records, crossmark data, text and data mining, and relationships between DOIs and other identifiers
This means you can create a record for a journal article, for example, that contains just bibliographic metadata. You decide to participate in our cited-by service, so you can submit just the reference list to be added to your metadata record . You decide to submit CrossMark, funding and/or license data, that can be added to the existing record in segments without resubmitting the record as a whole. this works well if you partner with vendors to provide funding information, or your platform doesn’t support reference deposits and you want to do that on your own.
You can add this metadata as needed without incurring additional fees. With the exception of Crossmark metadata, updating a record doesn’t cost you anything - we charge a one-time deposit fee when a record is initially registered, likewise we’ll charge a one-time per record Crossmark fee when the Crossmark data is initially added,, but we don’t don’t charge for Crossmark updates to existing cross marked records.
If you’ve discovered errors in your metadata or otherwise need to make an update, you’ll need to redeposit your metadata with the changes included – any metadata already in our system will be overwritten, so make sure you send us everything, particularly when updating bibliographic metadata. For example, if you deposit your DOIs with an online publication date before the item has been published in print, you can update the metadata once the print info is available.
The data that can be submitted using a resource deposit doesn’t need to be included when only core metadata is updated, but within each resource type you need to submit the complete resource data.
So for example if you discover you’ve left out a grant number from your funding information, you can submit just the funding data in an update! You do need to include all funding data for the item however, we don’t append data within a resource- if you include just the grant number, the existing funder information will be overwritten and your record will still be incomplete.
URLs are a bit special - You can update your URLs by resubmitting the bib. portion of your metadata record, or send us a list of DOIs and URLs and we’ll update them for you
We’ll move on to evaluating your metadata, which can be tricky. We have some plans to make it much easier for you to see at a glance where your problem areas but they aren’t in place yet, and there’s still a lot that can be done now, I’m going to walk you through some basics. We’ll start with how to view the metadata you’ve registered with us
if you want to easily eyeball your basic metadata, you can use our metadata search interface - it presents a segment of the metadata, not everything, but it lets you know some basics . You can search by DOI or by ISSN, article title, author - it’s a free text search
- in this example, there’s an encoding issue in the article title, it jumps out at you, the diamond question mark - other common things to look for are author information. we have a lot of authors who use this tool for various reasons, and they’re constantly contacting us to complain about issues with their names in publisher metadata - misspellings, wrong order, or they’re missing entirely, which causes problems when they try to claim credit for their work.
We have a fairly robust REST API that is publicly available and can be used to retrieve or interrogate your metadata. It displays most of the metadata you’ve registered - references are not included unless you have opted to make them public. By default references are not distributed to the public but you can opt to make them public, if you’d like to do so please contact crossref support and we’ll tell you how to make that happen.
You can use the REST API to retrieve all metadata for your prefixes, or retrieve it DOI by DOI as displayed here.
We have some reports that help you with metadata issues. Some are sent by email, usually to the technical contacts we have for your organization, so if you’ve had some staff turnover make sure you keep us up to date. Also, please review the emails we send to you - they usually come from email@example.com.
We also send a fair number of emails to members about metadata quality issues. About 1/3 of the requests that come through crossref support are related to metadata quality issues. Metadata consumers report problems one by one - as you probably know, we don’t touch your metadata, so we need to pass those reports along to you for action. We get a lot of complaints from authors about how their names or article titles are represented, and our metadata affiliates also pass along complaints about missing page numbers, incorrect titles - little things, but they make a big difference. Our metadata is displayed everywhere, so even tiny errors can have a huge impact.
I’m going to go into detail about a few of our reports - we have a title list on our website that allows you to look up your titles by ISSN (or title) It displays coverage information, which can be illuminating - if you do nothing else, journal publishers might want to scan the coverage listed to make sure you haven’t missed any issues, or registered content with a publication year of 2032 or even 1332 (it happens). We also have the title data available as a .csv file, it’s a big file but if you have a lot of titles
If you need help, we have lots of documentation, we have a small but capable support staff, we’re US-based and give support mostly by email.
as mentioned i’ve included a list of resources in the slides, i”ve also linked to a video of a talk given by Ian Calvert at our recent Live 16 event - the talk is about a 1/2 hr. and focuses on metadata quality, he has some fun with Crossref metadata and data visualizationsso if you have some time please watch.
Content Registration and Updating Metadata (Turkish)
İçerik kaydı ile
… ve diğerleri
Neleri kayıt ettirebilirim?
yazar isimleri, ORCID’ler, üye ortaklar, makale
başlıkları, ISSN, ISBN, sayfalar, cilt, sayılar,
tarihler, tanımlayıcılar’ı içeren her şey
Daha fazla üst veri
referans listesi, fonlama verisi, ORCID’ler, lisans verileri, klinik
çalışma numaraları, dizgi hatası, geri çekme, Crossmark hizmetiyle
güncellemeler ve daha fazlası, JATS tabanlı özetler, öğeler arası
ilişkiler vb. …
Dijital Nesne Tanımlayıcısı (DOI)
DOI kayıt adresi: http://doi.org/
Ön ek: 10.1155/
Son ek: 2013/727539
DOI son ek
Daha fazlası için: https://support.crossref.org/hc/en-us/articles/214669823
Üst veri şeması: her şey için
Kaynak şeması: Bibliyografik olmayan üst verilerin mevcut kayıtlara eklenmesi için
- fon verileri, metin ve
veri madenciliği lisans
verileri ve Benzerlik
Kontorlü için taranan
- Tek JATS-formatında
makaleler yükler, XSLT
Web deposit form
- manual entry form,
XML oluşturur ve sizin
için yükler (2017 yılının
başında yeni sürümü)
HTTPS POST, Crossref admin interface, deposit form,
Güncelleme ve süreç
Tüm içerik kaydı gönderimleri aynı
Çoğu hızlı bir şekilde işlenir ancak
tam tersi durumda, sıradaki yerinizi
Başardınız. İçeriğiniz artık kalıcı
tanımlayıcılara ve Crossref üst veri
Başarısız oldunuz... içeriğiniz
<?xml version="1.0" encoding="UTF-8"?>
<doi_batch_diagnostic status="completed" sp="cr6.crossref.org">
<batch_id>12009_DOIs_unreg_2007-09-21</batch_id> <record_diagnostic status="Success">
<record_diagnostic status="Failure" msg_id="22">
<doi>all doi's of the current journal element</doi>
<msg>ISSN "15304086" has already been assigned to a different title/publisher/genre</msg>
<msg>Added with conflict</msg>
<record_count> 3 </record_count>
<success_count> 1 </success_count>
<warning_count> 1 </warning_count>
<failure_count> 1 </failure_count>
Gönderme Sorunları ve uyarıları
• XML sorunları - Bütün XML'ler geçerli olmalıdır
• Başlık yönetimi: başlıklar arasında tutarlılık uygularız,
çoğunlukla kitaplar ve dergiler için geçerlidir
• İçerik sahipliği sorunları: Bir başlık elde ettiyseniz,
bildiğimizden emin olun!
• Karışıklık: 2 veya daha fazla DOI aynı üst veriyi paylaşıyor
Üst verilere ekleme, üst
DOI'lerinizi korumak önemli
Okuyucular yayınladığınız içeriği bulabilir ve
DOI yeniden yönlendirir:
Üst veri ekle ( Kaynak arşivi aracılığıyla)
• Referans Arşivleri
• Düzenli taranan URL’ler (Benzerlik Kontrolü için kullanılır)
• Çoklu Çözünürlüklü ikincil URL'ler
• Bileşenler (ek materyal kayıtları)
• Bütçe üst verileri
• Crossmark verileri
• Metin ve veri madenciliği lisans ilişkileri
Üst verilere yönelik güncellemeler
Kayıtlarınızı tekrar gönderin!
- güncellemekte olduğunuz bölümdeki tüm üst verileri içermelidir
Sadece URL'yi güncelle
- kaydınızı tekrar gönderin (sadece bibliyografik üst veriler)
- bize DOI'lerin ve URL'lerin listesini gönderin ve bunları sizin için
kimdir en iyi
Üst verilerinizi görüntüleme
Crossref Üst Veri Taraması
Önekleriniz için üst verinizi görüntüleyin (JSON):
Tekli üst veri kaydınızı görüntüleyin:
• Schematron raporu: Haftalık e-postayla gönderilir, bazı 'dağınık'
üst verileri tanımlar
• Alan ('eksik üst veriler') raporu: doldurulmamış bibliyografik üst
veri alanlarını listeler
• Başlık listesi: sayı, cilt, yayın yılı
• Uyuşmazlık raporu: Aynı üst verilere sahip kayıtları tanımlar
• Kararlılık raporu: kararlaştırılmış ancak kayıtlı olmayan DOI'leri
• Crossref'ten e-postalar <— çok önemli
Yardıma ihtiyacınız mı
• Crossref metadata and schema documentation:
• Resource deposits: https://support.crossref.org/hc/en-us/articles/214002366
• Updating metadata: https://support.crossref.org/hc/en-us/articles/213022486
• Metadata Search: http://search.crossref.org
• Metadata API: http://api.crossref.org
• XML API: https://support.crossref.org/hc/en-us/articles/213420726
• Reports: https://support.crossref.org/hc/en-us/sections/202832743
• Support: http://support.crossref.org or firstname.lastname@example.org
• Ian Calvert talk from Live 16: https://www.youtube.com/watch?v=vEvvb70TfiE