https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 --- Comment #478 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- (In reply to Marcel de Rooy from comment #473)

I wrote two follow-ups now. WIll attach them tomorrow.

But did look a bit closer to analytical records in Koha and they are quite different from what is done here. They use 773 but thats about it. So there seems to be no reason to braid(?) them together here. Making the analytics disappear when there are components.

Note: the components here work with 773 and record control numbers looked up in biblio records. Analytics works different, storing item numbers(!) in 773$9. This seems to be something that we add on top of MARC21, if I understand correctly (so no default MARC21).

Conclusion: We should keep them really separate from each other. Will have to add that to my follow-up still. Which should be very trivial.

Katrin: Could you confirm?

I believe there are some major differences between the features - so fully agree. What we are looking for here is linking between bibliographic records. We link a record to another record, using either $w or a combination of title and author from 773 for search. So this is about hierarchies on the bibliographic record level. EasyAnalytics as I understand it, is linking an item to multiple records using non-standard MARC subfields of 773. It's a useful feature, but a different use case. For example it could probably be used very well for "bound-togethers", where different works where combined into one bound unit (often found in historical holdings). We could probably make both work together by checking for the prefs and maybe existence of certain subfields in 773, but as UseControlnumber and Easyanalytics are already mutually exclusive right now, I think it's outside of scope here. -- You are receiving this mail because: You are watching all bug changes.