Difference between revisions of "Multi criterion file system"

From apm
Jump to: navigation, search
(just a very rough outline for now)
 
m
Line 3: Line 3:
 
A concept for a "file system" which allows to sort "folders" in multiple "super-folders" (no asymmetries)
 
A concept for a "file system" which allows to sort "folders" in multiple "super-folders" (no asymmetries)
  
{{todo|elaborate on the problems and opportunities}}
+
{{wikitodo|elaborate on the problems and opportunities}}
  
 
= The bad =
 
= The bad =
Line 13: Line 13:
 
=== Link embedding vs data embedding ===
 
=== Link embedding vs data embedding ===
  
* {{todo|use incscape and scribus as examples}}
+
* {{wikitodo|use incscape and scribus as examples}}
  
 
= The good =
 
= The good =
Line 21: Line 21:
 
* reconstructability of lost paths to files
 
* reconstructability of lost paths to files
  
{{todo|elaborate on "backward hierarchical multi project image preview."}}
+
{{wikitodo|elaborate on "backward hierarchical multi project image preview."}}
  
 
== Wikis ==
 
== Wikis ==

Revision as of 20:39, 12 July 2021

This article is a stub. It needs to be expanded.

A concept for a "file system" which allows to sort "folders" in multiple "super-folders" (no asymmetries)

(wiki-TODO: elaborate on the problems and opportunities)

The bad

The "solutions" that are none

File system links (soft and hard), Tags, Metadata, indexed search, ... are all hacks that only mend the symptoms of the core problem.

Link embedding vs data embedding

  • (wiki-TODO: use incscape and scribus as examples)

The good

  • same data in multiple projects – manumatic update distribution
  • Orthogonalized: locality management, importance management (backup degree), ...
  • reconstructability of lost paths to files

(wiki-TODO: elaborate on "backward hierarchical multi project image preview.")

Wikis

Wikis come closest to a solution but:

  • they don't integrate media well - no spontaneous scribble & free drag-and-drop like in linear note taking software
  • they are not fine grained enough - not for files.
  • they are not low level enough. They do not form a file system (proliferation of abstraction layers).

related