mirror of https://github.com/perkeep/perkeep.git
2c05f1a3d9
And also speed up /importer/TYPE page's query by saying it's unsorted, which gets us a better index. Hacky workaround. Should fix it in the query planner later instead. Fixes #1105 Change-Id: I140ffb40456ec802844584568d2f1a7a38b26e41 |
||
---|---|---|
.. | ||
testdata | ||
README | ||
picasa.go | ||
picasa_test.go | ||
testdata.go |
README
Picasa Importer =============== This is a working Perkeep 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://perkeep.org/issue/391