RE: Troubleshooting SCAT tables
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
I would like to thank everyone who replied to my posting about
troubleshooting SCAT tables.
The review file method of pinning down call number ranges, along with
searching the call# index via OPAC, has indeed helped us get a lot of
the gaps closed, and at this stage of the game, it looks like we just
have some more leg-work to do with these techniques. Funny - it
basically is what our trainer had explained but for some reason it
didn't click for me until I re-read Sandra's posting (below). We've got
it down from 18,000 down to 7,000 and making progress with each review.
Thanks for the replies, and thanks Corey for the update about the
enhancement for a tool that addresses this function. We will look
forward to seeing it in action.
Paul
___________________________________________
Paul Ericsson
Adult Services Supervisor / Automation Coordinator
Concord Public Library http://www.onconcord.com
45 Green St. Concord, NH 03301 603 230-3697
pericsson at onconcord dot com
___________________________________________
-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Seeman, Corey
Glenn
Sent: Wednesday, April 06, 2005 9:14 AM
To: IUG INNOPAC List
Cc: Seeman, Corey Glenn
Subject: RE: Troubleshooting SCAT tables
Paul and Sandra --
Sandra's solution makes a great deal of sense. Thanks for sharing it
with the list.
I was just looking at the Release 2005 preliminary enhancements
documentation and it appears that the reports will be able to write all
the records to a review file that fall out of the SCAT table when
running a report. These would be in the "Call number not in table"
category. If you have a lot that are falling out of the table, you can
break it down into sections (using Sandra's methodology below). One of
the nicest features of Millennium Statistics is to create a report by
index ranges without having to create a list first.
For the list of 2005 enhancements in Management Tools, please see:
http://csdirect.iii.com/csd/release_notes/enhlist/Rls2005_Prelim_Enhlist
.php#management_tools
Hope this is good news. We will be happy about this in Toledo.
Best -- Corey
Corey Seeman
Assistant Dean for Resource and Systems Management Assistant Professor,
University Libraries Carlson Library Mailstop #509 University of Toledo
2801 W. Bancroft
Toledo, OH 43606
---------------
corey dot seeman at utoledo dot edu
419.530.2333 (phone)
419.520-2726 (fax)
http://library.utoledo.edu/userhomes/cseeman (my home page)
http://library.utoledo.edu (main library page)
Nothing in life is to be feared, it is only to be understood. Now is the
time to understand more, so that we may fear less.
--Marie Curie
-----Original Message-----
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Card, Sandra
Sent: Tuesday, April 05, 2005 12:11 PM
To: 'IUG INNOPAC List'
Subject: RE: Troubleshooting SCAT tables
We have had a similar problem. I managed to reduce the amount of 'gap'
records by creating review files of call number ranges, e.g. H-HF etc
and run the SCAT against the review file. If a call number area had no
gaps, I could go on to the next call number area. This helped narrow the
problem from about 20,000 to less than 1,000 by identifying a narrower
area of the SCAT table to proofread.
Even though I had set up our SCAT table with ranges that included call
numbers that do not exist in LC, I still found a few areas with slight
problems. We originally had a SCAT table over 700 lines long, but
narrowed it down. In the process of redoing the SCAT table, some typos
occurred.
Once I resolved those through the review file method, we had less gaps.
However, we still have some unidentifiable gaps. I seem to remember
past enhancement requests to get out a list of such records?
This method does not tell you the gaps, it merely helps point out what
part of the SCAT table to review, review, and review again.
Sandra Card
Library
California State University, Los Angeles scard at calstatela dot edu
323-343-4894
-----Original Message-----
From: Ericsson, Paul [mailto:PEricsson at onconcord dot com]
Sent: Tuesday, April 05, 2005 8:42 AM
To: IUG INNOPAC List
Subject: Troubleshooting SCAT tables
Colleagues --
Our SCAT table continues to give us "challenges" (ahem). I know that
there
has been chatter on the list recently, but we are still stuck.
For our collection of 140,000 items, we have about 18,000 that are
falling
into a "gap" on the SCAT table. This is in addition to a smaller and
known
group of items that have "no call number"
We've tried to fill in the gaps in the SCAT table by defining some
ranges
that are not really call number ranges for our collection, but
theoretically
could be between where one real call number range ends, and where the
next
begins (know what I mean?). This has identified a small number, but not
hardly a dent in the 18K. We've done call number searches in the OPAC to
try
to identify the gaps, and still cannot find how the heck the huge group
of
items are hiding from the SCAT table.
So, I get this great plan, I thought, to run a cross-tab statistic
report,
using itype for the horizontal axis, and SCAT (call number) for the
vertical
axis. The idea is if we could find out what itypes are reporting a
record
count for this "gap" SCAT category, we could pin down some of the
variables
and hopefully find the culprits. But, no deal! The cross tab report does
not
list the "gap" even though the field statistics query does list the
"gap"
Has anybody been down this road and had a solution to help identify the
gaps
in the SCAT table? Tips & tricks?
Please excuse any repeat of earlier postings.
Thanks,
Paul
___________________________________________
Paul Ericsson
Adult Services Supervisor / Automation Coordinator
Concord Public Library http://www.onconcord.com
45 Green St. Concord, NH 03301 603 230-3697
pericsson at onconcord dot com
___________________________________________
--
This message was distributed through the Innovative Users Group INNOPAC
list
Public replies: INNOPAC at innopacusers dot org Update your subscription
options:
http://innopacusers.org/mailman/listinfo/innopac
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
--
This message was distributed through the Innovative Users Group INNOPAC
list
Public replies: INNOPAC at innopacusers dot org
Update your subscription options:
http://innopacusers.org/mailman/listinfo/innopac
--
This message was distributed through the Innovative Users Group INNOPAC
list
Public replies: INNOPAC at innopacusers dot org
Update your subscription options:
http://innopacusers.org/mailman/listinfo/innopac