Using eHive to create custom sites and applications 1924-5 NZ ‘Invincibles’ rugby team mascot, NZ Rugby Museum Paul Rowe V...
Paul Rowe Joint CEO, Vernon Systems Ltd Developers of collection management systems since 1985 http://www.flickr.com/photo...
Finding ways to tell your collections stories http://www.flickr.com/photos/46124960@N00/4322266394/
eHive Software as a Service CMS Collections management and online access to collections
Data storage platform <ul><li>Programming interfaces </li></ul><ul><li>Wordpress plugins </li></ul>http://www.flickr.com/p...
Staff in New Zealand, UK, and South Africa Focused on collections management software
<ul><li>600 museums worldwide </li></ul>
<ul><li>World’s first Software as a Service CMS </li></ul><ul><li>Launched in 2008 </li></ul>
A solution to common problems faced by small museums <ul><ul><li>Limited IT resources & budget </li></ul></ul><ul><ul><li>...
eHive collection management system <ul><li>Within eHive, each  contributor has their  own login to create and edit object ...
eHive web admin for collections management functions
eHive functions <ul><li>Object cataloguing </li></ul><ul><li>Acquisition tracking </li></ul>
Communities
<ul><li>Museum and collection info driven by eHive </li></ul><ul><li>Represents 400 museums </li></ul><ul><li>Collection r...
 
What’s an API and what’s it doing to my museum data? <ul><li>Application Programmable Interface </li></ul><ul><li>Websites...
Getting data in and out <ul><li>Bulk import via XML or spreadsheet </li></ul><ul><li>Export in text, Excel, PDF and XML fo...
 
Example eHive user Champs Chapel Museum of  East Hendred, UK
About the Trust, Museum and Village <ul><li>Small volunteer run organisation </li></ul><ul><li>Mixed collection </li></ul>...
East Hendred Museum on eHive <ul><li>Images and data converted in July 2009 </li></ul>
eHive forum and direct support http://www.flickr.com/photos/doctorow/2496308570/
Sharing data http://www.flickr.com/photos/ryanr/142455033/
Sharing data  <ul><li>Copyright issues </li></ul><ul><li>Less control of where your data ends up </li></ul><ul><li>eHive -...
<ul><li>eHive supports Creative Commons licences + other categories  </li></ul>
Current development <ul><li>Programming interfaces for  integration with other websites and products </li></ul><ul><li>Wor...
API <ul><li>RESTful </li></ul><ul><li>Returns JSON objects </li></ul><ul><li>Object, Account and Community API calls: </li...
OAUTH – allow access to content in eHive
One OAUTH key per app or site Wordpress site for your museum 3 rd  party application Regional website which harvest your d...
eHive and Wordpress <ul><li>Build your own museum website </li></ul><ul><li>100 million sites built in Wordpress </li></ul...
 
 
Plugins <ul><li>Add generic Wordpress widgets for contact forms, Flickr image feeds, embedded videos etc </li></ul><ul><li...
Old website that needed to be replaced
Key points for the DCGP Website is essential for data collection and publication Using eHive helped improve functionality ...
Built in 2001 No content management system (CMS), so background & project pages have remained static
Hard to navigate between the 3 different sections of the original website
Collection content needed to be preserved
Decision to move to eHive Update the website - add new caches and publications Fresh look New functionality – tagging, com...
Deliberately Concealed Garments Project (DCGP) new website
 
 
Tell your stories through Wordpress posts
 
 
 
 
Pages using the eHive plugins can include static content and eHive functions
Example of an eHive & Wordpress site with different theme
 
Why use software as a service? <ul><li>Simplifies public access </li></ul><ul><li>No need to buy servers or manage softwar...
eHive pricing
 
Find out more <ul><li>Paul Rowe </li></ul><ul><li>Vernon Systems </li></ul><ul><li>[email_address] </li></ul><ul><li>Twitt...
Upcoming SlideShare
Loading in …5
×

Using eHive to create custom sites and applications

1,863 views

Published on

