X-Envelope-to: notis-l@tcsvm.BITNET
X-VMS-To: NET%"notis-l@tcsvm"
Newsgroups: bit.listserv.notis-l
Date:         Mon, 27 Jul 1992 12:58:00 EDT
From:         Janet Woody <JWOODY@VCUVAX.BITNET>
Subject:      updated MDAS enhancement list

MDAS 1993 Enhancement List as of July 27, 1992


Numbers 13 and 14 are new to the list; number 12 may already be
included in release 1.3.   Can anyone confirm that?

I will be sending the final enhancement list to NOTIS by August
10, so quick responses will be appreciated.

If you've sent me your rankings already, you don't have to send
them again unless you've want to makes changes because of 13 and
14.  Thanks for your contributions to this list.

Janet Woody, MDAS SIG chair
phone: 804/367-0032
fax: 804/367-0151
Bitnet: jwoody@vcuvax

13   Add the ability to print or download circulation status.

     Rationale:  Circulation status will aid users and library
     staff in finding materials.

14   Allow separate security definitions for each database.  As
     an alternative to the current method of assigning a security
     level to each database and each patron category, add the
     capability to be able to limit database access to the patron
     category/department level.  This should be possible in the
     database definition function, where each patron
     category/department allowed to have access could be listed.

     Rational:  This is necessary to support licensing
     agreements.



Security features

1    Add the ability to suppress display of the security
     authorization number as the user types it.  Rationale:  This
     will prevent security authorization numbers from being
     "stolen" or "borrowed".

2    Add the ability to allow the patron to specify which kind of
     ID will be used for security authorization: SSN or patron
     ID.  Rationale:  Some sites have patrons with one or the
     other type of ID and adding this capability will support
     both types.

3    Add the ability to limit access to the MSYS function to
     screens only, similar to the way LSYS access can be limited
     to OPAC screens only.   Rationale:  This will prevent
     unauthorized staff from changing database parameters
     available in MSYS.


Editing features

4    Improved screen editing capability for MSYS and LSYS screen
     editing programs.
     Including:
          a.   Ability to insert lines in a screen or screen set
               and easily reformat the new screen.
          b.   Ability to delete lines and easily reformat the
               remaining lines.
          c.   Ability to move and copy lines within a screen or
               screen set across screens or screen sets.
          d.   Ability to copy entire screens or screen sets from
               one database to another (including from and to the
               OPAC).
          e.   Ability to make global screen changes; for
               example, to change every occurrence of a word or
               phrase on all screens with one command.

5    Ability to define system-wide explain screens that are
     accessible from the OPAC and all databases, or any
     combination of these.

     Rationale for 4 and 5:  These will make screen creation and
     editing simpler.


Holdings features

6    When HO is selected from an MDAS record, the system should
     display a summary holdings screen of the same format as that
     displayed in OPAC.  User options should be the same as in
     the OPAC.  Rationale:  This will help users to learn how to
     use the system and to interpret screens if MDAS and OPAC use
     the same formats and displays.

7    Add the ability to define the display order for processing
     units in the holdings locations display.  (for LSYS and MSYS
     programs)  Rationale:  This will allow each site to
     customize locations display so users can more easily be
     directed to appropriate locations.  At this time, processing
     units display alphabetically, which often places the most
     obvious location at the end of the listing.

Downloading and printing features

8    Add the ability to download/print holdings information.

9    Add the ability to define a separator page for output routed
     to a system printer.  Ideally, the system would prompt the
     user for a name to print as a header and footer for any
     print requests submitted from a terminal attached to a
     system printer.  There is no need to verify this name
     against the patron file since it is only used as an
     identifier on the separator page.  This should be definable
     at the terminal level through the NSYS function.  Rationale:
     This will assist users in identifying their printouts.


Documentation Enhancements

10   Provide complete documentation for the subdatabase feature
     including detailed description of how it works, its
     implications for MDAS users, any system resource
     implications, additional files and/or indexes required, CICS
     table changes needed, and database updating implications.
     Rationale:  We need full information when determining if
     subdatabases are useful for our sites, and, obviously, it is
     helpful to know how subdatabases work when attempting to set
     them up.

11   Provide complete and accurate field mapping documentation
     for all loaders.  Rationale:  This information is essential
     for determining labels, data display options, and training
     documentation.


Miscellaneous - This one may be included in release 1.3.

12   Add the ability to define brief and long views similar to
     the capability currently available for the OPAC within LSYS.
     Rationale:  This will increase compatibility between OPAC
     and MDAS.


Removed from the list:
     Support multiple institution groups' OPACs (with capability
     of different screen displays for each) in the MDAS menu
     structure.  At this point, we are more concerned with
     multiple OPACS being listed than with the ability to hook to
     multiple OPAC holdings.

     This capability exists with MDAS 1.3, zero level MDAS, and
     PACLink.


Before the following item will be added to the list, I am waiting
for NOTIS Systems to inform me as to whether or not this problem
is corrected in 5.0.2 or 5.1.  The PST number is PPQ 3763.  Does
anyone out there know if this works properly in 5.0.2 or 5.1?

     Add the ability to access any of the MDAS databases from the
     LT transaction.  At this time, when a search is redirected
     to the OPAC with an LTxx transaction, (for example, LTxx fi
     t dogs, which switches to the OPAC) the error message
     "command not recognized" displays whenever an MDAS database
     code is entered.


Loaders:

Cumulative Contents
Faxon Finder
MLA Bibliography
Facts on File

Chemical Abstracts  (new to this version of the list)
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU