IDs, URLs and the Web
In most cases an Event is generated when an Agent visits a webpage and notices a link between that webpage and a piece of Crossref registered content. The result is an Event where the Subject is the webpage and the Object is the registered content. We use the 'best possible' URL to refer to both the Subject and the Object.
When we say 'best' URL, we are trying to find the URL that uniquely represents the content. This allows people using the data to find Events that correspond to the same content. If a particular piece of content is referred to using a range of different URLs, it can be difficult or impossible to find Events that refer to it.
Broadly speaking, the best URL for a piece of registered content (i.e. the Object, such as a journal article) is a DOI. The best URL for a webpage (i.e. the Subject, such as a blog post) is its canonical URL.
Canonical URLs for Subjects
When an Agent visits a webpage, it records the URL that it visited. The webpage itself may indicate the 'best' URL to use via a canonical URL link. Including a canonical URL in a webpage's metadata is search engine best practice (encouraged, for example, by Google).
A webpage may be accessed via a number of different URLs. To take a real example, the following three URLs all correspond do the same content:
Whilst it's important to record exactly where we looked to find a particular link, it's also important that we represent content as consistently as possible. The above webpage has metadata indicating the canonical URL. When we identify a canonical URL we use this URL as the
subj_id in the Event. We store the URL we visited in the
subj.url so you always know which URL we visited in the first place.
Removing tracking URLs
Not all webpages provide canonical URLs. When this happens we use the next-best URL, which is the one we visited. We apply a couple of cleaning steps first:
If the URL we visited resulted in any redirection (for example some RSS aggregators include their own redirection URL) we will record the final URL that we arrived at. This means that the URL that the content was recorded against may be different from the URL that was visited from a Newsfeed. An example of this is:
- URL found in newsfeed:
- URL destination:
Secondly, some services (such as the above example) apply tracking URL parameters. These do not affect the content, but allow people to track how URLs are shared. Common examples include
utm_campaign which are used by Google Analytics. The presence of these URL parameters can be confusing, as they mean that one piece of content can be represented by an infinite number of different URLs.
To counteract this, we remove a known set of tracking parameters from URLs before using them in the
subj_id field. Here is an example:
- URL that we visited:
- URL that we use to record the content:
Which URL is used for
When picking a
subj_id, we use the following options in order:
- The canonical URL as indicated in the HTML metadata.
- Failing that, URL where we found the content (if there were redirects, then the final destination), with tracking parameters removed.
- Failing that (e.g. if there were errors removing the tracking parameters), the URL that the Agent visited.
DOIs for Objects
In most cases, the Object of an Event is a piece of Crossref or DataCite registered content. For these, the best URL to unambiguously identify the content is the DOI. The process of matching a DOI also confirms that it is actually a piece of registered content. If we cannot find the DOI, we cannot verify that it is Crossref registered content, so we do not produce an Event.
We look for DOIs as well as landing pages
Event Data Agents are on the look out for links to registered content items, but people on the Web use a variety of methods to refer to them. They could use a hyperlinked DOI (one you can click), or a plain-text DOI (one you can't click). They could also use the Article Landing Page (the page you get to when you click on a DOI). Every source is different: we tend to see most people using Article Landing Pages on social media and in blog posts, but on Wikipedia DOIs are frequently used.
Every Agent will attempt to match registered content items in as broad a manner as possible by looking for linked and unlinked DOIs and Article Landing Page URLs. We maintain a list of domain names that belong to publishers (see the Artifact page for more information) and track and query for those domains. When we see a URL that could be a landing page, we attempt to match it to a DOI.
Landing page matching isn't perfect
If we can't deduce that a landing page is for one of our registered content items, then we won't generate an Event. After all, not every URL on every publisher's site corresponds to an article.
If someone discusses an article in a blog and uses its DOI, and that DOI exists, there's an almost certain chance that we will match it and produce an Event. If they discuss an article and use its landing page URL, there's a very good chance that we will match it, but the matching process isn't perfect.
You should therefore be aware of the difference between Events that were matched using the DOI and those that were matched using the landing page URL, and that we may have a better rate of matching for DOIs.
Matching also varies from publisher to publisher. For some landing page domains we can easily match the DOI. For some we need to do a bit more work. For others, it's impossible.
We produce a full trace of every attempt in Evidence Records and Evidence Logs. See the service pages for information on how to access these.
If you are a publisher, refer to the Best practice for publishers to ensure we have the best chance at matching Events for your content.
You might want to know the difference
When we match an Event because someone discussed an Item using its DOI, the only processing that takes place is normalizing the DOI and checking that it exists. You can see the full process in the Evidence Record for that Event, even though there's not much to it.
When we match an Event because someone used a landing page, the Agent has to do some work to match it to a DOI. When we do this, we are making an implicit assertion that 'this landing page is for this DOI'. Our Agents reflect the data they find, so it's important to understand that this automated process and might not be 100% reliable.
You can put Event Data to different uses. You might want to know:
- How often do people use DOIs compared to landing page URLs?
- I'm only interested in data where I can be 100% sure that only the DOI is used.
- I want to know about these articles. I don't care what URL was used to refer to them.
When an Event links to a registered content item (nearly all Events do) it will use its DOI as the
obj_id. The corresponding optional
obj metadata may contain a
pid field (which is always the same) but additionally it may contain a
If the URL field is the same as the PID field (i.e. a DOI) then you know that the Event was collected because its DOI was mentioned. If the URL field is different, (e.g. a Landing Page URL) then you know it was collected because the landing page domain was mentioned.
It's always not one-to-one
DOIs can be assigned to books and book chapters, articles and figures. Each Agent will do its job as accurately as possible, with minimal cleaning-up, which could affect interpretation.
This means that if someone uses the DOI for a figure within an article in a blog post, we will record that figure's DOI. If they use the landing page URL for that figure, we will do our best to match it to a DOI. Depending on the method used, and what the publisher landing page tells us, we may match the article's DOI or the figure's DOI.
Sometimes two pages may claim to be about the same DOI. This could happen if a publisher runs two different sites about the same content. It's also possible that a landing page has no DOI metadata, so we can't match it to an Event.
The reverse is true: sometimes two DOIs point to the same landing page. This can happen by accident. It is rare, but does happen. This has no material effect on the current methods for reporting Events.
Landing page data can be out of date
We periodically scan our DOIs, take a sample and find the domains that are used by publishers. This is documented in our Artifacts, which have versions and date stamps. We therefore might miss Events in the time between a new domain being used and the Artifact being updated.
If a publisher stops using an Article Landing Page domain, we will not remove it from the list. Agents may at any time go back and re-process old data, or work with dumps of historical data. People may reuse content that points to old landing pages. We still want to attempt to match these if possible. Therefore the domain list Artifact only grows. As with all Artifacts, you can browse all past versions to see how it changes over time.
We don't match all domains
Some DOIs have been registered to domains such as
youtube.com. We have no way of matching YouTube videos back to DOIs. So, we exclude this small number of domains that we can never match.
We don't know all of the landing page URLs, and it's not possible to discover them all
Every DOI has a Resource URL, which is where you are sent when you click on a DOI hyperlink. This is known to Crossref and can be retrieved from the DOI system. However, in a large number of cases, this is not the final destination URL. Many publishers operate their own internal linking and redirecting services, which mean that when you click on a DOI you are sent through a series of redirects before ending up at the destination Article Landing Page.
Let's take a simple example of a Crossref demonstration DOI. The Crossref DOI
10.5555/12345678 has the Resource URL
http://0-psychoceramics-labs-crossref-org.libus.csd.mu.edu/10.5555-12345678.html, which you can see in the article metadata. If we follow the DOI we see only one redirect, that from the DOI link.
||Initial DOI redirect from Resource link|
In cases like this, the landing page is known to Crossref, as it's the same as the Resource link.
Let's take another example, the PLOS DOI
10.1371/journal.pone.0160106. The Resource link, which you can see in the article metadata is
http://dx.plos.org/10.1371/journal.pone.0160106, which is an internal link resolver operated by PLOS.
If we follow the DOI URL, we see the following chain of redirects.
||Initial DOI redirect from Resource link|
||Internal redirect within PLoS Site|
||Internal redirect within PLoS Site|
In cases like this, the final landing page is different to that registered with Crossref, so we can't know without following it.
10.XXX/YYY.06.008 without cookies enabled produces:
||Initial DOI redirect|
||Final error page|
The final step in this chain is an error page stating that cookies are required and it is therefore impossible to resolve the DOI using HTTP.
Crossref Membership rules #7 state that:
You must have your DOIs resolve to a page containing complete bibliographic information for the content with a link to — or information about — getting the full text of the content.
Where publishers break these rules, we will alert them.
Because of restrictions like this, along with other practical constraints, we cannot and do not attempt to visit every DOI ahead of time to find its landing page.
External parties matching content to DOIs
Crossref Agents are not the only ones creating Events, and therefore not the only ones that produce DOI-to-URL mappings.
It is possible for an external party to store activity around Items and use their own systems to match Items to DOIs, landing pages and other identifiers. Although their APIs can be queried using DOIs, they might have recorded activity against the Item using its landing page URL or another identifier. The internal mappings between various identifiers may change from time to time, which may mean that certain activity may be reported against one Item at one point in time, and then against another Item at another point in time. Data may therefore change over time and this may be caused by algorithms being updated, rather than user activity.
Event Data provides all available evidence for all Events, but is unable to provide visibility of mappings within external services. Data from these sources of this type should be interpreted with this in mind.