Re: Millennium Spine Label, Cont.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Date: Thu, 6 May 2004 15:12:55 -0400 (EDT)
- From: "Leo Papa" <papal@xxxxxxxxxx>
- Subject: Re: Millennium Spine Label, Cont.
Thank you for responding. I enjoyed your session on printing @ IUG but did
not want to impose upon you personally. I did not mention that our library
is a Silver site, so perhaps the problem I'm focusing on (which I reported
to III about 2 weeks ago) does not occur in Phase III label printing.
I'll embed my additional questions and comments within yours, below.
> In a nutshell, the system options in DB maintenance control all aspects of
> spine label printing from MilCat and from the character-based cataloging
> functions. PrintWizard can manipulate the output to a degree, but cannot
> fundamentally change the output.
While I have been able to define the fields to be printed on our spine
lable, through DB Maintenance, I am not sure the label size specs are
affecting the output in MilCAT.
> What exactly are you looking for? What you're telling the system right
> now is this:
> You want a spine label that is 8 characters wide
> You want a pocket label that is 1 character wide
> You want 3 characters between the 2
> You want the label to be 6 characters tall
> You want a 3-character gap between labels, vertically.
> Is this correct? Based on this, I'm assuming you're dealing with 1-inch x
> 2/3-inch labels with a 1/2-inch vertical gap between them, and no pocket
We only want to print spine labels. The actual size and space between
columns will be determined by the label stock we choose. This will
probably be something like Gaylord LSL02 spine labels (1"H x 1/3/5W), I
just hadn't looked for stock before entering these test sttings.
> We print both spine and pocket labels, so our init file won't help.
At IUG I was told that if you do not want to print a pocket label, don't
define it in DB Maintenance. So have not identified any fields for pocket
lables. But the setting for width in DB Maintenance will not except a
value of zero. So I defined the pocket label at the minimum width of 1
The problem, as I see it, is that the template in MilCAT (Silver?) does
not seem to adjust the size of the pocket label (or spine for that matter)
to these size specs in DB Maintenance. In MilCAT preview or print mode,
the template still has a 7 char spine and 28 char pocket label.
> Also, what version of PrintWizard are you using? If you're using 2.6, try
> using /preview to help you get your columns correct. What's important is
> the columnoffset setting, which tells PrintWizard how wide a column should
> be. If your labels are 1 inch wide and have a quarter inch gap, then you
> want to set columnoffset=1.25in columngutter=0.25in (Offset goes from
> column beginning to column beginning, gutter counts backwards and leaves
> that much of a gap.)
I have been able to adjust the size of the columns, in Print Wizard
preview, but the output is being affected by the number of characters in
both the spine and pocket label of the MilCAT template. Each field of the
call number is followed by 28 spaces for a non-existent pocket lable. This
is what I mean by the spine labels being offset.
> Hope this helps!
> Joe R.
> At 01:12 PM 5/6/2004 -0400, you wrote:
>>I've reviewed recent postings about Millennium spine lable printing and I
>>don't see a reference to the following question:
>>Do label specifications in DB Mainenance have any affect on the template
>>used to print lables within Millennium Cataloging?
>>INNOPAC SYSTEM OPTIONS (Database maintenance)
>>1 > Print spine label: YES
>>2 > Width of spine, in columns: 8
>>3 > Width of label, in columns: 1
>>4 > Width of gap, in columns: 3
>>5 > Height of label, in lines: 6
>>6 > Vertical space between labels on printout, in lines: 3
>>7 > Printer selection: USE LOCAL PRINTER
>>8 > Breakmode for call number: BREAK ON SPACE & SUBFIELD
>>These settings do not seem to change the appearance of the template
>>provided when I print lables in MilCAT. The template controls output
>>through a Standard Printer, as expected. But it also seems to affect
>>output generated by Print Wizard via JetDirect, even though the data is
>>being filtered by an *.init file.
>>If the MilCAT label template cannot be altered through Innovative, will a
>>correctly configured *.init file overide the template settings? So far
>>the sample "lables.ini" provided with PW only seems to offset the data
>>stream recieved from Millennium, i.e., it does'nt fully overide the
>>Does anyone have an *.init file for printing spine labels with parameters
>>similar to those I've specified above? If so, I would appreciate a copy
>>via my personal e-mail address. If you send one, please state the vendor
>>name and stock # for the label.
>>Canton Public Library
>>734.397.0999 ext 160
>>This message was distributed through the Innovative Users Group INNOPAC
>>Public replies: INNOPAC@xxxxxxxxxx
>>Update your subscription options:
> Joe Reimers
> Technology Support Assistant
> Notre Dame Law Library
> (574) 631-5994
> This message was distributed through the Innovative Users Group INNOPAC
> Public replies: INNOPAC@xxxxxxxxxx
> Update your subscription options:
Canton Public Library
734.397.0999 ext 160