Work Package #45540

[EPIC] Search

Added by Aske Ertmann over 2 years ago. Updated over 1 year ago.

Status:New Start date:2013-02-16
Priority:Should have Due date:
Assigned To:- % Done:

0%

Category:- Spent time: -
Target version:1.1

Description

Search

  • Target Audience: users want to search for nodes/domain models in the content & management view
  • Responsible: XY
  • Implemented by: XY, YZ
  • Amount: XY work days
  • Version: not planned yet
  • Planned Implementation Timeframe: X - Y

Motivation

[TODO write goal from a user's perspective. Try to answer the question: "Why is this work package important for the target group?"]

Goal

[TODO what do you want to archieve? Try to answer the question: "What do you want to archieve?"]

Deliverables

[TODO: write bullet points for measurable deliverables; flag them as must have and can have]

  • Should probably support Lucene search database like Solr & Elastic Search with a kind of indexing and search api layer, and then we should provide a fallback package that can use Mysql/PostgreSQL to index and search using the same API.

History

#1 Updated by Aske Ertmann over 2 years ago

  • Subject changed from Search to [EPIC] Search

#2 Updated by Sebastian Kurfuerst over 2 years ago

  • Adrian Föder has already worked on that (TYPO3.ElasticSearch for Domain Models)
  • Michael Klapper has started working on TYPO3.Solr; for TYPO3CR Nodes
  • Helmut Hummel is also interested in that

would be great if you could all figure out how to find synergies...

#3 Updated by Aske Ertmann over 2 years ago

  • Target version set to 1.1

#4 Updated by Sebastian Kurfuerst over 1 year ago

FYI:

Also available in: Atom PDF