Hi Katrin, It could be the case that it is tied to some localized configuration that we're using. Regardless, my worry is that changes to MARC may cause trickle-down changes to our implementation of Koha.
Additional context, I'm new to my position, less than 12 weeks here. But the non-profit I work for has been using Koha for many years, so it's quite possible, likely even, that the institutional knowledge about our implementation has evaporated. I discovered the recent LoC change to 856 while researching our 2nd issue. How to ensure that the links for cover thumbnail images coming out of Koha have the alt text necessary for accessibility compliance. Regards, Jacob *Jacob Jett* | Research Librarian | ASFPM 8301 Excelsior Dr. | Madison, WI 53717 tel: 608-828-3000 | desk: 608-828-6342 | floods.org <http://www.floods.org/> | *Email Jacob <ja...@floods.org>* On Tue, Oct 18, 2022 at 5:00 AM <koha-devel-requ...@lists.koha-community.org> wrote: > 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-requ...@lists.koha-community.org > > You can reach the person managing the list at > koha-devel-ow...@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. Koha 22.11 - Release dates (Tomas Cohen Arazi) > 2. question about MARC 856 $e (Jacob Jett) > 3. Re: question about MARC 856 $e (Katrin Fischer) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 17 Oct 2022 11:37:32 -0300 > From: Tomas Cohen Arazi <tomasco...@gmail.com> > To: koha-devel <koha-devel@lists.koha-community.org> > Subject: [Koha-devel] Koha 22.11 - Release dates > Message-ID: > <CABZfb=UOZRYj+kcKzMTjkN3xYQxqPyeFR83cyw_FRsqS= > tx...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi all, this cycle has been very busy and all of a sudden, it is ending! > > This are the preliminary dates so you are aware of: > > * Oct 28th - "Soft" feature freeze, nothing big or with high risk of > side-effects will be included into the final release if not marked > as Passed QA > * Nov 3-5 - "Hard" feature freeze, nothing considered as an improvement > will be pushed if not marked as Passed QA > * Nov 10th - String freeze, draft of release notes published > * Nov 17th - Only bug fixes considered major, critical or blocker will be > pushed > * Nov 25th - Final release > > PM me if you have any comments. > > -- > Tomás Cohen Arazi > Theke Solutions (http://theke.io) > ✆ +54 9351 3513384 > GPG: B2F3C15F > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.koha-community.org/pipermail/koha-devel/attachments/20221017/541e5c2d/attachment-0001.htm > > > > ------------------------------ > > Message: 2 > Date: Mon, 17 Oct 2022 15:02:32 -0500 > From: Jacob Jett <ja...@floods.org> > To: koha-devel@lists.koha-community.org > Subject: [Koha-devel] question about MARC 856 $e > Message-ID: > <CALBv4= > qrz5rr1fnsr7tgpwqsbpwrwbs8ogy5v-xefsjepvh...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi gang, > > Some context, I'm asking these questions because our organization has been > using the 856 $e field to display cover images to users searching the > catalog. I have questions regarding this practice: > > 1) I see that the nature of 856 $e was changed to record data provenance > metadata by the Library of Congress this year. Will there be a new place to > use for linking cover images? E.g., is Koha going to be developing a > specific 9XX field for the purpose or will there be a way for individual > libraries to define a field that does the same thing as the pre-2022 856 $e > did? (I'm assuming that an update that applies recent changes to MARC21 > will eventually get globally pushed out.) > > 2) Accessibility and image alt text--is there a way to add alt text to the > metadata such that accessibility widgets and software encountering images > like shared cover images can grab the alt text for those images? > > Thank you in advance for your answers. > > Regards, > > Jacob > > *Jacob Jett* | Research Librarian | ASFPM > 8301 Excelsior Dr. | Madison, WI 53717 > tel: 608-828-3000 | desk: 608-828-6342 | floods.org > <http://www.floods.org/> | *Email Jacob <ja...@floods.org>* > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.koha-community.org/pipermail/koha-devel/attachments/20221017/1190e4b3/attachment-0001.htm > > > > ------------------------------ > > Message: 3 > Date: Mon, 17 Oct 2022 22:27:41 +0200 > From: Katrin Fischer <katrin.fischer...@web.de> > To: koha-devel@lists.koha-community.org > Subject: Re: [Koha-devel] question about MARC 856 $e > Message-ID: <633b51a7-9195-d6cf-84cf-cb2d16192...@web.de> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi Jacob, > > I have to admit, I am not aware of a feature in Koha that uses 856 $e to > display cover images. Can you elaborate a bit on your use of it? Is it > linked to a system preference maybe? > > Katrin > > > On 17.10.22 22:02, Jacob Jett wrote: > > Hi gang, > > > > Some context, I'm asking these questions because our organization has > > been using the 856 $e field to display cover images to users searching > > the catalog. I have questions regarding this practice: > > > > 1) I see that the nature of 856 $e was changed to record data > > provenance metadata by the Library of Congress this year. Will there > > be a new place to use for linking cover images? E.g., is Koha going to > > be developing a specific 9XX field for the purpose or will there be a > > way for individual libraries to define a field that does the same > > thing as the pre-2022 856 $e did? (I'm assuming that an update that > > applies recent changes to MARC21 will eventually get globally pushed > out.) > > > > 2) Accessibility and image alt text--is there a way to add alt text to > > the metadata such that accessibility widgets and software encountering > > images like shared cover images can grab the alt text for those images? > > > > Thank you in advance for your answers. > > > > Regards, > > > > Jacob > > > > *Jacob Jett*| Research Librarian | ASFPM > > 8301 Excelsior Dr. | Madison, WI 53717 > > tel: 608-828-3000 | desk: 608-828-6342 | floods.org > > <http://www.floods.org/> | _Email Jacob <mailto:ja...@floods.org>_ > > > > _______________________________________________ > > 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/20221017/f771ec19/attachment-0001.htm > > > > ------------------------------ > > 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 203, Issue 10 > ******************************************* >
_______________________________________________ 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/
