Re: [Koha] E-mail configuration in koha version 3.0.6

[vikram zadgaonkar]

+1.
Upgrade first and configure.


Virus-free.
www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Vikram Zadgaonkar

On Thu, Aug 10, 2017 at 5:16 PM, SATISH  wrote:

> Hello Ravi Venkat,
>
> For setting up email facility:
> 1. you need to install Postfix, is a free and open-source - Mail Transfer
> Agent (MTA) on  Operating system (OS).
>
> 2. follow instructions in the following URL for configurations:
> http://kohageek.blogspot.in/search?q=postfix
>
> 3. then create a gmail account for your library and store username/password
> while doing Postfix configurations, later Koha system will be able to
> automatically send  email notices to borrowers for their transactions i,e
> issue,return, overdue,etc.
>
> 4. To send overdue Notices, Home > Tools > Overdue notice/status triggers
> and select the library
> and against each - (1) column-  patron category - mention no of days in
> "delay"  2nd column- select type of letter like, (overdue notice) in 3rd
> column and in
> 5th column enable Email with Tickmark.
>
> AND
>
> You can insert messages at -  Home › Tools › Notices & Slips
> Edit the default template or create new notice.
>
> And find some of the sample message that we are using for Govt. Engineering
> College, Hassan - Library.
>
> 1) Book Check-Out (Issue) Message
> 
> Dear  <> <>,
>
> The following book is checked out (Issued) from the library for your card
> number: <>
>
> Accession No: <>
> Call No: <>
> Title: <>
> Author: <>
> Check Out on: <>
> Due Date: <>
>
> This email is system generated. Please do not reply to this mail.
>
> Library and Informaiton Centre,
> Your Library Name
>
> 
> 2) Book Check-in (Return) Message
> --
> Dear   <>  <>,
>
> The following book is returned (check-in) to the library for your card
> number : <>
>
> Accession No: <>
> Call No: <>
> Title: <>
> Author: <>
> Borrowed On : <>
>
> Library and Informaiton Centre,
> Your Library Name
> 
>
> 3) Pre-Due Reminder ( Before Due Date)
> --
> Dear <> <>,
>
> The following book will be due soon for your card number
> <> :
>
> Accession No: <> -  <>, by <>
> Due Date: <>
>
> Please return or renew them before due date.
>
> Library and Informaiton Centre,
> Your Library Name
>
> Please do not reply to this notification as it was automatically generated.
> If you have any question regarding this notification, please contact
> Librarian
> =
>
> 4) Due Reminder (After Due Date)
> -
>
> Dear <> <> CARD NUMBER
> <>,
>
> According to our current records, you have following book(s) that is/are
> overdue. Please return or renew them at the Circulation section as soon as
> possible.
>
>
> Title: <>,  by <>
> Accession No:  <>
> Check out (Borrowed) date:  <>
> Due Date:  <>
>
>
> Library and Information Centre,
> Your Library Name
>
> Please do not reply to this notification as it was automatically generated.
> If you have any question regarding this notification, please contact
> Librarian.
>
> ==
>
> 5) Over Due (Final and Last Reminder)
>
> Dear <> <>,
>
> According to our Library records, you have books pending/overdue for your
> card number : <> .  Please return or renew them as
> soon as possible. There are two auto generated reminder emails have been
> sent by the system to you regarding library dues.  Please refer previous
> emails with the subject -  Item Due Reminder  or  Advance Notice of Item
> Due"  for finding books details. Please note that, this is the final
> reminder email.
>
> 
> Title: <>,  by <>
> Accession No:  <>
> Check out (Borrowed) date:  <>
> Due Date:  <>
> 
>
> Library and Informaiton Centre,
> Your Library Name
>
> --
>
> Hope, it help you to understand.
>
> with thanks
> Satish MV
> Librarian
> Govt. Engineering College, Hassan.
> Karnataka.
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[vikram zadgaonkar]

I do agree .

On Aug 11, 2017 1:56 AM, "Chris Cormack"  wrote:

> * Indranil Das Gupta (indr...@gmail.com) wrote:
>
>> Hi
>>
>> On Fri, Aug 11, 2017 at 1:04 AM, Chris Cormack 
>> wrote:
>>
>> So move it off the site and make it 'the community managed list'. Or some
>>> other name. But make it its own thing clearly maintained by volunteers, not
>>> part of the main site and in no way official at all.
>>>
>>
>> Anything on *.koha-community.org will be deemed "official" ;-)
>>
>
> Yep, right off that url is what I meant.
>
> Because I see the list as something that works against small companies,
> rather than for them. As your experience would attest Indranil.
> Not being on the list is used as a weapon against companies. So pretty
> much the exact opposite viewpoint to Brooke.
>
> I see the list as just one more obstacle in a dev/vendor being able to
> offer Koha support, rather than a help. Especially if as we are talking
> about is making it harder to get listed.
> This will be my last email on it, and I will be talking to my colleagues
> about having our name removed, and I hope the whole list and all the
> problems it causes for new developers goes away.
>
> Chris
>
>
>> indranil
>>
>
> --
> Chris Cormack
> Catalyst IT Ltd.
> +64 4 803 2238
> PO Box 11-053, Manners St, Wellington 6142, New Zealand
>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Reminder: Internet broadcast of Koha-US

