With AllowCheckoutNotes enabled there is a column labelled 'Note' in the checkouts table in the OPAC. Once you enter a note and submit it tells you that your note has been sent to the library. I believe that this will come as a surprise to quite a lof of people as the column doesn't indicate in any way that it's not a personal notes field but supposed to be used to communicate issues to the library. We should rephrase the table heading and maybe add a hint about what this is supposed to be used for.
I agree that the "Note" column isn't very descriptive to patrons. I use jQuery to relabel the column as "Report a problem with this item."
Thx for the suggestion George! Do you think we could agree on this change?
This suggestion seems clear enough to me, thank you George !
I agree and I know that at least a couple of other libraries are using jQuery to make the same or a similar change.
Created attachment 111944 [details] [review] Bug 26526: Relabel checkout note column in OPAC When checkout notes are active, there is currently a new column labelled 'Note' in the checkouts table in OPAC. When a note is added, this is sent to the library. For the user it's not clear from the label, that these notes are not personal, but for reporting to the library. The new label "Report a problem" aims to make this clearer. To test: - Turn on AllowCheckoutNotes system preference - Check out some items to your account - Go to the OPAC - Look at the list of checkouts - Apply patch - Reload the page and check the checkouts table again - Verify the heading has changed from "Notes" to "Report a problem" - Hover over the heading with your cursor to see some more info Bonus: Patch adds an id "checkout-notes" to the header cell, that will make it easier for libraries to change text or style if needed.
Created attachment 111950 [details] [review] Bug 26526: Relabel checkout note column in OPAC When checkout notes are active, there is currently a new column labelled 'Note' in the checkouts table in OPAC. When a note is added, this is sent to the library. For the user it's not clear from the label, that these notes are not personal, but for reporting to the library. The new label "Report a problem" aims to make this clearer. To test: - Turn on AllowCheckoutNotes system preference - Check out some items to your account - Go to the OPAC - Look at the list of checkouts - Apply patch - Reload the page and check the checkouts table again - Verify the heading has changed from "Notes" to "Report a problem" - Hover over the heading with your cursor to see some more info Bonus: Patch adds an id "checkout-notes" to the header cell, that will make it easier for libraries to change text or style if needed. Signed-off-by: Barbara Johnson <barbara.johnson@bedfordtx.gov>
Worked great!
Created attachment 112108 [details] [review] Bug 26526: Relabel checkout note column in OPAC When checkout notes are active, there is currently a new column labelled 'Note' in the checkouts table in OPAC. When a note is added, this is sent to the library. For the user it's not clear from the label, that these notes are not personal, but for reporting to the library. The new label "Report a problem" aims to make this clearer. To test: - Turn on AllowCheckoutNotes system preference - Check out some items to your account - Go to the OPAC - Look at the list of checkouts - Apply patch - Reload the page and check the checkouts table again - Verify the heading has changed from "Notes" to "Report a problem" - Hover over the heading with your cursor to see some more info Bonus: Patch adds an id "checkout-notes" to the header cell, that will make it easier for libraries to change text or style if needed. Signed-off-by: Barbara Johnson <barbara.johnson@bedfordtx.gov> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
This is a genuine improvement that clarifies the feature.. nice work. Passing QA Side Note; I wonder if at some point we should merge the results of these problem reports into the general problem reports UI recently introduced by Aliesha.
Pushed to master for 20.11, thanks to everybody involved!
backported to 20.05.x for 20.05.06
enhancement, not backported to 19.11.x