Question about the reports
Closed this issue · 2 comments
ze6killer commented
Hi,
Sorry, some more questions. This should be easier though.
As output of the script I can read the following:
...
Initial Found Files:[ 757]
- Bad Files:[ 7] = [ 750]
Note: some Bad files may no longer exist!
Photos count:
Local:[ 752]
Flickr:[ 6582]
Not in sets on Flickr:[ 410]
[32m[1369][2018.02.11 13:55:15]:[14886 ] [0m[PRINT ]:[uploadr] --------- (V2.6.7) End time: 2018.02.11 13:55:15 ---------
What does bad files mean please? :)
Thanks for all the good work!
Kind Regards,
Ze
oPromessa commented
Check the explanation for "badfiles" on "Usage Arguments".
Also discussed on issue #27.
Flickr "rejects" some files due to their type. So, instead of continuously attempting to load them on each run, the tool saves them and it bypasses them.
An upcoming version will also cater for "Error 8: File is too large" discussed on issue #37.
Anyhow you can:
- disable this control.check by not using the -b option.
- if you use -b option, you can, from time to time, "reset" and re-attempt to upload such files, you can use the "-c" option to cleanup such badflies.
Further notice on your example output:
- Local means locally found files on your drive and it should yield 750 in your example above, but this number may be off by 1 or 2. Still figuring it out to fix it.
- I've also noticed that the "Flickr" number reported by flickr as the number of pics found on flickr is sometimes off by 1. Can't do much here as this is the number returned by flickr itself.
- Finally "Not in sets on Flickr" indicates just that. It may indicate errors if it is bigger than 0, as all uploaded pics by uploadr should be on an Album. What I do normally, is to delete such pics from Flickr directly from the flickr/organize interface. But I've seen other users which have other tools uploading pics to Flickr to ignore this number.
ze6killer commented
Hi,
thanks for the explanationS. I'll follow on this other thread then to not mix things up too much.
Ze