Z TEXAS MEETING

Thursday, February 21, 2002

9:00am - 4:00pm

San Antonio Public Library

600 Soledad

San Antonio, TX 78205

210-207-2500

Map - Public Library is #13

Parking: $3.50 per day (NO in/out privileges)

Z39.50

Home | Implementation Resources

Agenda

Attendees:

[Words in maroon indicate items that have been assigned to someone.]

Updates:
 

  • TLA half-day preconference: Z39.50: The Last Mile

    Vendors: DRA, Epixtech, Gaylord, III, SIRSI, TLC
    • Is it possible to ask the ILS vendors for lists of Z39.50 servers and connection information in Texas? Vendors don't normally keep this type of information. It needs to come from the libraries themselves.
       
    • Might be possible to provide a draft of the Functional Area D to vendors at the conference.
       
    • Questions that need to be asked of the vendors at preconference (Chris):
      • How to check to see if the server is running

        Are these systems compliant with any profiles? Committed to becoming compliant (schedule/timeline)? If not, what do they support right now?
         
      • What searches are currently supported and what are attribute combinations for each?
         
      • Are you providing indexes according to the indexing guidance document?
         
    • Questions for participants (Chris):
      • Would you be willing to be notified by email if your Z server if down?
         
      • Will you provide connection information concerning your server? Either email it to Marilyn Johnson or we will provide a web form for submission. Chris and Marilyn will work on this form.
         
    • Presiders (Chris):
      • Take notes on the answers to general questions (e.g., Bath compliant? which levels? timelines?)
         
      • Provide a copy of the server list for everyonest
         
      • Provide a copy of subscription information for TZIG discussion list
         
  • Texas Z39.50 Server Information web page

    www.tsl.texas.gov/ld/projects/z3950/serverinfo.html
    • Marilyn Johnson has agreed to update this list. As server information changes, please email Marilyn with the updates.
       
    • It is estimated that Texas may have between 400-500 Z39.50 servers
       
    • Z-Spy from Index Data: www.indexdata.dk/zspy/
      • "Z-Spy is a robot-like script that automatically probes Z39.50 targets."
         
      • "Z-Spy will determine what parts of the Z39.50 protocol a given target supports and keep track of what targets are live. If a problem is encountered Z-spy can send an alerting e-mail to the system administrator and it can display detailed information on the target's support of various parts of the Z39.50 protocol plus reliability statistics."
         
      • Can this software be used to inform Z sites when their servers are down. Can it be modified to automatically send an email to the administrator instead of creating a report?
         
      • Kevin Marsh will research to see if this is feasible.
         
  • Bid Language for Z39.50 Functionality within an ILS

    www.tsl.texas.gov/ld/projects/z3950/rfplang.html
    • Available for libraries to use for bid documents.
       
    • We have had no comments on the language from vendors or librarians.
       
  • Z Texas Client
    • This client is almost ready to distribute. When it is ready, Bob Gaines will post the location to the z3950-tx discussion list.
       
    • Slavko has created a solid list of 46 Texas servers which will work with the client. Librarians should never get an unsupported search error message, as the list only includes the searches that are supported and work for each site.
       
    • The help section for the client no longer applies because of the changes made. Bob will ask that a URL be used in the help section. In this way, we can keep the help for this product and customize it as needed.
       
    • The audience for this client is librarians, not the the public.
       
    • This software will be demonstrated at the Technology programs for Small Library Management this spring.
       
  • Z Client Gateway Exploration
    • Kevin Marsh created a web page from which you can launch queries against Z servers using Index Data's ZAP
       
    • A couple of things were learned:
      • As a user interface, allowing a user to choose libraries by clicking on them becomes wearying
         
      • When searching all sites at once, many come back with errors (i.e., not found, attributes not supported)
         
    • To continue this research, what functionality do we want to see in this type of gateway:
      • Ability to limit by local geographic area (~10 miles)
         
      • Ability to limit by ILL providers that work with your home library
         
      • Ability to search by collection focus
         
      • Ability to search by type of library
         
    • Slavko showed us a demonstration of simultaneously searching Z and non-Z sites (libraries, databases, search engines); a profile had to be set up for each site searched (via SIRSI iBistro). The results are returned in both HTML and XML. The ZIG is allowing us to incorporate a Z search within a URL. This allows us to more easily search via the web. In order to make this sustainable, need to have these databases set up a Z structure on their end.
       
    • Kevin will put up a draft page with modified gateway
       
  • Z39.50 Implementation Aids
    • With no volunteers for this project, need to re-evaluate.
       
    • Many of the items we want are on the web site, but need to be pulled together. After that is done, we'll see what we still need to do. Maybe tackle these projects one at a time.
       
    • Do we want a form on this page asking for ideas for information needed here?
       
    • With the coming of ZLOT, maybe some of these will be created at TSLAC
       
  • Interoperability Testbed at the University of North Texas
    • Configuration of the Unicorn system has been complete
       
    • The 400,000 OCLC records are being parsed (resulting in approximately 4.5 million data elements)
       
  • ZLOT
    • "Virtual Catalog" or "Z Portal" part of the Library of Texas
       
    • Bill Moen is working on needs assessment for Telecommunications Infrastructure Fund Library Working Group, which dovetails with his ZLOT work
       
    • Focus groups have started; some political issues are starting to surface. This part of the LOT will have many more political issues than some of the others.
       

     

Functional Area D:
 

