HDTenEightyP/NetNews huggingface dataset:
Newsgroups: bit.listserv.notis-l
Date:         Tue, 21 Jul 1992 16:54:08 PDT
Comments:     Resent-From: Kathleen Matthews <LSYS1@UVVM.UVic.CA>
Comments:     Originally-From: Kathleen Matthews <LSYS1@UVVM.UVic.CA>
From:         "Kathleen Matthews" <LSYS1@UVVM.UVIC.CA>
Subject:      usage stats for inhouse periodical use
Comments: cc: Donna Signori <LDIVCOL2@UVVM.UVic.CA>,
              Elena Romaniuk <ENGIN@UVVM.BITNET>,
              Jessie Kurtz <JKURTZ@UVVM.UVIC.CA>,
              Dan Gillett <ZZGILLET@UVVM.BITNET>

**********************************************************************
KATHLEEN WEBSTER MATTHEWS (LSYS1@UVVM.UVIC.CA)
Systems Librarian, McPherson Library
UNIVERSITY OF VICTORIA, VICTORIA, B.C., CANADA.
(604) 721-8219
**********************************************************************


----------------------------Original message----------------------------
Our Collections Librarian has been asked to identify periodicals for
cancellation. A criteria that was referenced in pre NOTIS times was the
date stamp data in the various issues. Since NOTIS has been implemented our
library made a policy decision to not circulate periodicals. Thus we have
no date stamp data and no barcode for in house discharge stats. Is there any
library out there that has a clever method of determining in house use of
a periodical collection that does not involve barcoding and discharging
the issues? We are toying with the idea of date stamping as we reshelve
as a way to avoid barcoding.  Are there any non-NOTIS solutions (micro/manual)
that any of you are using that would generate ready made reports?  The fact
that we would still have to write a fancy SAS report to extract any meaningful
stats even if we were to go to the trouble of barcoding and discharging on
NOTIS the issues used in house does not encourage us to go ahead with a NOTIS
approach. Is anyone deriving meaningful stats on serial title usage from
the OPAC transaction logs ?  Many patrons first search the OPAC to get the
serial call number so is there search string data out on the logs that
perhaps could be used to derive some stats ??? If only the format was always
included in the search string????????   Thanks for any ideas/responses.

**********************************************************************
KATHLEEN WEBSTER MATTHEWS (LSYS1@UVVM.UVIC.CA)
Systems Librarian, McPherson Library
UNIVERSITY OF VICTORIA, VICTORIA, B.C., CANADA.
(604) 721-8219
**********************************************************************
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Purdue University Libraries
Newsgroups: bit.listserv.notis-l
Date:         Wed, 29 Jul 1992 10:43:19 EST
From:         Alan Alexander-Manifold <ALANAM@PURCCVM.BITNET>
Subject:      Re: 5.1 OPAC CHANGES (SCREEN)
              28 Jul 1992 14:11:19 PDT from <LSYS1@UVVM.UVIC.CA>

We have modified the screens provided from NOTIS quite substantially, and
are facing a very quick deadline for putting 5.1 in production.  I have
written a set of four SAS programs to help us with this conversion.  One
program extracts the OPAC screen data from the 5.0.2 LCRFILE and puts it
into an ASCII file, with each screen marked and separated by some coded
header and footer lines.  A second program takes the ASCII file and puts
it back into 5.0.2 LCRFILE record format, ready to be REPRO REPLACEd back into
the LCRFILE.  The third and fourth programs do the same for a set of 1.2.1 MDAS
screens from the SCRFILE.  In the JCL, you specify the database name in
an input file, and the screens are extracted.  You the do the same in
reverse to create 1.2.1 SCRFILE type records ready to REPRO REPLACE in your
SCRFILE.

This may not seem like much help, but the point is what you do with the
file while it is in ASCII format.  You can edit the file on your mainframe,
with any editor you have available, or, if you can download or ftp the
file to your PC or some other machine, you can pop it into your favorite word
processor to move text, delete and insert lines, even create new screens
if you can figure out the header information.  You can then upload the
file back to your system and run the reverse program to take your newly
formatted screens and put them back in the LCRFILE or SCRFILE.

I am willing to make these programs available, either through NOTISPRO
or by direct request to those that are willing to take them at their own
risk.  NOTIS is not fond of people manipulating the system control files
in this manner, and will be ready to lay the blame on these programs if
you later encounter problems with your LCRFILE or SCRFILE.  The programs
are not an ideal solution anyway, but it beats calling each screen up
with LSYS or MSYS and editing without a real editor.

