Academic Research Repository Migration Notice

Role: Principal Research Data Architect with 15 years of experience in scientific data warehousing and open-science repository engineering.

Context

• Research institution: {{institution_name}}
• Source database system: {{source_database_engine}}
• Destination repository: {{target_repository}}
• Scheduled migration window: {{migration_window}}
• Impacted academic departments: {{affected_research_labs}}
• Data governance mandate: {{retention_compliance_standard}}

Task

Draft a comprehensive stakeholder advisory email to department chairs and laboratory directors explaining the transition to the new database repository, detailing mitigation steps for read/write freezes, and providing instructions for pipeline validation.

Method

1. Review the operational impact of moving from {{source_database_engine}} to {{target_repository}} on ongoing experimental data capture.
2. Summarize the technical rationale behind the migration, highlighting performance and adherence to {{retention_compliance_standard}}.
3. Outline the precise schedule for {{migration_window}}, clearly delineating read-only and full-blackout periods.
4. Detail mandatory pre-migration actions required from {{affected_research_labs}}, including active pipeline pauses and checkpoint commits.
5. Explain the automated schema adaptation and data verification checks being executed during cutover.
6. Provide step-by-step post-migration connectivity instructions, including connection string updates and credentials provisioning.
7. Detail rollback contingencies and support escalation channels for lab technicians encountering data integrity anomalies.

Constraints

• MUST structure the email with scannable headers, bolded deadlines, and bulleted action items.
• MUST include explicit fallback support links and contact protocols for urgent queries.
• MUST NOT use overly dense database jargon where plain operational language communicates impact more effectively.
• Keep technical instructions strictly relevant to client-side database connections and ingestion scripts.

Output format

• Subject line (format: [ACTION REQUIRED] Database Migration: {{source_database_engine}} to {{target_repository}})
• Executive Summary (max 80 words)
• Timeline & Impact Breakdown (bulleted schedule)
• Required Lab Actions (numbered list by priority)
• Post-Migration Verification & Support (contact table format)
• Total length: 350-500 words

Self-review

• Confirm all 6 context variables are contextually woven into the email body.
• Verify that maintenance window blackout risks are prominently highlighted.
• Check that post-migration validation instructions are clear for non-DBA lab staff.