Hi Jacob, Most servers should already be using TLS 1.2, and all modern browsers should support it, so it’s all good. As for the ISBD, in terms of display, you could use custom XSLTs to change the display, but a maintenance burden would come with that for you. I don’t think there’s a way to transform metadata at export time. 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: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Jacob Jett Sent: Tuesday, 23 May 2023 12:59 AM To: koha-devel@lists.koha-community.org Subject: [Koha-devel] TLS connections Hi gang, It looks like AWS is upgrading their TLS connections from 1.0/1.1 to 1.2. Does anyone know if this will impact Koha records that point at AWS objects? Unrelated ISBD punctuation question. I've had some complaints from my staff about displaying ISBD punctuation. We use it in MARC to make sure that the metadata records are portable across multiple languages. However, I can sympathize that it doesn't look very clean in the display. Is there a Koha widget that either, let's us suppress displaying the ISBD punctuation or implements it at metadata record export time? Regards, Jacob Jacob Jett | Research Librarian | ASFPM 8301 Excelsior Dr. | Madison, WI 53717 tel: 608-828-3000 | desk: 608-828-6342 | <http://www.floods.org/> floods.org | Email Jacob <mailto:jacob@floods.org>