Please respond directly to me if you would be interested in obtaining
these programs.  I'll gauge from the response how I should make them
available.
                                                         \
       --Alan Alexander-Manifold               THe Online Resource
         Systems Implementation Manager        TTTTTTTTTTTTTTTTTTT
         Information Technology Department       T         //
         Purdue University Libraries             T  H H  OOO  RRR
         West Lafayette, Indiana   47907         T  HHH//O O  RRR
         (317) 494-2857    FAX: 494-9007         T  H/H  OOO  R R
         alanam@purccvm          (BITNET)           \\
         alanam@vm.cc.purdue.edu (Internet)           \
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.notis-l
Date:         Sat, 25 Jul 1992 16:21:50 EDT
Comments:     Resent-From: Betty Landesman <BETTY@GWUVM>
Comments:     Originally-From: Betty Landesman <BETTY@GWUVM>
From:         Betty Landesman <BETTY@GWUVM.BITNET>
Subject:      Bibliographic software

I'm going to try re-sending this - don't think it got to the list the
first time around.
----------------------------Original message----------------------------
We have looked into PBS' ProCite for downloading and manipulating records from
NOTIS.  However, it will handle only 3 processing units.  We are part of a
consortium system, and 3 is not enough.  PBS will only change this as
custom programming for us.  At a not trivial cost.

Is there anything ELSE out there that anyone on the list knows of that we
should investigate?  Or does anyone have a solution for the ProCite problem?


Betty Landesman
Coordinator, Systems Planning
Gelman Library
George Washington University
2130 H Street NW
Washington, DC   20052
BITNET: BETTY@GWUVM   Internet: BETTY@GWUVM.GWU.EDU
Phone: 202-994-1333   Fax: 202-994-1340
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.notis-l
Date:         Wed, 29 Jul 1992 13:42:31 EDT
From:         Irene Pelak <pelak@PILOT.NJIN.NET>
Subject:      Renew Overdue Tracking Number

We are getting some overdue notices for items that show a future due date.
All these itmes appear to have been renewed after they had become overdue.  It
appears that the renewal did not remove the reuest for the overdue notice to
be printed but the notice reflects the new due date.  I believe that there was
some discussion of this problem a little while back and I am looking for a
problem tracking number.
IRENE PELAK  TECH1  BERGEN COMMUNITY COLLEGE  201-447-9236
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.notis-l
Date:         Wed, 29 Jul 1992 16:02:42 EST
From:         Tom Norman <normant@GVSU.EDU>
Subject:      Global Heading Changes & LB890J

          In the hopes of saving someone hours of headaches (not to
          mention useless output) --  the UPSI switch settings for job
          LB890J  (Global Change Processing) do NOT work as
          documented.

          We tried running the job with the UPSI settings as
          '11100010'.  The job processed (with all condition codes
          equal to zero).  However, no records (bib or authority) were
          actually updated.

          After long sessions on the phone with NOTIS (and a 32 page
          fax) we found that the switches were not functioning as
          documented.  Per NOTIS we processed the job with the
          settings equal to '11000000'.  The job went to good EOJ, and
          all records (bib and authority) were updated accordingly.

          Tom Norman
          Systems Analyst
          Grand Valley State University
          Allendale, MI

          Internet:        normant@gvsu.edu
          Voice:           (616) 895-2289
          Fax:             (616) 895-3889
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Organization: Southeastern Louisiana University
X-Envelope-to: notis-l@TCSVM.BITNET
X-VMS-To: IN"notis-l@tcsvm.bitnet"
Newsgroups: bit.listserv.notis-l
Date:         Thu, 30 Jul 1992 16:07:00 CDT
From:         Kevin Calmes <TMIS1692@VEGA.SELU.EDU>
Subject:      Chat - Why Assembler is here to stay.

Here is why assembly language will never disappear...

Electricity on = 1, electricity off = 0 (or the inverse may be true as well)

There... Now you have two choices.  How you choose the arrange this abstraction
is entirely up to you.  Remember that if you choose not to decide, you still
have made a choice.

Hey! I know what!  Let's arrange a set of 8 switches and say that 11000001 = A

Nah, let's not.  Nobody would believe it anyway!

