5.2. Databases accessed using HITS

Although the Gale group makes many of its databases available by Z39.50 (Business and Company Resource Center, Health Reference Center Academic, etc.), four of its databases that are required for the LOT are not available in this way.

These databases are available by means of a proprietary protocol that works by sending rigorously specified HTTP GET requests, receiving XML documents, and parsing them to discover the result of the request. The protocol is called HITS (HTML InfoTrac Server, a singularly inappropriate name since HTML is not involved at all.) Detailed documentation of the HITS protocol may be obtained from Gale technical support.

Support for this protocol in the LOT was added in two stages.

The great bulk of the code for the Z39.50-to-HITS gateway is contained in the HITS and SimpleServer modules (and the modules that they, in turn, use). This means that the zHITSgate script itself is quite manageable - it's about 340 lines of Perl, including comments. Apart from translating Z39.50 queries to HITS queries, and enhancing HITS XML records with Dublin Core elements that the LOT software knows about, its main job is to provide configuration information specifying what databases to support, what access points they know about, what DC elements are included in their records, etc.

This means that, in order to add support for additional HITS databases (or change the details for those already supported), the zHITSgate script itself is the only file that needs to be edited. The underlying HITS and SimpleServer modules do not need to be changed.

When connecting to zHITSgate, a Z39.50 client should provide authentication - a username and password - to be passed through to the HITS server. If this is omitted, the Z39.50 Init request will be refused. It is a matter of policy what authentication information is used: a TexShare-global username/password pair might be used by all LOT access, or a library-specific username/password pair depending on which local library the user specifies. The gateway doesn't care - it just passes through whatever authentication information it is given.

The current version of zHITSgate supports the databases described in the following sections:

5.2.1. Biography & Genealogy Master Index

Vendor: Gale

Z39.50 database name: BGMI

This is not a bibliographic database, but a database of people. Accordingly, a title-search actually searches for people's names, since the names are ``titles'' of the records.

Table 5-2. BGMI: access points supported

Access PointMeaningNotes
1003authorSearches last name only
1016KeywordFull-text search
1032Doc-idAs returned as Dublin Core identifier

Table 5-3. BGMI: Dublin Core fields returned in brief/full records

DC FieldMeaningBriefFullExample
dateBirth/death datesYY1937-
typeDocument type YIndex Record
titleName reversedY Fruit, Melvyn Herschel
titleName YMelvyn Herschel Fruit
identifierRecord number YDO1900123100
sourceSource YBiography and Genealogy Master Index.

5.2.2. Student Resource Center GOLD

Vendor: Gale

Z39.50 database name: SRCG/SRC1

It appears experimentally that this database's full records contain two fewer Dublin Core elements than its brief records! (The full record also contains full text in most cases, or at least a long summary, but that information cannot be represented using Dublin Core fields.)

Table 5-4. SRCG: access points supported

Access PointMeaningNotes
1003author 
21subject 
1016keywordUsing this access point seems to be the same as not providing an explicit access point at all.
1032Doc-idAs returned as Dublin Core identifier

Table 5-5. SRCG: Dublin Core fields returned in brief/full records

DC FieldMeaningBriefFullExample
descriptionAnnotationY (Metro)
rightsOnline rightsY -- Text Available --
sourceJournal NameYYThe Plain Dealer (Cleveland, OH)
datePublication info.YYDec 3, 2003 pB3
identifierRecord numberYYCJ94846107
titleTitle YProposed recreation cuts, fee hikes draw complaints.
authorAuthorYYSusan Morrison

5.2.3. Texas Almanac

Vendor: Gale

Z39.50 database name: GTXS

Table 5-6. GTXS: access points supported

Access PointMeaningNotes
1016keywordThe Gale documentation says this works, but I can't get it to find any records. Better omit the access-point specification and use the default keyword search.
1032Doc-idAs returned as Dublin Core identifier

Table 5-7. GTXS: Dublin Core fields returned in brief/full records

DC FieldMeaningBriefFullExample
typeDocument typeYYTable
identifierRecord numberYYCG2199000423
sourceSource citation Y<I>Texas Almanac, 2002-2003</I>. Dallas Morning News, 2001.
titleLink textY Texas Cattle Marketed, 1965-1999 by Size of Feedlot
titleDocument title Y(as above)

5.2.4. What Do I Read Next?

Vendor: Gale

Z39.50 database name: WDRN

This database is actually a union catalogue of lots of different kinds of records, including things like lists of award winners as well as actual books. Accordingly, although there are a lot of fields that can appear, no single record seems to have anywhere near all of them.

Table 5-8. WDRN: access points supported

Access PointMeaningNotes
4titleRequires full title, not just a word from the title
1003authorRequires full name, not just surname or forename
21subjectMay require full title
1032Doc-idAs returned as Dublin Core identifier

Table 5-9. WDRN: Dublin Core fields returned in brief/full records

DC FieldMeaningBriefFullExample
formatBook format Y 
subjectSubjects YPoetry
typeDocument typeYYAwards List
contributorEditor name Y 
descriptionGenre YInspirational - Westerns
authorName reversedY Moore, John L.
authorName YJohn L. Moore
datePublication date Y1995 - 2001
identifierRecord numberYYM1300000070
sourceSource citation YWhat Do I Read Next? Farmington Hills, Mich.: Gale Group.
relationSimilar titles Y 
titleLink textY National Poetry Series Competition
titleTitle Y(as above)