TAB100-OPAC-NEW-ACQ is ignored in v.19 and v.20

• Article Type: General
• Product: Aleph
• Product Version: 19.01

Description:
Problem Description: In v.19 and v.20, regardless of the OPAC-NEW-ACQ setting, OPAC acquisition requests are allowed.

Actual Results:
If OPAC-NEW-ACQ = Y then OPAC acquisition requests are allowed.
If OPAC-NEW-ACQ = N then OPAC acquisition requests are allowed.

Expected Results:
If OPAC-NEW-ACQ = Y then OPAC acquisition requests are allowed.
If OPAC-NEW-ACQ = N then OPAC acquisition requests are not allowed.

Resolution:
OPAC-NEW-ACQ was depricated in v.19.

Upgrade Instructions:
1. The TAB100-OPAC-NEW-ACQ will not be used and should be deleted from tab100 of BIB library.
Note that it does not have a "header description" at tab100, since it was added to a closed version.

2. A new field added to Z61: Z61-NEW-ACQ-REQUEST Y/N
The Data Upgrade for Z61 should be as follows:
IF TAB100-OPAC-NEW-ACQ of bib_library/tab100 is "Y" AND
Z61-NEW-BOOK-PERMISSION = "Y"
THEN
MOVE "Y" TO Z61-NEW-ACQ-REQUEST
ELSE
MOVE "N" TO Z61-NEW-ACQ-REQUEST
END-IF.

3. The following WF files are new files:

bor-acq-body
bor-acq-tail
bor-acq-no-acq
bor-acq-head
bor-acq-exp-data
bor-acq-exp-cancel
bor-acq-exp-back
acq-request-doc-tail-conf
acq-request-doc-tail
acq-request-doc-head-conf
acq-request-doc-head
acq-request-confirm
acq-request
login-acq-session

• Article last edited: 10/8/2013