# US 2013/0159846 A1 · Profiling content creation and retrieval in a content management system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2013/0159846 A1 - Document ID: US20130159846A1 - Status: Published application - Kind: A1 - Application number: 13/764,952 - Filed: 2013-02-12 - Published: 2013-06-20 - Earliest claimed: 2007-09-21 - Assignees: International Business Machines Corporation - Inventors: John E. Petri - Web page: https://patentgrep.com/patent/US20130159846A1 ## CPC - G06F 40/123: Storage facilities - G06F 16/907: Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually - G06F 16/908: using metadata automatically derived from the content - G06F 16/93: Document management systems - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A content management system provides a profiling mechanism that automatically tags changes made to elements in a document with applicability metadata, and uses the applicability metadata when processing a request to the repository by a user to filter the query results according to a profile for the user. A profiling mapping policy defines roles for users of the content management system. When content is requested from the repository, the profiling mechanism inserts one or more additional request parameters based on the profile of the user. The results that match both the original request and the additional request parameter(s) are returned to the user. When the user views the results, additional filtering may occur to filter individual elements from the user that do match the user's profile. ## Claims ### Claim 1 An apparatus comprising: at least one processor; a memory coupled to the at least one processor; a repository residing in the memory that includes a plurality of documents, each document including a plurality of elements; and a content management system residing in the memory and executed by the at least one processor, the content management system managing the plurality of documents in the repository, the content management system comprising: a profiling mechanism that receives a request for one of the plurality of documents from the repository from a user, and in response to receiving the request from the user, modifies the request by inserting without further input from the user at least one additional request parameter according to a role of the user to limit elements from the document rendered to the user to elements that satisfy the role of the user, wherein the profiling mechanism monitors additions and modifications to a document by the user, and in response to the additions and modifications to the document by the user, inserts without further input from the user applicability metadata in the document for at least one changed element according to the role of the user, wherein the applicability metadata specifies a required role level for accessing the at least one changed element, and wherein the profiling mechanism limits elements from the document rendered to the user to elements that satisfy the role of the user by comparing the role of the user to the required role level specified in the applicability metadata for accessing the at least one changed element and excludes at least one element in the document from being rendered to the user when the at least one element is a changed element that has a required role level specified in the applicability metadata that is not satisfied by the role of the user, with the result that the profiling mechanism renders some of the plurality of elements in the document to the user and does not render other of the plurality of elements in the document to the user. ### Claim 2 (depends on 1) The apparatus of claim 1 further comprising a profile mapping policy that indicates how user data relates to the role of the user. ### Claim 3 (depends on 2) The apparatus of claim 2 wherein the user data comprises task the user is performing and type of element. ### Claim 4 (depends on 1) The apparatus of claim 1 wherein the profiling mechanism applies the role of the user when the user accesses results from the request so only elements that have applicability metadata that satisfies the role of the user is rendered to the user. ### Claim 5 An article of manufacture comprising: (A) a content management system comprising: a profiling mechanism that receives a request for one of the plurality of documents from the repository from a user, and in response to receiving the request from the user, modifies the request by inserting without further input from the user at least one additional request parameter according to a role of the user to limit elements from the document rendered to the user to elements that satisfy the role of the user, wherein the profiling mechanism monitors additions and modifications to a document by the user, and in response to the additions and modifications to the document by the user, inserts without further input from the user applicability metadata in the document for at least one changed element according to the role of the user, wherein the applicability metadata specifies a required role level for accessing the at least one changed element, and wherein the profiling mechanism limits elements from the document rendered to the user to elements that satisfy the role of the user by comparing the role of the user to the required role level specified in the applicability metadata for accessing the at least one changed element and excludes at least one element that is a changed element in the document from being rendered to the user when the at least one element has a required role level specified in the applicability metadata that is not satisfied by the role of the user, with the result that the profiling mechanism renders some of the plurality of elements in the document to the user and does not render other of the plurality of elements in the document to the user; and (B) non-transitory computer-readable media bearing the content management system. ### Claim 6 (depends on 5) The article of manufacture of claim 5 further comprising a profile mapping policy that indicates how user data relates to the role of the user. ### Claim 7 (depends on 6) The article of manufacture of claim 6 wherein the user data comprises task the user is performing and type of element. ### Claim 8 (depends on 5) The article of manufacture of claim 5 wherein the profiling mechanism applies the role of the user when the user accesses results from the request so only elements that have applicability metadata that satisfies the role of the user is rendered to the user.