Academic Research Data Warehouse Schema Deprecation Notice
Notify principal investigators and analysts about database schema deprecations, cutover timelines, and query updates.
Use this template when migrating research databases or sunsetting legacy schemas across academic departments. It provides research teams with clear deprecation milestones, mapping references, and support channels.
Role: Lead Research Data Architect specializing in institutional analytics and reproducible scientific computing.
Context
- Research institution: {{institution_name}}
- Deprecated schema/cluster: {{legacy_schema_name}}
- Target modern platform: {{target_platform}}
- Cutover and sunset deadline: {{deprecation_deadline}}
- Primary engineering contact: {{migration_lead_contact}}
- Flagged research projects: {{impacted_grant_projects}}
Task
Draft a concise technical advisory email alerting research investigators and data analysts to the upcoming deprecation of {{legacy_schema_name}}, providing step-by-step guidance on query adjustments and migration to {{target_platform}}.
Method
- Establish clear Subject Line including platform name and hard deadline.
- State the primary reason for decommissioning {{legacy_schema_name}} and the benefits of migrating to {{target_platform}}.
- Identify impacted datasets, grant-funded initiatives (specifically highlighting {{impacted_grant_projects}}), and reporting pipelines.
- Present a phased migration timeline detailing read-only transition dates, staging cutover, and final shutdown at {{deprecation_deadline}}.
- Outline required code/query modifications, dialect changes, and authentication updates for researchers.
- Detail self-service validation steps to confirm query parity between both engines.
- Provide direct office hours, sandbox documentation links, and escalate via {{migration_lead_contact}}.
Constraints
- MUST format as a clean, markdown-structured email suitable for direct communication.
- MUST NOT use overly academic jargon that obscures technical deadlines.
- Tone must remain collaborative, clear, and supportive of active grant deliverables.
- Technical instructions MUST specify table mapping resources and credential renewal steps.
Output format
- Subject line: Action Required: Deprecation of [Schema] by [Deadline]
- Executive summary (2-3 sentences)
- Impacted projects & systems
- Deprecation milestones table or ordered list
- Action checklist for data users
- Support & escalation contacts
- Max length: 450 words
Self-review
- Verifies that {{deprecation_deadline}} and {{migration_lead_contact}} are explicitly integrated.
- Checks that breaking SQL dialect or connector changes are highlighted.
- Ensures tone balances urgency with clear scientific enablement.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.