150 likes | 267 Views
RepoMMan and the University of Hull Institutional Repository Richard Green. RepoMMan project. Repository, Metadata and Management project JISC-funded for two years to end May 2007... ...to develop a BPEL-based, standards-compliant, web-services based, workflow tool for Fedora
E N D
RepoMMan and the University of Hull Institutional RepositoryRichard Green
RepoMMan project • Repository, Metadata and Management project • JISC-funded for two years to end May 2007... • ...to develop a BPEL-based, standards-compliant, web-services based, workflow tool for Fedora • Closely aligned with the University’s commitment to deploy an institutional repository
RepoMMan • Two strands: • research – user needs, documentation etc (BPEL, surveys, Beginner’s guide etc) • technical – development • Surface tool in University portal and/or Sakai C&LE
Hull’s vision for a DR • Hull’s vision for an Institutional Repository is an extremely broad one • Conventional view was exposure of completed objects • Hull’s view encompasses storage, access, management and preservation of a wide range of file types from concept to completion
Services • Survey revealed very wide range of file types potentially to deal with • Storage (backup) • Access (from anywhere) • Management (sharing, locking, versioning etc) • Preservation
Workflow • The repository will be a working environment as well as a showcase • Aim is to provide storage, access, management and potential preservation painlessly • Development based on user interviews and surveys (researchers thus far, soon Teaching and Learning, admin, etc) • Currently working on automation of repository processes (file handling, later auto-metadata) • Standards-compliant approach using web services
BPEL v JBPM • Fedora have workflow group in operation – JBPM approach • Hull’s BPEL/web services approach is complementary (all API-M and API-A functions are available through WSDLs) • Eventual alternate approaches for the Fedora Community
3-tier stack Soap requests and responses http requests and responses • Web services (inc Fedora) orchestrated by BPEL • Spring MVC layer • JSP presentation layer
Fedora web services • Three tier model means BPEL must communicate with Fedora WSDLs • Fedora 2.1(.1) WSDLs based on rpc/encoded messaging style: BPEL can’t reliably validate this via XML schema (nor can several other things!) • New WSDLs written for Fedora based on document/literal style: these validate OK • (Release in 2.2 ?) • Great example of Fedora community development (Fedora – Hull – Rightscom)
Managing user content • Try to need only a shallow user learning curve • Surface repository in known user environments (Portal, Sakai) • Expose it as a network drive? • Use Fedora collections as pseudo-directories
Get an existing object (versioning) • User gets current version by default but can see (and manipulate) older versions
Metadata generation • Take contextual metadata from environment (LDAP, Portal, Sakai) • Generate additional metadata from content (text, JHOVE etc) • Allow user to edit / tweak Acknowledgements to the Arrow consortiumfor the design idea
Coming next • Late summer: we hope to have a demonstrator of some of the workflow processes for researchers – working through the University Portal and the Sakai C&LE • Autumn: turn our attention to administrative and T&L needs. Exam paper repository.
Project website and contact • http://www.hull.ac.uk/esig/repomman • r.green@hull.ac.uk