Kevin

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
*  Kevin Calmes                           Internet: TMIS1692@SELU.EDU         *
*  Library Programmer - TECH1             IP#       147.174.1.5               *
*  Computing Services - MIS               Bitnet:   TMIS1692@SLU.BITNET       *
*  Southeastern Louisiana University      Voice:    (504) 549-3645            *
*  Box 409 SLU Station                    Fax:      (504) 549-5092            *
*  Hammond, LA  70402   USA               IBM 4361-M5  DOS/VSE/SP 3.1.2       *
*                                         CICS 1.7  NOTIS 4.6.1  GTO 3.0      *
*  "S'cuse me while I kiss the sky"       Location: 30.30.15N  90.27.40W      *
*                     Jimi Hendrix        Fishnet:  At the pond               *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: University Of Toledo
Newsgroups: bit.listserv.notis-l
Date:         Wed, 29 Jul 1992 11:45:59 EDT
From:         Douglas E Sinnott <SYSDES@UOFT01.BITNET>
Subject:      Chat: Enhancements

As a long time assembler programmer I'll jump in here just because:

The problem with the LMS code from my (a systems programmer) perspective,
is not that it's written in assembler, but that it's very poor program
design.

Modules have undocumented interdependencies; values that should be
variables are hard coded; the original programmer was paid by the number
of branch instructions he/she put into the program :-)

It matters not what language you implement the system in as long as the
basic design is sound.

Doug

+----------------------------------------------------------------------+
| One reason you can't take it with you is that it goes before you do. |
|                                                                      |
+----------------------------------------------------------------------+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.notis-l
Date:         Mon, 27 Jul 1992 17:18:00 EDT
From:         Dina.Giambi@MVS.UDEL.EDU
Subject:      Job Advertisement
Comments: To: NOTIS-L@VM.TCS.Tulane.EDU

     POSITION AVAILABLE DELAWARE - SEARCH EXTENDED TO 9/1/92

University of Delaware Library.  SEARCH EXTENDED  Head, Central Processing
Department.  Reporting to the Asst. Director for LIbrary Technical Services,
responsible for monographic and serial acquisitions, serials control and
public services, and government documents processing.  Integrated library
system using NOTIS software.  The department has a total staff of 27 includig
4 professional librarians in addition to the department head.  Qualifications:
Required: ALA accredited Master's degree; five or more years of professional
library experience, at least two in acquisitions.  Some supervisory
experience. Strong oral and written communications skills.  Ability to work
effectively and cooperatively with diverse personnel.  Preferred:  Experience
with an automated acquisitions system.  Knowledge of the domestic and foreign
book trade. Salary and Benefits: Rank and salary dependent upon experience and
qualifications. Senior Assistant Librarian (minimum $28,633), Associate
Library (minimum $32,044), or Librarian (minimum $36,411).  Prefer to hire at
the Associate Librarian level. Liberal benefits.  For further information
writeor call Maidel Cason, Assistant Director for Library Administrative
Services, University of Delaware Library, Newark DE 19717-5267.  (302) 831
2231. E-mail Maidel.Cason @mvs.udel.edu.  To ensure consideration applicatons
must be received by September 1, 1992.  Affirmative Action/Equal Opportunity
Employer.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: ELM [version 2.3 PL0]
Newsgroups: bit.listserv.notis-l
Date:         Tue, 28 Jul 1992 11:13:22 CDT
From:         Notis General ID <notis@TWAIN.NOTIS.COM>
Subject:      NOTIS AND Z39.50

THIS IS AN OFFICIAL NOTIS COMMUNICATIONS - DUE TO TECHNICAL PROBLEMS THIS NEVER
REACHED NOTIS-L

NOTIS Demonstrates Full Z39.50 Inter-operability!

On June 4, 1992, NOTIS demonstrated full NISO Z39.50 inter-operability with the
Coalition for Networked Information (CNI) test bed site at the University of
California Department of Library Automation. As part of the test the NOTIS
client exchanged standard Z39.50 protocol elements with the DLA server and
performed several inter-system searches. Since that time NOTIS has expanded
its test to include servers from OCLC, AT&T, UC Berkely, Penn State and MIT.

NOTIS is the first library vender to provide Z39.50 inter-system searching as
standard product offerings. Z39.50 support is included in the PACLink product,
InfoBase-- a Z39.50 database server, and ProPAC a Z39.50 graphical client.

The NOTIS PACLink product is installed at our four co-development SUNY
 Stonybrook.

For more information on PACLink contact NOTIS Systems at 708-866-0150.

Thank you in advance
Cheryl Wallace
Customer Support Services
Support Center Administrator
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.notis-l
Date:         Mon, 27 Jul 1992 09:50:46 EDT
Comments:     Converted from PROFS to RFC822 format by PUMP V2.2X
From:         PSAU@VM2.YORKU.CA
Subject:      New Circ Notice Problem