[Irma Birchall]

No problem for me Michael.
Perhaps try the link again now.

Cheers,
Irma
https://calyx.net.au




On 11 August 2017 at 02:29, Michael Kuhn  wrote:

> Hi Christopher
>
> On 8 August you wrote:
>
>
> I am excited about the Koha-US conference beginning tomorrow morning. For
 those of us who cannot make it up to Coeur d'Alene to attend this
 conference in person, don't worry...the conference can come to you. Look
 for the "Broadcast" hyperlinks on the webpage found at
 http://koha-us.net/index.php/2017_Koha-US_Conference. Please note that
 since there are two concurrent sessions during each time slot, you will
 need to select one of the two "Broadcast" links (one for the Community
 Room
 and one for the Story Room). There is a limited number of seats open for
 these broadcasts, so connect early before the seats are taken.

 Please feel free to contact me with your related comments and/or
 questions.

>>>
>
> Now at the second day of the 2017 Koha US Conference the URL
> http://koha-us.net/index.php/2017_Koha-US_Conference is not accessible
> ("Forbidden. You don't have permission etc etc"), so it's neither posible
> to see the program or even click one of the Broadcast-Links...
>
> Best wishes: Michael
> --
> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Reminder: Internet broadcast of Koha-US

[Christopher Davis]

Michael,

Thank you for notifying me about the problem with the Koha-US conference
website. I apologize for the inconvenience and it should be working now.

Christopher Davis
​Secretary, Koha-US
cgda...@uintah.utah.gov​



On Thu, Aug 10, 2017 at 10:29 AM, Michael Kuhn  wrote:

> Hi Christopher
>
> On 8 August you wrote:
>
>
> I am excited about the Koha-US conference beginning tomorrow morning. For
 those of us who cannot make it up to Coeur d'Alene to attend this
 conference in person, don't worry...the conference can come to you. Look
 for the "Broadcast" hyperlinks on the webpage found at
 http://koha-us.net/index.php/2017_Koha-US_Conference. Please note that
 since there are two concurrent sessions during each time slot, you will
 need to select one of the two "Broadcast" links (one for the Community
 Room
 and one for the Story Room). There is a limited number of seats open for
 these broadcasts, so connect early before the seats are taken.

 Please feel free to contact me with your related comments and/or
 questions.

>>>
>
> Now at the second day of the 2017 Koha US Conference the URL
> http://koha-us.net/index.php/2017_Koha-US_Conference is not accessible
> ("Forbidden. You don't have permission etc etc"), so it's neither posible
> to see the program or even click one of the Broadcast-Links...
>
> Best wishes: Michael
> --
> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[Chris Cormack]

* Indranil Das Gupta (indr...@gmail.com) wrote:

Hi

On Fri, Aug 11, 2017 at 1:04 AM, Chris Cormack  wrote:


So move it off the site and make it 'the community managed list'. Or some other 
name. But make it its own thing clearly maintained by volunteers, not part of 
the main site and in no way official at all.


Anything on *.koha-community.org will be deemed "official" ;-)


Yep, right off that url is what I meant.

Because I see the list as something that works against small companies,
rather than for them. As your experience would attest Indranil.
Not being on the list is used as a weapon against companies. 
So pretty much the exact opposite viewpoint to Brooke.


I see the list as just one more obstacle in a dev/vendor being able to
offer Koha support, rather than a help. Especially if as we are talking
about is making it harder to get listed. 


This will be my last email on it, and I will be talking to my colleagues
about having our name removed, and I hope the whole list and all the
problems it causes for new developers goes away.

Chris



indranil


--
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand


signature.asc
Description: PGP signature
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[Indranil Das Gupta]

Hi

On Fri, Aug 11, 2017 at 1:04 AM, Chris Cormack  wrote:

> So move it off the site and make it 'the community managed list'. Or some 
> other name. But make it its own thing clearly maintained by volunteers, not 
> part of the main site and in no way official at all.

Anything on *.koha-community.org will be deemed "official" ;-)

indranil
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[Diedre Conkling]

