Page MenuHomePhabricator

Implement Flow search frontend
Closed, DuplicatePublic

Description

I haven’t broken this ticket down yet. Similar to TOC, we can create lots of smaller tasks.
I’m not at all familiar with how TOC works & I guess we’ll reuse some of that too, so I could use some help to break this up into smaller pieces.

Whatever the interface for end-users will look like, we'll probably have to make sure it isn't visible when no Extension:CirrusSearch, Extension:Elastica or Elasticsearch is available? (3rd party wikis using Flow)

Current mockups:
http://pauginer.github.io/prototypes/flow/filters/index.html
https://docs.google.com/presentation/d/1DQabV3mjE9ReV9zs1qAi8u_A5560QEVX4aK95pc0Whs/edit#slide=id.p

There’s a very barebones Special:FlowSearch patch already, at https://gerrit.wikimedia.org/r/#/c/161947/
It hasn’t been updated in awhile (probably trivial rebase) - not sure if we’ll want to keep this around, was more of a POC (although it has the benefit of having an url to link to)

Event Timeline

matthiasmullie claimed this task.
matthiasmullie raised the priority of this task from to Medium.
matthiasmullie updated the task description. (Show Details)
matthiasmullie changed Security from none to None.
matthiasmullie added a subscriber: matthiasmullie.

For the most part, this is not blocked on T78787, since we can (mostly) use default ES config on our development devices.
The only thing I can think of that we'll be blocked on T78787 for, is highlighting.

All that's needed is https://gerrit.wikimedia.org/r/#/c/126996/, which will allow you to index data & call an API to get search results.

See https://www.mediawiki.org/wiki/Flow/Architecture/Search on how to set that up.

Amire80 renamed this task from Implement search frontend to Implement Flow search frontend.Apr 4 2015, 10:14 AM