I have a shallow tree to display: action -> action item -> error
There can be millions of actions, tens to thousands of items per action and (usually) 0 to 1 errors per item. There can be also errors for an action (then I guess tens of them).
Obviusly with that amount of data actions and action items need to have some filtering.
The goal is to:
- quickly see the status of an action
- to browse errors for an action
- to see on which action items the action was executed
All of these 3 object have more properties than the columns I could fit resonably in a table (but not too much, 5-15 at the moment).
Do you have some pattern for showing such data? Would you use 2 paginated tables for actions and items, the items table depending on actions table? Some kind of paginated tree? What is your suggestion for such kind of data?