I've been looking at the Flicker API and was interested in finding geocoded images and have used a couple of their API methods.
Is there a way to expand out the attached xml information if the API request is not an original connection? I have created multiple dynamic links which is derived from one API request which fetches a set of images id and then creates 10+ new API requests specifically querying information for each ID. I am able to retrieve the xml output for each link but now have to process out these xml objects' information. Is it possible to expand these out using scripts or to create an expand xml operation block to do it within Omniscope?
I've also encountered similar issues with JSON data formats and haven't really figured out the best way to deal with these types of data. The discussion on scripting and php deserialization is along the same lines but the example Omniscope file doesn't seem to be working:
For the flickr scenario you could use a 'Batch append links' merging feed to convert the XML. We are aware of a bug with this feed and XML docs which will prevent you using this particular approach but I will try and get a fix in for you tomorrow.
The basic approach is to try and use the existing XML Mapping functionality to convert the flickr data but also to do it as a batch process.
This would save you having to write/adapt a custom script.
As of tomorrow's 2.8 build you will be able to extract Flickr data via DataManager using XML mappings.
The workflow uses an additional XML mapping to download the details of each individual search result and then parse them into a tabular format. When configuring a mapping in a 'Batch append files' source or a 'Batch append links' merging feed then you will be prompted for a file to based the mapping on. Just enter one of the API URLs which is generated in your Field Organiser.
I have attached your IOK with a few modifications. The Flickr API key will probably need replaced with your own one in all the DM blocks.