Ok assume i have the nodes 1,2,3, and the following Vocabulary terms:

    - A
    - - A1
    - - A2
    - B
    - - B1
    - - B2

I've set up a Smartqueue with the queue limit of 1. The purpose being so that each node can "own" a particular Taxonomy Term.

So my various nodes might have the following Terms associated:

    nid1 A1, A2
    nid2 B1, B2
    nid3 B2

So my various Subqueues look like

    Subqueue A1 = nid1
    Subqueue A2 = nid1
    Subqueue B1 = nid2
    Subqueue B2 = nid3

If I just view the generated View I get a very peaceful list like:

    nid1
    nid1
    nid2
    nid3

If I add a field such as Taxonomy Term however, the view explodes into way more rows and I get loads of duplicates, as well as results which should not be shown (i.e. Subqueue B1 is showing both nodes nid2 + nid3, even though only nid2 is in that particular subqueue).

What I would eventually like to do is output the following results:

    Node // Term // Parent
    nid1 // A1 // A
    nid1 // A2 // A
    nid2 // B1 // B
    nid3 // B2 // B

Am I doing something wrong or is this just something Smartqueue was not built to handle this?

It seems as though the link between Taxonomy and Subqueue is arbitrarily built in the module code rather than the database and that Views doesn't recognize the relationship.

As far as I can tell the field that is outputting the correct Taxonomy Term ID is the field Subqueue Reference. If this was provided as a Taxonomy Relationship, then surely from that Taxonomy Term and Parent Taxonomy Term could be acquired from that.