776 - Additional Physical Form Entry http://www.loc.gov/marc/bibliographic/bd776.html is currently not displayed in OPAC or staff and should be added.
Just adding a +1 this is an important field for sound recording libraries.
Created attachment 61161 [details] [review] Bug 15140: [3.22] Add MARC21 776 to OPAC and staff display Adds code to opac and staff detail XSLT in order to show 776$t and a link based on 776$w (record control number). $w should be in the form: (MARCOrgCode)Record-number For instance: (NL-AmRIJ)12345 Note: You should have enabled default opac/intranet XSLT view. Test plan: [1] Add two 776s (one with $t and $w and one with $t only) [2] Verify that you see "Additional physical formats" on opac-detail. Does the link for $w work? [3] Check intranet detail too.
Created attachment 61162 [details] [review] Bug 15140: Add MARC21 776 to OPAC and staff display Adds code to opac and staff detail XSLT in order to show 776$t and a link based on 776$w (record control number). $w should be in the form: (MARCOrgCode)Record-number For instance: (NL-AmRIJ)12345 Note: You should have enabled default opac/intranet XSLT view. Test plan: [1] Add two 776s (one with $t and $w and one with $t only) [2] Verify that you see "Additional physical formats" on opac-detail. Does the link for $w work? [3] Check intranet detail too. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
I think the link should use Record-controlnumber, not the biblionumber for linking, like 773.
I have another thing: $t can be empty if your linked record has no author/main heading is the title (not sure how to say this right in English). In this case the title will be in $a and $t is empty. Best to display both. Also: Because we only check for existence of 776 the display will look broken when there is only $a.
Created attachment 61351 [details] [review] Bug 15140: Add MARC21 776 to OPAC and staff display Adds code to opac and staff detail XSLT in order to show 776$t (or $a) and a link based on 776$w (record control number). $w should be in the form: (MARCOrgCode)Record-number For instance: (NL-AmRIJ)12345 Note: You should have enabled default opac/intranet XSLT view. Test plan: [1] Add two 776s (one with $t and $w and one with $t only) [2] Verify that you see "Additional physical formats" on opac-detail. Does the link for $w work? [3] Check intranet detail too. [4] Empty 776$t and put text in $a. Check detail page again. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
(In reply to Mirko Tietgen from comment #4) > I think the link should use Record-controlnumber, not the biblionumber for > linking, like 773. Thanks. Adjusted.
(In reply to Katrin Fischer from comment #5) > I have another thing: $t can be empty if your linked record has no > author/main heading is the title (not sure how to say this right in > English). In this case the title will be in $a and $t is empty. Best to > display both. Also: Because we only check for existence of 776 the display > will look broken when there is only $a. Adjusted too. Thanks
Instead of "/cgi-bin/koha/catalogue/search.pl?q=Control-number:" it has to be "/cgi-bin/koha/opac-search.pl?q=Control-number:"
(In reply to Felix Hemme from comment #9) > Instead of "/cgi-bin/koha/catalogue/search.pl?q=Control-number:" it has to > be "/cgi-bin/koha/opac-search.pl?q=Control-number:" Good catch. Copy/paste.. Thanks.
Created attachment 62531 [details] [review] Bug 15140: Add MARC21 776 to OPAC and staff display Adds code to opac and staff detail XSLT in order to show 776$t (or $a) and a link based on 776$w (record control number). $w should be in the form: (MARCOrgCode)Record-number For instance: (NL-AmRIJ)12345 Note: You should have enabled default opac/intranet XSLT view. Test plan: [1] Add two 776s (one with $t and $w and one with $t only) [2] Verify that you see "Additional physical formats" on opac-detail. Does the link for $w work? [3] Check intranet detail too. [4] Empty 776$t and put text in $a. Check detail page again. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Hi Marcel, linking works fine now. But I think the value from subfield $i (relationship information) should be displayed if second indicator = 8. Like in field 775 (other edition entry). I changed the status to "Failed QA". Please change it again if that was not correct.
Created attachment 62908 [details] [review] Bug 15140: Display $i when ind2==8 See MARC specification. Note that we have a preceding text before all 776s too. Test plan: [1] Set field 776 ind2 to 8. And add text in $i. [2] Look for this text on OPAC detail and staff detail. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
(In reply to Felix Hemme from comment #12) > Hi Marcel, > linking works fine now. But I think the value from subfield $i (relationship > information) should be displayed if second indicator = 8. Like in field 775 > (other edition entry). I changed the status to "Failed QA". Please change it > again if that was not correct. Thanks for testing, Felix. I have tried to implement your suggestion in the second patch.
Patch tested with a sandbox, by Felix Hemme <felix.hemme@thulb.uni-jena.de>
Created attachment 63232 [details] [review] Bug 15140: Add MARC21 776 to OPAC and staff display Adds code to opac and staff detail XSLT in order to show 776$t (or $a) and a link based on 776$w (record control number). $w should be in the form: (MARCOrgCode)Record-number For instance: (NL-AmRIJ)12345 Note: You should have enabled default opac/intranet XSLT view. Test plan: [1] Add two 776s (one with $t and $w and one with $t only) [2] Verify that you see "Additional physical formats" on opac-detail. Does the link for $w work? [3] Check intranet detail too. [4] Empty 776$t and put text in $a. Check detail page again. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl> Signed-off-by: Felix Hemme <felix.hemme@thulb.uni-jena.de>
Created attachment 63233 [details] [review] Bug 15140: Display $i when ind2==8 See MARC specification. Note that we have a preceding text before all 776s too. Test plan: [1] Set field 776 ind2 to 8. And add text in $i. [2] Look for this text on OPAC detail and staff detail. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl> Signed-off-by: Felix Hemme <felix.hemme@thulb.uni-jena.de>
(In reply to sandboxes@biblibre.com from comment #17) > Signed-off-by: Felix Hemme <felix.hemme@thulb.uni-jena.de> Thx
Created attachment 65185 [details] [review] Bug 15140: Add MARC21 776 to OPAC and staff display Adds code to opac and staff detail XSLT in order to show 776$t (or $a) and a link based on 776$w (record control number). $w should be in the form: (MARCOrgCode)Record-number For instance: (NL-AmRIJ)12345 Note: You should have enabled default opac/intranet XSLT view. Test plan: [1] Add two 776s (one with $t and $w and one with $t only) [2] Verify that you see "Additional physical formats" on opac-detail. Does the link for $w work? [3] Check intranet detail too. [4] Empty 776$t and put text in $a. Check detail page again. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl> Signed-off-by: Felix Hemme <felix.hemme@thulb.uni-jena.de> Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
Created attachment 65186 [details] [review] Bug 15140: Display $i when ind2==8 See MARC specification. Note that we have a preceding text before all 776s too. Test plan: [1] Set field 776 ind2 to 8. And add text in $i. [2] Look for this text on OPAC detail and staff detail. Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl> Signed-off-by: Felix Hemme <felix.hemme@thulb.uni-jena.de> Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
Created attachment 65187 [details] [review] Bug 15140 (QA Followup) lowercase the search index Zebra doesn't care about cases, but ES does and default mapping is 'control-number' Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
What about NORMARC?
(In reply to Nick Clemens from comment #21) > Created attachment 65187 [details] [review] [review] > Bug 15140 (QA Followup) lowercase the search index > > Zebra doesn't care about cases, but ES does and default mapping is > 'control-number' > > Signed-off-by: Nick Clemens <nick@bywatersolutions.com> Should we have a new bug to fix all other occurrences of Control-number?
(In reply to Katrin Fischer from comment #23) > (In reply to Nick Clemens from comment #21) > > Created attachment 65187 [details] [review] [review] [review] > > Bug 15140 (QA Followup) lowercase the search index > > > > Zebra doesn't care about cases, but ES does and default mapping is > > 'control-number' > > > > Signed-off-by: Nick Clemens <nick@bywatersolutions.com> > > Should we have a new bug to fix all other occurrences of Control-number? Please open up a new report for that. Thanks.
(In reply to Jonathan Druart from comment #22) > What about NORMARC? The NORMARC XSLTs are way out of sync with the MARC21 ones. (Lots of patches were pushed without this question.) Since it is only a presentation issue, I would not like to address that here. Those responsible for NORMARC should be more involved in keeping it updated. Personally, I would not move that burden to MARC21 developers.
(In reply to Marcel de Rooy from comment #25) > (In reply to Jonathan Druart from comment #22) > > What about NORMARC? > > The NORMARC XSLTs are way out of sync with the MARC21 ones. (Lots of patches > were pushed without this question.) Since it is only a presentation issue, I > would not like to address that here. Those responsible for NORMARC should be > more involved in keeping it updated. Personally, I would not move that > burden to MARC21 developers. Did we already agree on that?
I think Marcel is right - we should develop them independently, because there is only a very limited number of people who know NORMARC - not sure if there is English documentation available even.
(In reply to Marcel de Rooy from comment #24) > (In reply to Katrin Fischer from comment #23) > > (In reply to Nick Clemens from comment #21) > > > Created attachment 65187 [details] [review] [review] [review] [review] > > > Bug 15140 (QA Followup) lowercase the search index > > > > > > Zebra doesn't care about cases, but ES does and default mapping is > > > 'control-number' > > > > > > Signed-off-by: Nick Clemens <nick@bywatersolutions.com> > > > > Should we have a new bug to fix all other occurrences of Control-number? > > Please open up a new report for that. Thanks. Done - bug 18981
(In reply to Katrin Fischer from comment #27) > I think Marcel is right - we should develop them independently, because > there is only a very limited number of people who know NORMARC - not sure if > there is English documentation available even. Definitely no info in any language other than Norwegian! The good news is, the National library of Norway has decided to kill off NORMARC and use MARC21 instead. See bug 18984 for some more details. So definitely go ahead and ignore NORMARC! :-)
Pushed to master for 17.11, thanks to everybody involved!
Enhancement not pushed to 17.05.x