[Koha-devel] Alerting users to breaking changes / backwards incompatibility

[dcook at prosentient.com.au]

Wonderful! Y’all are way ahead of me. Glad it’s already been done.

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Online: 02 8005 0595

 

From: Tomas Cohen Arazi <tomascohen at gmail.com> 
Sent: Friday, 29 May 2020 6:39 AM
To: David Cook <dcook at prosentient.com.au>
Cc: koha-devel <koha-devel at lists.koha-community.org>
Subject: Re: [Koha-devel] Alerting users to breaking changes / backwards incompatibility

 

Create an SQL report with the following query:

 

SELECT COUNT(marcxml) FROM biblioitems;

 

And then go to the reports list. You will notice it tells you this: https://snipboard.io/5wjCUc.jpg

 

El mié., 27 may. 2020 a las 21:23, <dcook at prosentient.com.au <mailto:dcook at prosentient.com.au> > escribió:

Oh great. I don’t think I’ve seen that?

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Online: 02 8005 0595

 

From: Tomas Cohen Arazi <tomascohen at gmail.com <mailto:tomascohen at gmail.com> > 
Sent: Thursday, 28 May 2020 9:53 AM
To: David Cook <dcook at prosentient.com.au <mailto:dcook at prosentient.com.au> >
Cc: koha-devel <koha-devel at lists.koha-community.org <mailto:koha-devel at lists.koha-community.org> >
Subject: Re: [Koha-devel] Alerting users to breaking changes / backwards incompatibility

 

We already do something similar with the biblio_metadata table.

 

El mié., 27 de mayo de 2020 20:35, <dcook at prosentient.com.au <mailto:dcook at prosentient.com.au> > escribió:

Hi all,

 

I was just thinking how a lot of SQL reports will return unexpected results when we merge the deleted* tables with their live/active counterparts. 

 

What do people think about a modal popup in the reports (on a per user basis) alerting them to how they may need to update their reports following an upgrade which changes reporting behaviour?

I’m not 100% sure how we’d do it, but it’s something we could re-use through much of the Koha staff client. 

 

Or maybe we could raise a flag in the borrower row during an upgrade, and when they log into the staff client, they’re presented with a “You need to know…” kind of page. After all, users aren’t going to be reading release notes, and sysadmins doing upgrades aren’t necessarily going to do the best job communicating to every single staff user about what they need to know in an upgrade.

 

But that’s easier said than done too, especially when you’re upgrading past multiple versions. 

 

Anyway, just putting it out there. As you can see, I haven’t thought about it too deeply yet. 

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Online: 02 8005 0595

 

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




 

-- 

Tomás Cohen Arazi

Theke Solutions (http://theke.io <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/20200529/87d20e1a/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 484 bytes
Desc: not available
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20200529/87d20e1a/attachment-0001.sig>