"

Section 2 – Responsibilities and Resources in Research Partnerships

Balancing budgets and data needs

Billie Hu

In addition to relationship building, effective data management requires careful planning of practical things like resources and costs. These should be approached collaboratively, considering the needs and constraints of all partners.

Examples of resource needs:

  1. Technical infrastructure: Discuss and assess the hardware and software needed for data collection, analysis, storage, and sharing.
    • Examples: servers, storage devices, cloud services, or database applications.
  2. Personnel and expertise: Identify who will be responsible for data-related tasks such as collection, cleaning, documentation, or dissemination.
    • Examples: community members, researchers, data managers, or external consultants.
  3. Training and capacity building: Provide training for community members and researchers to strengthen their skills in data stewardship.
    • Topics might include data quality, ethical principles, and best practices tailored to the project.
  4. Access and sharing services: Plan for how data will be made accessible and usable for both researchers and the community.
  5. Collaborative cost planning: Estimate costs together, being mindful of both the immediate needs of the project and long-term sustainability.
    • Consider incorporating budget items for capacity-building initiatives, infrastructure development, or community engagement activities.
A non-profit worker looks up opportunities for funding on her computer in Salvador, Brazil. May 29, 2017
Marielle Velander, CC-BY-SA 4.0 https://commons.wikimedia.org/wiki/File:A_non-profit_worker_looks_up_opportunities_for_funding_on_her_computer_in_Salvador,_Brazil._May_29,_2017.jpg
definition

License

Icon for the Creative Commons Attribution-ShareAlike 4.0 International License

Community Research Data Toolkit Copyright © 2024 by McMaster University Libraries is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License, except where otherwise noted.

Digital Object Identifier (DOI)

https://doi.org/https://doi.org/10.71548/0jbq-fq80