Development Roadmap

This roadmap organizes upcoming work for the Michael J Wright archive into delivery buckets. Each bucket lists the core milestones and highlights the current focus. Update the status notes at the end of every sprint and regenerate the documentation site (npm run build:docs).

1. Repository Structure & Preservation

• Finalize Fedora container hierarchy (collections, projects, exhibitions, writings).
• Document naming conventions for binaries, derivatives, and metadata payloads.
• Define RDF models for descriptive, technical, and rights metadata.
• Introduce SHACL/JSON Schema validation and add runbook to /docs.
• Status: Draft hierarchy in place; metadata schema refinement scheduled for next sprint.

2. Ingestion & Curation Workflow

• Build manifest-driven ingestion tool (CSV/JSON upload + binary drop).
• Automate derivative generation (WebP, thumbnails, PDF, audiovisual cues).
• Capture provenance and audit events for each ingest.
• Publish curator onboarding guide with step-by-step instructions.
• Status: Requirements gathered; tooling design in review.

3. API & Public Site Integration

• Expose /api/v1/collections, /items, /search via Cloudflare Worker.
• Add pagination, filtering, and cache headers to Worker responses.
• Provide IIIF Presentation manifests for high-value items.
• Connect michaeljwright.com.au to Worker endpoints for content pulls.
• Status: Worker proxy live; API schemas being drafted.

4. Discovery & Syndication

• Mirror metadata into search index (OpenSearch/Algolia).
• Build partner export formats (JSON, CSV, METS) with scheduling.
• Evaluate OAI-PMH or other interoperability protocol requirements.
• Coordinate with partner institutions for pilot ingestion.
• Status: Partner outreach initiated; export format mapping underway.

5. Operations & Governance

• Configure Prometheus + Grafana dashboards and alert thresholds.
• Implement Cloudflare Zero Trust for curator/admin access.
• Automate nightly backups for Fedora binaries and PostgreSQL dumps.
• Establish quarterly secret rotation and incident response runbooks.
• Status: Baseline monitoring configured; Zero Trust rollout planned.

6. Documentation & Community

• Expand /docs with metadata standards, troubleshooting, and FAQ.
• Add contributor guidelines, coding standards, and issue templates.
• Record short walkthrough videos for curators and developers (placeholder until assets produced).
• Schedule quarterly roadmap reviews with stakeholders.
• Status: Engagement plan published; next updates focus on metadata documentation.

How to Update This Roadmap

1. Edit this file to reflect progress or add new milestones.
2. Run npm run build:docs to regenerate HTML outputs.
3. Deploy the updated documentation with npm run pages:deploy.
4. Note major shifts in the engagement plan so stakeholders stay aligned.