[Koha] Erotic materials (some say pornography)

[hansbkk at gmail.com]

On Sun, Feb 27, 2011 at 2:52 AM, Waylon Robertson
<wrobertson1981 at yahoo.co.nz> wrote:
> customized the source.

I'd like to avoid going that far. So back to this idea:

>> Completely separate site/database; can multiple Koha sites share the same Patron tables?
>> Can you then filter access per database based on Patron category?

Suggestions anyone?

I suppose worst case scenario I could export a Patron category and
import that into the separate DB?



> ----- Original Message ----
> On Sun, Feb 27, 2011 at 2:21 AM, Waylon Robertson
> <wrobertson1981 at yahoo.co.nz> wrote:
>>
>> for the site i work for, we're abusing the branches table, using it for
>> libraries (completely different sections, in one db). and i coded in access
>> controls to only allow those who have the branch in their borrower attributes,
>> to be able to search those branches. limits are put inside opac-search.pl to
>> filter against the branches (in our case of multiple libraries, "or" boolean.
>>in
>> yours, possibly a "not" bool unless patron category = adult)
>
> Thanks Waylon. Do you mean that you've customized the Koha source
> scripts to accomplish this, or just set system preferences in
> conjunction with your "abuse" of branches?
>
>
>> ----- Original Message ----
>> From: "hansbkk at gmail.com" <hansbkk at gmail.com>
>> To: koha at lists.katipo.co.nz
>> Sent: Sat, 26 February, 2011 12:50:00 PM
>> Subject: [Koha] Erotic materials (some say pornography)
>>
>> The obvious solution is of course is to have a completely separate
>> site/database; can multiple Koha sites share the same Patron tables?
>> Can you then filter access per database based on Patron category?
>>
>> The main problem with this approach is that of course it's not a
>> black-and-white judgement call but shades of grey - from "a few
>> soft-core bits" vs "pretty racy stuff" vs "outright pornography". So
>> ideally the whole collection could remain in a single database and
>> just be classified using an appropriate field.
>>
>> Based on such a field, is it possible to toggle visibility in the OPAC
>> based on Patron category (disallowing anonymous visitors of course)?