Browse Prior Art Database

A system to support retention policies for social contents

IP.com Disclosure Number: IPCOM000234725D
Publication Date: 2014-Jan-31
Document File: 3 page(s) / 48K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a system for supporting retention policies for social contents using the social platform and the content applications. The system works by layering a metadata service into the search index of the social platform to provide compliance focused Application Protocol Interfaces (APIs) to appropriate vendors.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 3

A system to support retention policies for social contents

Social contents are unique and complex. As the world of content becomes more social, information becomes more accessible and interconnected. This allows the knowledge

worker to be more productive but it also introduces new challenges for data retention

policies. Social content has a complex inner relationship (e.g., thread responses, linked resources, etc.). In addition, traditional content, such as files, is beginning to surface social capabilities such as shared comments, likes, followers, activity stream entries, re-posts, etc.

All of these characteristics need to be taken into account when making content retention decisions. Managing contents retention is very important for many reasons. There are legal requirements, such as the removal of sensitive information/material as soon as a project is completed. Content growth and time sensitive information pollute the overall content space. In addition, record retention rules must be applied based on business needs.

Current solutions do not effectively manage both the social content characteristics and the retention decisions. A system is needed to support various retention policies and

compliance needs for social contents.

The novel system for supporting retention policies for social contents assumes the inclusion of two discrete components: the social platform and the content applications.

Sometimes a content application ships as part of the social platform (such as Wikis, files, blogs, etc.) but this is not required. The novel system has a set of key components layered into the social platform, including:


• Search Index


• Meta Data Service


• Activity Stream (push of create, update, delete events)


• Social Enablers (e.g., commenting, rating, read metrics, community context, etc.)

Activity Stream and Social Enablers allow content applications to fit into the social platform. These contribute events when the content changes and consume social enablers to add social features to the content application.

Compliance rule engines require being able to query the content application for information about the content in order to derive logic about what has changed (or not changed), given a set of compliance criteria. These criteria evolve over time as social constructs wrapper native applications, but since the native content application lacks knowledge of all social interaction patterns, native applications are unable to answer such questions all alone.

Instead, the Compliance solution leverages the social platform to query the platform search index for content matching the desired criteria (e.g., read during the last week, shared with key influencers, etc.). The social graph is as important as the content when

1


Page 02 of 3

determining what to archive, delete, or retain. Compliance solutions also require the ability to persist custom metadata within the application and use this metadata on custom queries (e.g., filter out...