About Umlaut - Revision history

Jrochkind at 00:30, 9 October 2014

2014-10-09T00:30:40Z

Jrochkind at 16:17, 19 June 2012

2012-06-19T16:17:34Z

Jrochkind at 16:17, 19 June 2012

2012-06-19T16:17:14Z

Jrochkind at 16:17, 19 June 2012

2012-06-19T16:17:01Z

Jrochkind at 16:16, 19 June 2012

2012-06-19T16:16:41Z

Jrochkind at 16:16, 19 June 2012

2012-06-19T16:16:13Z

Jrochkind at 16:16, 19 June 2012

2012-06-19T16:16:00Z

Jrochkind at 16:15, 19 June 2012

2012-06-19T16:15:29Z

Tdowling149 at 12:11, 6 July 2009

2009-07-06T12:11:16Z

Edward Vielmetti: more internal links, categories; hard to find all this stuff

2009-02-25T16:02:45Z

more internal links, categories; hard to find all this stuff

@@ Line 1: / Line 1: @@
 =WARNING: This is Outdated Documentation!!!!=
-'''THIS IS OUTDATED DOCUMENTATION''' See new Umlaut documentation at http://github.com/team-umlaut/umlaut/wiki
+'''THIS IS OUTDATED DOCUMENTATION''' See new Umlaut documentation at http://github.com/team-umlaut/umlaut
 ---------

← Older revision		Revision as of 16:17, 19 June 2012
Line 1:		Line 1:
−	=Outdated Documentation!!!!=	+	=WARNING: This is Outdated Documentation!!!!=

	'''THIS IS OUTDATED DOCUMENTATION''' See new Umlaut documentation at http://github.com/team-umlaut/umlaut/wiki		'''THIS IS OUTDATED DOCUMENTATION''' See new Umlaut documentation at http://github.com/team-umlaut/umlaut/wiki

← Older revision		Revision as of 16:17, 19 June 2012
Line 1:		Line 1:
−	= Outdated Documentation!!!!	+	=Outdated Documentation!!!!=

	'''THIS IS OUTDATED DOCUMENTATION''' See new Umlaut documentation at http://github.com/team-umlaut/umlaut/wiki		'''THIS IS OUTDATED DOCUMENTATION''' See new Umlaut documentation at http://github.com/team-umlaut/umlaut/wiki

← Older revision		Revision as of 16:17, 19 June 2012
Line 1:		Line 1:
		+	= Outdated Documentation!!!!
		+
	'''THIS IS OUTDATED DOCUMENTATION''' See new Umlaut documentation at http://github.com/team-umlaut/umlaut/wiki		'''THIS IS OUTDATED DOCUMENTATION''' See new Umlaut documentation at http://github.com/team-umlaut/umlaut/wiki
	---------		---------

@@ Line 1: / Line 1: @@
 '''THIS IS OUTDATED DOCUMENTATION''' See new Umlaut documentation at http://github.com/team-umlaut/umlaut/wiki
+---------
 [[Category:Umlaut]] __NOTOC__

← Older revision		Revision as of 16:16, 19 June 2012
Line 3:		Line 3:

	[[Category:Umlaut]] __NOTOC__		[[Category:Umlaut]] __NOTOC__
		+
	Umlaut is an open source project originally developed by [[Ross Singer]] while at Georgia Tech, and subsequently worked on quite a bit by Jonathan Rochkind of Johns Hopkins University. Umlaut is sometimes called a “link-resolver front end” or a “middle-tier link resolver”. In fact, the Umlaut is a link resolver, in the sense that it receives [[OpenURL]] requests–usually representing a citation for a scholarly work–and responds with information on services available related to that citation–most significantly, with electronic availability. However, unlike most typical link resolver products (such as [[SFX]]), the Umlaut does not manage its own “knowledge base” of information on what titles an institution possesses from what vendors, and how to link to them. Umlaut relies on SFX–accessed through the [[SFX API]]–for that information and service.		Umlaut is an open source project originally developed by [[Ross Singer]] while at Georgia Tech, and subsequently worked on quite a bit by Jonathan Rochkind of Johns Hopkins University. Umlaut is sometimes called a “link-resolver front end” or a “middle-tier link resolver”. In fact, the Umlaut is a link resolver, in the sense that it receives [[OpenURL]] requests–usually representing a citation for a scholarly work–and responds with information on services available related to that citation–most significantly, with electronic availability. However, unlike most typical link resolver products (such as [[SFX]]), the Umlaut does not manage its own “knowledge base” of information on what titles an institution possesses from what vendors, and how to link to them. Umlaut relies on SFX–accessed through the [[SFX API]]–for that information and service.

