<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 8708 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 199, Issue 24<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. ElasticSearch Geoserch (Thomas Klausner)<br> 2. Re: ElasticSearch Geoserch (Stowasser Rainer)<br> 3. Re: ElasticSearch Geoserch (Uwe Dierolf)<br> 4. Re: ElasticSearch Geoserch (Thomas Klausner)<br> 5. Re: Gitlab policy changes (Tomas Cohen Arazi)<br> 6. Re: Gitlab policy changes (Victor Grousset/tuxayo)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Wed, 29 Jun 2022 12:04:39 +0200<br>From: Thomas Klausner <domm@plix.at><br>To: Koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] ElasticSearch Geoserch<br>Message-ID: <20220629100439.GD196434@plix.at><br>Content-Type: text/plain; charset=us-ascii<br><br>Hi!<br><br>We are currently discussing a project where a customer wants to add a <br>geosearch to Koha (store lat/lng in biblio, use Elastic geo queries [0] <br>together with a leaflet.js map to find biblios in a certain area).<br><br>I assume that might be of interest to Koha in general?<br><br>I also assume that this will only be possible via some changes to Koha <br>core code (i.e. adding a new search field to ES and Koha, define <br>mappings), while some things might be doable as a plugin (the "frontend" <br>map etc).<br><br>Before we start hacking I'd like to get some feedback from you:<br><br>* Would something like this be considered to be added to future Koha <br> versions?<br>* Do you think it's feasable / possible to add to Koha?<br>* Has anybody maybe done a geosearch before? (I couldn't find <br> anything..)<br><br>Greetings,<br>domm<br><br><br>0: https://www.elastic.co/guide/en/elasticsearch/reference/6.8/geo-queries.html<br><br>-- <br>#!/usr/bin/perl https://domm.plix.at<br>eor(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}<br><br><br>------------------------------<br><br>Message: 2<br>Date: Wed, 29 Jun 2022 10:17:07 +0000<br>From: Stowasser Rainer <rainer.stowasser@zamg.ac.at><br>To: Thomas Klausner <domm@plix.at>, Koha-devel<br> <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] ElasticSearch Geoserch<br>Message-ID: <951ff8886e04451c83fa1a8c9073a35f@zamg.ac.at><br>Content-Type: text/plain; charset="us-ascii"<br><br>So that you get a feeling what Thomas is talking about<br><br>I want this<br><br>https://gisgba.geologie.ac.at/geonames/<br><br>as open source solution in koha<br><br>The customer ;-)<br><br>Kind regards<br>Hofrat Mag. Rainer Stowasser<br>Head of Library and Archives ZAMG<br><br>________________________________________<br>Von: Koha-devel <koha-devel-bounces@lists.koha-community.org> im Auftrag von Thomas Klausner <domm@plix.at><br>Gesendet: Mittwoch, 29. Juni 2022 12:04:39<br>An: Koha-devel<br>Betreff: [Koha-devel] ElasticSearch Geoserch<br><br>Hi!<br><br>We are currently discussing a project where a customer wants to add a<br>geosearch to Koha (store lat/lng in biblio, use Elastic geo queries [0]<br>together with a leaflet.js map to find biblios in a certain area).<br><br>I assume that might be of interest to Koha in general?<br><br>I also assume that this will only be possible via some changes to Koha<br>core code (i.e. adding a new search field to ES and Koha, define<br>mappings), while some things might be doable as a plugin (the "frontend"<br>map etc).<br><br>Before we start hacking I'd like to get some feedback from you:<br><br>* Would something like this be considered to be added to future Koha<br> versions?<br>* Do you think it's feasable / possible to add to Koha?<br>* Has anybody maybe done a geosearch before? (I couldn't find<br> anything..)<br><br>Greetings,<br>domm<br><br><br>0: https://www.elastic.co/guide/en/elasticsearch/reference/6.8/geo-queries.html<br><br>--<br>#!/usr/bin/perl https://domm.plix.at<br>eor(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}<br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br>EXTERNAL EMAIL: Do not click any links or open any attachments unless you trust the sender and know the content is safe.<br><br><br><br><br>------------------------------<br><br>Message: 3<br>Date: Wed, 29 Jun 2022 12:22:32 +0200<br>From: Uwe Dierolf <uwe.dierolf@kit.edu><br>To: Thomas Klausner <domm@plix.at>,<br> koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] ElasticSearch Geoserch<br>Message-ID: <20220629102232.GD619296@ubka.uni-karlsruhe.de><br>Content-Type: text/plain; charset=iso-8859-1<br><br>Hi there,<br><br>we already implemented something like this and are using it within Primo.<br><br>Try it and go to<br> https://primo.bibliothek.kit.edu/primo-explore/search?tab=kit&sortby=date&vid=KIT<br>Then search for "php head first" and take the second hit (german book)<br>On the full title you see the typical google maps "mark a position" icons in read, click on them<br><br><br>Best regards, Uwe <br><br>--------------------------------------------------------------------------<br>Karlsruhe Institute of Technology (KIT)<br>KIT-Library<br>Dipl.-Inform. Uwe Dierolf<br>Straße am Forum 2<br>Geb. 30.50, Raum 628.1<br>76131 Karlsruhe - Germany<br>+49 721 608-46076<br>uwe.dierolf@kit.edu<br>--------------------------------------------------------------------------<br><br>Am Wed, Jun 29, 2022 at 12:04:39PM +0200 schrieb Thomas Klausner:<br>> Hi!<br>> <br>> We are currently discussing a project where a customer wants to add a <br>> geosearch to Koha (store lat/lng in biblio, use Elastic geo queries [0] <br>> together with a leaflet.js map to find biblios in a certain area).<br>> <br>> I assume that might be of interest to Koha in general?<br>> <br>> I also assume that this will only be possible via some changes to Koha <br>> core code (i.e. adding a new search field to ES and Koha, define <br>> mappings), while some things might be doable as a plugin (the "frontend" <br>> map etc).<br>> <br>> Before we start hacking I'd like to get some feedback from you:<br>> <br>> * Would something like this be considered to be added to future Koha <br>> versions?<br>> * Do you think it's feasable / possible to add to Koha?<br>> * Has anybody maybe done a geosearch before? (I couldn't find <br>> anything..)<br>> <br>> Greetings,<br>> domm<br>> <br>> <br>> 0: https://www.elastic.co/guide/en/elasticsearch/reference/6.8/geo-queries.html<br>> <br>> -- <br>> #!/usr/bin/perl https://domm.plix.at<br>> eor(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}<br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>Message: 4<br>Date: Wed, 29 Jun 2022 12:35:00 +0200<br>From: Thomas Klausner <domm@plix.at><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] ElasticSearch Geoserch<br>Message-ID: <20220629103500.GE196434@plix.at><br>Content-Type: text/plain; charset=us-ascii<br><br>Hi!<br><br>On Wed, Jun 29, 2022 at 12:22:32PM +0200, Uwe Dierolf wrote:<br> <br>> we already implemented something like this and are using it within Primo.<br>> <br>> Try it and go to<br>> https://primo.bibliothek.kit.edu/primo-explore/search?tab=kit&sortby=date&vid=KIT<br>> Then search for "php head first" and take the second hit (german book)<br>> On the full title you see the typical google maps "mark a position" icons in read, click on them<br><br>Nice!<br><br>Though what we're trying to do - as pointed out by Rainer aka "the <br>customer" :-) - is to show what area / location is relevant to the <br>contents of the book, not where the physical copy of the book is <br>located.<br><br>Here's more context, which should be ok to "leak" as Rainer also posted <br>the URL of the current system:<br><br>The library in question collects geological books / articles, most of <br>which discuss a very specific area. They want to list all books <br>thematically linked to an area:<br><br>https://gisgba.geologie.ac.at/geonames/<br>Enter "Znaim", hit enter, wait a bit. You'll see a map of Znojmo and <br>surrounding areas. Click on one of the red dots, and in the popup on <br>"view more" => A new tab opens showing books about "Znojmo".<br><br>Greetings,<br>domm<br><br>-- <br>#!/usr/bin/perl https://domm.plix.at<br>for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}<br><br><br>------------------------------<br><br>Message: 5<br>Date: Wed, 29 Jun 2022 10:11:47 -0300<br>From: Tomas Cohen Arazi <tomascohen@gmail.com><br>To: "Victor Grousset/tuxayo" <victor@tuxayo.net><br>Cc: Jonathan Druart <jonathan.druart@bugs.koha-community.org>,<br> koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Gitlab policy changes<br>Message-ID:<br> <CABZfb=V8GrSu3yUHNyRweCDSXCKQBdeZ9v2nQH2Yy50-Z0st1Q@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all, I have submitted the form, and also contacted the sales department<br>so we can explain how the project management works and to clarify any<br>doubts. I will add others to the conversation once I get the call with the<br>sales people.<br><br>Thanks everyone.<br><br>El mié, 29 jun 2022 a las 0:37, Victor Grousset/tuxayo (<victor@tuxayo.net>)<br>escribió:<br><br>> On 22-06-28 10:23, Jonathan Druart wrote:<br>> > Sorry for the late reply, I didn't really know what to say. As I was<br>> > involved earlier in the discussion I feel that by not replying, I am<br>> > agreeing with your message, Victor.<br>><br>> No worries, I think no one in the discussion was to be assumed to agree<br>> with the idea that it would be a scam attempt to apply as is for the<br>> non-profit program. Because for that someone must agree that we do not<br>> fit at all with the non profit criteria for maintainers. That's the main<br>> point of the message and necessary condition before starting to talk<br>> about the scam thing.<br>> And it seems everyone leans towards that we fit. So if anything to<br>> assume, is that everyone was leaning towards agreeing to apply in good<br>> faith without being a attempt to trick GitLab, thinking that we fit<br>> enough in the criteria.<br>><br>> > However I do not agree at all.<br>> > I do not recognize myself in your words<br>><br>> That's fine, it's my own view that we don't fit and the arguments to<br>> apply anyway with less moral remorse are only mine.<br>><br>> > and I do not think "scamming gitlab" is a point of the discussion.<br>> > The matter is to know if we are eligible for a program they support,<br>> > and find the best way to apply in agreement with their terms and our<br>> > project's view.<br>><br>> Alright, looks good that way, I had to think hard to find moral<br>> justifications to apply as is without complying to their terms.<br>> (Assuming we would lean toward that we don't fit at all with their terms.)<br>> My feelings when reading the discussion were that bringing up Koha<br>> Community as an organization or Horowhenua Library Trust was very<br>> dubious and that we should be upfront that it would be a dubious<br>> application to their program. Thus the scam thing.<br>><br>> > We are relying quite a lot on gitlab, and I personally think the open<br>> > source product they provide is great. I thank their team for that.<br>> ><br>> > With this answer, I only wanted to take distance with your words.<br>><br>> What about the main point of the message? My most important words are<br>> that we don't fit at all with their terms. (details in previous message)<br>> Sorry that I went too far developing the scam thing that it took all the<br>> attention.<br>><br>> Cheers,<br>><br>> --<br>> Victor Grousset/tuxayo<br>> _______________________________________________<br>> Koha-devel mailing list<br>> Koha-devel@lists.koha-community.org<br>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>> website : https://www.koha-community.org/<br>> git : https://git.koha-community.org/<br>> bugs : https://bugs.koha-community.org/<br>><br><br><br>-- <br>Tomás Cohen Arazi<br>Theke Solutions (http://theke.io)<br>✆ +54 9351 3513384<br>GPG: B2F3C15F<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220629/e75a7f0b/attachment-0001.htm><br><br>------------------------------<br><br>Message: 6<br>Date: Wed, 29 Jun 2022 20:24:57 +0200<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: dcook@prosentient.com.au<br>Cc: 'koha-devel' <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Gitlab policy changes<br>Message-ID: <57b3eb05-e6a3-0c9a-387c-ece4a21740d0@tuxayo.net><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>On 22-06-29 04:00, dcook@prosentient.com.au wrote:<br>> [...] <br>> Victor, I'm not going to try to respond line by line to your message,<br><br>No worries, what about the main point of my 1st message? That we don't <br>fit at all with their terms when looking at our roles list no matter how <br>we define maintainers.<br><br>> but I will say that everyone (myself included) has just been genuinely trying to interpret Gitlab's policy and how it applies to Koha; no one is trying to mislead anyone. The Koha community is the most good natured group of people that I've ever known in my entire life.<br><br>Sorry that I have made many people uncomfortable.<br><br>When I said «In practice we would be trying to scam GitLab.com» it was <br>in «You don't realize it but it's misleading». Not «You are consciously <br>and malevolently thinking to mislead them»<br><br><br>> [...]<br>> <br>> Anyway, I think that Tomas is going to try reaching out to Gitlab for more information, so we'll see what they say. Ultimately, we can speculate one way or another all we want, but it's up to Gitlab to say whether or not we fit, and I think that you can rest assured that we'll be open and honest with whatever information that they want to support their decision-making.<br><br>Bringing up HLT or Koha Community as non profit organization to be able <br>to tick the box<br>«project maintainers are not seeking to make profit from this project by <br>for example, selling services [...]» didn't look like<br>«you can rest assured that we'll be open and honest with whatever <br>information that they want to support their decision-making»<br><br>Instead I though we gotta be upfront with ourselves if we were going <br>that way which seemed misleading to me. (to bend so much things so they <br>fit) And that we needed to find reasons to be morally ok with that.<br><br>Cheers,<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 199, Issue 24<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>