lutece-elasticdata

Name: lutece-elasticdata
Availability: InStock
Author: vanhemsj

Create standardized Elasticsearch DataSource modules for Lutece 8 plugins.

Updated Aug 23, 2026

Search Tags:#plugin #elasticsearch #datasource #data-indexing #lutece #elasticdata #cdi

Ready to run

npx skills add https://github.com/vanhemsj/lutecepowers --skill lutece-elasticdata

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lutece-elasticdata
Source: https://github.com/vanhemsj/lutecepowers/tree/main/skills/lutece-elasticdata
Command: npx skills add https://github.com/vanhemsj/lutecepowers --skill lutece-elasticdata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a standardized blueprint for implementing Elasticsearch DataSource modules for Lutece 8 plugins, enabling consistent indexing patterns across projects.

Core Features & Use Cases

CDI-based auto-discovery of DataSource implementations within a plugin.
Full and incremental indexing via the plugin-elasticdata framework, with configurable mappings and DataObject definitions.
Reusable patterns for DataSource, DataObject, and event listeners to accelerate plugin development.

Quick Start

Configure a new data source module with proper DataSource and DataObject implementations and wire it into the elasticdata framework to enable automated indexing.

Frequently Asked Questions about lutece-elasticdata

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement Elasticsearch data indexing for a Lutece 8 plugin?▼

You implement Elasticsearch data indexing by creating standardized DataSource and DataObject modules using the plugin-elasticdata framework, enabling CDI auto-discovery and batch synchronization to ensure consistent indexing workflows across modules.

What is CDI auto-discovery for DataSource implementations in Lutece?▼

CDI auto-discovery is a mechanism that automatically detects and registers DataSource implementations within a Lutece 8 plugin, eliminating manual configuration and streamlining the integration of custom data indexing workflows into the elasticdata framework.

Does Lutece 8 support incremental synchronization for Elasticsearch data indexing?▼

Yes, Lutece 8 supports incremental synchronization for Elasticsearch data indexing through the plugin-elasticdata framework, allowing configurable mappings and DataObject definitions to update indexed data efficiently alongside full batch indexing operations.

What's the best way to standardize data indexing workflows across Lutece plugins?▼

The best way to standardize data indexing workflows is to use a reusable blueprint providing DataSource, DataObject, and event listener patterns with built-in daemon orchestration, ensuring consistent Elasticsearch indexing implementations across multiple Lutece projects.

Can I configure custom Elasticsearch mappings using the Lutece elasticdata framework?▼

Yes, you can configure custom Elasticsearch mappings using the Lutece elasticdata framework by defining DataObject structures that specify how your data is mapped and indexed, ensuring search queries match your domain requirements accurately.

Why do I need DataObject and DataSource implementations for Lutece 8 data indexing?▼

DataObject and DataSource implementations are required because they define the structured data extraction and indexing logic that the plugin-elasticdata framework uses to orchestrate batch processing and CDI event handling for Elasticsearch synchronization.