Hello all, A common theme presented by museums are the islands of information that are created by computer systems for retail, admissions/ticketing, reservations, ecommerce, general food service etc.
There are two core ways to solve this problem: 1) Build interfaces between these systems to share information. These solutions are very time consuming and never quite work as advertised. 2) Getting a system that consolidates all of these functions together. A good whitepaper on the topic can be found at http://www.outboundsoftware.com/testcorn.html - The Corning Museum of Glass. I welcome your comments. Marc Jorrens Outbound Software -----Original Message----- From: mcn-l-bounces at mcn.edu [mailto:[email protected]] On Behalf Of Sweeting III, Floyd Sent: Thursday, February 07, 2008 8:27 AM To: Museum Computer Network Listserv Subject: Re: [MCN-L] Multiple member online accounts + growing onlineservices =1 big mess Here at the Frick we use Blackbaud Raiser's Edge and Patron's Edge for both membership and admissions ticketing and I know Blackbaud has an ecommerce solution (we do not use it). We use Yahoo for ecomm. and EmbARK for our CMS and Xinet for our DAM, Wordpress for our intranet, Filemaker for numerous internal databases. I have to say that we have not been happy with the Blackbaud products and I would also like to hear what others are using for various solutions. Floyd Sweeting III Head, Information Systems The Frick Collection ________________________________ From: [email protected] on behalf of Patrick Sent: Thu 2/7/2008 8:12 AM To: mcn-l at mcn.edu Subject: [MCN-L] Multiple member online accounts + growing online services =1 big mess Hi folks, Here's our situation (and I'll bet it is similar for many of you): Like everyone, we're trying to offer more of our services online. To date, we have an online ecommerce system (xcart) and an online hosted ticketing system (Gateway). We will soon have an online education registration system (Semtek) and are contemplating an online member portal (Raisers Edge). Each system is pretty much standalone so there is the potential for a given member to have 4 separate accounts, each with different account names, credentials, etc. You can see where the messiness comes in for our members and customers. My research so far has revealed solutions for managing more homogenous environments (such as internal employee user accounts) but nothing that can herd the member cats. Has anyone addressed this problem for cultural institutions and would like to share thoughts? All help appreciated. Thanks in advance, Patrick Clancy Director of Information Technology The New York Botanical Garden --------------------------------- Never miss a thing. Make Yahoo your homepage. _______________________________________________ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu <http://www.mcn.edu/> ) To post to this list, send messages to: mcn-l at mcn.edu To unsubscribe or change mcn-l delivery options visit: http://toronto.mediatrope.com/mailman/listinfo/mcn-l
