Hi Admire, Are you running your commands as sudo?
> On 21 Aug,2017, at 9:06 AM, Admire Mutsikiwa <[email protected]> > wrote: > > Hi Katrin, > > I have tried to use the koha-rebuild-zebra -v -f $(koha-list) and I got some > errors. However, if I do koha-rebuid-zebra -v $(koha-list) leaving out -f it > runs. Sometimes it works and sometime it does not work. Possibly the problem > could be file permissions. Which directories/files are involved in the index > process and what permissions should they have? > > > Best Regards, > > Admire. > > > > -----Original Message----- > From: Koha [mailto:[email protected]] On Behalf Of > [email protected] > Sent: Tuesday, 15 August 2017 4:51 PM > To: [email protected] > Subject: Koha Digest, Vol 142, Issue 41 > > Send Koha mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.katipo.co.nz/mailman/listinfo/koha > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific than "Re: > Contents of Koha digest..." > > > Today's Topics: > > 1. Re: Restrict access (Katrin) > 2. Re: Import holds? (Katrin Fischer) > 3. Re: Restrict access (Tomas Cohen Arazi) > 4. Re: Restrict access (Marcel de Rooy) > 5. Re: Restrict access (Tomas Cohen Arazi) > 6. Re: Import holds? (Mark Alexander) > 7. Re: Koha Perl script for re-indexing (Katrin Fischer) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 15 Aug 2017 12:25:36 +0200 > From: Katrin <[email protected]> > To: [email protected] > Subject: Re: [Koha] Restrict access > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi, > > using Agerestriction is a good idea, but at the moment it will only prevent > Circulation. Koha doesn't have a mechanism to control access to linked files. > As Eric pointed out there are several problems to consider there and it will > require an external solution to Koha. > > Hope that helps, > > Katrin > > >> On 14.08.2017 16:29, Lennon Mazonde wrote: >> Hi, >> >> As Eric said, i don't know if you can filter out search results for >> certain patrons in the OPAC. >> >> What if you try enabling the AgeRestrictionMarker >> <http://translate.koha-community.org/manual/sphinx-branch/en/html/02_a >> dministration.html?highlight=agerestriction#AgeRestrictionMarker>syste >> m preference under Home › Administration › System preferences > >> Circulation Preferences > Checkout Policy? You can then place an age >> restriction in field 521$a (Audience note) for each item that you plan >> on setting age restrictions. Does that stop patrons from being able to >> download the files? >> >> Kind regards, >> >> Lennon >> >> >>> On 13/08/2017 22:03, fjcosta wrote: >>> Thank you Lennon. >>> I did as you told: three types of patrons and three kinds of items, >>> and under Circulation and Fine rules I manage to restric each type of >>> patron to its item permission (basic to basic, intermediate to >>> basic+intermediate, and >>> advanced to all). >>> But when a reader under patron type basic makes a search in OPAC, all >>> material (basic, intermediate and advanced) is visible and, if is a >>> PDF files, he can download and read it. >>> Would you please consider help me in this issue? >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://koha.1045719.n5.nabble.com/Restrict-access-tp5943311p5943320.h >>> tml Sent from the Koha-general mailing list archive at Nabble.com. >>> _______________________________________________ >>> Koha mailing list http://koha-community.org [email protected] >>> https://lists.katipo.co.nz/mailman/listinfo/koha >> >> _______________________________________________ >> Koha mailing list http://koha-community.org [email protected] >> https://lists.katipo.co.nz/mailman/listinfo/koha > > > > ------------------------------ > > Message: 2 > Date: Tue, 15 Aug 2017 12:47:45 +0200 > From: Katrin Fischer <[email protected]> > To: [email protected] > Subject: Re: [Koha] Import holds? > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Mark, > > holds information is stored differently in every ILS and at the moment > there exists no generic tool to import holds into Koha. For a migration > you could try to map the data you get out of Mandarin to the columns in > Koha's reserves table and then use a script or SQL to fill it. It can be > useful to place a few different holds in Koha first to see what data is > required/set by Koha itself. > > Hope this helps, > > Katrin > > >> On 11.08.2017 16:23, Mark Alexander wrote: >> Our little (24K items) library has successfully moved from Mandarin to >> Koha as of Tuesday. I was able to import the catalog, patrons, and >> checkouts (issues) from Mandarin by writing scripts to convert >> Mandarin-generated data to Koha-compatible data. >> >> The one missing thing is holds (reserves). I'm still looking for a >> way to generate a holds report in Mandarin, but assuming I can >> generate such a report, I don't see a way to import hold information >> into Koha. I was able to use KOC files to import issues, but the KOC >> file format doesn't support holds. I was wondering if there is some >> other way to import holds programmatically, or if anyone else has had >> to deal with this problem when migrating to Koha. >> _______________________________________________ >> Koha mailing list http://koha-community.org >> [email protected] >> https://lists.katipo.co.nz/mailman/listinfo/koha > > > > ------------------------------ > > Message: 3 > Date: Tue, 15 Aug 2017 12:13:30 +0000 > From: Tomas Cohen Arazi <[email protected]> > To: Katrin <[email protected]>, [email protected] > Subject: Re: [Koha] Restrict access > Message-ID: > <CABZfb=W0a4DeEVDNx7FRinsBXrk2V67-C6jmmNiit=ymv0g...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > That'd be an interesting feature for someone to sponsor. > > It would require doing permission checks in Koha::UploadedFile(s). > > El mar., 15 de ago. de 2017 7:26 AM, Katrin <[email protected]> > escribió: > >> Hi, >> >> using Agerestriction is a good idea, but at the moment it will only >> prevent Circulation. Koha doesn't have a mechanism to control access to >> linked files. As Eric pointed out there are several problems to consider >> there and it will require an external solution to Koha. >> >> Hope that helps, >> >> Katrin >> >> >>> On 14.08.2017 16:29, Lennon Mazonde wrote: >>> Hi, >>> >>> As Eric said, i don't know if you can filter out search results for >>> certain patrons in the OPAC. >>> >>> What if you try enabling the AgeRestrictionMarker >>> < >> http://translate.koha-community.org/manual/sphinx-branch/en/html/02_administration.html?highlight=agerestriction#AgeRestrictionMarker >>> system >>> preference under Home › Administration › System preferences > >>> Circulation Preferences > Checkout Policy? You can then place an age >>> restriction in field 521$a (Audience note) for each item that you plan >>> on setting age restrictions. Does that stop patrons from being able to >>> download the files? >>> >>> Kind regards, >>> >>> Lennon >>> >>> >>>> On 13/08/2017 22:03, fjcosta wrote: >>>> Thank you Lennon. >>>> I did as you told: three types of patrons and three kinds of items, and >>>> under Circulation and Fine rules I manage to restric each type of >>>> patron to >>>> its item permission (basic to basic, intermediate to >>>> basic+intermediate, and >>>> advanced to all). >>>> But when a reader under patron type basic makes a search in OPAC, all >>>> material (basic, intermediate and advanced) is visible and, if is a PDF >>>> files, he can download and read it. >>>> Would you please consider help me in this issue? >>>> >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> >> http://koha.1045719.n5.nabble.com/Restrict-access-tp5943311p5943320.html >>>> Sent from the Koha-general mailing list archive at Nabble.com. >>>> _______________________________________________ >>>> Koha mailing list http://koha-community.org >>>> [email protected] >>>> https://lists.katipo.co.nz/mailman/listinfo/koha >>> >>> _______________________________________________ >>> Koha mailing list http://koha-community.org >>> [email protected] >>> https://lists.katipo.co.nz/mailman/listinfo/koha >> >> _______________________________________________ >> Koha mailing list http://koha-community.org >> [email protected] >> https://lists.katipo.co.nz/mailman/listinfo/koha >> > -- > Tomás Cohen Arazi > Theke Solutions (https://theke.io <http://theke.io/>) > ✆ +54 9351 3513384 > GPG: B2F3C15F > > > ------------------------------ > > Message: 4 > Date: Tue, 15 Aug 2017 12:19:39 +0000 > From: Marcel de Rooy <[email protected]> > To: "[email protected]" <[email protected]> > Subject: Re: [Koha] Restrict access > Message-ID: > > <vi1pr05mb3487e326e70b43126552d004ce...@vi1pr05mb3487.eurprd05.prod.outlook.com> > > Content-Type: text/plain; charset="iso-8859-1" > > Not sure if muffling AgeRestriction into UploadedFiles is a good idea. A > solution to restrict access to uploads for selected users should be broader > than that imo. > > Marcel > > > ------------------------------ > > Message: 5 > Date: Tue, 15 Aug 2017 12:21:26 +0000 > From: Tomas Cohen Arazi <[email protected]> > To: Marcel de Rooy <[email protected]>, > "[email protected]" <[email protected]> > Subject: Re: [Koha] Restrict access > Message-ID: > <CABZfb=wixhhxtbw4znmtahd1fp9_d5-u4knooycgqucsoe-...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > I wouldn't propose such a thing! > What I meant is a permissions checking layer for UploadedFile(s), be it > borrower category-wise or similar. > > El mar., 15 ago. 2017 a las 9:20, Marcel de Rooy (<[email protected]>) > escribió: > >> Not sure if muffling AgeRestriction into UploadedFiles is a good idea. A >> solution to restrict access to uploads for selected users should be broader >> than that imo. >> >> Marcel >> _______________________________________________ >> Koha mailing list http://koha-community.org >> [email protected] >> https://lists.katipo.co.nz/mailman/listinfo/koha >> > -- > Tomás Cohen Arazi > Theke Solutions (https://theke.io <http://theke.io/>) > ✆ +54 9351 3513384 > GPG: B2F3C15F > > > ------------------------------ > > Message: 6 > Date: Tue, 15 Aug 2017 08:55:57 -0400 > From: Mark Alexander <[email protected]> > To: Katrin Fischer <[email protected]> > Cc: koha <[email protected]> > Subject: Re: [Koha] Import holds? > Message-ID: <1502801531-sup-8500@t60p> > Content-Type: text/plain; charset=UTF-8 > > Excerpts from Katrin Fischer's message of 2017-08-15 12:47:45 +0200: >> holds information is stored differently in every ILS and at the moment >> there exists no generic tool to import holds into Koha. For a migration >> you could try to map the data you get out of Mandarin to the columns in >> Koha's reserves table and then use a script or SQL to fill it. It can be >> useful to place a few different holds in Koha first to see what data is >> required/set by Koha itself. > > Thank you. That makes sense, and I was already thinking of doing > something like this. But there aren't a large number of holds, and it > might be less time-consuming to enter them manually than to study the > database tables and write the script. > > > ------------------------------ > > Message: 7 > Date: Tue, 15 Aug 2017 16:51:10 +0200 > From: Katrin Fischer <[email protected]> > To: [email protected] > Subject: Re: [Koha] Koha Perl script for re-indexing > Message-ID: <[email protected]> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Admire, > > I think you could maybe write a plugin to achieve this, but at the same > time I would strongly recommend figuring out the source of your problem > as this should not be necessary. Could it be that the permissions on the > index files are not correct? I notice you are using the rebulid_zebra.pl > script instead of using the package command > koha-rebuld-zebra -f <instance> > > Hope that helps, > > Katrin > >> On 12.08.2017 07:32, Mr Mutsikiwa Admire wrote: >> Hi >> >> I have three instances of Koha system that have been upgraded to Koha >> 17.05 that are giving issues with re-indexing and have to manually run >> /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -v -b -x -r to >> recreate a full index. >> >> I am thinking of having a script that will be accessible to >> superlibrarian via a link in the Koha staff interface that when >> clicked will run the command above. Any pointers on what I may have >> to do to achieve that would be greatly appreciated. >> > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Koha mailing list > [email protected] > https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > End of Koha Digest, Vol 142, Issue 41 > ************************************* > > _______________________________________________ > Koha mailing list http://koha-community.org > [email protected] > https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org [email protected] https://lists.katipo.co.nz/mailman/listinfo/koha
