Add Map Creation to Admin Dashboard

[timothyfcook]

We need to think more about what this should look like.

Maybe we could build an in-browser drag-and-drop tool that lets you move around any resources you've uploaded into a visual order (a.k.a. pathway) and lets you save these as sub-topics and group sub-topical pathways into topical groups.

e.g. https://jqueryui.com/sortable/

And then... user's maps are published to a unique URL where they can share them with the public. e.g. cityasacampus.org/admin/uid123/maps/my-topical-map123

Not sure how easy this will be with the current CaaC Map, since it is currently run manually, not as-a-service on-demand. It could be fine for MVP to let users add map data to a "map queue" and then we run map-builder manually and stand-up maps for them as needed. Just so we can enable 5-10 users to start testing it for feedback.

Eventually, we should pursue both isolated map creation like this, as well as a larger universal map that is emergent (a la https://github.com/saxifrage/caac-map/issues/55)

[MatthewVita]

[dmtroyer]

I am curious how this co-exists with @whit537's current efforts, as it seems like he's putting a lot of work into automated creation of the maps?

On Mon, Sep 28, 2015 at 6:06 PM Matthew Vita notifications@github.com wrote:

[image: img] https://camo.githubusercontent.com/65ffd9963878f85ec3e94a19cd055abc8854e215/68747470733a2f2f6d656469612e67697068792e636f6d2f6d656469612f794e766c616c446e49414154752f67697068792e676966

— Reply to this email directly or view it on GitHub https://github.com/saxifrage/cityasacampus/issues/227#issuecomment-143887321 .

[timothyfcook]

Chad is just building the map creator. This will be where we start to source data for the maps and enable users to create their own maps.

[timothyfcook]

The maps are generated "automatically" (when we run gen.py) from the map data. Here I'm talking about building an admin GUI that would allow admins to manipulate their library of opportunity_instance s in the map format.

As a map-creator, I need to be able to:

• See the library of all opportunity_instance elements I have control over within my organizer permissions
• Define a topic and sub-topic for the elements (if not already defined)
• Define a map_name
• visually manipulate them into an appropriate order for the map (i.e. define the before_this and after_this attributes
• Run the map generator with the information
• Preview the map and then make any edits
• Publish the map to a unique URL that I can share with the public

[dmtroyer]

Create a new pathway, name a topic and subtopic for a group of resources for this pathway and define the order.

Start with making pathways in an effort towards interactive map making.

[chadwhitacre]

Here's where we're currently producing the JSON that the map generator depends on:

https://github.com/saxifrage/caac-map/blob/c05208f4cb9aac9c81237e16dcef4c37c6f3e522/fetch.py#L54-L129

I suppose that would need to be ported to Ruby for embedding in the Rails app. I don't think it makes sense at this point to port the whole of caac-map to Ruby. I think we should shell out to it, though we could easily teach it to take JSON on stdin if that's easier from the Ruby side.

[chadwhitacre]

Spent some time with @dmtroyer @sdanko11 just now IRL explaining the current map architecture. Sounds like a good next step is to move the /map/ subdir from the gh-pages branch over to master. I've reticketed that as #255, because as I understand it the scope of this ticket is more ambitious.

[chadwhitacre]

@sdanko11 Here's the spreadsheet we're currently using: https://docs.google.com/spreadsheets/d/1wZ2uz0KTkylLgo46fJ7gYYpNEKjVljoGTCjFecjZQ9c/edit?usp=sharing.

[timothyfcook]

Sounds like the right plan to me.

Excited for the two projects to slowly merge as we hone in on mvps for both!

On Oct 16, 2015, at 11:37 AM, Chad Whitacre notifications@github.com wrote:

Spent some time with @dmtroyer @sdanko11 just now IRL explaining the current map architecture. Sounds like a good next step is to move the /map/ subdir from the gh-pages branch over to master. I've reticketed that as #255, because as I understand it the scope of this ticket is more ambitious.

— Reply to this email directly or view it on GitHub.

[chadwhitacre]

I reopened #201 for constructing pathways. Then this ticket is about making maps, given pathways.

[dmtroyer]

I reopened #201 for constructing pathways. Then this ticket is about making maps, given pathways.

I think we can make that work. Just to clarify, in the user workflow a map will be created first, though?

[chadwhitacre]

in the user workflow a map will be created first, though?

That's not my expectation (cross-linking https://github.com/saxifrage/cityasacampus/pull/364#issuecomment-166414571 and my answer there). An organizer will only ever have two maps: draft and published. I think the best UX will be to create the underlying map object(s) on the fly as needed, rather than requiring the user to explicitly create a map object.

[dmtroyer]

Some direction from @timothyfcook and @chelseaerdner as to how or if this will fit into the mockups from https://github.com/saxifrage/cityasacampus/issues/205#issuecomment-154440422 would be super helpful for me.

[chadwhitacre]

Some direction from @timothyfcook and @chelseaerdner as to how this will fit into the mockups from https://github.com/saxifrage/cityasacampus/issues/205#issuecomment-154440422 would be super helpful

+1