<!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 6715 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 203, Issue 11<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. Re: Koha-devel Digest, Vol 203, Issue 10 (Jacob Jett)<br> 2. Shortcodes in HTML areas (David Cook)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 18 Oct 2022 07:40:48 -0500<br>From: Jacob Jett <jacob@floods.org><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] Koha-devel Digest, Vol 203, Issue 10<br>Message-ID:<br> <CALBv4=rp_FojGsCL67vACFdAdfAQGojYzQrbqMW8A15okqVaLg@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi Katrin,<br><br>It could be the case that it is tied to some localized configuration that<br>we're using. Regardless, my worry is that changes to MARC may cause<br>trickle-down changes to our implementation of Koha.<br><br>Additional context, I'm new to my position, less than 12 weeks here. But<br>the non-profit I work for has been using Koha for many years, so it's quite<br>possible, likely even, that the institutional knowledge about our<br>implementation has evaporated. I discovered the recent LoC change to 856<br>while researching our 2nd issue. How to ensure that the links for cover<br>thumbnail images coming out of Koha have the alt text necessary for<br>accessibility compliance.<br><br>Regards,<br><br>Jacob<br><br>*Jacob Jett* | Research Librarian | ASFPM<br>8301 Excelsior Dr. | Madison, WI 53717<br>tel: 608-828-3000 | desk: 608-828-6342 | floods.org<br><http://www.floods.org/> | *Email Jacob <jacob@floods.org>*<br><br><br>On Tue, Oct 18, 2022 at 5:00 AM <koha-devel-request@lists.koha-community.org><br>wrote:<br><br>> 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>><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. Koha 22.11 - Release dates (Tomas Cohen Arazi)<br>> 2. question about MARC 856 $e (Jacob Jett)<br>> 3. Re: question about MARC 856 $e (Katrin Fischer)<br>><br>><br>> ----------------------------------------------------------------------<br>><br>> Message: 1<br>> Date: Mon, 17 Oct 2022 11:37:32 -0300<br>> From: Tomas Cohen Arazi <tomascohen@gmail.com><br>> To: koha-devel <koha-devel@lists.koha-community.org><br>> Subject: [Koha-devel] Koha 22.11 - Release dates<br>> Message-ID:<br>> <CABZfb=UOZRYj+kcKzMTjkN3xYQxqPyeFR83cyw_FRsqS=<br>> txYbA@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>><br>> Hi all, this cycle has been very busy and all of a sudden, it is ending!<br>><br>> This are the preliminary dates so you are aware of:<br>><br>> * Oct 28th - "Soft" feature freeze, nothing big or with high risk of<br>> side-effects will be included into the final release if not marked<br>> as Passed QA<br>> * Nov 3-5 - "Hard" feature freeze, nothing considered as an improvement<br>> will be pushed if not marked as Passed QA<br>> * Nov 10th - String freeze, draft of release notes published<br>> * Nov 17th - Only bug fixes considered major, critical or blocker will be<br>> pushed<br>> * Nov 25th - Final release<br>><br>> PM me if you have any comments.<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: <<br>> http://lists.koha-community.org/pipermail/koha-devel/attachments/20221017/541e5c2d/attachment-0001.htm<br>> ><br>><br>> ------------------------------<br>><br>> Message: 2<br>> Date: Mon, 17 Oct 2022 15:02:32 -0500<br>> From: Jacob Jett <jacob@floods.org><br>> To: koha-devel@lists.koha-community.org<br>> Subject: [Koha-devel] question about MARC 856 $e<br>> Message-ID:<br>> <CALBv4=<br>> qRZ5rR1fNsr7tgpWQsBPWRwbs8oGY5v-xEFSJEPVhCaA@mail.gmail.com><br>> Content-Type: text/plain; charset="utf-8"<br>><br>> Hi gang,<br>><br>> Some context, I'm asking these questions because our organization has been<br>> using the 856 $e field to display cover images to users searching the<br>> catalog. I have questions regarding this practice:<br>><br>> 1) I see that the nature of 856 $e was changed to record data provenance<br>> metadata by the Library of Congress this year. Will there be a new place to<br>> use for linking cover images? E.g., is Koha going to be developing a<br>> specific 9XX field for the purpose or will there be a way for individual<br>> libraries to define a field that does the same thing as the pre-2022 856 $e<br>> did? (I'm assuming that an update that applies recent changes to MARC21<br>> will eventually get globally pushed out.)<br>><br>> 2) Accessibility and image alt text--is there a way to add alt text to the<br>> metadata such that accessibility widgets and software encountering images<br>> like shared cover images can grab the alt text for those images?<br>><br>> Thank you in advance for your answers.<br>><br>> Regards,<br>><br>> Jacob<br>><br>> *Jacob Jett* | Research Librarian | ASFPM<br>> 8301 Excelsior Dr. | Madison, WI 53717<br>> tel: 608-828-3000 | desk: 608-828-6342 | floods.org<br>> <http://www.floods.org/> | *Email Jacob <jacob@floods.org>*<br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <<br>> http://lists.koha-community.org/pipermail/koha-devel/attachments/20221017/1190e4b3/attachment-0001.htm<br>> ><br>><br>> ------------------------------<br>><br>> Message: 3<br>> Date: Mon, 17 Oct 2022 22:27:41 +0200<br>> From: Katrin Fischer <katrin.fischer.83@web.de><br>> To: koha-devel@lists.koha-community.org<br>> Subject: Re: [Koha-devel] question about MARC 856 $e<br>> Message-ID: <633b51a7-9195-d6cf-84cf-cb2d161926af@web.de><br>> Content-Type: text/plain; charset="utf-8"; Format="flowed"<br>><br>> Hi Jacob,<br>><br>> I have to admit, I am not aware of a feature in Koha that uses 856 $e to<br>> display cover images. Can you elaborate a bit on your use of it? Is it<br>> linked to a system preference maybe?<br>><br>> Katrin<br>><br>><br>> On 17.10.22 22:02, Jacob Jett wrote:<br>> > Hi gang,<br>> ><br>> > Some context, I'm asking these questions because our organization has<br>> > been using the 856 $e field to display cover images to users searching<br>> > the catalog. I have questions regarding this practice:<br>> ><br>> > 1) I see that the nature of 856 $e was changed to record data<br>> > provenance metadata by the Library of Congress this year. Will there<br>> > be a new place to use for linking cover images? E.g., is Koha going to<br>> > be developing a specific 9XX field for the purpose or will there be a<br>> > way for individual libraries to define a field that does the same<br>> > thing as the pre-2022 856 $e did? (I'm assuming that an update that<br>> > applies recent changes to MARC21 will eventually get globally pushed<br>> out.)<br>> ><br>> > 2) Accessibility and image alt text--is there a way to add alt text to<br>> > the metadata such that accessibility widgets and software encountering<br>> > images like shared cover images can grab the alt text for those images?<br>> ><br>> > Thank you in advance for your answers.<br>> ><br>> > Regards,<br>> ><br>> > Jacob<br>> ><br>> > *Jacob Jett*| Research Librarian | ASFPM<br>> > 8301 Excelsior Dr. | Madison, WI 53717<br>> > tel: 608-828-3000 | desk: 608-828-6342 | floods.org<br>> > <http://www.floods.org/> | _Email Jacob <mailto:jacob@floods.org>_<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>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: <<br>> http://lists.koha-community.org/pipermail/koha-devel/attachments/20221017/f771ec19/attachment-0001.htm<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 203, Issue 10<br>> *******************************************<br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221018/4f2ff43d/attachment-0001.htm><br><br>------------------------------<br><br>Message: 2<br>Date: Wed, 19 Oct 2022 13:58:13 +1100<br>From: "David Cook" <dcook@prosentient.com.au><br>To: "'koha-devel'" <koha-devel@lists.koha-community.org><br>Cc: "'Kyle Hall'" <kyle@bywatersolutions.com><br>Subject: [Koha-devel] Shortcodes in HTML areas<br>Message-ID: <01f701d8e366$a4ce9140$ee6bb3c0$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all,<br><br> <br><br>I've been working with Wordpress plugins lately, and I've been thinking how<br>the Wordpress shortcodes are really handy. They let you easily inject<br>content from a plugin into any content area in Wordpress just by including<br>something like "[my_search_results]". <br><br> <br><br>One use would be for Koha plugins to inject content. For something like<br>Bywater's Coverflow, that could be quite interesting. It could also make it<br>easier to inject content from plugins without having to rely on Javascript<br>(although using Javascript with Koha plugin REST API routes is very nice). <br><br> <br><br>I was thinking it could be useful for moving around core Koha blocks of<br>content like "Quote of the day", so the response is generated server-side<br>but is still easily customizable. <br><br> <br><br>Anyway, it's just a thought.<br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221019/e71dc4dd/attachment.htm><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 203, Issue 11<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>