Umlaut wishlist

From Code4Lib
Revision as of 16:38, 21 October 2010 by (Talk)

Jump to: navigation, search

Some actual current future plans:

  • Fix HathiTrust adapter to use new HT plugin, including not showing fulltext for just portions of a serial. (Or showing it in 'see also' section only)
  • Rails3
  • 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.
  • 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 Technolgoy Reports article has some ideas, I think.

old Desired or planned features.

  • Full-text availability check from -- 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.
  • Journal ToC from CiteULike
  • 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.
    Unofficially it will return json:

  • Rochester “Getting Users Fulltext” style code to skip right to the full text, skipping content-provider metadata pages.

  • UMich Mirlyn for metadata enrichment?

  • xISBN/thingISBN use. (Some thought is required in how to integrate this while avoiding false positives). Bowker ISSN service for metadata enhancement. OCLC xISSN? Integrate preceding/succeeding title information from OPAC or xISSN?
  • LibraryLookup: At least until xISBN is baked in we could provide a link to this service. Increases the chances of finding a desired book in the catalog through work set grouping. Used by LibX.
  • Journal covers from Ulrich's via screen-scraping (or Ulrich's/sersol built in api?)

  • Connotea integration

  • Fetch ToC from LC. Screen scrape, I guess? Or z3950? Any other content from LC?

  • Link to Books In Print ala Notre Dame. example

  • bip search url? :

  • SFX plugin: Notice when first title given is non-roman, and look for roman title to enhance metadata with when so.

  • HIP and other OPAC searchers should pull ToC from MARC 505 when present. And 856's judged to be ToC in ToC, not full text.

  • Fix Umlaut Referent to more easily allow multiple authors. Architectural change neccessary to get a lot of this stuff working right.

  • Enhance metadata to have full metadata for a refworks etc export. Using: CrossRef? Metalib? Anything else?

  • A general purpose responsecache. Schema: Date, service/source, key. Use for caching image urls, ToC urls from LC, etc.

  • Fix Worldcat registry auto-discovery.

  • Add a Worldcat search that uses API, instead of screen scrape.

  • Switch OCA search to use OCA native APIs, instead of indexdata mirror index.

  • fix unapi in umlaut. unapi to rsi? For zotero.

  • Change background to use Spawn plugin instead of manual threading. Investigating using spawn with fork instead of thread (terry reese on limited pool of forks).

  • Crazy idea for an abstract interface/architecture to support querying web service apis that require client side javascript, like Google Books and Scopus.

  • Integrate my various local document delivery services into menu of options when full text isn’t available. More generally, a clear architecture for providing localized doc delivery services in addition to a single ILL link.

  • SFX adaptor: Add a "rollup" feature that pays attention to dates to avoid eliminating coverage.