Summary: | Marc21: Show i for 776 | ||
---|---|---|---|
Product: | Koha | Reporter: | Kelly McElligott <kelly> |
Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED FIXED | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | flyingendpaper, lauren_denny, m.de.rooy |
Version: | 17.11 | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
Kelly McElligott
2018-05-10 15:04:10 UTC
The 76X-78X Linking Entry Fields in MARC21 (including the 776 field) require that $i contain "Relationship Information," i.e., "Online version," or "Large print version," or "Print version." Explanation with usage examples here: https://www.loc.gov/marc/bibliographic/bd76x78x.html There are more examples and explanations of usage in OCLC's Bibliographic Formats & Standards: https://www.oclc.org/bibformats/en/7xx/76x-78x.html So libraries that catalog according to these standards have records that conform to them--my library has LOTS of records that conform to these standards. So if the $i is not displaying, there is no indication of the relationship between the record displayed and what it's linking to. ByWater Solutions in its training videos suggests changing/using the $t to indicate relationship, but this isn't practical for us (too many records involved) and we can't catalog this way since it doesn't conform to the MARC21 standards that we follow & that we must use in OCLC. In addition, many older records (including Library of Congress records) only have a $i with relationship information and the $w with record numbers--the $t for title information is not required and wasn't always included until OCLC created a macro for pulling the information from the linked record. So it would be wonderful if Koha could also conform to these standards to display the relationship information using the subfield, $i, that the standards use to display/store the relationship information. Koha even calls the $i "Display text" in the Bibliographic Frameworks, so if I have it checked to display in the staff client & opac, I would love it to display. This already exists in koha. I don't remember which version it started to appear though. :) We use the 776$i on a regular basis. It would be nice if it could be displayed in the other linking fields that Heather mentions in her comment. Should that be a new bug? (In reply to Lauren Denny from comment #2) > This already exists in koha. I don't remember which version it started to > appear though. :) We use the 776$i on a regular basis. > > It would be nice if it could be displayed in the other linking fields that > Heather mentions in her comment. Should that be a new bug? Yes, please :) But I believe we already do show in several, not sure which ones might be missing still if at all. |