Status Update
Comments
rj...@gmail.com <rj...@gmail.com> #2
While I can understand (to some extent) why the API doesn't allow deleting of photos, modification of albums (old and new) should be safe enough.
ri...@gmail.com <ri...@gmail.com> #3
jf...@google.com <jf...@google.com> #4
At the moment the API has been designed around the upload/connect/share use cases as outlined in our documentation:
Please 'star' this issue to indicate your interest in this functionality, this will help us prioritize this feature in the future.
rd...@gmail.com <rd...@gmail.com> #5
dn...@gmail.com <dn...@gmail.com> #6
to which developer sends an album id and an array of mediaItem ids, etc.
Considering that backup & sync is fast and automatic, the use-case cited at <jf...@google.com>'s comment (dated Jul 30 2018) is pretty-much obsolete.
Why would User want to explicitly upload photos when backup & sync does it automatically, with no effort?
The use-case this issue requests is much more valuable, both to developers and end-users; and it is easy to implement:
it's practically the same as POST
bp...@gmail.com <bp...@gmail.com> #7
ru...@gmail.com <ru...@gmail.com> #8
ed...@gmail.com <ed...@gmail.com> #9
ph...@darrenm.net <ph...@darrenm.net> #10
ek...@myzoss.com <ek...@myzoss.com> #11
rw...@gmail.com <rw...@gmail.com> #12
ma...@gmail.com <ma...@gmail.com> #13
wo...@wooh.hu <wo...@wooh.hu> #14
btw how to 'star' an issue?
na...@gmail.com <na...@gmail.com> #15
an...@gmail.com <an...@gmail.com> #16
gi...@gmail.com <gi...@gmail.com> #17
I just implemented a downloader for my photos/albums and it was pretty smooth. Intended to write an uploader and came across this. This is a significant limitation.
dn...@gmail.com <dn...@gmail.com> #18
It has been in the queue since June, 2018.
Does this mean it starts all over again?
bu...@gmail.com <bu...@gmail.com> #19
ar...@gmail.com <ar...@gmail.com> #20
gi...@gmail.com <gi...@gmail.com> #21
re...@gmail.com <re...@gmail.com> #22
When we could get updates on this feature request?
rd...@gmail.com <rd...@gmail.com> #23
ce...@gmail.com <ce...@gmail.com> #24
ho...@gmail.com <ho...@gmail.com> #25
jj...@gmail.com <jj...@gmail.com> #26
om...@gmail.com <om...@gmail.com> #27
rt...@gmail.com <rt...@gmail.com> #28
al...@gmail.com <al...@gmail.com> #29
mh...@gmail.com <mh...@gmail.com> #30
sl...@gmail.com <sl...@gmail.com> #31
Why did you close picasa api?
de...@gmail.com <de...@gmail.com> #32
jo...@gmail.com <jo...@gmail.com> #33
ke...@gmail.com <ke...@gmail.com> #34
But currently I have to add videos to that shared album manually...like an animal. Ugh. I reviewed the API, and saw that I could poll and check for new photos within a timeframe...great! One of the attributes I can see about a new photo is the filename, and the Blink camera autogenerates a filename that is easy identifiable; all I would have to do is check for that pattern, and if it's in the new filelist, add that (already uploaded and sync'd!) video to the shared album. Except, of course...I can't do that.
So instead of just sticking a cron job on one of my VPNs to check for new videos once an hour, it looks like I currently need to *write an Android app* to do this. I'll have to take the Blink video directory *out* of automatic upload, then write an app for the sole purpose of doing what Google Photos already does for me, with the added ability to put the videos in an album. This does not seem like a sensible way to the finish line, although at this point I am seriously considering it (which kind of blows my mind).
Does this make sense at all? This is but one of many use-cases that could be *drastically* simplified if we could just put a media item (photo or video) that is *already* in Photos (via the automagic of Google Photos upload) into a new album!
ab...@gmail.com <ab...@gmail.com> #35
mr...@gmail.com <mr...@gmail.com> #36
[Deleted User] <[Deleted User]> #37
so...@gmail.com <so...@gmail.com> #38
be...@gmail.com <be...@gmail.com> #39
tt...@chanzuckerberg.com <tt...@chanzuckerberg.com> #40
fi...@algures.net <fi...@algures.net> #41
ke...@gmail.com <ke...@gmail.com> #42
ed...@gmail.com <ed...@gmail.com> #43
an...@gmail.com <an...@gmail.com> #44
ag...@gmail.com <ag...@gmail.com> #45
de...@gmail.com <de...@gmail.com> #46
jf...@google.com <jf...@google.com> #47
The latest release of the Google Photos Library API includes two new calls: `albums.batchAddMediaItems` and `albums.batchRemoveMediaItems`. With these calls you can add (and remove) media items that you have uploaded to albums that your application has created.
You can find out more in the release notes (
ma...@gmail.com <ma...@gmail.com> #48
I believe the majority of people here want to organize media items *not* uploaded by their app, i.e. uploaded by the photos app on the phone.
I'm sure many will be disappointed, but for clarity the docs clearly state:
"Note that you can only add media items that have been uploaded by your application to albums that your application has created."
mp...@gmail.com <mp...@gmail.com> #49
ke...@gmail.com <ke...@gmail.com> #50
rj...@gmail.com <rj...@gmail.com> #51
"... to organize the existing photo library as Albums without having to upload new media. For example, I have several hundred gigabytes of photos that i don't want to download to re-upload to put into an Album."
The methods provided in the "fix" do not address this problem.
This should be re-opened or Changed to "Won't Fix" (which I suspect is the real case...)
sa...@gmail.com <sa...@gmail.com> #52
I was not lazy and got to the google.photos team and got the answer that this task was included in the roadmap. And now it turns out that this was the wrong information. Perhaps they simply did not hear me or (something "as always" in your Corporation оf Good) -- the added methods in principle already existed before (when adding an album).
Do we need to create a new request and transfer all our stars to it? Don't be evil, please.
ma...@gmail.com <ma...@gmail.com> #53
Note that I can already list and view the existing photos in my existing albums (even if they weren't uploaded by my app).
Why do batchAddMediaItems and batchRemoveMediaItems only allow access to photos and albums created by my app? Is there a particular security concern here? If not, it should only take a few minutes for a developer to take out these silly security checks.
da...@gmail.com <da...@gmail.com> #54
mp...@gmail.com <mp...@gmail.com> #55
ma...@gmail.com <ma...@gmail.com> #57
ak...@gmail.com <ak...@gmail.com> #58
"These new APIs are good in their own right, however they don't address the core issue outlined here.
I believe the majority of people here want to organize media items *not* uploaded by their app, i.e. uploaded by the photos app on the phone."
exactly and this is still not possible... these items can only be viewed from API and nothing more :(
dj...@gmail.com <dj...@gmail.com> #59
de...@gmail.com <de...@gmail.com> #60
mi...@gmail.com <mi...@gmail.com> #61
ba...@gmail.com <ba...@gmail.com> #62
xu...@gmail.com <xu...@gmail.com> #63
jp...@gmail.com <jp...@gmail.com> #64
ru...@gmail.com <ru...@gmail.com> #65
no...@gmail.com <no...@gmail.com> #66
lu...@gmail.com <lu...@gmail.com> #67
ra...@rr7.com <ra...@rr7.com> #68
ri...@rilhia.com <ri...@rilhia.com> #69
fi...@gmail.com <fi...@gmail.com> #70
ke...@gmail.com <ke...@gmail.com> #71
This is a massive disappointment to find. I've been uploading security cam screenshots to google photos and just want them to move into an album after a day. The upload app cant upload to a specific album and the photos api can't move them.
ni...@gmail.com <ni...@gmail.com> #72
Marking it fixed is almost a showcase of their ignorance. It's Google.
li...@gmail.com <li...@gmail.com> #73
ol...@gmail.com <ol...@gmail.com> #74
lj...@gmail.com <lj...@gmail.com> #75
ts...@gmail.com <ts...@gmail.com> #76
ab...@gmail.com <ab...@gmail.com> #77
rr...@gmail.com <rr...@gmail.com> #78
al...@gmail.com <al...@gmail.com> #79
ca...@gmail.com <ca...@gmail.com> #80
an...@angadsingh.in <an...@angadsingh.in> #81
sp...@gmail.com <sp...@gmail.com> #82
th...@gmail.com <th...@gmail.com> #83
th...@gmail.com <th...@gmail.com> #84
ni...@gmail.com <ni...@gmail.com> #85
sa...@udemy.com <sa...@udemy.com> #86
js...@gmail.com <js...@gmail.com> #87
ri...@gmail.com <ri...@gmail.com> #88
ar...@gmail.com <ar...@gmail.com> #89
do...@amon.cc <do...@amon.cc> #90
na...@gmail.com <na...@gmail.com> #91
+1
ba...@gmail.com <ba...@gmail.com> #92
so...@gmail.com <so...@gmail.com> #93
hi...@gmail.com <hi...@gmail.com> #94
hu...@gmail.com <hu...@gmail.com> #95
How can you seriously pretend to even have anything remotely close to an API without such basic functionality? This is not an API but an overly complex and completely useless pile of crap.
I have just spent hours wiring the basics of a webapp that was going to allow my family members to easily arrange their own photos into shared family albums, only to find out that, no sir, there is no way to actually build such a simple functionality because pictures automatically uploaded from a phone into google photos cannot be moved into albums by a 3rd party application.
What the actual fuck? What kind of moron came up with the limitations of this "API"? How little do you care about your users that not only you can't be bothered to build a halfway decent UX but you prevent any 3rd party from offering an alternative? Are you really trying to push people away from using your product?
ac...@gmail.com <ac...@gmail.com> #96
ac...@gmail.com <ac...@gmail.com> #97
sc...@gmail.com <sc...@gmail.com> #98
Organize existing MediaItems (photos/videos) into albums using Photos Library API
Feature Request: add ability to add a photo to an album
Allow to change metadata of any mediaItem
j....@gmail.com <j....@gmail.com> #99
At the very least, make this restriction absolutely clear in the docs. I've overlooked this and spent way to long building a script to organize my fotos only to realize that it won't work.
Description
The purpose of this feature would be to organize the existing photo library as Albums without having to upload new media. For example, I have several hundred gigabytes of photos that i don't want to download to re-upload to put into an Album.