Three ways to efficiently manage documents:
Folder/File Canonical Naming
Cloud disk synchronization backup
The combination of the above three methods can effectively help us achieve the following goals:
Naming by convention: categorize project files/personal documents for easy finding
Document version control: reduce the copying and backup of documents by yourself, automatically build key historical versions, even if they are deleted by mistake, they can be retrieved and restored to the document status of a certain historical node as required
Cloud Disk Synchronous Backup: Synchronous backup of important documents, and real-time backup immediately if there is any modification
We already know these three methods, how should we implement them?
Method 1: Folder/document specification naming
1. First make some rules for our naming
Our common version naming format is [name].xyz-[state]
name is an optional field, usually v, which means version
xyz is the serial number of each version, which follows the semantic version naming convention. Actually based on this specification, the name field should not appear before the version
state is an optional field, indicating the version status, for example, b indicates beta test version, other common statuses, which will b2b data be described in detail later
What are Semantic Versioning Naming Rules?
The core rules are as follows:
0.yz represents the development stage, everything may change at any time, not stable version.
1.0.0 defines this version as the initial
stable version, and all subsequent updates are modified based on this version.
The version status is as follows:
2. After understanding the naming rules, we can name the folders/documents commonly used in our workstations reasonably
For ongoing projects: do a good job in project classification, distinguish folders, and classify different project files
Outer folder name: iwork or project project
First-level folder name: date_project name Example: 2018_0115_project name
Secondary folder name: version_1.0 (do this secondary for important changes)
Three-level folder name: Arrange according to the work content
For completed projects: organize and name them in time, and put them in the Archive archive.
Naming: project name (project number)_version_start and end time
Example: Snail APP project_V1.0.1_2018/01/25-03/15
Snail APP project_V1.0.1_2018_01250315
As shown in the figure below, the folder names of each level are displayed, whether the corresponding project has a corresponding version, and if so, the corresponding version number can be added to the name.