KCite Plugin
The KCite plugin provides a means for referencing scholarly works in WordPress posts. The author includes a unique identifier for a publication in their post, and the plugin queries a web service to retrieve metadata about that publication. This metadata is then used to build a bibliography at the foot of the post, with in-place citations in the text referring to it.
The [cite] shortcode is interpreted to produce citations from the appropriate sources, also produces a formatted bibliography at the foot of the post, with appropriate links to articles.
The plugin uses the CrossRef API to retrieve metadata for Digital Object Identifiers (DOIs) and NCBI eUtils to retrieve metadata for PubMed Identifiers (PMIDs).
Syntax
DOI Example – [cite source=’doi’]10.1021/jf904082b[/cite]
PMID example – [cite source=’pubmed’]17237047[/cite]
Whichever ‘source’ is identified as the default (see Installation), will work without the source attribute being set in the shortcode. so:
[cite]10.1021/jf904082b[/cite]
Will be interpreted correctly as long as DOI is set as the default metadata source.
Example
(Paragraph taken from (http://www.ncbi.nlm.nih.gov/pubmed/20375448)).
There is recognition in the pharmaceutical industry that the current paradigm of research and development needs to change. Drugs based on novel chemistry still take 10-15 years to reach the market, and development costs are usually between $500 million and $2 billion (http://dx.doi.org/10.1016/S0167-6296(02)00126-1) (http://dx.doi.org/10.1377/hlthaff.25.2.420). Most novel drug candidates fail in or before the clinic, and the costs of these failures must be borne for the companies concerned by those drug candidates that do reach the market. These costs make it difficult even for large pharmaceutical companies to bring truly new drugs to market, and are completely prohibitive for publicly-funded researchers. An alternative means of discovering new treatments is to find new uses for existing drugs or for drug candidates for which there is substantial safety data. This repositioning approach bypasses the need for many of the pre-approval tests required of completely new therapeutic compounds, since the agent has already been documented as safe for its original purpose (http://dx.doi.org/10.1038/nrd1468).
Bibliography
Fuzzier Logic » Blog Archive » KCite – easy citations in Wordpress
January 18, 2011 @ 10:22 pm
[...] using Google Docs, we shouldn’t put unnecessary obstacles in their path, and so on. So the tool that we have produced, called KCite, uses simple text-based tags to process citations. These tags [...]
Fuzzier Logic » Blog Archive » The Problem with DOIs
February 8, 2011 @ 4:41 pm
[...] also created a referencing system for WordPress. This does DOI lookups for the user, currently using CrossRef, or PubMed. We [...]
Michael Bell » Blog and Website Updates
February 28, 2011 @ 4:40 pm
[...] also updating, I installed some new plug-ins, one of which is KCite (See KnowledgeBlog for more info). It allows me to cite papers in my blog, simply by stating their DOI in between cite [...]
Fuzzier Logic » Blog Archive » Automatic citation processing with Zotero and KCite
April 13, 2011 @ 9:47 am
[...] can download it from the Knowledgeblog Google Code site) that formats a citation in such a way that KCite, Knowledgeblog’s citation engine, can understand it. Now, when I insert citations into my [...]
danny
April 18, 2011 @ 11:34 pm
I’m using WordPress 3.1.1 and Kcite 1.3. When I first added the citations to my first blog post, the pubmed references worked but the DOI references were only able to link to the journal articles and not access the metadata (presumably because I hadn’t entered a email adress that was regestered with CrossRef).
I added my email address (which IS registered with CrossRef), but now Kcite doesn’t work at all. When I bring up my blog, I get the following error message at the top of the entry:
Warning: Invalid argument supplied for foreach() in /home/unchemyst/unchemyst.org/wp-content/plugins/kcite/kcite.php on line 181
Also, I can’t undo my addition of a registered email address.
Yikes!
admin
April 19, 2011 @ 2:09 pm
I’m sorry it’s not working for you. From looking at the error message, I would say, that kcite is having trouble retrieving the metadata for the articles, and so can’t generate the bibliography. The crash is a little unfortunate under these circumstances. With kcite, we’re following a fast “release early and often” approach; generally this is good, but bugs are somewhat inevitable.
I’d love to give more specific advice, but it’s very hard to debug at a distance. Would you be able to send an email to knowledgeblog-discuss@knowledgeblog.org with a bit more information. Particularly useful would be a URL to the broken blog (if it’s accessible and you haven’t taken the post down). Also, the full contents of the post (everything from the edit dialog of wordpress). It’s possible that this problem is being triggered by a specific DOI or PMID.
There should be a new release of kcite within the next week, with additional functionality. I’m hoping we can move toward a plugin which is stable enough for general use as soon as possible.
Thanks for the feedback.
Phil
WordPress | Digital Monograph Technical Landscape study #jiscPUB
May 10, 2011 @ 8:42 am
[...] are similar issues/risks with stuff like WordPress shortcodes such as KCite from KnowledgeBlogs. It’s a great tool for authors, allowing them to cite things in a [...]
WordPress [and the jiscPUB project] | ptsefton
May 11, 2011 @ 12:22 am
[...] [...]
The Ontogenesis Knowledgeblog: Lightweight Semantic Publishing | Knowledge Blog
June 7, 2011 @ 2:21 pm
[...] http://knowledgeblog.org/kcite-plugin [...]