Changes

* Parsing of formatted references from an entry screen. Use '''THIS IS OUTDATED DOCUMENTATION''' See new Umlaut documentation at http://winggithub.comp.nus.edu.sgcom/parsCitteam-umlaut/ package. Very interesting! Or a similar UCOP package: http:umlaut//purl.net/net/egh/hmmwiki--------citation-extractor/

Some actual current future plans: * JournalTOCs ToC? * Use OCLC xISBN to find HT and Internet Archive/OCA matches? * Internet Archive -- use new OL/IA api, discover search-inside-the-book.  * WorldCat, use new api, link directly to nearest public library in 'see also' or elsewhere.  * CiteSeerX -- source of 'cited by' info, AND, most excitingly, open access pre-prints. But their Atom/RSS feeds (the only API I could find) don't seem to advertise enough info to actually use these features. Would need to talk to developer team -- possibly offer to help code? Also not entirely clear how big their corpus actually is, if it's worth it.  * Try screen-scraping Google Scholar (and maybe Microsoft Academic) to get the open access full text links they find. Also, there's a Springer API for open access content now. http://dev.springer.com/docs/Restful_operations * When no full text is found, provide link to search on Google Scholar, or Bing Academic? Need to have sufficient metadata to create the search. Oct 2010 Library Technology Reports article has some ideas, I think.   '''old''' Desired or planned features.  * Check for similar articles from: http://biosemantics.org/jane/faq.php#api * Full-text availability check from http://chroniclingamerica.loc.gov/ -- check by title/city, check by lccn (?), able to check particular dates/link to particular dates and/or pages of paper? * Allow a service_response to have a tree relationship to children, so for instance alternate versions of a text can be attached as children of the main link, expandable by the user.  * http://export.arxiv.org/api_help/ !!!! * PubMed Central full text lookup http://www.ncbi.nlm.nih.gov/entrez/query/static/esearch_help.html (SFX may already do this?) * Journal ToC from CiteULike * Parsing of formatted references from an entry screen. Use http://wing.comp.nus.edu.sg/parsCit/ package. Very interesting! Or a similar UCOP package: http://purl.net/net/egh/hmm-citation-extractor/ See list of such packages here under "Other Parsing Tools" http://freecite.library.brown.edu/ * LibraryThing open knowledge API for more data. http://www.librarything.com/blog/2008/08/free-web-services-api-to-common.php * Connect to internet linked movie database on movies: http://www.linkedmdb.org/ * Add information about the conversation happening around an article with Scintilla if we have a URL, PMID or DOI(Alf at Scintilla would prefer us NOT to use the API for high-traffic. But we can copy his techniques internally to Umlaut. CrossRef and PubMed for "cited by" on DOI and PMID identifiers are a good idea. He has also reverse engineered the Scopus javascript api to allow server-side json access. http://hublog.hubmed.org/archives/001512.html):

* "Cited by" service. Scopus via screen scraping? (scopus javascript api? http://www.scopus.com/scsearchapi/ See also http://hublog.hubmed.org/archives/001512.html ) ISI Web of Science is too hard to even screen scrape the interface is such a mess, but Scopus looks do-able. Google scholar?