Popular archive database ids

Ok, I understand that user fields is not good, but we now have some popular article databases, which have standard ids for stored articles: JSTOR, Bibcode (NASA ADS), PubMed, arXiv. I think it is very useful to have corresponding fields in Zotero's article records.
  • What's the use case here? We'll get PubMed (and PMCID). We'll likely find a solution for arXiv. But why would you want to store a JSTOR ID in a separate field? And where would the list end?
  • Use case is to cite many id's at the same time for faster search. For example, one reader may have access only to NASA ADS and find articles instantly by Bibcode by copying it to browser address bar. Another reader may have only JSTOR, and so on. Personally, I work a lot with Wikipedia and would like to build complex references for sources. See for example:
    http://en.wikipedia.org/wiki/James_Chadwick#References (that's not mine, in case)
  • At least one of the Wikipedia citation templates provides for embedding citation metadata in the page, in COinS format. Metadata can be digested by openURL resolvers, which is a more robust way of handling the access problem.

    You might check out the Citoid project at Wikipedia, which aims to streamline the citing process for authors.
  • Thank you for tipping off about citoid. I will try it in my local wiki. OpenURL is also very interesting, but it has many issues:
    * unfortunately, this way is not robust: having installed OpenURL Referrer add-on for Firefox, I cannot connect to free.lm.worldcat.org;
    * not many people aware of COinS in wiki pages and how to setup resolver;
    * I work with Russian Wikipedia, and none of it's citation templates uses COinS;
    * not many metadata will be visible in printed paper ;)

This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.

Sign In or Register to comment.