I updated ResolveRef last night and checked in the most current sourcecode to svn at Google Code.
New features include:
- Suggest/autocomplete for journal title field, using the journal title lists provided by PubMed.
- A “Verify” button. Allows a ResolveRef URL to be constructed with the web form and verified as working and valid without actually forwarding the user to the article.
- Some bugfixes (handled the case where there is no DOI in the PubMed record, handled network timeouts to PubMed)
- Refreshed visuals
- Disqus comments box for feedback
In the interest of just getting something working quickly, I implemented the suggest feature in the laziest, possibly most RAM and CPU hungry way possible (the “JQuery Suggest” code queries the web app with substrings as you type each character. At the server side, the app uses a regex to scan a ~1.5 Mb list of journal titles held in RAM). I’ve already noticed a few “This request used a high amount of CPU” warnings in the logs, with the threat “High CPU requests have a small quota, and if you exceed this quota, your app will be temporarily disabled“. If my nasty hack starts heating up Google’s datacentre too much, I might have to disable the ‘suggest’ feature until I can implement it “properly”.