I mostly just read this list but I thought I'd comment on this subject.  I
think this should be put to a vote.  I think Chris has spelled out three
good categories.  It might be that there are one or two more categories.
Just add those suggestions in the next day or two and then put out a poll.



On Thu, Aug 10, 2017 at 12:34 PM Chris Cormack 
wrote:

> Hi All
>
> A proposal, for voting on.
> 1/ make the listing criteria more stringent + move the list off the main
> site to its own thing.
>
> Or we just make it more official and increase all the problems.
>
> So move it off the site and make it 'the community managed list'. Or some
> other name. But make it its own thing clearly maintained by volunteers, not
> part of the main site and in no way official at all.
>
> Chris
>
> On 11 August 2017 3:26:44 AM NZST, Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> wrote:
> >Vinod,
> >
> >This already exists and is auto-generated for each release.
> >For 17.05, https://koha-community.org/koha-17-05-released
> >But, as said previously by others, 1 != 1 and there are much more than
> >just
> >writing patches in a community daily tasks.
> >
> >Regards,
> >Jonathan
> >
> >On Thu, 10 Aug 2017 at 07:15 vinod mishra  wrote:
> >
> >> I think we can make a parameter like the company who have submitted
> >at
> >> least five patch/new code for major active release oldoldstable,
> >oldstable
> >> and stable will be only listed. For example if a company has five
> >> code/patch in 16.5 than he may be listed continuously up-to 17.5 once
> >17.11
> >> will release and there is no contribution in 16.11 than they may be
> >delist.
> >>
> >> Above is only one parameter but someone have to monitor this
> >continuously
> >> to update the list, however range of version can be increased, by
> >doing so
> >> they will be encouraged to contribute continuously if they do not
> >want to
> >> die from list.
> >>
> >>
> >> With Regards,
> >>
> >> Vinod Kumar Mishra,
> >> Assistant Librarian,
> >> Biju Patnaik Central Library (BPCL),
> >> NIT Rourkela,
> >> Sundergadh-769008,
> >> Odisha,
> >> India.
> >> Mob:91+9439420860
> >> Website: http://mishravk.com/
> >> ORCID ID: http://orcid.org/-0003-4666-7874
> >>
> >> *"Spiritual relationship is far more precious than physical. Physical
> >> relationship divorced from spiritual is body without soul" -- Mahatma
> >> Gandhi*
> >>
> >> On Wed, Aug 9, 2017 at 8:47 PM, Mark Tompsett 
> >> wrote:
> >>
> >> > Greetings,
> >> >
> >> > Nathan A. Curulla suggested:
> >> > > Maybe we should change the listing to “contributing support
> >companies”
> >> or
> >> > > something like that.
> >> >
> >> > While I think that is a good idea, and then companies without
> >community
> >> > participation get removed, the problem still remains: people don't
> >read.
> >> > We've put a nice disclaimer that this is not an official list and
> >has no
> >> > official seal of approval meaning to the list, and yet people still
> >use
> >> it
> >> > that way. It is impossible to educate people who refuse to read,
> >even
> >> > though
> >> > the preamble write up is a rather good explanation of how to look
> >for a
> >> > Koha
> >> > support provider. As such, the only reasonable course of action is
> >to
> >> > delete
> >> > the list, otherwise it will continue to be used that way, no matter
> >what
> >> we
> >> > put on the page(s).
> >> >
> >> >
> >> > Owen Leonard wrote:
> >> > > It would be a duplicate listing ... and should be rejected.
> >> >
> >> > Who determines it is a duplicate listing? Because last time I
> >looked some
> >> > other entries looked like duplicates to me, much like OpenLX/BBB.
> >And
> >> > cleaning up duplicates is a pain. Yet another reason to just delete
> >the
> >> > list
> >> > already.
> >> >
> >> > GPML,
> >> > Mark Tompsett
> >> >
> >> > ___
> >> > Koha mailing list  http://koha-community.org
> >> > Koha@lists.katipo.co.nz
> >> > https://lists.katipo.co.nz/mailman/listinfo/koha
> >> >
> >> ___
> >> Koha mailing list  http://koha-community.org
> >> Koha@lists.katipo.co.nz
> >> https://lists.katipo.co.nz/mailman/listinfo/koha
> >>
> >___
> >Koha mailing list  http://koha-community.org
> >Koha@lists.katipo.co.nz
> >https://lists.katipo.co.nz/mailman/listinfo/koha
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
-- 
*Diedre Conkling*




*Lincoln County Library DistrictP.O. Box 2027Newport, OR 97365Phone & Fax:
541-265-3066Work email**: **die...@lincolncolibrarydist.org*

