1. Update Item Records (manage-63)
Version 21.1 rep_change #002027
A ELUNA
Andrea Hell

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 batch service is now introduced: Advance update item records (manage-63). This batch service allows updating a larger amount of item fields than manage-62.
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

4. Introduction
Description: Update Item Records (manage-62) service supports updating of limited number of item fields.
Solution: A new batch service is now introduced: Advance update item records (manage-63). This batch service allows updating a larger amount of item fields.
The new fields are:
Item call no. 1 type
Item call no. 2 type
OPAC note
CIRC note
Internal note
Item statistic
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

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

6. Configuration
1) If localization is required, add the following lines to ./alephe/pc_b_lng/menu-circ.xml:
<item>
<display>Advanced Update Item Records (manage-63)</display>
<file>p-manage-63</file>
</item>
2) Add new line to alephe/tab/user_function.lng:
 ITEM-UPDATE-S L Item Updates Services MANAGE L MANAGE-63 Advanced update item records
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

7. Configuration
3) Add new lines into <ADM library>/tab/pc_tab_exp_field.lng
P-MANAGE L Sub-library SUBLI
P-MANAGE L Material type MATER
P-MANAGE L Item status STATU
P-MANAGE L Item collection COLLE
P-MANAGE L Item call no LOC1
P-MANAGE L Item call no.1 type LOC1T
P-MANAGE L Item call no LOC2
P-MANAGE L Item call no.2 type LOC2T
P-MANAGE L Order number ORDNO
P-MANAGE L Subscription number SUBSN
P-MANAGE L Arrival date ADATE
P-MANAGE L Item process St PSTAT
P-MANAGE L Item year (first level of chronology) YEAR
P-MANAGE L Remote Storage ID DEPOS
P-MANAGE L OPAC note ONOTE
P-MANAGE L CIRC note CNOTE
P-MANAGE L Internal note INOTE
P-MANAGE L Item statistic ISTAT
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

8. Configuration <BIB library>/form_lng/updated-items-report.xsl
4) Add new xsl files
<BIB library>/form_lng/updated-items-report.xsl
<BIB library>/form_lng/rejected-items-report.xsl
5) If localization is required, add: $alephe_root/error_lng/p_manage_63
6) Run util/I/6

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

10. Example
For some items in sub-library WID we want to delete call-number type 4 AND change item status from 92 to 01
Sample record:
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

11. Example This is the input file for p_manage_63 $alephe_scratch/items
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

12. Example
If we try to perform our modification with manage_62 it is not possible as the field „Call no. 1 type“ can‘t be handled

13. Example
We run manage_63 and change/delete the item call no. 1 type and item status
ZZ is added to indicate that the field content will be changed to „blank“
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

14. Example
In the batch log we can see that 2 records were rejected and 4 records were updated
Unlike our competitors, we did not release a new revolutionized system every few years but rather took the evolutionary approach

15. Example
In the file list section in task manager we see the „Rejected Items Report“ ...
These items were rejected because they are on loan and parameter CHANGE-ITM-STS-LOAN=N is set in tab100 which means that changing an item status for an item on loan is avoided.

16. Example
... and the Updated Items Report