Skip to main content

A Implementation - Taxonomy Factory (part 2)

In a previous post, I presented the Taxonomy Factory and a way of retrieving taxonomies and keywords from Tridion.

In this post, I will present more functionality about retrieving content tagged against a certain Keyword.

    string[] GetRelatedContent(IMyKeyword keyword);
    string[] GetRelatedContentBySchema(IMyKeyword keyword, string schemaTitle);
    string[] GetRelatedContentBySchemaAndMetadata(IMyKeyword keyword,
            string schemaTitle, string metadataKey, string metadataValue);

All these methods return a list of TcmUris representing Components or Pages that are tagged with the given Keyword.

Method GetRelatedContent is the simplest of these methods, and it returns the TcmUris of all items that are directly tagged with the given Keyword. The implementation uses the Tridion.ContentDelivery.Taxonomies.TaxonomyRelationManager to retrieve the related content:

    private TaxonomyRelationManager manager;

    public MyTaxonomyFactory()
        manager = new TaxonomyRelationManager();

    public string[] GetRelatedContent(IMyKeyword keyword)
        Keyword tridionKeyword = new Keyword(keyword.TaxonomyId, keyword.Id);
        return manager.GetTaxonomyContent(tridionKeyword, false);

Method GetRelatedContentBySchema returns only Component TcmUris, which are tagged with the given Keyword and which are also on the given Schema title. The method uses the GetTaxonomyContent method on the TaxonomyRelationManager that also accepts a Criteria object. We are passing in a SchemaTitleCriteria to restrict the result set.

public string[] GetRelatedContentBySchema(IMyKeyword keyword, string schemaTitle)
    Criteria schemaCriteria = new SchemaTitleCriteria(schemaTitle);
    Keyword tridionKeyword = new Keyword(keyword.TaxonomyId, keyword.Id);
    return manager.GetTaxonomyContent(tridionKeyword, false, schemaCriteria);

Finally, method GetRelatedContentBySchemaAndMetadata returns Component TcmUris that are tagged with the given Keyword and are also on a given Schema title and have the given custom meta field and value. The method creates an AndCriteria between a SchemaTitleCriteria and a CustomMetaValueCriteria and then passes the AndCriteria to the GetTaxonomyCriteria method:

public string[] GetRelatedContentBySchemaAndMetadata(IMyKeyword keyword,
        string schemaTitle, string metadataKey, string metadataValue)
    Criteria criteria = new AndCriteria(
        new SchemaTitleCriteria(schemaTitle),
        new CustomMetaValueCriteria(new CustomMetaKeyCriteria(metadataKey), metadataValue)
    Keyword tridionKeyword = new Keyword(keyword.TaxonomyId, keyword.Id);
    return manager.GetTaxonomyContent(tridionKeyword, false, criteria);

These simple methods provide very powerful querying capabilities for dynamic content, which I happen to use extensively in my last 3 projects (all in DD4T context).


Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: I stumbled upon the following post from 2008 (!!!), , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven