| | 21 | |
| | 22 | === Use cases (Ate en Erik) === |
| | 23 | 1) A simple one: Ate would like to be able to generate a simple overview of the animals currently alive, in a second stage maybe filtered or grouped by a second(/third/n th) criterion such as location. |
| | 24 | --> steps involved (for as far as I can see now) |
| | 25 | * Filter targets by rights: (only show the targets I am entitled to see), this has to happen under the hood, currently not implemented I guess. |
| | 26 | * Filter targets by type: --> only show targets of type animal. This is currently implemented in Eriks matrix by filtering on labeled groups prior to generating the matrix, the matrix therefore only contains observable targets of one type. Should this be reconsidered for a generic matrixviewer? |
| | 27 | * Add an EAV --> in the case of AnimalDB: the Status event. |
| | 28 | * filter by the most recent application of the status event. (animals can have multiple protocol applications, in the case of the status feature only the most recent protocol application is valid. |
| | 29 | * filter by active/inactive values. --> if endtime is present, then the animal is dead/not present, if it is not set, the animal is still alive. In this case the value istself (active) is irrelevant but the presence of endtime siganls the relevant change. In Erik's current implementation it is impossible to filter/select/group by the times attached to the event, making it impossible to generate this overview. |
