1 / 16

Fedora is……..

Fedora: What’s New, What’s Coming Thornton Staples Co-Director of the Fedora Project University of Virginia Library National Library of Wales October 24, 2005. Fedora is……. Fedora is a foundation for many kinds of information management strategies

blade
Download Presentation

Fedora is……..

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Fedora:What’s New, What’s ComingThornton StaplesCo-Director of the Fedora ProjectUniversity of Virginia LibraryNational Library of WalesOctober 24, 2005

  2. Fedora is…….. • Fedora is a foundation for many kinds of information management strategies • Fedora was never intended to be an end-user application • Fedora is a powerful, flexible repository management system • Fedora can be the “plumbing” for formally defined webs of content

  3. IF someone asks you how Fedora compares with DSpace…….. Tell them to look at these clients: • The Elated Client • NSDL’s web submission client • VALET, an institutional repository client from VTLS • FEZ, an institutional repository client developed at the University of Queensland in Australia (see http://www.fedora.info/tools for more info about all four of these)

  4. “Fedora Inside” Known Use Cases • Digital Library Collections • Institutional Repository • Educational Software • Information Network Overlay • Digital Archives and Records Management • Digital Asset Management • File Cabinet / Document Management • Scholarly publishing

  5. Fedora 2.1 Features • Authentication plug-ins for Tomcat • Plug-in #1 : Tomcat user/password file or database • Plug-in #2 : LDAP tie-in • Plug-in #3 : Radius Authentication • Support for SSL • Authorization module • XML-based policies using XACML • Repository-wide policies • Object-specific policies • Fine-grained policy enforcement

  6. XACML Policies • API-M policies that can control all of the management functions at all levels • API-A policies that control repository access • Repository-wide object policies • Object-specific policies about an object as a whole or any of its components • We distribute a complete set of example policies • XACML builder tool coming soon

  7. New in Fedora 2.1 for theResource Index • Resource Index corruption problems diagnosed and fixed (Kowari memory bug) • Scale and Performance Testing (NSDL 2M objects, >100M triples) • Sesame support for an alternative open-source RDF database

  8. Fedora Service Framework

  9. Fedora 2.1 Features (cont.) • PROAI Server (Advanced OAI Provider) • Harvest multiple metadata formats • Harvest datastreams and disseminations • Incremental harvest by last modified date • Support for OAI sets • Directory Ingest Service • Facilitate ingest of hierarchical directories of files • Submit files as .zip or .jar (with a METS manifest) • Automatically asserts parent-child relationships in RELS-EXT • Stages content and ingests as FOXML objects into repository • Directory Ingest Client • Web client (signed applet) • Browse directory trees, select dir/files, add metadata, add relations • Packages as zip/jar and ingests into Fedora repository

  10. Fedora 2.1 Features (cont.) • Rebuild Utility for Repository Indices • Improved logging using log4j • Trippi.log • Kowari.log • Repository log • Handle System Plug-in for PID Generation • New Command-line utilities • fedora-reload-policies • validate-policy • fedora-rebuild • FedoraClient utility class for building new clients

  11. Fedora Development Priorities2006-2007 • New Fedora Framework Services • Federated Repositories • Federations with name service • Federation with other repositories (DSpace, aDORE, arXiv) • “Content Model” Specification Language • Advanced Object Creation Workbenches • Tools for RDF browse and graph traversal • Scalability/Performance – very large repositories • Web services security and Shibboleth • Code Refactoring • Fedora as web app (.war)

  12. Fedora Service Framework (2005-07)

  13. Fedora Community Building • Fedora Advisory Board • Vision • Commission Working Groups • Prioritize Development • Define Sustainability Model • Collaborative Development Opportunities • Share Tools via www.fedora.info • User-contributed Tools, Apps, Services

  14. Fedora Community Working Groups • Preservation Working Group (Ron Jantz, Rutgers) • Requirements for preservation services • Define service APIs and technical integration with Fedora 2.1 + • Preservation metadata recommendations for Fedora • Development plan for new services • Workflow Working Group (Peter Murray, OhioLink) • Requirements for a workflow service • Define service APIs and technical integration with Fedora 2.1 + • Create a reference Implementation with an open-source workflow engine.

  15. Fedora Community Working Groups (cont.) • Outreach Working Group (Linda Langschied, Rutgers) • Improve content of Fedora web site • More user-oriented information (currently technical focus) • Community Showcase – demos, graphics • Survey database with simple web form to profile users • Collaboration Environment • Wiki, Confluence, other? • Content Model Working Group (under charter) • Formalization of notion of Fedora content model • XML schema to define content models • Investigate ontology-based content model definition • Round up existing content models and publish to promote reuse

  16. Fedora Web Sitewww.fedora.info

More Related