Re: [Koha-devel] [Koha-patches] Pull request: Bug 5528 analytical records
[Moving to koha-devel for discussion] Good morning. Katrin Fischer and I spent the morning poking at the code for bug 5528, and we have a few comments. 1) The "Analyze" link is a bit confusing. I think we both expected that link to run a script that would find pre-existing links. Perhaps that could be changed to something like "Create analytic"? 2) We both had some trouble figuring out how to use the new features. Is there any documentation? 3) The DB update needs to add subfields '0' and '9' to the 773 field. Otherwise, nothing works, and there's no indication why. 4) Links to the host record should appear on the XSLT display, too, not just the Normal display. Analytic records created using the "Analyze" link also seem to break the existing 773 display when XSLT is enabled, and it's not clear why. 5) Using barcodes for linking is a little troubling, since some libraries with analytics may not have barcodes. It seems to me a good compromise would be to have the option to create links based on either the barcode or the 773$w. Regards, Jared On Wed, Jan 5, 2011 at 1:09 PM, savitra sirohi <savitra.sirohi@osslabs.biz>wrote:
Hi, analytical records patches are available at:
git://kohadev.osslabs.biz/bug_5528_analytical_records.git
The patches are rebased to master and include Unimarc support.
Thanks, Savitra Sirohi Nucsoft OSS labs http://www.osslabs.biz _______________________________________________ Koha-patches mailing list Koha-patches@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-patches website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Jared Camins-Esakov Freelance bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins@cpbibliography.com (web) http://www.cpbibliography.com/
Hi to all, I write a particial answer to those questions:
2) We both had some trouble figuring out how to use the new features. Is there any documentation?
I'm the volonteer to write documentation on the feature. In fact the answer is no. So a little documentation: The feature is visible only if the preference 'EasyAnalyticalRecords' is on yes. The feature is for linking analitycal to their fathers. So in fact it only insert a 773 (Marc21) / 461 (Unimarc) in the analytical record. The idea is that the anaytical record is not indipendent part of a host record. For example an illustration inside a book. So the analytical record not has items but you can use the item data of the host. This is why it used the barcode, it is the identifier of the item. The only others identifier of the item is the itemnumber but is not a clearly visible data for the librarian. So the workflow that I image: 1)Librarian catalogues the host record at bibliographic level and add 1 o more items to it 2)Librarian insert the analytical record at bibliographic level, he doesn't add an item 3)Librarian connects analytical with host reading the barcode with the barcode reader.
3) The DB update needs to add subfields '0' and '9' to the 773 field. Otherwise, nothing works, and there's no indication why. Right, those definitions are mandatory.
5) Using barcodes for linking is a little troubling, since some libraries with analytics may not have barcodes. It seems to me a good compromise would be to have the option to create links based on either the barcode or the 773$w.
In fact this feature si primary done to link a record with items (the host) to records without items. So if the library want to do link without barcodes, is better that setup the preference 'EasyAnalyticalRecords' on 'NO'. I think that links with bibliographic data are better done with Katrin Fischer patch. Bye Zeno Tajoli -- Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci qaunto tra AT con @)
Jared, Thanks for the feedback. Work on including '0' and '9' to the database scripts is already in progress. I will change the link to "Create analytic" and take a look at XSLT (completely missed this!) as well. Adding to Zeno's explanation: relationships can be created by: 1. From the analytical record, using the "Link to host item", under Edit menu. This creates a new 773/461 field in the analytical record. 2. From the host record, using the "Create analytic" link. This creates an empty MARC record, with just the 773 populated. 3. Running the CLI script, create_analytical_rel.pl, this looks at analytical records with 773 fields populated, finds the host items bibilionumber and itemnumber using the barcode stored in 773$o (Marc21) and populates subfields 0 and 9. The host's items are displayed under the analytical record as well as under the host record. Holds can be placed on the host items from the analytical records. Only specific holds are allowed for analytical records. Thanks, Savitra On Mon, Jan 10, 2011 at 8:10 PM, Zeno Tajoli <tajoli@cilea.it> wrote:
Hi to all,
I write a particial answer to those questions:
2) We both had some trouble figuring out how to use the new features. Is there any documentation?
I'm the volonteer to write documentation on the feature. In fact the answer is no. So a little documentation:
The feature is visible only if the preference 'EasyAnalyticalRecords' is on yes. The feature is for linking analitycal to their fathers. So in fact it only insert a 773 (Marc21) / 461 (Unimarc) in the analytical record. The idea is that the anaytical record is not indipendent part of a host record. For example an illustration inside a book. So the analytical record not has items but you can use the item data of the host.
This is why it used the barcode, it is the identifier of the item. The only others identifier of the item is the itemnumber but is not a clearly visible data for the librarian.
So the workflow that I image: 1)Librarian catalogues the host record at bibliographic level and add 1 o more items to it 2)Librarian insert the analytical record at bibliographic level, he doesn't add an item 3)Librarian connects analytical with host reading the barcode with the barcode reader.
3) The DB update needs to add subfields '0' and '9' to the 773 field. Otherwise, nothing works, and there's no indication why. Right, those definitions are mandatory.
5) Using barcodes for linking is a little troubling, since some libraries with analytics may not have barcodes. It seems to me a good compromise would be to have the option to create links based on either the barcode or the 773$w.
In fact this feature si primary done to link a record with items (the host) to records without items. So if the library want to do link without barcodes, is better that setup the preference 'EasyAnalyticalRecords' on 'NO'.
I think that links with bibliographic data are better done with Katrin Fischer patch.
Bye Zeno Tajoli -- Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci qaunto tra AT con @)
participants (3)
-
Jared Camins-Esakov -
savitra sirohi -
Zeno Tajoli