ub/circ:if mod_op in patron table not SYS-UB, name not updated

• Article Type: General
• Product: Voyager
• Product Version: 2001.2

Description:
Bug Report for Issue # 17608 / VYG-4253

Module: Universal Borrowing/Circulation
Other Modules that are affected or might have an affect: n/a
Release(s) - indicate both first reported in and most recent replicated in:
Reported in 2001.2; replicated in Unicode (QA setup)
PC O/S (if this is PC specific): n/a
Server Platform(s) affected: Solaris/all
Browser type & version (if WebVoyage): n/a

Expected Results:
Information that is protected from editing in the child, such as names and institution ids, will be
updated by changes in the parent - regardless of whether the modify_op_id in the patron table is
SYS-UB or other, or if the transaction is via WebVoyage request (instead of walkup).

Actual Results:
If the modify_op_id in the patron table is not SYS-UB, edits to the name/institution id in the parent
record will not be pulled down into the child during subsequent transactions for walkups; for
transactions that go through the WebVoyage request process, the update does not occur even
if the stub's modify operator id is still SYS-UB.

Workflow implications:
There is no way to edit name/institution id information in a stub, either through the parent or child.
In a situation such as this, the stub would also not be eligible for deletion/re-creation until it passed
its purge date.

Replication steps:
--in dbA create patron John Smith
--create a stub in dbB (with the same name),
--return to dbA and edit the patron's name so the name reads John Doe instead
-->the next time you perform a transaction with the stub, the stub will be updated to read John Doe.
This is expected behavior.
then:
--in dbB, open John Doe's patron record, right click, select Edit Patron and (even w/o editing) click save
(effectively making the modify_op_id in the patron table something other than SYS-UB)
--return to dbA and edit the patron's name so it reads John Smith again.
-->the next time you perform a transaction with the stub, the stub will not be updated, and will retain the name
John Doe instead of changing to John Smith to match the parent record. There is no way to edit this in the
existing stub.
If you repeat the first three steps but perform a subsequent transaction through the WebVoyage request
process again, you'll see that even with a modify operator of SYS-UB, the name will not be updated.

Resolution:

• Article last edited: 10/8/2013