It’s been exactly two months since the day my Desktop Picasa app stopped connecting to my Google account. The secret handshakes no longer worked. The known tricks for appending URLs were useless. Whether I was ready to or not, I had to move on.
I’m still trying to recover, but here’s more or less how things go now …
Perhaps a blessing in disguise, we were also preparing to leave for a few months of travel, where photos would certainly be taken and systems would certainly be tested.
Transitioning to a new system required a huge shift in thinking, mostly with respect to my online album sharing. Picasa Desktop had allowed me to organize into folders by date and location. (As frequent travellers, we mostly cared about photos at the “Where were we?” level of organization.) Then, within that structure, I could selectively choose which photos per album would be mirrored and available online for public viewing.
But, now that my local laptop folders couldn’t simply be mirrored through Picasa Desktop as Picasa Web Albums, I had to switch to thinking about creating actual online albums separate from thinking about the folders on my machine.
My basic workflow remains similar to the process described in my previous photo organization workflow post, with some notable changes now that Picasa Web Albums no longer exist.
What happens when I take a photo on my phone?
Here’s my step-by-step procedure for creating and maintaining my online photo albums in Google Photos. It’s still a work in progress, and has become a little more involved now that I have Joe contributing some of his photos to my albums, too.
1… Culling: I first use a Gallery app (built-in Gallery, or Piktures) to go through new photos taken and delete any obviously bad ones, or chose favourites among duplicates and discard the rest. I’ve learned that it’s a lot easier to manage photos on my device first, before they get uploaded to cloud services. And, the fewer there are, the easier it is to manage them!
2… Google Photos manual backup only: I have decided to disable Google Photos’ auto backup, although I do regularly back up all my photos there. One reason to do so is that opening up Photos will show you a cloud with a line through it symbol for all the new photos that have not yet been uploaded, and this is very helpful for knowing which photos have/haven’t been organized yet. Because I want all my uploaded photos to end up in at least one album (further explained below), not just in the big shoe box that is the uploaded stream of photos, I can see at a glance which photos I haven’t yet placed in an album.
3… Add to a public Google Photos albums directly From the “not yet backed up” photos, I select the ones I want to be in a publicly visible album (usually not all of them) and “upload to album” choosing my current, public album. For example, right now that album is “2016-09 Sweden” but next week, I’ll create “2016-10 Milan.” Note: You don’t have to back up photos first; you can simply “add to album” and, by virtue of the fact they’ve been uploaded to Google Photos, they are now, in fact, “backed up.”
4… Add to a private Google Photos album directly Now, I go back to my list of photos and some will still have the “not uploaded” cloud icon in and among the stream of photos. I select ALL photos from the starting point of the “not yet uploaded” photos (including the ones that I just added to a public album) and upload them to my current PRIVATE album (in this case, “Fall on the road”) to ensure that every photo is uploaded into at least one album. The photos shared publicly are only uploaded once, but they exist in two different albums.
5… DropBox auto upload: In the mean time, all my photos, at full size, are uploaded via DropBox auto camera upload. Dropbox is a sneaky little thing, and no matter how quickly I manage to delete a photo locally, it seems it always gets uploaded to Dropbox. But, unlike Google Photos, there isn’t a nice way to see which ones have or haven’t uploaded if you disable the automatic upload. Furthermore, these files will only end up on my local machine, and are not the ones used in public albums, so I don’t have to think about which ones exist where. So, although it means I do have to go through these files separately and once again delete the ones I don’t want to keep, it seems to be the lesser evil of that or constantly disabling/enabling DropBox’s auto backup. This camera uploads folder is linked to my laptop, and eventually, these photos will show up as local files on my machine.
At this point, each photo exists on
- my phone’s microSD card (original file)
- DropBox (identical copy of file, renamed according to DropBox’s convention)
- Google Photos (as a “high quality” copy)
Organizing Local Photos on my Machine
- Move the files from DropBox “Camera Uploads” folder into a local folder named for the current place and time, deleting any photos I don’t want to keep. Since we travel fairly regularly, all of my folders are of the format “2016-10-03 Milan” (using the starting date of the trip). If we’re home for a while, then a folder would be named something like “2016-04-11 Spring in Summerside” and would be the “current folder” until either the season changed, or an event occurred.
- Rename files (I use A Better Finder Rename 10) for easier identification. I struggled a long time with file names, because I want them to be meaningful independent of any application. If I send files to friends and family, I want them to be identifiable. I eventually decided on the naming convention: YYYY-MM-DD hh.mm.ss PlaceOrEvent-001
- The date/time stamp follows the same convention DropBox does and makes it easy to identify photos in chronological order, and to identify when they occured.
- Using seconds usually is enough to make each photo’s timestamp unique. If some photos were taken in rapid succession, I manually edit the seconds so that the photos are still chronological, but each with a unique name.
- Using text for a place or event name makes for easier searching and “reading” of file names. Most of the time, this text is a city name, and identifies a photo as being from a particular trip. But, it could be a conference, concert, tournament or other event. This is helpful in finding a photo that I know was taken in Munich, but I don’t know on which specific trip to Munich it was taken.
- I tried to live without sequence numbers, but I’ve realized that if I want to select or use a photo from an album, it’s much easier to pick out and remember photo number 237 from the list of files rather than selecting from an hh:mm:ss identifier. So, the timestamp is for ensuring the pictures can sort chronologically, but the sequence number at the end is for actually identifying individual photos from the album.
- Backup folders to the home NAS. Our NAS has an identical copy of the “Pictures” directory on my laptop. This isn’t a sync, but a one-way copy. Typically, once a photos folder has been processed (created, files renamed) on my laptop, there are no changes to it, and it can then be copied over and archived on our NAS.
- Backup my Mac using SuperDuper to create a bootable backup on an external hard drive.
Now, I have the original DropBox copy of the photo on my machine, a backup on the home NAS and a backup on an external hard drive. This is in addtion to the original file still on my phone.
(Note: Since I have shared access to Joe’s Camera Uploads folder on DropBox, I also include any of Joe’s cell phone photos in my local photos.)
Viewing and Sharing my photos
Google Photos is my primary photo sharing tool. Most of my family uses Android, so they all have Google accounts and this is the easiest way for family to keep up with our travel photos.
Albums intended to be public
- are shared with individual family members so that they receive notification that the album has been created, and whenever new photos are added to the album. Sharing settings are further refined depending on whether I want others to be able to add photos to the album or be able to comment on photos.
- are shared to one of my Google Plus “Collections” that are visible from my Google Plus profile. Currently, I have different collections for Family photos, Travel photos, my Nature photos (I take a lot of bird pics with my ultra super zoom camera) and Bowling photos from Joe’s various tournaments and competitions. This is my attempt at creating my own Photo Gallery pages, since Google Photos does not currently offer a generic landing page where people can see all of your public albums. This way, anyone can view all my public albums, even if I haven’t shared anything with them personally.
Albums intended to be private
- are created as private (unshared) albums. All items created in Google Photos are private by default.
- are created in order to work with my third-party Picasa apps. Back when Google used Picasa Web Albums as its online photo system, there was no “photo stream” or “photo archive” - only albums. Every photo in PWA was in an album. When Google started to offer mobile photo backups, it created several (annoying!) auto backup folders, sometimes several each day because every photo had to be in an an album. So, all of the older apps created to view and manage Picasa folders operate on the assumption that all photos exist in albums. In order to keep using those mobile apps (which are more full-featured than Google Photos currently is) to view and manage my photos, I need to organize every photo into in album, whether I intent to share it or not.
Integrating Photos Taken on my Camera
In order to give me some extra uploading and editing flexibility, I use a micro SD card in an SD adaptor in my Nikon Coolpix P900 camera. This means that I can insert the card directly into my Samsung Galaxy Note tablet’s micro SD card slot and access my camera photos as if they were taken on a mobile phone. Then, I can upload to Google Photos in the same way I would from my phone. If I wanted to, I could also have these photos upload to DropBox and then process them on my laptop by moving them out of my Camera Uploads folder into local folders, renaming them in the process.
But, Nikon’s importing software for Mac OS is actually pretty nice. After initial set up, it’s essentially a one-click import, rename and choose destination folder. And, especially if I’m somewhere with poor network speeds or connectivity, then uploading to DropBox simply to redownload from DropBox can be painfully slow. So, lately I have tended instead to import my camera photos directly to a folder watched by the Google Photos Uploader for Mac. Once the photos in that folder have uploaded, I move them into the appropriate local folder in my “Pictures” directory.
In both cases, I can fully integrate my camera photos with my mobile phone photos both online in Google Photos and locally in my file system.
Synching All Photos Locally on my Mobile Devices
The final step is to make all (and, I do mean all) my photos available for offline viewing on my phone. This is where my third-party Android apps, and consequently, all the extra albums in Google Photos, come into play.
The app Picasa Tool (now called “Tool for Google Photos”) is an exceptionally reliable offline sync for previously Picasa, now Google Photos albums. This app has downloaded tens of thousands of photos in hundreds of albums without fail, and all are available to view offline. Not only can I then view my entire photo collection without using any data, but also I have access to these photos when I’m offline. Picasa Tool downloads and stores low res versions of the photos, but they are perfectly fine for viewing and looking up past events.
My system is similar to my old system, except that now I think of, and manage, my online photos completely separately from my local photos:
Now, there is no direct link between the primary copy of photos on my laptop and my online albums. My online system is my online system, and separately, copies of the original files are stored locally on my machine, and the NAS.
With credit/thanks/apologies to Tim Minchin:
This is my photo management system
And it’s fine
It’s where I spend a vast majority of my time
It’s not perfect, but it’s mine
~ Tim Minchin, “Not Perfect”