If the module could also browse, display in sets and show the tags common to a flickr group.

So, the root http://www.sitename.domain/flickrhood would be linked to the flickr group rather than the individuals.

To me this would help create more of a community 'hood feel.

Everyone who had an account on the drupal site could link their images stored in flickr to a group in flickr. This would then create a commonality of tag links for the community and a general community 'pool' of images within the drupal site.

Comments

andrewlevine’s picture

andrewlevine commented
Status: Active » Closed (works as designed)

I haven't implemented the frontend of the community part of flickrhood yet.

Rather then have a flickr group for a drupal site, and just duplicate all the functionality of that group, I had previously decided to collect information from the users individually. If I remember correctly this was because having this group wouldn't yield any advantage over just creating a site-specific tag that users would put on photos. Things would be more complicated (admin has to create the group, users have to join the group, etc).

I'm totally open to changing my plan if you can convince me yours make more sense.

Andrew

deantregenza’s picture

deantregenza commented

I don't pretend to know the inside or outs of how flickr and the API works.

I suppose I just thought that by using the flickr group API functions it may have done most of the work for you.

What I primarily hope for would be that in the frontend of the community you would get a combined 'tag' list that could also be searched within drupals search function.

Thinking your idea through - it would be the most 'less is more' approach as it doesn't depend on the member assigning their images to the flickr group. But, on the other hand, they may want to have the option to restrict images that they want to specifically share with the rest of the members on the drupal site. This would also help keep the images to the subject matter of interest to the community.