Question about behavior of SIP AF Screen Message information
Our Company provides self service software and related products for libraries. We are working with a customer where an unusual situation has occurred and need to understand whether the environment is representative of Koha typical behavior, a problem with a particular release or unique to this customer because it is not something we have seen with other systems nor have any of our Koha users reported problems. We are attempting to help this Koha customer solve a problem. The protocol document describes the use of the screen message (AF) field as text for display to a borrower, typically informative information related to blocks or other reasons why a patron cannot circulate an item. We use AF information to set rules for access to computers and of course for self check out and we display the contents of the AF field to the borrower. Often the text in AF is consistent for given conditions so that the contents are predictable. In this customer's environment there are unique, manually created one-off messages that are obviously intended to be seen only by staff (circulation type information that is not appropriate for a patron to see) embedded in some very lengthy AF fields in the SIP response. It appears that the field is continuously appended with patron-facing and staff-facing text, making the strings quite long and unpredictable. Any insight into this will be appreciated. Thanks Mike Monk EnvisionWare, Inc.
* Mike Monk (mmonk@envisionware.com) wrote: Hi Mike
Our Company provides self service software and related products for libraries. We are working with a customer where an unusual situation has occurred and need to understand whether the environment is representative of Koha typical behavior, a problem with a particular release or unique to this customer because it is not something we have seen with other systems nor have any of our Koha users reported problems. We are attempting to help this Koha customer solve a problem.
What version of Koha are they running?
The protocol document describes the use of the screen message (AF) field as text for display to a borrower, typically informative information related to blocks or other reasons why a patron cannot circulate an item. We use AF information to set rules for access to computers and of course for self check out and we display the contents of the AF field to the borrower. Often the text in AF is consistent for given conditions so that the contents are predictable.
In this customer's environment there are unique, manually created one-off messages that are obviously intended to be seen only by staff (circulation type information that is not appropriate for a patron to see) embedded in some very lengthy AF fields in the SIP response. It appears that the field is continuously appended with patron-facing and staff-facing text, making the strings quite long and unpredictable.
Do you know how they are creating these messages and what field they are storing them in, in Koha? Chris
Any insight into this will be appreciated.
Thanks
Mike
_______________________________________________ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
Chris Thank you for your response. The version is 3.01.00.032 The user is typing information into two fields on the Modify Patron Screen Under the Library set-up section, there are fields for Registration Date, Expiry Date, OPAC Note and Circulation Note. In Circulation Note there is text that says: MESSAGES: This is a test....... My understanding is that the library wants these 'Circulation Notes' to be visible to staff on the staff circ screen during check out. These notes contain information that is not suitable for patrons. These messages are displaying to patrons because they are delivered via the AF field in SIP. So on a self service station the text displays as follows: "Greetings from Koha." <text from OPAC note: "Please see staff."> <text from CIRCULATION note: "MESSAGES: Don't let this ..."> In some cases the combined strings are 3-4 times the 'typical' length of a 64. Mike On Dec 20, 2011, at 1:47 AM, Chris Cormack wrote:
* Mike Monk (mmonk@envisionware.com) wrote:
Hi Mike
Our Company provides self service software and related products for libraries. We are working with a customer where an unusual situation has occurred and need to understand whether the environment is representative of Koha typical behavior, a problem with a particular release or unique to this customer because it is not something we have seen with other systems nor have any of our Koha users reported problems. We are attempting to help this Koha customer solve a problem.
What version of Koha are they running?
The protocol document describes the use of the screen message (AF) field as text for display to a borrower, typically informative information related to blocks or other reasons why a patron cannot circulate an item. We use AF information to set rules for access to computers and of course for self check out and we display the contents of the AF field to the borrower. Often the text in AF is consistent for given conditions so that the contents are predictable.
In this customer's environment there are unique, manually created one-off messages that are obviously intended to be seen only by staff (circulation type information that is not appropriate for a patron to see) embedded in some very lengthy AF fields in the SIP response. It appears that the field is continuously appended with patron-facing and staff-facing text, making the strings quite long and unpredictable.
Do you know how they are creating these messages and what field they are storing them in, in Koha?
Chris
Any insight into this will be appreciated.
Thanks
Mike
_______________________________________________ > Koha-devel mailing list > Koha-devel@lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
participants (2)
-
Chris Cormack -
Mike Monk