Question

What needs to be configured in order to properly display MAB holding information in Primo interface?

Answer

As Primo is expecting holding data in USM format, MAB customers should perform conversion between MAB holding information and USM format in XXX60.

Example setup from customer server:

xxx60/tab/tab_expand:
HOL-LOC fix_doc_convit FILE=tab_fix_mab2usmhol

xxx60/tab/tab_fixmab2usmhol:
! 1 2 3 4 5
!!!!!-!-!!!!!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!>
200 a 86630 a
200 b 86630 a edit_field MERGE-I,SORT=ab
200 c 86630 x edit_field PREFIX="[L?ckenangabe: ",SUFFIX="]"
200 d 86630 x edit_field MERGE-I,SORT=cd
200 e 86630 z edit_field PREFIX="Kommentar: "
200 f 8521 c
200 g 8522 b edit_field PREFIX="Standort: "
200 h 8522 c
200 k 8521 z
OWN a 8521 b edit_field MERGE-I,SORT=bc
##### #####

(Table tab_fixmab2usmhol is a new table. You may copy $mab01_dev/mab01/tab/tab_fix_mab2usm to ./xxx60/tab to have an example for the structure of the table.)



Note: The following fix should be installed for full functionality (rep_change #003816 in Aleph 20, rep_change #002295 in Aleph 21):

---------------------------------------------------------
Description: RESTful API - In a MAB environment, the holdings API does not work properly when there is no sublibrary parameter in the URL. In such cases, the holdings API should retrieve all of the holdings.

Solution: This has been corrected.
---------------------------------------------------------

Category: Interoperability (500)

Subject: Primo

• Article last edited: 15-July-2015