UseControlNumber preference is set to "Don't use" and the EasyAnalyticalRecords preference is set to 'Display.' I created a record, and then selected New child record and created an analytic. Then, following the instructions in the manual Chapter 5 http://es.koha-community.org/manual/3.10/en/cataloging.html#cataloganalytics I linked the analytic to the host item. This resulted in two 773 fields. The first (created when adding a new child record contains: w Host Record control number 005037189 d Place, publisher, and date of publication Milwaukee : Hal Leonard, [2002?] z International Standard Book Number 0634038788 t Title Selections from O brother, where art thou? : The second 773, created when I linked the child to the parent contains the above, plus 0 Host Biblionumber 19017 9 Host Itemnumber 20551 The search for analytics is driven by the host item number, which is not included in the 773 that is created with a new child record. So you must link the child to the parent. But why create an additional 773? It looks messy. Second part possibly not related at all to the above: When I go to the host item in the staff interface and click on Analytics it says Used in 4 analytics ('4 analytics' is a link: http://kohaadmin-test.efdss.org/cgi-bin/koha/catalogue/search.pl?idx=hi&q=20551 If I click on the link: No results found. No results match your search for 'hi,wrdl: 20551' in VWML Test Catalog. But if I put the host item number 20551 into the search field, it returns the children and the parent record. Something about the search from analytics is not functioning correctly.
I've just been going through the options and if my understanding is correct it would appear there's been a regression somewhere. I'm sure it used to be that when you enabled EasyAnalytics, then the 'Analyze items' menu option replaced 'New child record' as an option under the 'New' menu in a record display. With both options present it's very easy to get confused between the two different mutually exclusive procedures for creating analytics. However.. I do think we should be able to enhance the functionality such that the options are no longer mutually exclusive. I'll open another bug for this as an enhancement.
This is from the template for the links: 152 [% IF ( EasyAnalyticalRecords && CAN_user_editcatalogue_edit_catalogue ) %] 153 <li><a href="/cgi-bin/koha/catalogue/detail.pl?biblionumber=[% biblionumber %]&analyze=1">Analyze items</a></li> 154 [% END %] 155 [% IF CAN_user_editcatalogue_edit_catalogue %] 156 <li><a href="/cgi-bin/koha/cataloguing/addbiblio.pl?parentbiblionumber=[% biblionumber %]">New child record</a></li> 157 [% END %] We could easily hide the 'new child record' if EasyAnalytics is turned on - althought it would be nicer to find a way to have both coexist (item level linking and record level linking).
Hmm, I'de totlay forgotten about this bug and analytics is now out of my mindspace :( I'de love to see a more thorough treatment of this allowing for the preferences to be used collaboratively.
I did start work on this.. though only to the level of documenting what the expected behaviour for analytics at the marc level should be.. http://wiki.koha-community.org/wiki/Analytics
Looks like that page is somewhat out of date compared to our internal one.. I'm just sanitzng and transfering my findings from 2013 onto the community wiki.. alsmost as a sort of RFC for this work
I've updated my ramblings and documentatino now: http://wiki.koha-community.org/wiki/Multipart_Bibliographics That page links out to three separate pages for each of the possible UseControlNumber combinations.. I need to add in the EasyAnalytics thoughts for each of those specific use cases.
For a quick fix however to this particular bug.. Katrins identified the right place in the templates that needs amending.. perhaps one for an Academy student?
Created attachment 35270 [details] [review] Bug 10241 - Easy analyticals creates two 773 fields. Search/link from host to children is broken Hidden 'New child record' if 'EasyAnalytics' is set to display. Testing plan: -Turn on 'EasyAnalytics'. Check the drop down menu from the records page *The drop down menu should include 'Analyze items' and not include 'New child record' -Turn off 'EasyAnalytics'. Again check the drop down menu from the records page *The drop down menu should include 'New child record' and not inlucde 'Analyze items'
Created attachment 35284 [details] [review] [SIGNED OFF] Bug 10241 - Easy analyticals creates two 773 fields. Search/link from host to children is broken Hidden 'New child record' if 'EasyAnalytics' is set to display. Testing plan: -Turn on 'EasyAnalytics'. Check the drop down menu from the records page *The drop down menu should include 'Analyze items' and not include 'New child record' -Turn off 'EasyAnalytics'. Again check the drop down menu from the records page *The drop down menu should include 'New child record' and not inlucde 'Analyze items' Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Created attachment 35294 [details] [review] [PASSED QA] Bug 10241 - Easy analyticals creates two 773 fields. Search/link from host to children is broken Hidden 'New child record' if 'EasyAnalytics' is set to display. Testing plan: -Turn on 'EasyAnalytics'. Check the drop down menu from the records page *The drop down menu should include 'Analyze items' and not include 'New child record' -Turn off 'EasyAnalytics'. Again check the drop down menu from the records page *The drop down menu should include 'New child record' and not inlucde 'Analyze items' Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de> Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Cheers Thomas, another bug bites the dust :)
Patch pushed to master. Thanks Thomas!
Pushed to 3.18.x will be in 3.18.4 release
(In reply to Chris Cormack from comment #13) > Pushed to 3.18.x will be in 3.18.4 release Pushed to 3.16.x, will be in 3.16.8