[ List Archives Home ] [ Thread index for 2008 ]
[ Date index for 2008 ]
[ Author index for 2008 ]
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
- Date: Thu, 25 Sep 2003 12:26:02 -0400
- From: "Gowing, Cheryl A." <cgowing@xxxxxxxxxx>
- Subject: RE: RE: protecting the new circactive field?
It may be that as long as the CIRCAC field is incorrectly editable on
your system, then it would not be overlay protected on a download,
unless you specifically reference it in the patron load profile.
I tested our CIRCAC field as soon as I read Corey's posting, and found
that it was also editable. I called the Help Desk to have them fix
this and get the fixed field reference number so I could adjust our
patron load profile [it's #163].
I was told "all the fixed fields should automatically be protected from
overlay" - seemingly implying to me that no action was needed on my
part.
I test loaded/overlaid my patron record and found the circactive field
was wiped out. Luckily, III hadn't yet 'fixed' the fact that CIRCAC was
incorrectly editable on our system, so I was able to edit my CIRCAC
field to reset it. I then edited our m2btab.p profile, adding 163 to
the list of fixed fields to protect, and reloaded my record. This time
the CIRCAC field was protected.
I alerted the Help Desk to the fact that they may start receiving a
large volume of calls on this, as it is beginning to look like a
systematic bug.
I would suggest you first test whether CIRCAC is editable, and if so,
contact the Help Desk to have this turned off. Once CIRCAC is no longer
editable, then test whether it is being protected from overlay. It may
be that once the field is no longer editable, the field is automatically
protected. If not, then your patron load table will need to be
adjusted, either locally or by III.
Cheryl A. Gowing
ILS System Coordinator
Richter Library
University of Miami
Coral Gables, FL 33124
Ph: (305) 284-6018
Fax: (305) 284-4027
cgowing@xxxxxxxxxx
-----Original Message-----
From: Lesha Fossey [mailto:L.Fossey@xxxxxxxxxx]
Sent: Thursday, September 25, 2003 12:09 PM
To: innopac@xxxxxxxxxx
Subject: Re: RE: protecting the new circactive field?
On Thu, 25 Sep 2003 09:02:20 -0400 "Mitlin, Laurance R."
<mitlinl@xxxxxxxxxx>
wrote:
> Here's the reply I got from the helpdesk when I asked about protecting
the
> CIRCACTIV field:
> "This field does not need to be included in this list, nor added to
the
overlay > protection list for patron loads. The field is system
generated and
cannot be > directly edited by staff or patrons. . .
. . .Updating the patron record should not affect this field in any way.
If you
> can provide specific examples where this field is being updated during
a
patron > record load, please let me know. I will then reopen this call
and start
a new > investigation."
Thanks Larry
It DEFINITELY is being overridden in our system, as I've been test
loading a
file of three records (including mine!) in preparation for automating
our staff
details. Before I loaded the file my circactive field had a date in.
After
loading the file it had -- -- --
I called this in to the helpdesk yesterday. I've had a callnumber
response but
no actual reply yet. Perhaps they are realising there is a problem, as
I'd have
expected it to be as they describe.....
I'll keep the list posted.
Lesha
--
----------------------
Lesha Fossey MA MCLIP
Assistant Librarian, Circulation Services
University of Exeter
Stocker Road TEL: 01392 263878
Exeter FAX: 01392 263871
EX4 4PT E-MAIL: L.Fossey@xxxxxxxxxx
--
This message was distributed through the Innovative Users Group INNOPAC
list
Public replies: INNOPAC@xxxxxxxxxx
Update your subscription options:
http://innopacusers.org/list/listinfo/innopac