Update Item Records (manage-63) Version 21.1 rep_change #002027 A21.1.5.6 - ELUNA - 2306 Andrea Hell

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

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

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

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

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-63 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

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

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

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

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

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

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

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

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

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.

Example ... and the Updated Items Report

Andrea.Hell@exlibrisgroup.com