Centralized, server-less content management
First Claim
1. A content management system comprising:
- a non-dedicated server that comprises a live content server that hosts live content and a content server that hosts staged content;
said content server including;
a processor coupled to a memory;
a metadata directory on said content server configured to store a metadata file associated with a work-in-progress (WIP);
a first folder on said content server for storing notifications to a plurality of users in a workflow group; and
a second folder on said content server for storing one or more versions of said WIP;
a remote filing system associated with said content server;
interface logic at a computer of each of said plurality of users, said interface logic polling said first folder through said remote filing system for locating said notifications; and
a WIP state variable that controls edit access to said WIP;
wherein said metadata file comprises information mapping said staged content to said live content, the WIP state variable, and identifying which of the plurality of users is editing the WIP; and
wherein a content document on said content server is locked responsive to an editing user of said plurality of users selecting said document for editing, wherein, responsive to said user selection, said metadata file is locked for each of said plurality of users except said editing user.
3 Assignments
0 Petitions
Accused Products
Abstract
A content management system (CMS) is made up of a content server that includes a metadata file stored on the content server relating to transactions performed with a work-in-progress (WIP), a first folder on the content server for storing notifications to a plurality of users in a workflow group, and a second folder on the content server for storing one or more versions of the WIP. The CMS also includes a remote filing system associated with the content server. The CMS also includes interface logic at a computer of each of the plurality of users allows the user to manipulate the WIP and polls the first folder through the remote filing system for locating the notifications. A WIP state variable is included within the metadata file that assists the control of edit access to the WIP.
9 Citations
32 Claims
-
1. A content management system comprising:
-
a non-dedicated server that comprises a live content server that hosts live content and a content server that hosts staged content; said content server including; a processor coupled to a memory; a metadata directory on said content server configured to store a metadata file associated with a work-in-progress (WIP); a first folder on said content server for storing notifications to a plurality of users in a workflow group; and a second folder on said content server for storing one or more versions of said WIP; a remote filing system associated with said content server; interface logic at a computer of each of said plurality of users, said interface logic polling said first folder through said remote filing system for locating said notifications; and a WIP state variable that controls edit access to said WIP; wherein said metadata file comprises information mapping said staged content to said live content, the WIP state variable, and identifying which of the plurality of users is editing the WIP; and wherein a content document on said content server is locked responsive to an editing user of said plurality of users selecting said document for editing, wherein, responsive to said user selection, said metadata file is locked for each of said plurality of users except said editing user. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A method comprising:
-
creating, on a non-dedicated server that hosts both live content and staged content, a file structure, said file structure comprising; a live content file that contains said live content; a metadata directory configured to store a metadata file associated with said staged content; a user folder for holding one or more messages directed to a user; a work-in-progress (WIP) folder for holding one or more versions of WIP within said staged content; responsive to an edit state of said WIP, restricting editing of said metadata file to an editing user; responsive to said WIP entering a transit state; opening said editing of said metadata file; storing one of said one or more messages to said user folder, wherein said message notifies availability of said WIP for review; and responsive to a publish command issued by said user, copying a current version of said WIP to a publish location; wherein said metadata file comprises information mapping said staged content to said live content, a WIP state variable, and identifying any user editing the WIP. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A computer program product having a non-transitory computer readable storage device with computer program logic recorded thereon, said computer program product comprising:
-
code for creating, on a server that hosts both a) live content that is published for access by users and b) staged content that is not published for access by said users, a file structure, said file structure comprising; a live content file that contains said live content; a metadata directory configured to store a metadata file associated with said staged content; a user folder for holding one or more messages directed to a user; a work-in-progress (WIP) folder for holding one or more versions of WIP in said staged content; responsive to an edit state of said WIP, code for restricting editing of said metadata file to an editing user; responsive to said WIP entering a transit state; code for opening said editing of said metadata file; code for storing one of said one or more messages to said user folder, wherein said message notifies availability of said WIP for review; and responsive to a publish command issued by said user, code for copying a current version of said WIP to a publish location; wherein said metadata file comprises information mapping said staged content to said live content, a WIP state variable, and identifying any user editing the WIP. - View Dependent Claims (20, 21, 22, 23, 24, 25)
-
-
26. A system comprising:
-
a server comprising both a) a web server that hosts live web content that is published for general public access and b) a content management server that hosts staged content that is not published for general public access; a processor coupled to a memory on said server; a file structure on said server, said file structure comprising a live web content file that contains said live web content hosted by said web server; said content management server comprising means for creating in said file structure; a metadata directory configured to store a metadata file associated with said staged content; a user folder for holding one or more messages directed to a user; a work-in-progress (WIP) folder for holding one or more versions of WIP in said staged content; responsive to an edit state of said WIP, means for restricting editing of said metadata file to an editing user; responsive to said WIP entering a transit state; means for opening said editing of said metadata file; means for storing one of said one or more messages to said user folder, wherein said message notifies availability of said WIP for review; and responsive to a publish command issued by said user, means for copying a current version of said WIP to a publish location; wherein said metadata file comprises information mapping said staged content to said live content, a WIP state variable, and identifying any user editing the WIP. - View Dependent Claims (27, 28, 29, 30, 31, 32)
-
Specification