Posted by temelkoff on April 14, 2011 at 9:20pm
I am looking for best (available) practices to manage images for news. Is essential for news images to be reused some times. Does someone find a way to reuse images and arrange them in galleries?
I want to upload images, arrange them in galleries and be able to attach them to articles multiple times?
For now the closest I found is “IMCE file browser”, but it’s very basic way.
There are no thumbnails no description for pictures, only preview when you select the picture.
Someone found a way?
Comments
Galleria Feature
You could try to use Gallerua Feature to Create galleries: http://www.trellon.com/content/blog/making-galleria-feature.
Then you could update it to be able to bind galleries to views.
I think that the best choices
I think that the best choices are available at OpenPublish. It is deployed in Drupal6, and brings a lot of features for images and articles. Create a "image" content type, then create an article select the previous image as a related media in the article. You can have several related medias, as audio, image or video. try it, you will see that it is really great for newspapers.
OpenPublish and NodeStream
The question was about managing images for news, though dporto99 broaden the scope to the best distro for a news site, and plugged Phase II's OpenPublish distro in that context. As long as we're there, one should not overlook NodeOne's Nodestream distro. I think these are the main players in the drupal distro for news space.
The issues involved in choosing a distribution (or building from scratch) are larger than those involved in evaluating a single use case (such as best support for handling images in news). The actual use cases supported by each distro will of course be evolving, so it is deceptive to look at presently supported use cases. Usability is a more important factor, and looming much larger than that, is the question of life-cycle costs associated with a solution, be it a customized distribution, or a custom solution. Isn't that why we choose a distribution? To gain the advantages of the development and QA (reduced life cycle cost) of the distribution producer? But it is complicated, in some ways, working behind the distro introduces new costs, which would not be associated with just building the damn thing from scratch. i.e. when the new distro release breaks your production site in an unexpected way.
So the question of how well the distro (and the distro creator) supports the ongoing integration, this I think is more important than any particular implemented use case. I think it would be valuable to develop these questions.
I heartily agree that rarely
I heartily agree that rarely is usage or production viewed as a cost when evaluating a distribution. However, for a distro to be valuable to the end user it must be intuitive in nature. In other words, a CMS is not as valuable as a CPS, or Content Production System. As primarily a journalist, my goal is not so much classification and categorization of content, but developing content. Such content development requires seamless operation from writing to insert images, to adding cutlines and finally publishing it to all media - twitter, facebook, rss and more. Unless a distro can accomplish these core tasks flawlessly and without any intervention, the distro is worthless.
This core ability to produce and publish is why many turn to "blogging" platforms (an increasingly out-of-date description.) I would love to see a Drupal distro built for online publishers (not developers for online publishers) that just works. I understand this is not as "fun" as throwing in the kitchen sink in terms of features, but sometimes all you want is to be able to turn on the faucet and be sure you'll get water.
Other solution with Node Reference
Hi.
I think you could implement this solutions, an easy way of reuse the images and create image galleries with node reference to image nodes.
Here you can obtain some info: Best image solution for images and news
And here you can see the solution online: Unicef
It's a website developed by our team at Emergya. All the images and videos are nodes. We used node references to that nodes in views.
Hope it helps.
Calm Down & Clear the Cache