Welcome to the MUSIT to Specify Migration Knowledge Base

This documentation covers the planning, architecture, and execution of migrating the Norwegian University Museums (MUSIT) collection management system to Specify.

Sections

• Development Setup: Set up the local Python environment.
• Kubernetes Deployment: Deploy the staging stack with Helm.
• Architecture: Data flow and system component overview.
• Infrastructure: Source (MUSIT), staging (Sigma2), and production (AWS) details.
• Database Strategy: Single-db vs multi-db strategy analysis.
• Risk Assessment: Risk analysis for the selected database strategy.
• Database Fields: Auto-generated schema reference and ERD.
• Oracle Schema Overview: Deep analysis and grouping of the legacy source schemas and tables.
• Migration Strategy (Phased): Strategy for merging shared data and iteratively migrating datasets to Specify 7.
• User migration report: migration_report.json from the Migrate Users Prefect flow (Phase 1.4).
• MUSIT collection agents migration: ACTOR / PERSON_NAME → Specify Agent (Phase 1.1; Prefect flow migrate_musit_agents_flow).
• Specify structure sync: sync_specify_structure_flow — create divisions, disciplines, and collections from YAML (post-bootstrap, idempotent).
• Migration reports on S3: Shared bucket folder layout and report.json conventions.
• Migration (ETL Technical): ETL pipeline implementation details from Oracle to MariaDB.
• NIRD Application Text: Text used in the Sigma2/NIRD application.
• Specify + Feide SSO: Feide OIDC integration notes, onboarding model, and rollout guidance.
• Submitted Proposal (PDF): Final submitted NIRD application.
• Data Management Plan (DOCX): Project data management plan.