[Koha] Koha suppression of records

[Linda Culberson]

Margo,
You're a life saver, and since the life you probably saved is my own, I 
am very grateful.
Thanks!
Linda

On 9/8/2011 1:04 PM, Margo Duncan wrote:
> Linda,
>
> Yes, that's right.  You should be able to see that in your Authorized Values.  I've attached a screenshot of ours.
>
> Margo
>
> -----Original Message-----
> From: Linda Culberson [mailto:lculber at mdah.state.ms.us]
> Sent: Thursday, September 08, 2011 11:57 AM
> To: Margo Duncan
> Cc: koha
> Subject: Re: [Koha] Koha suppression of records
>
> Margo,
> Thanks for the reply.  We were discussing that possibility and I was wondering if having anything in the 942 subfield n suppressed it or does it have to be a "1"?  So is it unsuppressed if it's a "0"?
>
> I really appreciate your help.
> Linda
>
> On 9/8/2011 11:26 AM, Margo Duncan wrote:
>> Linda,
>>
>> I would change the default for 942$n to 0.  Your staff will then use the correct framework, but add changing 942$n to 1 as part of their workflow.
>>
>> Margo
>>
>> Margo Duncan, MLS
>> Systems Librarian
>> Robert R. Muntz Library
>> The University of Texas at Tyler
>> 903.566.7174 | mduncan at uttyler.edu
>>
>> -----Original Message-----
>> From: koha-bounces at lists.katipo.co.nz
>> [mailto:koha-bounces at lists.katipo.co.nz] On Behalf Of Linda Culberson
>> Sent: Thursday, September 08, 2011 10:46 AM
>> To: koha
>> Subject: [Koha] Koha suppression of records
>>
>> All,
>> We are having a problem with suppression of newly created records in
>> Koha and wonder how others are handling the work flow with newly
>> created records and items. We have/had some of our frameworks set up
>> where the default for the 942 subfield n was 1 so that a record when
>> created would be automatically suppressed.  But that record can't be
>> unsuppressed, apparently and stay in that framework because when
>> saved, the default setting puts it back to 1  - suppressed.  So we
>> were going to then leave the default framework  to be unsuppressed,
>> meaning that if a record is "finished" it has be be changed to
>> default.  The problem is the the 952 fields are set according to
>> framework - because we have so many different types of materials and
>> collections that adding new items goes much faster when you are in the
>> right framework.  But if you change a records framework to add items,
>> then you must remember to change it back every time to get it
>> unsuppressed again.  So, our system isn't work
> ing.
>>
>> I'm having a hard time convincing the staff this isn't a bug in Koha, that it just is the way it works.  So my question is, what does work?
>>
>> Any suggestions would be greatly appreciated.
>>
>

-- 
Linda Culberson      lculber at mdah.state.ms.us
Archives and Records Services Division
Ms. Dept. of Archives & History
P. O. Box 571
Jackson, MS 39205-0571
Telephone:  601/576-6873   Fax:  601/576-6824