ppKrauss
commented
2 years ago Now we have a "conceptual reference" for selection concepts, see digital-guard/stats/docs/report-public.
Requirements for the selection interface
Some options, like license options, are few ones, can be pre-loaded into the interface, some others need ajax-check. All are available as microservice. The first draft of the interface can use only HTML <input text>, <input checkbox> and <select> tags. Input text can be enhanced by auto-complete.
- License family filter.
<input checkbox>with names and on-mouse-over hint explanation. - Jurisdiction filter, by country or more specific (ISOlabel_ext).
<select>or map or<input text>auto-autocomplete. - Layer filter.
<input checkbox>with names and icons. - Donor filter.
<select>. - Date of donation filter (received date).
<input text>(year or year-month or interval). - package number restriction (text box).
<input text>.
The "check filters" is a <input submit> button listing filter countings, but future interface can use React to enable/disable filters (perhaps need all lists in the Javascript memory)... For both, perhaps, a interface for change filter order (by drag and drop) is interesting.
All published "filtered data" as CutGeo (ex. git.digital-guard.org/preservCutGeo-BR2021 GeoJSON files) can be downloaded directly from Github website, with no bandwidth consumption from AddressForAll.
The ideal interface is a step-by-step form to select all user-needs and express it as a JSON specification (like a config file). This specification can be used by external software, as provided for in digital-guard/loadCutGeo-kit/issues/2, or in a "download needs" webpage.