Using Imported Flickr Image in Views

Any ideas on this?

i like this idea -- i'm not a user of CCK or views, but i've seen it in action :)
i'd need to find docs and RTFM. Can you help out here? Might be a seperate module, or a complimentary module instead.

I would also like to have access to edit the nodes created by Flickr Rippr to add fields (i.e. taxonomy, CCK fields, etc). Is that possible?

i was thinking of adding a nodetemplate for the flickr nodes. Taxonomy, i had flickrtags converting to drupal taxonomy in d4.7 version, but it really didn't scale well. There were many thousands of tags, and it caused the taxonomy admin page to get enourmous.. Taxonomy changed a bit since then, so i'll need to rewrite it, with lotsa warnings about it causing giant vocabuluaries.

I agree that this is a great idea. I wish I had time right now to help implement this. I haven't really looked into the code of this module, but the concept of what it does is very appealing and when I looked at the phpFlickr site, it show that there is a lot of promise for this method. Linking this into CCK and views would amplify it's potential enormously by allowing you to create many customized displays for your photos.

Views and CCK

Views and CCK will open up a lot of possibilities:
* views can perform customized queries for tags or sets or keywords in the descriptions/titles
* views can create gallery pages
* views can create cool blocks with customized queries for tags or sets
* any future modules that tie into views.

Imagefield

If you tied it into the imagefield module (http://drupal.org/project/imagefield), then it would open up a ton of great features:
* the use of imagecache (http://drupal.org/project/imagecache) to create customized sizes and croppings of the images for greater display control in themes.
* thickbox or something similar for displaying DHTML/AJAX image viewers (galleries/slideshows).
* asset management tools, such as the upcoming asset manager module (http://drupal.org/project/am) which is very promising and allows for easy insertion of images into content.

Here's a good article that would show some of the benefits - http://www.lullabot.com/articles/image_and_image_exact_sizes_vs_imagefie...

Flickr Image Hosting? even with imagefield?
It would of course be nice if you could still use the images the photos from the flickr site for the sizes that they provide and only have to serve the custom imagefield version from your own servers, but this may be too complicated to worry about since the server would have to download the original photo from which to make the custom sizes in order to maintain maximum image quality.

Taxonomy

I like the idea of being able to import taxonomy. You should be able to specify which taxonomy to import flickr tags into. That way it can overlap with the tags that are used on other types of content, or it could be placed into it's own taxonomy system so that it doesn't clutter the taxonomy that is used to classify those other types of content. That should be a user decision since requirements differ site to site.

Set Importing

Sets and Photos on Flickr have a many to many relationship. You can assign a single photo to multiple sets and obviously a set can contain multiple photos. It would be ideal if these relationships could be maintained when importing/synchronizing.

Taxonomy presents a fairly simple way to do this. Sets could also be imported as taxonomy terms. These would be imported into a different taxonomy than the one that stores tags. It would be a bit like the Gallery module which has it's own taxonomy where each term represents a photo gallery. For each photo that gets imported, it's sets would get added and the photos would be assign that taxonomy. I'm not sure how to maintain the order of the photos in the set, though it would probably be pretty simple. This is one of the features I like most about using Flickr for photo management is that the Organizr tools on their site are way better than anything we could create on our own sites, so being able to set up photo galleries and slideshow presentations becomes so much easier to manage.

A more powerful solution might be to import the sets into custom cck data types instead of using taxonomy terms. This may be a requirement to maintain image order in the sets. It may be more difficult to maintain the relationship between photos and their sets but it could be done by using node-reference fields. ... needs more thought, and I suspect these answers already exist in some module ...

Teamplay ... ?
Another module with common interests is Embedded Media Field (http://drupal.org/project/emfield), which also doesn't leverage imagefield and instead creates it's own cck image field called "Embedded Image Field". It would be worth communicating about this, perhaps on Drupal Groups to see what direction is best to go so that not too much work is overlapping or if work could be shared by both modules. Embedded media does also support a couple other photo hosting sites. Perhaps EMF could simply enclose FlickrRipper so that it could abandon that branch of it's coding requirements and leave it up to this module which would also be useful for people that have simpler needs such as only displaying images on a blog from their flickr photos. I think the methods are going to be radically different since I think that module doesn't use phpFlickr (http://phpflickr.com/), which has a lot of potential given all the extras that can be easily opened up by using the simple function provided by phpFlickr.

Anyway, I've written way more than I intended. I've been looking for an ideal way to incorporate Flickr into my sites and these modules come close with all the great work that's already been done, but there are still things I would love to do that I just can't. I hope to have more time next month and would love to work on making these things happen, though I would probably need some guidance. Let me know what you think of my ramblings. Maybe we would get a discussion going on drupal groups?