Provenance code mapping

For the final load, you have the option to map a Millennium/Sierra Item record field (or bib record subfield) to the Alma item record provenance code field.  Note that there is no mapping on the Migration Form for the Provenance code field in Alma.  This means that if you want to map a III field to the provenance code field, any value that you wish to map to Alma need to exist in the Provenance code table already.  Note that the following values are currently populated in all CSU Provenance code tables. 

c - Cooperative or consortial purchase
d - Deposit
e - Exchange
f - Free
g - Gift
l - Legal deposit
m - Membership
n - Non-library purchase
p - Purchase
q - Lease
u - Unknown
z - Other method of acquisition

Let's say that you wanted to map the Millennium/Sierra ICODE2 value to the Provenance code field in Alma.  In your ICODE2 field, you have the values 'n', 's', and 'r'.  You map the ICODE2 field to the PROVENANCE_CODE field on the Items tab of the Field Mapping form, like below: 

In your Alma Provenance code table, you can add the values 's' and 'r' to the Provenance code table in Alma, so that these ICODE2 values map to your added 'r' and 's' Provenance codes.  Note that the ICODE2 'n' value will automatically map to 'Non-library purchase' because your current table already has the value 'n' contained within it. If you run into this situation and aren't sure how to handle it, feel free to contact Sarina.