File naming: nested structure for short filenames should be rearranged

[jrsmith3]

Perhaps the nested structure for short filenames should more closely follow the structure for long filenames.

YYYYMMDD/experimenter/sample/experiment/HHMM.extension

In this way, its easier to simply copy this nested structure into data.

[jrsmith3]

Following on, the goal is to make the barrier for partial success low. Partial success is taking data on an instrument that is limited to 8-character filenames, properly saving that data in a nested directory structure, then getting that data into data.

Using the nested structure above, collisions are unlikely. Here's how I envision things happening: someone will take a bunch of data and save it using the nested structure described above. They are lazy, so instead of renaming the files into long filenames, they just copy their nested directory structure directly into data. Lets say there's a subdirectory in data called lazy_bum which is for collecting data in this nested structure. Every day that data is added, there will be two cases:

1. No one else has added nested directories to data/lazy_bum.
2. Someone has added nested directories to data/lazy_bum.

In case 1, A direct drag-and-drop of the entire nested structure is sufficient to avoid name collisions in data/lazy_bum.

In case 2, drag-and-drop will throw a warning. At this point, the user can simply drag-and-drop their experimenter subdirectory into the existing YYYYMMDD subdirectory.

[jrsmith3]

Alternatively, perhaps the best way to deal with this problem is for people to have a program that will convert nested directory structures to long filenames before any of the data gets near data.