Re: [Koha] Show online subscription info only to patrons

2017-10-23 Thread Katrin Fischer
Hi Eric, you could add a new page to the OPAC using |RestrictedPageContent and |||RestrictedPageTitle system preferences. Then use OpacNav or similar to add a link to the new page. It will look like: [Your OpacBaseUrl]/cgi-bin/koha/opac-restrictedpage.pl. The page is only accessible when you

[Koha] Show online subscription info only to patrons

2017-10-23 Thread Stephanie Schweter
Hi Eric, We submitted a ticket to ByWater to get a "your databases" tab added to do something similar. The web opac guru at ByWater, Michael, said he could easily add this feature. Basically, you would need to edit the pages related to the OPAC content to add this option. Check Koha Administrat

Re: [Koha] Site Migration - Staff (-Intra) Site Software Error on Login

2017-10-23 Thread John Ciempka
“Do you have a line number? :)” When migrating through an older package v.16.05.17.000, The web error log displayed: mainpage.pl: Can't locate object method "ymd" via package "dateonly" (perhaps you forgot to load "dateonly"?) at /usr/share/koha/lib/Koha/DateUtils.pm line 225.: /usr/share/koha

[Koha] Show online subscription info only to patrons

2017-10-23 Thread Eric Phetteplace
Hi all, Does anyone have a method for displaying information only to logged in users in the catalog? Something in between a private note visible only to staff and a public note visible to anyone? We have some journal subscriptions with an online component that uses a shared login. We want our pat

Re: [Koha] Salvaging data before using DBMS auto increment fix

2017-10-23 Thread Pedro Amorim
Thanks for your reply, Marcel. I'll probably go for option number 2 given the size of the data, it's safer and I'm happy with it. Thanks a bunch, have a good one. Pedro Amorim 2017-10-23 12:46 GMT+00:00 Marcel de Rooy : > Hmm. You need to have room in the deleted range to do that of course.. >

Re: [Koha] Salvaging data before using DBMS auto increment fix

2017-10-23 Thread Marcel de Rooy
Hmm. You need to have room in the deleted range to do that of course.. -Oorspronkelijk bericht- Van: Koha [mailto:koha-boun...@lists.katipo.co.nz] Namens Marcel de Rooy Verzonden: maandag 23 oktober 2017 14:43 Aan: Koha list Onderwerp: Re: [Koha] Salvaging data before using DBMS auto incr

Re: [Koha] Salvaging data before using DBMS auto increment fix

2017-10-23 Thread Marcel de Rooy
Pedro, Personally I would delete the 19 old ones. Your option 2. Easiest, no big data loss.. In contrast with your option 3 you could also renumber the 19 old issues in the deleted table. The autoincr will be reset when you add another record and you made room for the 19 new ones. It seems safe

[Koha] Salvaging data before using DBMS auto increment fix

2017-10-23 Thread Pedro Amorim
Hello all, I want to implement https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix on our instance, however from my understanding this will only prevent the problem from happening in the future, it will not fix the current corrupted data. I happen to have 19 ids that exist on both issues

[Koha] Informatics launches Library Technology Conclave (LTC) 2018, an annual event - 23-25 January 2018, Goa University Library

2017-10-23 Thread Amit Gupta
Greetings from Informatics! Koha Conclave started by Informatics two years ago, is re-launched with new name and expanded scope as Library Technology Conclave - LTC for short. The last Conclave was held in Pune in partnership with the Information Resource Centre, TCS, Pune. The forthcoming event -