*Home email: **diedr...@gmail.com* 

“If you don't like 

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[Chris Cormack]

Hi All 

A proposal, for voting on. 
1/ make the listing criteria more stringent + move the list off the main site 
to its own thing. 

Or we just make it more official and increase all the problems. 

So move it off the site and make it 'the community managed list'. Or some other 
name. But make it its own thing clearly maintained by volunteers, not part of 
the main site and in no way official at all. 

Chris 

On 11 August 2017 3:26:44 AM NZST, Jonathan Druart 
 wrote:
>Vinod,
>
>This already exists and is auto-generated for each release.
>For 17.05, https://koha-community.org/koha-17-05-released
>But, as said previously by others, 1 != 1 and there are much more than
>just
>writing patches in a community daily tasks.
>
>Regards,
>Jonathan
>
>On Thu, 10 Aug 2017 at 07:15 vinod mishra  wrote:
>
>> I think we can make a parameter like the company who have submitted
>at
>> least five patch/new code for major active release oldoldstable,
>oldstable
>> and stable will be only listed. For example if a company has five
>> code/patch in 16.5 than he may be listed continuously up-to 17.5 once
>17.11
>> will release and there is no contribution in 16.11 than they may be
>delist.
>>
>> Above is only one parameter but someone have to monitor this
>continuously
>> to update the list, however range of version can be increased, by
>doing so
>> they will be encouraged to contribute continuously if they do not
>want to
>> die from list.
>>
>>
>> With Regards,
>>
>> Vinod Kumar Mishra,
>> Assistant Librarian,
>> Biju Patnaik Central Library (BPCL),
>> NIT Rourkela,
>> Sundergadh-769008,
>> Odisha,
>> India.
>> Mob:91+9439420860
>> Website: http://mishravk.com/
>> ORCID ID: http://orcid.org/-0003-4666-7874
>>
>> *"Spiritual relationship is far more precious than physical. Physical
>> relationship divorced from spiritual is body without soul" -- Mahatma
>> Gandhi*
>>
>> On Wed, Aug 9, 2017 at 8:47 PM, Mark Tompsett 
>> wrote:
>>
>> > Greetings,
>> >
>> > Nathan A. Curulla suggested:
>> > > Maybe we should change the listing to “contributing support
>companies”
>> or
>> > > something like that.
>> >
>> > While I think that is a good idea, and then companies without
>community
>> > participation get removed, the problem still remains: people don't
>read.
>> > We've put a nice disclaimer that this is not an official list and
>has no
>> > official seal of approval meaning to the list, and yet people still
>use
>> it
>> > that way. It is impossible to educate people who refuse to read,
>even
>> > though
>> > the preamble write up is a rather good explanation of how to look
>for a
>> > Koha
>> > support provider. As such, the only reasonable course of action is
>to
>> > delete
>> > the list, otherwise it will continue to be used that way, no matter
>what
>> we
>> > put on the page(s).
>> >
>> >
>> > Owen Leonard wrote:
>> > > It would be a duplicate listing ... and should be rejected.
>> >
>> > Who determines it is a duplicate listing? Because last time I
>looked some
>> > other entries looked like duplicates to me, much like OpenLX/BBB.
>And
>> > cleaning up duplicates is a pain. Yet another reason to just delete
>the
>> > list
>> > already.
>> >
>> > GPML,
>> > Mark Tompsett
>> >
>> > ___
>> > Koha mailing list  http://koha-community.org
>> > Koha@lists.katipo.co.nz
>> > https://lists.katipo.co.nz/mailman/listinfo/koha
>> >
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>
>___
>Koha mailing list  http://koha-community.org
>Koha@lists.katipo.co.nz
>https://lists.katipo.co.nz/mailman/listinfo/koha

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Reminder: Internet broadcast of Koha-US

[Michael Kuhn]

Hi Christopher

On 8 August you wrote:



I am excited about the Koha-US conference beginning tomorrow morning. For
those of us who cannot make it up to Coeur d'Alene to attend this
conference in person, don't worry...the conference can come to you. Look
for the "Broadcast" hyperlinks on the webpage found at
http://koha-us.net/index.php/2017_Koha-US_Conference. Please note that
since there are two concurrent sessions during each time slot, you will
need to select one of the two "Broadcast" links (one for the Community
Room
and one for the Story Room). There is a limited number of seats open for
these broadcasts, so connect early before the seats are taken.

Please feel free to contact me with your related comments and/or
questions.



Now at the second day of the 2017 Koha US Conference the URL 
http://koha-us.net/index.php/2017_Koha-US_Conference is not accessible 
("Forbidden. You don't have permission etc etc"), so it's neither 
posible to see the program or even click one of the Broadcast-Links...


Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[Jonathan Druart]

