Newsgroups: bit.listserv.notis-l
Date:         Mon, 6 Apr 1992 13:17:00 CDT
From:         "Mary Alice Ball, Loyola Univ." <ZMABBIE@LUCCPUA.BITNET>
Subject: Implementing Release 5.0: Log of responses

A couple of weeks ago I sent out two messages asking for advice from
NOTIS sites that had put up 5.0 and survived.  Here is the log I kept.
My thanks to everyone who responded.  Please excuse the fact that our
mailer truncated some messages; I believe it is still possible to
understand the content.  I have included the messages from those
asking for a copy of this information since sometimes that in itself
is useful for tracking sites at the same phase of implementation.

Mary Alice Ball
Head of Library Systems
Loyola University of Chicago                 (312) 508-2686

========================================================================
Date:      Sat, 14 Mar 1992 10:39:39 EST
From:      Lee Radigan <LIBLJR@SUVM.BITNET>
To:        ZMABBIE
Subject:   release 5.0

Hi, Mary Alice!

    I've been fighting with the LSYS data entry here, and can give you
a few pointers, I think.
    First, that note about building order & receiving unit codes before
trying to do OPR security is quite right!  Any code you need on a screen
MUST be defined before you try to use it, no matter what.
    In the NUGM handouts from this past year, there's information on
building circulation tables in 5.0, and the person who put it together
(I think it was Ben Schapiro, but I'm at home and can't verify this)
has shown the circulation-related screens in the order in which you
need to handle them.  For example, you must define fine reasons BEFORE
attempting to build circulation policies.
    There are a couple of things the manuals won't tell you - and they
can hang you up.  If you want to restrict update access for your tech
services workers, you'll need to build "technical processing groups"
and assign each location to a group.  The catch?  There's a maximum of
160 locations per group.  This has to do with the size of the LCRfile
record, and thus is NOT changeable; it's also NOT documented.  Having
hit that restriction head-on, I didn't try grouping more than 160 locs
in a bill & fine payment group, but I strongly suspect the limit holds
there as well.
    Also, I'd recommend a review of all circ policies, because once
