perkeep

History

Brad Fitzpatrick bafc53703d context: don't allow mutating an existing context's HTTP client Instead, require specifying it when constructing a new context. Prevents misuse and bugs / data races. Change-Id: I775e998bf69b9e238ec726c469494c1a65f8f9de		2014-07-02 14:34:24 -07:00
..
testdata	Rewrite Picasa importer for the new Importer API	2014-05-21 22:37:50 +02:00
README	…
picasa.go	picasa: fix compilation failure	2014-07-01 11:48:35 -07:00
picasa_test.go	context: don't allow mutating an existing context's HTTP client	2014-07-02 14:34:24 -07:00

README

Picasa Importer
===============

This is a working Camlistore importer for Picasa. So far it can import
all photos but not their metadata.

To use:

1) Retrieve an api credential from a project of you from
   https://console.developers.google.com/
   Select/create a project, then under APIs & auth / Credentials, create a new
   web application client id.

2a) Start the devcam server with picasakey flag:
    $ devcam server -verbose -picasakey='Client ID:Client secret'

2b) Place the Client ID and the Client secret in your (low-level) server-config.json:

    "/importer-picasa/": {
        "handler": "importer-picasa",
        "handlerArgs": {
            "apiKey": "Client ID:Client secret"
        }
    },

    and start your camlistore server.

3) Navigate to http://<server>/importer-picasa/start and authorize the app
   to manage your Photos.

4) Watch import progress on the command line (start devcam with -verbose flag).


TODO
----

  * The used OAuth2 scope is for managing (read & modify) photos, but this
    needs only read rights. Is a stricter scope available?
  * The album's author name is not used yet, and the album's short name is needed.
  * Picasa Web dumps a lot of metadata on us. Which would be usable?

See https://code.google.com/p/camlistore/issues/detail?id=391