Synchronization and strategic storage of multiple versions of a file

Patent metadata

Field	Value
Publication number	US-9805051-B2
Application number	US-201414482952-A
Country	US
Kind code	B2
Filing date	Sep 10, 2014
Priority date	Sep 10, 2014
Publication date	Oct 31, 2017
Grant date	Oct 31, 2017

Abstract

Disclosed are some examples of systems, methods and storage media for synchronizing files between a user's computer and a remote system, and more specifically, to strategically storing updated versions of a file on the remote system. In some implementations, a system is capable of receiving a request including an updated version of a file. The system is additionally capable of identifying a version type of the updated version, identifying a current version of the file stored in one or more storage devices, and determining, based on the version type of the updated version, whether to store the updated version in the one or more storage devices as a new version or to replace the current version with the updated version. The system is further capable of storing the updated version in the one or more storage devices based on the determination.

First claim

What is claimed is:

1. A system comprising:
a database system implemented using a server system, the database system configurable to cause:
processing a first request comprising a first updated version of a file, a selection of a first version type and a first indication of a first user permission level, the file comprising a current version and a plurality of historical versions;
identifying the first version type of the first updated version of the file as a minor version of the file based on the first user permission level;
processing a second request comprising a second updated version of the file different from the first updated version of the file, a second user selection of a second version type and a second indication of a second user permission level, the second indication of the second user permission level being a higher level than the first permission level;
identifying a first current version of the file stored in a database of the database system;
identifying the second version type of the second updated version of the file as a major version of the file based on the second user permission level, the major version of the file representing a new version of the file to replace the first current version;
designating the first current version of the file as a first one of the historical versions; and
storing the second updated version of the file as a second current version.

2. A computer-implemented method comprising:
processing a first request comprising a first updated version of a file, a selection of a first version type and a first indication of a first user permission level, the file comprising a current version and a plurality of historical versions;
identifying the first version type of the first updated version of the file as a minor version of the file based on the first user permission level;
processing a second request comprising a second updated version of the file different from the first updated version of the file, a second user selection of a second version type and a second indication of a second user permission level, the second indication of the second user permission level being a higher level than the first permission level;
identifying a first current version of the file stored in one or more storage devices;
identifying the second version type of the second updated version of the file as a major version of the file based on the second user permission level, the major version of the file representing a new version of the file to replace the first current version;
designating the first current version of the file as a first one of the historical versions; and
storing the second updated version of the file in the one or more storage devices based as a second current version.

3. A computer program product comprising program code executed by one or more processors when retrieved from a non-transitory computer-readable storage medium, the program code comprising instructions configurable to cause:
processing a first request comprising a first updated version of a file, a selection of a first version type and a first indication of a first user permission level, the file comprising a current version and a plurality of historical versions;
identifying the first version type of the first updated version of the file as a minor version of the file based on the first user permission level;
processing a second request comprising a second updated version of the file different from the first updated version of the file, a second user selection of a second version type and a second indication of a second user permission level, the second indication of the second user permission level being a higher level than the first permission level;
identifying a first current version of the file stored in one or more storage devices;
identifying the second version type of the second updated version of the file as a major version of the file based on the second user permission level, the major version of the file representing a new version of the file to replace the first current version;
designating the first current version of the file as a first one of the historical versions; and
storing the second updated version of the file in the one or more storage devices based as a second current version.

4. The system of claim 1 , wherein identifying the second version type of the second updated version of the file as indicating the major version of the file comprises:
determining whether there are two or more version types associated with the file.

5. The system of claim 1 , the database system configurable to cause:
identifying a source of the second updated version, and
identifying a source of the first current version; and
wherein the storing is based on the source of the second updated version and the source of the first current version.

6. The system of claim 1 , the database system configurable to cause:
identifying a name of the second updated version, and
identifying a name of the first current version; and
wherein the storing is based on the name of the second updated version and the name of the first current version.

7. The system of claim 1 , the database system configurable to cause:
identifying a timestamp of the second updated version, and
identifying a timestamp of the first current version; and
wherein the storing is based on the timestamp of the second updated version and the timestamp of the first current version.

8. The method of claim 2 , wherein identifying the second version type of the second updated version of the file as indicating the major version of the file comprises:
determining whether there are two or more version types associated with the file.

9. The method of claim 2 , the method further comprising:
identifying a source of the second updated version, and
identifying a source of the first current version; and
wherein the storing is based on the source of the second updated version and the source of the first current version.

10. The method of claim 2 , the method further comprising:
identifying a name of the second updated version, and
identifying a name of the first current version; and
wherein the storing is based on the name of the second updated version and the name of the first current version.

11. The method of claim 2 , the method further comprising:
identifying a timestamp of the second updated version, and
identifying a timestamp of the first current version; and
wherein the storing is based on the timestamp of the second updated version and the timestamp of the first current version.

12. The computer program product of claim 3 , wherein identifying the second version type of the second updated version of the file as indicating the major version of the file comprises:
determining whether there are two or more version types associated with the file.

13. The computer program product of claim 3 , the instructions further configurable to cause:
identifying a source of the second updated version, and
identifying a source of the first current version; and
wherein the storing is based on the source of the second updated version and the source of the first current version.

14. The computer program product of claim 13 , the instructions further configurable to cause:
identifying a source of the second updated version includes identifying a user responsible for the second updated version;
identifying a source of the first current version includes identifying a user responsible for the first current version; and
storing the second updated version when the source of the second updated version is different than the source of the f

Assignees

• Salesforce Com Inc

Inventors

• Bergner Emil
• Bose Miko A
• Johnson James

Classifications

• G06F16/178 Primary

  Techniques for file synchronisation in file systems · CPC title

• G06F17/30174 Primary

  Physics · mapped topic