Skip to main content

A DD4T.net 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).


Comments

Popular posts from this blog

Toolkit - Dynamic Content Queries

This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio

A DD4T.net Implementation - Custom Binary Publisher

The default way to publish binaries in DD4T is implemented in class DD4T.Templates.Base.Utils.BinaryPublisher and uses method RenderedItem.AddBinary(Component) . This produces binaries that have their TCM URI as suffix in their filename. In my recent project, we had a requirement that binary file names should be clean (without the TCM URI suffix). Therefore, it was time to modify the way DD4T was publishing binaries. The method in charge with publishing binaries is called PublishItem and is defined in class BinaryPublisher . I therefore extended the BinaryPublisher and overrode method PublishItem. public class CustomBinaryPublisher : BinaryPublisher { private Template currentTemplate; private TcmUri structureGroupUri; In its simplest form, method PublishItem just takes the item and passes it to the AddBinary. In order to accomplish the requirement, we must specify a filename while publishing. This is the file name part of the binary path of Component.BinaryConten

Scaling Policies

This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the