Bug #37091
Create a specialized Solr Search for the TER
| Status: | Resolved | Start date: | 2012-05-11 | ||
|---|---|---|---|---|---|
| Priority: | Should have | Due date: | 2012-05-25 | ||
| Assignee: | Ingo Renner | % Done: | 80% |
||
| Category: | [FOR] Search | ||||
| Target version: | - | ||||
| Votes: | 0 |
Description
Last Monday Ingo, Joern and I agreed to create a specialized Solr Search for the TER (SolrTER)
This is the facets we will have:
- Status
- Categories
- Downloads
- Last Update
- Author
- has Manual (yes/no)
Optional & nice to have facets
- Extbase Extension
- Dependencies
- Conflicts
A list displaying all TER Extensions will be placed here:
http://typo3.org/extensions/repository/
The list will look exactly like the current list or TERFE2
Search results will be displayed here:
http://typo3.org/extensions/repository/search/
The list will look exactly like the current list or TERFE2 but will have the facets
We have discused that we will offer a way to choose the facets in the list context. I.e. under the Search field and in the Listeelements.
History
Updated by Ingo Renner about 1 year ago
- File solr_ter.png added
- Status changed from New to Accepted
- % Done changed from 0 to 80
Status Update:
The TER search has been implemented using Solr. We currently have filters on state and category.
The testing is currently being prepared with Tolleiv on latest.t3o.
There's one outstanding issue right now:
The current TER FE plugin handles list, search, and single view in one controller on one page. by replacing the list and search view with Solr the TER FE plugin cannot stay on the same page. The current idea is to move the TER FE /extension single view to a separate page. By doing that the URL for the single view would change though. A solution for that could be to exclude that part of the page path from realurl so that the URLs would be the same as before and still having the two plugins separated on different pages.
Alternatively we could switch between Solr and TER FE plugins using conditions on URL parameters.
Preview:
Updated by Thomas Loeffler about 1 year ago
Looks nice, Ingo!
For one issue to link from the own extension listing to the detail view, I added a Typoscript setting for getting the PID with the extension detail view.
We can use that for all links to the detail view if solution 1 is to be used.
I can't wait latest.t3o to be ready for tests. :)
Updated by Ingo Renner about 1 year ago
I know, we use that constant already to generate the links during indexing
Updated by Ingo Renner about 1 year ago
... locally I've added a single view pid
Updated by Thomas Loeffler about 1 year ago
So, in future we have to edit a seperate extension to change the list view?
Updated by Ingo Renner about 1 year ago
nothing to edit, everything should be indexed automatically.
If you mean the rendering/output, yes it's a separate template.
Updated by Helmut Hummel about 1 year ago
If all versions of an extension are marked as insecure, the extension itself also must not appear in the list. Will this be the case?
Another question: The single view will still be rendered by terfe2 right?
Updated by Helmut Hummel about 1 year ago
Helmut Hummel wrote:
Another question: The single view will still be rendered by terfe2 right?
Ah, OK. This seems to be the case ;)
Updated by Ingo Renner about 1 year ago
Helmut Hummel wrote:
If all versions of an extension are marked as insecure, the extension itself also must not appear in the list. Will this be the case?
since we only index the latest/current version of an extension I guess this will be the case
Updated by Ingo Renner 11 months ago
currently implemented facets:
- status
- category
- last update
For the has manual facet we would need such a flag/field in the TER tables.
Updated by Joern Bock 6 months ago
- Target version deleted (
Release 2.0)
Updated by Joern Bock 5 months ago
- Status changed from Accepted to Resolved