Skip to content

Commit 149d0ec

Browse files
Update README.md
1 parent 3026adb commit 149d0ec

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

README.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,15 @@
11
# Curator
22

3-
The curator is a file sorting automation daemon. It is meant to serve as a **part** of a comprehensive data management solution.
3+
On the surface this project is a high performance small media deduplicator. Able to spot duplicates against a collection of hundreds of thousands in a fraction of a second without the need to keep meta-data files separate to your data.
4+
5+
Dig deeper and the project reveals itself for what it actually is. A different way to use your file system, perhaps to its full potential. To this end, we ask "what if we treated files as more than just a blob of data identified by its path?". What if instead of paths, files are identified by any number of arbitrary meta-data? Which at a whim, may be used to create whatever directory structure one's workflow requires, based on rules instead of manual intervention? Similar to how SQL databases creates materialized views, optimal to a particualr workflow.
6+
7+
To this end, the program maintains a `mono-collection`. A centralized location that serves as the authority of data and metadata for all the files it manages. Then based on rules and meta data, the service selects files and links them to other locations in your filesystem creating directory structures that suits a particular workflow.
8+
9+
Under this vision
10+
* Directory structure no longer needs to be planned out beforehand.
11+
* Rule based file sorting produces fewer placement inconsistencies than its manual counterpart.
12+
* If directory structure requirements change, or more than one directory structure is required, all that's required is to change a rule and the daemon take care of the rest.
413

514
## What's in the box
615

0 commit comments

Comments
 (0)