[GH-ISSUE #11216] website model library functionality bug when sorted in "newest" mode #33149

Closed
opened 2026-04-22 15:33:45 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @thejjw on GitHub (Jun 27, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11216

What is the issue?

Hello,
Why does browsing model in "newest" sort1 does not sort in newest order? I think the second item should be the first item in this case..

Image

Thanks.

Relevant log output


OS

No response

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @thejjw on GitHub (Jun 27, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11216 ### What is the issue? Hello, Why does browsing model in "newest" sort[^1] does not sort in newest order? I think the second item should be the first item in this case.. ![Image](https://github.com/user-attachments/assets/987d4632-dbfb-44d4-823d-f70d6a5d6a12) Thanks. [^1]: https://ollama.com/search?o=newest ### Relevant log output ```shell ``` ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the bug label 2026-04-22 15:33:45 -05:00
Author
Owner

@rick-github commented on GitHub (Jun 27, 2025):

"newest" means by date added. So mistral-small3.2 was added after gemma3n, but gemma3n was updated more recently.

<!-- gh-comment-id:3012454665 --> @rick-github commented on GitHub (Jun 27, 2025): "newest" means by date added. So mistral-small3.2 was added after gemma3n, but gemma3n was updated more recently.
Author
Owner

@thejjw commented on GitHub (Jun 27, 2025):

oh...okay...its hard to understand why the displayed metric and the sort metric is different, but i guess its at least the page is sorted accordingly.
thanks.

<!-- gh-comment-id:3012481383 --> @thejjw commented on GitHub (Jun 27, 2025): oh...okay...its hard to understand why the displayed metric and the sort metric is different, but i guess its at least the page is sorted accordingly. thanks.
Author
Owner

@Notbici commented on GitHub (Jun 30, 2025):

Hah a gulf of human evaluation issue.. its technically correct.. but I still think this is a problem which you're going to face with something public and usable by well.. end users..

I'd recommend adding filters:

  • Recently Updated
  • Recently Added

Then just put both dates in the UI results. {date_added}, {last_updated}.
There's a good reason for both, some really nice models get revised. Now if they were added 6 months ago, and you're searching for the latest model its going to be way down the list.

My 0.2c.

<!-- gh-comment-id:3020613776 --> @Notbici commented on GitHub (Jun 30, 2025): Hah a gulf of human evaluation issue.. its technically correct.. but I still think this is a problem which you're going to face with something public and usable by well.. end users.. I'd recommend adding filters: - Recently Updated - Recently Added Then just put both dates in the UI results. {date_added}, {last_updated}. There's a good reason for both, some really nice models get revised. Now if they were added 6 months ago, and you're searching for the latest model its going to be way down the list. My 0.2c.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#33149