Versions Compared

Key

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


(warning)  Update:  From the January 2019 Release Sneak Preview

  • Bibliographic/Holdings Local Fields to Be Exported to Analytics – It will be possible to define any bibliographic field, and not only a 9XX field, to be exported to Analytics.


CSU campuses need to configure their local fields to be mapped for analytics (LOCAL PARAMS = 9xx fields; up to five can be mapped by EL for use in analytics).

Each campus will need to submit a Salesforce case (see: https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/Add_bibliographic_fields_to_Alma_Analytics)

...

Each campus must select five 9xx fields to be mapped to Alma Analytics. Fields 958, 962-969, and 972  are reserved for local institution-defined internal notes. Any CSU library is free to define any of these fields for local use. These local internal note fields do not publish to Primo. Please see Local Fields in Alma & Primo.

There is no deadline for submitting this request to ExLibris. However, determining which fields will be used in Analytics may impact the set up of Import Profiles, data clean-up projects, or other workflow. Also note: ExLibris may take up to 2 weeks to execute this configuration change.  Please also note that while it is possible to change the designated fields later via a new SalesForce case, Ex Libris strongly discourages it, as it is a complex process and may cause unintended issues. Recommended timeline: Before Go-Live or soon thereafter.

...