hxlstandard / hxl-proxy Goto Github PK

Move the save form to a separate screen or pop-up in filter-preview, and perhaps show only the first ~25 lines of a dataset, with a link to show the whole thing.

Have removed breadcrumb navigation, but now there's no good way to get back to the dataset from a visualisation. Need to rethink the whole navigation, now that we've moved to Bootstrap.

http://127.0.0.1:5000/data/edit?url=https%3A//docs.google.com/spreadsheets/d/1_TFjKh_rcZmYFjgEDhDXoya16piFZHMpmZgLzrqlS5Y/export%3Fformat%3Dcsv%26gid%3D2125848767%26single%3Dtrue

Allow a user to save a filter definition, with a password for editing. That way, the original URL doesn't have to be exposed, and the share URL is shorter.

Add the functionality from hxlmerge.

It's the redirect to /edit without a password

The home page for hxl-proxy shouldn't necessarily be a filter-definition page. Choose a different path.

hxl.parser => hxl.io

The public link style doesn't make it through munge_url()

Let people define stub names for when a filter is downloaded (e.g. "somalia-3w-sectors"). This can come after the hash code in the URL, to avoid collisions, and a straight ".csv" or ".json" extension on the hash can redirect to the stub (as can any wrong stub).

Format dates properly, based on tag names.

Add Access-Control-Allow-Origin: * header to all data files (CSV, JSON, etc.).

Use the hashtags to guess what maps and graphs to offer by default.

Support the new hxlmerge options --replace and --overwrite (and remove --before).

Make it easy to clone a filter to start a new one.

See http://flask.pocoo.org/docs/0.10/testing/

Instead of asking for the login when the user clicks a nav item, ask for it as needed when entering the data-edit page. That way, a saved bookmark will work, and we can simplify the markup on the other data pages and in the nav menu.

Requires adding the relative URL path so that the validator can load a relatively-referenced taxonomy; or, alternately, simply abandoning relative referencing.

Instead of requiring a merge, geocode from the github.io site if there's no lat/lon or bounds.

When the target dataset does not contain a HXL hashtag row, hxl-proxy doesn't catch the exception or report any error to the user.

Add support for the libhxl add and rename filters.

For example, validate the syntax for a list of tags.

The per-dataset approach is awkward; consider migrating to a per-user authentication, maybe with HDX as an IdP.

Instead of a URL, allow an HDX CKAN resource, so that we can capture updates to the URL.

The rename filter does not preserve the original header when no new header is specified.

http://proxy.hxlstandard.org/data/edit?filter_count=7&url=https%3A%2F%2Fdocs.google.com%2Fspreadsheets%2Fd%2F1_TFjKh_rcZmYFjgEDhDXoya16piFZHMpmZgLzrqlS5Y%2Fexport%3Fformat%3Dcsv%26gid%3D2125848767%26single%3Dtrue&format=html&filter01=add&add-tag01=%23country%2Bcode&add-value01=GIN&add-header01=Country+code&add-before01=on&filter02=add&add-tag02=%23country&add-value02=Guinea&add-header02=Country&add-before02=on&filter03=rename&rename-oldtag03=%23region&rename-newtag03=%23adm1&rename-header03=&filter04=&filter05=&filter06=&filter07=

Throws an exception related to TagPattern -- could be a problem in libhxl-python

In the edit view, let the user choose a specific part of the filter pipeline to preview.

Make sure that the preview point doesn't get captured in the profile itself.

In the data menu, add a "validate" option.

Make it possible to save a schema URL with the filter.

• Move validation to main navigation menu
• Make validation work for unsaved profile
• Test with custom schema
• Test that custom schema saved with profile

Do as with the tagger, and have a table of fields to add.

Add purpose-built forms to simplify generating maps and graphs.

Allow the user to specify a password at filter-creation time, then require that for future editing (and also set a cookie for good measure).

Typing e.g. "country" into the tag field of the Add filter adds "country" instead of "#country" as the hashtag. This could be a problem in other single-tag fields as well.

Right now, still get a popup dialog when there's already a valid login cookie.

Make sure all the buttons make sense, and maybe add a prominent Save button (even though it's in the navmenu).

Use the results of count to graph at multiple levels.

Instead of a filter being tied to only one dataset, allow for reusable recipes.

Provide an overview page listing all saved profiles (maybe have a visibility flag).

When the user chooses to edit an existing filter, don't make the user enter the password again on the edit form.

Reuse code for picking dataset from HDX.

All rows with lat/lon or bounds turned into features.

Other columns become properties of each feature.

PreviewFilter is getting passed through the edit page even when there is a null source, causing an exception.

Shows only 2/4 rows of this dataset: http://127.0.0.1:5000/data/edit?filter_count=7&format=html&url=https%3A//docs.google.com/spreadsheets/d/1ytPD-f4a8CbNKTfMS3EqZOpBo9LWCk_NDKxJCgmpXA8/edit%3Fusp%3Dsharing&filter07=&filter04=&filter05=&filter02=&filter03=&filter01=&filter06=

The schema is saved the first time with the profile, but not subsequent times; in fact, it gets eliminated if I edit a profile.

When I first save a filter from the edit page, I'm prompted to enter my password before the edit page reopens.