|Summary:||Re-engineer Talking Tech support in Koha|
|Product:||Koha||Reporter:||Kyle M Hall <kyle.m.hall>|
|Component:||Notices||Assignee:||Kyle M Hall <kyle.m.hall>|
|Status:||CLOSED INVALID||QA Contact:||Testopia <testopia>|
|Priority:||P5 - low||CC:||kyle, sally.healey|
|Change sponsored?:||---||Patch complexity:||---|
|Documentation contact:||Documentation submission:|
|Text to go in the release notes:||Version(s) released in:|
Description Kyle M Hall 2015-08-31 12:16:16 UTC
Right now Talking Tech support within Koha works, but does not integrate well with the existing messaging system. I would propose we re-engineer Talking Tech by doing the following: 1) Remove all the exceptions that hide/modify the use of the 'phone' notice so that it is once again treated like any other type of notice. 2) Define the 'phone' notice for a given action as the line that is created in the CSV file 3) Have the outbound cron script for Talking Tech gather these notices together into a CSV file, rather than having it generate the notices and CSV file itself. This will end with a much cleaner implementation of Talking Tech that could easily be used for other phone automation systems as well!
Comment 1 Kyle M Hall 2016-03-01 14:51:22 UTC
This course of action would result in the loss of functionality. I will have to find an alternative approach.