mirror of
https://github.com/photoprism/photoprism.git
synced 2026-03-02 22:57:18 -05:00
Option to copy/export file names/paths for batch of selected photos #1090
Labels
No labels
ai
android
api
auth
awesome
bug
bug
ci
cli
config
database
declined
deprecated
docker
docs 📚
documents
duplicate
easy
enhancement
enhancement
enhancement
epic
faces
feedback wanted
frontend
hacktoberfest
help wanted
idea
in-progress
incomplete
index
invalid
ios
labels
live
live
low-priority
macos
member-feature
metadata
mobile
nas
needs-analysis
no-coding-required
no-coding-required
observability
performance
places
please-test
plus-feature
priority
pro-feature
question
raspberry-pi
raw
released
released
released
research
resolved
security
sharing
tested
tests
third-party-issue
thumbnails
upgrade
upstream-issue
ux
vector
video
waiting
won't fix
won't fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/photoprism#1090
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?
Originally created by @catleeball on GitHub (Sep 9, 2021).
From the Photoprism web UI, It would be nice if the user could:
This would be nice for folks who want to browse, search, and select photos in Photoprism, and then manipulate the photos with an outside tool.
This would be particularly handy since photoprism can search along labels and metadata fairly easily, but there will always be a niche tool or feature or script that a user will want to apply to that selection. :)
An example workflow might be:
Thanks!
@graciousgrey commented on GitHub (Sep 10, 2021):
Wouldn't it be even more convenient to have the action "Open selected files with tool xy" ?
@ludditus-RPI commented on GitHub (Sep 10, 2021):
There are definitely use cases for "open file in tool xy" but I can also see a use case that wants to not open 50 images simultaneously in a photo editor - some tools would open a separate window for each image and might be pretty sluggish.
@catleeball commented on GitHub (Sep 12, 2021):
Sorry for my slow reply here!
@graciousgrey : That would be a nice feature for general users! But it would also be nice to access the filepaths for use with scripts.
If I were to do "Open selected with..." and choose something like
/usr/bin/vimcould I access the plain text paths? Or "Open with..." and specify "script.sh" where the script is listening for stdin, would that work maybe?@graciousgrey commented on GitHub (Sep 25, 2021):
@ludditus-RPI True it really depends on the tool.
@catleeball What path would you expect to be exported for stacks and raws?