Ezsolrsearchextrabundle Laravel Package

Product Decisions This Supports

• Search relevance roadmap: Informs whether to prioritize boosted full-text search (multi-field, publish-date, phrase, exact-match boosting) versus treating search as a commodity capability.
• Document/content indexing scope: Supports decisions about indexing binary file plain-text content into the full-text field, relevant for document-heavy intranets, archives, and knowledge bases.
• Build vs. buy vs. extend: Provides a reference point for extending eZ Platform/Ibexa Solr search instead of building a custom Solr handler or purchasing a separate search product.
• Platform strategy: Clarifies investment in the eZ Platform/Ibexa + Solr stack. This is a Symfony/eZ bundle, not a Laravel-native package, so it is relevant only where that platform is already strategic.
• Feature validation: Useful as a low-cost spike to validate demand for advanced search criteria before committing engineering time to native or commercial alternatives.
• Risk and dependency planning: Low stars, zero dependents, a subtree-split repo, and an unclear license mean this should not become a strategic dependency without legal and maintenance review.

When to Consider This Package

• You are already running eZ Platform/Ibexa with Solr and need search capabilities such as file-content indexing or configurable full-text boosting.
• You need a time-boxed prototype to test whether relevance tuning improves a specific user journey, such as document search, support knowledge bases, or media archives.
• You have in-house PHP/Symfony and Solr expertise and can fork, pin, and maintain the bundle if upstream activity stalls.
• You accept the licensing ambiguity (NOASSERTION) only after legal review, or you plan to treat the code as a reference implementation rather than a production dependency.
• You are not on a greenfield Laravel application, do not need commercial SLAs, and are not relying on an active contributor community.

Look elsewhere if you need a Laravel-native search package, a vendor-supported search product, a permissively licensed dependency with clear obligations, or a solution with meaningful adoption and ecosystem support.

How to Pitch It (Stakeholders)

For executives: This is a small, free open-source extension for eZ Platform/Ibexa Solr search. It could accelerate search relevance experiments and document indexing at low initial cost, but it is not a strategic platform bet: adoption is negligible, licensing is unclear, and maintenance risk is high. Approve only as a bounded spike or internal reference, not as a production-critical dependency without legal and engineering sign-off.

For engineering: Treat it as a focused reference for extending Solr search in eZ/Ibexa, especially full-text boosting and binary file indexing. The repository is a read-only subtree split, issues belong upstream, and the package is not Laravel-native. If pursued, pin a version, review the license, add integration tests, and plan to vendor or fork. Recommended next step: a short proof-of-concept against a real content corpus, with a clear exit criterion and no long-term commitment until search relevance is proven as a product differentiator.