2023-04-05 - Product Committee

Presenter

Time

Notes

5 min

• The action item for Ayush remains open

• The tech team trainings are progressing

@Sarah Farooqi

5 min

https://exchange.dial.global/

• The digital impact exchange Q1 release

• A new digital public infrastructure filter was added and more detailed information on the products is accessible. A new playbook has been added about picture-based insurance.

• Q: about the definitions of Building Blocks and hierarchy of the displayed BBs.

• The products shown are based on the list of the DPGA, digital health atlas, new america and private submissions. The private submissions are checked before publication on the website. The ownership of a product can be authenticated upon request.

• Sarah will check the linked repositories. The informationen is not directly linked to the repos, right now the informationen is collected from Github and might not be up to date. It is flagged when the information was updated and if by whom. Wes asks that in the future the information could be displayed in more detail.

• Q: Are the use cases on the website real-life use cases or case studies? A: Both should be displayed and updated/ maintained. For now case studies are not published. In the future, after user research, the use case section will be utilized more.

@Sainabou Jallow

15 min

What factors do we use to determine who is listed as a contributor to a Use Case (and more generally)? Are there any established standards for this?

Draft proposal

Option 1

To be listed as a contributor, one of the following criteria must be met:

• Involved in identifying and designing the use case.

• Conducted research, facilitated stakeholder engagement and collected/synthesized data pertaining to the use case topic.

• Participated in drafting or revising the use case; and approved the final version. 

 Guideline:

• List core author(s) of the use case documentation.

• List contributors in alphabetical order - giving details of their role i.e., identified use case, provided relevant documents, authored the use case, external subject matter expert, member of the Product, Technical and/or Country Engagement committee that reviewed and provided input in the use case document. 

Option 2

 Follow existing standard for recognizing all contributions to a research out - the Contributor Roles Taxonomy CRediT.

CRediT (Contributor Roles Taxonomy) is a high-level taxonomy, including 14 roles, that can be used to represent the roles typically played by contributors to research output. ** Many journals and publishers have adopted the CRediT system in their submission process.

The model allows contributors to share a description of their input, using 14 pre-defined contributor roles: 1. conceptualization; 2. data curation; 3. formal analysis; 4. funding acquisition; 5. investigation; 6. methodology; 7. project administration; 8. resources; 9. software; 10. supervision; 11. validation; 12. visualization; 13. writing – original draft; 14. writing – review & editing.

Guideline:

• All contributors should be listed and assigned a role, and multiple roles are possible. This provides a detailed description of diverse contributions to the work.

• If multiple contributors are assigned the same role, the degree of contribution can be quantified, by including ‘lead’, ‘equal’ or ‘supporting’ next to the role.

• All contributors should be able to review and approve the assigned roles.

• It is the responsibility of the Product Owner and lead use case author to assign and confirm the roles.

Example: A.T.K.: conceptualization (lead), data curation (lead), formal analysis (lead), investigation, methodology (lead), project administration (lead), resources (lead), visualization, writing—original draft and writing—review and editing (equal); D.R.: conceptualization (supporting), formal analysis (supporting), methodology (supporting), resources (supporting), supervision (supporting), validation and writing—review and editing (supporting); H.R.: conceptualization (supporting), data curation (supporting), project administration (supporting), validation and writing—review and editing (supporting)

Discussion:

• Rachel: Categorization of different contributions could lead to certain types of contributions coming across as more important than others

• Margus: “Github Conquistador” badge

• Ramkumar: Need to ensure that we recognize the people who have been involved over the last few years

• Sherman: Including organization/government ministries may be helpful and lend credence to the use cases. Would need to get approval from the org/gov to do this.

• Yolanda: Include the names of those that were involved in the digital service design, including government representatives

• Wes: Ordering important and/or levels of contribution?

  • Yolanda: Alphabetical is the UN standard, levels are not important

  • Rachel: Organizations would be helpful to include but we may not have the data to consistently and accurately do this

Next Steps:

• Ramkumar to determine individuals that were working on Use Cases prior to gitbook timeframe and share with Saina

• Yolanda to get the names and approval of people to include from country engagement work

•  

@Wes Brown

15 min

GIZ, Estonia, Dial, ITU