Learner Profiles

The intended audience is library data-services staff, OSPO and DataSquad students, and incoming service operators. These profiles are teaching assumptions to check in a pilot, not observations about named colleagues.

Student contributor

---

Assume basic terminal navigation, text editing, and Git familiarity, but no AWS account or administrator background. The learner wants to publish collection content and understand a failure without guessing. Success is a local published page, an explicit verification check, and a reproducible repair. Provide extra setup support for containers and YAML indentation.

Staff member or incoming operator

---

Assume familiarity with a service’s users and operational consequences, with uneven experience in automation. The learner needs to distinguish desired state, reported changes, application correctness, and recoverable data. The public core builds those habits; the Dataverse extension supplies operational reasoning. Production competence requires separate authorized practice and a current runbook.

Certification learner

---

Assume this learner also has, or is developing, Linux administration experience. They need to write automation from requirements without a finished role or AI solution. The optional certification page distinguishes executed drills from mapped objectives and planned VM practice. Containers do not establish SSH, real-host SELinux/firewall behavior, or persistence after reboot.