New endpoint for vendor fund mapping (910$d to 980$h)

[cappadona]

Need

When processing submitted MARC order files, the Lehigh App will lookup and replace vendor fund codes in the 910$d of incoming records with the corresponding local fund code, adding it to the 980$h of the processed record. This service will be needed outside and beyond the limited life of the Lehigh App, so the decision was made to add it as an external dependency instead of embedding it within.

Draft Proposal

Endpoint

/vendor-funds

Query params

Both optional but if neither are included in request, return HTTP 400: Bad Request

• code: Vendor fund code to lookup
• local-code: Local fund code to lookup

Returns

corresponding local or vendor fund code

Fund mapping will be managed via flat CSV in the repo.

Background

Vendor print loads in LSTools (aka VPRs) have an initial processing step where the vendor fund in the 910$d is mapped to a local fund (via DB lookup) and then the resulting local fund is added to the 980$h. This new endpoint would facilitate the vendor to local fund lookup. The current VENDOR_FUND table of the lstools DB has 60 rows and 3 applicable columns:

• vendor_fund
• local_fund
• location

• General Spec for Vendor Print loads
• Current fund mapping logic from cul-it/batch-apps/shared-perl/prodproc/vendor_print.pl