...

• Outreach to Dataverse software adopters. Use the data provided to the TDR liaison in reports to reach out (thank you notes, etc) to researchers to strengthen relationships and to recruit.
• Create targeted, discipline-specific guidance, metadata recommendations and DMPTool templates for researchers
• Documentation and training materials refresh (2021-22) (especially for the adjectival changes to 'dataverse')
• Annual activities:
  • Present on/promote the repository at a minimum 3 conferences (disciplinary and library)
    • add annual info about this to annual report template
  • Webinar series or in-person event 
    
    • continue Webinar series (relatively 2 per term)

Larger datasets 

Datasets >10GB

• Define and document recommended data limits per institution
  • TDR WG creating policy and procedures
• Consider payment system for more space

Assessment

• User facing assessment survey
• Complete Core Trust Seal certification - ongoing
• Google Analytics
• Annual activities:
  • TCDL report on usage
• Carpentries Pilot Report (2021) - by Needs Assessment group of the Carpentries Cohort and Leads

Accessibility

• Policy guidance for audio/visual material
• TDL is working on platform accessibility audits in the coming year, creating and sharing VPATs, and future work

Curation

• DMPTool - has anyone reviewed since they redid it (Research Outputs is sep tab, and you can register the DMP with a researcher ID - ORCID, etc)
• Investigate existing curation tools 
  • Dashboard
  • Analyze the content from Data Curation Network (DCN) 
  • Previewers - learn more and document
  • GeoBlacklight
  • Others in the Dataverse Community

System Integrations

• Ongoing
  • R
• Consider and prioritize
  • ORCiD - https://github.com/IQSS/dataverse/issues/4236
  • OSF (follow the lead of the UVA work)
  • Vireo - await stable release
  • OJS - site growing number of journal datasets in Dataverse - consider engaging OJS group
  • DSpace - await stable release (linking publications with their data)
  • WholeTale or Code Ocean
  • Docker or other software containers

...

deprecated Public TDR Roadmap and Annual Activities

This document is a living document which outlines the TDR service development and enhancement priorities of the TDR Steering Committee and the TDL.

Outreach & Training

• Outreach to Dataverse software adopters. Use the data provided to the TDR liaison in reports to reach out (thank you notes, etc) to researchers to strengthen relationships and to recruit.
• Expand TDR engagement to include more than one staff person at each institution. Establish mechanism for TDR SC to assist each other with outreach projects and do collective outreachoutreach – done
• Create targeted, discipline-specific guidance, metadata recommendations and DMPTool templates for researchers
• Annual activities:
  • Present on/promote the repository at a minimum 3 conferences (disciplinary and library)
    • add annual info about this to annual report template
  • Webinar series or in-person event (Carpentries Project team in 2021)
    
    • continue Webinar series (relatively 2 per term)

Larger datasets 

Datasets >10TB

• Define and document recommended data limits per institution
  • TDR WG creating policy and procedures
• Develop at least one Remote Storage Agent for larger datasets - Done
  • pilot at TACC/UTLibs - Done
  • goal of one complete and one in progress in FY2021 - Done and ongoing at UT
• Consider payment system for more space

Assessment

• Complete Core Trust Seal certification - ongoing
• Review reports against needs assessment report
• Google Analytics
• Annual activities:
  • TCDL report on usage

Accessibility

• Policy guidance for audio/visual material

System Integrations

• Consider and prioritize
  • ORCiD
  • OSF (follow the lead of the UVA work)
  • Vireo - await stable release
  • OJS - site growing number of journal datasets in Dataverse - consider engaging OJS group
  • DSpace - await stable release
  • GeoBlacklight 
  • DMPTool
  • WholeTale or Code Ocean
  • R - Capstone project
  • Docker or other software containers

...

• Dataverse training to develop expertise*#
• Good data sharing practices and issues that may arise, e.g. rights issues, privacy and restricted data, proper citation.*#
• Develop training curriculum
• Workshops#
• Videos*#
• Open forum for discussion and questions TBD e.g. Slack, Google groups.*

Assessment

• Needs assessment - researchers in institutions
• Measure the impact of data reuse
• Audit for optimum repository functionality
• Identify good assessment tools*#
• Identify dataverse use metrics*#
• Data curation and best practices in curation (TXState)

...

• Account request for non-TDL users collaborating with researchers at TDL member institutions possibly with limited permissions to specific Sub-Dataverses*
• Expand third-party authentication capabilities (OAuth2 Google log in)*
• Work with IQSS at Harvard to refine access to specific Institutional and sub-dataverses#

Accessibility

• Accessibility assessment#
• Policy guidance for audio/visual material

...