Extending the action_logs table
Hi everyone, I started to work on logging Holds actions (Bug 14642). One of the interesting things to log is the context in which those actions take place (OPAC, staff, CLI scripts). Do u have any opinion on the best way to do it besides just adding an 'interface' column or smth similar? Regards -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
I like that idea. On Tue, Jun 28, 2016 at 1:37 PM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
Hi everyone, I started to work on logging Holds actions (Bug 14642). One of the interesting things to log is the context in which those actions take place (OPAC, staff, CLI scripts).
Do u have any opinion on the best way to do it besides just adding an 'interface' column or smth similar?
Regards -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://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/
I don't have any suggestions. The new column sounds like a good and easy way to do that. 2016-06-28 18:37 GMT+01:00 Tomas Cohen Arazi <tomascohen@gmail.com>:
Hi everyone, I started to work on logging Holds actions (Bug 14642). One of the interesting things to log is the context in which those actions take place (OPAC, staff, CLI scripts).
Do u have any opinion on the best way to do it besides just adding an 'interface' column or smth similar?
Regards -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://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/
Thanks for your answers. El vie., 1 jul. 2016 a las 12:03, Jonathan Druart (< jonathan.druart@bugs.koha-community.org>) escribió:
I don't have any suggestions. The new column sounds like a good and easy way to do that.
2016-06-28 18:37 GMT+01:00 Tomas Cohen Arazi <tomascohen@gmail.com>:
Hi everyone, I started to work on logging Holds actions (Bug 14642). One of the interesting things to log is the context in which those actions take place (OPAC, staff, CLI scripts).
Do u have any opinion on the best way to do it besides just adding an 'interface' column or smth similar?
Regards -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://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/
Koha-devel mailing list Koha-devel@lists.koha-community.org http://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 (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
Le 01/07/2016 17:02, Jonathan Druart a écrit :
I don't have any suggestions. The new column sounds like a good and easy way to do that. +1 and it could be useful in other areas. For example, cataloguing = we've some bots that create/update records, for example for the SUDOC. With such a column available, we could differentiate "human" cataloguing and "bot" cataloguing. We could also use this in circulation (SIP2 checkout or self-checkout or staff-interface standard checkout)
2016-06-28 18:37 GMT+01:00 Tomas Cohen Arazi <tomascohen@gmail.com>:
Hi everyone, I started to work on logging Holds actions (Bug 14642). One of the interesting things to log is the context in which those actions take place (OPAC, staff, CLI scripts).
Do u have any opinion on the best way to do it besides just adding an 'interface' column or smth similar?
Regards -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://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/
Koha-devel mailing list Koha-devel@lists.koha-community.org http://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/
-- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries
El mié., 6 jul. 2016 a las 7:12, Paul Poulain (<paul.poulain@biblibre.com>) escribió:
Le 01/07/2016 17:02, Jonathan Druart a écrit :
I don't have any suggestions. The new column sounds like a good and easy way to do that. +1 and it could be useful in other areas. For example, cataloguing = we've some bots that create/update records, for example for the SUDOC. With such a column available, we could differentiate "human" cataloguing and "bot" cataloguing. We could also use this in circulation (SIP2 checkout or self-checkout or staff-interface standard checkout)
I did it relying on C4::Context->interface so it is just a matter of making it handle more 'interfaces' and the relevant scripts set it correctly for logactions to pick it. Or just pass it as a parameter to logactions :-D https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16829 Please test so we push it ASAP! Regards -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
My +1, especially for scripts. sb
On 06 lug 2016, at 12:12, Paul Poulain <paul.poulain@biblibre.com> wrote:
Le 01/07/2016 17:02, Jonathan Druart a écrit :
I don't have any suggestions. The new column sounds like a good and easy way to do that. +1 and it could be useful in other areas. For example, cataloguing = we've some bots that create/update records, for example for the SUDOC. With such a column available, we could differentiate "human" cataloguing and "bot" cataloguing. We could also use this in circulation (SIP2 checkout or self-checkout or staff-interface standard checkout)
2016-06-28 18:37 GMT+01:00 Tomas Cohen Arazi <tomascohen@gmail.com>:
Hi everyone, I started to work on logging Holds actions (Bug 14642). One of the interesting things to log is the context in which those actions take place (OPAC, staff, CLI scripts).
Do u have any opinion on the best way to do it besides just adding an 'interface' column or smth similar?
Regards -- Tomás Cohen Arazi Theke Solutions (https://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://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/
Koha-devel mailing list Koha-devel@lists.koha-community.org http://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/
-- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://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/
participants (5)
-
Barton Chittenden -
Jonathan Druart -
Paul Poulain -
Stefano Bargioni -
Tomas Cohen Arazi