Tagged: itemized sets, job, PO Line
My institution would like to perform batch actions on PO lines created by an import job. The job ID is given, which I use to call this API endpoint (JSON type):
https://api-ca.hosted.exlibrisgroup.com/almaws/v1/conf/jobs/ALL/instances/xxxxxxxxxxxxxxxxx
The result looked promising at first, containing this entry:
{ “type”: { “value”: “CREATE_SET”, “desc”: null }, “population”: { “value”: “IMPORTED_PO_LINES”, “desc”: “Total PO lines imported” }, “members”: 19, “link”: “https://api-ca.hosted.exlibrisgroup.com/almaws/v1/conf/sets?population=IMPORTED_PO_LINES&job_instance_id=xxxxxxxxxxxxxxxxx” },
But when I visited that https://api-ca.hosted.exlibrisgroup.com/almaws/v1/conf/sets?population=IMPORTED_PO_LINES&job_instance_id=xxxxxxxxxxxxxxxxx URL, the “population” and “job_instance_id” parameters both seem to be disregarded, and the result just listed every set that exists instead of those pertaining to the job.
Is there another endpoint I have missed that should be called instead?
The API would be POST (to create a set) and not GET. Please try following this blog post: https://developers.exlibrisgroup.com/blog/creating-sets-from-md-import-job-results-using-alma-api/ Thanks, Ori
