[gc_dataset_importer] Action buttons after a successful upload

[nicopace]

While uploading the data, I noticed that this pipeline has one of two paths:

we upload another dataset
we use the data to create a view in explorer
Would be good to provide buttons for each of these actions straight from here.

[nicopace]

For gc-explorer, it is done doing a POST call to /api/config/new_table/{name_of_table} ... so it might be easy to replicate it from windmill.

[nicopace]

Related to ConservationMetrics/gc-explorer#188

[rudokemper]

Note that the GC Explorer API is not exposed externally at the moment. So this work would require work on GC Explorer to do something like whitelist other subdomains (e.g. windmill.{domain} can make API requests to explorer.{domain}

[nicopace]

Note that the GC Explorer API is not exposed externally at the moment. So this work would require work on GC Explorer to do something like whitelist other subdomains (e.g. windmill.{domain} can make API requests to explorer.{domain}

I think the request is simpler than what it may feel.
It would be a link to the right page that creates the config... or even the instruction for the person that uploaded the dataset to go and do that step (or the other workflow of creating a chart or dashboard on superset).

[rudokemper]

I think the request is simpler than what it may feel. It would be a link to the right page that creates the config... or even the instruction for the person that uploaded the dataset to go and do that step (or the other workflow of creating a chart or dashboard on superset).

This actually brings up an interesting quirk about our approach to integrating third party softwares as much as possible: they all have their own RBAC system, that are fit-for-purpose for the functionality of the specific tool.

• Windmill has Admin, Operator, Developer
• GC Explorer (and Landing Page) has Admin, Member, Guest, SignedIn (aka Public) -- largely mirroring what Terrastories does
• Superset has a range of standard roles e.g. Admin, Gamma, Alpha but you can create your own

Currently, the analog of "Operator" in GC Explorer does not exist. One has to be a GC Explorer Admin to access /config. So a link to that page would not work for a Windmill Operator user, who is not likely to be an Admin in GC Explorer.

I think the best we can do for now is instructions. Maybe we can link to a page on GC Docs for more information?

[rudokemper]

• GC Explorer (and Landing Page) has Admin, Member, Guest, SignedIn (aka Public) -- largely mirroring what Terrastories does

To be fair, in Terrastories a "Member" role can add / edit data. They just cannot access any of the admin functionality like overall Community settings and user management. So maybe more effort can be made to bring the GC Explorer "Member" role in-line with the "Operator" role in Windmill.

But giving access to the /config route is much more precarious than Terrastories editing permissions. You can easily break stuff in there, and there some access tokens like Mapbox and Planet.

Maybe there is a future middle ground where a Member can do a limited amount of things in /config including setting up a new view with i.e. an already set-up Mapbox basemap, but we're a ways off from that for now.

[nicopace]

I think the best we can do for now is instructions. Maybe we can link to a page on GC Docs for more information?

I like this approach for now.
And eventually reflect on the permissions systems.