Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add filename search as a chip #2213

Merged
merged 1 commit into from
Jul 5, 2018
Merged

add filename search as a chip #2213

merged 1 commit into from
Jul 5, 2018

Conversation

akash1810
Copy link
Member

This will make it easier to debug errors from s3 watcher.

image

this will make it easier to debug errors from s3 watcher
Copy link
Contributor

@mbarton mbarton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great! I've wanted this for a while

@akash1810 akash1810 merged commit 69cf118 into master Jul 5, 2018
@akash1810 akash1810 deleted the aa-filename-chip branch July 5, 2018 14:38
@paperboyo
Copy link
Contributor

Great! I wanted this for... like... 3 years.

More “debugging” chips I say!

@paperboyo
Copy link
Contributor

For the future: this (and maybe all chips) should accept wildcards...

@akash1810
Copy link
Member Author

For the future: this (and maybe all chips) should accept wildcards...

Interesting. Do you have an example where this should apply?

@paperboyo
Copy link
Contributor

paperboyo commented Jul 5, 2018

I try not to let me sick mind wonder where there are no examples. As with all things search/filter, this applies in the same way to Grid, Open Explorer, Bubbles (@currysoup 👋) and all else. If I would like to appear just a little bit facetious, I would say it wouldn’t exactly hurt to have it in dotcom too. Applies to fields AND to values.

(Baby-syntax for wildcards/broken regex/stupid mix. I don’t care much for which is chosen as long as there is an easily accessible help where I will be learning it all over again every single time.)

  • filename:Screen Shot*.png (matches all OSX screenshots)
  • filename:_MG*.jpg −has:fileMetadata.icc (finds candidates for straight from Canon JPGs in AdobeRGB)
  • filename:\d*tomWimbledon5jul18.jpg (finds recent Tom Jenkins’ shoot)
  • filename:.*_modified\..{3,4} OR filename:\1\..{3,4} (finds all occurrences where paperboyo tries to workaround the lack of Versions: originals and modified images; sorted by filename)
  • fileMetadata:icc.Profile Description."sRGB*" OR fileMetadata:xmp.photoshop:ICCProfile."sRGB*" (finds all images with whatever crazy flavour of sRGB profile there is)
  • fileMetadata:xmp.dc:creator["\d*"] (finds images with any number of Creator entries)
  • fileMetadata:exifSub.Lens Specification."*-*" (finds images taken with a zoom lens)
  • fileMetadata:xmp.dc.* (finds all images with any Dublin Core properties)

All this combined with filters showing no. of hits next to properties (and an extra free-text filter for entering the property you’re interested in*) should make most librarians blush.

*to explain, imagine:

  • a search by:Tom Jenkins and a filter sidebar where for a free-text filter you enter filename:\d*.*.jpg
    (should return a list of shoots sorted by the number of photos in each shoot (provided he is consistent in his naming scheme. And provided someone fixes my baby-regex)
  • a search fileMetadata:xmp.dc:creator["\d*"] and a free-text filter containing fileMetadata:xmp.dc:creator* (shows a distribution of Creator entries)

I could go on. How useful any of that would be? How popular? I’m not paid to care seriously for such questions. Luckily.

@paperboyo
Copy link
Contributor

Anecdata-lly, out of all weak signals of photoshoots, filenames are a surprisingly strong one (just look for matching strings where only the numbers differ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants