I usually take photographs in batches, all relating to a particular subject or activity (such as "My Vacation in Honduras", or "Susan's Wedding"). These batches vary in size, but often number in the hundreds of photos.

ImageX uploads all selected images to the same, single gallery ("Library"). To distribute photos from this gallery, the user is required to edit each photo, and change the gallery name to a more suitable one. When working with batches of photos (especially large batches), this is a time-consuming process. (With one batch, I resorted to applying an SQL update statement to the underlying tables rather than attempt to edit 190 photos just to change the gallery on each).

If the ImageX UI included an option that controlled the target gallery in which the items would be first placed, then a great deal of needless, mindless processing would be shifted from the end-user to the application.

Comments

lpitcher’s picture

lpitcher commented

I should note that I use the gallery values to distinguish which particular subject or activity the image belongs to. Thus, images that I load through ImageX are immediately moved to other galleries, and the "Library" gallery is emptied.

If you include a user-set target Gallery as part of the UI, it could default to the "Library" gallery, keeping the current behaviour. Only when the user changes it to some other Gallery name would this new behaviour apply.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Component: User interface » Code

A similar issue is #314057: Upload images into a specific OG based on the URL.

I've created an alternate way to tag images using Views Bulk Operations: bulk image uploading and tagging screencast.

DBSLLC’s picture

DBSLLC commented

Any other updates, ladies and gents?