I looked at it briefly for a different field, and found my understanding of XSL lacking. Adding a column to the database was the quick solution for me.
I guess I can take another look. It might be a good solution. My thinking is that it's good to see data from the two ( potentially different ) copies of the record, what's in the database columns and what's in the marcxml column. I'll have to look again at the XSL to see where it comes from too. On Mon, 2008-12-01 at 17:44 -0500, Joshua Ferraro wrote: > Michael, > > Have you experimented with the XSL support? I think it's a much better > way of solving this problem and many other problems with what should > display than adding more columns to the biblio table. > > My two cents ... > > Josh > > On Mon, Dec 1, 2008 at 4:23 PM, Michael Hafen <[EMAIL PROTECTED]> wrote: > > Excellent, and it looks like it isn't used at the moment. > > > > Thanks. > > > > On Mon, 2008-12-01 at 20:58 +0100, Frederic Demians wrote: > >> > Which UNIMARC subfield to link to, and > >> > >> In UNIMARC, sub-title field: 200$e. > >> > >> -- > >> Frédéric > > -- > > Michael Hafen > > Systems Analyst and Programmer > > Washington County School District > > Utah, USA > > > > for Koha checkout > > http://koha-dev.washk12.org > > or > > git://koha-dev.washk12.org/koha > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel@lists.koha.org > > http://lists.koha.org/mailman/listinfo/koha-devel > > > > > -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://koha-dev.washk12.org or git://koha-dev.washk12.org/koha _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
