1. Fedora Service Framework Sandy Payette, Executive Director UK Fedora Training London January 22-23, 2009

2. Your Applications Supporting Services Repository Service (APIs) ManageAccessSearch RDF (Query) Access ServiceBind Manage Policy Ingest Validate Registry RDF Index Store Fedora Services Institutional Repo Web 2.0 Digital Library Archivist Workbench Asset Management e-Research OAI Etc. Search Ingest Service Framework (Notional View)

3. Core Repository Service

4. Persistence Logic Trust Interface How is the repository exposed?

5. Persistence Logic Trust Interface How can it ensure appropriate access?

6. Persistence Logic Trust Interface How is data manipulated to fulfill requests?

7. Persistence Logic Trust Interface How is the data stored?

8. Persistence Registries and Indexes Files Authentication Logic Trust Interface Consumer s Producers Functional View Manage API-M Access API-A Search (API-A) RDF Query Access ServiceBind Manage Policy Ingest Validate Registry RDF Index Store

9. Persistence Sun XACML Engine HTTP Basic AuthN Fedora "Module" Interface Logic Trust Interface Technical View HTTP / HTTPS Transport Message Format HTTP / SOAP / XML Storage Interface (via LLStore/Akubra plug- ins) JDBCTrippi Authentication Authorization FOXML and Binary Files Registries and Indexes RDBMS -File system -SRB/iRODS -Sun Open Storage -Amazon S3 -More coming… -Mulgara -MPTStore -MySQL -Postgres -Oracle -more

10. Repository Service APIs API-A - Fedora Access (SOAP) API-M - Fedora Management (SOAP) API-A-LITE - Fedora Access and Registry Search (REST) API-M-LITE – Selected Management Operations (REST) RISearch – Resource Index for RDF Query (REST) Fedora REST API – streamlined (new with Fedora 3.0)

11. Fedora Repository Service GSearch OAI Ingest Point-to-Point Service Integrations More… repository publishes events Services have configuration files to connect them with repository service

12. Fedora Service Framework Current Services OAI Provider Service –Based on PROAI –Multiple metadata formats; oai sets –Configure to harvest Fedora dissemination types Directory Ingest Service –Submit a directory of files with a METS manifest –Hierarchy preserved as object-to-object relationship

13. OAI Provider with Polling Update

14. Directory Ingest (DirIngest)

15. Fedora Search Service (GSearch) GSearch: Fedora Generic Search Service –Configure to index any datastreams –Configure to index any service-based dissemination –Plug in Lucene, Solr, or Zebra Developed by Gert Schmeltz Pedersen of DTU

16. GSearch Design

17. Fedora Repository Service GSearch OAI Ingest Simple JMS Simple JMS Messaging - Enables Service Integration More… First, we are providing simple messaging (via JMS using ActiveMQ) repository publishes events services listen and consume events or other messages Messaging introduced in Fedora 3.0…. GSearch is first service to become JMS enabled

18. Publish and subscribe –Core repository service can publish API-M events –Services can subscribe and listen to events –Services can publish their own events Provides a “glue” for the service framework –Services can listen for repository events to update themselves –Services can listen for events to do a job (e.g., format migration) Gsearch is enabled as listening/consumer in Fedora 3.0 We will adapt these services next: –OAI Provider – listen for API-M events to refresh cache –Fedora Journaling – listen for API-M events and replay Fedora Messaging Service

19. Future Services Preservation Validation and Integrity Service –Datastreams – validate the bytestream format –Digital Objects – validate based on content models Preservation Monitoring and Alerting Service –Listen to message broker for special events Checksum failure API-M modification events –Initiate actions Email preservation manager Kick off an automated process (e.g., migrate) Basic Workflow –Standards-based (e.g., BPEL) –Configurable –Univ of Hull’s RepoMan work as a model for the way forward

20. Fedora Services http://fedora- commons.org/documentation/3.0/use rdocs/index.html#services http://fedora- commons.org/documentation/3.0/use rdocs/index.html#services