Tell us what you are trying to do?
Hi!
I am building a website for a composer where each “Work” represents a specific musical composition, such as Sonata No. 1. The Work is connected to several related content types via Toolset relationships, including:
1. Performers: Musicians who have played the work.
2. Concerts: Events where the work has been performed.
3. References: Articles, books, or other citations discussing the work.
Each content type (CPT) has its own Single Post page, where relationships are displayed in reverse. For example:
• A Performer page lists related Works, Concerts, and References.
• A Concert page lists related Works, Performers, and References.
• A Work page lists related Performers, Concerts, and so forth.
Each relationship is shown in separate Views on these Single Post pages, allowing dynamic presentation of related content.
What I Am Trying to Achieve:
At the bottom of each Work page, I want to display a single unified list of all relevant References dynamically. These references may come from multiple indirect and direct relationships:
1. Performers who are connected to the Work.
2. Concerts where the Work was performed.
3. Direct References connected to the Work itself.
Many References include intermediary metadata, such as page numbers from books where the reference appears, much like academic footnotes. This metadata also needs to be displayed.
The Goal:
• Unified Reference List: Create a View that aggregates all References connected to the Work—whether indirectly (via Performers or Concerts) or directly.
• Avoid Duplicates: Ensure no reference appears more than once in the list, even if it is linked to multiple related entities.
• Display Metadata: Include intermediary data (e.g., page numbers) where applicable.
The Challenge:
Currently, references must be manually associated with each CPT where they appear. This is inefficient and risks inconsistencies. Instead, I want a View for References that dynamically retrieves all relevant references for content already displayed on a given page—without duplicating associations.
The specific challenges are:
1. Traversing nested relationships (e.g., Work → Performer → Reference).
2. Dynamically aggregating References from all connected content types into a single list.
3. Ensuring no duplicate References appear.
4. Properly displaying intermediary metadata for References, such as page numbers.
This functionality would simplify content management and ensure accurate, consistent presentation of references across the site.
Is there any documentation that you are following?
I have reviewed Toolset documentation and forum posts but haven’t been able to achieve this. I’ve experimented with nested Views (and even double-nested Views) but either get duplicate results (as the system cycles through Performer IDs) or blank lists.
Is there a similar example that we can see?
No similar example currently exists.
What is the link to your site?
hidden link (The site is under maintenance mode and only accessible to logged-in users.)
Thank you for your help!