Bug 7414 - Analytics records need to use indicators to determine display
Summary: Analytics records need to use indicators to determine display
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: MARC Bibliographic data support (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Galen Charlton
QA Contact:
URL:
Keywords:
Depends on:
Blocks: 34482
  Show dependency treegraph
 
Reported: 2012-01-06 16:51 UTC by lculber
Modified: 2023-08-04 20:12 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lculber 2012-01-06 16:51:58 UTC
In the 78X fields used in MARC21 for linking related records (such as serials), the indicators control the display. The first indicator set to 0 the note does not display, set to 1 the note does display. What the second indicator means varies according to field. Now that Koha has the functionality to handle analytics, I think adding the ability to use the indicator is a logical next step.
Comment 1 Katrin Fischer 2019-04-28 22:03:30 UTC
Is the note field $i in this case?
Comment 2 Katrin Fischer 2023-08-04 18:10:42 UTC
(In reply to Katrin Fischer from comment #1)
> Is the note field $i in this case?

Hi Heather, can you maybe help me out understanding the documentation here?
Comment 3 Heather 2023-08-04 18:35:54 UTC
Hi, Katrin!

Of course!

This is the relevant documentation:
https://www.loc.gov/marc/bibliographic/bd760787.html

And I think Koha already does this correctly, but I haven't tested *all* the fields.  This is the way the indicators work:

First indicator: 0 = do not display a note
  1 = display a note
(This usually means to a system, "display a 500 note in addition to displaying the 7XX linking entry field," so most often it's set to zero, because the 7XX linking entry field has all the relevant information in it--and the link!)

Second indicator controls the display of default words or phrases about the relationship between the bibs being linked, and you will see in the MARC documentation above a list of "display constants" (i.e., default display words and phrases) that can be chosen.

For all fields except 780 and 785, the second indicator can also be set to 8 which will allow the display of a note from the free text entered into $i.  (This is how $i is used.)  A very common implementation of this are the 776 fields on related print and online versions of books; it wouldn't be helpful to use the display constant "Available in another form" because that doesn't tell you *what* the other form is, so the 776s usually look something like this:

On the printed book record:
776 08 $i Online version $a Hobb, Robin. $t Mad ship $w (OCoLC)1234567
On the ebook version:
776 08 $i Print version $a Hobb, Robin. $t Mad ship $w (OCoLC)7654321

This is a bib in our catalog using the very common 780 & 785, showing Koha correctly using the second indicator display constants:
https://keys.bywatersolutions.com/cgi-bin/koha/opac-detail.pl?biblionumber=16159

Hope this helps--let me know if this was anywhere near what you wanted!!
--h2
Comment 4 Heather 2023-08-04 19:06:39 UTC
Hi, again!

Looking this over again, if the bug is only about the 773 field (which is in an analytic record), then Koha is already doing it correctly, I think.  We are on 22.11.07, and this analytic record in our catalog has:
773 0_ $t Sea story annual $g 1943, cover $w (OCoLC)38923654
And Koha correctly displays the display constant:  In:
https://keys.bywatersolutions.com/cgi-bin/koha/opac-detail.pl?biblionumber=37701
(As do the other analytics I've looked at in our catalog.)
I haven't tested this on sandboxes, though!

The initial description of this bug is a little confusing, though, because the bug is titled, "Analytics records need to use indicators to determine display," and then the description talks about 78X fields--but analytic records use 773 fields to link to their "Host" (or sometimes called "Parent").

Hope this helps!
--h2