| Summary: | Help on summary field in authority type editor | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Janusz Kaczmarek <januszop> |
| Component: | Documentation | Assignee: | Chris Cormack <chris> |
| Status: | NEW --- | QA Contact: | Bugs List <koha-bugs> |
| Severity: | normal | ||
| Priority: | P5 - low | CC: | alex.arnaud, julian.maurice, marie-luce.laflamme, phil, veron |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Attachments: | Proposed patch | ||
Created attachment 3469 [details]
Proposed patch
Comment on attachment 3469 [details]
Proposed patch
The attachment has been added here by mistake. I am sorry -- I do not know how to erase it...
Still valid? Hi Janusz, could you give an example we could use in the manual? I am not sure what xxx and yyy would be. Is this still valid? Should we include this in the documentation? Can some of our UNIMARC devs help out here? I am looking for verification of comment#1 and an example that we could put in the manual. Sort of still valid, but not exactly.
At first the feature applied to both MARC21 and UNIMARC, but then it became UNIMARC only. Janusz wanted the documentation to say that it was UNIMARC only, but now the documentation no longer exists at all. Which is fine, it was wrong. At one point you could only have four characters (not three) before and after the field number and subfield code, but that limit is gone, and it was never limited to digits, because the whole point was punctuation.
You can see examples by looking at a UNIMARC install, because we actually ship it by default for UNIMARC. Administration - Authority types, for any type other than Default look at the Summary column.
It's an attempt at dealing with the fact that UNIMARC tends to use multiple subfields, and to not put the ISBD punctuation that goes between them into the authority record. So while a MARC21 authority would have 100$a as "Smith, Bessie," and 100$d as "1894-1937" and if you just stick them together with a space between, you get the correct punctuation, UNIMARC would have 200$a "Smith" 200$b "Bessie" 200$f "1894-1937" so just sticking them together doesn't look good, or correct, since correct for UNIMARC would be "Smith, Bessie (1894-1937)".
So in a UNIMARC install the default Summary for Personal Name is the template "[200a][, 200b][ 200d][ ; 200c][ (200f)]" which says to show 200$a then if there's a 200$b show it after comma space, then if there's a 200$d show it after a space, then if there's a 200$c show it after space semicolon space, then if there's a 200f show it after space ( with a ) after it. That's all fine, it creates a properly punctuated heading, but it doesn't go far enough, and nothing stops the default summary that was intended to only be created when there's no template from showing.
The default summary is a link to the authority details page wrapped around the heading, followed by (on new lines) see-from, see-also, and other scripts.
The other thing that's untrue in what the former documentation said is "things outside [] are kept as is (including HTML)" because now we escape anything and everything, lots of things twice. So you can't imitate the link to details in a Summary template, and if you want to include see-from, see-also, other-scripts, and notes, you're going to have to do it all in one run-on line.
And there's also currently no way to hide the default summary even if you could completely replace it (other than hiding it with CSS, and that may be what people supporting UNIMARC installs do instead of upstreaming a fix). Once upon a time, we only built the default one if you didn't have a template, but now we build them both. And although jcamins did see that showing both was silly, and he added an "UNLESS ( summary.summaryonly )" block to allow the default one to be hidden, he must have then realized there wasn't any way to actually replace it, because he didn't add any code that would ever set summary.summaryonly.
Sorry, I don't know how to distill that down to a manual entry. "If you like the better punctuated version and can live with having to go to the Actions menu to get to MARC preview, you might like to have something like #authorities_searchresultlist_results .authorizedheading { display: none; } in your IntranetUserCSS and something similar in OPACUserCSS so the unpunctuated version doesn't show."?
|
I have dug through C4::AuthoritiesMarc::BuildSummary and, if I understand well, what on-line help says on summary: >> The summary contains an "ISBD" like description to explain how the entry must be shown in the result list. The syntax is : * [xxxFFFSyyy] where are up to 3 digits BEFORE the field, FFF the field number, S the subfield code, yyy up to 3 digits AFTER the field. * things outside [] are kept as is (including HTML) * repeatable fields are managed. << is relevant for UNIMARC authorities *ONLY*. For MARC21 the content of the summary field, taken as string, will just precede the summary constructed by the function. Am I right? If so then I think this remark should be in the help file not to confuse users. Regards, Janusz