http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5632 Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |olli-antti.kivilahti@jns.fi --- Comment #7 from Olli-Antti Kivilahti <olli-antti.kivilahti@jns.fi> --- Hi there! I went through the whole SIP2.0 manual from 3M and I got 15 instances of date-use using the SIP::timestamp and 3 usages with no definition (optional) of the timeformat (see down). All undefined usages are using the AH-field. <SNIP> 2.00 Item Information Response due date AH variable-length optional field. 2.00 Renew Response due date AH variable-length required field Checkout Response due date AH variable-length required field 2.00 Hold Response 2.00 expiration date BW 18-char, fixed-length optional field: YYYYMMDDZZZZHHMMSS </SNAP> I think one can strongly infer from the documentation that using the established timeformat (the SIP-format) is supposed to be used. The SIP-device vendor anyway should format the date to be displayed per configuration. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.