1. Log for Patron Record Changes
Version 21 rep_ver #017818
Yoel Kortick

2. Agenda Introduction Configuration Example
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

3. Introduction Purpose of Enhancement
A new log records changes made to the patron record, the name of the user who implemented the change, and the time and date the change was made.
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

4. Introduction Description (part 1 of 2):
The log is created when one of the following is added, updated, or deleted in the patron record :
global patron record
local patron information
address information
patron IDs
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

5. Introduction Description (part 2 of 2):
The following new components have been added:
A new ORACLE table, Z307 of usr_library, for recording changes made on patronʹs related entities.
A new configuration table, tab_patron_log.lng, which defines the actions that trigger patron log creation (Z307).
A new batch service, cir-27, which produces a report of changes made for patron records.
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

6. Agenda Introduction Configuration Example
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

7. Configuration Make sure Z307 Oracle table exists in the $usr_library:
desc z307
Name Null? Type
Z307_REC_KEY NOT NULL CHAR(27)
Z307_USER_LIBRARY CHAR(5)
Z307_ACTIVE_LIBRARY CHAR(5)
Z307_TYPE CHAR(3)
Z307_TEXT VARCHAR2(300)
Z307_CATALOGER_NAME CHAR(10)
Z307_CATALOGER_IP VARCHAR2(20)
Z307_CATALOGER_IP_V VARCHAR2(50)
Z307_DATE_TIME_X CHAR(14)
Z307_UPD_TIME_STAMP CHAR(15)
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

8. Configuration
Define the actions that trigger log creation by configuring ./<usr_library>/tab/ tab_patron_log.lng. !
!!!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!->
001 Y Update of global patron record-Details
002 Y Update of global patron record-Blocks
003 Y Update of local patron record-Details
004 Y Update of local patron record-Blocks
005 Y Update of local patron record-Privileges
006 Y Update of patron addresses
007 Y Update of patron IDs
010 Y Delete of global patron record
011 Y Delete of local patron record
012 Y Delete of patron address record
013 Y Delete of patron ID
020 Y New global patron record created
021 Y New local patron record created
022 Y New patron address record created
023 Y New patron ID created
See table header for more details
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

9. Configuration
If localization is required, add the following lines to ./alephe/pc_b_lng/ menu-circ.xml (under the Patron Records sub menu):
<item>
<display>
Patron Record Log Changes Report (cir-27)
</display> <file>p-cir-27</file>
</item>
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

10. Agenda Introduction Configuration Example
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

11. Example Here we have changed the name of global patron record 00000012
Added middle name “Samuel”
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

12. Example
Here we have changed the local patron status for record in LAW sub library
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach
Changed to

13. Example Here we have changed the email address
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

14. Example Here we have added a new ID
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

15. Example We can see the records in the Oracle table
select Z307_REC_KEY,Z307_TYPE,Z307_TEXT from Z307;
**** Hit return to continue ****
Update of global patron record-Details
Update of local patron record-Details
Update of patron addresses
New patron ID created
4 rows selected.
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

16. Example Now we run “Patron Record Log Changes Report (cir-27)”
Here we are retrieving all changes for all patrons made on Jan. 03, 2012
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

17. Example The job is running
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

18. Example The changes appear in the report
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach