[Koha] Koha pluging for linking fields and RDA -76X-78X fields

[Hernandez, Heather H]

Hello!

Apologies for my late reply--we had a family emergency, but all is now well!

IMO, the relator codes in $4 are efficient but not as human-friendly as the terms in $e--some libraries use both.  (We use only $e terms in new cataloging.)  I like the relator terms--Koha displays them well.

And Koha links well to whatever number you use in the 001.

You're right--we're not using the work-relationship-designators (in RDA Appendix J) because we find the relationships supplied by the indicators in the 78X linking entry fields sufficient--typing in the relationship designators is, well, extra typing. ::grin::

There are relator codes listed on the MARC21 page under "Relators" at MARC Code List for Relators (Network Development and MARC Standards Office, Library of Congress) (loc.gov)<https://www.loc.gov/marc/relators/>  (I'm sorry, but I don't know where non-English ones may be.)  Since they're MARC21 codes, they're not listed in the RDA Toolkit.  And, yes--it can get confusing about what's where!

And, Katrin, about Bug 29733, using a linker in Koha similar to the authority linker is an intriguing idea, but it is not what other ILS's and bibliographic utilities do as far as I know (which is limited!)--at the moment, we are able to import our records into Koha from OCLC without change, and the 78X linking works immediately, because Koha linking uses the exact same data in 78X linking entry fields as OCLC.  Having to wait, e.g., for a script to one to add something like a $9 field to achieve the linking would not be ideal for us.

Also, authority records change constantly--references are added and/or deleted, language and terminology changes, people die and death date is added, etc., etc., etc., so the headings used in the bibliographic records need to change as well, and there are many headings in each bibliographic record, so having Koha create the linkage via a script is worth waiting for the script to run.  The linking in 78X linking entry fields must necessarily be thought about by the cataloger(s), and systems with advanced functionality create it automatically (e.g., in OCLC one simply puts the record number into the appropriate MARC field and runs a macro and the rest of the field is populated from the source bib record--I have yet to see if such a macro can work in Koha, but want to!).  The relationships have to be thought about by the cataloger, and aren't usually that many, so are easily put in by the cataloger, so at least in my opinion, having Koha create yet another linkage via script is added & not really necessary.  But this is only my opinion, based on a very particular workflow--it may serve the vast majority of the Koha community!  And a syspref to turn it on or off is always possible.

Cheerio!
--h2

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Ms. Heather Hernandez (she, her, hers)
Technical Services Librarian
Library catalog:  https://keys.bywatersolutions.com/<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkeys.bywatersolutions.com%2F&data=05%7C01%7CHeather_Hernandez%40nps.gov%7C950a4b896c6840abbf2708da5a0692c2%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637921281518907037%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KDx6voZToIrZN2QYqe18e9S16%2B44bJ99OzKqi608gvQ%3D&reserved=0>
San Francisco Maritime National Historical Park Research Center
2 Marina Blvd., Bldg. E, 3rd floor, San Francisco, CA  94123-1284
415-561-7032 (office generally Tu-W & F, telecommuting M&Th)
heather_hernandez at nps.gov<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwebmail.lmi.net%2Fsrc%2Fcompose.php%3Fsend_to%3Dheather_hernandez%2540nps.gov&data=05%7C01%7CHeather_Hernandez%40nps.gov%7C950a4b896c6840abbf2708da5a0692c2%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637921281518907037%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xRq2sXM4t7jF7lA1WvRZ7q0ff4hgben1igzi2FlLBu4%3D&reserved=0>