3 ms·
> With any of these identifiers, the thing you do instead of just punching the ID into a search engine, is to first search for either 1. the website of the enti
by IanCal 6y ago
> With any of these identifiers, the thing you do instead of just punching the ID into a search engine, is to first search for either 1. the website of the entity you know owns the thing, or 2. some kind of "catalog" site; and then plug the otherwise-non-unique identifier in there. Your identifier, despite not being unique generally, is unique when put in the context of a domain-specific keyspace.
Nit-picky perhaps but DOIs are extremely unlikely to be used elsewhere to mean something else. In a search engine you'll get either the original article or articles that cite it. The reason you'd use something else to get to the article is that there's a single location for all of them to be resolved, and even then people will still just google them. In fact, googling them can be more reliable when they've not been correctly registered.
It's not really counter to the general point, they're not useful for products and perhaps I misread your statement but DOIs absolutely work as "just look for this string".
- derefr 6y agoYou're right; DOIs aren't a good example. Edited to remove.
- rb12345 6y agoIn the case of DOIs, https://dx.doi.org/${DOI} https://dx.doi.org/${DOI} should also return the target article with no need to search.
- IanCal 6y agoOnly if correctly registered :) it does usually work but I'm always surprised at how frequently they don't. I work with large amounts of them though, which tends to bring out the edge cases. Googling can be more reliable, and typically safe given how unique they tend to be (again, weirdly not always). A bonus is you may get results for related pages that reference your wanted paper