Hi, dear Koha Community! At the last Koha-US Cataloging SIG meeting (recording here: https://youtu.be/dzSaJYkayVA ), we had the pleasure of actual Koha developer Tomas attending and we talked about how nice it would be if Koha had a function where we could generate related records that had some fields automatically generated from data in the source record, starting with a very common related record, an online version of a hardcopy book. I've started making a list of the minimum fields that would be helpful to have generated either from the source record or commonly needed in an online version record, and am sharing it here so that others could take a look and chime in, since my cataloging experience is in academic & specialized library collections, and I'm sure that I'm missing what would be useful in other settings. Generate: 008/23 o (i.e., letter o), OCLC fixed field FORM If present in source record, duplicate for editing in generated record: 050 082 090 1XX 24X All subfields except $h (if $h is present in source record, do not duplicate in source record) 264 336 4XX 5XX notes in the original order of the source record (according to RDA rules, following the order of importance, then the order of the description, not numeric MARC field order) 6XX 7XX 8XX If 260 is present in source record, transcribe into generated record as follows: 260 $a should be 264 _ 1 $a 260 $b should be 264 _1 $b 260 $c should be 264 _1 $c enclosed in brackets (this is the simplest way to cope with what may or may not be a copyright date, publication date, etc., which is done differently in RDA than in AACRX, etc.) 300 $a data should be duplicated in generated record after the text: 1 online resource ( 300 $b data should be duplicated and followed by a closed parentheses, i.e.: ) 300 $c from source record should not be duplicated Generate: 337 _ _ computer ǂb c ǂ2 rdamedia 338 _ _ online resource ǂb cr ǂ2 rdacarrier Generate the following 588 field, preceding all other 5XX notes: 588 _ _ Description based on print version record. Generate the following 776 0 8 field, placed in numeric order among the duplicated 7XX fields, with the first generated subfield being: $i Online version And with the following subfields duplicated from the source record's...: $a from 100 or 110 or 111's all subfields (i.e., whatever is in an entire 100, 110, or 111 will be put into one $a in the 776) $t from the 130 (if present) $a, $f, $g, $k, $n, and $p in the source record (like the 776 0 8 $a, the contents of the source record's subfields are not separate subfields in the generated record); if no 130 is present in the source record, duplicate the data from the source record's 245 $a, $f, $g, $k, $n, and $p If a 240 field is present in the source record, duplicate the data from all the source subfields into one $s field $b from all subfields in the source record's 250 fields $d from all the subfields in the 260 or 264 _ 1 and/or 264 _2 and/or 264 _3 $w record control number generation is complicated for those libraries using Library of Congress Control Numbers ("DLC") and/or OCLC numbers ("OCoLC")-- certain of these numbers must have padding zeroes inserted, etc. Within OCLC's Connexion Client software, there is a macro that automatically generates them from the source record's control number, correctly formatted in a 7XX Linking Entry Field, so it's possible! This OCLC Technical Bulletin describes the different formats that the OCLC Control Number may have: https://files.mtstatic.com/site_10606/4194/0?Expires=1599242062&Signature=ffOHdji3YNQ5bfe4rMDA5CpsLjM1PWYuPEDFpqM8EJRpSIPM05C8jN~AcgTzzWXp0rmIGtxlQc2bVbnPJqn8xxMNebpvyT2cUyeUT22kFcI0YjEh-cZSfrt-A~4Phl5cNzpTKK-dixZaiLUd6QPr~a3R-oary6XUjzaF9WcB5-g_&Key-Pair-Id=APKAJ5Y6AV4GI7A555NA And this describes the formats of OCLC numbers stored in the 001 field (for libraries that use that & store the number there): https://help.oclc.org/Metadata_Services/OCLC_MARC_records/Content_designator... Of course, this assumes that a Koha library would like to display & use the record number in the 776 as the hyperlink--we do, and ByWater has it working for us (with the exception of the 787s displaying a bit wonky in the wrong place)--this functionality can be seen in our catalog with these records: https://keys.bywatersolutions.com/cgi-bin/koha/opac-detail.pl?biblionumber=4... https://keys.bywatersolutions.com/cgi-bin/koha/opac-detail.pl?biblionumber=2... Then, not to be forgotten, would be a macro in the Advanced Bibliographic Editor that would then generate a new 776 in the print version record (similarly generated as above), with data drawn from the new online version record, with the $i for the print version record being: $i Online version Some additional resources: MARC Bibliographic 76X-78X Linking Entry Fields: https://www.loc.gov/marc/bibliographic/bd76x78x.html OCLC's Bibliographic Formats and Standards, 3 Special Cataloging Guidelines, 3.3.1 Electronic Resources: https://www.oclc.org/bibformats/en/specialcataloging.html#electronicresource... Dreaming big!! --h2 P.S. I realize I may have the start of a development bug here, and could take a stab at entering into Bugzilla, but I wanted to get some input on the above first, so that if it does go into Bugzilla, it's good for more types of libraries--the 776 $w is very US/Library of Congress/OCLC centric because of my very limited perspective on it, and I frankly am ignorant of better options & would love to hear from others what those would be. Thank you! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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/