search

TravelMapping / DataProcessing

Data Processing Scripts and Programs for Travel Mapping Project
4 stars 6 forks source link

Store "dashboard" information for easy display #69

Open jteresco opened 6 years ago

jteresco commented 6 years ago

Related to #68, storing information that could be used to have a "developer dashboard" kind of page seems useful. Key pieces of information from the site update log could be displayed more prominently on such a page. Information to store and display could include general stats about the most recent site update, counts of the number of datacheck errors in various categories, lists of problems encountered (like those described in #68), plus things like the number of unmatched wpt files. Ideas for other useful items are welcome.

michihdeu commented 6 years ago

A filter per contributor could be helpful. Or that an user-specific link works:

http://tm.teresco.org/devel/datacheck.php?rg=deu-bb,deu-be,deu-bw,deu-by,deu-hb,deu-he,deu-hh,deu-mv,deu-ni,deu-nw,deu-rp,deu-sh,deu-sl,deu-sn,deu-st,deu-th,aut,lie,che,bel,hrv,nld,cze,ltu,swe

Only the first region parameter works now.

jteresco commented 6 years ago

Filtering by contributor sounds useful here and probably in some other contexts. Ideally we'd store that information somewhere, like in the countries.csv, regions.csv file and/or systems.csv files for easy addition to the DB to support subsequent filtering. Here's a quick first thought. If a contributor is listed as responsible for a country, that would filter down to regions of that country unless overridden by a different entry in regions.csv. Would there be any case we'd want a system to override region/country? Maybe if someone's developing a new system but aren't handling maintenance on active systems in that region?

michihdeu commented 6 years ago

I think filter by region would be fine.

If one develops a new system and doesn't maintain the region, it's still possible to modify routes of other systems, e.g. for adding a new waypoint to an existing route for a route of the new system. If one really wants to check this, it would be possible to filter for this region only.

Keep it simple.

jteresco commented 4 years ago

I was thinking about this idea again, in the context of being able to see the progression of various parts of the project over time. Possibly using a more persistent table in the DB, add new entries for each site update tracking various project stats, and be able to look back at them. This could, for example, show growth of the number of systems/routes/mileage, fluctuations in datacheck errors, etc.