Send Koha-devel mailing list submissions to
    koha-devel@lists.koha-community.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
    koha-devel-request@lists.koha-community.org

You can reach the person managing the list at
    koha-devel-owner@lists.koha-community.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."


Today's Topics:

1. Google showing "Borrow" option for nearby public libraries
(dcook@prosentient.com.au)
2. Re: Google showing "Borrow" option for nearby public
libraries (Tomas Cohen Arazi)
3. Re: Google showing "Borrow" option for nearby public
libraries (dcook@prosentient.com.au)
4. Collecting ideas to have an easier time with large patch
submissions. And inventory of large submissions that are stuck.
(Victor Grousset/tuxayo)


----------------------------------------------------------------------

Message: 1
Date: Tue, 19 Apr 2022 12:03:38 +1000
From: <dcook@prosentient.com.au>
To: "'koha-devel'" <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Google showing "Borrow" option for nearby public
    libraries
Message-ID: <00a501d85391$b11a3e00$134eba00$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"

Hi all,



I was looking up a book the other day on Google when I noticed a section
called "Borrow" and it showed two local library services where I could
borrow the book.



I did a bit more Googling today and noticed this:
https://developers.google.com/search/docs/advanced/structured-data/book



It looks like individual libraries would need to register their interest
first, but after that the system would need to serve a feed file that Google
would regularly harvest.



Does anyone have a Koha library where they're currently doing this? It could
make for an interesting Koha plugin.



David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia



Office: 02 9212 0899

Online: 02 8005 0595



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220419/83456974/attachment-0001.htm>

------------------------------

Message: 2
Date: Mon, 18 Apr 2022 23:20:40 -0300
From: Tomas Cohen Arazi <tomascohen@gmail.com>
To: David Cook <dcook@prosentient.com.au>
Cc: koha-devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Google showing "Borrow" option for nearby
    public libraries
Message-ID:
    <CABZfb=X4+KiMa1=s3Awi1Pru_nDB+xa4tsupKHCMbk6JSMg1Pw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I'd say it is a neat core feature as well! Nice finding!!

El lun, 18 abr 2022 23:04, <dcook@prosentient.com.au> escribió:

> Hi all,
>
>
>
> I was looking up a book the other day on Google when I noticed a section
> called “Borrow” and it showed two local library services where I could
> borrow the book.
>
>
>
> I did a bit more Googling today and noticed this:
> https://developers.google.com/search/docs/advanced/structured-data/book
>
>
>
> It looks like individual libraries would need to register their interest
> first, but after that the system would need to serve a feed file that
> Google would regularly harvest.
>
>
>
> Does anyone have a Koha library where they’re currently doing this? It
> could make for an interesting Koha plugin.
>
>
>
> David Cook
>
> Senior Software Engineer
>
> Prosentient Systems
>
> Suite 7.03
>
> 6a Glen St
>
> Milsons Point NSW 2061
>
> Australia
>
>
>
> Office: 02 9212 0899
>
> Online: 02 8005 0595
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220418/ca5c39e4/attachment-0001.htm>

------------------------------

Message: 3
Date: Tue, 19 Apr 2022 12:31:32 +1000
From: <dcook@prosentient.com.au>
To: "'Tomas Cohen Arazi'" <tomascohen@gmail.com>
Cc: "'koha-devel'" <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Google showing "Borrow" option for nearby
    public libraries
Message-ID: <00b501d85395$95a7bc20$c0f73460$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"

Thanks!



Here’s an example of the links that I see where <ISBN> is replaced with the ISBN of what you’re searching:



http://link.randwick.nsw.gov.au/id/isbn/<ISBN>/resource/borrow?share=g



The two library councils I’m seeing both use the same library system but they belong to different local government entities (one in the east and one in the west). The URLs are government URLs, but I imagine it was the ILS/LMS vendor who spear-headed the effort.



David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia



Office: 02 9212 0899

Online: 02 8005 0595



From: Tomas Cohen Arazi <tomascohen@gmail.com>
Sent: Tuesday, 19 April 2022 12:21 PM
To: David Cook <dcook@prosentient.com.au>
Cc: koha-devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] Google showing "Borrow" option for nearby public libraries



I'd say it is a neat core feature as well! Nice finding!!



El lun, 18 abr 2022 23:04, <dcook@prosentient.com.au <mailto:dcook@prosentient.com.au> > escribió:

Hi all,



I was looking up a book the other day on Google when I noticed a section called “Borrow” and it showed two local library services where I could borrow the book.



I did a bit more Googling today and noticed this: https://developers.google.com/search/docs/advanced/structured-data/book



It looks like individual libraries would need to register their interest first, but after that the system would need to serve a feed file that Google would regularly harvest.



Does anyone have a Koha library where they’re currently doing this? It could make for an interesting Koha plugin.



David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia



Office: 02 9212 0899

Online: 02 8005 0595



_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org>
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220419/95863bd8/attachment-0001.htm>

------------------------------

Message: 4
Date: Tue, 19 Apr 2022 05:00:06 +0200
From: Victor Grousset/tuxayo <victor@tuxayo.net>
To: koha-devel <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Collecting ideas to have an easier time with
    large patch submissions. And inventory of large submissions that are
    stuck.
Message-ID: <68196e45-4d6f-b4d3-8545-51cb58db5cb6@tuxayo.net>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi :)

At the development IRC meeting of 6 April 2022 it was discussed what
could be done to help large developments better move forward using the
recent experience with recalls patches (bug 19532).

Here is what came out of it:
- resist scope creep and ask only for necessary changes for inclusion
(Minimun Viable Product)
- ask to focus discussions on concrete actions for the dev to reach an
acceptable MVP
- note somewhere all the potential follow ups ideas so that they don't
get lost and it easier to move on knowing they are somewhere not lost
- bring the development as a topic in meetings and QA team discussions
to get focus on it

What do you think of these? Any other ideas/guidelines to complete this?

What are the large patch submissions that are stuck that you know about?
If you could send messages in the past in the ticket, what would you
sent that would have hopefully helped it move forward?


Here are some other ideas:

- When submitting large changes, submit a minimal version first if
possible and if a more complete version might be too much. Even if it
will be hard to maintain a separate more complete version for your
customers. If it gets stuck, it will be worse than doing it in chunks.
- Maybe reboot a submission on a new ticket with a chopped down version
if noticing you should have went for the previous guideline.
- Maybe propose taking on testing complicated stuff of someone else if
they do the same for your submission. It will be worth your time if it
avoids being stuck for months/years with dozens of rebases on the ticket
plus on your customer's Kohas due to it being a effectively a fork.


Cheers,

--
Victor Grousset/tuxayo


------------------------------

Subject: Digest Footer

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/


------------------------------

End of Koha-devel Digest, Vol 197, Issue 8
******************************************