Skip to main content

A DD4T.net Implementation - Taxonomy Converter

In a previous post, I presented the Taxonomy Factory and a way of retrieving taxonomies and keywords from Tridion. One of the promises I made in there was to explain the conversion process from a Tridion Keyword to a specialized class MyKeyword, a subclass of DD4T.ContentModel.IKeyword.

The DD4T IKeyword class does not provide a way to navigate the taxonomy downwards -- it only provides a ParentKeywords property. Therefore, I created IMyKeyword:

public interface IMyKeyword : IKeyword
{
    IList<IMyKeyword> ChildKeywords { get; }
    IMyKeyword ParentKeyword { get; }
    new IList<IMyKeyword> ParentKeywords { get; }
}

Its accompanying implementation class is quite trivial:

using dd4t = DD4T.ContentModel;

public class MyKeyword : dd4t.Keyword, IMyKeyword
{
    private IList<IMyKeyword> _childKeywords = new List<IMyKeyword>();
    public IList<IMyKeyword> ChildKeywords
    {
        get { return _childKeywords; }
    }

    private IList<IMyKeyword> _parentKeywords = new List<IMyKeyword>();
    public IMyKeyword ParentKeyword
    {
        get { return _parentKeywords.FirstOrDefault(); }
    }
    public new IList<IMyKeyword> ParentKeywords
    {
        get { return _parentKeywords; }
    }
}

In order to convert a Tridion.ContentDelivery.Taxonomies.Keyword to MyKeyword, I'm using the following TaxonomyConverter class, which performs a recursive deep-copy of the given Tridion Keyword to a MyKeyword instance, by populating all properties and building the Parent/Child keyword sets.

using dd4t = DD4T.ContentModel;
using tridion = Tridion.ContentDelivery.Taxonomies;

public class TaxonomyConverter
{
    public IMyKeyword ConvertToDD4T(tridion.Keyword keyword)
    {
        string publicationUri = UriHelper.GetPublicationUri(keyword.KeywordUri);
        dd4t.Publication publication = BuildPublication(keyword, publicationUri);

        IMyKeyword result = new MyKeyword()
        {
            Description = keyword.KeywordDescription,
            Id = keyword.KeywordUri,
            Key = keyword.KeywordKey,
            MetadataFields = BuildMetadata(keyword.KeywordMeta),
            OwningPublication = publication,
            Path = BuildPath(keyword),
            Publication = publication,
            PublicationId = publicationUri,
            TaxonomyId = keyword.TaxonomyUri,
            Title = keyword.KeywordName
        };

        ConvertToDD4TList(result.ParentKeywords, keyword.ParentKeywords);
        ConvertToDD4TList(result.ChildKeywords, keyword.KeywordChildren);

        return result;
    }

    public void ConvertToDD4TList(IList<IMylKeyword> myKeywords, IList tridionKeywords)
    {
        if (tridionKeywords == null)
        {
            return;
        }

        foreach (tridion.Keyword tridionKeyword in tridionKeywords)
        {
            myKeywords.Add(ConvertToDD4T(tridionKeyword));
        }
    }

    private dd4t.FieldSet BuildMetadata(CustomMeta customMeta)
    {
        IDictionary nameValues = customMeta.NameValues;
        if (customMeta == null || nameValues.IsNullOrEmpty())
        {
            return null;
        }

        dd4t.FieldSet fieldSet = new dd4t.FieldSet();
        foreach (NameValuePair pair in nameValues.Values)
        {
            string name = pair.Name;
            switch (pair.ValueType)
            {
                case 2: // Date
                    fieldSet.Add(name, new dd4t.Field()
                    {
                        Name = name,
                        DateTimeValues = pair.MultipleValues.Cast<DateTime>().ToList()
                    });
                    break;

                case 3: // Numeric
                    fieldSet.Add(name, new dd4t.Field()
                    {
                        Name = name,
                        NumericValues = pair.MultipleValues.Cast<float>().Select(x => Convert.ToDouble(x.ToString())).ToList()
                    });
                    break;

                default: // String
                    fieldSet.Add(name, new dd4t.Field()
                    {
                        Name = name,
                        Values = pair.MultipleValues.Cast<string>().ToList()
                    });
                    break;
            }
        }

        return fieldSet;
    }
}


Comments

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: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , 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...

Publish Binaries to Mapped Structure Groups

Today's TBB of the Week comes from the high demand in the field to publish binary assets to different mapped Structure Groups. By default SDL Tridion offers two ways of publishing binaries: All binaries publish to a folder defined in your Publication properties; All binaries rendered by a given template publish to a folder corresponding to a given Structure Group; In my view, both cases are terrible, over-simplified and not representing a real use-case. Nobody in the field wants all binaries in one folder and nobody separates binary locations by template. Instead, everybody wants a mapping mechanism that takes a binary and publishes it to a given folder, defined by a Structure Group, and this mapping is done using some kind of metadata. More often than not, the metadata is the TCM Folder location of the Multimedia Component. I have seen this implemented numerous times. So the solution to publish binaries to a given location implies finding a mapping from a TCM Folder to 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...