Z TEXAS MEETING

9:00am - 4:00pm
May 6, 2002
Texas State Library and Archives Commission
1201 Brazos
Austin, TX 78205
512-463-5456

Z39.50
Home | Implementation Resources

Minutes

[Maroon text color indicate work items.]

Attendees:

• Virginia Allen, Lamar University
• Holly Gordon, Texas State Library and Archives Commission
• Cathy Hartman, University of North Texas, co-chair
• Marilyn Johnson, Texas State Library and Archives Commission
• Slavko Manojlovich, SIRSI/Memorial University of Newfoundland
• Kevin Marsh, Texas State Library and Archives Commission
• Jim Moreno, Texas State Library and Archives Commission
• Christine Peterson, Amigos Library Services, co-chair
• Sheila Williams, Euless Public Library

Functional Area E

Functional Area D in Bath is now being used for authority record searching; we are switching ours to Functional Area E.

Review of searches from last meeting:

• Level 0:
  • E.0.1. Author Search - Keyword
  • E.0.2. Title Search - Keyword
  • E.0.3. Subject Search - Keyword
  • E.0.4. Any Search - Keyword
• Level 1:
  • E.1.1. Author Search - Keyword with Right Truncation
  • E.1.2. Title Search - Keyword with Right Truncation
  • E.1.3. Subject Search - Keyword with Right Truncation
  • E.1.4. Any Search - Keyword with Right Truncation
  • E.1.5. Author Search - Unanchored Phrase
  • E.1.6. Title Search - Unanchored Phrase
  • E.1.7. Subject Search - Unanchored Phrase
  • E.1.8. Any Search - Unanchored Phrase

Level 1:

E.1.9. Standard Identifier - Keyword
Uses: Searches standard identifiers such as ISBN, ISSN, ERIC, etc., but does not identify a specific standard number scheme.  Servers can choose which standard identifiers to index to support this search.

E.1.10 Date of Publication Search
Uses: Searches for the year in which a resource is created.
Possible Field Names: Publication Year, Creation Year, Start Date, End Date (journal start and end dates)

The Date of Publication Use attribute must be used as a search limiter in conjunction with another operand (i.e., used to limit a search using other Use attribute values). Z-servers may reject a query that only includes the Date of Publication Use attribute.

(If vendors have a mmddyy date, can they get the yyyy date that is required here? Are they compliant if they don't translate to the yyyy format?)

E.1.11 Language Search
Uses: Searches for a phrase that indicates the language of the resource.

The Language Use Attribute must be used as a search limiter in conjunction with another operand (i.e., used to limit a search using other Use Attribute values). Z-servers may reject a query that only includes the Language Use Attribute.

Checked Dublin Core - DC-Language (1105) to see if it supports a phrase search; DC actually uses a 2-letter code for language, so changed to word search

Add to the beginning of the document: Written with Texas databases in mind. TexShare has at least one database written in Spanish. Written for databases in which the citations are in a single language.

E.1.12 Source Search - Title-Host-Item
Uses: Searches for a phrase that indicates the language of the resource, e.g., journal titles, conference titles, book titles.

E.1.13 Availability of Items with Full-text Search

Check with OCLC to see how they do this; we expect a Yes/No or a flag
Maybe ask ZIG for new use attribute

Talked about adding a Date Range Search.  

• Used in NISO and Bath; many of their records have a Date 1 and Date 2, so a range search is necessary
• In these types of databases, we rarely have two dates
• This search is not needed

E.1.14. Resource Type Search - Phrase
Uses: Searches for phrase that indicates the type of resource, e.g., journal articles, conference papers, world-wide web resource.

• Checked into Dublin Core DC-ResourceType, but it isn't robust enough for our needs.
• Asked others to check their databases to see what types of information are in these types of fields; there is no standard; some values are phrases, so decided to code this as truncated phrase search

Level 2:

Discussed including a search or limiter on Audience; however, we weren't able to find enough data to understand how this might work

Discussed the possibility of a Name Search – Unanchored Phrase. However, we determined that vendors generally cannot differentiate between topical and name subjects, so decided not to implement this yet.

Discussed the possibility of including searches for each controlled vocabulary, but it is not necessary in this environment

E.2.1 URL Search
Uses: Searches for a complete or partial Uniform Resource Locator.

Ask Ray Denenberg what the best use attribute is for this search and what is the best attribute combination to use when searching URLs with truncation.

Check SilverPlatter, Ebsco, and OCLC to see what attribute combinations they use for URLs

FYI: Want to to be able to put in a string of characters, e.g., nasa.gov and find jpl.nasa.gov and trk.nasa.gov and www.nasa.gov

We discussed including Publisher Name Search - Keyword, but decided this was more useful in a native interface for a single database; less so in a broadcast search; so we didn't include it

Scan

• We found no paragraph explaining scan in NISO; it isn't intended for broadcast; need to ask Bill if this is true for NISO and Bath;
• Can we view a browse list for titles, authors, subjects?

E.2.SCAN.1 Author – Exact Match
Uses:To browse an ordered list of words that contain the name of a person or entity responsible for a resource.

E.2.SCAN.2 Title – Exact Match
Uses:To browse an ordered list of words that contain the titles of resources.

E.2.SCAN.3 Subject – Exact Match
Uses: To browse an ordered list of subject-type words (e.g., descriptors, identifiers, subject headings).

The termlist for a Subject Exact Match Scan is:

In browse, need to check to see if structure is word or phrase in Ebsco, OCLC or SilverPlatter 

Look at wording -- Virginia, Sheila, Kevin and Bill; then send to some vendors for feedback

Z Texas Profile

• Need to update Z Texas to come into compliance with NISO and Bath; keep the name of the search in Z Texas; link directly to the search in the NISO profile
• Discussed differences in format searches in Bath and NISO; decided that we needed a phrase search that will retrieve data from MARC subfields that do not necessarily use controlled vocabulary, e.g., 245 |h

Z Texas Client

• The client is now available via CTLS web site; available at no charge
• http://www.ctls.net/ztexas/

Virtual Union Catalog

• Valerie Johnson leaving TSLAC; Kevin Marsh will be covering some of her work until the position is filled

Interoperability Testbed

• Testbed is up and running
• http://www.unt.edu/zinterop/

Title for Functional Area E - Profile for Searching Citation Databases

• databases can have full-text attached, but just searching the citation
• not searching citation databases like SSCI or SCI
• Think about it

Next Meeting:

• May not need one, so none scheduled
• Small group will look over a draft of the profile
• After changes are made, will send the profile our for comment to interested vendors

Handouts:

• Agenda
• Access points for full text/A&I databases (from 11/13/01 meeting)
• The U.S. National Z39.50 Profile for Library Applications (DRAFT, September 15, 2001)
• Bib-1 Attribute Set
• Structure for Identifying Searches (worksheets)
• Format Searches (Bath and NISO)
• Z Texas Profile, revised draft, May 4, 2002

Return to Z39.50 Home

return to top