Exhibitor briefing at Museums and the Web 2011, Philadelphia

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,863
On SlideShare
0
From Embeds
0
Number of Embeds
251
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Image: Nether Wallop Cache - waistcoat, stomacher, paper patterns
  • These are typical objects: Boot - most commonly found object is footware - Northampton Museum have concealed shoe index Bottle - quite a few bottles Stomacher - Nether Wallop Cache
  • Each contributor has their own private account with login access. Each object record with images can be marked as belonging to one or more communities. NZMuseums was marked as a default community for published objects records for each of the NZMuseums members.
  • A very positive and effective site. Image: Reigate Doublet - found in Reigate - iconic object Launched in 2001 it was innovative Webstats have proved, about 4000 visits It had a virtual collection of finds The website provided a means of data collection as well as dissemination (report a find on line) It provided a mechanism for finders to report finds via on the online report a find form - which was cutting edge at the time But by 2007 we wanted to bring the website up todate because it now seemed rather clunky
  • Now that we’re almost finished here’s a quick summarise: We decided to put repeat the image of the guinneapigs as the key point is to share information - it’s a carrot in this case Thanks: All the funders of the Deliberately Concealed Garments Project - noteably the Scaggs Foundation, the AHRC and the Textile Conservation Centre Foundation, KGB Internet for hosting the website since 2001 Thanks to the finders = who may well be in the audience
  • Talking websites here It was frustrating for Dinah in her academic role as she wasn’t able to add to the bibliography regularly - also to share the oral histories which is a hugely rich resource, accessibility ……
  • Three sections Static pages 2 database pages 3 ‘How to’ pages
  • All the content is there as a very rich resource - just needs to be added to and refresh the look
  • Five main reasons to update to eHive Update - using a CMS so we can update the website from anywhere with internet connection The website was looking dated, and the navigation wasn’t clear, well to me anyway CAPTCHA is the wiggly words and numbers which can be easily read by human and prevents standard automated software from filling out forms. For example, Paul Rowe - a personal touch is that he met me in London whilst over from New Zealand to discuss the website which gave me confidence in developing the website And now Zoe is going to tell you about eHive another example, not the Deliberately Concealed Garments Project
  • Now we’re back to the Deliberately Concealed Garments project - We wanted some continuity and modernisation, but keep a similar look and feel so repeat visitors feel confident and comfortable with site = we feel eHive understood our requirements immediately
  • This is key to the website - being able EASILY to tell us about what they’ve found. Trust has been established - very clear about people’s privacy Now back to Zoe
  • Using a lightbox mode - easy and quick to filter and pick what they want.
  • The policy was to call each cache by location - no names or address, just geographical location.
  • Example of the detailed object record
  • Using eHive to create custom sites and applications

    1. 1. Using eHive to create custom sites and applications 1924-5 NZ ‘Invincibles’ rugby team mascot, NZ Rugby Museum Paul Rowe Vernon Systems Museums and the Web Saturday 9 th April 2011 Philadelphia
    2. 2. Paul Rowe Joint CEO, Vernon Systems Ltd Developers of collection management systems since 1985 http://www.flickr.com/photos/wizzer/5358480666/
    3. 3. Finding ways to tell your collections stories http://www.flickr.com/photos/46124960@N00/4322266394/
    4. 4. eHive Software as a Service CMS Collections management and online access to collections
    5. 5. Data storage platform <ul><li>Programming interfaces </li></ul><ul><li>Wordpress plugins </li></ul>http://www.flickr.com/photos/waleedalzuhair/2492158122/
    6. 6. Staff in New Zealand, UK, and South Africa Focused on collections management software
    7. 7. <ul><li>600 museums worldwide </li></ul>
    8. 8. <ul><li>World’s first Software as a Service CMS </li></ul><ul><li>Launched in 2008 </li></ul>
    9. 9. A solution to common problems faced by small museums <ul><ul><li>Limited IT resources & budget </li></ul></ul><ul><ul><li>Complex software </li></ul></ul><ul><ul><li>Hard to publish to web </li></ul></ul><ul><ul><li>Run by volunteers who may want to contribute from home </li></ul></ul>http://www.flickr.com/photos/collinmel/1450793951/
    10. 10. eHive collection management system <ul><li>Within eHive, each contributor has their own login to create and edit object records and upload images </li></ul>
    11. 11. eHive web admin for collections management functions
    12. 12. eHive functions <ul><li>Object cataloguing </li></ul><ul><li>Acquisition tracking </li></ul>
    13. 13. Communities
    14. 14. <ul><li>Museum and collection info driven by eHive </li></ul><ul><li>Represents 400 museums </li></ul><ul><li>Collection records from 70 museums </li></ul>
    15. 16. What’s an API and what’s it doing to my museum data? <ul><li>Application Programmable Interface </li></ul><ul><li>Websites or applications can talk to each other </li></ul><ul><li>Data can be reused </li></ul>3 rd party website Selected collection records redisplayed with different presentation/context . . . . . API – “the telephone line” eHive Collection records . . . . .
    16. 17. Getting data in and out <ul><li>Bulk import via XML or spreadsheet </li></ul><ul><li>Export in text, Excel, PDF and XML formats </li></ul>
    17. 19. Example eHive user Champs Chapel Museum of East Hendred, UK
    18. 20. About the Trust, Museum and Village <ul><li>Small volunteer run organisation </li></ul><ul><li>Mixed collection </li></ul><ul><li>Replacing an existing image database </li></ul><ul><li>Needed to reduce costs </li></ul>
    19. 21. East Hendred Museum on eHive <ul><li>Images and data converted in July 2009 </li></ul>
    20. 22. eHive forum and direct support http://www.flickr.com/photos/doctorow/2496308570/
    21. 23. Sharing data http://www.flickr.com/photos/ryanr/142455033/
    22. 24. Sharing data <ul><li>Copyright issues </li></ul><ul><li>Less control of where your data ends up </li></ul><ul><li>eHive - 3 rd party search “opt-out” option </li></ul>
    23. 25. <ul><li>eHive supports Creative Commons licences + other categories </li></ul>
    24. 26. Current development <ul><li>Programming interfaces for integration with other websites and products </li></ul><ul><li>Wordpress plugins to enable eHive users to build their own museum websites </li></ul>
    25. 27. API <ul><li>RESTful </li></ul><ul><li>Returns JSON objects </li></ul><ul><li>Object, Account and Community API calls: </li></ul><ul><li>Get record by id or keyword search </li></ul><ul><li>Get recent, interesting or popular records </li></ul><ul><li>Get tags </li></ul><ul><li>Object specific API calls </li></ul><ul><li>Put (add) tags </li></ul><ul><li>Get/Put (add) comments </li></ul><ul><li>e.g. http://ehive.com/api/v1/objects?query=picasso </li></ul>
    26. 28. OAUTH – allow access to content in eHive
    27. 29. One OAUTH key per app or site Wordpress site for your museum 3 rd party application Regional website which harvest your data http://www.flickr.com/photos/xtinalamb/61688141/
    28. 30. eHive and Wordpress <ul><li>Build your own museum website </li></ul><ul><li>100 million sites built in Wordpress </li></ul>http://www.flickr.com/photos/koenvereeken/2088902012/
    29. 33. Plugins <ul><li>Add generic Wordpress widgets for contact forms, Flickr image feeds, embedded videos etc </li></ul><ul><li>Embed collection info from eHive </li></ul>http://www.flickr.com/photos/13942060@N00/87656563/
    30. 34. Old website that needed to be replaced
    31. 35. Key points for the DCGP Website is essential for data collection and publication Using eHive helped improve functionality and appearance
    32. 36. Built in 2001 No content management system (CMS), so background & project pages have remained static
    33. 37. Hard to navigate between the 3 different sections of the original website
    34. 38. Collection content needed to be preserved
    35. 39. Decision to move to eHive Update the website - add new caches and publications Fresh look New functionality – tagging, commenting, contact form Vernon Systems understands museums collections Price - very competitive and good value!
    36. 40. Deliberately Concealed Garments Project (DCGP) new website
    37. 43. Tell your stories through Wordpress posts
    38. 48. Pages using the eHive plugins can include static content and eHive functions
    39. 49. Example of an eHive & Wordpress site with different theme
    40. 51. Why use software as a service? <ul><li>Simplifies public access </li></ul><ul><li>No need to buy servers or manage software </li></ul><ul><li>Automatic backups & updates </li></ul><ul><li>Fewer compatibility issues </li></ul><ul><li>Access from anywhere with a web connection </li></ul><ul><li>Smaller ongoing costs, no initial purchase cost </li></ul>
    41. 52. eHive pricing
    42. 54. Find out more <ul><li>Paul Rowe </li></ul><ul><li>Vernon Systems </li></ul><ul><li>[email_address] </li></ul><ul><li>Twitter: armchair_caver </li></ul><ul><li>www.ehive.com </li></ul>

    ×