Hi Mike,
At the BFI our web team extract our Adlib data via API, although they are loading it to Drupal not Wordpress (I think quite a few organisations are loading Adlib data to Drupal for massaging it on the way to their web platform).
That has some benefits, eg it allows our web team to create an entity for each agent (in Adlib terminology, each person / institution), and load all work records into that agent entity. That enables a straightforward display of filmography, which is trickier to achieve with only an API call.
It also has some drawbacks, data management overheads are duplicated, etc.
RE your point about collections data sitting 'over there' rather than being woven in - have a look at our bfi website's Sight and Sound greatest films area, about the recent poll (which ousted Kane from number 1 for the first time since records began):
http://explore.bfi.org.uk/sightandsoundpolls/2012
Our Adlib data is woven into that area quite well, with hyperlinks to detailed view of filmographies records, enriching the user experience quite nicely, I think. All of those links and embedded pieces of data are targetting from the Drupal entities, but they could as easily work as live API calls, I think.
Stephen
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
|