denislepage
commented
4 years ago This one will definitely need a bit more thinking on my part than #29 .
I think both ideas can share the same authentication rules. I.E. summary views can be included in the list of accessible tables.
The main difference is that in the case of data summaries, we'd definitely want to allow some filtering, and that may be less important for the other table (though potentially also useful).
Perhaps we can set up something generic way to support filtering. I'll expand on the other issue.
From Denis' email of Oct 24, 2019:
I would like to think about allowing some summaries. The main priority one is a list of events that can be used to zero-fill a partial dataset (e.g. a single species that only contains positives). We can likely replicate the same filtering rules as for the data itself (not sure if we'd allow filtering on record-level fields such as species, but probably not). There may be value in allowing more flexibility with other types of arbitrary summaries, but I think we can start with the events, and perhaps unique locations. I'll need to look at what table I would want to use for that. Most of it will be based on the indexed fields in bmde. There may already be a static summary table that I can use instead.