Open DerekCaelin opened 1 year ago
This increased in size from 7 to 12 because of discovered complexity:
Right now our data model looks kind of like this for memberships:
landscape -> group -> memberships
And the idea is to change it to:landscape -> membership list -> memberships
The issue I found is that shared files/links are also under this structure:landscape -> group -> shared files/links
So, I can’t remove the dependency from landscapes to groups without breaking the relationship between landscapes and files/link.... This is not a blocker just adds more effort to the task
5 points of effort were addressed in October, 7 will be done in November
In Landscapes and Groups, use the model for membership list we developed for story maps, which will allow us to be more flexible.