-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to query Message Alert entity as regards delivery status #139
Comments
The reason that we associated delivery status with the Patron rather than with the Message/Alert is that the delivery status for a specific Message/Alert could vary from Patron to Patron. If there is a requirement to anonymise the message delivery status information, i.e. to disassociate it from identifiable Patrons, we would have to add some properties to the Message/Alert entity to allow it to carry aggregated delivery status information. But there are a number of ways this might be done, e.g. absolute numbers of Patrons, percentages, or broader, vaguer categories. |
At the Technical Panel meeting on 27/02/2019 we agreed that some detailed work is needed to add this feature, with particular attention to the status of messages sent to multiple patrons. |
Code list MAD defines three delivery status codes:
These are currently employed when querying a Patron entity/record, and indicate the status of a specific message/alert associated with that Patron. A Message/alert entity can be associated with one or more Patrons, one or more Patron categories. To fully communicate the delivery status of a specific message/alert, the following would need to be communicated:
The overall structure could be something like the following:
A minimal implementation of this enhancement would be to implement composite E15C16 and just two of its sub-elements: E15D16.1 and E15D16.2. This would provide some vague information about the number of Patrons who have received the message/alert and how many of those have acknowledged receipt. There is only any point in implementing E15C16.3 and E15C16.4 if the delivery status information for each Patron or Patron category is to be included in the Message/alert record. Otherwise, the terminal might as well retrieve the information by selecting Patron records associated with the message/alert and retrieving the delivery status in each case. This could be done by requesting a list of all Patron entities that are associated with a specific Message/alert entity, and arranging for a set of partial Patron records to be embedded in the response. In summary, there are two ways to resolve this issue:
|
The Technical Editors discussed this briefly. What is proposed probably contains more information - and more duplicate information that can be retrieved from Patron records - than is needed. A suggestion would be to modify the proposal to remove E15D16.3.2 Delivery status and the whole of E15D16.4.5. But in that case E15D16.3.1 simply duplicates E15D11, which would mean that E15D16.3 is redundant. A simpler structure would therefore be:
The disadvantage with this simpler structure is that the delivery status information is only available in aggregated form. To determine whether a message/alert has been delivered to a particular Patron, it will still be necessary to retrieve the Patron record. |
To handle the cases where messages are sent to Patrons related to specified Loans or Reservations (message/alert audience code values '03' or '04'), the above could be extended as follows:
A single composite is all that is needed, since the message/alert audience cannot be both '03' and '04'. |
See issue #139. Added E15C16 Delivery information.
Message delivery status is a property of the Patron entity, so it is not possible to query the delivery status by accessing the Message\Alert entity (for example if the message has been sent to via Patron Category)
The text was updated successfully, but these errors were encountered: