Ideas: possibly improvements to the output of the metrics command

[andrewphilipsmith]

Draft:

• --summary (just show the number of metrics that match the search criteria)
• --exclude-description (the description field can be very verbose. The output would be more readable if it was excluded in some cases).
• --unique-values / group-by. If I do a search that generates lots of results, I want to get back the list of unique titles / unique geometries etc (so that I know have to refine my search in future).
• Add functionality to filter for "derived metrics"/"original census metrics only" (see Add basic population layer from popgetter a-b-street/15m#10 (comment))
• Add ability to search by source_data_url
• Add ability to search with regex (match_type: "exact", "regex" to include in CLI but also add "startswith", "contains" internal API)
• Add ability to set case sensitivity for search

[andrewphilipsmith]

Related to #80 and #64:

Regex switch

(--regex | --exact-match)
The search/filter arguments should either (a) all be interpreted as exact matches or (b) all be interpreted as regexs.

The relevant arguments are:

  -g, --geometry-level 
  -s, --source-data-release 
  -p, --publisher 
  -c, --country 
      --source-metric-id <SOURCE_METRIC_ID>
      --hxl 
      --name 
      --description

Notes

• -t, --text Should always be interpreted as regex irrespective of the switch.
• For all other fields, the default value should be --exact-match.
• If a user requires a mixture of exact match and regexs, it is assumed that that user would be able to craft their regexs to give exact matches in the relevant fields:

popgetter metrics --geometry-level "^oa$" --description "something interesting"

Case insensitive

There should be a switch (--case-sensitive | --case-insensitive)

The default value should be --case-insensitive.