Worfklow suggestions for keeping Photos in sync across multiple devices, without 3rd-party services?

I take photos with both my Android smartphone and a fullblown DLSR.

I manage photos – organize, rename, rotate, etc. – on my Opensuse box with KDE’s Gwenview, and on my phone with Pixie Reef’s “Fishbowl” Photo Gallery (https://market.android.com/details?id=com.littlefatfish.photo&hl=en).

I’m interested in your ideas about ways to keep everything in sync – without using 3rd-party online services (No Picases, Flickr, Smugmug, etc).

What needs to be kept in sync, somehow, includes:

The photos themsleves.
Their organization among, and order in, various ‘albums’.
Photo & filesystem metadata – timestamps, filenames, EXIF data.
PhotoApplication-specific data

recognizing that at any time a change may be made on either device.

rsync is a possibility, but once photos move into different dirs, it’d get messy.

What workflow can I use to do this?

Do I need a central server in the mix? If not using the 3rd-party services, is OwnCloud my best/only choice – assuming that after each (group of)change(s) on each device I manage to sync with it?

check out unison, rsync but with bi-directional syncing.

On Fri, 02 Sep 2011 23:06:03 +0000, ip15 wrote:

> Do I need a central server in the mix? If not using the 3rd-party
> services, is OwnCloud my best/only choice – assuming that after each
> (group of)change(s) on each device I manage to sync with it?

If you’ve got multiple devices and platforms, I’d suggest a central
server of some sort - whether that’s your desktop PC or a service like
Dropbox/Spideroak/etc.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

The central-server seems to be a requirement; peer-to-multiple-peer solutions just aren’t there yet.

That central-server needs some ‘awareness’ of photo organization & data, I think. Either built-in or something I ‘teach’ it.

Time-stamp mods for certain. State of rotation, EXIF data, folder hierarchy, etc. are almost-not-quite-must-haves.

in Mac+iOS-land, iTunes local+online solves the problem completely.

Using, e.g., PicasaWeb + Picasa-aware clients might be workable. But I’d really prefer NOT to have my data in someonee else’s hands. So a hosted (local or remote doesn’t matter to me) server is my req’t.

It’s the capabilities I’m unclear about.

On Sat, 03 Sep 2011 02:16:02 +0000, ip15 wrote:

> The central-server seems to be a requirement; peer-to-multiple-peer
> solutions just aren’t there yet.
>
> That central-server needs some ‘awareness’ of photo organization & data,
> I think. Either built-in or something I ‘teach’ it.
>
> Time-stamp mods for certain. State of rotation, EXIF data, folder
> hierarchy, etc. are almost-not-quite-must-haves.

I think you might be overthinking this - photos are files, and the
applications can handle parsing the metadata - the underlying challenge
is getting the data replicated.

Either that, or providing remote access to centrally-stored data
regardless of platform.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

> I think you might be overthinking this - photos are files, and the
> applications can handle parsing the metadata - the underlying challenge
> is getting the data replicated.

Overthinking’s possible …

Ok, simple file replication is easy enough to handle; a good reminder. So moving photo albums (dirs) & files around, the replication handles that. Just have to get the source and target trees correct.

I’m realizing that I’m worrying really about a different issue (is it?).

Llet’s say I change PhotoA’s display orientation (landscape → portrait) on the Phone, as displayed in its photo app, can the metadata be “passed AND translated” – either peer-to-peer, or through ‘my’ central server – to my desktop box so PhotoA appears in the desktop photo app’s display ALSO re-oriented?

I’m guessing unless the metadata is standard enough – or identical like in the iTunes case – that’s not gonna work.

On Sat, 03 Sep 2011 05:06:02 +0000, ip15 wrote:

>> I think you might be overthinking this - photos are files, and the
>> applications can handle parsing the metadata - the underlying
> challenge
>> is getting the data replicated.
>
> Overthinking’s possible …
>
> Ok, simple file replication is easy enough to handle; a good reminder.
> So moving photo albums (dirs) & files around, the replication handles
> that. Just have to get the source and target trees correct.
>
> I’m realizing that I’m worrying really about a different issue (is it?).
>
> Llet’s say I change PhotoA’s display orientation (landscape → portrait)
> on the Phone, as displayed in its photo app, can the metadata be “passed
> AND translated” – either peer-to-peer, or through ‘my’ central server
> – to my desktop box so PhotoA appears in the desktop photo app’s
> display ALSO re-oriented?
>
> I’m guessing unless the metadata is standard enough – or identical like
> in the iTunes case – that’s not gonna work.

If the metadata is part of the file, it would be replicated with the file
when it’s saved.

If it’s not part of the file, you’d need to sync the directory where that
data is stored as well - but a directory like that would be related to
the software used rather than the file itself.

So the question is this - if you rotate the image and save it, is the
metadata updated to reflect that (or in the case of an orientation
change, usually the file is saved with the orientation displayed on
screen - ie, if you were saving it in a raw format like TIFF, the
sequence of the data would represent the data going across the screen
rather than the orientation of the data in the file (not sure I’m
explaining that clearly enough).

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C