Image management, ACDSee, F-spot, Shotwell, DigiKam, IrfanView

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
peterx's picture

ACDSee, F-spot, Shotwell, DigiKam, and IrfanView all provide some sort of image management from basic to Pro. None of them work on the Web. I looked for an equivalent based on Drupal for flexibility and found nothing. I wrote file/image management applications before Drupal, ported some to D4, D5, D6, and am looking to start again in D7. Is this the right group to discuss image management?

There is no equivalent application in Drupal. There was one attempt at an image management application for Drupal and it faded out. There are lots of attempts at image upload management and image selection for insertion into articles. My requirement is to separate upload from processing so the original is always untouched, so specific processing for articles, galleries, and everything else can be selectively applied after the images are reviewed.

There are a few galleries with tagging and other forms of classification built in. I am aiming to keep the classification separate from any gallery so a gallery can be replaced without losing the classification.

Drupal 7 resolved some image handling decisions and missed on some other points, the lack of a standard date field being one. My target is an application that works with the D7 minimal profile plus a defined set of other modules from core plus, probably, the date field, to make the base simple for people who want a stand alone application. When people want more, they can replace bits with with their choice of alternatives.

Comments

One of the goals of Media

Scott J's picture

One of the goals of Media module is to Use the fields API (formerly CCK) to add fields to any type of media thus allowing you to add a date field if you need one.

Scott Jackson
Wollongong Australia

peterx's picture

Hello Scott, Media looks good for adding media to nodes. I am aiming for an application where each media item is itself a node because it is the focus of the application. The item might be added somewhere or it might be a product in a shop or it might be input to the development of a product.

In media terms, not Media module terms, each item is an asset. Assets have ownership and history. History is a good thing to have in revisions. An asset might be edited into slightly different versions for sale to different customers or for use in different articles. There could be a lot of different dates related to an asset.

A date processing example might help. A photograph from New Years Eve 2010, of which I have hundreds plus a lot of video, has a date/time when it was taken. It also has 2010-12-31 as the event date despite being taken at 1:45 am on 2011-01-01.

A workflow example might also help. The original asset might be 30 MB of RAW file. There might be a 3 KB JPEG watermarked demo for display to anonymous users and a 300 KB watermarked example for display to logged in customers. The original might be trimmed slightly then stored as a PNG then the demos produced from the PNG. The node would record the derived versions and they could be attached using the Media module but the original would be untouched and the basis for the node.

Image

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: