Core Services vs. Scientific Collaboration

Most projects involve established Core services. Some also include deeper scientific contributions from Core personnel. Clarifying expectations early helps avoid confusion about scope, billing, acknowledgment, and authorship.

Before You Begin:

A quick conversation with the Core can prevent confusion later. 

Discuss at the Start of the Project:

Scope • Charges • Acknowledgment/RRID • Publication and Authorship Expectations
Important: Describing a project a “collaboration” does not remove established Core services from the Core workflow or applicable billing.
 

When You Are Using a Core Service

Established services using Core personnel, equipment, resources, workflows, or technical expertise.

What you should do:

  • Submit the work through the Core’s normal request process 
  • Expect applicable Core charges 
  • Acknowledge the Core and include the RRID, where available

When Core Personnel Also Make a Scientific Contribution

In some projects, Core personnel may contribute beyond routine service, for example, through study design, method development, non-routine analysis, interpretation, or other substantive scientific input.

What you should do:

  • Keep the Core service in the normal Core workflow; applicable charges still apply
  • Clarify the scientific contribution separately
  • Discuss potential authorship early and base it on the actual contribution

When the Collaboration Is Outside the Core

A Core-affiliated faculty member may also collaborate independently as an academic investigator.

This is outside the Core only when:

  • No Core services are being provided 
  • No Core staff, equipment, or resources are being used
  • No Core charges apply