|
December 03, 2009, 09:24 AM
|
|
what are some tools and techniques that we are going to need to migrate our photos to this site successfully?
|
| |
|
|
December 03, 2009, 09:32 AM
|
|
i think i'm going to give this application a shot, under windows emulation, unless gustavo has some better idea:
http://www.callingshotgun.net/about/migratr/
some things i'm looking out for:
http://www.23hq.com/striatic/a/settings
in settings, i want my uploads to be under a creative commons license, so i'm changing the default right away. this way i won't be forced to re-license on a photo by photo basis.
i'd also like to link my flickr photo descriptions to their counterpart images on 23hq. not sure how to do this yet - possibly manually.
geotagging is a bit more arcane here, although there are some interesting bonus features and api tools:
http://www.23hq.com/forums/message-view?message_id=5140848#message5143159
|
| |
|
|
December 03, 2009, 09:35 AM
|
|
also to consider - locking commenting on flickr photos, after linking to 23 counterparts. keep new comments in one place. not sure about this, but worth some thought.
|
| |
|
|
December 03, 2009, 09:38 AM
|
|
here is a 23hq compatible standalone uploader, for potential help with a less automated transfer strategy:
http://picturesync.net/
|
| |
|
December 03, 2009, 09:40 AM
|
|
Linking and locking manually is guaranteed pain.
The problem is that the relevant hack has to deal with authentication, which is also a pain.
|
| |
|
|
December 03, 2009, 09:42 AM
|
|
can be done over time. not incredibly urgent - just an idea.
|
| |
|
|
December 03, 2009, 09:08 PM
|
|
I guess the first question would be whether it makes sense to "migrate" things, as opposed to starting fresh.
|
| |
|
|
December 03, 2009, 09:12 PM
|
|
i'd rather be able to search my entire collection on one site, instead of across a couple.
|
| |
|
December 03, 2009, 10:27 PM
|
|
Does the license defaults here not apply to uploads with migratr?
|
| |
|
|
December 03, 2009, 10:33 PM
|
|
i'm assuming they do apply. but the default license is copyright.
|
| |
|
|
December 04, 2009, 01:57 AM
|
|
|
|
| |
|
Team 23
December 05, 2009, 02:04 AM
|
|
Migration is a tricky issue.
Migratr is usually the recommended option, but you're right (there's even a thread about it) that there are features missing and annoying downsides when it comes to transfering state. The url-based import method suggested here is pretty cool -- although, I wouldn't count on it to actually transfer 1000+ photos. Something is bound to go wrong somewhere in the process and handling errors cross-domain is a browser will cause trouble.
With migration, hacks are usually not the right approach. We have some code around to handle imports from flickr and I'd be happy to clean it up and actually have an easy, built-in option for moving onwards (and upwards...). It'd be a weeks or two before this tool would be available in either case, but let me know if you don't come up with a good migration option.
|
| |
|
|
December 05, 2009, 03:54 AM
|
|
"It'd be a weeks or two before this tool would be available in either case, but let me know if you don't come up with a good migration option."
i talked with the migratr developer over IM and he was very helpful and responsive, and said he plans to add this functionality eventually. however, i don't think he'll be able to fix these problems very quickly. i also felt bad making so many feature requests from free, non-ad supported software : [
waiting a couple of weeks to have a "non-hack", seamless migration solution would be great, and better than using greasemonkey or migratr.
you'd also be converting certain people to "plus" more quickly, given such a method. ; ]
|
| |
|
|
December 05, 2009, 04:06 AM
|
|
it would also be nice to make migration simple enough that anyone can do it with a couple of clicks.
even migratr [which makes things as simple as possible given its inherently complicated underlying nature] or an automated greasemoney script [which would allow proper sideloading] are way over the heads of most people, and definitely inconvenient.
|
| |
|
|
December 07, 2009, 06:38 AM
|
|
i'm assuming they do apply. but the default license is copyright.
Just read that. At account creation time yes (just like flickr), but did you not find the license selection in options? I believe they even try to offer Public Domain here. Although I'd prefer them adopt CCzero if they want to go that direction.
(just catching up here because about to try some migration tests).
|
| |
|
|
December 07, 2009, 06:41 AM
|
|
i found that immediately, yes.
|
| |
|
|
December 07, 2009, 06:41 AM
|
|
well, almost immediately. : ]
|
| |
|
|
December 07, 2009, 06:54 AM
|
|
oh sorry. I mis-skimmed that last time... thought you were having a problem with the default license, not you had solved the expected problem.
|
| |
|
|
February 17, 2010, 01:52 AM
|
|
so my flickr pro account lapses on march 2nd.
is flickr -> 23 migration going to be possible any time soon?
i'd rather not have to re-purchase my flickr pro account, because my archives would be on 23.
|
| |
|
February 17, 2010, 08:49 AM
|
|
I too am anxious to move my flickr photos here, before my flickr account expires
|
| |
|
|
Team 23
February 18, 2010, 07:42 AM
|
|
Hey guys -- I realize we got a little sidetracked on our end in building the transition tool. But it's certainly not forgotten.
|
| |
|
|
June 09, 2010, 05:08 AM
|
|
Well, my flickr pro expired. So much for that...
|
| |
|
|
June 09, 2010, 05:46 AM
|
|
|
|
| |
|
|
Team 23
June 09, 2010, 12:20 PM
|
|
I know guys... I've upped this in my inbox, but know that if should have been done a long time ago. The good news is that we've hired an extra developer at 23, which should at least get us somewhere.
|
| |
|
|
June 09, 2010, 08:32 PM
|
|
mine did too. a long time ago. whatever.
*sigh*
if you ever get around to doing this or run into problems with flickr, please let us know.
|
| |
