| 2015-10-27 15:41:18 |
Dan Wells |
description |
* Evergreen master
We had a local request to add call number and location information to records emailed from the TPAC. Doing so is possible, but it involves duplicating a lot of display logic from misc_util.tt2.
Right now, Action Trigger stores all of its templates in the DB, while the OPAC templates are in the filesystem. From what I have seen so far, they are not easily shared. Some possible steps which would bring these areas together might include:
1) Implement a common INCLUDE_PATH. If the Template processors for each service knew where to look, it should be possible to even use filesystem templates (or template fragments) within the DB templates (e.g. using PROCESS).
2) Create a shared library of template/display functions. Right now, Action Trigger has a collection of "helpers", while TPAC hangs some methods on the 'ctx' object. We may want to abstract these out such that they could be attached to an object used in either environment.
Discussions relating to slightly different angles on this bug are also in progress on #1407504 and #1347774. |
* Evergreen master
We had a local request to add call number and location information to records emailed from the TPAC. Doing so is possible, but it involves duplicating a lot of display logic from misc_util.tt2.
Right now, Action Trigger stores all of its templates in the DB, while the OPAC templates are in the filesystem. From what I have seen so far, they are not easily shared. Some possible steps which would bring these areas together might include:
1) Implement a common INCLUDE_PATH. If the Template processors for each service knew where to look, it should be possible to even use filesystem templates (or template fragments) within the DB templates (e.g. using PROCESS).
2) Create a shared library of template/display functions. Right now, Action Trigger has a collection of "helpers", while TPAC hangs some methods on the 'ctx' object. We may want to abstract these out such that they could be attached to an object used in either environment.
Discussions relating to slightly different angles on this bug are also in progress on bug #1407504 and bug #1347774. |
|