Vinod,

This already exists and is auto-generated for each release.
For 17.05, https://koha-community.org/koha-17-05-released
But, as said previously by others, 1 != 1 and there are much more than just
writing patches in a community daily tasks.

Regards,
Jonathan

On Thu, 10 Aug 2017 at 07:15 vinod mishra  wrote:

> I think we can make a parameter like the company who have submitted at
> least five patch/new code for major active release oldoldstable, oldstable
> and stable will be only listed. For example if a company has five
> code/patch in 16.5 than he may be listed continuously up-to 17.5 once 17.11
> will release and there is no contribution in 16.11 than they may be delist.
>
> Above is only one parameter but someone have to monitor this continuously
> to update the list, however range of version can be increased, by doing so
> they will be encouraged to contribute continuously if they do not want to
> die from list.
>
>
> With Regards,
>
> Vinod Kumar Mishra,
> Assistant Librarian,
> Biju Patnaik Central Library (BPCL),
> NIT Rourkela,
> Sundergadh-769008,
> Odisha,
> India.
> Mob:91+9439420860
> Website: http://mishravk.com/
> ORCID ID: http://orcid.org/-0003-4666-7874
>
> *"Spiritual relationship is far more precious than physical. Physical
> relationship divorced from spiritual is body without soul" -- Mahatma
> Gandhi*
>
> On Wed, Aug 9, 2017 at 8:47 PM, Mark Tompsett 
> wrote:
>
> > Greetings,
> >
> > Nathan A. Curulla suggested:
> > > Maybe we should change the listing to “contributing support companies”
> or
> > > something like that.
> >
> > While I think that is a good idea, and then companies without community
> > participation get removed, the problem still remains: people don't read.
> > We've put a nice disclaimer that this is not an official list and has no
> > official seal of approval meaning to the list, and yet people still use
> it
> > that way. It is impossible to educate people who refuse to read, even
> > though
> > the preamble write up is a rather good explanation of how to look for a
> > Koha
> > support provider. As such, the only reasonable course of action is to
> > delete
> > the list, otherwise it will continue to be used that way, no matter what
> we
> > put on the page(s).
> >
> >
> > Owen Leonard wrote:
> > > It would be a duplicate listing ... and should be rejected.
> >
> > Who determines it is a duplicate listing? Because last time I looked some
> > other entries looked like duplicates to me, much like OpenLX/BBB. And
> > cleaning up duplicates is a pain. Yet another reason to just delete the
> > list
> > already.
> >
> > GPML,
> > Mark Tompsett
> >
> > ___
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> >
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[Indranil Das Gupta]

Hi,

On Aug 10, 2017 5:47 PM, "BWS Johnson"  wrote:

>  Mashing some stuff up here, but I feel like we need a vote on this
either over the listserv or at the next IRC General Sep 6.

+1

>  I'm not for a patch wall. Carrots, not sticks.

I'm afraid the metaphor "patch wall" escapes me. Can you pls elaborate?

>> Basically, do we become bureaucrats OR do we write Koha?
>
>  It doesn't have to be an either or decision. You choose to write
code, which is great. When developers think "Oh yuck, I can be coding
instead" Librarians should step up.

Not to nitpick, but I used "write" as a metaphor for all activities around
Koha, given that the written word is our primary tool - whether to answer
user queries, write a blog about a cool new feature, improve the wiki and
manual, discuss and decide new spec (e.g. the MARC framework debate we are
having on the devel list that needs inputs and approval from librarians
even more than from the devs) and finally of course there's writing the
code.

A dev who simply says "Yuck! I could be coding instead" is IMHO a poor one
who has basically stopped listening to the users and the eco-system they
are in.

Cheers
Indranil

> Cheers,
> Brooke
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Getting Elastic search 5.X working with authority searching and presentation in the Koha staff intranet

[Tomas Cohen Arazi]

El jue., 10 ago. 2017 a las 8:24, David Holoshka ()
escribió:

> Hi,
>
> We would like to see this feature working.  Do we just report what is
> not working in Bugzilla and submit patches for the items or is their
> some kind of coordination with other people that we need to take into
> account ?
>

The best approach is to first search in bugzilla for existing reported
bugs. For example there's this one:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18624

If you don't find anyone related, please file a bug report detailing how to
reproduce the issue.

Is there a plan or roadmap for elastic search work or do we just do what
> we want ?
>

Nick Clemens (kidclamp) is working heavily on the ES integration, you can
ask him on IRC channel.


> Is this the right mailing group for this question ?


If it gets technical, better on koha-devel. But a healthy conversation
about the ES implementation roadmap can belong here.

