evaluating the possibilities of SmugMug API
syntern
Registered Users Posts: 10 Big grins
Hi,
I've started to go online with my photo catalogs, and in the end I've concluded two options. #1: create a custom application that suites my needs or #2 adapt my requirements to SmugMug's possibilities and features, and use the API to fine-grain my use of it. In this thread I'll describe my workflow and related requirements, could you please help me to mark what is possible with SmugMug and what is not?
I edit my photos with Lightroom, keywords, description, everything. As I'm not native English, I use an extended content field that looks something like this:
I have a working implementation of the above script (which does even more: resizing, watermarking, etc). Now, my desire is to create a site that has photo urls like this:
example.com/en/[short prefix something]/first-line-is-the-english-title-for-the-photo/[any postfix or id]
example.com/hu/[short prefix something]/valami-magyar-leiras-jon/[any postfix or id]
Of course, variations may apply, but in general terms, I want the language code in the first part of the url, and a separate friendly url for each photo, and the localized text for each version. On the other hand, for each keyword, I'd like to create a "smart gallery" that contains the pictures that have the specified keyword...
So far I have seen only a few bits from SmugMug API, and I might be missing something, but my strong suspicion is that the above requirements are not really possible to match at the moment. Is this a correct assessment?
I've started to go online with my photo catalogs, and in the end I've concluded two options. #1: create a custom application that suites my needs or #2 adapt my requirements to SmugMug's possibilities and features, and use the API to fine-grain my use of it. In this thread I'll describe my workflow and related requirements, could you please help me to mark what is possible with SmugMug and what is not?
I edit my photos with Lightroom, keywords, description, everything. As I'm not native English, I use an extended content field that looks something like this:
First line is the English title for the photo Some description follows if there is any, in multiple lines.. #hu // now we change the lang to Hungarian Valami magyar leiras jon // something in Hungarian - that will be the title of the photo ...The same goes to the keywords, I use no-space keywords and I have a translation table that is automatically able to create Hungarian version of the keyword list. After I've done with my export, I run my script through the exported photos and with exiftool and custom processing I create an English and a Hungarian version of the descriptions. I even generate friendly urls from the title like, first-line-is-the-english-title-for-the-photo in the case above, and valami-magyar-leiras-jon in Hungarian.
I have a working implementation of the above script (which does even more: resizing, watermarking, etc). Now, my desire is to create a site that has photo urls like this:
example.com/en/[short prefix something]/first-line-is-the-english-title-for-the-photo/[any postfix or id]
example.com/hu/[short prefix something]/valami-magyar-leiras-jon/[any postfix or id]
Of course, variations may apply, but in general terms, I want the language code in the first part of the url, and a separate friendly url for each photo, and the localized text for each version. On the other hand, for each keyword, I'd like to create a "smart gallery" that contains the pictures that have the specified keyword...
So far I have seen only a few bits from SmugMug API, and I might be missing something, but my strong suspicion is that the above requirements are not really possible to match at the moment. Is this a correct assessment?
0
Comments
Want faster uploading? Vote for FTP!
http://translate.google.com/translate_tools
My Smugmug Site
Want faster uploading? Vote for FTP!