Table 2.
CC functional areaa | Corresponding CC member roles and responsibilities | Agree n (%) |
---|---|---|
Leadership and administration | Provide infrastructure for between-site collaboration | 54 (98.2) |
Plan scientific meetings | 50 (90.9) | |
Arrange conference calls | 48 (87.3) | |
Coordinate webinars | 48 (87.3) | |
Manage website | 47 (87.0) | |
Manage listserv | 47 (85.5) | |
Serve as a liaison with funders | 41 (74.6) | |
Respond to site needs and problem-solving | 39 (70.9) | |
Data and bioinformatics | Assist with data management | 41 (75.9) |
Assist with data analysis | 27 (49.1) | |
Developmental projects | Coordinate pilot project RFAs | 48 (87.3) |
Lead development of pilot project RFAs | 42 (76.4) | |
Education and training | Offer training on how to integrate disciplinesa | 43 (78.2) |
Provide guidance on integrated disciplinary approachesa | 38 (69.1) | |
Offer skills training | 35 (63.6) | |
Provide scientific expertise in initiative content areas | 33 (60.0) | |
Provide scientific mentorship | 32 (59.3) | |
Offer discipline-specific training | 26 (48.2) | |
Integration and self-evaluation | Provide a broad perspective of initiative activities | 44 (80.0) |
Assist sites with gauging transdisciplinary progressa | 38 (69.1) | |
Suggest midcourse corrections | 38 (69.1) | |
Develop transdisciplinary evaluation metricsa | 36 (65.5) |
Notes: Rows may not sum to 58 due to missing data. Responses do not differ between TREC investigators and NCI program staff based on Fisher’s exact tests.
Functional areas correspond to TREC CC cores.