Acquisitions API - Interested in user – add other identifiers in addition to Primary ID
Currently Alma allows multiple identifiers to identify ALMA Users, however the Acquisitions API (Interested In users) mapping only allows “primary_ID”.
We’d like any other identifiers used in Alma also be allowed in the mapping (e.g. Email Type). If this is added on the API parameter, staff can use the less sensitive info instead on vendor site.
Noting that adding other identifiers in the Interested_User api parameters - is only doing what EOD acquisition workflow/mapping can already do.
It is cumbersome for staff having need to search the requester’s primary id to be able to use this feature.
Ref #06652820 – Gobi Order API – interested_user - alma identifiers
paul wei
shared this idea
-
Jenifer Holman
commented
I was going to add a new idea when I found this one already posted. We have been beta testing the new Alma API integration with Mosaic and this limitation will cause several extra steps in our purchasing workflow. It seems odd that our old EOCR records actually give us more functionality than the API.