A cool module which has great potential. I've incorporated it into the site I'm creating which is building an entomological identification system.

http://professor-moriarty.com/info/node/4

Currently I'm just starting to build the diptera branch, but what I would like to do is for each of the generalizations: Order, Family, Genus have examples thumbs of the lower branches in the hierarchy. So for example clicking on a thumb of a hoverfly would take you to the Syrphidae page.

So if an image is being displayed by virtue of having the machine tag <prefix>:<type>=<nid> then if it also has the tag <prefix>:<type><nid>=<link-nid> the href for the image should go to node/<link-nid> rather than the default node/<nid>/flickr/n.

Thank you for your consideration.

Comments

tobiassjosten’s picture

tobiassjosten commented

It's always nice hearing that the module is actually used. Thanks for telling!

As for the linking, I think that should be handled on a node basis. Relate your nodes using a node relation CCK field. Then you can create a view where you pull the node relations of the current node in, and show their proper data. In this case, the proper data would be the Flickr photos. Flickr nodes doesn't yet pack any Views handlers to offer that but I could definitely see it within the scope of the module.

Would this solution handle your case or have I misunderstood something?

walwyn’s picture

walwyn commented

OK as I'm new to drupal terminology so I'm not absolutely sure I follow this. What I think you are saying is that if one has a node 'diptera' then gather up all the data (flickr photos) from its immediate sub-nodes: Syrphidae, Bibionidae, Asilidae, Rhagionidae, Stratiomyidae, Tabanidae, etc. then somehow link each image with the sub-node from which it came.

One problem with this is that starting off at Entomology you only really need one or two images to indicate Diptera. However, the Diptera node will need several images to indicate the different families. So in order to avoid and explosion of images in the root nodes, one would need to do a union of the images in the current node with the images in the child node to determine where the link of the current node's images should go.

N = Set of images in current node
P = Set of images in child node
(N u P) -> child node

if its possible to perform that operation then the CCK views would work.

I'll need to investigate CCK and views.