<?xml version='1.0' encoding='utf-8' ?>
<!--  If you are running a bot please visit this policy page outlining rules you must respect. http://www.livejournal.com/bots/  -->
<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:media='http://search.yahoo.com/mrss/'>
<channel>
  <title>CiteULike</title>
  <link>http://citeulike.livejournal.com/</link>
  <description>CiteULike - LiveJournal.com</description>
  <lastBuildDate>Wed, 29 Jun 2005 13:26:37 GMT</lastBuildDate>
  <generator>LiveJournal / LiveJournal.com</generator>
  <lj:journal>citeulike</lj:journal>
  <lj:journalid>5111123</lj:journalid>
  <lj:journaltype>personal</lj:journaltype>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/12631.html</guid>
  <pubDate>Wed, 29 Jun 2005 13:26:37 GMT</pubDate>
  <title>British Medical Journal (BMJ)</title>
  <link>http://citeulike.livejournal.com/12631.html</link>
  <description>You can now post articles directly from the &lt;a href=&quot;http://bmj.bmjjournals.com/&quot;&gt;British Medical Journal&lt;/a&gt; to CiteULike. Many thanks to Will Wade for writing this plugin using the &lt;a href=&quot;http://www.livejournal.com/users/citeulike/11953.html&quot;&gt;developer&apos;s kit&lt;/a&gt;. I wonder if whoever eventually works out a cure for cancer will be a CiteULike user. That would be - as my American friends say - &quot;neat&quot;.</description>
  <comments>http://citeulike.livejournal.com/12631.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>3</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/12488.html</guid>
  <pubDate>Mon, 27 Jun 2005 21:58:54 GMT</pubDate>
  <title>Anthrosource</title>
  <link>http://citeulike.livejournal.com/12488.html</link>
  <description>You can now post anthropology articles from &lt;a href=&quot;http://www.anthrosource.net&quot;&gt;anthrosource&lt;/a&gt; to CiteULike using the bookmarklet. This is another user submitted plugin using the plugin development kit. It turned out that two people were independently working on an anthrosource plugin, but Christopher Kelty got there first. I never knew there were so many anthropologists in the world...&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update:&lt;/b&gt; It seems there are, indeed, plenty of anthropologists in the world, and they&apos;ve written an &lt;a href=&quot;http://savageminds.org/2005/06/27/tutorial-how-to-use-citeulike-with-anthrosource/&quot;&gt;exceptionally comprehensive introduction&lt;a&gt; to using CiteULike with Anthrosource. It probably works just as well if you want to use CiteULike with any other source of articles (particle physics, for example), and I&apos;m actually embarrassed that they&apos;ve written a better tutorial than I have on the site itself...&lt;/a&gt;&lt;/a&gt;</description>
  <comments>http://citeulike.livejournal.com/12488.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/12161.html</guid>
  <pubDate>Sat, 25 Jun 2005 01:07:27 GMT</pubDate>
  <title>Smithsonian/NASA ADS Astronomy/Planetary Abstract Service</title>
  <link>http://citeulike.livejournal.com/12161.html</link>
  <description>The CiteULike bookmarklet now works with the &lt;a href=&quot;http://adsabs.harvard.edu/&quot;&gt;Smithsonian/NASA ADS Astronomy/Planetary Abstract Service&lt;/a&gt;.</description>
  <comments>http://citeulike.livejournal.com/12161.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/11953.html</guid>
  <pubDate>Fri, 24 Jun 2005 19:02:52 GMT</pubDate>
  <title>API for developing plugins released</title>
  <link>http://citeulike.livejournal.com/11953.html</link>
  <description>I&apos;ve released an open source version of CiteULike&apos;s plugin interface (the code which scrapes citation details from external sites) under the BSD license. It&apos;s available to browse here:&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://svn.citeulike.org/svn/plugins/&quot;&gt;http://svn.citeulike.org/svn/plugins/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;and the HOWTO which provides the documentation as it stands at the moment is here:&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://svn.citeulike.org/svn/plugins/HOWTO.txt&quot;&gt;http://svn.citeulike.org/svn/plugins/HOWTO.txt&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;If you want to pull the source code down and start hacking it, you can get it using subversion (&lt;a href=&quot;http://subversion.tigris.org/&quot;&gt;http://subversion.tigris.org/&lt;/a&gt;) by typing:&lt;br /&gt;&lt;pre&gt;svn co http://svn.citeulike.org/svn/ citeulike&lt;/pre&gt;&lt;br /&gt;The relevant features are:&lt;ul&gt;&lt;li&gt; Language neutral. You can write plugins in whatever programming language you like (assuming it can run on my server).&lt;br /&gt;    &lt;li&gt; Sample code. I&apos;ve tidied up a few of the existing plugins and released them as part of the new system. Ultimately I&apos;ll convert them all, but it&apos;s now at a state where it makes sense to release it and get everyone hacking on it.&lt;br /&gt;    &lt;li&gt; Proper documentation. It walks you through all the steps required to produce a new plugin.&lt;br /&gt;    &lt;li&gt; Test suite. You can (and should) write test cases for your scraper, and we&apos;ll know when the site changes its format and breaks the scraper (such is the nature of writing these things).&lt;br /&gt;    &lt;li&gt; Test harness. You can actually run the tests against your code without having to guess whether they&apos;d work or not (which was the case up until now if you wanted to write a plugin).&lt;br /&gt;    &lt;li&gt; Common utility functionality (Author names, RIS, and BibTeX parsing) build into the &quot;driver&quot; part of the code, so you don&apos;t need to re-invent the wheel.&lt;br /&gt;&lt;/ul&gt;&lt;br /&gt;It&apos;s live on the server now, as is the first user submitted plugin (from Diwaker Gupta) to scrape the proceedings from the computer science journals on the &lt;a href=&quot;http://www.usenix.org&quot;&gt;USENIX site&lt;/a&gt;.</description>
  <comments>http://citeulike.livejournal.com/11953.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>6</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/11748.html</guid>
  <pubDate>Mon, 20 Jun 2005 18:13:12 GMT</pubDate>
  <title>Edit DOIs for your articles</title>
  <link>http://citeulike.livejournal.com/11748.html</link>
  <description>Another new features lets you add a DOI (&lt;a href=&quot;http://www.doi.org&quot;&gt;Document Object Identifier&lt;/a&gt;) to your article on CiteULike if it doesn&apos;t have one and you know what it should be. Just click down to the view article page, and hit the &quot;Edit links and DOIs...&quot; button. You&apos;ll obviously need to be logged in, and you&apos;ll need to have the article in your collection.&lt;br /&gt;&lt;br /&gt;Apparently some journal styles actually &lt;b&gt;require&lt;/b&gt; you to produce bibliographies with DOIs, so this should help if you publish in one of those.</description>
  <comments>http://citeulike.livejournal.com/11748.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/11404.html</guid>
  <pubDate>Sun, 19 Jun 2005 16:45:59 GMT</pubDate>
  <title>MathSciNet Parser</title>
  <link>http://citeulike.livejournal.com/11404.html</link>
  <description>I&apos;ve added experimental support for &lt;a href=&quot;http://www.ams.org/mathscinet&quot;&gt;MathSciNet&lt;/a&gt;. You should be able to use the &quot;Post to CiteULike&quot; bookmarklet to automatically add articles from MathSciNet to your library without all that tedious mucking about copying and pasting details.&lt;br /&gt;&lt;br /&gt;By &lt;i&gt;experimental&lt;/i&gt;, I mean that it seems to work, but I&apos;d be interested to hear from you at &lt;a href=&quot;mailto:bugs@citeulike.org&quot;&gt;bugs@citeulike.org&lt;/a&gt; if it&apos;s not behaving. To be trendy, I should probably call it &lt;i&gt;Beta&lt;/i&gt; or something like that. Google seem to have recently redefined that word to mean just &quot;new feature&quot;.</description>
  <comments>http://citeulike.livejournal.com/11404.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/11176.html</guid>
  <pubDate>Sun, 19 Jun 2005 10:19:30 GMT</pubDate>
  <title>Find your Personal PDFs more easily</title>
  <link>http://citeulike.livejournal.com/11176.html</link>
  <description>I&apos;m now back from holiday. After a grand total of sixty seven hours sitting in railway carriages in Western Russia, I&apos;m now surprisingly keen to get back to work.&lt;br /&gt;&lt;br /&gt;The first minor update follows on from the &lt;a href=&quot;http://www.livejournal.com/~citeulike/10614.html&quot;&gt;Personal PDF announcement&lt;/a&gt;. When you upload your own copy of the PDF file, you&apos;ll be able to see a small icon in the list view to let you tell at a glance which files you&apos;ve already uploaded and which ones you haven&apos;t. Previously, you had to go down to the &quot;view article&quot; page, which was a real pain.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update:&lt;/b&gt; The same now applies to articles with notes. If an article has public notes attached to it (or it&apos;s your own article with private notes and you&apos;re logged in) then you&apos;ll get a handy icon in the list view too. It looks ugly as anything, but it&apos;s quite useful.</description>
  <comments>http://citeulike.livejournal.com/11176.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>2</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/11005.html</guid>
  <pubDate>Fri, 27 May 2005 17:01:23 GMT</pubDate>
  <title>Japanese CiteULike</title>
  <link>http://citeulike.livejournal.com/11005.html</link>
  <description>My thanks to Marica Odagaki for producing a &lt;a href=&quot;http://jp.citeulike.org&quot;&gt;Japanese translation of CiteULike.&lt;/a&gt; I&apos;m always amazed by how much effort goes into translating an entire web site and how people like Marcia kindly volunteer to help out. Hopefully this will help with all the Japanese users currently use Google Translate to access CiteULike. I&apos;ve no idea how well it translates into Japanese, but it has certainly produced some fairly interesting Japanese-&amp;gt;English ones when I&apos;ve used it.</description>
  <comments>http://citeulike.livejournal.com/11005.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/10614.html</guid>
  <pubDate>Mon, 25 Apr 2005 07:59:24 GMT</pubDate>
  <title>Personal PDFs</title>
  <link>http://citeulike.livejournal.com/10614.html</link>
  <description>Do you keep copies of the PDFs of some of your articles on your hard drive? Can you never find the right one when you want to? Or, do you keep these files on a machine at work and sometimes want access to them at home?&lt;br /&gt;&lt;br /&gt;Now you can keep a personal copy of the PDF on the CiteULike server. When you&apos;re logged in, just navigate down to any article with your web browser and you&apos;ll get the option to upload the PDF from your hard drive. After that, you&apos;ll have access to the content wherever you can log in to CiteULike.&lt;br /&gt;&lt;br /&gt;There are obviously some restrictions to comply with copyright law. In order to prove that you have access rights to the content, you must be able to upload the PDF file directly into your account. That&apos;s to say, you must prove that you had a copy of the article in the first place - CiteULike will not be able to get hold if it in any other way.&lt;br /&gt;&lt;br /&gt;Secondly, rather obviously, you must be logged in to your CiteULike account to download the article again when you, say, want to read it at home. That&apos;s the &quot;personal&quot; aspect. Think of this service as (a more organised and convenient) extension of your local hard drive. You can keep your content on it, but you can&apos;t use it to share that content with anyone else.&lt;br /&gt;&lt;br /&gt;All data is backed up to a remote site and, in the initial testing phase, there are no usage quotas. I&apos;ll clearly need to impose some sort of limit at some point, but I&apos;ve got plenty of disk space and I want to get an idea of popularity so I can work out where I should peg the limit.&lt;br /&gt;&lt;br /&gt;Coming next (once I&apos;m happy I&apos;ve set the usage limits correctly) is the ability to do a full text search on all the PDFs in your collection. This will hopefully solve the &quot;where did I read that?&quot; problem - all you&apos;ll need to do is ask CiteULike to search through all the papers you&apos;ve ever read and tell you exactly where you read it.</description>
  <comments>http://citeulike.livejournal.com/10614.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>16</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/10265.html</guid>
  <pubDate>Mon, 21 Mar 2005 13:27:08 GMT</pubDate>
  <title>Optimisations</title>
  <link>http://citeulike.livejournal.com/10265.html</link>
  <description>I&apos;ve rewritten a substantial chunk of what goes on behind the scenes on the server. You shouldn&apos;t notice any difference except from:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;The &quot;delete article&quot; button has moved from the list page to the article page itself.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;If two people post the same article in rapid succession, you only see the latter as opposed to filling the page up with multiple instances of it.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;and..&lt;br /&gt;&lt;ul&gt;&lt;li&gt;page generation is 10 times faster than before (for some of the more commonly viewed pages).&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;The chances of this all working entirely smoothly are pretty slim, so please let me know if you notice anything untoward happening on the site.&lt;br /&gt;&lt;br /&gt;The geeky explanation of what I&apos;ve done is as follows:&lt;br /&gt;&lt;br /&gt;I replaced a simple shared-memory hashtable with &lt;a href=&quot;http://www.danga.com/memcached/&quot;&gt;memcached&lt;/a&gt; together with &lt;a href=&quot;http://www.citeulike.org/opensource/memcached.adp&quot;&gt;some modifications to handle dependencies in data &lt;/a&gt; as well as a &lt;a href=&quot;http://www.citeulike.org/opensource/memcached.adp&quot;&gt;custom Tcl client API&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;The advantage of this is that I can pre-cache the HTML rendering of each article in the list (hence I moved the &quot;delete&quot; button so the HTML doesn&apos;t depend on whether you&apos;re logged in or not), and use memcached&apos;s method for fetching multiple objects in one request to simply suck down all the HTML fragments and then simply play them out to the webserver. Not only is this approximately 10 times faster than what I had before (a typical page with all the articles in the cache renders in 12ms), but most of the remaining time is taken up just waiting for the data to appear over the network - and this consumes next to no CPU at all. That means I&apos;ve managed to get at least an extra factor of ten capacity out of the existing hardware (and there are probably still some more optimisations I can do if I need to), and I can now use multiple instances of memcached to effectively scale up capacity by adding more hardware when required.&lt;br /&gt;&lt;br /&gt;So, I&apos;m now in a pretty good position to cope with growth of number of users (which is exponential), and I can now get back to spending more time adding features (like finally writing that API) than worrying about this stuff. The only thing I still need to do, of course, is fix all the bugs which I&apos;ve just introduced - please do let me know if you notice anything broken.</description>
  <comments>http://citeulike.livejournal.com/10265.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>9</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/10071.html</guid>
  <pubDate>Tue, 01 Mar 2005 00:21:28 GMT</pubDate>
  <title>Import your existing BibTeX file into CiteULike</title>
  <link>http://citeulike.livejournal.com/10071.html</link>
  <description>Do you want to start using CiteULike but you&apos;ve already spent ages making a BibTeX file packed with every article you&apos;ve ever read? Fear not, you can now &lt;a href=&quot;http://www.citeulike.org/import_bibtex&quot;&gt;import it into CiteULike&lt;/a&gt;.</description>
  <comments>http://citeulike.livejournal.com/10071.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>15</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/9792.html</guid>
  <pubDate>Sun, 27 Feb 2005 00:21:21 GMT</pubDate>
  <title>Amazon books</title>
  <link>http://citeulike.livejournal.com/9792.html</link>
  <description>I&apos;ve added an Amazon plugin so you should be able to post books from their web site using the normal bookmarklet. You can&apos;t post any of the other things they sell (like microwave ovens, for example) as that would be extremely confusing.</description>
  <comments>http://citeulike.livejournal.com/9792.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/9661.html</guid>
  <pubDate>Tue, 15 Feb 2005 10:00:56 GMT</pubDate>
  <title>Roundup of two minor new features...</title>
  <link>http://citeulike.livejournal.com/9661.html</link>
  <description>&lt;ul&gt;&lt;br /&gt;&lt;li&gt;&lt;b&gt;For the librarians:&lt;/b&gt; Install one of Dan Chudnov&apos;s magic &lt;a href=&quot;http://curtis.med.yale.edu/dchud/resolvable/&quot;&gt;dynamic appropriate resolver bookmarklets&lt;/a&gt; and click it when you&apos;re looking at an article on CiteULike. Dan&apos;s trying to push the ideas behind this as a standard for embedding this sort of information in web pages, and I&apos;m all in favour of that.&lt;/li&gt;&lt;br /&gt;&lt;br /&gt;&lt;li&gt;&lt;b&gt;For the fastidious:&lt;/b&gt; You&apos;ve now got much more control over how you can edit the detail of your articles once they&apos;re in your library. Clicking the &quot;Edit details...&quot; button on the article page should let you do things that you previously couldn&apos;t do (like changing the article type, and adding abstracts), while clicking the &quot;Edit links...&quot; button will let you associate another URL with the article. This is handy if you eventually find a PDF of it online.&lt;/li&gt;&lt;br /&gt;&lt;/ul&gt;</description>
  <comments>http://citeulike.livejournal.com/9661.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/9378.html</guid>
  <pubDate>Sat, 12 Feb 2005 15:00:07 GMT</pubDate>
  <title>New language - Italian</title>
  <link>http://citeulike.livejournal.com/9378.html</link>
  <description>... or, at least it&apos;s new to CiteULike, even if the language itself has been about for a while (something to do with the Romans, I believe). Many thanks to &lt;a href=&quot;http://moloko.itc.it/paoloblog/&quot;&gt;Paolo Massa&lt;/a&gt; for his hard work &lt;a href=&quot;http://it.citeulike.org&quot;&gt;translating the site into Italian&lt;/a&gt;. There&apos;s barely room for the array of flags in the top right-hand corner of the page any more - I&apos;m amazed at the sheer number we&apos;ve got now. Thanks again to everyone who&apos;s contributed to all these translations.</description>
  <comments>http://citeulike.livejournal.com/9378.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/8971.html</guid>
  <pubDate>Fri, 04 Feb 2005 13:41:26 GMT</pubDate>
  <title>citeulike-discuss mailing list</title>
  <link>http://citeulike.livejournal.com/8971.html</link>
  <description>It&apos;s high time we had an email discussion list for CiteULike. I&apos;ve set one up, and you can subscribe here:&lt;br /&gt;&lt;br /&gt;&lt;a href=&quot;http://www.citeulike.org/mailman/listinfo/citeulike-discuss&quot;&gt;http://www.citeulike.org/mailman/listinfo/citeulike-discuss&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Feel free to use it for general discussion about the service, ideas for what you&apos;d like CiteULike to do, and any questions or concerns you might have. If you&apos;ve got a question about your account, or a specific bug report, that should go directly to me (Richard Cameron - camster@citeulike.org) and not to the list.</description>
  <comments>http://citeulike.livejournal.com/8971.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/8925.html</guid>
  <pubDate>Wed, 02 Feb 2005 14:20:17 GMT</pubDate>
  <title>Extremely long lists of tags - filter them!</title>
  <link>http://citeulike.livejournal.com/8925.html</link>
  <description>I&apos;ve added a little filter box to the list of tags on the right hand side of the pages. I find this quite useful to find stuff now my list of tags has grown to a horrendous length.&lt;br /&gt;&lt;br /&gt;It&apos;s a bit of a javascript hack, and it&apos;s possible that it might not behave itself on every browser, so I&apos;d be interested to hear if it doesn&apos;t work out for you (unless, of course, you&apos;re using a text browser like Lynx!).</description>
  <comments>http://citeulike.livejournal.com/8925.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>3</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/8530.html</guid>
  <pubDate>Mon, 31 Jan 2005 17:44:21 GMT</pubDate>
  <title>New plugin: Science</title>
  <link>http://citeulike.livejournal.com/8530.html</link>
  <description>&lt;a href=&quot;http://www.sciencemag.org/&quot;&gt;Science&lt;/a&gt; is now fully supported in CiteULike, which means you can add articles from it without having to type in the details.</description>
  <comments>http://citeulike.livejournal.com/8530.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/8307.html</guid>
  <pubDate>Fri, 28 Jan 2005 18:13:30 GMT</pubDate>
  <title>IEEE Xplore</title>
  <link>http://citeulike.livejournal.com/8307.html</link>
  <description>... and you can also post articles from &lt;a href=&quot;http://ieeexplore.ieee.org/&quot;&gt;IEEE Xplore&lt;/a&gt; and have the details automatically appear for you.</description>
  <comments>http://citeulike.livejournal.com/8307.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/7991.html</guid>
  <pubDate>Fri, 28 Jan 2005 16:43:58 GMT</pubDate>
  <title>Nature</title>
  <link>http://citeulike.livejournal.com/7991.html</link>
  <description>Quick update: You can now post articles directly from the nature.com website without having to type the details in manually.</description>
  <comments>http://citeulike.livejournal.com/7991.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/7823.html</guid>
  <pubDate>Tue, 18 Jan 2005 00:27:35 GMT</pubDate>
  <title>Post anything - not just from supported sites</title>
  <link>http://citeulike.livejournal.com/7823.html</link>
  <description>I&apos;ve obviously been spending too much time working on CiteULike and not enough time using it. It&apos;s only in the last few days I&apos;ve discovered just how frustrating it is to get an error message when CiteULike won&apos;t let me post a particular article because it&apos;s not from a supported site.&lt;br /&gt;&lt;br /&gt;So, I&apos;ve removed this restriction. You can now post any URL you like. The only downside is that if it&apos;s not from a site that CiteULike knows about, you&apos;ll have to type in the citation details yourself.&lt;br /&gt;&lt;br /&gt;There&apos;s a bit of history to why I decided to impose the restriction in the first place. When I wrote the site I didn&apos;t want it to become yet another social bookmarking site. I wanted it to fill a specific niche - academic articles. For it to be a useful academic resource, I reasoned, I had to make sure that users could browse about and get academic articles and not, say, details of chalets in France posted by a biochemist trying to organize his skiing holiday. That sort of thing would seriously devalue the site.&lt;br /&gt;&lt;br /&gt;Secondly, I wanted to make sure the citation details were reasonably accurate (and spam free), so I initially decided to only take this information from serious online databases (like PubMed and Sciencedirect).&lt;br /&gt;&lt;br /&gt;However, it&apos;s just far too annoying to be limited to a finite set of providers, so I had to make the change. There&apos;s still the issue of not polluting the quality of articles with arbitrary web pages though. To solve this, if you post a web page (or a PDF file, or whatever) from an unrecognized source, it will appear in you library, but not on the front page. Of course if you post the same article as others you&apos;ll still be able to see the &quot;posted by &lt;i&gt;x&lt;/i&gt; others link&quot; to find out who. This should hopefully be a reasonable compromise which will limit the damage that spammers can do to the site while allowing users the flexibility to actually store their entire bibliography online, and not just part of it.&lt;br /&gt;&lt;br /&gt;Hope this helps.</description>
  <comments>http://citeulike.livejournal.com/7823.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>14</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/7513.html</guid>
  <pubDate>Mon, 17 Jan 2005 21:21:15 GMT</pubDate>
  <title>Two small things: edit details and private notes</title>
  <link>http://citeulike.livejournal.com/7513.html</link>
  <description>Two quick updates:&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;When you post a note on an article you&apos;ve now got the option of making it private. Only you will be able to read it, and you&apos;ll only be able to read it when you&apos;re logged in. This means you can criticize your boss&apos;s work to your heart&apos;s content without him seeing it.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;You can edit the metadata (author, title, journal name, page, etc) of articles in your collection. Sometimes (especially with Citeseer) the data which gets imported is just wrong, and you need to manually fix it up. This is really handy if you then want to export your library to BibTeX or EndNote. Your changes only apply to your copy of the article, so they won&apos;t appear on the front page of CiteULike or in anyone else&apos;s library.&lt;/li&gt;&lt;br /&gt;&lt;/ul&gt;</description>
  <comments>http://citeulike.livejournal.com/7513.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/7302.html</guid>
  <pubDate>Fri, 14 Jan 2005 14:16:27 GMT</pubDate>
  <title>Watchlists, now without that really annoying &quot;feature&quot;</title>
  <link>http://citeulike.livejournal.com/7302.html</link>
  <description>I&apos;ve just made a small change to the way watchlists work. It&apos;s something which has been annoying me for ages, but I&apos;ve only just got round to fixing it. Previously, if someone posted an article which matched your watchlist criteria, then it would appear regardless of whether you already had it in your library or not. This seemed to happen quite often, and it only served to annoy me.&lt;br /&gt;&lt;br /&gt;So, from now on, you&apos;ll only see articles in your watchlist which you haven&apos;t already posted into your collection.</description>
  <comments>http://citeulike.livejournal.com/7302.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/7015.html</guid>
  <pubDate>Tue, 11 Jan 2005 12:41:58 GMT</pubDate>
  <title>CiteULike in Norwegian</title>
  <link>http://citeulike.livejournal.com/7015.html</link>
  <description>There&apos;s now a &lt;a href=&quot;http://no.citeulike.org/&quot;&gt;Norwegian version&lt;/a&gt; of CiteULike. We seem to have a disproportionate number of Norwegian users on the site, so hopefully this will be useful for them.&lt;br /&gt;&lt;br /&gt;My usual plug for anyone else interested in translating CiteULike (or even part of it) into their native language still stands! I&apos;d be delighted to hear from you at &lt;a href=&quot;mailto:camster@citeulike.org&quot;&gt;camster@citeulike.org&lt;/a&gt;.</description>
  <comments>http://citeulike.livejournal.com/7015.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/6890.html</guid>
  <pubDate>Sun, 09 Jan 2005 00:36:22 GMT</pubDate>
  <title>How much do you want to read this article?</title>
  <link>http://citeulike.livejournal.com/6890.html</link>
  <description>My paper-based filing system (which has now been almost completely replaced by CiteULike) was an enormous pile of papers, all wrapped up in a folder with the words &quot;to read&quot; written on it in big letters. I also had some general procedure whereby the articles that I really wanted to read got inserted somewhere near the top, and the ones I wasn&apos;t really in a hurry to get through went somewhere towards the bottom.&lt;br /&gt;&lt;br /&gt;I&apos;ve added this functionality into CiteULike, so when you post a paper you&apos;ll get asked how urgently you want to read it. Your options are:&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;Top priority!&lt;br /&gt;&lt;li&gt;I really want to read it&lt;br /&gt;&lt;li&gt;I will read it&lt;br /&gt;&lt;li&gt;I might read it&lt;br /&gt;&lt;li&gt;I don&apos;t really want to read it&lt;br /&gt;&lt;br /&gt;&lt;li&gt;I&apos;ve already read it&lt;br /&gt;&lt;/ul&gt;&lt;br /&gt;Afterwards, you&apos;ll be able to order your library in the way my paper file used to work - things which you ought to read first at the top of the list. Obviously, you can change the priority via the &quot;view article&quot; page when you&apos;re logged in too.&lt;br /&gt;&lt;br /&gt;I decided against letting users rate papers in terms of quality, and just went with recording how high up the user&apos;s personal &quot;to do&quot; list the article is. There were a few reasons for this:&lt;br /&gt;&lt;br /&gt;In my paper-based world, when I finished reading an article, took it out of the &quot;to read&quot; folder and put it into its permanent home in the filing cabinet, I&apos;d never in a million years think of scribbling a mark out of ten on it. Firstly it would sometimes be incredibly presumptuous to do so, and secondly it doesn&apos;t really achieve anything. If I realize that the article is of no interest to me and that I&apos;m never going to cite it or refer to it again, it just goes straight in the bin; otherwise I keep it. It&apos;s really just a simple yes/no choice for me.&lt;br /&gt;&lt;br /&gt;However I did find myself instinctively prioritizing all the stuff in the &quot;to read&quot; folder, and so I think that&apos;s the obvious ranking to use on CiteULike. It also avoids any potentially embarrassing situations where the author of an article (especially if he happens to be my boss) gets offended that I&apos;ve given his article a bad mark. I haven&apos;t. It&apos;s just that it&apos;s not strictly relevant to what I&apos;m reading at the moment.</description>
  <comments>http://citeulike.livejournal.com/6890.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>1</lj:reply-count>
</item>
<item>
  <guid isPermaLink='true'>http://citeulike.livejournal.com/6534.html</guid>
  <pubDate>Fri, 31 Dec 2004 21:24:08 GMT</pubDate>
  <title>CiteULike is now searchable...</title>
  <link>http://citeulike.livejournal.com/6534.html</link>
  <description>I&apos;ve added a search bar to the top of every page. Now that we&apos;ve got something like 70,000 articles online, it seemed sensible to actually be able search the whole collection.&lt;br /&gt;&lt;br /&gt;I use a fairly standard approach at the moment: stemming, stop words, and ranking search results by: a) how close together the search terms appear in the record, and b) the idea that matching an author is better than matching a title, which is in turn better than matching in an abstract, which is better than matching anything else (like a journal name or a page number).&lt;br /&gt;&lt;br /&gt;There&apos;s a lot of room for improvement here. The grand plan is to try to make the search results more relevant to you. For example if you&apos;re an astrophysicist (and have posted lots of articles on astrophysics to your library) then it&apos;s probably a safe bet that you&apos;re more interested in results from astrophysics journals than you are in sociology journals. This is very much the &lt;i&gt;grand&lt;/i&gt; plan, but I&apos;m sure we&apos;ll get there eventually.&lt;br /&gt;&lt;br /&gt;Happy new year!</description>
  <comments>http://citeulike.livejournal.com/6534.html</comments>
  <lj:security>public</lj:security>
  <lj:reply-count>0</lj:reply-count>
</item>
</channel>
</rss>
