mirror of
https://github.com/photoprism/photoprism-docs.git
synced 2026-04-25 18:55:58 +03:00
[PR #101] [CLOSED] Correct search docs regarding album search term #120
Labels
No labels
bug
docs 📚
done
enhancement
enhancement
help wanted
idea
low-priority
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/photoprism-docs#120
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/photoprism/photoprism-docs/pull/101
Author: @des4maisons
Created: 1/30/2022
Status: ❌ Closed
Base:
master← Head:search-docs-update📝 Commits (1)
2a7ba9aCorrect search docs regarding album search term📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
docs/user-guide/organize/search.md(+1 -1)📄 Description
When trying to use the search docs to search only for photos in a certain album, I found that using the syntax described on the docs (
albums:"<title of album>") did not work for me. I had to usealbum:"<ID of album>"(albumwith no S, and ID instead of title of album) to get the expected results.For example, the following worked (I found the string ID of the album in the URL for that album):

However searching by the album name (eg
album:"2022-01-23"oralbums:"2022-01-23") included many pictures not in the album. Searching withalbums:(with S) and using the ID of the album returned no results (egalbums:"ar66h2u1kjj3myku").This change updates the docs according to my experience.
However I'm new to photoprism and I suspect that I'm missing something. Please feel free to tell me what I'm doing wrong, and indicate to me how I can clarify the docs so that others don't run into the same thing as me.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.