http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14377

Kyle M Hall <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #16 from Kyle M Hall <[email protected]> ---
(In reply to Katrin Fischer from comment #14)
> Hm, I think 0/1 as the description is not very friendly for the cataloger
> and might lead to some confusion. Another suggestion: We could use the
> mechanism that makes system preferences available in the XSLT. We could
> create a variable to store the description that matches the authorised value
> category linked to 942$n for the value 1. And then base the check on that.
> Does that make sense? :)

I don't think I followed that well ; )

Here's what I'm thinking:
1) Add a new system preference OpacSuppressionValue that defines the value ( 1,
the Authorised Value description for 1, default of 1 if not set ). So this
value could be 1, Yes, Si, Oui or what have you.
2) Pass this new pref to the XSLT
3) Compare against the pref value rather than just '1'

Is this what you are thinking Katrin?

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to