[Koha-bugs] [Bug 6557] biblioitems.totalissues unused

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6557

--- Comment #25 from Jared Camins-Esakov <jcamins at cpbibliography.com> ---
Paul,

(In reply to comment #24)
> I can't decide myself to push this patch. Let me share my comments:
>  * it add a syspref to decide wether we should update this field through a
> cron or in real time. The FAUSP (Fighters Against Useless SysPrefs) commitee
> has some concern: if it's long to do, who will set this syspref to 1 ? Small
> libraries have a low-grade hardware, large libraries circulate a lot. My
> conclusion is that noone will set the syspref to 1. So the syspref
> could/should be removed.

I think it is worth having the syspref and the option for realtime update for
two reasons:
1. in the future performance may improve, and this is definitely a feature that
people might want. By including the syspref now, we forestall the requests that
it be added.
2. For very small libraries, setting up a cron job can be a significant
hardship, and if you're circulating one item per minute on average, the
performance hit from realtime updating doesn't really matter.
3. (I'm like the Spanish inquisition, with fear, surprise, and ruthless
efficiency... can I start over?) Although I consider the performance hit to be
significant, the fact is we're not looking at an operation any more inefficient
than checking out any item was in 3.2.

>  * OTOH, the UpdateTotalIssues sub uses ModBiblio. It appears that it's
> because the popularity sorting is based on 942$0 field. that's why it's so
> long & I can't see another method to populate this field. 
>  * In UNIMARC default setup, the totalissue field is attached to 942$0 like
> in MARC21. Quite surprising according to me, but not wrong afaik

I noticed that. And was baffled by it. But I figure, if it ain't broke...

>  * The install documentation should be updated to reflect the
> misc/cronjobs/update_totalissues.pl (can be done later. Having
> crontab.example updated is a good 1st step)

-- 
You are receiving this mail because:
You are watching all bug changes.