[Koha-bugs] [Bug 10212] Columns configuration for tables

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10212

--- Comment #46 from Jonathan Druart <jonathan.druart at biblibre.com> ---
Created attachment 29076
  -->
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=29076&action=edit
Bug 10212: Columns configuration for tables

This development introduces ColVis into Koha and provides a configuration
page for columns visibility.

ColVis is a plugin for DataTables. It allows to change the visibility of
the columns in the table.

* This development adds:
  - the js and css file for ColVis
  - a new DB table 'columns_settings'
  - a new template plugin 'ColumnsSettings'
  - a new package C4::Utils::DataTables::ColumnsSettings
  - a new admin page admin/columns_settings.pl

* How it works:
A yaml file is created (admin/columns_settings.yml) in order to take an
inventory of all tables where ColVis is implemented. This file is read
to create the list of modules, pages and tables in the configuration
page.
There are 3 possible keys in the yml:
 - is_hidden: default is 0
The column will be hidden.
 - cannot_be_toggled: default is 0.
ColVis will allow to hide/show the column.
 - cannot_be_modified: default is 0
Default values (in the yml) won't be modifiable.

When a user changes (or saves) the configuration for one module, all
columns are added to the DB table. The values in the DB get the upper hand
on the yaml values.

* Humm, strange?
It seems weird to have 2 storages for the same values. But I
think it will be easy to add an entry and maintain the yaml rather than
adding a new row (and new entry in updatedatabase script) in the DB.

* Test plan:
1/ Execute the updatedatabase in order to create the new table.
2/ Take a look to the yml structure.
3/ Go on the checkouts page (circ/circulation.pl).
4/ Check that you cannot hide the 3 last columns on the issues table.
5/ Check that you cannot hide the 2 last columns on the holds table.
6/ Try to hide/show columns.
7/ Go on the columns configuration page (admin/columns_settings.pl).
8/ Only the last tab are filled with data. Check/uncheck checkboxes and
save.
9/ Go on the checkouts/holds page and check that the behavior is what
you expected.
10/ Give me some feedback :)

* To go further: We can imagine that the configuration is saved for each
user (and not globally like it is made with this patch).

Signed-off-by: sonia bouis <sonia.bouis at univ-lyon3.fr>

-- 
You are receiving this mail because:
You are watching all bug changes.