...
Note that anything that is in the CALL #(ITEM) field will override all other call number fields. The CALL #(ITEM) field and the CALL #(BIBLIO) fields never retain the $h and $i upon export from Millennium and Sierra. If it is important to retain these subfields, you can choose not to export CALL #(ITEM) or CALL #(BIBLIO) at all.
If If you do wish to include the CALL#(ITEM) field, you may do so, but turn off the setting under Settings | Create Lists | "Look up call numbers". Leaving this setting on will cause you should consider listing it as the last call number field option on your Field Mapping form. In the example below, instead of placing it in the CALL #(ITEM) field to be fully populated, and will subsequently override all other call number fields with a call number that does not contain the $h and $i subfields. column, you could place it in call_field_7. This will ensure that the CALL #(ITEM) column is used only when all MARC call number fields are empty. If it is important to retain the $i in the holdings call number, I would suggest not exporting the either listing CALL #(ITEM) field from Sierra/Millenniumlast on your Field Mapping form, or not including it on your Field Mapping form.
This is what my Field Mapping form looks like for the situation outlined above. Note that I am not including the CALL #(ITEM) field at all. My modified headings '090|abitem', '050|abitem' and '086|abcditem' are listed before the bib record call number MARC fields, because I want the item call number fields to take precedence. If you wish for the bib record call number fields to take precedence, you would list the corresponding MARC fields for the bib record call numbers first.
This is what a successfully migrated call number looks like in Alma after taking this approach.