Regards
-- 
Tomás Cohen Arazi
Theke Solutions (https://theke.io )
✆ +54 9351 3513384
GPG: B2F3C15F
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[BWS Johnson]

Salvete!

 Mashing some stuff up here, but I feel like we need a vote on this either 
over the listserv or at the next IRC General Sep 6.


>>
Further, everyone who maintains the website do so as volunteers. Expecting
them to start acting as police is probably not the best of ideas. I know
for a fact that Liz stopped volunteering on the PAID provider section
maintenance as she was sick of dealing with it.

>>

 I'm happy to serve as the gatekeeper for this page for a year.


 I'm not for a patch wall. Carrots, not sticks.

>>
Basically, do we become bureaucrats OR do we write Koha?

>>


 It doesn't have to be an either or decision. You choose to write code, 
which is great. When developers think "Oh yuck, I can be coding instead" 
Librarians should step up.

Cheers,
Brooke
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] E-mail configuration in koha version 3.0.6

[SATISH]

Hello Ravi Venkat,

For setting up email facility:
1. you need to install Postfix, is a free and open-source - Mail Transfer
Agent (MTA) on  Operating system (OS).

2. follow instructions in the following URL for configurations:
http://kohageek.blogspot.in/search?q=postfix

3. then create a gmail account for your library and store username/password
while doing Postfix configurations, later Koha system will be able to
automatically send  email notices to borrowers for their transactions i,e
issue,return, overdue,etc.

4. To send overdue Notices, Home > Tools > Overdue notice/status triggers
and select the library
and against each - (1) column-  patron category - mention no of days in
"delay"  2nd column- select type of letter like, (overdue notice) in 3rd
column and in
5th column enable Email with Tickmark.

AND

You can insert messages at -  Home › Tools › Notices & Slips
Edit the default template or create new notice.

And find some of the sample message that we are using for Govt. Engineering
College, Hassan - Library.

1) Book Check-Out (Issue) Message

Dear  <> <>,

The following book is checked out (Issued) from the library for your card
number: <>

Accession No: <>
Call No: <>
Title: <>
Author: <>
Check Out on: <>
Due Date: <>

This email is system generated. Please do not reply to this mail.

Library and Informaiton Centre,
Your Library Name


2) Book Check-in (Return) Message
--
Dear   <>  <>,

The following book is returned (check-in) to the library for your card
number : <>

Accession No: <>
Call No: <>
Title: <>
Author: <>
Borrowed On : <>

Library and Informaiton Centre,
Your Library Name


3) Pre-Due Reminder ( Before Due Date)
--
Dear <> <>,

The following book will be due soon for your card number
<> :

Accession No: <> -  <>, by <>
Due Date: <>

Please return or renew them before due date.

Library and Informaiton Centre,
Your Library Name

Please do not reply to this notification as it was automatically generated.
If you have any question regarding this notification, please contact
Librarian
=

4) Due Reminder (After Due Date)
-

Dear <> <> CARD NUMBER
<>,

According to our current records, you have following book(s) that is/are
overdue. Please return or renew them at the Circulation section as soon as
possible.


Title: <>,  by <>
Accession No:  <>
Check out (Borrowed) date:  <>
Due Date:  <>


Library and Information Centre,
Your Library Name

Please do not reply to this notification as it was automatically generated.
If you have any question regarding this notification, please contact
Librarian.

==

5) Over Due (Final and Last Reminder)

Dear <> <>,

According to our Library records, you have books pending/overdue for your
card number : <> .  Please return or renew them as
soon as possible. There are two auto generated reminder emails have been
sent by the system to you regarding library dues.  Please refer previous
emails with the subject -  Item Due Reminder  or  Advance Notice of Item
Due"  for finding books details. Please note that, this is the final
reminder email.


Title: <>,  by <>
Accession No:  <>
Check out (Borrowed) date:  <>
Due Date:  <>


Library and Informaiton Centre,
Your Library Name

--

Hope, it help you to understand.

with thanks
Satish MV
Librarian
Govt. Engineering College, Hassan.
Karnataka.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Getting Elastic search 5.X working with authority searching and presentation in the Koha staff intranet

[Katrin]

Hi Dave,

it's always good to start with filing a bug report on bugzilla. I'd also 
suggest to review the existing bugs for Elasticsearch, to check if your 
problem has already been found and is being worked on. Testing some of 
those bugs would also help a lot!


There is an omnibus bug that will help you find other linked bugs 
relating to Elastic:


https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12478

And there is an Epic for Elasticsearch on our Kanban board:

https://tree.taiga.io/project/joubu-koha-rm-1711/epic/27