they're in 5.0, they're going to be tedious to change.  The reason?
All policies for circulation are established location by location
within service unit.  So, if a given service unit wants to change the
policy for a patron category (or wants to add a patron category), you
can't just enter the change once and reassemble - you have to go into
the policy for each location circulatable at that service unit and
enter the change for that location, then go on to the next.  It takes
a LOT of time!  (Can you tell how happy I'm not?)
    Those are the only things that come to mind right now, but if you
have any further questions, feel free to call me.

Lee Radigan, LIB1             |  "There are many horrible sights in the
Syracuse University Library   |  multiverse.  Somehow, though, to a soul
LIBLJR@SUVM                   |  attuned to the subtle rhythms of a
libljr@suvm.acs.syr.edu       |  library, there are few worse sights than
(315) 443-9507  (voice)       |  a hole where a book ought to be."
(315) 443-9510  (fax)         |                          Terry Pratchett
========================================================================
Date:        Mon, 16 Mar 92 07:29:25 EST
From:        "Gregory S. Mollica" <UPGM@NMUMUS.BITNET>
To:          <ZMABBIE>
Subject: Implementing release 5.0

Mary Alice,

I would be interested in material you receive concerning your
NOTIS-L request for 5.0 installation information. If possible,
could you forward to me any responses you believe are useful.
Else, could you summarize for the list.

Thanks,

Gregory S. Mollica
Project Coordinator
UPRLC, Inc. Automated Library Services
(906) 227-1109
UPGM@NMUMUS



========================================================================
From:         Lydia Pettis <LRP@CORNELLC.BITNET>
Subject:      Re: Another 5.0 question: operator security
To:           "Mary Alice Ball,
              Loyola Univ. of Chicago" <ZMABBIE@LUCCPUA.BITNET>

At Cornell we handled the security by creating "master profiles" and then
copying them and updating as necessary. For circulation, for instance,
we have three levels of security: student, supervisor and billing supervisor.
I created the 3 service unit profiles corresponding to these, and gave
a list of opids for the 3 categories to other people and said "copy this
profile to all of these opids". It worked well to break these down into
the various components of service unit and patron group. You will have a
LOT of profiles for circ staff and need to bear in mind the item record
security changes...which result in more profiles than you ever wanted.

Our circ staff have a profile for our one processing unit (which does NOT
cover temp location access), 2 service unit profiles (their library and a
default service unit--if your circ staff do item record maintenance at a
non-dedicated circ terminal you need the default srvc unit sign-on to allow
temp location access), and 3 patron group profiles.

Your technical services staff who require access to the temp location
field will also require the default service unit profile.

This data entry process is tedious and I recommend batching the profiles
together by group, especially for people who are not really familiar with
the security tables.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*  Lydia Pettis                    PHONE:  (607) 255-9477   *
*  Programmer/Analyst              BITNET: LRP @ CORNELLC   *
*  501 Olin Library                                         *
*  Cornell University              FAX:    (607) 255-9346   *
*  Ithaca, NY  14850                                        *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
========================================================================

Resent-Date:  Fri, 13 Mar 92 15:08:55 CST
Resent-From:  Nancy Pope <LBYSEC@LSUVM.BITNET>
Resent-To:    Mary Alice Ball <zmabbie>
Subject:      Another 5.0 question: operator security

I have maintained Lotus spreadsheet with all the security levels, so I could
sort on CICS ID, seclevl, department, name, etc.
I used the sort on seclevl, entered one at each level, and copied FOREVER.
I noticed I wanted to give everybody access to eveything or nothing by
the end... and I've only done one of my LC104s.
Nancy Pope, LSU
----------------------------Original message----------------------------
Sorry to be posting another message in the same five minutes...

I am trying to download 4.6.1 NOTIS tables and manipulate the data
so that a student can key everything into the control files.  I would
like to streamline the process for the sake of efficiency and accuracy.

Did those of you who entered operator security profiles find one method
preferable?  I am wondering about whether it is easier to pull all info
about an individual together and enter it all at once.  Or whether it
is easier to enter a profile for one person and use the copy feature
to create profiles for staff with identical privileges.  Any and all
comments appreciated.

Thanks.

Mary Alice Ball
Loyola University of Chicago
========================================================================
Resent-Date:  Fri, 13 Mar 92 15:11:33 CST
Resent-From:  Nancy Pope <LBYSEC@LSUVM.BITNET>
Resent-To:    Mary Alice Ball <zmabbie>
Subject:      Implementing release 5.0

I followed Ben Shapiro's instructions from the pre Midwinter Circ workshop,
for the order to enter LCR data. First hint is you DON"T follow the order
listed on the menus. And since circ data is interrelated with all the other...
I could just fill in the odd pieces like LC104. Here it is in brief:

Keep all your LC100, LC101 tables, as well as the ones you think you won't
need.
Service unit work unit security: item, bill & fine, circ funtions.
Patron policy: group, category.
Circ policy: fine reasons & functions, fine reasons; reason/fund exception.
Location: (converted w/NOTIS pgm) check acq, circ & cat values
  system wide hold group. b&f payment group. b&f location/fund exception grp.
Calendar.
Circ policy: loan/overdue policies. item loan codes. circ situations. discharge
  routing intervals.

Then remember: other work unit security, OPAC, and currency conversion.
I'm still plowing through... when we get our 5.0.1 tape to load!
Good luck - I'm glad to know I'm not alone doing this now.

Nancy
----------------------------Original message----------------------------

Loyola is just beginning to implement release 5.0 and I would be happy
to learn from others' experiences.  Does anyone have implementation or
testing plans that he or she would be willing to share?  I have looked
through technical and user documentation, and Telnet'd to Syracuse and
searched NOTIS-L.  I can't find anything that establishes if the control
files should be entered online in any particular order.  However, I have
a note in last year's NUGM material that says order/receiving units
must be entered before o/p/r work unit security.  It is this type of
information that I would be especially grateful for.

Thanks for your help.

Mary Alice Ball
Loyola University of Chicago
========================================================================
To: ZMABBIE
From: "Maria R. Sugranes"  <MARIA@FELIX.LIB.CSULB.EDU>
Date:     13 Mar 92 13:25:56 PST
Subject:  Re: Implementing release 5.0

Hi Mary Alice, if you get anything good please pass it on.  We are
putting 5.0 in test then 5.0.1 then 5.0.2 just for my staff.  Hope to
have it for regular staff test sometime in April.


Maria R. Sugranes, Manager Library Automation Services, Cal State Long Beach
                       maria@felix.lib.csulb.edu
                     (310) 985-1776  (310) 985-1703 FAX
========================================================================
Date:         Mon, 16 Mar 92 09:32:24 CST
From:         SMUIR@UA1VM.BITNET
Subject:      Table for 5.0.x
To:           Mary Alice Ball <zmabbie>

Mary Alice, Feel free to call me if you do not get enough information
about inputting tables.  I will be glad to share tips and horror stories
with you.

********************************
*  SCOTT P. MUIR               *
*  THE UNIVERSITY OF ALABAMA   *
*  SMUIR@UA1VM                 *
*  SMUIR@UA1VM.UA.EDU          *
*  (205) 348-2299              *
********************************
========================================================================
Date:      Mon, 16 Mar 92 08:20:03 CST
To:        ZMABBIE
From:      "Fred Gulden" <LB.FHG@ISUMVS.BITNET>
Subject:   Creating 5.0 operator security

>I am trying to download 4.6.1 NOTIS tables and manipulate the data
>so that a student can key everything into the control files.  I would
>like to streamline the process for the sake of efficiency and accuracy.
>
>Did those of you who entered operator security profiles find one method
>preferable?  I am wondering about whether it is easier to pull all info
>about an individual together and enter it all at once.  Or whether it
>is easier to enter a profile for one person and use the copy feature
>to create profiles for staff with identical privileges.  Any and all
>comments appreciated.
>
>Thanks.

I would recommend the latter course, unless you want to keep your students
busy for days on end.  I grouped the profiles into clumps of people that
were alike or very nearly alike.  It's much faster to copy a profile and
then make a few changes than it is to create an entire new one for each
person.  I didn't have any students and had to do it all myself, so I
felt a bit of time spent up front organizing things was time saved later
on.

One caveat ...   When you create a profile in LSYS for a user ID
that doesn't exist yet in LMST, one is created in LMST under the covers.
Presumably the LMST profile that gets created should be identical to the
one that exists for the profile you are copying from.  So you need to
be careful/mindful of what is in LMST security as well as LSYS security
if you use the copy approach.

************************************************************************
*  Fred Gulden                     *                                   *
*  Systems Specialist (LIB1)       *    BITNET:  LB$FHG@ISUMVS         *
*  34 Parks Library                *     PHONE: (515) 294-2445         *
*  Iowa State University           *       FAX: (515) 294-1885         *
*  Ames, IA  50011                 *                                   *
************************************************************************
========================================================================

From:         Edie Dixon <DIXON@WISCMACC.BITNET>
Subject:      Re: Implementing release 5.0
To:           "Mary Alice Ball,
              Loyola Univ. of Chicago" <ZMABBIE@LUCCPUA.BITNET>

For the circ portion, you need loan codes established, patron groups and patron
categories established, location names established,  ---  all the "building
blocks"  before you do any of the loan and situation stuff.  It really is like
starting from scratch -- and, based on LC102 tables, from front, then to back to
front (i.e. locations, then cirps, then cirpols.cirplans)

Call if you want more detail -- we just went up last Thursday -- and nottoo bad,
if I do say so myself!

Edie Dixon, LIB1
U of Wisconsin
bitnet: DIXON@wiscmacc
phone: 608-262-3525
========================================================================

Date:     Wed, 18 Mar 1992 08:27 CST
From:     <WRIGHTJA@VUCTRVAX.BITNET>
Subject:  What I wish I'd Known
To:       zmabbie

Mary Alice, let me congratulate you on the adventure on which you are about to
embark.  We implemented 5.0 without benefit of any documentation and survived
it, so it can be done.  Handy hints, which you may have received elsewhere:
1.  NEVER, NEVER copy one location from another one.  It copies technical
processing groups (used to restrict work on records to subsets of locations
within the processing unit).  Unfortunate, and NOTIS acknowledges the problem,
but hasn't fixed it.  You need to establish what subsets of records may need to
be available for editing, and after a location is defined you add the location
to the group.  We used a combination of processing unit code and service unit
code to name the groups.  A couple of locations that were set up by copying
can't be used or corrected because of our attempt at efficiency.  Bill and fine
groups for service units are another example of what could go wrong in copying.
2.  Dates for beginning of circulation "situations" are automatically set at the
date the policy is entered in the tables.  Since you will have a number of
materials charged out under the old policies when you change to 5.0+, set up a
macro with the date (maybe when you went onto NOTIS, or something way back) and
enter it when the tables are created.
3.  Keying in all of the information is cumbersome and time consuming, but you
can copy security from one ID to another, and circulation situations, as well.
4.  You can copy all of the circulation situations for one location to another
location, even between service units.  The bad news is, though, that you can't
add a new patron category to more than one existing set of situations without
entering it in in the table each location affected by the change.
5.  You have probably heard about service unit vs. processing unit priorities
in security for item records, but it never hurts to be reminded.  This release
seems to assume that service units should have the "final say-so."  You can not
enter a temporary location in an item record from any terminal which is not
identified with a service unit, in 101TB4.  This is unfortunate in our opinion,
since it necessitates allocating a lot of terminal resources to service units
just so that temporary locations can be used.  Many of our public service folks
could do some temp. location work from dial-in terminals in their offices, but
the terminals must now have an assinged address and be identified to a service
unit, which is a chore to say the least.  At first, we wasted a lot of time in
trying to establish what was wrong with the operator security when people
couldn't do what they could do in 4.6.
6.  Don't run the LCSH heading claiming program, if you load these tapes in
your system.  It doesn't work, and makes trouble.  But that a post
implementation bit of advice.

These are the searing memories that come to mind immediately.  I hope that they
don't come as a surprise to you.  Good luck in your implementation, there are
some good things, like the immediate changes in authorizations, location names,
policies, etc. when you have LSYS up and running.

_______________________________________________________________________________
/ Jean Wright                        /                 Bitnet:                /
/ Research and Development Librarian /           WRIGHTJA@VUCTRVAX            /
/ Library Systems                    /                Internet:               /
/ Vanderbilt University              /      wrighja@ctrvax.Vanderbilt.Edu     /
/ Nashville, TN                      /         Phone: (615) 322 - 2718        /
-------------------------------------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU