Fedora Commons

Last updated
Fedora
Developer(s) Open Source
Initial releaseMay 16, 2003;21 years ago (2003-05-16)
Stable release
6.2.0 [1] / 2022-06-03 [±]
Repository
Platform Java
Type Digital asset management
License Apache License 2.0
Website fedora.lyrasis.org

Fedora (or Flexible Extensible Digital Object Repository Architecture) is a digital asset management (DAM) content repository architecture upon which institutional repositories, digital archives, and digital library systems might be built. Fedora is the underlying architecture for a digital repository, and is not a complete management, indexing, discovery, and delivery application. It is a modular architecture built on the principle that interoperability and extensibility are best achieved by the integration of data, interfaces, and mechanisms (i.e., executable programs) as clearly defined modules.

Contents

History

The Fedora Repository open source software is a project supported by the DuraSpace not-for-profit organization. The software has its origins in the Flexible Extensible Digital Object Repository Architecture (i.e., Fedora) which was originally designed and developed by researchers at Cornell University. [2] Fedora is an architecture for storing, managing, and accessing digital content in the form of digital objects inspired by the Kahn and Wilensky Framework. [3] Fedora began as a DARPA and National Science Foundation funded research project at Cornell University's Digital Library Research Group in 1997, where the first reference implementation was written in Java using a CORBA-based distributed object approach. [4] [5] The University of Virginia began experimenting [6] with the Cornell software and later joined with Cornell to establish the Fedora Repository project that re-implemented Fedora as open source software. Since then, several modifications have been made to the architecture, [7] and in late 2005, version 2.1 was released. [8] Fedora defines a set of abstractions for expressing digital objects, asserting relationships among digital objects, and linking "behaviors" (i.e., services) to digital objects.

In 2003 Red Hat, Inc. applied for trademark status for the name "Fedora" to be associated with their Linux operating system project. [9] Cornell and UVA formally disputed the request and, as a final settlement, all parties settled on a co-existence agreement that stated that the Cornell-UVA project could use the name when clearly associated with open source software for digital object repository systems and that Red Hat could use the name when it was clearly associated with open source computer operating systems. [10]

Technology

Fedora provides a general-purpose management layer for digital objects. [11] Object management is based on content models that represent data objects (units of content) or collections of data objects. The objects contain linkages between datastreams (internally managed or external content files), metadata (inline or external), system metadata (including a PID – persistent identifier – which is unique to the repository), and behaviors that are themselves code objects that provide bindings or links to disseminators (software processes that can be used with the datastreams). Content models can be thought of as containers that give a useful shape to information poured into them; if the information fits the container, it can immediately be used in predefined ways.

Fedora supports two types of access services: a management client for ingest, maintenance, and export of objects; or via API hooks for customized web-based access services built on either HTTP or SOAP. A Fedora Repository provides a general-purpose management layer for digital objects, and containers that aggregate mime-typed datastreams (e.g., digital images, XML files, metadata). Out-of-the-box Fedora includes the necessary software tools to ingest, manage, and provide basic delivery of objects with few or no custom disseminators, or can be used as a backend to a more monolithic user interface.

Fedora supports ingest and export of digital objects in a variety of XML formats. This enables interchange of objects between Fedora and other applications, as well as facilitating digital preservation and archiving.

The Fedora Project is currently supported by the DuraSpace organization.

See also

Related Research Articles

<span class="mw-page-title-main">Open Archives Initiative</span> Informal organisation

The Open Archives Initiative (OAI) was an informal organization, in the circle around the colleagues Herbert Van de Sompel, Carl Lagoze, Michael L. Nelson and Simeon Warner, to develop and apply technical interoperability standards for archives to share catalogue information (metadata). The group got together in the late late 1990s and was active for around twenty years. OAI coordinated in particular three specification activities: OAI-PMH, OAI-ORE and ResourceSync. All along the group worked towards building a "low-barrier interoperability framework" for archives containing digital content to allow people harvest metadata. Such sets of metadata are since then harvested to provide "value-added services", often by combining different data sets.

