Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Acq loader - inconsistent behavior acq loader - strange behaviour 0

    • Article Type: General
    • Product: Verde
    • Product Version: 2

    Description:
    Acquisitions loader from Aleph (available through Admin / Initial / Load Acquisitions):

    The match for the Acquisition record can be done by one of two fields: Acquisition number (input field acquisitionNumber) or Purchase Order Number (input field orderNumber).

    When the match is found by acquisitionNumber and multiple acquisitions are found, the process takes the first with status ACTIVE and the matching subscription dates (the assumption is that since the Acquisition No. is a system generated identifier and can not be entered manually, if there are multiple acquisition records with the same Acquisition No., they apparently refer to the same Acquisition which has been renewed).

    However, when the acquisitionNumber is empty and the match is found by orderNumber and multiple acquisitions are found, the process rejects the whole record with error "multiple match for Acquisition record with OrderNumber=..." (the assumption is that since the Order number can be entered manually, in case the same Order Number was entered into more than one Acquisition, it is ambiguous which of these multiple acquisitions should be updated and therefore the update is rejected).

    The current algorithm leads to an incorrect situation in the following case: if a Purchase Order No. was properly entered to a single Acquisition, and this record was renewed, both the Acquisition No. and the Purchase Order No. are identical for the old and the new acquisition records (in other words, there are multiple acquisition records in the system having the same Purchase Order No.- these acquisition records refer to the same Acquisition). In this case, when using the loader to locate the Acquisition by Purchase Order Number, it is incorrect to reject the update (in this case the behavior should be consistent for both cases - no matter which field is used as a matching point).

    The process should be fixed as follows: when multiple acquisitions are found by matching orderNumber, it should be checked whether all the multiple acquisition records have the same Acquisition No. (refer to the same Acquisition). If this is the case, the process should take the first acquisition with status ACTIVE and the matching subscription dates like it does if the match is found by Acquisition No.

    Resolution:


    • Article last edited: 10/8/2013
    //Feedback