# Item identifiers in CSL \[a rose by any other identifier\]

**URL:** <https://discourse.citationstyles.org/t/item-identifiers-in-csl-a-rose-by-any-other-identifier/648>\
**Category:** CSL Development\
**Created:** [June 1, 2009, 6:58pm UTC](https://discourse.citationstyles.org/t/item-identifiers-in-csl-a-rose-by-any-other-identifier/648 "2009-06-01T18:58:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Richard\_Karnesky](https://avatars.discourse-cdn.com/v4/letter/r/ba8739/32.png) [@Richard\_Karnesky](https://discourse.citationstyles.org/u/Richard_Karnesky)\
**Post date:** [June 1, 2009, 6:58pm UTC](https://discourse.citationstyles.org/t/item-identifiers-in-csl-a-rose-by-any-other-identifier/648/1 "2009-06-01T18:58:48Z")

</div>

I think when there was discussion of identifiers for bibo, I pointed out  
the list suggested in the MODS XML. That schema seemed to be built  
knowing that there are dozens of different identifiers (millions if you  
include all of the different possible local ids) & so this list isn’t  
"comprehensive" & there are identifiers not listed here (such as  
pmid/pmcid/arXiv/etc.):

hdl, doi\*, isbn\*, isrc, ismn, issn\*, issue number, istc, lccn\*, local,  
matrix number, music plate, music publisher number, sici\*, uri\*, upc\*,  
videorecording identifier, stock number

Starred entries are in bibo already. Bibo also includes:  
asin, coden, eanucc13, gtin14, oclc, pmid

I don’t know how, off-hand, the LoC uses issue number & the local  
identifier. All others from their list seem to be fairly unique  
identifiers. It’d be nice for bibo to support all of them & any could  
conceivably warrant citation in at least some edge/corner cases. I  
believe that some of the multimedia identifiers have been requested for  
Zotero, but that isn’t my field & it is hard to keep up. I know  
PMID/PMCID/arXiv numbers are fairly frequent requests.

I don’t know the best course to take with this “identifier soup” is, but  
perhaps we should decide which of these should and should not be  
"cite-able" via CSL or if there is a smarter way to do this before  
adding them each individually.

–Rick

---

<div class="post-metadata">

**Author:** ![Bruce\_D\_Arcus1](https://avatars.discourse-cdn.com/v4/letter/b/4bbf92/32.png) [@Bruce\_D\_Arcus1](https://discourse.citationstyles.org/u/Bruce_D_Arcus1)\
**Post date:** [June 1, 2009, 7:18pm UTC](https://discourse.citationstyles.org/t/item-identifiers-in-csl-a-rose-by-any-other-identifier/648/2 "2009-06-01T19:18:37Z")

</div>

> I think when there was discussion of identifiers for bibo, I pointed out  
> the list suggested in the MODS XML. That schema seemed to be built  
> knowing that there are dozens of different identifiers (millions if you  
> include all of the different possible local ids) & so this list isn’t  
> “comprehensive” & there are identifiers not listed here (such as  
> pmid/pmcid/arXiv/etc.):
> 
> hdl, doi\*, isbn\*, isrc, ismn, issn\*, issue number, istc, lccn\*, local,  
> matrix number, music plate, music publisher number, sici\*, uri\*, upc\*,  
> videorecording identifier, stock number
> 
> Starred entries are in bibo already. Bibo also includes:  
> asin, coden, eanucc13, gtin14, oclc, pmid
> 
> I don’t know how, off-hand, the LoC uses issue number & the local  
> identifier. All others from their list seem to be fairly unique  
> identifiers. It’d be nice for bibo to support all of them & any could  
> conceivably warrant citation in at least some edge/corner cases.

We haven’t gotten any requests for new ones, but BIBO’s been designed  
to be extended. One can either ask us to add a new id in the bibo ns,  
or one can create their own and reference the bibo:identifier property  
(which in turn references dc:identifier).

> I believe that some of the multimedia identifiers have been requested for  
> Zotero, but that isn’t my field & it is hard to keep up. I know  
> PMID/PMCID/arXiv numbers are fairly frequent requests.
> 
> I don’t know the best course to take with this “identifier soup” is, but  
> perhaps we should decide which of these should and should not be  
> “cite-able” via CSL or if there is a smarter way to do this before  
> adding them each individually.

I think it’s fine to do ad hoc, but to add them to CSL, there has to  
be a clear use case (e.g. a style that requires it).

Bruce
