Acquisitions Data Tasks

UPDATE 1/23/24: Data tasks have moved to a consolidated list, so this page is no longer being updated. See https://duke.atlassian.net/l/cp/uB1nC90B

Purpose: The purpose of this page is to track specific data-related tasks related to the Alma Implementation.

This is a draft list - not in priority order.

#	Topic/Task	Description	Next Steps
1	Add Aleph data elements as an Alma note record.	Some Aleph data elements won't migrate or they crosswalk to new values and we need to determine which are important enough to add as a note on a budget, vendor, order, or invoice for reference. Ex: Aleph order material type doesn't migrate, Aleph invoice types REG and INT will both crosswalk to Accounting Department.	Create comprehensive list of data elements (see list below on this page). Determine preferred format - does each get loaded as a separate note or concatenated into one string as an Aleph migration note. Add to list of DST projects so the work can be prioritized
2	Blank Subscription Renewal date values	Determine whether any cleanup is needed.	Pull the list of orders. https://duke.box.com/s/4gmuzn8s7zwebn1iyt89tukl8j1b4ied Review
3	SU order status and XXX status cleanup
4	Update Renewal dates - the migration process doesn't look at the order and that's our source of truth.	Need to flip these dates via API after migration	Add to list of DST projects so the work can be prioritized

Vendor

Budget

Order

Acquisition method
Material type
Order/subscription log
Order Status - we mapped deprecated values to different values in Alma - do we need to preserve the Aleph value on a note?

Invoice

Other

Libraries