Since this profile deals only with searching of the citation and abstract information and not the full text, should we include a statement concerning searching full text? If a vendor is going to provide fulltext searching as well as searching of the citation and abstract, should we ask to have them standardize in some way (e.g., use use attribute 1010 - body of text; structure attribute 2). Maybe we could do this in a non-normative section of the document. Difficult to say something about an area that the profile does not cover.

Need to add a statement concerning the default Boolean operator if more than one keyword is used in a keyword search.

  • Level 0: High recall searches
  • Level 1: Greater precision
  • Level 2: Specialized audiences/searches

D.0.1. Author Search - Keyword

Use: Searches for complete word in fields that contain the name of a person or entity responsible for a resource.

 

Attribute Type Attribute Values Attribute Names
Use (1) 1003 author
Relation (2) 3 equal
Position (3) 3 any position in field
Structure (4) 2 word
Truncation (5) 100 do not truncate
Completeness (6) 1 incomplete subfield

D.0.2. Title Search - Keyword

Use: Searches for complete word in fields that contains titles of resources.

Attribute Type Attribute Values Attribute Names
Use (1) 4 title
Relation (2) 3 equal
Position (3) 3 any position in field
Structure (4) 2 word
Truncation (5) 100 do not truncate
Completeness (6) 1 incomplete subfield

D.0.3. Subject Search - Keyword

Use: Searches for complete word in fields that contain subjects (e.g., descriptors, identifiers, subject headings).

Attribute Type Attribute Values Attribute Names
Use (1) 21 subject
Relation (2) 3 equal
Position (3) 3 any position in field
Structure (4) 2 word
Truncation (5) 100 do not truncate
Completeness (6) 1 incomplete subfield

D.0.4. Any Search - Keyword

Use: Searches for complete word in fields that are commonly used as access points (as defined by the server). Any searches comprising more than one keyword are interpreted in such a way that the terms may exist in the same or different attributes.

Attribute Type Attribute Values Attribute Names
Use (1) 1016 any
Relation (2) 3 equal
Position (3) 3 any position in field
Structure (4) 2 word
Truncation (5) 100 do not truncate
Completeness (6) 1 incomplete subfield

--------------------------------------------------------------------------------



D.1.1. Author Search - Keyword with Right Truncation

Use: Searches for complete word beginning with the specified character string in fields that contain the name of a person or entity responsible for a resource.

Attribute Type Attribute Values Attribute Names
Use (1) 1003 author
Relation (2) 3 equal
Position (3) 3 any position in field
Structure (4) 2 word
Truncation (5) 1 right truncate
Completeness (6) 1 incomplete subfield

D.1.2. Title Search - Keyword with Right Truncation

Use: Searches for complete word beginning with the specified character string in fields that contain titles of resources.

Attribute Type Attribute Values Attribute Names
Use (1) 4 title
Relation (2) 3 equal
Position (3) 3 any position in field
Structure (4) 2 word
Truncation (5) 1 right truncate
Completeness (6) 1 incomplete subfield

D.1.3. Subject Search - Keyword with Right Truncation

Use: Searches for complete word beginning with the specified character string in fields that contain subjects (e.g., descriptors, identifiers, subject headings).

Attribute Type Attribute Values Attribute Names
Use (1) 21 subject
Relation (2) 3 equal
Position (3) 3 any position in field
Structure (4) 2 word
Truncation (5) 1 right truncate
Completeness (6) 1 incomplete subfield

D.1.4. Any Search - Keyword with Right Truncation

Use: Searches for complete word with the specified character string in fields that are commonly used as access points (as defined by the server). Any searches comprising more than one keyword are interpreted in such a way that the terms may exist in the same or different attributes.

Attribute Type Attribute Values Attribute Names
Use (1) 1016 any
Relation (2) 3 equal
Position (3) 3 any position in field
Structure (4) 2 word
Truncation (5) 1 right truncate
Completeness (6) 1 incomplete subfield

D.1.5. Author Search - Unanchored Phrase

Use: Searches for a phrase anywhere in fields that contain the name of a person or entity responsible for a resource.

Attribute Type Attribute Values Attribute Names
Use (1) 1003 author
Relation (2) 3 equal
Position (3) 3 any position in field
Structure (4) 2 word
Truncation (5) 100 do not truncate
Completeness (6) 1 incomplete subfield

D.1.6. Title Search - Unanchored Phrase

Use: Searches for a phrase anywhere in fields that contain the title of a resource.

Attribute Type Attribute Values Attribute Names
Use (1) 4 title
Relation (2) 3 equal
Position (3) 3 any position in field
Structure (4) 2 word
Truncation (5) 100 do not truncate
Completeness (6) 1 incomplete subfield

D.1.7. Subject Search - Unanchored Phrase

Use: Searches for a phrase anywhere in fields that contains subjects (e.g., descriptors, identifiers, subject headings).

Attribute Type Attribute Values Attribute Names
Use (1) 21 subject
Relation (2) 3 equal
Position (3) 3 any position in field
Structure (4) 2 word
Truncation (5) 100 do not truncate
Completeness (6) 1 incomplete subfield

D.1.8. Any Search - Unanchored Phrase

Use: Searches for a phrase anywhere in fields that are commonly used as access points (as defined by the server).

Attribute Type Attribute Values Attribute Names
Use (1) 1016 any
Relation (2) 3 equal
Position (3) 3 any position in field
Structure (4) 2 word
Truncation (5) 100 do not truncate
Completeness (6) 1 incomplete subfield

Next Meeting:
 

Handouts:
 

 

Return to Z39.50 Home

 
Page last modified: April 29, 2014