That sounds like an exciting project! We have some BrightSign hardware that was not fully deployed (before we had my position at this institution), so I'm looking into what we may be able to do with it now to get some more interactives or even digital signage into our rather static exhibition. I'm also familiar with you as Te Papa is a case study used by Dexibit. Welcome to the list!
*Jess Rezac* Director of Digital Engagement, American Jazz Museum Phone: (816) 474-5035 | Email: jre...@kcjazz.org <https://by2prd0712.outlook.com/owa/redir.aspx?C=vAZ7qMBJfk6LlzKo0XmWVR1XIPiqR9AI_1Ovbx5Rh35GlaDl_NBaWfi6eDlvO4zf3C9Jzk7sp2E.&URL=mailto%3ajrezac%40kcjazz.org> *Where it lives!* | Facebook <http://facebook.com/americanjazzmuseum> | Twitter <http://twitter.com/americanjazzkc> | Website <http://americanjazzmuseum.org> On Thu, Aug 10, 2017 at 6:00 PM, Richard Hulse <richard.hu...@tepapa.govt.nz > wrote: > Hi, > > I have just joined this list and thought I would briefly introduce myself, > and let you know what I am working on. > > I am a Digital Product Owner at Te Papa Tongarewa - The Museum of New > Zealand, where I started in Jan 2017. Prior to this I worked at Radio New > Zealand (NZ's public radio broadcaster) where I was in charge of digital > products (app and website) for 11 years. (Linked in: > https://nz.linkedin.com/in/richard-hulse-91383847) > > At Te Papa I am working on a stream of work called the Digital Experience > Delivery System (DEDS). > > This is a system to build and deploy digital experiences in a repeatable > way, and includes analytics and real-time active monitoring of the > application. > > At the technical core of the system is a custom player, built using > Electron. This communicates with our build system which packages each > interactive on-demand. Interactive are designed to run stand-alone > (networking is not required once running). > > For the UI we build these based on our Digital Language System ( > https://te-papa.github.io/), which is under continual development as we > conduct user testing and build more components. > > The interactives themselves are built using a set of ReactJS components > and a React-based starter kit that we've created in house. > > Our target hardware (at this stage) is the HP Mini, but simpler > interactives can also run on BrightSign (minus Electron), and presumably > Raspberry PI grade hardware. > Ultimately I'd like to get this to the point where it interactives are > hardware agnostic, subject to CPU requirements. > > The code is not public at this stage, but I am looking into that at the > moment. > > At this stage we are still in the development phase, but I'm happy to post > updates or answer questions here if there is interest. > > > Regards, > > Richard Hulse > Digital Product Owner > Te Papa Tongarewa, Museum of New Zealand > > > > > > > > > ____________________________________________________________ > __________________ > > This email has been filtered by SMX. > For more information visit http://smxemail.com > ____________________________________________________________ > __________________ > > > _______________________________________________ > You are currently subscribed to mcn-l, the listserv of the Museum Computer > Network (http://www.mcn.edu) > > To post to this list, send messages to: mcn-l@mcn.edu > > To unsubscribe or change mcn-l delivery options visit: > http://mcn.edu/mailman/listinfo/mcn-l > > The MCN-L archives can be found at: > http://www.mail-archive.com/mcn-l@mcn.edu/ > >
_______________________________________________ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
