possible to include 866 data with holding policy?

Ex L

•  TBD

College/OCLS

•  Discuss extract options internally
•  Notify EXL of conclusions
•  See https://3.basecamp.com/3765443/buckets/23965261/messages/4567462052OCLS couldn’t extract Marc holdings, so we’ll enter this information manually after cutover

•  Yes
•  No

serial control/issues rejects

College/OCLS

•  See discussion at https://3.basecamp.com/3765443/buckets/23965261/messages/4605826169#__recording_4610562045
•  Review title references in serial control and issue extracts
•  Is there a more reliable bib link, rather than SERC_TITLE_KEY?
•  See bib/serial control linking requirements at https://knowledge.exlibrisgroup.com/Alma/Implementation_and_Migration/Migration_Guides_and_Tutorials/Symphony_to_Alma_Data_Delivery_and_Migration_Guide#Serial_Control_Record
•  See discussion Options for Failed Sirsi Serial Control/Issues RecordsWe will pick the option of using SERC_TITLE_KEYs as a matching point but ignore the leading letter. While SISAC_ID option is highly recommended, we found not all our serial records have SISAC_ID (373 against 416).

•  Yes
•  No

Holding Code not mapped on TL mig form; holdings given an UNASSIGNED location, and P2E titles not made electronic

College

•  Values from serial control mapped as HOLDING_CODE on Field Mapping Form will be listed in Column A of the Migration Form “Holding Code” tab
•  Ensure columns C and D on the “Holding Code” tab are populated with combinations of SIRSI home library location, from columns A/B of the “Alma Location” tab.

•  Yes
•  No

marked additional ID 2 as internal during test Load

Mark Barcode as internal

ExL

•  Mark Additional IS 2 internal if requested.
•  Mark Barcode as internal; this is already noted on the internal ExL tracking spreadsheet.

College

•  Confirm for Exl whether this should be repeated for Cutover
•  Refer to: https://3.basecamp.com/3765443/buckets/23965261/messages/4664833789#__recording_4723013180
•  Could you also mark Barcode field as internal AFTER cutover? We couldn’t sync this field through SIS anyway (the value is the same as primary ID)
•  Joy Wen (Unlicensed) , I have it in my notes to mark BARCODE as internal. --Andrea

•  Yes
•  No

TL funds extract was missing FY

College

•  IF submitting a funds extract for CO, ensure it includes funds for the current FY that is declared on the CO migration form.
•  Do not include the FY in fund codes for current FY. See https://3.basecamp.com/3765443/buckets/23965261/messages/4810954546#__recording_4813451642
•  We have set up a new fund structure in Alma and will not reload fund extract since those currently in Alma will retain for cutover.

•  Yes
•  No
•  

NOTES from Serial Control file records were not migrated to 852$x in Alma Holdings record.

ExL

•  Determined this was a bug in migration script that will be fixed for Cutover

College

•  Double-check that mapped serial control notes appear in the holding when data is delivered.
•  I’m more concerned with the subscription status of the serials. While this cannot be migrated, we will manually add this in Alma after cutover.

•  Yes
•  No

•  See my comment.

Preferred Name mapping (see TL Delivery Notes)

ExL

•  Amend baseline CO Field mapping form to remove “USER_NAME” from preferred name mapping

•  Yes
•  No

Base status mapping from 999$k resulted in many items in “Technical Migration” that didn’t need to be

ExL

•  Amend baseline migration form so that the default, for items with no 999$k, is that they are available/on shelf.

College

•  Do not change line 5 on the “Item BAse Status” tab of the migration form. Map all other rows as directed.

•  Yes
•  No

•  SERC_TITLE_KEY
•  SISAC_ID
•  OTHER:
•  I do need to identify specific parameters for SERC_TITLE_KEY or OTHER as described in the Backgrounder (OCLS and Ex Libris will follow up with you)
•  We will pick the option of using SERC_TITLE_KEYs as a matching point but ignore the leading letter. As mentioned here Options for Failed Sirsi Serial Control/Issues Records

From Andrea (5/4): Noted.

•  Map nothing (items inherit material types from bibs)
•  Map to same field as item type (usually Sirsi 999$t)
•  Map to 999$x

From Andrea (5/4): Done.

•  Courses & Reading List Headers
•  Ledgers and Funds
•  Licenses
•  COUNTER data
•  Will vendors be retained? We would like them to be retained.

From Andrea (5/4): Noted. And: Vendors are always retained.

PQIS Activations

•  I want PQIS at Cutover
•  I do NOT want PQIS at Cutover

Ebook Central Integration (Ebook Central Perpetual, DDA and Subscription)

•  I want E-Book Central Pro Integration (EBC) run at Cutover
•  I do NOT want EBC at Cutover

From Andrea (5/4): Noted.

•  Yes
•  No

From Andrea (5/4): Noted.

•  Yes
•  No

From Andrea (5/4): Noted.