Interfacing with remote content management systems
AssigneeShinydocs Corporation
InventorJason William David Cassidy
Life of this patent
Estimating the term…
Abstract
A content management system interface at a local computer device is configured to receive user file commands from a file manager and translate the user file commands into content management commands for sending to the remote content management system via a network interface. The content management system interface can further be configured to receive remote file information from the remote content management system via the network interface and translate the remote file information into user file information for the file manager.
Claims17
A computer device for interfacing with, and smooth migration from a legacy storage to, a remote content management system, the computer device comprising:
- a memory;
- a network interface;
- and
- a processor coupled with the memory and the network interface, the processor configured by a set of executable instructions to operate:
- a file manager stored in the memory, the file manager comprising a graphic user interface and an application program interface (API) for receiving a plurality of user file commands from at least one application executed by the processor and outputting user file information;
- a content management system interface stored in the memory, the content management system interface comprising control logic and configured to receive the plurality of user file commands from the file manager and translate the plurality of user file commands into content management commands for sending to the remote content management system via the network interface, the content management system interface further configured to receive remote file information from the remote content management system via the network interface and translate the remote file information into the user file information for the file manager;
- wherein the content management system interface is configured to:
- copy a file from an existing file store to the remote content management system upon receiving a user file command from the plurality of user file commands to access the file and upon determining that the file is not already present at the remote content management system;
- migrate the file on an as-needed basis, wherein a progressive and seamless migration is provided over a time period;
- control a local/shared drive, wherein the content management system interface appears substantially identical to the local/shared drive,
- wherein the control logic is configured to:
- apply at least one filename mask, evaluate at least one file permission for restricting access to at least one file, modify at least one file attribute, modify metadata, control operation of the content management system interface, and map at least one remote path located at the remote content management system,
- wherein the metadata comprises at least one information element of author information, creation date information, modification date information, tag information, and file-size information,
- wherein the permissions associate at least one of a user identity and a group identity to at least one of a specific permitted command and a specific restricted command for at least one specific file,
- wherein the content management system interface comprises an authentication component configured to prompt a user to provide credentials for access to the content management system interface and the remote content management system, and
- wherein authentication by the authentication component is implemented as at least one of a username and password combination, a certificate, and a query of at least one of an enterprise server and a support server.
Dependencies are inferred from the claim text.