Sonny Software

I had initially wanted to have a way of integrating citeulike and bookends automatically (RSS sync for example). But actually now I'm very happy with how using the bookends browser you can easily do selective imports, and know what you previously imported (yellow highlight). This all works really well, so I really just wanted to feed back a thank you Jon for such excellent features!!!

Thank you, I appreciate it.

Jon
Sonny Software

I do have one request, when you check if a reference was previously imported you don't seem to use DOI as a potential key to check. I have this reference which even after adding to my library is not "yellow-highlighted" as already in my library when reimporting it:

http://www.citeulike.org/user/iandol/article/13692614

It has no PMID, ISSN or URL, but idoes have a DOI. Would this be possible to match against?

Bookends does use DOIs for this purpose. I'll take a look.

Jon
Sonny Software

I see that this reference has both a DOI and a PMID, which is confusing Bookends. I've fixed this in the next update, and now after importing this reference it will appear in yellow if you go to it again.

Jon
Sonny Software

OK, it would be good if it could import the PMID # as currently only the DOI was imported (my PMID and PMCID fields are blank). Thanks for your super quick fix!

Please download 12.5.8 again. I made a silent update that has that fix in it.

Jon
Sonny Software

And can confirm this is now fixed, thanks Jon!

Jon, I have a new question, currently abstracts and keywords are not imported from citeulike, but they are present in the citeulike articles. As an example:

http://www.citeulike.org/user/iandol/article/13746415

BE imports this without the abstract or keywords. However you can easily get the RIS or Bibtex using dedicated URLs easy to retrieve by prepending endnote or bibtex:

http://www.citeulike.org/endnote/user/i ... e/13746415
http://www.citeulike.org/bibtex/user/ia ... e/13746415

For the general library page http://www.citeulike.org/user/iandol you can still generate those export URLs from the cite numbers. Could Bookends use these URLs for import instead of whatever method you currently use (are you scraping the HTML?)

Bookends imports the COinS embedded in the CiteULike web page. It apparently doesn't contain that information. I can take a closer look and see if the import can be improved.

Jon
Sonny Software

That's actually rather involved -- the data from CrossRef via the DOI, for example, also lacks the abstract and keywords. I'll keep it in mind, though, and think of how it might be approached.

Jon
Sonny Software

Yes, unfortunately it seems you need to use the custom URL schemes or do some fragile scraping of the page to get that info. The abstract is embedded in the <meta name="description> and within <div id="abstract-body"> but then you'd need a custom processor for Citeulike, or some way to use the /endnote/ or /bibtex/ URL schemes which again would be specific to citeulike.

Thanks for taking a look, is there a reason you can't embed abstract and keywords in the COinS <span>? I can suggest this to citeulike if this is possible, but I don't know what COinS is supposed to support...

CiteULike would have to do the embedding. I've dealt with them in the past, and they were responsive. However, I don't see an option in COinS for abstract or keyword. Here are the specifications

http://ocoins.info/cobg.html

Jon
Sonny Software

Yes, the parent OpenURL spec also only has one additional point to use a private data field, on p.44 (14.3Private Data Descriptors) of this doc:

http://www.niso.org/apps/group_public/d ... _r2010.pdf

A Private Data Descriptor specifies information about the Entity using a method not defined in this
Standard. This Standard does not provide any global mechanisms to interpret Private Data. Instead, it
is assumed that the Resolver and the Referrer have a common understanding, based on a tacit or
explicit bilateral agreement. To make it possible for the Resolver to interpret Private Data, a
ContextObject that contains a Private Data Descriptor must identify the Referrer that created it.

Example: but it would require collaboration across referrers and resolvers of COiNs fragments and I imagine may confuse (introduce bugs) resolvers that didn't expect that fragment.

Suppose I'll just have to get used to doing this manually!