[Koha-bugs] [Bug 15851] "Analytics: Show analytics" showing regardless of whether they have analytics.

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Wed Aug 30 11:34:08 CEST 2017


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

--- Comment #14 from Katrin Fischer <katrin.fischer at bsz-bw.de> ---
(In reply to Hugo Agud from comment #13)
> At the what we need is to know if a bib record has analytics, we do not need
> silly xslt links based on bib-leve:s (journals) and on the other hand we
> have forgotten about chapters not only serial (bib-level:b)

The links have been created so you can hide them very easily with CSS if you
don't want or need them.

> The link between bib and analytics is 773 field... here the big issue is
> most of fields are text 773$t and the one to one link are 773$0 773$9 or
> even 773$x(issn (journals) or 773$w(controlnumber) depends on every library,
> how they have created the analytics...they will have more or less filled tags
> 
> If you're using koha and have created the analytics with koha you will have
> a nice 773 to work create links ;)

Not all libraries catalog solely in Koha. But: you can create analytics within
Koha in 2 different ways already. One is EasyAnalytics which is tied to the
items, the other is from the detail view available as well and supports
Controlnumber linking: New > New child record. If a 001 exists, it will be
used.

The different linking methods/options are the reson that there is a fallback
from $w to a Title search. More logic could be added there to include other
possible good search parameters like ISBN/ISSN.

> Now in the staff cients, in the analytics tab you have info about if that
> item has anaytics attached and how many... because the 773$9 (one to one
> link and it works fine)

Please keep in mind that this is only available for libraries using
EasyAnalytics.

> I think there is not a 100% solution, because there will be plenty of
> different situations and one solution won't match all possible situations
> 
> I like the idea of the syspref 'GetAnalyticsCount' but we must be clear
> enought with the customers explaining how the links works
> 
> The idea it should be, that the library must  check their current 773 tags
> and fix it. (they have a nice batch record modification tool)

> 
> There is 3 potential ways:
> for current biblionumber --> appear the link if there is any 773$0 that
> matchs the biblio
> or

There is no $0 defined for 773 in MARC standard?

> 
> for current itemnumbers --> appear a link if there is any 773$9 that matchs
> the itemnumber
> 
> or
> for current issn --> apprear a link if there is any 773$x that matches 022$a

Please don't forget $w here - it's actually one of the best possible links, as
the matching should be exact based on ID.


> I don not like the control-number:
> the use of control number I dislike because koha is not using 001
> control-number

Please keep other workflows in mind. Our records are linked outside of Koha by
ID in an external cataloguing environment, everything is held together by 001.
One central cataloguing environment, data delivered to lots of different ILS.
Also: 001/$w IS MARC standard.

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


More information about the Koha-bugs mailing list