DDF Content Application Users Guide

• DDF Content Framework
  • Content Framework Architecture
  • Content Component Types
    • Storage Providers — proxies to storage mechanisms used to store the content
    • Content Framework — the core of the Content application, routes requests and responses between the Content Components
    • Content Plugins — process Content operations after content storage, generally to parse content's metadata and create a Metacard from it to insert into the catalog provider
    • Content Endpoints — components that accept external requests and interface with the internal components, storing content in the content repository and/or creating catalog entries
    • Content Data Components — domain objects representing the content to be stored
    • Content Operations — represents all transactions that occur in the Content Framework, specifically requests and responses
  • Content Framework Execution Flow: Create Content and Catalog Entry from GeoJson File
• DDF Content Core
  • File System Storage Provider — provides the implementation to create/update/delete content items as files in the DDF Content Repository.
  • Content Cataloger Plugin — provides the implementation to parse content, create a Metacard, and create/update/delete catalog entries in the Metadata Catalog.
  • Standard Content Framework — provides the reference implementation of a Content Framework
  • Directory Monitor — allows ApplicationName to monitor a directory for files to be ingested into the Content Framework
• DDF Content REST CRUD Endpoint — allows clients to perform CRUD operations on DDF Content using REST, a simple architectural style, over HTTP
• DDF Content Application Install/Uninstall

Whitelist

The following packages have been exported by the DDF Content Application and are approved for use by third parties:

• ddf.content
• ddf.content.data
• ddf.content.operation
• ddf.content.plugin
• ddf.content.storage
• ddf.content.util
• ddf.content.core.directorymonitor