Authority controlled fields for publisher
Hi, The topic has been asked before, but not exactly in the specific circumstances that I'm facing. My company (essentially, yours truly) is installing Koha for a customer, and migrating data. They insist on having fields 260$a and 260$b to be authority controlled. I solved that by modifying the BKS framework, setting 260$a to be a GEOGR_NAME and 260$b a CORPO_NAME. So far, so good. The trouble starts when you try the little icon to look up an authority record. If I click on that icon for 260$b (name of the publisher) and choose an existing one, the value instead ends up in 260$a. Now I don't think that this is a bug in Koha, but I do think that I'm not understanding this facility entirely, and the documentation doesn't seem to address this issue either. I'm aware that field 260 is supposed to contain transcribed data, and we've pointed this out to the customer, but this is what they want. Could somebody please enlighten me, whether I've taken the correct approach? Thanks, - Peter
Hi, Peter! I think one reason that the documentation might be lacking for trying to authority control 260 subfields is that this isn't a very standard thing to do, since 260 (and 264) are supposed to be transcribed to aid in identification of the title. Would your client accept a more standard way for access to authority controlled fields for this aspect of the titles, which would be to add a 710 for the authorized form of the publisher's name, and a 751 for the authorized form of the geographic location of the publisher? This may be not possible at all for your setting, though, but that being the more standard approach might help explain why there might not be a lot of information out there to control subfields in 26X fields. Best, h2 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ms. Heather Hernandez (she, her, hers) Technical Services Librarian San Francisco Maritime National Historical Park Research Center 2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA 94123-1284 415-561-7032, heather_hernandez@nps.gov<https://webmail.lmi.net/src/compose.php?send_to=heather_hernandez%40nps.gov> Library catalog: http://keys.bywatersolutions.com/
Hi Peter, apart from Heather's excellent cataloguing advice - maybe this little plugin could be an option: *Bug 15933* <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15933> - Add cataloguing plugin to search for existing publishers in other records It's not using authorities, but it might help to get a bit more control of the input on this field. Hope this helps, Katrin On 10.12.20 00:16, Peter Korsten wrote:
Hi,
The topic has been asked before, but not exactly in the specific circumstances that I'm facing.
My company (essentially, yours truly) is installing Koha for a customer, and migrating data. They insist on having fields 260$a and 260$b to be authority controlled. I solved that by modifying the BKS framework, setting 260$a to be a GEOGR_NAME and 260$b a CORPO_NAME. So far, so good.
The trouble starts when you try the little icon to look up an authority record. If I click on that icon for 260$b (name of the publisher) and choose an existing one, the value instead ends up in 260$a.
Now I don't think that this is a bug in Koha, but I do think that I'm not understanding this facility entirely, and the documentation doesn't seem to address this issue either. I'm aware that field 260 is supposed to contain transcribed data, and we've pointed this out to the customer, but this is what they want.
Could somebody please enlighten me, whether I've taken the correct approach?
Thanks,
- Peter _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
participants (3)
-
Hernandez, Heather H -
Katrin Fischer -
Peter Korsten