Yes, we have the exact same problem at York University and our tracking
number is PPQ7472.

>An item was charged on June 23 by a patron whose id expired oJune 26, so a due
>date of June 26 was generated.  So far so good.  The first overdue notice was
>generated on July 21 as if the patron had the full 14 day loan and then adding
>the 14 days we normally wait before printing our first notice.  I think the
>notice should have been generated 14 days after June 26.  Is this a problem?
>Does any one else have this problem?  Is there a problem tracking number?
>IRENE PELAK  TECH1  BERGEN COMMUNITY COLLEGE  201-447-9236

Pak Sau
Library Computing Services
York University, Toronto, Canada
Environment: MVS/XA, LMS 5.0.2, NOTISearch 1.0.1.
             (LMS 5.1 and MDAS 1.3 in test region).
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.notis-l
Date:         Wed, 22 Jul 1992 16:46:00 CDT
From:         Barbara <BAUGHMAN@UTDALLAS.BITNET>
Subject:      Recalls

We have had so many problems with recalls, and we keep learning of new
ones.  There is no way to allow recalls and enforce reasonable policies
on fines or even due dates.  Whoever rewrote this part of NOTIS to work
with the new LCRFILE tables, didn't understand how the system was suppose
to work.  This program or programs needs to be totally reviewed
and reworked.  Piecemeal fixes are not acceptable.  Unless this is reworked
I cannot be convinvced that there aren't more bombshells waiting to be
discovered.  Somewhere in the process, recall coding was not properly
explained to the programmer, not thoroughly tested, or something.
Does NSI even have something that explains the program logic as it
existed in 4.6.1?  We'd like that same logic to be reflected in 5.0.x.
Right now it doesn't even bear a remote resemblance.  And, yes, there are
other folks who recall NSI saying at NUGM 1991 "There are no changes to
the circulation module except that some things that obviously didn't use
to work now work."

I'm not trying to put the blame on anyone in particular.  I'd personnally hate
to be the programmer who had to figure out how recalls work.  I just want
it redone so that it works.  NSI needs a very clear flowchart of the recall
logic and someone needs to check that the logic is followed in the program.
Without this, I don't see how NSI can claim to have an LMS system that
handles recalls.

Barbara Baughman
TECH1
University of Texas at Dallas
(214) 690-2157
BAUGHMAN@UTDALLAS.BITNET
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.notis-l
Date:         Thu, 30 Jul 1992 14:40:26 EDT
From:         Gerald Snyder <FCLGES@NERVM.BITNET>
Subject:      Re: Chat: Enhancements
              30 Jul 1992 10:13:15 EDT from <gpmenos@FIRESTONE.PRINCETON.EDU>

On Thu, 30 Jul 1992 10:13:15 EDT Gerard Philippe Menos said:
>
>Assembler was once necessary to ensure an efficient application.  The
>compromise in software development was necessary to accomodate the
>hardware of the past.  But advances in hardware now allow us to get
>the apps we need more quickly and more cheaply with high-productivity
>development environments, without compromising on performance.
>
>Phil Menos
>Princeton University Libraries


     How many sites can afford to upgrade hardware everytime a
vendor increases the function/resource load of its software ?
Good design improves performance in any language. Good design
also improves maintainability. Putting in the effort for a well
designed, efficient system is part of the reason that software
work gets concentrated into a central companies.

Gerald Snyder, FCLA
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Resent-Organization: Southern Methodist University
Newsgroups: bit.listserv.notis-l
Date:         Mon, 27 Jul 1992 16:04:19 CST
Comments:     Resent-From: Carolyn Kacena <VB7R1001@SMUVM1>
Comments:     Originally-From: "Kathleen Matthews" <LSYS1@UVVM.UVIC.CA>
From:         Carolyn Kacena <VB7R1001@SMUVM1.BITNET>
Subject:      Re: New Circ Notice Problem

Yes, if you want to block on the number of overdues outstanding the block
appears to only come into effect after the first notice is printed...in our
case 7 days after it is overdue.  This has recently been confirmed within
our test region as we tried to work out various notice message relationships.
We are using NOTIS5.0.1 in production and test -- MVS/XA and CICS2.11.


Carolyn Kacena
Director, Academic Support Automation
Fondren Library East 328
Southern Methodist University
Dallas, TX 75275-0135

