Bug 13529 - Easy analyticals and UseControl number should be able to coexist
Summary: Easy analyticals and UseControl number should be able to coexist
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: MARC Bibliographic data support (show other bugs)
Version: master
Hardware: All All
: P4 normal (vote)
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-07 12:04 UTC by Martin Renvoize
Modified: 2023-05-10 19:28 UTC (History)
6 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Renvoize 2015-01-07 12:04:11 UTC
+++ This bug was initially created as a clone of Bug #10241 +++

At current, EasyAnalytics and UseControlNumber are mutually exclusive and lead to all sorts of strange issues if both are enabled at the same time.

I believe this should not be the case and that with some re-factoring the two features could be made to compliment each other.

I've started putting together some documents to outline my understanding of how the MARC21 rules should fit together with the UseControlNumber piece as a whole, I suggest we enhance this and then look at adding in the EasyAnalytics functionality to that area rather than the other way around.

http://wiki.koha-community.org/wiki/Multipart_Bibliographics
Comment 1 Lauren Denny 2023-05-10 19:28:26 UTC
Could someone explain why the two system preferences 'UseControlNumber' & 'EasyAnalytics' cannot co-exist?  We used to have both turned on until a recent upgrade and now only use 'UseControlNumber' so that we can seperate our links to the corresponding relationship instead of combining all the options into the 773 field.

We are needing features from both system preferences.
The flexibility of the 'UseControlNumber' allows koha to use seperate linking fields based on the relationship between records/items instead of putting all the links in the 773 which is only for the parent/child relationship.
And how EasyAnalytics allows koha display the item record on both records for those linked together.

Here are functions that are utilized by the EasyAnalytics that I would find helpful with some ideas on how to make it work. (I am not a programer so I don't totally know if they would work but are ideas from a librarian's point of view.)

1 - Have a drop-down menu that allows you to choose the linking field you want the information to koha auto-populate subfields from based on the bibilonumber instead of the barcode.  The field selected where to put the inforamtion to pulled based on system preference or framework selection.

2- System preference that allows you to control which fields auto-populate with the selected field.  
245$ab title to $t, 1xx$a author to $a, 250$a edition to $b, 001 control number (biblionumber) to $w , 260/264 publishing details to $d, 020 ISBN to $x, 022 ISSN to $z

Another idea would be to have a checkbox in the framework that people select that tells koha what information to pull into the field.

3- Have the item record appear on both the parent & child records
This would be helpful for records using the 773 (parent & child relationship) where one item record is 'shared' with both record.  It is physcially on the child record but would be helpful to patrons to have a list of all the items associated with the parent record.  

An idea would be, if the item number or barcode is found in the 773 field, the item appears on record with the link.  If these subfields are empty the item will not display on the linked record.