One column in an Analytics output should display the contents of the marc 500 field for each bib record. How do I get Analytics to include this?
You can add Local Param fields to analytics, it will allow you to enrich the bibliographic information exported to Analytics with additional information stored in MARC 9XX local fields in Alma
Since it is only possible to add 9xx field as local params, I would like to suggest you to copy the information to one of the 9xx bib fields .
PROBLEM: You want field 500 to be evaluable in Analytics.
SOLUTION: You can use the "Local Param" fields in the "Bibliographic Details" dimension in Analytics. (See explanation in Alma Analytics Guide in the "Bibliographic Details" chapter.) But since these fields can only be used for 9xx fields, first you need to copy the 500 content to a 9xx field of your choice.
This is how it works:
1. Define a new normalization rule. The syntax of normalization rules is explained in the Alma Resource Management Guide, chapter "Working with Normalization Rules". This could be an example for your rule:
rule "copy 500 Field to 901 Field"
copyField "500" to "901"
You may of course change this rule according to your needs by restricting it to subfields or choosing another field than 901.
2. Save and test the normalization rule. ALWAYS test a normalization rule before running it as a process! You find more information about testing a normalization routine in the document "Using Normalization Rules" which you can access from the doc portal (path Alma - Product Documentation - Resource Management - How To Documents and Presentations).
3. Add the new rule as a process. You do this via Resource Management Configuration / Cataloging / Metadata Configuration / MARC21 Bibliographic / Normalization / Add Process.
(This is also described in detail in the above-mentioned document.)
4. Now you can run the normalization process. You can run it from the menu of the metadata editor, or on a set using the "Run Process" option, or in an import routine, or when copying an external resource. All this you find described in the "Using Normalization Routines" document.
5. In order to make the new field evaluable in Alma, Ex Libris Support needs to add the definition to the system that "Local Param1" should be used for 9xx. In order to do so, please tell us the three-digit field code (e.g. 901), and we will be happy to set this up for you. (You may also tell us now, even before performing steps 1 to 4, then there won't be an additional delay.)
6. Once the ETL has run, the "Local Param1" will contain the content of field 9xx and can be evaluated in Analytics.
- Article last edited: 20-Feb-2017