(214) 692-3229             FAX: (214) 360-0609 or (214) 692-4138
Bitnet:   VB7R1001@SMUVM1
Internet: VB7R1001@vm.cis.smu.edu.

----------------------------Original message----------------------------
Does this mean that the patrons are not blocked until the
overdue notice is produced?????

On Mon, 27 Jul 1992 09:50:46 EDT <PSAU@VM2.YORKU.CA> said:
>Yes, we have the exact same problem at York University and our tracking
>number is PPQ7472.
>
>>An item was charged on June 23 by a patron whose id expired oJune 26, so a due
>>date of June 26 was generated.  So far so good.  The first overdue notice was
>>generated on July 21 as if the patron had the full 14 day loan and then adding
>>the 14 days we normally wait before printing our first notice.  I think the
>>notice should have been generated 14 days after June 26.  Is this a problem?
>>Does any one else have this problem?  Is there a problem tracking number?
>>IRENE PELAK  TECH1  BERGEN COMMUNITY COLLEGE  201-447-9236
>
>Pak Sau
>Library Computing Services
>York University, Toronto, Canada
>Environment: MVS/XA, LMS 5.0.2, NOTISearch 1.0.1.
>             (LMS 5.1 and MDAS 1.3 in test region).

**********************************************************************
KATHLEEN WEBSTER MATTHEWS (LSYS1@UVVM.UVIC.CA)
Systems Librarian, McPherson Library
UNIVERSITY OF VICTORIA, VICTORIA, B.C., CANADA.
(604) 721-8219
**********************************************************************
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.notis-l
Date:         Wed, 29 Jul 1992 17:44:14 EST
From:         Debbie Morrow <morrowd@GVSU.EDU>
Subject:      CHAT-L: to alleviate or not to alleviate ....
Comments: To: notis-l@tcsvm.BITNET, abbottd@GVSU.EDU

   After marveling over the concept of "not alleviating" the OPAC screen
   problem, I concluded that the sentence was *supposed* to have read,
   "Prepare *now* to alleviate ...."  I agree with the request that NSI
   provide a conversion program personally, although I will have to re-do
   our EXP screens myself in any case.  I found this out mere days after
   designing floor plans that take up the (presently) available screen area
   pretty much entirely.  Sigh!

   Debbie Morrow
   GVSU
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: ELM [version 2.3 PL0]
Newsgroups: bit.listserv.notis-l
Date:         Wed, 29 Jul 1992 11:19:46 CDT
From:         Notis General ID <notis@TWAIN.NOTIS.COM>
Subject:      CICS STATUS: MACRO TO COMMAND LEVEL

THIS IS AN OFFICIAL NOTIS COMMUNICATIONS - DUE TO TECHNICAL PROBLEMS, THIS NEVER
 REACHED NOTIS-L

For MVS users only, IBM will no longer support macro level CICS with release
 3.2. NOTIS has had several calls from customers about our migration plans.

MDAS was the first NOTIS product written to command level. Over the past three
 years we have been working toward migrating all products from macro level to
 command leve.  Several products and various modules of the LMS Systems have
 been successfully converted to command level language:

-OPAC
-LSYS, NSYS, MSYS ETC.
-SERIALS
-GTO
-NOTISearch
-PACSearch
-PacLoan

Other modules are in the process of being rewritten to command level code. This
 is a bigger project than we originally forcasted, and it will take several
 years to migrate all NOTIS products to command level coding. Our committment to
 command level coding can be seen in the number of products we have already
 converted.

NOTIS Systems, Inc.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: ELM [version 2.3 PL0]
Newsgroups: bit.listserv.notis-l
Date:         Thu, 23 Jul 1992 10:40:21 CDT
From:         Notis General ID <notis@TWAIN.NOTIS.COM>
Subject:      TOPIC--1992 NUGM speaker correction

DUE TO TECHNICAL PROBLEMS THIS MESSAGE NEVER REACHED NOTIS-L. WE APOLOGIZE
FOR THE INCONVENIENCE THE DELAY MAY HAVE CAUSED.

Please make the following changes to the Session Descriptions in your 1992
NUGM Registration Booklet:

Session #67:  Tracing an LT Transaction
	The Presenter should be Tom Marqui,
				Systems Engineer
				NOTIS Systems, Inc.

Session #86:  Tracing an OPAC Transaction
	The Presenter should be Jerry Specht
				Chief Systems Engineer
				NOTIS Systems, Inc.

Thank you in advance for your participation in NUGM 1992.