Hi,

Right. This wasn't proscriptivist as much as an example of what happens
with gphoto2. It just reproduces the directory structure on the camera, so
my camera has that example structure.

What's nice about leaving up to the utility is that we don't have to
flatten or change where the files come from with rsync we ust recurse
through the folders, and pulling the jpegs using Gphoto2 and then are
rsyncc just faithfully reproduced structure
On Nov 12, 2013 6:12 PM, "kgf" <notifications@github.com> wrote:

> In README.md:
>
> > @@ -43,22 +43,50 @@ Basic Workflow
> >  * Repeat
> >  *
> >
> > -Sub workflow: Grabbing images from the camera
> > ----------------------------------------------
> > -* Consider use of gphoto2 (available from apt-get)
> > -  * sudo apt-get install gphoto2
> > +Data structures: File directories
> > +----------------------------
> > +* Base directory is off of user home directory
> > +* Base directory name, by default, is "autotransfer"
> > +* Subdirectories in autotransfer contain images from each pi, including the local one
> > +* Subdirectories are named using a scrubbed version of the ethernet mac address for every pi
> > +* Within each subdirectory, the image directory file structure from the camera will be reflected.
>
> I'm trying to think if there is value in splitting it up this far ? just
> thinking that
> /{{mac address}}
> /images
> /video
> may be enough. We would prioritize the images first, since they'll
> transfer sooner. Some images will be uploaded via a web interface. There
> could be multiple cameras attached. It could be a simple thumb drive...
>
> What do you think ?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/kgf/auto-transfer/pull/6/files#r7611272>
> .
>