Hi Kevin
We are such a vendor, but avoided Bluetooth and instead built a
'private web' device using plain vanilla Web standards so that we can
be compatible with all web-browsing devices.
We incorporated a CMS (standard Drupal 7 with multi-lingual support in
our case) but have also been working on the concept of separating the
delivery platform from the content - effectively using our Info-Point
as a 'front end' to someone's 'back end' (that is not a euphemism).
We have, with the expert help of Richard Light, recently developed the
ability to network to a MODES collections server, and are interested
to do the same for other systems that have a significant number of
users, or to look at other ideas to avoid the content silos.
For small independent museums it is not a problem, but I can see the
point for the bigger collections - you don't want to be driven by the
hardware vendor's boundaries.
Regards
Neil Rathbone
www.info-point.eu
> All,
>
> we like many museums have been approached by commercial Ibeacon
> CMS/Hardware vendors - seems the cultural sector is next best placed after
> retail to make use of this kit. I know there have been some innovative uses
> on this tech in museums/galleries - my thought was more about the content
> authoring environment - most of the commercial offerings seem to have
> standalone CMS's - which create another content silo - what would be good
> would be a plugin into a generic CMS (Wordpress) and that can push content
> to the beacons - via a fixed template; in this way non tech dept. would be
> able to author content, dynamically -
>
>
> does anybody have any thoughts about this approach ?
>
> Cheers
>
> Kevin
>
> Kevin Carter
> Royal Museums Greenwich
> Technical Project Manager - Digital Media
****************************************************************
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/
****************************************************************
|