On 2015-03-23T12:53:19+1100, Mike Morris <[email protected]> said:
MM> Ditto. I'm fastidious about not only hierarchy, but file naming MM> conventions.
As am i! However, although i do prefer to slot files into a hierarchy, i regularly encounter situations where i can't find a document on my local filesystem, because the hierarchy location that seemed most appropriate to me at the time i filed it is not where my mind is at right now.
Artificial example: say there's a paper "The Philosophy of Mathematics". Initially i might have put it under a 'philosophy' folder, because it was part of a range of philosophy reading i was doing at the time. Now, however, my focus has moved to foundations of maths, and so i might expect to find it under a 'mathematics' folder.
So, as has been noted elsewhere in this thread, i've found that the 'best' ontology can change over time depending on circumstances. Hence my suggestion below.
MM> I've only fairly recently started using ownCloud, but would drop MM> it immediately if a hierarchical folder structure were not at MM> least an option (and consider dropping it if that were not the MM> default). In my application, volume alone would make a single MM> listing unusable.
MM> IMHO, the best compromise, for those whose brains work like MM> Christian's, is a search feature that
MM> (1) searches all folders, (2) returns a single list, and (3) MM> supports wildcards.
MM> That way searching for "*" gives the desired flat listing. But of MM> course those whose brains differ will likely have differing MM> opinions. (See Above :-)
Well, how about adding functionality to create, modify and delete 'virtual folders' whose contents are derived from metadata such as filenames, tags or dates? E.g. one could create a virtual folder based on the tags 'work' and 'project3' and a date filter 'accessed since 20150101', such that its contents would include all files matching those criteria.
(Note that i'm not necessarily suggesting that this /replace/ file hierarchies, but merely that it be available to /accompany/ them, or not, as users and contexts require.)
Alexis. _______________________________________________ User mailing list [email protected] http://mailman.owncloud.org/mailman/listinfo/user
