Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Document View Management System Based on Role Model

IP.com Disclosure Number: IPCOM000240314D
Publication Date: 2015-Jan-22
Document File: 7 page(s) / 172K

Publishing Venue

The IP.com Prior Art Database

Abstract

The main idea of this disclosure is to provide a document view function to keep a mapping relationship between user/role and content.We just need to maintain a single version, and specify which content is visible to which user/role,each user/role should have a password for identification,document can be exported to different versions based on roles

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

Page 01 of 7

Document View Management System Based on Role Model


1. Background:

Document is widely used in business, for different business using propose, we may have different content view for different users, like: User A: grant permission on content page 1 to 10
User B: grant permission on content page 5 to 15
User C: grant permission on content page 8 to 20

Pain points

Pain point 1:


Currently solution is we need to maintain 1 baseline version and make 3 different copies, it wastes a lot of disk space.

Pain point 2:


What's more important is that if we need to update some content in the document, we need to open all versions and update one by one, it wastes huge time.

Pain point 3:


For sensitive documents, we need to keep different versions for the same event, and send a specific version to the specific person, it's easily to make mistake.

Pain point 4:


For non-sensitive documents, like advertisement / notice, they may contains lots of contents and we need time to find what we want and have interests.

Pain point 5:


Due to different personal document preference, like font, background color, size, user need to change settings one by one.


2. Summary of Invention:

The main idea of this disclosure is to provide a document view function to keep a mapping relationship between user/role and content We just need to maintain a single version, and specify which content is visible to which user/role
Each user/role should have a password for identification
Document can be exported to different versions based on roles

1



Page 02 of 7

The implementation workflow could be like following:
1.There should be a role management function for document owner, the owner is able to create/delete role and set password for each roles.


2.On each content page, it can implement by right clicking menu and select Role->Grant permission to the role, then grant read/write permission.


3.Save the file and exit.


4.When re-openning the file, a prompt dialog will let user to input role/password, and load related grant content once pass the authentication.


5.Another solution is export the document based on a specified role, then generate a new copy to that role. This will not contain role/password check.

Claim points:
1. Document content management based on roles

The module identifies roles via role name/password. Each role has a document pages mapping list.

Users can do operations below:
Add / remove role


Reset role password
Rename role
Add / remove document page to role
Grant read / write permission for each document page

Please see the chart below.

2



Page 03 of 7


2. Simplify the version management process


Users don't need to keep several copies for a same document but for different purpose.


For non-sensitive document, users just need to update one single document, then use export feature to generate different versions.


For sensitive document, if author updates the single document then send to target users, they can see the updated content with role/password.


3. Export to the role to follo...