Old Release

This documentation covers an old version of Fedora. Looking for another version? See all documentation.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Core Features

Content by label

There is no content with the specified labels

Optional Features

  • Page:
    Backup and Restore — The Fedora 4 Backup capability allows a user, such as the repository manager, make a REST call to have the repository binaries and metadata exported to the local file system. Inversely, the Restore capability allows a user to make a REST call to have the repository restored from the contents of a previous Backup operation. In addition, with the default configuration, files are stored on disk named according to their SHA1 digest, so a filesystem backup approach can also be used.
  • Page:
    Backup and Restore — The Fedora Backup capability allows a user, such as the repository manager, to make a REST call to have the repository binaries and metadata exported to the local file system. The Restore capability allows a user to make a REST call to have the repository restored from the contents of a previous Backup operation. In addition, with the default configuration, files are stored on disk named according to their SHA1 digest, so a filesystem backup approach can also be used.
  • Page:
    Backup and Restore — The Fedora 4 Backup capability allows a user, such as the repository manager, make a REST call to have the repository binaries and metadata exported to the local file system. Inversely, the Restore capability allows a user to make a REST call to have the repository restored from the contents of a previous Backup operation. In addition, with the default configuration, files are stored on disk named according to their SHA1 digest, so a filesystem backup approach can also be used.
  • Page:
    Backup and Restore — The Fedora Backup capability allows a user, such as the repository manager, to make a REST call to have the repository binaries and metadata exported to the local file system. The Restore capability allows a user to make a REST call to have the repository restored from the contents of a previous Backup operation. In addition, with the default configuration, files are stored on disk named according to their SHA1 digest, so a filesystem backup approach can also be used.
  • Page:
    Backup and Restore — The Fedora Backup capability allows a user, such as the repository manager, to make a REST call to have the repository binaries and metadata exported to the local file system. The Restore capability allows a user to make a REST call to have the repository restored from the contents of a previous Backup operation. In addition, with the default configuration, files are stored on disk named according to their SHA1 digest, so a filesystem backup approach can also be used.
  • Page:
    External Search —

    To support the differing needs for sophisticated, rich searching, Fedora 4 comes with a standard mechanism and integration point for indexing content in an external service.  This could be a general search service such as Apache Solr or a standalone triplestore such as Fuseki or Blazegraph
  • Page:
    External Search — To support the differing needs for sophisticated, rich searching, Fedora comes with a standard mechanism and integration point for indexing content in an external service.  This could be a general search service such as Apache Solr or a standalone triplestore such as Fuseki or Blazegraph
  • Page:
    External Search — To support the differing needs for sophisticated, rich searching, Fedora comes with a standard mechanism and integration point for indexing content in an external service.  This could be a general search service such as Apache Solr or a standalone triplestore such as Fuseki or Blazegraph
  • Page:
    External Search —

    To support the differing needs for sophisticated, rich searching, Fedora 4 comes with a standard mechanism and integration point for indexing content in an external service.  This could be a general search service such as Apache Solr or a standalone triplestore such as Fuseki or Blazegraph

Supplementary Information

  • Page:
    External Content — When referencing content hosted outside of the repository, you can create an empty binary to act as a placeholder for the external content, specifying the URL of the external content.
  • Page:
    External Content — When referencing content hosted outside of the repository, you can create an empty binary to act as a placeholder for the external content, specifying the URL of the external content.
  • Page:
    External Content — When referencing content hosted outside of the repository, you can create an empty binary to act as a placeholder for the external content, specifying the URL of the external content.
  • Page:
    External Content — When referencing content hosted outside of the repository, you can create an empty binary to act as a placeholder for the external content, specifying the URL of the external content.
  • Page:
    External Content — When referencing content hosted outside of the repository, you can create an empty binary to act as a placeholder for the external content, specifying the URL of the external content.
  • Page:
    External Content — When referencing content hosted outside of the repository, you can create an empty binary to act as a placeholder for the external content, specifying the URL of the external content.
  • Page:
    External Content — When referencing content hosted outside of the repository, you can create an empty binary to act as a placeholder for the external content, specifying the URL of the external content.
  • Page:
    External Content — When referencing content hosted outside of the repository, you can create an empty binary to act as a placeholder for the external content, specifying the URL of the external content.
  • Page:
    Identifiers — Identifiers can be specified in REST API calls and generated either automatically using the internal PID minter or via an external REST service.
  • Page:
    Identifiers — Identifiers can be specified in REST API calls and generated either automatically using the internal PID minter or via an external REST service.
  • Page:
    Identifiers — Identifiers can be specified in REST API calls and generated either automatically using the internal PID minter or via an external REST service.
  • Page:
    Identifiers — Identifiers can be specified in REST API calls and generated either automatically using the internal PID minter or via an external REST service.
  • Page:
    Identifiers — Identifiers can be specified in REST API calls and generated either automatically using the internal PID minter or via an external REST service.
  • Page:
    Linked Data Platform — The W3C Linked Data Platform (LDP) specification details a simple approach for a read-write Linked Data architecture; lays out a set of best practices for Linked Data architecture; and defines a basic interaction model based on HTTP access to web resources that describe their state using the RDF data model. Fedora implements the LDP specification for create, read, update and delete (CRUD) operations, allowing HTTP, REST, and linked data clients to make requests to the repository.
  • Page:
    Linked Data Platform — The W3C Linked Data Platform (LDP) specification details a simple approach for a read-write Linked Data architecture, lays out a set of best practices for Linked Data architecture, and defines a basic interaction model based on HTTP access to web resources that describe their state using the RDF data model. Fedora implements the LDP specification for create, read, update and delete (CRUD) operations, allowing HTTP, REST, and linked data clients to make requests to the repository.

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.