Engagement & Onboarding Plan
This plan outlines how we will support curators, contributors, and downstream partners as the archive grows.
1. Vision & Principles
- Single source of truth: Fedora remains the authoritative store for master files and metadata.
- Open standards first: Prefer IIIF, Dublin Core, and JSON-LD for interoperability.
- Automation with guardrails: Automate ingestion and publishing, but keep human review for preservation-critical tasks.
- Progressive hardening: Start with trusted users, add Cloudflare Zero Trust or Azure AD enforcement before wider rollout.
2. Stakeholder Personas
| Persona | Needs | Access Mode |
|---|---|---|
| Curators | Upload media, enrich metadata, manage releases | Authenticated Fedora UI + bulk ingest scripts |
| Editors | Review exhibitions, schedule publications | Cloudflare Pages admin tooling |
| Partner Libraries | Consume metadata/binaries programmatically | Syndication API, scheduled exports |
| Public Audience | Browse and discover narrative experiences | Cloudflare Pages frontend |
3. Iteration Roadmap
- MVP Archive (Current Sprint)
- Secure tunnel, Worker auth, Pages frontend, admin credentials documented.
- Generate technical documentation under
/docsroute.
- Ingestion Tooling
- Build manifest-driven uploader (CSV/JSON) with audit logs.
- Define metadata profile and validation rules (SHACL or JSON Schema).
- Syndication API
- Extend Worker with
/api/v1JSON endpoints backed by Fedora + search index. - Add caching, pagination, and signed delivery URLs.
- Extend Worker with
- Zero Trust Rollout
- Integrate email OTP or Azure AD SSO via Cloudflare Access for Fedora UI & docs.
- Map Fedora service accounts to Worker secrets for system-to-system calls.
- Partner Distribution
- Offer IIIF manifests, OAI-PMH feed, and nightly export packages.
- Document onboarding steps for library partners.
- Operational Excellence
- Automate backups, add Grafana dashboards for ingest latency & worker errors.
- Schedule quarterly credential rotation and security reviews.
4. Governance & Communications
- Change log: Maintain release notes in the
/docsarea for every deployment. - Support workflows: Triage requests in sprint planning; prioritize user-facing issues.
- Training: Host recorded walkthroughs covering ingestion, metadata QA, and publishing.
- Policy alignment: Ensure licensing, rights statements, and privacy terms are captured in metadata.
5. Next Steps
- Approve metadata schema draft and ingestion tooling requirements.
- Stand up Zero Trust pilot for internal stakeholders.
- Begin building
/api/v1endpoints in the Worker with documented contracts. - Onboard first partner library with sample dataset and feedback loop.