+1 to displaying all standard information on the Details page. If a library has this info in a record, but DOESN'T want it displayed, then can either remove the info, or strip the field out with JQuery. Hopefully 'sensitive' information is not being put in MARC records...
I'm with Magnus on this one; a tool where the user can edit what fields are displayed in what order with what additional HTML (links and lists and spans etc), would be ideal. This is going to be particularly difficult with XSLT, because XSLT is, well, difficult. There has been a spec written to do User-Uploaded XSLT, so a library could modify and tweak the display as they need. We at ByWater weren't able to find enough folks interested in funding it, though, last time we asked, so it was shelved in favour of other projects. I'd really like to see more done with the ISBD view. As it stands, it's not terribly useful, as we've mostly moved away from cards at this point. But it's user-editable in a system preference, and can pull in MARC information and mix it with plaintext. If we used some of this code elsewhere, I think we could create a very customizable and user-friendly record display interface. Mashing that code up with the "tokens" we have in the Notices editor, and adding a little JQuery, could give us that drag/drop experience for customizing a record display. Probably not the most practical idea for immediate deployment, but making these sorts of display tweaks data-based instead of code-based will greatly easy the upgrade process for many libraries with particular information display needs. Cheers, -Ian On Fri, Dec 16, 2011 at 3:06 AM, Magnus Enger <[email protected]> wrote: > 2011/12/15 Fischer, Katrin <[email protected]>: > > +1 from me too. > > > > The XSLT is done so that only information in your records shows up. I > don't > > see why people would not want that. > > +1 > > In an ideal world I think we would have some cool graphical tool where > each library could easily configure their own display by dragging tags > and subfields around, set conditions, formatting etc. Well, one can > dream... > > Best regards, > Magnus Enger > libriotech.no > _______________________________________________ > Koha-devel mailing list > [email protected] > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Ian Walls Lead Development Specialist ByWater Solutions ALA Midwinter Booth #2048 Phone # (888) 900-8944 http://bywatersolutions.com [email protected] Twitter: @sekjal
_______________________________________________ Koha-devel mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
