Bug 29176 - Additional LOC Classifications Should Display on a Newline
Summary: Additional LOC Classifications Should Display on a Newline
Status: RESOLVED DUPLICATE of bug 27613
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: 20.05
Hardware: All All
: P5 - low trivial (vote)
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-05 13:36 UTC by Eliana
Modified: 2021-10-05 15:51 UTC (History)
0 users

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


Attachments
LOC Classification in OPAC (172.90 KB, image/png)
2021-10-05 13:36 UTC, Eliana
Details
Screenshot showing a customized display with Bug 27613 (48.37 KB, image/png)
2021-10-05 15:33 UTC, Owen Leonard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eliana 2021-10-05 13:36:02 UTC
Created attachment 125737 [details]
LOC Classification in OPAC

When a title has multiple LOC classifications they appear smooshed together with no spaces in both the staff client and OPAC. If there are multiple classifications then additional ones should appear on a newline for legibility's sake. 

Another option would be to use the pipe character to separate additional classifications, similar to how subject headings appear.
Comment 1 Owen Leonard 2021-10-05 15:24:20 UTC
I'm going to mark this a duplicate of Bug 27613 because the patch for that bug makes improvements which I think are the correct solution for this bug report.

*** This bug has been marked as a duplicate of bug 27613 ***
Comment 2 Owen Leonard 2021-10-05 15:33:28 UTC
Created attachment 125745 [details]
Screenshot showing a customized display with Bug 27613

This is what it would look like if you added custom CSS separating the tags. Otherwise the pipe character would appear where the ♦ is.
Comment 3 Eliana 2021-10-05 15:51:24 UTC
(In reply to Owen Leonard from comment #2)
> Created attachment 125745 [details]
> Screenshot showing a customized display with Bug 27613
> 
> This is what it would look like if you added custom CSS separating the tags.
> Otherwise the pipe character would appear where the ♦ is.

Thank you so much, that's exactly what I was looking for!