Browse Prior Art Database

DGLS: Saving Content For Different Audiences According to Profile Induced Rules Disclosure Number: IPCOM000233990D
Publication Date: 2014-Jan-06
Document File: 2 page(s) / 51K

Publishing Venue

The Prior Art Database


Disclosed are a method and system to save written content according to an audience profile. The profile triggers rules to automatically hide or show certain content when the document is saved. This eliminates the need for a user to create and save multiple versions of the same basic content with variations for different audiences.

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

Page 01 of 2

Saving Content For Different Audiences According to Profile Induced Rules

Saving Content For Different Audiences According to Profile Induced Rules

When preparing a slide presentation or other document , a user might need to include or remove content (e.g., speaker notes, notes of confidentiality, technical information, statistics, etc.) based on the reader or audience. For example, a Sales team and a Research & Development team might need the same high-level information, but content specific to those groups is very different; or, a presenter might want to share a slide deck, but not the speaker notes. Currently, the addition and removal of content is a manual process that requires the writer to develop and maintain multiple versions of the same basic information with variations based on audience . This is a labor-intensive and time-consuming process.

A method is needed to allow a content developer to more efficiently prepare , save, and share presentations or documents based on the needs of the reader or audience .

The novel idea is to save any content that a user creates and intends to share with others (e.g., presentations, text documents, emails, blog entries, etc.) according to a profile. The user defines profiles and rules in relation to the impact that a profile has on the content. The rules are applied before the document is saved .

For example, when creating a presentation, the user can save/print according to a predefined profile, such as Sales Team, Research & Development Team, Public, Confidential, etc. For each profile, some rules are predefined and saved by the user .

During the development of the document, the user codes the content so that it can be associated with the profile rules. Content can be coded by color, with keywords, by annotations on a page, etc. The predefined profile rules affect which content is hidden or shown, as the method applies the rules to the coded content before it is saved . The user does not have to maintain different versions for different people ; the method simply hides or shows...