Bug 5561

Summary: Help on summary field in authority type editor
Product: Koha Reporter: Janusz Kaczmarek <januszop>
Component: DocumentationAssignee: Chris Cormack <chris>
Status: NEW --- QA Contact: Bugs List <koha-bugs>
Severity: normal    
Priority: P5 - low CC: alex.arnaud, julian.maurice, katrin.fischer, marie-luce.laflamme, 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:
Attachments: Proposed patch

Description Janusz Kaczmarek 2010-12-30 12:50:17 UTC
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
Comment 1 Janusz Kaczmarek 2011-03-28 16:53:28 UTC Comment hidden (obsolete)
Comment 2 Janusz Kaczmarek 2011-03-28 17:01:42 UTC
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...
Comment 3 Marc VĂ©ron 2016-03-27 05:56:44 UTC
Still valid?
Comment 4 Katrin Fischer 2017-09-12 12:43:18 UTC
Hi Janusz, could you give an example we could use in the manual? I am not sure what xxx and yyy would be.
Comment 5 Marie-Luce Laflamme 2020-07-24 19:41:42 UTC
Is this still valid? Should we include this in the documentation?
Comment 6 Katrin Fischer 2020-08-30 20:09:58 UTC
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.