Bug 17598 - Make use of itemtypes.summary
Summary: Make use of itemtypes.summary
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-09 14:53 UTC by Magnus Enger
Modified: 2019-09-24 05:33 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Who signed the patch off:
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 Magnus Enger 2016-11-09 14:53:58 UTC
There is a field called itemtypes.summary in the DB, but as far as I have been able to tell, it is not displayed anywhere. Please enlighten me if I am wrong! :-) 

Here is the definition in installer/data/mysql/kohastructure.sql:

  summary text, -- information from the summary field, may include HTML
Comment 1 Owen Leonard 2019-03-07 19:53:25 UTC
Do we have a good reason to start making use of itemtypes.summary or should we drop it?
Comment 2 Katrin Fischer 2019-03-07 19:54:38 UTC
I think it was once explained as a UNIMARC feature to me. Adding Frido and Victor - maybe one of them knows.
Comment 3 Fridolin SOMERS 2019-03-08 10:14:36 UTC
Oh looks like its an old trick to customize search results :
https://gitlab.com/koha-community/Koha/blob/fcd6bdc5b8ed5cd48b19d03a86e2ab9aaa0b0626/C4/Search.pm#L1963

This is useless with XSLT display.

I think it can be removed from db and item types configuration page.
Comment 4 Fridolin SOMERS 2019-05-15 12:03:16 UTC
Ah looks like it is used to customise addbooks.tt display :

https://gitlab.com/koha-community/Koha/blob/604c7b818b63b93c66bb751ceb9d99bc1c109be9/koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/addbooks.tt#L80

I think we should remove this code (also from C4/Search.pm).
Comment 5 Katrin Fischer 2019-09-24 05:33:38 UTC
Some working test plan is on bug 23663.

It has some issues, like displaying <br/> in the result list when activated.

I think if we can't implement the feature for XSLT results, we should remove it.