• Home
• About
• Screenshots
• Architecture
• Licence
• Standard Installation
• Installation Walk-through by Example
• Production Install
• Troubleshooting
• Dependencies
• Script Installation
• Development Setup via Script
• Supplejack Components
• Supplejack Website
• Supplejack Client
• Supplejack Common
• Supplejack Worker
• Supplejack Manager
• Supplejack API
• Creating your API
• API Admin
• Schema DSL (Domain Specific Language)
• Creating Schemas
• Using the API
• Authentication
• Metrics API
• Sets API
• Records API
• Concepts API
• Using the manager
• Job Status
• Concepts Configuration
• Link Checker
• Code Snippets
• Introduction to parser scripts
• Parser DSL (Domain Specific Language)
• Validations
• XML Namespaces
• Attribute Transformation Options
• Enrichments
• Modifiers
• Activity Metrics
• Item Metrics
• Usage Metrics

Developed in Ruby on Rails, there are several core components of the Supplejack platform:

• Manager (user interface for controlling activity)
• Worker (for harvesting, enrichment, and link checking activity)
• API (public API wrapper to search index and metadata repository)
• Common (shared helpers for the the Worker and Manager)

Additionally, the Suppejack stack includes:

• Website (demo web application that provides simple search, result, filtering, and view interfaces to collected items)
• Client (client gem used by the demo website to interface with the Supplejack API)

Supplejack relies on integration with both a search index (default is Solr) and a metadata repository (default is MongoDB). The code and documentation provided is tailored for a monolithic install, however in a full production environment DigitalNZ runs a cluster of front-end services delivering the public API, supported by a back-end service dedicated to harvesting.