plugin_event issueshttps://gitlab.in2p3.fr/tev/plugin_event/-/issues2019-12-05T19:23:40+01:00https://gitlab.in2p3.fr/tev/plugin_event/-/issues/31migrate to python3.72019-12-05T19:23:40+01:00LE GAC Renaudmigrate to python3.7* python 3.7
* web2py 2.18.3
* matplotlib 3.1.1
* pandas 0.25.2
* plugin_dbui 0.9.9.1-py37* python 3.7
* web2py 2.18.3
* matplotlib 3.1.1
* pandas 0.25.2
* plugin_dbui 0.9.9.1-py37https://gitlab.in2p3.fr/tev/plugin_event/-/issues/6Add the possibility to filter a list / metric on the field history.data2018-09-16T18:39:26+02:00LE GAC RenaudAdd the possibility to filter a list / metric on the field history.data* In list (metric) filter add the field data
* The filter operation is `contains`* In list (metric) filter add the field data
* The filter operation is `contains`https://gitlab.in2p3.fr/tev/plugin_event/-/issues/7Remove the constraint on the start date in reports2018-09-16T18:39:26+02:00LE GAC RenaudRemove the constraint on the start date in reports* Currently the `start date` has to be specified in list / metric reports.
* Remove this constraint.
* If not specified scan all database entries.* Currently the `start date` has to be specified in list / metric reports.
* Remove this constraint.
* If not specified scan all database entries.https://gitlab.in2p3.fr/tev/plugin_event/-/issues/1Rename database fields2018-05-18T05:04:30+02:00LE GAC RenaudRename database fields* In order to keep consistency with the others data table and to avoid ambiguities, rename the database fields in the following ways:
```
objects.reference --> objects.object
objects.serial_number --> objects.reference
obj...* In order to keep consistency with the others data table and to avoid ambiguities, rename the database fields in the following ways:
```
objects.reference --> objects.object
objects.serial_number --> objects.reference
objects.batch_number (decide to keep it or not)
events.data --> events.model (to avoid confusion with history.data)
```https://gitlab.in2p3.fr/tev/plugin_event/-/issues/25Add a the table blobs or materials2018-05-18T05:04:30+02:00LE GAC RenaudAdd a the table blobs or materials* link a series of file or URL to an event.
* The `blobs` table has four fields: `id`, `id_events`, `file name` or `path` and `blob`.
* No foreign key in the table `history`.
* Require to develop callback on record insert, delete or...* link a series of file or URL to an event.
* The `blobs` table has four fields: `id`, `id_events`, `file name` or `path` and `blob`.
* No foreign key in the table `history`.
* Require to develop callback on record insert, delete or update.
* Add the entry `Add material` in the `HistoryContextMenu`.
* Tune the component `RowHistoryData` to display a list of hyperlink to download file, follow URL, *etc*.
* It might be usefull to have a dedicated node which allows to see the material for event and to filter them.
* ...https://gitlab.in2p3.fr/tev/plugin_event/-/issues/27Add link in list to edit event2018-05-18T05:04:30+02:00LE GAC RenaudAdd link in list to edit event* In a list the column `id` should be a link
* Clicking on the link open a form allowing to edit the event
* This technique is used in limbra* In a list the column `id` should be a link
* Clicking on the link open a form allowing to edit the event
* This technique is used in limbrahttps://gitlab.in2p3.fr/tev/plugin_event/-/issues/28New interface to create list2018-05-18T05:04:30+02:00LE GAC RenaudNew interface to create listCreate a list is still complicated. To ease this process create a new interface.
* When a source is displayed, customized it like a spreadsheet and save it:
- Hide/show column via the grid interface
- Tune the size of the colu...Create a list is still complicated. To ease this process create a new interface.
* When a source is displayed, customized it like a spreadsheet and save it:
- Hide/show column via the grid interface
- Tune the size of the column via the grid interface
- Entry in a context menu to Add / delete columns
- Entry in a context menu to Add a `computed column`
- Entry in a context menu to define `sorter`
- Entry in a context menu to define the `query`
- Entry in a context menu to define `protection`
- Entry in a context menu to `Save as...`
* When a list is displayed is it also possible to customize, duplicate or save it:
- On top of the previous case, add an entry in the context menu `Save..`
* Remove the viewport node `Configure lists`
* Rename the viewport node `Lists` → `My lists`https://gitlab.in2p3.fr/tev/plugin_event/-/issues/29Bug in UserDataMultiDefault2018-05-18T05:04:30+02:00LE GAC RenaudBug in UserDataMultiDefault* `plugin_dbui 0.9.8.2`
* The following sequence is not working:
- Open the `History` table
- Create a new event `Budget xFR` (OK)
- Open and existing event `Budget xFR` (OK)
- Create a new event `Budget xFR` -- faile...* `plugin_dbui 0.9.8.2`
* The following sequence is not working:
- Open the `History` table
- Create a new event `Budget xFR` (OK)
- Open and existing event `Budget xFR` (OK)
- Create a new event `Budget xFR` -- failed since the data block is empty
* The issue is located in the widget `UserDataMultiDefault`https://gitlab.in2p3.fr/tev/plugin_event/-/issues/30Bugs...2018-05-18T05:04:29+02:00LE GAC RenaudBugs...Series of bugs appears during the preparation of the EAP in September 2017. They are related to the *user data block* in the form as well as in the grid.
In the form
* Update an entry in the history grid (for an vent with a non-empty da...Series of bugs appears during the preparation of the EAP in September 2017. They are related to the *user data block* in the form as well as in the grid.
In the form
* Update an entry in the history grid (for an vent with a non-empty data block)
* Move to the tab *event*. In most of the case the data block is empty
* Close the form an reopen it, then the data block is OK
In the grid
* Select an event
* Expand several data blocks
* It is working fine but after several iteration the data block is not displayed properly and the form is corrupted
* The only possibility is to restart the application
Other instabilities appears when filtering the history tables and playing with list, ....https://gitlab.in2p3.fr/tev/plugin_event/-/issues/8Sort list in decreasing order2018-05-18T05:04:29+02:00LE GAC RenaudSort list in decreasing order* List can be sort according to the value of several fields
* The sort order is always `ASC`
* Allow the `DES` using the web2py construct `~`, *i.e* `~year` or `~teams.team`, ....
* A user case is the list `track_lhcbfrance / promotio...* List can be sort according to the value of several fields
* The sort order is always `ASC`
* Allow the `DES` using the web2py construct `~`, *i.e* `~year` or `~teams.team`, ....
* A user case is the list `track_lhcbfrance / promotion CNRS` where promotion should be displayed in decreasing year.
https://gitlab.in2p3.fr/tev/plugin_event/-/issues/9Migrate the python documentation to sphynx2018-05-18T05:04:29+02:00LE GAC RenaudMigrate the python documentation to sphynxhttps://gitlab.in2p3.fr/tev/plugin_event/-/issues/10Review code compliance with pylint and jslint.2018-05-18T05:04:29+02:00LE GAC RenaudReview code compliance with pylint and jslint.https://gitlab.in2p3.fr/tev/plugin_event/-/issues/11Run several aggregation functions on the same database field in metric 1D2018-05-18T05:04:29+02:00LE GAC RenaudRun several aggregation functions on the same database field in metric 1D* In the current implementation, an internal error is raise when runnig a metric 1D using the column `min(history.data.age)` and `mean(history.data.age)` at the same time.
* It is is related to the use of the same database field with tw...* In the current implementation, an internal error is raise when runnig a metric 1D using the column `min(history.data.age)` and `mean(history.data.age)` at the same time.
* It is is related to the use of the same database field with two different aggregation functions.
* It might be interesting to remove this bottleneck.
* One user case can be found in `track_lhcbfrance` *metric1D / promotion per grade*. The idea is to display at the same time the min, mean and max age for a given grade.https://gitlab.in2p3.fr/tev/plugin_event/-/issues/12Add grid filter to the history table using the field data2018-05-18T05:04:29+02:00LE GAC RenaudAdd grid filter to the history table using the field data* Add a *grid filter* on the `history` table using the field `data` and the operator `contains`
* Does not work with `plugin_dbui` 0.8.1
* The main `viewport` is not render properly
* No error message
* ...* Add a *grid filter* on the `history` table using the field `data` and the operator `contains`
* Does not work with `plugin_dbui` 0.8.1
* The main `viewport` is not render properly
* No error message
* ...https://gitlab.in2p3.fr/tev/plugin_event/-/issues/13change javaScript namespace2018-05-18T05:04:29+02:00LE GAC Renaudchange javaScript namespace* `plugin_dbui` 0.9.0 or higher
* Change javaScript namespaces to `Dbui` and `TrackEvents`* `plugin_dbui` 0.9.0 or higher
* Change javaScript namespaces to `Dbui` and `TrackEvents`https://gitlab.in2p3.fr/tev/plugin_event/-/issues/14Add the table domain2018-05-18T05:04:29+02:00LE GAC RenaudAdd the table domain* In the current version the field `domain` exists in the `teams` table.
* It is at a wrong place since we can have people in the same team working in different domain, *e.g* LAL covering both flavor physics and Heavy Ion.
* In order t...* In the current version the field `domain` exists in the `teams` table.
* It is at a wrong place since we can have people in the same team working in different domain, *e.g* LAL covering both flavor physics and Heavy Ion.
* In order to cover all cases, add the table `domains` with one field `domain`.
* Remove the field `domain` in the `teams` table.
* Link the `history` table to the `domain` one.
* Modify selector and filter accordingly.https://gitlab.in2p3.fr/tev/plugin_event/-/issues/15Migrate to Ext JS 62018-05-18T05:04:29+02:00LE GAC RenaudMigrate to Ext JS 6https://gitlab.in2p3.fr/tev/plugin_event/-/issues/16Create the plugin_event2018-05-18T05:04:29+02:00LE GAC RenaudCreate the plugin_event* In order to create dedicated application like `track_lhcbfrance` migrate the core of the `track_events` application into the `plugin_events`. By doing this, dedicated application can have their own reports, scripts, *etc*.
* Migrate t...* In order to create dedicated application like `track_lhcbfrance` migrate the core of the `track_events` application into the `plugin_events`. By doing this, dedicated application can have their own reports, scripts, *etc*.
* Migrate the content of `models`, `modules`, `views` in `plugin_events`
* Add a layer to configure the plugin by selecting for examples database tables. In some case the user can instantiate only the table `history` while it will provide its own table `domains`, `people`, `object` with the current structure and additional field. In others cases, you are not interested by the table `lists`, `metric1D`, `metric2D` since the application provide only a set of pre-defined reports.
* A possible way of doing it, is to create a Class `EventModel`.
* ...https://gitlab.in2p3.fr/tev/plugin_event/-/issues/17Improve the context menu of the history table2018-05-18T05:04:29+02:00LE GAC RenaudImprove the context menu of the history table* Revisit the context menu of the history table.
* It should contains the action `new` event, `split` event and `close` event.
* Keep the action `update`, `duplicate` and `destroy`.
* The action `split` is a wizard. It request the `e...* Revisit the context menu of the history table.
* It should contains the action `new` event, `split` event and `close` event.
* Keep the action `update`, `duplicate` and `destroy`.
* The action `split` is a wizard. It request the `end_date`. It closes the select event by the `end_date`, duplicate it with the `start_date` equal to `end_date` + 1 day and allow the user to update the other field.
* The action `close` event is also a wizard requesting only the `end_date`.https://gitlab.in2p3.fr/tev/plugin_event/-/issues/18Improve widgets to filter on data in selector2018-05-18T05:04:28+02:00LE GAC RenaudImprove widgets to filter on data in selector* Use the tool `Dbui.form.plugin.Mapper` in `Selector` uses by reports.
* Upgrade `TrackEvent.grid.HistoryFilter` by using Mapper`* Use the tool `Dbui.form.plugin.Mapper` in `Selector` uses by reports.
* Upgrade `TrackEvent.grid.HistoryFilter` by using Mapper`