Main -> Support Zone -> InSite Archives -> June 1997 Issue

InSite: Technical News for SiteSearch Users

Issue # 3

June 17, 1997

Contents

InSite is intended to create discussion about the use and implementation of Open SiteSearch software and explore the technology used by its components. The newsletter will be distributed to the SiteSearch list on a regular basis and is designed as an informational resource for SiteSearch system administrators. It is brought to you by the SiteSearch support team. Any suggestions or comments are appreciated.


Top Story

SiteSearch Meetings and Festivities at ALA

Here at OCLC, we are closing out a banner year for the Open SiteSearch software! Highlights include two new software releases and 43 new libraries. It’s become a tradition to share the celebration of our success with the SiteSearch user community at ALA Annual.

This year we are hosting an after dinner dessert buffet on Sunday, June 29, from 9:00 p.m. – 11:00 p.m. in the OCLC Suite. We invite you and your colleagues to come by and sample some special California desserts and dessert wines. Invitations to this special event were sent to your institution’s administrative contact. If you are able to attend and require an invitation, please let us know. If possible, please RSVP by June 20.

In addition, to this social event, you have three opportunities for finding out what’s in the works for SiteSearch:

  1. On Sunday and Monday morning at 8:30 a.m., the SiteSearch staff are hosting breakfast and previewing our ground-breaking work with Java.
  2. On Sunday afternoon, SiteSearch staff will demo a prototype of the coming Web-based documentation. Feedback at this early stage from you and your staff can help us develop a more useful product.
  3. SiteSearch Development and Customer Services staff will be available every day in the OCLC booth 1234 from 11:00 a.m. -12:00 noon and 3:00 p.m. - 4:00 p.m. Please come by for a sneak preview of SiteSearch 4.0.

For all of the above events, please RSVP to Becky Hawk () to reserve a seat. We hope you will be able to attend many of these events and look forward to seeing you in San Francisco!

For those of you who will not be attending the conference, we will be giving you an update of the activities that take place in the next issue of InSite.

[return to top]


FAQs

In each issue of InSite, we will highlight some questions frequently asked of the support team. As a reminder, be sure to send all SiteSearch problem reports to for tracking and assignment.

Displaying Subfields in the correct order

Q: Using a full record fcl I created, how do you display the subfields $x, $y, and $z of 650 and 651 subject fields in the correct order?

A: To keep these in the proper order, set up a "conditional_field" using the desired tags, place the "data_ordered" keyword inside the conditional_field, and finally add the line "field(<desired tags>)". Thus, to keep 24, 25, and 26 in order, add a section like this to your full record Marc fcl:

     conditional_field(24,25,26)

             {

             data_ordered

             field(24,25,26)

             {

             label="[ ... ]"

             trailer="[ ...]"

             separator="[ ... ]"

             [ ... ]

             }

             }

Substringing with Overcite

Q: Is there a way to do substringing in Overcite or in the WebZ entity language? I need to pull individual elements out of the MARC 008 field, which is a fixed- length field with fixed-length elements at fixed positions within the field. I need to test the value in byte 6 of this field and conditionally print one of the dates from bytes 7-10 or 11-14. Any suggestions on how to do this?

A: There is a substr functionality within the WebZ entity language. You can store things in entities and test on them. Add the following to the .fcl within WebZ entity language section (<oclc-app ... ):

      ....

        field(8)

        {

        substr_offset=5

        substr_len=1

        label="byte6=$q"

        trailer="$q;"

        }

        field(8)

        {

        substr_offset=6

        substr_len=4

        label="date1=$q"

        trailer="$q;"

        }

        field(8)

        {

        substr_offset=10

        substr_len=4

        label="date2=$q"

        trailer="$q;"

        }

        ....

        

[return to top]


Software Fixes for Release 3.1

As SiteSearch users report bugs or ask for enhancement requests, our development staff make changes to the executables for SiteSearch. Patch releases replace the executables of your SiteSearch software package and are available from SiteSearch Support. The following section describes patch releases for Version 3.1:

Patch release: ss-3.1.0.1

  1. httpman: A change was made to httpman to handle a new http syntax used by Microsoft Internet Explorer, preview 4.0.
  2. httpgate: When a request was made for a set of records from a Z39.50 server and the maximum message size was exceeded, not all records requested were returned. A fix was made to httpgate to retrieve the remaining records from the server. For example, if a request was made for 10 records and the message size was exceeded, only the first 7 were retrieved in the first response. Httpgate now issues a second request for the remaining 3 records.
  3. httpgate: The overcite formatter was enhanced to enable the use of a very large translate_text_table. Translate_text_table is used within fcl files to transform input data from codes to output as text (i.e., 3-letter codes for languages and holding libraries)
  4. irpserv: For database access controlled at the z39.50 server level, there was a problem with not checking access to messages passed onto another z39.50 server using the version 2 protocol (server_type = irp).

Patch release: ss-3.1.0.2

  1. overcite library: Fixed a problem where new diacritics that were added with add_diacritic keyword were not recognized unless there was a has_diacritics at the top level of the fcl.
  2. irpserv: In the previous version of irpserv, only one tag path or number could be specified for sorting. We have added the option to specify multiple fields. Here is a sample entry for irpserv.ini:
    # sort specification
    
    #             z3950 key   class of sort   newton sort fields	name
    
    sort_field1 = 4           element         26/0 27               title
    
    sort_field2 = 1003        field           27/1,2 28             author
    
    
  3. httpgate: We added functionality required to request sorted records from Sirsi Z39.50 servers. To enable this feature for Sirsi servers, you must add a new server flag: "UseSortAttributesField=TRUE" which will encode the sort request with the sortAttribute tag required by Sirsi.
  4. httpgate: Fixed a problem where search terms longer than 62 characters in conjunction with a CGI script caused httpgate to crash.
  5. httpgate: We have added the ability to store multiple ISOILL authorizations, passwords, and OCLC institution symbols so that different authorizations can be passed to the ILL server based on the users login or location. The following section demonstrates how to create profile database entries:

    The new section added to pro_labels.ini:

            [ISOILL]
    
            var1=ILL_aut
    
            var2=ILL_pwd
    
            var3=ILL_inst

    An example authorization:

          aut=WebZGuest,pwd=WebZGuest,utyp=guest,instsym=ocl,\
    
            ILL_aut=100011111,ILL_pwd=xyz,ILL_inst=ocl,\
    
            name=WebZ Guest User,\
    
            street1=1 SiteSearch Drive,\
    
            cty=Dublin,st=OH,zip=43017,\
    
            cntry=US,phone=6147771111,fax=6147776666,\
    
            id=9999,status=other,dept=technology development
  6. httpgate: Enhanced statistics generation was improved so that null fields won't be written to httpgate log files.

[return to top]


SiteSearch Training Class Schedule

  • SiteSearch WebZ, ZSS, & ISP
    July 14-18, 1997 - Dublin, Ohio
  • SiteSearch WebZ, ZSS, & ISP
    July 28-August 1, 1997 - Dublin, Ohio

Note: Training class schedules are subject to change. For more information or to register for upcoming classes, please contact .

Questions or comments regarding InSite should be sent to with 'InSite' in the subject line.

[return to top]


[Main][Documentation][Support][Technical Reference][Glossary][Search]