At the Carnegie Museum of Art, we’ve been looking into bypassing IMu and 
building and using the XML export feature, and building our API off those 
exports.  We don’t have a pressing need for realtime data in our API, and it 
means that the developers working on the API (i.e., me!) don’t need to be as 
intimately involved in the intricacies of EMu—it’s just an XML parsing problem. 
 It also means that there are no security issues, as least as far as writing 
goes—the API doesn’t have any access to the real database, so it is impossible 
to get to non-exported data or overwrite and live data.

We’re not sure that’s the best technique—we go back and forth on using IMu or 
continuing down this path.  We’d also be interested in any feedback or insights 
people might have.

David Newbury
(773) 547-2272

On Thu, Feb 12, 2015 at 6:50 PM, Adrian Kingston <>

> Hi all
> We're (Te Papa) finally looking to use IMu a bit more from our EMu. We're 
> thinking about a public facing API and a few more specialist uses. Does 
> anyone have any experience they can share on successfully/unsuccessfully 
> using IMu for external feeds/API etc?
> Cheers
> Adrian Kingston
> Digital Collections Senior Analyst
> Museum of New Zealand Te Papa Tongarewa
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Visit the Te Papa website
> The email message together with the accompanying attachments may be
> CONFIDENTIAL. If you have received this message in error, please notify
> immediately and 
> delete the original message. The views expressed in this message are 
> those of the individual sender, except where the sender specifically 
> states them to be views of Te Papa. Te Papa employs strict virus 
> checking measures and accepts no liability for any loss caused either
> directly or indirectly by a virus arising from the use of this message
> or any attached file.
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ______________________________________________________________________________
> This email has been filtered by SMX.
> For more information visit
> ______________________________________________________________________________
You are currently subscribed to mcn-l, the listserv of the Museum Computer 
Network (

To post to this list, send messages to:

To unsubscribe or change mcn-l delivery options visit:

The MCN-L archives can be found at:

Reply via email to