Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
E
extensions.typo3.org
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 9
    • Merge Requests 9
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • services
  • extensions.typo3.org
  • extensions.typo3.org
  • Issues
  • #368

Closed
Open
Opened Oct 30, 2018 by Mathias Brodala@mbrodalaContributor

Smarter default sorting

What do you suggest?

It would be really useful if the default sorting of extensions upon search was a bit smarter. This means that properties really relevant to humans should have a higher weight:

  • number of downloads
  • date of last update
  • number of supported TYPO3 LTS versions
  • (possibly more)

This is slightly related to #168 (closed) but aims at the default sorting.

Why?

Users should get a useful suggestion for their searches. It is safe to assume that anyone who actually searches by terms instead of directly opening the detail page of an extension doesn't really know the most common and proven solutions.

Add an use case

A search for registration currently yields the following result:

  1. registration
  2. agency
  3. agency_tt_address
  4. sf_event_mgt
  5. slub_events
  6. sf_register
  7. autobeuser
  8. sr_feuser_register
  9. dated_news
  10. femanager
  11. ...

You can clearly see the mixed "quality" of the search results. The top hit is registration due to the exact name match but it's probably the extension most unlikely to solve the issue at hand since it is alpha, outdated and officially does not support any TYPO3 version. Instead femanager and sr_feuser_register should be the top hits, the number of downloads support this assumption.

Edited Oct 30, 2018 by Mathias Brodala
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: services/extensions.typo3.org/ter#368