[Koha] I'm confused about where normal view customization occurs

[Doug Dearden]

Thanks Joe, I'll look at the HTML::Template perldoc.  By your reply I surmise that this takes a code modification and there is no way to do it from the admin pages.

Regarding the copy prog stuff, I was doing that in an effort to use the "opactheme" option.  Copy the default theme, rename it, then make minor modifications to the copy and point a second database at that theme rather than the default.  It didn't work, I put in a bug report (#2774) to which Owen commented "There are a LOT of instances in templates and code where the "prog" theme is hardcoded."  So I abandoned that avenue.  With xsl on for one DB and off for the other, I was able to customize the detail page the xsl version uses and leave the other alone.  With the exception of those changes, the rest of my customizations are simple ones that can be pointed to from the System Preferences - different color.css files, simple changes in the header via html in the right place in system preferences.  Because of that I haven't been using git.  My notes about the install make me think that I thought it was going to remove aptitude in favor of it.  As I was using aptitude to look for perl packages as well as others, I said no to installing git.  Perhaps I misunderstood something there.   

This is my first time using Linux and Perl on a production system, so I am learning those as I go.  It is not my intention to do any major modifications in the Perl code, but I can tweak where necessary to get things looking the way our librarian would like them to.  Is there a reference on git you can point me to?  Or can you tell me how it is used in Koha development?  I am completely in the dark regarding it.    

Thanks,

Doug


>>> Joe Atzberger <ohiocore at gmail.com> 2/20/2009 11:24:53 AM >>>
Like any page, you can add TMPL_VAR's to the template, and add to the script
that populates it.  It sounds like you should refer to the HTML::Template
perldoc to see how it operates.

The XSL solution is a lot slicker if you can manage it, but that only
applies for the OPAC (when enabled).

I'm not sure what approach you are taking by copying prog, but then using a
"second database" on it.  Copying prog is pretty drastic and is sure to cut
off your developments from mainline updates.  If you use git to control your
code, then you wouldn't need to copy everything (since you could always
revert to the mainline version if it got messed up), and you could still
pull down updates.

--Joe

On Fri, Feb 20, 2009 at 12:46 PM, Doug Dearden <dearden at sarsf.org> wrote:

> Ah, OK.  I have multiple databases and have turned on the xsl option on one
> of them and used it to customize how the clickable links appear, as that
> database is cataloging on-line resources.  I ran into trouble turning on xsl
> for the other databases, as the "prog" directory is hard coded in many
> places in the code, and copying the file structure over to a new directory
> and pointing a second database at that structure didn't work, too many
> things still fetched from "prog".  Because of that I left the xsl option off
> on the main catalog DB.
>
> So is the answer to my question that the customization for this occurs at
> the Perl template level?  Or is there some other place in the Admin that I
> can add other fields to the Title line in the Normal View?
>
> Thanks,
>
> Doug
>
> >>> Nicole Engard <nicole.engard at liblime.com> 2/20/2009 9:14 AM >>>
> The screenshots in the manual are probably different because some were
> taken with XSL on and others with it off.  There are two system
> preferences that control this and can be found here:
>
> https://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/administration/Global-Preferences/Global-Preferences--OPAC 
>
> ---
>
> Nicole C. Engard
> Open Source Evangelist, LibLime
> (888) Koha ILS (564-2457) ext. 714
> nce at liblime.com 
> AIM/Y!/Skype: nengard
>
> http://liblime.com 
> http://blogs.liblime.com/open-sesame/ 
>
>
>
> On Fri, Feb 20, 2009 at 11:06 AM, Doug Dearden <dearden at sarsf.org> wrote:
> > Hello all,
> >
> > I am trying to figure out if there is an easy way to add to the fields
> that appear in the Normal view of the OPAC and the Staff Client.
>  Specifically, we currently see the 245$a field as the Title in the search
> results and detail view page.  Is there a way in the Admin screens to change
> the display so the 245$b subfield is appended to the 245$a subfield, and
> display both as the Title?  I thought this would be customizable from within
> the frameworks, but I don't seem to be having any luck.  Looking at the doc
> on this page:
> https://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/opac/opac-details-pagethe samples show titles with two different formats, one of which appears to
> be displaying info that is normally in the 245$b field.
> >
> > Is this customization that takes place at the Perl template level?  Or is
> there something I am missing in the Admin?
> >
> > Thanks,
> >
> > Doug
> >
> > _______________________________________________
> > Koha mailing list
> > Koha at lists.katipo.co.nz 
> > http://lists.katipo.co.nz/mailman/listinfo/koha 
> >
>
>
> _______________________________________________
> Koha mailing list
> Koha at lists.katipo.co.nz 
> http://lists.katipo.co.nz/mailman/listinfo/koha 
>