← Older revision		Revision as of 16:15, 19 June 2012
Line 1:		Line 1:
		+	THIS IS OUTDATED DOCUMENTATION See new Umlaut documentation at http://github.com/team-umlaut/umlaut/wiki
		+
		+
	[[Category:Umlaut]] __NOTOC__		[[Category:Umlaut]] __NOTOC__
	Umlaut is an open source project originally developed by [[Ross Singer]] while at Georgia Tech, and subsequently worked on quite a bit by Jonathan Rochkind of Johns Hopkins University. Umlaut is sometimes called a “link-resolver front end” or a “middle-tier link resolver”. In fact, the Umlaut is a link resolver, in the sense that it receives [[OpenURL]] requests–usually representing a citation for a scholarly work–and responds with information on services available related to that citation–most significantly, with electronic availability. However, unlike most typical link resolver products (such as [[SFX]]), the Umlaut does not manage its own “knowledge base” of information on what titles an institution possesses from what vendors, and how to link to them. Umlaut relies on SFX–accessed through the [[SFX API]]–for that information and service.		Umlaut is an open source project originally developed by [[Ross Singer]] while at Georgia Tech, and subsequently worked on quite a bit by Jonathan Rochkind of Johns Hopkins University. Umlaut is sometimes called a “link-resolver front end” or a “middle-tier link resolver”. In fact, the Umlaut is a link resolver, in the sense that it receives [[OpenURL]] requests–usually representing a citation for a scholarly work–and responds with information on services available related to that citation–most significantly, with electronic availability. However, unlike most typical link resolver products (such as [[SFX]]), the Umlaut does not manage its own “knowledge base” of information on what titles an institution possesses from what vendors, and how to link to them. Umlaut relies on SFX–accessed through the [[SFX API]]–for that information and service.

@@ Line 1: / Line 1: @@
 [[Category:Umlaut]] __NOTOC__
-Umlaut is an open source project originally developed by [[Ross Singer]] while at Georgia Tech, and subsequently worked on quite a bit by Jonathan Rochkind of Johns Hopkins University. Umlaut is sometimes called a “link-resolver front end” or a “middle-tier link resolver”. In fact, the Umlaut is a link resolver, in the sense that it receives [[OpenURL]] requests–usually representing a citation for a scholarly work–and responds with information on services available related to that citation–most significantly, with electronic availability. However, unlike most typical link resolver products (such as [[SFX]]), the Umlaut does not manage it’s own “knowledge base” of information on what titles an institution possesses from what vendors, and how to link to them. Umlaut relies on SFX–accessed through the [[SFX API]]–for that information and service.
+Umlaut is an open source project originally developed by [[Ross Singer]] while at Georgia Tech, and subsequently worked on quite a bit by Jonathan Rochkind of Johns Hopkins University. Umlaut is sometimes called a “link-resolver front end” or a “middle-tier link resolver”. In fact, the Umlaut is a link resolver, in the sense that it receives [[OpenURL]] requests–usually representing a citation for a scholarly work–and responds with information on services available related to that citation–most significantly, with electronic availability. However, unlike most typical link resolver products (such as [[SFX]]), the Umlaut does not manage its own “knowledge base” of information on what titles an institution possesses from what vendors, and how to link to them. Umlaut relies on SFX–accessed through the [[SFX API]]–for that information and service.
 ==User Interface Flexibility==

@@ Line 1: / Line 1: @@
 [[Category:Umlaut]] __NOTOC__
-Umlaut is an open source project originally developed by Ross Singer while at Georgia Tech, and subsequently worked on quite a bit by Jonathan Rochkind of Johns Hopkins University. Umlaut is sometimes called a “link-resolver front end” or a “middle-tier link resolver”. In fact, the Umlaut is a link resolver, in the sense that it receives OpenURL requests–usually representing a citation for a scholarly work–and responds with information on services available related to that citation–most significantly, with electronic availability. However, unlike most typical link resolver products (such as SFX), the Umlaut does not manage it’s own “knowledge base” of information on what titles an institution possesses from what vendors, and how to link to them. Umlaut relies on SFX–accessed through the SFX API–for that information and service.
+Umlaut is an open source project originally developed by [[Ross Singer]] while at Georgia Tech, and subsequently worked on quite a bit by Jonathan Rochkind of Johns Hopkins University. Umlaut is sometimes called a “link-resolver front end” or a “middle-tier link resolver”. In fact, the Umlaut is a link resolver, in the sense that it receives [[OpenURL]] requests–usually representing a citation for a scholarly work–and responds with information on services available related to that citation–most significantly, with electronic availability. However, unlike most typical link resolver products (such as [[SFX]]), the Umlaut does not manage it’s own “knowledge base” of information on what titles an institution possesses from what vendors, and how to link to them. Umlaut relies on SFX–accessed through the [[SFX API]]–for that information and service.
 ==User Interface Flexibility==
@@ Line 12: / Line 12: @@
 ==Check for Public Access Versions==
-To discover if an open access version of an item is available, Umlaut does an author/title keyword search of IndexData’s indexes of OAISter and Open Content Alliance freely available text.. This is imperfect because all we can do is an author title keyword search. But when it works, it’s cool.
+To discover if an open access version of an item is available, Umlaut does an author/title keyword search of IndexData’s indexes of [[OAISter]] and [[Open Content Alliance]] freely available text.. This is imperfect because all we can do is an author title keyword search. But when it works, it’s cool.
 ==OPAC Integration==
@@ Line 25: / Line 25: @@
 * Google Books search to complement the OCA and Gutenberg searches I’ve got.
 * Connection to OCLC Identities
-* 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?
+* [[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?
 * Integrate my various local document delivery services into menu of options when full text isn’t available.
@@ Line 33: / Line 33: @@
 For those looking for technical details to give our Umlaut the run-through, the base url is:
   http://findit.library.jhu.edu/resolve