This is the draft outline for an intensive 3-day Fedora workshop for developers and repository administrators. The workshop days will be broken up into smaller modules that build on each other. Module materials will be developed to serve in both instructor-led and self-paced learning environments.
Common Topics
presentation slides
| Name | Learning Goals | Activity | Prerequisites | Number of Sessions | Presenter | Author |
|---|---|---|---|---|---|---|
| Introducing Fedora Repositories | role of Fedora repository software review some case studies | discussion | none | 1 | David Wilcox | David Wilcox |
| Fedora Front-ends | tour of Islandora, Hydra, and custom front-ends interoperability between front-ends ingest methods | discussion | none | 1 | Unknown User (acoburn) | |
| Content Migration | migrating content from Fedora 3 to 4
| guided steps | VirtualBox workshop Vbox image migration-utils test content | 1 | Michael Durbin | |
| SPARQL-Update | introduction to SPARQL-Update SPARQL cheat-sheet updating resources in Fedora 4 | guided steps | VirtualBox workshop Vbox image | 1 | Andrew Woods | |
| Linked Data Platform | what is linked data and how is it used
linked data formats supported advantages of the LDP standardization
| discussion | none | 2 | ||
| Indexing Fedora | demonstrate admin search and limitations explain message queue (fcrepo-message-consumer) set up Solr indexing set up Fuseki indexing add objects with properties query indexes | guided steps | VirtualBox workshop Vbox image | 1 | Greg Jansen | |
| Authentication and Roles | authN: concepts and components built-in authentication (fedora as back-end) Apache authN (E.G. mod Shibboleth) Tomcat authN (E.G. LDAP Realm) basic roles authorization | presentation slides | none | 0.5 or 1 | Greg Jansen | |
| Extensible Authorization | XACML: request flow and components configuration of XACML authorization module policy language available request attributes and how to add more adding more object (aka resource) attributes arbitrariness of XACML roles ACL model and how to link to policies | presentation slides | 1 | Greg Jansen | ||
| Content Modelling Practice | implication of Fedora/LDP containers:
distinguishing other uses of containment:
linking for reuse (E.G. XACML policies) hands-on practice: Using containment and other relationships between objects and datastreams, coming up with two ways to model your group's example data. Review models (after break) | group work | none | 1 | Greg Jansen |
Dev/Ops Topics
| Name | Learning Goals | Activity | Prerequisites | Number of Sessions | Presenter | Author |
|---|---|---|---|---|---|---|
clustering for high availability metrics achieved in Fedora testing storage options projection over arbitrary storage | presentation | none | 0.5 or 1 | Andrew Woods | ||
| explore key configuration files how to run playbooks:
basic Fedora host variables:
additional Fedora playbooks:
| guided steps | VirtualBox workshop Vbox image | nice to have, but lower priority postponed if we do it. | ||
| Extending Fedora | extension points and how best to use them Apache Camel framework API extension architecture
| presentation slides | none | 0.5 or 1 | ||
why project participation is the best intro building, maven project structure IDE setups for module development Fedora sprints and how to participate | presentation | none | 0.5 or 1 | Andrew Woods |
3 Comments
Greg Jansen
One helpful tool in the process might be some kind of tracing proxy built into the VM kit. It would be great if participants could see all the request/response traffic on the wire.
Greg Jansen
At this point, only the "Indexing Fedora" module is outside of the DEV-OPS track and requires a VM. We might think about whether it is worth explaining/installing VMs to be able to do these tasks individually..
Greg Jansen
An alternative to having a separate day or track for DEV-OPS is to have "over the shoulder" participation for less technical staff. So the devops participants would complete the VM/vagrant steps and the others would "ride along".