Bug 19239 - Cataloguing authority search result list to show double dashes for selected MARC 6XX subfields
Summary: Cataloguing authority search result list to show double dashes for selected M...
Status: RESOLVED DUPLICATE of bug 11442
Alias: None
Product: Koha
Classification: Unclassified
Component: MARC Authority data support (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-01 16:19 UTC by Iming Chan
Modified: 2021-03-18 18:03 UTC (History)
3 users (show)

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


Attachments
Authority search results (176.01 KB, image/png)
2018-12-26 06:06 UTC, Iming Chan
Details
Authority search results (in Cataloging Authorties plugin) (108.01 KB, image/png)
2018-12-26 06:07 UTC, Iming Chan
Details
Normal bibliographic view (in Cataloging) (196.82 KB, image/png)
2018-12-26 06:08 UTC, Iming Chan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Iming Chan 2017-09-01 16:19:18 UTC
On the cataloguing authority search result result list, show double dashes (--) before MARC 6XX subfields $v, $x, $y and $z data.

Currently, the result list shows as:

Australia History 2001-

Enhanced authority result list will show the above heading as:

Australia -- History -- 2001-
Comment 1 Iming Chan 2018-12-26 06:06:52 UTC
Created attachment 83485 [details]
Authority search results
Comment 2 Iming Chan 2018-12-26 06:07:31 UTC
Created attachment 83486 [details]
Authority search results (in Cataloging Authorties plugin)
Comment 3 Iming Chan 2018-12-26 06:08:08 UTC
Created attachment 83487 [details]
Normal bibliographic view (in Cataloging)
Comment 4 Katrin Fischer 2018-12-28 07:16:26 UTC
I was wondering if this should be using the AuthoritySeparator system preference?
Comment 5 Phil Ringnalda 2021-03-18 18:03:03 UTC

*** This bug has been marked as a duplicate of bug 11442 ***