The Advanced Authoring Format (AAF) is a file format for professional cross-platform data interchange, designed for the video post-production and authoring environment. It was created by the Advanced Media Workflow Association (AMWA), and is now being standardized through the Society of Motion Picture and Television Engineers (SMPTE).

The Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) is a protocol developed for harvesting metadata descriptions of records in an archive so that services can be built using metadata from many archives. An implementation of OAI-PMH must support representing metadata in Dublin Core, but may also support additional representations.

In library and archival science, digital preservation is a formal process to ensure that digital information of continuing value remains accessible and usable in the long term. It involves planning, resource allocation, and application of preservation methods and technologies, and combines policies, strategies and actions to ensure access to reformatted and "born-digital" content, regardless of the challenges of media failure and technological change. The goal of digital preservation is the accurate rendering of authenticated content over time.

Enterprise content management (ECM) extends the concept of content management by adding a timeline for each content item and, possibly, enforcing processes for its creation, approval, and distribution. Systems using ECM generally provide a secure repository for managed items, analog or digital. They also include one methods for importing content to manage new items, and several presentation methods to make items available for use. Although ECM content may be protected by digital rights management (DRM), it is not required. ECM is distinguished from general content management by its cognizance of the processes and procedures of the enterprise for which it is created.

<span class="mw-page-title-main">DSpace</span> Repository software package

DSpace is an open source repository software package typically used for creating open access repositories for scholarly and/or published digital content. While DSpace shares some feature overlap with content management systems and document management systems, the DSpace repository software serves a specific need as a digital archives system, focused on the long-term storage, access and preservation of digital content. The optional DSpace registry lists almost three thousand repositories all over the world.

The term Open Archival Information System refers to the ISO OAIS Reference Model for an OAIS. This reference model is defined by recommendation CCSDS 650.0-B-2 of the Consultative Committee for Space Data Systems; this text is identical to = 57284 ISO 14721:2012. The CCSDS's purview is space agencies, but the OAIS model it developed has proved useful to other organizations and institutions with digital archiving needs. OAIS, known as ISO 14721:2003, is widely accepted and utilized by various organizations and disciplines, both national and international, and was designed to ensure preservation. The OAIS standard, published in 2005, is considered the optimum standard to create and maintain a digital repository over a long period of time.

DPubS, developed by Cornell University Library and Penn State University Libraries, is a free open access publication management software. DPubS arose out of Project Euclid, an electronic publishing platform for journals in mathematics and statistics. DPubS is free software released under Educational Community License.

Nuxeo is a software company making an open source content management system.

The Agrega project is a digital repository which is to be used by 19 educational authorities in Spain. Each educational authority will have its own repository of curricular learning objects created according to educational standards, and each single repository will be able to integrate and interoperate with other learning systems locally and worldwide.

<span class="mw-page-title-main">Metadata</span> Data

Metadata is "data that provides information about other data", but not the content of the data itself, such as the text of a message or the image itself. There are many distinct types of metadata, including:

<span class="mw-page-title-main">Digital library</span> Online database of digital objects stored in electronic media formats and accessible via computers

A digital library is an online database of digital objects that can include text, still images, audio, video, digital documents, or other digital media formats or a library accessible through the internet. Objects can consist of digitized content like print or photographs, as well as originally produced digital content like word processor files or social media posts. In addition to storing content, digital libraries provide means for organizing, searching, and retrieving the content contained in the collection. Digital libraries can vary immensely in size and scope, and can be maintained by individuals or organizations. The digital content may be stored locally, or accessed remotely via computer networks. These information retrieval systems are able to exchange information with each other through interoperability and sustainability.

The Handle System is a proprietary registry assigning persistent identifiers, or handles, to information resources, and for resolving "those handles into the information necessary to locate, access, and otherwise make use of the resources". As with handles used elsewhere in computing, Handle System handles are opaque, and encode no information about the underlying resource, being bound only to metadata regarding the resource. Consequently, the handles are not rendered invalid by changes to the metadata.

<span class="mw-page-title-main">TACTIC (web framework)</span> Web-based, open source workflow platform and digital asset management system