If you send an email to Jonathan Druart, he will send you an invitation 
so you can join the discussion.


Generally the koha-devel list is thought to be used for more technical 
questions.


Hope this helps!

Katrin


On 10.08.2017 13:24, David Holoshka wrote:

Hi,

We would like to see this feature working.  Do we just report what is 
not working in Bugzilla and submit patches for the items or is their 
some kind of coordination with other people that we need to take into 
account ?


Is there a plan or roadmap for elastic search work or do we just do 
what we want ?


Is this the right mailing group for this question ?

Best Regards,

Dave

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Getting Elastic search 5.X working with authority searching and presentation in the Koha staff intranet

[David Holoshka]

Hi,

We would like to see this feature working.  Do we just report what is 
not working in Bugzilla and submit patches for the items or is their 
some kind of coordination with other people that we need to take into 
account ?


Is there a plan or roadmap for elastic search work or do we just do what 
we want ?


Is this the right mailing group for this question ?

Best Regards,

Dave

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] E-mail configuration in koha version 3.0.6

[Bob Birchall]

Read the manual.  Look for:
- circulation alerts;
- overdue notices;
- email alerts and notices;
- triggers;
- email cron jobs.

Koha 3.0.6 is a very old version of Koha and is completely unsupported. 
It lacks features and contains bugs and security vulnerabilities. You 
should upgrade without delay.


Bob Birchall
Calyx

On 10/08/17 20:59, Dr. B. RAVIIVVENKAT wrote:

Dear Sir,

How to do E-mail ( for book remainder purpose) configuration in koha 3.0.6





*Dr. B. RaviivvenkatDeputy LibrarianUniversity LibraryTumkur University,
Tumakuru-572103. Joint-Secretary. KULA, Mysuru.Secretary, TUDLA, Tumakuru ,
Co-ordinator Shodhaganga*
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[Indranil Das Gupta]

For the longest time, I resisted getting listed on the PAID support
providers list because of personal reasons. But then I started running up
against RFPs that made listing there a mandatory qualification point for
placing a bid. Now that my outfit is there for quite some time, I can
honestly tell that not a *single* piece of work has landed from being
listed there. Sure there has been a few enquiries but that's the extent of
if.

The time when Koha needed the visibility of local support has largely
passed, at least in India where Koha has emerged as the defacto choice. On
the other hand, Indian service providers on that list make up ~25% (or
more) of the global listing in number, yet the number of contributions,
including patches have probably been the least. Most are not even active in
the community.

So I do not consider deletion of the page to do anyone any major
disservice, since we can't do anything about false claims - yes, several of
the Indian providers listed make tall claims of community contribution and
show the listing as being the proof. Surprise!!! No one reads the
disclaimers! :D

cheers
indranil

--
Indranil Das Gupta
L2C2 Technologies

Phone : +91-98300-20971
WWW  : http://www.l2c2.co.in
Blog: http://blog.l2c2.co.in
IRC : indradg on irc://irc.freenode.net
Twitter : indradg
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] E-mail configuration in koha version 3.0.6

[Dr. B. RAVIIVVENKAT]

Dear Sir,

How to do E-mail ( for book remainder purpose) configuration in koha 3.0.6





*Dr. B. RaviivvenkatDeputy LibrarianUniversity LibraryTumkur University,
Tumakuru-572103. Joint-Secretary. KULA, Mysuru.Secretary, TUDLA, Tumakuru ,
Co-ordinator Shodhaganga*
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[Michael Kuhn]

Hi



I think we can make a parameter like the company who have submitted at
least five patch/new code for major active release oldoldstable, oldstable
and stable will be only listed. For example if a company has five
code/patch in 16.5 than he may be listed continuously up-to 17.5 once 17.11
will release and there is no contribution in 16.11 than they may be delist.



This means everything else except writing patches is not considered as 
"help".


Best wishes: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
T 0041 (0)61 261 55 61 · E m...@adminkuhn.ch · W www.adminkuhn.ch
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[Indranil Das Gupta]

Vinod:

Koha like most successful FOSS projects, work on a "honour" system where
everyone is expected to do the right thing. We do have a "code-of-conduct"
but that is mostly about diversity and other issues.

Further, everyone who maintains the website do so as volunteers. Expecting
them to start acting as police is probably not the best of ideas. I know
for a fact that Liz stopped volunteering on the PAID provider section
maintenance as she was sick of dealing with it.

The "X" no. of patch criteria does not solve anything IMHO for several
reasons. Patches are not linear entities. Often they get to be completed
only with active contribution of others. Most often, the patches are
credited to individuals and not the companies they represent. So what
happens when an employee dev leave and say joins another Koha service
provider? Who will get the credits? It may sound easy, but its not so
legally. Then how does a patch say one that permanently addresses the
auto-increment issue compare against 5 trivial string patch?

