Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add nicer interface for managing dataset data #39

Open
3 tasks
mjumbewu opened this issue Feb 24, 2020 · 1 comment
Open
3 tasks

Add nicer interface for managing dataset data #39

mjumbewu opened this issue Feb 24, 2020 · 1 comment
Labels
hackillinois spike 📈 Spikes will often need to be planned out into multiple issues/tasks.

Comments

@mjumbewu
Copy link
Member

mjumbewu commented Feb 24, 2020

Some things it should allow:

  • filter by type of place
  • hide/show places and submissions from the map
  • download in bulk, CSV or GeoJSON, with the ability to select/reorder/rename fields

On second thought, most of this can be done passably by the existing admin interface. It's not the nicest way, but it is 85% there. The main things that it cannot do are:

  • Easily export bulk data
  • Choose fields to export with bulk data
  • Filter/sort places by JSON-blob attributes (like place type)
@mjumbewu mjumbewu added hackillinois spike 📈 Spikes will often need to be planned out into multiple issues/tasks. labels Feb 24, 2020
@BenSturmfels
Copy link
Contributor

BenSturmfels commented Sep 8, 2021

We've built something custom along these lines - a log-in based dashboard for project stakeholders that allows them to browse, search and update places, comments and attachments to their particular projects, export as Shapefile and such. Also includes some ability for stakeholders to be able to dynamically update contents of the welcome and FAQ pages shown on front-end. It's not yet in a form that's general-purpose enough to merge into Shareabouts, but I'd be happy to discuss the approach we've taken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hackillinois spike 📈 Spikes will often need to be planned out into multiple issues/tasks.
Projects
None yet
Development

No branches or pull requests

2 participants