Versions Compared

Old Version 33

changes.mady.by.user Corinna Baksik

Saved on

compared with

New Version Current

changes.mady.by.user Corinna Baksik

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt

Item Record fields - only required fields, or fields with best practices, are listed below

Tab: General Information
FieldRequired?Note
BarcodeYEnter the Harvard barcode for the item, or leave the barcode field blank to use a temporary system-generated barcode (will be created when the Item is saved)
Copy IDIf appl.
 

Material TypeYsee list at Item Material Types
Item policyYsee list at Item Policies 
Is Magnetic
 

see Best Practice: https://
wiki
harvardwiki.
harvard
atlassian.
edu
net/
confluence
wiki/x/
BwDKDQ
uRV_Aw
Enumeration A/BIf appl.e.g. multi-volume works or serials
Chronology I/JIf appl.e.g. multi-volume works or serials
DescriptionIf appl.

Generally this is left blank, unless the description is needed to distinguish items such as:

    • multi-volume works
    • serial volumes/issues
    • accompanying material that is barcoded separately

Do not use this field for:

    • copy numbers of duplicate items (e.g. you have 2 copies of the same book)
    • item policy
    • ownership information (e.g. "Widener copy")

For serials, once the Enum/Chron data has been filled in, use the Generate button to create the description.

Important information on the effect of the Description field in HOLLIS and Alma Fulfillment:

    • The presence of any content in the Description field turns off the Title-Level requesting feature, and turns ON the item filters in the Get It section:

Image Modified

    • When we have multiple copies and they are all the same, we want the Title-level requesting feature turned on so Alma can automatically push the request to the available copy. Therefore, to ensure that Title-Level requesting is enabled, item descriptions should be blank if all copies are the same.
    • If items represent different volumes/issues, item descriptions should not be null. This will allow the user to choose the specific item record they need.
Retention informationIf appl.see Best Practice: 

 

Tab: ENUM / CHRON
FieldRequired?Note
Enumeration A/BIf appl.This is carried over from the General tab. If entered here first it will carry over into the General tab.  
Permanent library/locationYInherited from Holdings
Tab: Notes
FieldRequired?Note
Internal Note 3N, but best practice is to add before withdrawalUsed to record reason for withdraw. See Items - Deleting (Withdrawing)
Statistics Note 2NRestricted to shared retention commitment notes. For example: 'committed to retain - ReCAP'. This note is required for all items where a commitment to retain has been made. Also required, field 538 with commitment statement in holdings.