Basically, do we become bureaucrats OR do we write Koha?

Just my 2c

-Indranil
On Aug 10, 2017 3:45 PM, "vinod mishra"  wrote:

> I think we can make a parameter like the company who have submitted at
> least five patch/new code for major active release oldoldstable, oldstable
> and stable will be only listed. For example if a company has five
> code/patch in 16.5 than he may be listed continuously up-to 17.5 once 17.11
> will release and there is no contribution in 16.11 than they may be delist.
>
> Above is only one parameter but someone have to monitor this continuously
> to update the list, however range of version can be increased, by doing so
> they will be encouraged to contribute continuously if they do not want to
> die from list.
>
>
> With Regards,
>
> Vinod Kumar Mishra,
> Assistant Librarian,
> Biju Patnaik Central Library (BPCL),
> NIT Rourkela,
> Sundergadh-769008,
> Odisha,
> India.
> Mob:91+9439420860
> Website: http://mishravk.com/
> ORCID ID: http://orcid.org/-0003-4666-7874
>
> *"Spiritual relationship is far more precious than physical. Physical
> relationship divorced from spiritual is body without soul" -- Mahatma
> Gandhi*
>
> On Wed, Aug 9, 2017 at 8:47 PM, Mark Tompsett 
> wrote:
>
> > Greetings,
> >
> > Nathan A. Curulla suggested:
> > > Maybe we should change the listing to “contributing support companies”
> or
> > > something like that.
> >
> > While I think that is a good idea, and then companies without community
> > participation get removed, the problem still remains: people don't read.
> > We've put a nice disclaimer that this is not an official list and has no
> > official seal of approval meaning to the list, and yet people still use
> it
> > that way. It is impossible to educate people who refuse to read, even
> > though
> > the preamble write up is a rather good explanation of how to look for a
> > Koha
> > support provider. As such, the only reasonable course of action is to
> > delete
> > the list, otherwise it will continue to be used that way, no matter what
> we
> > put on the page(s).
> >
> >
> > Owen Leonard wrote:
> > > It would be a duplicate listing ... and should be rejected.
> >
> > Who determines it is a duplicate listing? Because last time I looked some
> > other entries looked like duplicates to me, much like OpenLX/BBB. And
> > cleaning up duplicates is a pain. Yet another reason to just delete the
> > list
> > already.
> >
> > GPML,
> > Mark Tompsett
> >
> > ___
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > https://lists.katipo.co.nz/mailman/listinfo/koha
> >
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))

[vinod mishra]

I think we can make a parameter like the company who have submitted at
least five patch/new code for major active release oldoldstable, oldstable
and stable will be only listed. For example if a company has five
code/patch in 16.5 than he may be listed continuously up-to 17.5 once 17.11
will release and there is no contribution in 16.11 than they may be delist.

Above is only one parameter but someone have to monitor this continuously
to update the list, however range of version can be increased, by doing so
they will be encouraged to contribute continuously if they do not want to
die from list.


With Regards,

Vinod Kumar Mishra,
Assistant Librarian,
Biju Patnaik Central Library (BPCL),
NIT Rourkela,
Sundergadh-769008,
Odisha,
India.
Mob:91+9439420860
Website: http://mishravk.com/
ORCID ID: http://orcid.org/-0003-4666-7874

*"Spiritual relationship is far more precious than physical. Physical
relationship divorced from spiritual is body without soul" -- Mahatma
Gandhi*

On Wed, Aug 9, 2017 at 8:47 PM, Mark Tompsett  wrote:

> Greetings,
>
> Nathan A. Curulla suggested:
> > Maybe we should change the listing to “contributing support companies” or
> > something like that.
>
> While I think that is a good idea, and then companies without community
> participation get removed, the problem still remains: people don't read.
> We've put a nice disclaimer that this is not an official list and has no
> official seal of approval meaning to the list, and yet people still use it
> that way. It is impossible to educate people who refuse to read, even
> though
> the preamble write up is a rather good explanation of how to look for a
> Koha
> support provider. As such, the only reasonable course of action is to
> delete
> the list, otherwise it will continue to be used that way, no matter what we
> put on the page(s).
>
>
> Owen Leonard wrote:
> > It would be a duplicate listing ... and should be rejected.
>
> Who determines it is a duplicate listing? Because last time I looked some
> other entries looked like duplicates to me, much like OpenLX/BBB. And
> cleaning up duplicates is a pain. Yet another reason to just delete the
> list
> already.
>
> GPML,
> Mark Tompsett
>
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha