[Koha-bugs] [Bug 22690] Merging records with many items too slow (Elasticsearch)

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

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22690

--- Comment #209 from Jonathan Druart <jonathan.druart+koha at gmail.com> ---
(In reply to Katrin Fischer from comment #208)
> (In reply to Nick Clemens from comment #207)
> > (In reply to Ere Maijala from comment #206)
> > > Jonathan,
> > > 
> > > I'm still not sure it makes sense to delete the tracking information when a
> > > biblio is deleted. That would break the first use case described here:
> > > 
> > > https://bywatersolutions.com/news/koha-tutorial-track-click-system-preference
> > > 
> > > The second example has a JOIN with the biblio table, but I'm not convinced
> > > it's intentionally ignoring the case of deleted biblios.
> > 
> > I think both cases there are tracking use of current resources.
> > 
> > My assumption would be that a deleted resource is no longer available and
> > the decisions has already been made (i.e. you ended the subscription) so
> > that tracking does not need to be retained
> 
> I think this is true if you want to report on a specific resource, but I
> think the information could still be useful if you want to purchase the
> records again in another license model or when doing annual reporting on
> e-resource use.

I am not sure it's relevant as you lost the link (on delete set null).

The question basically is: do we want to know how many times a user clicked on
records that have been deleted?

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