Adding Structure and Metadata at the Delivery Tier for Unstructured Content

Adding Structure and Metadata at the Delivery Tier for Unstructured Content

Abstract

This article details the significant value of adding structure and metadata at the delivery tier for unstructured support content such as PDF and HTML. By implementing structure at this level, organizations can enhance content accessibility, improve user experience and maximize call deflection.

Introduction

The need for a cohesive approach to manage unstructured formats and rich media content has never been more critical, yet many organizations' support content is still in unstructured formats, particularly in PDFs and HTML files. These formats often lack the metadata necessary for efficient retrieval and unification.  

The Importance of Structure in Unstructured Content

Adding structure and metadata to unstructured documents allows organizations to leverage their existing content to provide better search and content retrieval, to reuse and unify content, and to improve user experience. This in turn enhances customer self service and reduces support costs. 

Challenges with Unstructured Content

1. Inefficiency in Retrieval: Unstructured content is often difficult to search and retrieve due to the absence of metadata.
2. Content Reuse: The content generated is often required to be deployed in multiple locations- updating this content is often a painful and time consuming process. 
3. Unified Support Content: Different teams may use disparate systems to author various types of content, leading to difficulties in unifying this content for effective support delivery.

Benefits of Adding Structure

1. Faceted Search: By adding metadata and categorization to unstructured files, organizations can significantly improve search capabilities.  Faceted search is a very powerful approach for easily locating support content.
2. Improved User Experience: Once structured, support content can be unified and more easily integrated with interactive elements, enhancing user engagement.
3. Unified Content: Unifying Content at the delivery tier provides a single source of truth for all assets.

Use Cases

1. PDF only- Customers have an issue with multiple PDFs.  Organizations are often beholden to PDF output due to existing designs and the support team’s familiarity with the existing authoring solution.  

Injecting metadata to PDF files at the delivery tier delivers enhanced findability.  If the content is embedded in multiple locations, then allowing for links to this content provides a straightforward process for updating new content.

1. PDF & HTML-  In this case there is a need for the ingestion of content structure already present in HTML.  This can then be used to automatically generate navigation and metadata at the publishing layer.  

Unify this with additional metadata to align with PDF assets.  This approach allows for unified content delivery HTML and PDF assets.

1. PDF, HTML & Rich Media- When rich media such as video is also present then there is a need to inject metadata in order to align with PDF and HTML content.

Once again,- this allows for unified support content delivery.

Creating a Unified Content Management Support Strategy

To create a unified content management strategy for your organization to deliver unstructured content:

1. Evaluate Current Content systems and repositories that are present within support delivery. Is your current delivery serving your needs, or do you need a more comprehensive solution such as a unified delivery portal that can add structure and metadata to your unstructured content?
2. Inject Metadata at the Delivery Tier:  Allow for assets to be imported into a solution and ingest current metadata (if available) whilst having a capability to enhance and inject metadata within the delivery tier.  Focus on developing metadata that will unify the search process.
3. Automate Metadata Tagging: Automatically ingest existing metadata and use this to automate search facets and metadata deployment.
4. Headless Delivery: If you have existing portals/sites/systems where you need to publish the support content, you may need headless delivery that utilizes the enhanced structure and metadata.  

Conclusion

The ability to add structure at the delivery tier for unstructured content presents numerous advantages for organizations.  By enhancing searchability, improving user engagement, and streamlining workflows, businesses can leverage their support assets more effectively for digital delivery. 

Approaching this at the delivery tier allows teams to continue using their current authoring solutions, with minimal disruption to the support content creation process.  This approach delivers findable content and unified support content experiences. This needs to be delivered in a simple user interface due to the ongoing need to update, tag and unify this content.