1) Category 1     2) Category 2    3) Current Location    4) Home Location     5) Item Type

• Often the requestor of the move will give call number range to move, current location of the items, and the location the items are being moved to.

• ITS has to use the selitemprt report to carefully select the correct items being moved based on call number range and selecting the HOME location of the items (where they are sitting NOW). DO NOT USE CURRENT LOCATION only, since the current location can be "CHECKEDOUT", if the items circulate.

• Careful with location selection, did the requestor get all the locations listed? With the move of items to 9LTR from 3LT-TEMP and 2LB-REF, ITS had to check for items in 3LT_TEMP and 3LT-TEMP_ and 2LB-REFDSK as well, the requestor agreed that these needed to be checked even though they were not listed on the original request.

• The selprtcallitem report will generate a file of item keys and barcodes of selected items in the /s/sirsi/Unicorn/Rptcustom/Run directory.

• This file of item keys is VERY useful to do some additional steps of analysis:
  • What are the ITEM TYPES of the selected items? cat file | selitem -iI -otIS > itemck

  • Review the results of the ITEM TYPE in case you need to suggest to the requestor that the items being moved may need their ITEM TYPE "fixed" globally as well as the location. For example, when items were moved from 3LT-TEMP and 2LB-REF up to 9LTR, all those items which have DEFINITE in the ITEM TYPE had to be changed to LIBONLY but the cases of PERIODICAL or SEP-RECORD item types had to be left UNCHANGED!

  • Pre-Dec. 2003 one had to run the 866.locnchange.ksh program found in /Work/NDL in order to get some reports. Run as in: 866.locnchange.ksh OUTPUT_FILENAME OLD_LOCN NEW_LOCN. But now the selitemedit program will do the 852 and 866 fixes automatically using edimarc.
    • ckeys which have an 852|c location from the old location code which Cataloguers need to clean up
    • ckeys which have an 866 location subfield (DOBIS loaded 866 tags) carrying the old location code which again, Cataloguers need to clean up
    • Corrections are vital especially for RELAIS's proper functioning!

• Run the selitemedit report when you have tested all the steps on the test server first and are sure things are being done to the requestors specifications. Seledititem report will use the file of itemkeys in /s/sirsi/Unicorn/Rptcustom/Run and will feed them into Sirsi's edititem tool.

• Only ONE item feature can be changed per run of selitemedit reports, so if you need to change HOME LOCATION (which also changes the CURRENT LOCATION at the same time--unless current=CHECKEDOUT), and ITEM TYPE, two runs of the report are required. For the two runs of the edit report, you may use the same or perhaps different /s/sirsi/Unicorn/Rptcustom/Run/fileX files.