Bug 15279 - Deprecate bespoke syntax for Slips and Notices
Summary: Deprecate bespoke syntax for Slips and Notices
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: unspecified
Hardware: All All
: P1 - high enhancement with 11 votes (vote)
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on: 15277 15278 34472
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-02 13:13 UTC by Kyle M Hall
Modified: 2023-12-20 13:56 UTC (History)
8 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall 2015-12-02 13:13:39 UTC
Once Template Toolkit syntax for Slips and Notices has gotten to the point where it can fully replace our bespoke format, we should deprecate and remove the old format.
Comment 1 George Williams (NEKLS) 2023-09-19 23:59:00 UTC
Right now, many librarians struggle with Template Toolkit notices because there is a lack of good documentation.

I agree with the idea of getting rid of Koha's bespoke notices and slips syntax, but not until there's better documentation for Koha's end users on how to use Template Toolkit.
Comment 2 David Cook 2023-09-20 02:33:08 UTC
(In reply to George Williams (NEKLS) from comment #1)
> Right now, many librarians struggle with Template Toolkit notices because
> there is a lack of good documentation.
> 
> I agree with the idea of getting rid of Koha's bespoke notices and slips
> syntax, but not until there's better documentation for Koha's end users on
> how to use Template Toolkit.

I think bug 15277 would help with that
Comment 3 Rebecca Coert 2023-09-21 15:15:41 UTC
+1
Comment 4 Martin Renvoize 2023-11-14 20:51:38 UTC
This has been stuck for a very long time with minor flurries of activity over the years.

I'd love to see a concerted effort some time. I've added it to the roadmap, but we need a commitment from multiple parties to actually work on it, test etc.  we
Comment 5 Katrin Fischer 2023-11-14 21:46:15 UTC
I believe this is not only a technical issue but also an issue of better documentation. We need to enable people to achieve at least the same results as with 'hungry alligators' in an easy to understand way. Then we can build on it for more complex things.

And we will need a deprecation period.

But I think we should do it :)