Skip to main content

Toolkit - Dynamic Linking

This post if part of a series about the File System Toolkit - a custom content delivery API for SDL Tridion.

In this post I describe the dynamic link resolving logic as part of the Link Factory.

There are three types of links: Component, Page and Binary links. Each of these links can be resolved using the Link Factory.

Component Link

Resolving a Component link implies finding the URL of the Page the target Component appears on. Using the current Toolkit models, it is quite straight forward to retrieve the URL, because the link information is contained within the Component model.

However, there might be several potential links available when performing Component link resolving. Namely, there can be several cases possible:
  • there is no linking information available in the Component model -- this means the link cannot be resolved (i.e. there is no Page published that contains the given Component);
  • there is exactly one Page available that contains the Component -- this means we retrieve the Page URL and return it as the link;
  • there are several potential Pages available that contain the Component -- in this case we need to pick one page only according to the following algorithm: 
    • take the Page that contains the Component with the highest link priority. If there are more than one pages possible, then go to next step;
    • take the Page relatively closest to the Page where the link is displayed on. The relative distance is the number of folders one page is away from the other. If there are more than one pages possible, then go to next step;
    • take the page that was published the latest;
You might notice that in order for the algorithm to work, we must provide the current Page -- this is the page where the link is displayed on. Without this page, we cannot identify accurately the relatively closest potential page.

public Link getComponentLink(TcmUri pageUri, TcmUri componentUri) {
    LinkImpl result = new LinkImpl();
    ComponentMeta componentMeta = modelFactory.getModel(componentUri);
    List<LinkInfo> linkInfos = componentMeta.getLinkInfos();
    if (linkInfos == null || linkInfos.size() == 0) {
        return result;
    }

    String[] urlParts;
    PageMeta pageMeta = modelFactory.getModel(pageUri);
    if (pageMeta == null) {
        urlParts = new String[0];
    } else {
        urlParts = pageMeta.getUrl().split("/");
    }

    int pageId = pageUri.getItemId();
    int maxPriority = 1;
    int minDistance = Integer.MAX_VALUE;
    List<LinkInfo> filteredInfos = new ArrayList<>();

    for (LinkInfo linkInfo : linkInfos) {
        if (linkInfo.getPage() != pageId) {
            int distance = getDistance(urlParts, linkInfo.getUrl());
            int priority = linkInfo.getPriority();
            if (priority > maxPriority) {
                maxPriority = priority;
                minDistance = distance;
                filteredInfos.clear();
            } else if (distance < minDistance) {
                minDistance = distance;
                filteredInfos.clear();
            }
            if (priority == maxPriority && distance == minDistance) {
                filteredInfos.add(linkInfo);
            }
        }
    }

    LinkInfo linkInfo = getLastPublished(filteredInfos);
    if (linkInfo != null) {
        result.setResolved(true);
        result.setUrl(linkInfo.getUrl());
        result.setTargetUri(new TcmUri(componentUri.getPublicationId(),
                linkInfo.getPage(), ItemTypes.PAGE));
    }

    return result;
}

Below are the two helper methods getDistance between two paths and getLastPublished date out of a collection of Pages.

private int getDistance(String[] parts, String url) {
    int result = 0;

    String[] parts2 = url.split("/");
    int n = Math.min(parts.length, parts2.length) - 1;
    int i = 0;
    boolean loop = true;

    for (; i < n && loop; i++) {
        if (!parts[i].equals(parts2[i])) {
            loop = false;
            i--;
        }
    }

    result += parts.length - i - 1;
    result += parts2.length - i - 1;

    return result;
}

private LinkInfo getLastPublished(List<LinkInfo> linkInfos) {
    switch (linkInfos.size()) {
        case 0:
            return null;

        case 1:
            return linkInfos.get(0);

        default:
            long maxPublished = 0;
            LinkInfo result = linkInfos.get(0);

            for (LinkInfo linkInfo : linkInfos) {
                TcmUri metaUri = new TcmUri(linkInfo.getPublication(), linkInfo.getPage(), ItemTypes.PAGE);
                PageMeta pageMeta = modelFactory.getModel(metaUri);
                if (pageMeta != null) {
                    long lastPublished = pageMeta.getLastPublished().getTime();
                    if (lastPublished > maxPublished) {
                        maxPublished = lastPublished;
                        result = linkInfo;
                    }
                }
            }

            return result;
    }
}

Page Links

Resolving a page link implies retrieving the Page model by TcmUri and returning its URL.

public Link getPageLink(TcmUri pageUri) {
    LinkImpl result = new LinkImpl();
    PageMeta pageMeta = modelFactory.getModel(pageUri);
    if (pageMeta == null) {
        return result;
    }

    result.setResolved(true);
    result.setUrl(pageMeta.getUrl());
    result.setTargetUri(pageMeta.getTcmUri());

    return result;
}

Binary Links

Resolving a binary link implies retrieving the Multimedia Component model and retrieving its link information URL. Binaries can be published using different variants, so we can either identify a link by its variant or, in the absence of a variant, simply serve the first link available.

public Link getBinaryLink(TcmUri binaryUri, String variant) {
    LinkImpl result = new LinkImpl();
    ComponentMeta binaryMeta = modelFactory.getModel(binaryUri);
    if (binaryMeta == null) {
        return result;
    }

    if (!binaryMeta.isMultimedia()) {
        return result;
    }

    List<LinkInfo> linkInfos = binaryMeta.getLinkInfos();
    if (linkInfos == null || linkInfos.size() == 0) {
        return result;
    }

    variant = variant == null ? "" : variant;

    for (LinkInfo linkInfo : linkInfos) {
        String linkVariant = linkInfo.getVariant();
        linkVariant = linkVariant == null ? "" : linkVariant;
        if (variant.equals(linkVariant)) {
            result.setResolved(true);
            result.setUrl(linkInfo.getUrl());
            result.setTargetUri(binaryUri);
            break;
        }
    }

    return result;
}



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...

REL Standard Tag Library

The RSTL is a library of REL tags providing standard functionality such as iterating collections, conditionals, imports, assignments, XML XSLT transformations, formatting dates, etc. RSTL distributable is available on my Google Code page under  REL Standard Tag Library . Always use the latest JAR . This post describes each RSTL tag in the library explaining its functionality, attributes and providing examples. For understanding the way expressions are evaluated, please read my post about the  Expression Language used by REL Standard Tag Library . <c:choose> / <c:when> / <c:otherwise> Syntax:     <c:choose>         <c:when test="expr1">             Do something         </c:when>         <c:when test="expr2">             Do something else         </c:when...

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...