RE: protecting the new circactive field?

["Seeman, Corey Glenn" <CSeeman@xxxxxxxxxx>]

Lesha -- When we were beta testing, this field in our patron records were also unprotected insofar as editing is concerned.  In Milcirc, it has a different color background.  

We contacted the helpdesk about this and they set it right up.  However, we never thought about the overlaying problems that you outlined below.  We are looking at the same situation, by doing regular downloads and blowing out the CIRCACTIV field (I have not really looked at it since the early days of our implementation with Phase 3 and I am now I have nothing there).  

This is an excellent point and I suppose that it was just left off the Phase 3 install.  I would imaging that a call to the helpdesk to get this added to the fields that can be chosen for protection is the ticket for people who load full databases on a regular basis.  

Thanks for brining this to the attention of the users.  

Best -- Corey
 
Corey Seeman
Assistant Dean for Resource & Systems Management 
University of Toledo
corey.seeman@xxxxxxxxxx
419-530-2333
 
http://library.utoledo.edu/userhomes/cseeman/
http://library.utoledo.edu (Main Library Page)
 

	-----Original Message----- 
	From: Lesha Fossey [mailto:L.Fossey@xxxxxxxxxx] 
	Sent: Wed 9/24/2003 7:48 AM 
	To: innopac@xxxxxxxxxx 
	Cc: innocirc@xxxxxxxxxx 
	Subject: protecting the new circactive field?
	
	

	(crossposted to innocirc - apologies if you receive a duplicate)
	
	Hi
	
	I've just noticed that the new "Circactive" fixed field in patron records is NOT
	automatically protected from being over-written when an incoming record matches
	and overwrites!
	
	Even worse, when I try to add that field to our overlay protection list (system
	options, database maintenance options, edit overlay protection list, patron
	record) and choose Add a fixed length field, that the new CIRCACTIVE field
	doesn't appear, so I can't even add it to the overlay protection table manually!
	
	Has anyone else noticed this? And if so, is it just a case of getting Innovative
	to add it to the list of fixed fields so I can then add it to our table
	manually? Or do people agree that it really should be automatically protected
	like several other fields? Wasn't the whole point of it that we could tell when
	a record was last used for circulation rather than merely updated?!
	
	Opinions/suggestions please.....
	
	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
	

¶¸©2)žEêh®Úk¡Ç¬±çL Á)j»lšémŠ–«·ö¥µêçjدz×±·úej)í{[¡Ü¤z›m{†Ù¥