https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43674
--- Comment #9 from Pedro Amorim (ammopt) <[email protected]> --- (In reply to Phan Quang Minh from comment #6) > 1. Timestamp format. Koha emits <timestamp>2026-09-30 10:23:41</timestamp> > and > <lastChange> likewise — a space instead of T, no timezone. That is not a > valid > xs:dateTime, and unlike element order it genuinely stops a parser: our > deserialiser > throws on it, and XSD validation rejects it. This is the one remaining > defect that > actually blocks the exchange. Already reported against the plugin at > https://github.com/openfifth/koha-ill-iso18626/issues/7, but > Koha/ILL/ISO18626/Request.pm > has the same problem in core. > > 2. Agency identifiers. Core still sends supplyingAgencyId = > 'sup_agency_value' and > requestingAgencyId = 'req_agency_value' (Koha/ILL/ISO18626/Request.pm > lines 352, 359). > We cannot match an incoming supplyingAgencyMessage to a partner, so we > fall back to > matching on requestingAgencyRequestId alone — which means we cannot > verify who sent > it. See my earlier comment on this bug. Thank you Phan. Please file a bug for each of these issues. My suggestion: rescope bug 43694 to the datetime issue. File a new bug for the req_agency_value/sup_agency_value issue. Let's keep testing and discussion here about the ISO18626 envelope. Thank you. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list -- [email protected] To unsubscribe send an email to [email protected] website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
