joebillings
commented
4 years ago Update: We removed Secondary Activities and Organisational Structure from the map shortly before releasing Solidarity Oxford.
The reason for this was twofold - sorting the data was taking too long and we were getting the data in a suboptimal way.
When sse_initiative.js processes the data it expects each datapoint to contain represent a unique initiative. Including organisational structure and secondary activities in the query will generate multiple datapoints for some initiatives because the respective fields can contain multiple values.
Instead of adding UID checking to see which initiative we were dealing with, we waited until the initiative had been generated and used a new query for it to find the organisational structure and secondary activities. This was at best resource intensive and slow and at worst generated browser errors due to the number of requests made.
I propose that we adapt the existing query to include the organisational struct and secondary activities and check the UID of each datapoint before processing to see if the values need adding to an existing initiative or not.
This should be possible by checking against the object initiativesByUid.
sunnydean
ColmMassey
The Map App already knows about the secondary activities, we just need to alphabetise the structure that stores them before they are displayed in the directory.
It was suggested that we also have an indication of initiatives' activities in the initiative popup. Since we're using colours, this could be a row of coloured circles that each have a tooltip to display the activity when hovered over.