[Koha] Number of Koha Libraries in the World

[Mirko Tietgen]

Hi,

Chris Cormack schrieb am 13.12.2016
> I'm happy to volunteer to do all of those tasks.

Cool!

> CC-BY-SA is the license I would suggest, does anyone have objections?  Adding a method to retrieve the data is easy.

Sounds good to me.

> And the rest I can write because I can see all the code so can write up exactly what is stored and how.

Yes, I know "everyone" can do it, in theory ;) Lacking the time to
do it myself though.

> As to the why for the sysprefs it's really useful when we are doing the should we deprecate this feature, is anyone using it question. So I can write that up too.

Makes sense, I have not thought about that.

> Should be done within a day or 2.

Wow. Thanks! I'm happy to write up something in German about it
based on that.

-- Mirko



> Chris
> 
> 
> On 14 December 2016 6:10:20 AM NZDT, Mirko Tietgen <mirko at abunchofthings.net> wrote:
>> Hi.
>>
>> it needs privacy information. What is anonymized, where and when?
>> Who has access to non-anonymised data (if anyone)?
>>
>> It needs an imprint/statement of responsibility on the website. Who
>> is responsible for gathering and processing the data, and for
>> anonymizing it? Where is the data stored?
>>
>> It needs a license. Saying it is open data does not make it open, I
>> can't find a license except for the hea code.
>>
>> It needs actual data to download, or it is not open data but some
>> graphs someone somewhere renders with data they pile up secretly.
>>
>> It needs information about why a gazillion sysprefs are gathered, be
>> that anonymized or not, and probably an option to turn that off.
>>
>> Just a pile of German 2€cents with basic questions nobody is going
>> to ask, but just not turn on the data collection. I'm asking it so
>> at some point I might be able to recommend turning it on, which so
>> far I don't, because I doubt it is compatible to German data privacy
>> laws.
>>
>> -- Mirko
>>
>> PS: Yes for the open vs proprietary part. I just don't think we are
>> there yet.
>>
>>
>>
>>
>> Chris Cormack schrieb am 13.12.2016
>>> I agree, we could make the installer/upgrade prompt them to fill them
>> in also.
>>>
>>> And then it's just building an interface, if we can get JSON from Hea
>> then that part is easy. It then needs no work from users except to fill
>> in the sysprefs.
>>>
>>> Chris
>>>
>>>
>>> On 14 December 2016 5:31:01 AM NZDT, Jonathan Druart
>> <jonathan.druart at bugs.koha-community.org> wrote:
>>>> The easiest way in my opinion would be to improve Hea, we already
>> have
>>>> Koha
>>>> instances sending their data.
>>>> It is very easy for libraries to register as they just need to fill
>>>> some
>>>> sysprefs in.
>>>>
>>>> On Tue, 13 Dec 2016 at 17:04 Nathan Curulla
>> <nate at bywatersolutions.com>
>>>> wrote:
>>>>
>>>>> Hi Everyone,
>>>>>
>>>>> I hear what you are all saying about this and agree that it would
>> be
>>>>> better to roll our own, but here is the thing: Hea is not user
>>>> friendly at
>>>>> all and the Wiki is not a good marketing tool because it is not
>>>> pretty (no
>>>>> offense on either of these). If you really want to market Koha you
>>>> need to
>>>>> look at these things from the eyes of a non-developer, non-tech
>>>> oriented
>>>>> librarian. If you do that you will see that these two tools are not
>>>>> optimal, especially in comparison to something that larger
>> companies
>>>> that
>>>>> Koha competes with are going to put out.
>>>>>
>>>>> It is good to hear that you want to clean things up and re-invent
>> the
>>>>> wheel, but actually doing that in a reasonable amount of time in a
>>>>> competitive environment is another thing. If someone has a concrete
>>>>> proposal for an attractive, sortable, searchable, easy to submit to
>>>> option
>>>>> on the website for libraries to put information in than I think
>> that
>>>> would
>>>>> be great and I will do everything to help that I can, but who is
>>>> going to
>>>>> do it and when? With products like Folio coming Koha needs to be
>>>> front and
>>>>> center in the open source library world and showing the world how
>>>> many
>>>>> people use it is a no brainer (and should be easy) in terms of ways
>>>> to do
>>>>> just that.
>>>>>
>>>>> So the options are that someone volunteers to create this interface
>>>>> (ByWater staff can help with this if given the access and
>> permission,
>>>> but
>>>>> we aren’t going to do it alone) with a completion target of end of
>>>> Feb.
>>>>> 2017, or we link out to a third party site that already has the
>>>> content. If
>>>>> we don’t hear from anyone about the former we are going to go with
>>>> the
>>>>> latter. We need to move on this kind of stuff soon or Koha will be
>>>> left in
>>>>> the dust in the coming emergence of open source in the library
>> world.
>>>> We
>>>>> need to become more accessible to those who don’t code, otherwise
>> we
>>>> are
>>>>> playing into the misconception that open source is for developers
>>>> only.
>>>>>
>>>>> Respectfully,
>>>>>
>>>>> -Nate
>>>>>
>>>>>> Nathan A. Curulla
>>>>>> Owner, CRO
>>>>>> ByWater Solutions
>>>>>> Support and Consulting for Open Source Software
>>>>>> Headquarters: Portland, OR.
>>>>>> East Coast Office: Redding, CT.
>>>>>> Phone/Fax # (888) 900-8944 xt 2
>>>>>> Cell # (203) 685-7207
>>>>>
>>>>>> http://bywatersolutions.com <http://bywatersolutions.com/>
>>>>>> nate at bywatersolutions.com <mailto:nate at bywatersolutions.com>
>>>>> _______________________________________________
>>>>> Koha mailing list  http://koha-community.org
>>>>> Koha at lists.katipo.co.nz
>>>>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>>>>
>>>> _______________________________________________
>>>> Koha mailing list  http://koha-community.org
>>>> Koha at lists.katipo.co.nz
>>>> https://lists.katipo.co.nz/mailman/listinfo/koha
>>>
>>
>>
>> _______________________________________________
>> Koha mailing list  http://koha-community.org
>> Koha at lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>