Ability to quickly favorite a photo while browsing

It would be great to have a simple little clickable icon in the corner of each picture as your browsing your library to mark it as a “favorite”.

Even better would be to have the ability to pick one custom tag to assign to that button. So any time you tap that button it will tag the photo with whatever tag you set in the settings.

As of right now something this small is what’s keeping me using Photo Prism. Because with a library of almost 200k images it’s nice to just be able to quickly mark the best or most important pictures.

In Adobe Lightroom Classic this feature is called Quick Collection and it’s a very handy feature for temporarily organizing photos

1 Like

That would actually be a really cool way of handling this. I use Lightroom all the time and didn’t even think of that.


Welcome to PhotoStructure @Redletter20! Great suggestion: I agree, PhotoPrism’s fave button is easy to use (I hadn’t checked it out for a while and played with the demo yesterday).

But the prerequisite for this feature is the ability to favorite an asset in the first place. A couple questions come from that:

Is there a difference between ratings, :star:, or :heart:?

I had a discussion with some earlier beta users about ratings and favorite/star, and some people wanted

  1. a simple boolean: an asset is marked or not (used by google photos)

  2. a five-star rating (used by adobe and DigiKam)

  3. a ten-star rating (used by many professional DAMs)

  4. Both 1. and either 2. or 3.

Some people suggested that adobe’s flags to carry over.

I actually look at the rating metadata already, and those files rated -1 are excluded.

I could dare to simplify and just support 1., and if the metadata rating is > 3, mark it as a favorite.

And then what?

So, after you’ve marked something as a favorite, how would you expect to get back to your favorites?

  1. Is it just a nav menu like in PhotoPrism? The issue with that is it gets a bit unweildy when you have many hundred/thousand faved assets. I think making that view just do a search for faved:true would make it more useful.

  2. Is it a mode that you turn on while browsing (only show faved assets)?

  3. Something else clever you thought of

(I’ll build 1. after I finish search, and then I need to build delete/exclude, and then probably faces, and then this…)

Thanks for bringing this up!

1 Like

My suggestion - I don’t know if it has already been mentioned before:

→ make multi-selection easy ! Like in any file manager, [Left click] on the first picture, then [Ctrl]+[Left Click] to add another picture to the list of selection, or [Shift]+[Left Click] to select a range of pictures. On mobile devices, this would be [Long tap] on the first picture, then [Tap] on the others you want to add (and… what is the usual move to select a range of files on a mobile ?)

→ Once you have one or several selected pictures, an overlay menu would appear with several actions to do on that selection (Rating or favorite / Share / Download / Move to… / Delete or Trash / …)


i think you should have both, a page for favourites and the search filter.


I definitely am onboard with the multi selection and being able to set a tag.

However I think a simple favorite or not with a page showing all favorites would be welcome too. Just a star, a heart, maybe just double tap the image. Then they all show up in a library called favorites. Simple and fast.

Totally understand the desire, and don’t disagree… I do strongly wish for the data to be stored somewhere in the normal EXIF/IPTC fields so that it’s mobile across platforms. If it’s “just” in the PhotoStructure database, then it’s “vendor lock-in” and I’ll avoid using it - which I would rather not :slight_smile:

Absolutely: this is a big design goal of PhotoStructure from the beginning.

I’ve been completely sunk by prior abandoned apps that squirreled stuff into places that were hard to extricate.

I wanted to test the favorited:true search query, so I just added a tag parser that sets assets as favorited if the “best” variant has a rating of >= 4. This will land in -alpha.3. UI to do mark assets as favorite (and save a sidecar or file metadata with a value of Rating) will come in a future release.

1 Like

And just to be clear… unless you go off in left field, I’m saying that I would avoid using that feature, not avoid PhotoStructure :slight_smile:

1 Like

I suggest to start using custom EXIF hierarchical subject/keyword to store any PhotoStructure specific metadata, so it’s available to view even outside of the PhotoStructure app itself if needed. Such as

!!!PhotoStructureInternal > Favorited


!!!PhotoStructureInternal > Rating > 5


!!!PhotoStructureInternal > Collections > !!!QuickCollection

This model will allow you to store any textual metadata but being available to view via ExifTool or any other DAM with hierarchical subject support

1 Like

Interesting idea!

As far as I understand, EXIF tags don’t support arbitrary keys.

All of the metadata the PhotoStructure extracts or modifies should be able to be encoded in standard tags.

I’m hoping to be able to encode all user operations into the XMP history struct: https://exiftool.org/TagNames/XMP.html#ResourceEvent

The reason I suggested to keep the metadata in the HierarchicalSubject tag rather than custom XMP tags because most of the software I’ve used don’t have a nice way to view those. From the other hands, hierarchical keywords are visible even in standard Windows File Properties window (in a flat form, though)

1 Like

Alternatively, I suggest you to use both custom XMP tags with the fallback to the hierarchical keywords.

Personally, I even use keywords like Albums > Album1 in addition to putting my photos to Album1 album in my DAM, so this information is not vendor-locked and I can easily switch my DAMs if needed

I think a heart and/or a 5 star or even 3 star system would be good. 10 star is too much.

I also agree with what was said about multi-selection being key and the overlay for various actions to do on the multiple images.

I think this ability is very closely related to albums.

Since I saw the link to the initial release on the 2.0.0-alpha build I was re-reading this thread and thought of something- not asking for a change, just pointing out a different use case fir future thought.

Up the chain @mnm mentioned looking for items with >4 of whatever as favorites… makes sense and I don’t object.

But… I use stars differently… it’s a system I saw recommended somewhere and really clicked for me.

Good pictures get 1 star… then the best of those might get 2… and the best of the two’s get a three- I don’t think I have any (yet) above that.

So instead of seeing a really good picture and saying “that’s a five” I say “that’s a star”. And then if I’m browsing starred pictures and one really stands out somehow, it gets another star.

Maybe it’s just a weird mental thing for me :slight_smile:

Again, just a random thought.

1 Like

I actually made the rating for what :heart: means be configurable, so we can handle 1 star. It’s just a toggle for now, though, so the “super star” isn’t handled (yet).

Sure: it’s a bit involved!

  1. If a user has liked (or un-liked) an asset via PhotoStructure, and the asset file variations nor their sidecars have not been touched since that action was made, that value wins.

  2. Otherwise, PhotoStructure looks for a number between -1 and 5 associated to the Rating metadata tag (see the XMP specification: (this supports a value from 0 to 5, or -1 for “rejected”) in both files and sidecars. “First one in wins”: PhotoStructure first looks at the “best” asset file variation and sidecars. If that file doesn’t have a value, it looks at the first file with a value in order of last-modified time. If no value is found, it looks at the RatingPercent tag (which is only rarely used) and converts it to a value between 0 and 5.

    Given that we find either a Rating or RatingPercent, the asset will be considered “liked” if the value is equal to or greater than the new-in-version 2.0 likeRating setting, which defaults to 3.

  3. If we still don’t have a value yet, we’ll look for a Google Takeout JSON file associated to any asset file variation. If any are found, and a favorited value is set, we’ll use that.

You probably have it somewhere, but a single “reference document” of which metadata fields are used by Photostructure would be a great resource.

Feel like I’ve asked (and probably had this answered) before, sorry if it’s a repeat :slight_smile:

1 Like

Nope: I’m afraid I’ve done pretty much all of it on-demand.

When I get a chance, I’m wanting to convert the docs at photostructure.com (and more reference docs from the forum) into a proper manual: Migrate all PhotoStructure documentation to a "manual"