The process of finalizing three projects from six strong pitches was not easy, but there was a helpful air of generosity and a sense of community in the room. There was no time to dwell on the outcome as we immediately settled into our groups and in project Bandurapedia we had a quick yet fruitful discussion on roles and responsibilities. I took on the role of one of the two researchers and I will also help create content for outreach as well as shadow the Frontend/Backend programmers to satiate my interest in coding. The team agreed to share weekly reporting responsibilities by making individual entries to a shared document so the project manager had the information available for compilation. Given that each member will be taking on multiple roles, it is crucial to find ways to share the load as evenly as possible so we can meet the timelines we set ourselves.
In the past week, we set up communication channels (Signal/ google drive folders), had our first meeting over zoom and set up action items to address the proposal feedback, revision process, platform selection and collaborative agreement. We discussed options for an alternate project name since Bandurapedia indicated a larger scope than the project’s current focus on the Women’s Bandura Ensemble of North America. This also brought us to one of the major dependencies of the project that requires WBENA approval for all the content, a known risk that is acceptable considering the project’s determination to feature the community’s voice and build trust in the spirit of the slow archives approach. To mitigate the risk to the extent possible, we decided to work on an agreement with WBENA to assure transparency through the cycle, settle on conflict resolution strategies and seek early approval of prepared wireframes of the webpages. We have also set up our introductory meeting with WBENA.
The stage is now set for revising the proposal, finalizing roles and getting the show on the road. We have a long way to go, but we are coming together as a team. The team members are enthusiastic, positive, generous and there is a heartening spirit of collaboration and cooperation. The start is reassuring.
Recommended reading: One of the readings from the Politics and DH course proposes an ethical visualization workflow that could be useful to all three projects. The advice to follow an ethical approach towards data collection, curation and visualization is explained through the comparison of two projects. The approach advocating for transparency to convey the veracity of the data sources and due care to avoid biases could be particularly beneficial to the GDPW project and data normalization suggestions could be useful to consider for the carousel project if they decide to go ahead with recommending geographical areas for new carousels.