UX: Custom filters based on saved search queries #1672

New issue

Closed

opened 2026-02-20 00:18:51 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 00:18:51 -05:00

Owner

Originally created by @dingedan on GitHub (Jan 10, 2023).

Describe what problem this solves and why this would be valuable to many users

PhotoPrism already has a very advanced search feature with many possible text filters but it's a bit of a hassle to always remember the terminology or to always have to type a filter that you frequently use.

Describe the solution you'd like

A custom drop down selection field in the extended search menu with 'bookmarked' search queries. These bookmarks can be managed in the settings section where the list can be maintained. For each entry there are two configurable text fields: 'name' and 'query'. The name is displayed in the selection box and the query is obviously what is then (invisibly) applied when selected in the search. In the settings it should also be possible to delete entries and of course to add new ones. The ability to re-order would be nice to have.

Describe alternatives you've considered

Browser bookmarks

Additional context

Use cases for which I'd currently use this:

Filter for photos with certain missing meta data so I can update those.
We are multiple users in our family and so far I've uploaded their pictures in different folders, using such a filter would make it easy to switch between photos from the different users or combined. This feature will probably be added soon as part of the multi-user development but until then a custom filter would be useful.

Originally created by @dingedan on GitHub (Jan 10, 2023). **Describe what problem this solves and why this would be valuable to many users** PhotoPrism already has a [very advanced search feature](https://docs.photoprism.app/user-guide/search/filters/) with many possible text filters but it's a bit of a hassle to always remember the terminology or to always have to type a filter that you frequently use. **Describe the solution you'd like** A custom drop down selection field in the extended search menu with 'bookmarked' search queries. These bookmarks can be managed in the settings section where the list can be maintained. For each entry there are two configurable text fields: 'name' and 'query'. The name is displayed in the selection box and the query is obviously what is then (invisibly) applied when selected in the search. In the settings it should also be possible to delete entries and of course to add new ones. The ability to re-order would be nice to have. **Describe alternatives you've considered** Browser bookmarks **Additional context** Use cases for which I'd currently use this: - Filter for photos with certain missing meta data so I can update those. - We are multiple users in our family and so far I've uploaded their pictures in different folders, using such a filter would make it easy to switch between photos from the different users or combined. This feature will probably be added soon as part of the multi-user development but until then a custom filter would be useful.

deekerman

2026-02-20 00:18:51 -05:00

closed this issue
added the
duplicate
label

deekerman commented

2026-02-20 00:18:53 -05:00

Author

Owner

@kvalev commented on GitHub (Jan 10, 2023):

This is very similar to #1431

@kvalev commented on GitHub (Jan 10, 2023): This is very similar to #1431

deekerman commented

2026-02-20 00:18:53 -05:00

Author

Owner

@graciousgrey commented on GitHub (Jan 13, 2023):

@dingedan as far as I can see #1431 should cover your use case. I will close this issue as duplicate, feel free to leave a 👍 in the smart albums issue :)

@graciousgrey commented on GitHub (Jan 13, 2023): @dingedan as far as I can see #1431 should cover your use case. I will close this issue as duplicate, feel free to leave a :+1: in the smart albums issue :)

deekerman commented

2026-02-20 00:18:53 -05:00

Author

Owner

@dingedan commented on GitHub (Jan 13, 2023):

@graciousgrey : Yes indeed it covers my uses cases, thanks for pointing that out @kvalev. I do feel that the way I had this in mind would be a lot more versatile once the filters are made available in all views as described in #651 but I also understand prioritization of features is needed.

@dingedan commented on GitHub (Jan 13, 2023): @graciousgrey : Yes indeed it covers my uses cases, thanks for pointing that out @kvalev. I do feel that the way I had this in mind would be a lot more versatile once the filters are made available in all views as described in #651 but I also understand prioritization of features is needed.