https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28874 --- Comment #3 from Martin Renvoize <martin.renvoize@ptfs-europe.com> --- As in a nice simple way to construct display options from data returned from the API. Example, if we want to replace some of our data tables with Ajax equivalents using the API, for anything that includes Biblio title we can't easily replicate the structure returned by the biblio-title.inc template.. i.e a nice linked title consisting of multiple fields from the bib record. Yes, we can add a custom render function but we should keep it dry/reusable in the same way the template include is. Similarly, I'm not sure what route we've taken with regards av displays and the API. We return lots of codes.. is the intention to use embeds to get descriptions and even then, are we distinguishing between opac and staff and translations? Having a nice easy to call tender function that takes the code and converts it for display the way we have for TT would aid in the route to modernising the front end with load on demand and things. -- You are receiving this mail because: You are watching all bug changes.