implements the proposed funtionality and further allows to write and add your own handlers for future file formats.
is aware of the content, starting with the basics such as the MIME-type, and all kinds of additional metadata which are either extracted from internal -handlers or are manually added by you, e.g. such as tags, keywords, or ratings.
Instead using countless programs handling a particular content, which scans the filesystem for updates, create previews, know about the content and make it available,is aware of many file formats and therefore the content; and if you want a new format covered, write your own handler to extract metadata automatically.
Because most immanent metadata is indexed so a reverse lookup is fast, e.g. filename, modification time, keywords, tags, file size, MIME-type, and also the full text of the content is indexed, so one can look for words, and gets a list of all files which contain that word - instantly.
locatecan be used to find files based on filename, but that's about it
isn't a typical hierarchical filesystem as it has no topological constraints, and the hierarchical filesystem appearance is one view of many views of a dataset.
In this sense you can view a dataset based on metadata keys in many other ways:
Since you can freely add metadata by your own, you are also free to choose your own views on the dataset.
This way, it provides the flexibility and freedom of unordered data, and at the same time some tool to bring order into the metadata, to make it easier to query and create useful statistics.
The MetaFS Archive format (marc) is introduced which allows to archive and backup your metadata enriched data on any media outside of therealm - never again lose crucial metadata of your data.
FAQ).eventually should scale from single digit to hundreds of terabytes (see also
René K. Müller
November 2013, March 2015, last update March 2016