Re: SCAT Table question

["Felice K. Lowell" <felice.lowell@xxxxxxxxxx>]

The only way I know of to make the scat table work is to insure that the 
database is "clean."  Unless you write into the scat table all possible 
variations you want recorded, you won't be getting accurate answers.  In 
other words, if your call numbers are keyed Fiction|aAbe and Fiction 
|aAbe and Fiction |a Abe (note spacing), you will have to set up a scat 
table which searches for all of those conditions.  The alternative is to 
search for each condition, determine which alternative you prefer, and 
globally update all of those 099 fields which do not conform.  A lot of 
work now, but ultimately rewarding.
Another solution - again long term and labor-intensive - remove the 
location i.e. Fiction or Video or Vid from the call number so that the 
scat table sorts only by the call number portion.  Then you will also be 
able to determine what titles are in which location for an inventory or 
other purpose.
Or , globally update Fiction |aAbe to 822|aAbe - and Vid |a822.33 to 
Video|a822.33 - and Video 1077 to Video|b1077, etc
 
Felice

Penny Cowan wrote:

>     I'm positive that SCAT tables will be the death of me!  Can anyone 
> give words of wisdom when trying to track local call numbers -- i.e.  
> Video 1077, Video Midwest,  Vid 822.33, Fiction Abe, Bio Hunt, Garden 
> Jus,  etc.  We have all of these kinds of call numbers in 099 fields 
> that are indexed in our Dewey index.  Some are entered with a subfield 
> a between words and some are not --  i.e. Fiction|aAbe,  Video 1057    
> Our SCAT table contains both LC and Dewey call numbersr along with 
> these local call numbers and we are getting way too many that show up 
> as not in table.  Thanks, Penny Cowan




--- StripMime Report -- processed MIME parts ---
multipart/alternative
  text/plain (text body -- kept)
  text/html
---