New feature (idea) for Koha 3
Hello, A new feature that could (should ?) be implemented in Koha 3 : biblios have the "ISBD" system preference, that contains a personnalised version of the biblio. My libraries reported that it would be nice (better) to have : 1- 1 specific "template" for each itemtype 2- a specific "template" to show the summary of the biblio in the result list (= having a different template for monographies & serials for example) 3- the same thing for authorities. (I must admit that authorities details are really awful, it's almost the raw MARC record) 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) 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. Warning : "template" don't mean "HTML::Template", it means something the library can modify -- 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
On Wed, Aug 02, 2006 at 02:03:35PM +0200, Paul POULAIN wrote:
A new feature that could (should ?) be implemented in Koha 3 : biblios have the "ISBD" system preference, that contains a personnalised version of the biblio. My libraries reported that it would be nice (better) to have : 1- 1 specific "template" for each itemtype 2- a specific "template" to show the summary of the biblio in the result list (= having a different template for monographies & serials for example) 3- the same thing for authorities. (I must admit that authorities details are really awful, it's almost the raw MARC record)
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).
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).
(there is already a syspref for enabling MARC view by default, right?)
Warning : "template" don't mean "HTML::Template", it means something the library can modify Right ...
Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
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
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. * ************************************************************************ *
Hi, it's been a while since our (Andrés Tarallo and me) last post to the list, mostly because now we have our own version of Koha. We had to make a lot of programming to meet the university requierements, which we think are very specific so we haven't submited them to Koha. I can comment on them later if you want. To the point: the item number 2 "a specific template to show the summary of the biblio in the result list" is a very old requierement from our libraries and we are planning to fullfill them, but we are not how to implement them. I have some comments on this. We have 2 libraries, each with it's own boss and it's been a nightmare for Andrés and I to make them coordinate some things, one of the most problematics was the presentation of each itemtype. We completely rewrite the "normal" presentation and introduced the "template" concept that Paul mentions. The problem is that WE (the programmers) need to modify the templates every time a librarian changes his mind. What we want to do is create some sort simple "language" and the corresponding interpreter so the librarians can make their own modifications, and this would apply to the results list and the normal presentation. Our librarians and most of south-american librarians are comfortable with MICRO-ISIS, the Unesco cataloging system, and MICRO-ISIS already has this functionallity. We could also improve it very easily because in MICRO-ISIS you have a short field to define the presentation, so you can't waste any byte and you must write all the "presentation program" in ONE long line, not very funny. If this is possible, the system will have at least a default template for the results list and another for the normal presentation. But librarians will be able to define a new pair of templates for each itemtype. If some itemtype does not have a defined template then the default is used. I know the ISBD display and I think your "item 1" is a must, but our Koha version (2.2 based) does not implement any "if-then-else" like statement. This kind of decision making is necessary for example when a field doesn't exists and must be substituted with some other content. Another issue are the repeated fields, some functionality must be provided to display repeated fields like subjects, the ones in the 6XX range, etc. We don't use the authorities section so I have no specific comments on item 3, but perhaps some of the above may also apply to this. Best regards, -- Ing. Ernesto Silva. Coordinador de Desarrollo Web y Sistemas Abiertos Universidad ORT Uruguay. E-mail: silva@ort.edu.uy Tel: (+598-2) 902-1505 ext. 206 Paul POULAIN wrote:
Hello,
A new feature that could (should ?) be implemented in Koha 3 : biblios have the "ISBD" system preference, that contains a personnalised version of the biblio. My libraries reported that it would be nice (better) to have : 1- 1 specific "template" for each itemtype 2- a specific "template" to show the summary of the biblio in the result list (= having a different template for monographies & serials for example) 3- the same thing for authorities. (I must admit that authorities details are really awful, it's almost the raw MARC record)
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)
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.
Warning : "template" don't mean "HTML::Template", it means something the library can modify
participants (4)
-
Anthony Youngman -
Ernesto Silva -
Joshua Ferraro -
Paul POULAIN