[Bug 36887] New: Migrate "Authorized Values (BOR_NOTES)" into "Patrons (custom message)" in Notices
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36887 Bug ID: 36887 Summary: Migrate "Authorized Values (BOR_NOTES)" into "Patrons (custom message)" in Notices Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs@lists.koha-community.org Reporter: martin.renvoize@ptfs-europe.com QA Contact: testopia@bugs.koha-community.org CC: caroline.cyr-la-rose@inlibro.com, katrin.fischer@bsz-bw.de, testopia@bugs.koha-community.org Depends on: 29393, 36717, 32986 With the introduction of custom email messages in Bug 29393, we discussed (https://chat.koha-community.org/koha-community/pl/ixoy58im47dhpr4gmwtn9sdbjw) the opportunity to merge the "Patrons (custom slip)" notice type introduced in Bug 32986 and the new "Patrons (custom message)" notice type. We could also do away with the BOR_NOTES authorized value that is currently used for the non-email notes/messages and instead combine them into the above and use a checkbox for display options (staff or opac & email) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29393 [Bug 29393] Ability to send emails from patron details page https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32986 [Bug 32986] Add ability to generate custom slips for patrons https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36717 [Bug 36717] Merge "Patrons (custom slip)" and "Patrons (custom message)" in Notices -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36887 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|36717 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36717 [Bug 36717] Merge "Patrons (custom slip)" and "Patrons (custom message)" in Notices -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36887 Martin Renvoize <martin.renvoize@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|32986 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32986 [Bug 32986] Add ability to generate custom slips for patrons -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36887 Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=36717 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36887 --- Comment #1 from Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> --- Is this a duplicate of Bug 36717 or a different thing? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36887 Cheryl <clackman@fargolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clackman@fargolibrary.org -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36887 Benjamin Daeuber <bdaeuber@cityoffargo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bdaeuber@cityoffargo.com --- Comment #2 from Benjamin Daeuber <bdaeuber@cityoffargo.com> --- What does the workflow look like here? As an example, right now we have a BOR_NOTE that puts a message on the patron card that they brought back an item missing a disc. So the staff person picks the note from the dropdown that says "Item mixup at <Branch>:" then they type in the title of the item. Would your suggestion keep that workflow, or would it behave differently? Also, presumably this would allow us to send an email at the same time, so we can let the patron know they need to get us the disc. Would it be the same note, or would different "transport types" (if that's the term for a staff note), generate different messages like notices do now (so we could send a more detailed message to the user)? My other concern is ensuring that no accidental emails are sent. I never want someone to accidentally click "email" on a message that should be staff only. The nice thing about the current setup is that it doesn't allow accidental OPAC notes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36887 --- Comment #3 from Benjamin Daeuber <bdaeuber@cityoffargo.com> --- We'd also need to consider what happens if the user doesn't have an email. I don't like the idea of rolling these into print notices. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36887 --- Comment #4 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- (In reply to Caroline Cyr La Rose from comment #1)
Is this a duplicate of Bug 36717 or a different thing?
Not a duplicate but a parallel.. The other one is about merging two 'message templates' into one template with two message transport types.. This one is about migrating the authorized value into notices so you get the additional functionality that notice templates offer (i.e access to template toolkit tooling with variable replacements and no longer a hidden hard coded limit of 200 characters). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36887 --- Comment #5 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- (In reply to Benjamin Daeuber from comment #3)
We'd also need to consider what happens if the user doesn't have an email. I don't like the idea of rolling these into print notices.
This is just a proposal to get the discussion rolling. I don't have any sponsorship at this time to proceed with anything as yet. I think we can certainly ratify this area, perhaps introduce another transport type for 'display in browser' messaging or something along those lines.. Either way.. I don't want to reduce the functionality but rather clarify it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36887 Bug 36887 depends on bug 29393, which changed state. Bug 29393 Summary: Ability to send emails from patron details page https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29393 What |Removed |Added ---------------------------------------------------------------------------- Status|Needs documenting |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36887 Lisette Scheer <lisette@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisette@bywatersolutions.co | |m --- Comment #6 from Lisette Scheer <lisette@bywatersolutions.com> --- I think this is a great idea. You could say something like "Item mixup at [% loggedinbranch %]" and have it autofill. Even better if down the line we could check a box/select from the item to have all the item information autopopulate as well. Additionally we can already send e-mails through there, this would just be a more useful way, you could add the message + send the corresponding email and not put anything in the e-mail field if it was staff only. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org