OpenContentURL is now available for download from the TSG Downloads page.
OpenContentURL makes it easy for end-users to generate dynamic permanent links to documents that are stored in a content management system or portal. It reduces or eliminates the problem with out of date links to documents in web site, training material, and references throughout an organization. You can read more about how one of our client’s is using it here.
The Problem – Lack of integration
Operating in an environment with integrated IT systems can be a challenge. Users and administrators rely on ECM systems to manage their documents, both in front of and behind the curtains. As systems grow and change, users and IT departments struggle with the need to ensure URL links remain valid for critical procedural and reference documents. With little to no ability to efficiently find dead links in company materials, businesses run the risk of not locating the right information at a crucial time. Policies, legal agreements and even mission critical archives have the potential to be mislinked or misplaced.
The Solution – OpenContentURL
OpenContentURL is a configurable and modular product providing the capability to create permanent links to ECM documents using document attributes. Originally developed for a client who needed a link from SharePoint to go to either Documentum or a portal depending on a rule the product is designed with configuration and flexibility in mind.
An OpenContentURL deployment consists of three components, a source link generator, a target link receiver, and a service with an XML configuration file for handling the linking rules.
Key Features
- Generate permanent links across multiple ECM systems
- Share permanent links across multiple electronic mediums such as email, portals, or other ECM systems like SharePoint
- Links created with OpenContentURL are valid for the entire life of the document. Generated links will always point back to the current approved content, even if re-versioned or re-approved.
The OpenContentURL download includes the following components:
- Resolver Service – Receives and translates an incoming OpenContentURL source link to a target link based on rules mapped to the parameters on the source link. It then redirects the user to the target link.
- Webtop Source Link Generator – The source link generator is unique to the source location of the document. The source link generator contains the rules that will select specific document attributes and build them into a URL link unique to that document.
- The sample included in the distribution builds a link from Webtop using dm_document attributes.
- Webtop Target Link Receiver – The target link receiver will parse parameters and use them to locate the document in the target system. The module will then call a function to return and display the document. The target link receiver communicates directly with the target system.
- The sample included in the distribution includes a Webtop component that will parse an incoming OpenContentURL target link, find the document, build the DRL link for it and then redirect to that link to display the document.
- Documentation is included to walk you through the installation process and application usage.
Not included in this release, but available soon as part of our core HPI product, is an HPI Target Link Receiver. If you are interested in this functionality now, please contact us at inquiry@www.tsgrp.com
As always, you can check out the TSG Learning Zone to see demos of OpenContentURL in action!
This is a great tool
Will OpenContentURL integrate with TaskSpace 6.5 and 6.6?
Even if this integration is not OOTB with OpenContentURL – we can perhaps work on creating the ‘custom link generator’ and ‘receiver’ for TaskSapce – but would such an integration be feasible? Specifically
1. the ‘link resolver’ – is it a WDK customisation’ OR an external servlet? The reason I ask this is because unlike Webtop TaskSpace does not provide a WDK component similar to the DRL component to customise – so an external servlet that translates the inbound URL into a TaskSpace style email link will be preferable
2. Is it possible that OpenContentURL links point to a specific version of the target document instead of ALWAYS pointing to the latest version?
regards
Hi Paras.
Thank you for the positive feedback!
On your first question, the link resolver/receiver and link generator that are in the sample are WDK customizations. However, there is no reason that a separate web service couldn’t be used as a link resolver. As you describe, the web service could take the target OpenContentURL link and convert it into a TaskSpace email link.
It is possible to have a link point to a specific document, version or otherwise. The key is all in how the source link is generated. The parameters put on the link simply need to be sufficient to identify the correct document in the target system.
It sounds like you have a good business case for using the link generator with TaskSpace. I’d love to hear if you choose to use OpenContentURL as part of your system.
Looks a very useful tool.
If you use this solution for intranet content stored in SharePoint to link to documents stored in Documentum, how would the content appear in SharePoint search results? Does the solution support transfer of metadata or for SharePoint to fuly index the linked content ?
Hi Tim.
A URL link is what is stored in SharePoint so the icon that is chosen for that type would display. Ideally, a nice human readable document name would accompany them. If the URLs are indexed they should show up in the SP search results.
This solution uses metadata included as part of the URL for searching and locating the document so it doesn’t transfer it. The metadata needs to already exist in the target system, ex. Documentum.