TACTIC is a web-based, open source workflow platform and digital asset management system supported by Southpaw Technology in Toronto, ON. Designed to optimize busy production environments with high volumes of content traffic, TACTIC applies business or workflow logic to combined database and file system management. Using elements of digital asset management, production asset management and workflow management, TACTIC tracks the creation and development of digital assets through production pipelines. TACTIC is available under both commercial and open-source licenses, and also as a hosted cloud service through Amazon Web Services Marketplace.

Islandora is a free and open-source software digital repository system based on Drupal and integrating with additional applications, including Fedora Commons. It is open source software. Islandora was originally developed at the University of Prince Edward Island by the Robertson Library and is now maintained by the Islandora Foundation, which has a mission to, "promote collaboration through transparency and consensus building among Islandora community members, and to steward their shared vision for digital curation features through a body of software and knowledge."

Data defined storage is a marketing term for managing, protecting, and realizing the value from data by combining application, information and storage tiers.

Imixs Workflow is an open-source project, providing technologies for building Business Process Management solutions. The project focus on human based workflows used to execute and control workflows in organisations and enterprises. In difference to task-oriented workflow engines, which focus on automated program flow control (tasks), Imixs Workflow is a representative of an event-based workflow engine. Here, the engine controls the status of a process instance within a defined state-diagram. By entering an event, the state of a process instance can be abandoned or changed. In human-centric workflow engines, events usually occur by an interaction of the actor with the system, for example by approving or rejecting a business transaction. They can also be triggered by scheduled events. An example of this is an escalation of an unfinished task.

<span class="mw-page-title-main">Samvera</span>

Samvera, originally known as Hydra, is an open-source digital repository software product. Samvera main components are Fedora Commons, Solr, Blacklight, and HydraHead. Each Samvera implementation is called a "head". "Samvera" is Icelandic for "togetherness".

References

  1. "Release notes - Fedora Repository Project". github.com. 24 June 2022. Retrieved 24 June 2022.
  2. Payette, S., and Lagoze, C., “Flexible and Extensible Digital Object and Repository Architecture (FEDORA)”, European Conference on Research and Advanced Technology for Digital Libraries, Lecture Notes in Computer Science, Springer, 1998
  3. Kahn, R., Wilensky R., A framework for distributed digital object services, International Journal on Digital Libraries. Volume 6 Issue 2, April 2006. Springer-Verlag Berlin, Heidelberg.
  4. Payette, Sandra; Lagoze, Carl (2000). Policy-Carrying, Policy-Enforcing Digital Objects. European Conference on Research and Advanced Technology for Digital Libraries. arXiv: 1312.1260 .
  5. Payette, Sandra; Lagoze, Carl (1998). Flexible and Extensible Digital Object and Repository Architecture (FEDORA). Research and Advanced Technology for Digital Libraries. arXiv: 1312.1258 . doi:10.1007/3-540-49653-X_4 . Retrieved June 25, 2022.
  6. Staples, T., Wayland, R., Virginia Dons FEDORA: A Prototype for a Digital Object Repository. D-Lib Magazine. July/August 2000.
  7. Payette, S. and Staples, T., “The Mellon Fedora Project: Digital Library Architecture Meets XML and Web Services,” Sixth European Conference on Research and Advanced Technology for Digital Libraries, Lecture Notes in Computer Science, Springer, September 2003
  8. Lagoze, C., Payette, S., Shin, E., and Wilper, C., “Fedora: An Architecture for Complex Objects and their Relationships,” International Journal on Digital Libraries, Special Issue on Complex Objects, Springer, 2005
  9. Becker, D., Red Hat, researchers in name tiff. CNET News.com. November 6, 2003.
  10. "Fedora repository project history". Archived from the original on 2014-02-22. Retrieved 2012-08-14.
  11. "Green, R., Awre, C., The REMAP Project: Steps Towards a Repository-enabled Information Environment. Ariadne Magazine. April 30, 2009". Archived from the original on December 6, 2018. Retrieved June 13, 2012.

Further reading