Bug 11653 - For tag "020" only subfields "a" is displayed in MARC XSLT OPAC's detail template
Summary: For tag "020" only subfields "a" is displayed in MARC XSLT OPAC's detail temp...
Status: CLOSED WONTFIX
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: Main
Hardware: All All
: P5 - low minor (vote)
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-31 17:46 UTC by Claudio Costales
Modified: 2017-12-07 22:16 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 Claudio Costales 2014-01-31 17:46:19 UTC
MARC XSLT OPAC's detail template and Intranet detail template only display subfield "a" for tag "020". It is  needed  showing all subfields according MARC rules. 

example
=======
For:
020 	##$a0870686933$qv. 1$z087064302
	
Display:
ISBN 0870686933 (v. 1) ISBN (invalid) 0870684302 



Reference: http://www.loc.gov/marc/bibliographic/bd020.html
Comment 1 Tomás Cohen Arazi 2014-10-29 18:23:58 UTC
Setting as In Discussion, anyone interested please comment on the bug so we make a decision.
Comment 2 Claudio Costales 2014-10-29 18:33:56 UTC
Please look at subfield "q" too that is new in MARC and is not present neither in XSLT detail template nor cataloguing framework (default and book).
Comment 3 Tomás Cohen Arazi 2014-10-29 19:18:08 UTC
(In reply to bondiurbano from comment #2)
> Please look at subfield "q" too that is new in MARC and is not present
> neither in XSLT detail template nor cataloguing framework (default and book).

I don't think we shoud show the invalid ISBN as default, you can always fix your own XSLT (that's on of the purposes of using XSLT's for that). I'm open to other voices telling otherwise.

Regarding $q, I think it is something we should do. But definitely belonging to another bug report.
Comment 4 Owen Leonard 2017-01-05 11:55:37 UTC
No further comments, so I'm going to consider this settled for now.