Again late to the conversation ... I've long felt that the MARC data is admirably suited to a Multi-Value database model. The basics behind Multi-Value and XML data are pretty much identical. I want to be very careful suggesting yet another database technology (seeing as you've already got Zebra and MySQL), but if they're not addressing your problems, shouldn't you at least be addressing that? Cheers, Wol -----Original Message----- From: koha-devel-bounces+anthony.youngman=eca-international.com@nongnu.org [mailto:koha-devel-bounces+anthony.youngman=eca-international.com@nongnu.org] On Behalf Of Paul POULAIN Sent: 02 August 2006 13:32 To: Joshua Ferraro Cc: Koha-devel@nongnu.org Subject: Re: [Koha-devel] New feature (idea) for Koha 3 Joshua Ferraro a écrit :
On Wed, Aug 02, 2006 at 02:03:35PM +0200, Paul POULAIN wrote:
Unless someone declares he is already working on this, I'll do it (me or hdl or antoine, depends on who get some time to do this. I think 2 days are needed to do something working well) What would you use as the 'template'? Might I suggest XSLT? You can do some pretty amazing transformations with it and if you stored the XSLT markup in the db (like in a syspref) the librarian could edit it to change the way the MARC was displayed. So you would have: MARCXML from system -> XSLT Stylesheet (from sypref) -> HTML Markup inserted on detail page (or even on original results page, since we already have the full MARC with zebra).
Of course you can suggest XSLT. I haven't investigated what it means in term of needed packages, but for sure that's a way I plan to investigate.
PS : Other ideas in the same area : - rewrite the "normal" (=detail.pl), to get rid of non MARC database - add a systempreference to enable MARC view or disable it in OPAC. IMO the old MARC db must be completely removed or else seriously overhauled. One major problem is we can't add arbitrary MARC fields for display in detail.pl; another is we can't have repeatable fields display properly without writing a new subroutine (even current additional authors stuff doesn't preserve order properly).
Right. I think we all agree that only a few fields could be useful in the non MARC DB. Something like : title, author, ISBN, and nothing more.
(there is already a syspref for enabling MARC view by default, right?)
A syspref to choose which view you want by default. It's set to "ISBD" for most of my libraries, as you can do many things with it already (except preserving subfield order in a field, I know) -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19 _______________________________________________ Koha-devel mailing list Koha-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel * ************************************************************************ * This transmission is intended for the named recipient only. It may contain private and confidential information. If this has come to you in error you must not act on anything disclosed in it, nor must you copy it, modify it, disseminate it in any way, or show it to anyone. Please e-mail the sender to inform us of the transmission error or telephone ECA International immediately and delete the e-mail from your information system. Telephone numbers for ECA International offices are: Sydney +61 (0)2 8272 5300, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 2333. * ************************************************************************ *