Streamlining Research Workflows: Faculty Information Support for Data Management

Recent Trends

Over the past several years, universities and research institutions have steadily increased investment in centralized data management support. The growing complexity of grant requirements, the push for open science, and the rise of data-intensive disciplines have all accelerated demand for faculty-facing services. Common recent trends include:

• Expansion of research data management (RDM) units within libraries or IT departments
• Integration of data management planning tools with proposal submission systems
• Adoption of institutional repository platforms that accept datasets alongside publications
• Development of tiered support models: self-service guidance, one-on-one consultations, and dedicated data stewards for large projects

Faculty information support now often aims to embed data management into researchers' existing workflows rather than treating it as a separate administrative task.

Background

Data management has moved from an optional good practice to a formal expectation from funders, publishers, and institutional policies. Faculty members—especially those in STEM, social sciences, and health fields—are increasingly required to submit data management plans, store and share data according to FAIR principles (Findable, Accessible, Interoperable, Reusable), and retain data for specified periods. Traditional support, such as generic workshops or static website guidelines, has proven insufficient for diverse disciplinary needs.

Many institutions now recognize that effective faculty information support must bridge the gap between generic policy requirements and the specific tools, formats, and storage preferences of different research communities.

Background efforts typically include collaboration between libraries, IT services, research offices, and sometimes specialized data science units.

User Concerns

Faculty members express several recurring concerns when interacting with institutional data management support systems:

• Time overhead: Even with support, preparing a data management plan or depositing data can feel like an unfunded burden on research time.
• Discipline mismatch: Generic templates or storage solutions may not fit lab workflows, field data collection practices, or humanities source management.
• Conflicting guidance: Different funders and journals impose varying standards; faculty want consistent, institution-level advice that adapts per requirement.
• Privacy and IP ambiguity: Concerns about who can access sensitive or commercially valuable data, and how long it must be kept.
• Unclear ownership: When multiple support units are involved, faculty may not know whom to contact for a specific issue.

These concerns highlight the need for streamlined, personalized, and ongoing support rather than one-time training.

Likely Impact

If faculty information support for data management continues to mature, several outcomes are plausible:

• Higher compliance rates with funder data policies, reducing the risk of grant rejection or non-compliance penalties.
• Greater reusability of institutional research outputs, potentially boosting citation and collaboration.
• Reduced administrative friction for faculty, as integrated tools automate aspects of metadata generation, storage selection, and access control.
• More equitable support across departments, if institutions adopt scalable models that offer both basic self-service and expert consultations.

However, the impact depends on whether support actually adapts to faculty workflows rather than imposing one-size-fits-all procedures. Early adopters report that consultation hours drop and data deposit rates rise when support is embedded in the research lifecycle—before data collection, during analysis, and at publication time.

What to Watch Next

Observers and practitioners should monitor several developments that will shape the future of faculty information support:

• Machine-assisted planning: Tools that automatically suggest data management plan text based on the research proposal, lab environment, or previous submissions.
• Cross-institutional collaboration: Shared support networks, especially for consortia or multi-site projects, to avoid duplicating effort.
• Integration with researcher profiles: Systems that connect data outputs with ORCID, Scopus, or institutional CV platforms, reducing manual data entry.
• Evolving funding mandates: As funders update their data policies, support services must quickly adapt and communicate changes.
• Measurement of support effectiveness: Institutions are beginning to track metrics such as time saved, faculty satisfaction, and data reuse rates to justify continued investment.

The next phase will likely involve deeper automation and personalization while maintaining human expertise for complex cases. Faculty information support is shifting from a compliance service to a strategic partner in research acceleration.