CollectiveAccess
1.8

Introduction to CollectiveAccess

  • What is CollectiveAccess?

Setup & Install

  • System Requirements
  • Installation
  • General Instructions
  • Setup.php
  • Backups

Data Modelling in CA

  • Introduction to Data in CA
  • Installation Profiles
  • Primary Tables
  • Metadata Elements
  • Relationships
  • Interstitial Data
  • Lists and Authorities
  • Data Dictionary
  • Locales
  • Labels

Configuration

  • Overview
  • Configuration File Syntax

Search & Browse

  • Overview
  • Search Syntax
  • Search Forms
  • Search Builder
  • Browse
  • Indexing Options
  • Search Engines
    • SQL Search
    • ElasticSearch

Editing

  • Overview
  • User Interfaces
  • User Interface Administration
  • Batch editing

Media

  • Intro to Media
  • Media Mirroring
  • Batch import
  • Background processing

Reporting

  • Displays
  • Display Template Syntax
  • Expressions
  • Template Unit Syntax
  • PDF Output
  • Generating Labels
  • Barcodes

Workflow

  • Tracking location
  • Alerts
  • Sets

Import

  • Import Mapping
  • Import Tutorial
  • Running an Import
  • WorldCat
  • Getty Vocabularies
  • Chenhall Nomenclature
  • Media embedded metadata

Export

  • Mappings
  • OAI-PMH Provider
  • External export

Administration

  • User Access Control
  • Maintenance Functions
  • Command line utilities

Developer

  • Translation
  • Web APIs
  • Internal APIs
  • Plugins

Reference

  • Settings
  • Glossaries
CollectiveAccess
  • Docs »
  • Search Engines »
  • SQL Search

SQL Search¶

SQLSearch is an engine that employs regular MySQL tables to create an inverted index stored. This technique was used in the 0.5x version of CollectiveAccess and provided reasonable performance and scalability combined with easy deployment (zero-configuration is required). For version 0.6 and 1.0 alternative engines were explored that leveraged existing code (eg. PHP Lucene, MySQL FULLTEXT, SOLR, etc.). While ultimately workable, none of the other options combine the deployment and performance characteristics of the inverted index approach. Thus, a new Unicode-friendly “SQL Search” plugin has been implemented, as of version 1.1, as an alternative to PHP Lucene and MySQL Fulltext, the other “easy deploy” options. As of version 1.1, SqlSearch is the default search engine option and as of version 1.3 the only supported “easy deploy” option.

Pros: Performance and scalability are generally good; deployment is effortless

Cons: Indexing can be slow; disk space requirements for indices can be large

Status: Implemented

Next Previous

© Copyright 2022, Whirl-i-Gig Last updated on Apr 20 2022.

Built with Sphinx using a theme provided by Read the Docs.