1 / 23

EMu on the Web Past, Present and Future

EMu on the Web Past, Present and Future. Alex Fell KE Software. Past. KE TexHTML. 1993-4 (ish). About the time the first browsers were developed. One of the first web interfaces to a database. Cutting edge for it's time. Became very complex over the course of it's lifetime.

duane
Download Presentation

EMu on the Web Past, Present and Future

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EMu on the WebPast, Present and Future Alex FellKE Software

  2. Past

  3. KE TexHTML • 1993-4 (ish). About the time the first browsers were developed. • One of the first web interfaces to a database. • Cutting edge for it's time. • Became very complex over the course of it's lifetime.

  4. KE TexHTML – Victoria Parliament

  5. Present

  6. Texxmlserver and PHP • Developed initially in 2001. • Aimed to simplify web development by using existing technologies (XML over HTTP and PHP). • “Standard Interface” customisable by the customer. • “Custom Interface” to allow more complex pages to be developed by KE Staff and external developers.

  7. “Standard” PHP Interface • Presents a configurable, catalogue-centric view. • Very quick to set up, so a collection can be on the web very soon after going live with EMu. • Limited amount of customisation available. • Common (shared) presentation layer makes extensive changes hard because all users of the standard interface may be affected.

  8. “Custom” PHP Interface • Page design and operation not at all defined. • Pages can be made to any brief, so no limit on design or functionality. • Because no design / layout work is done for you, pages take longer to produce and complex pages often require a developer. • Many of our older customers now use plenty of the custom interface as part of their sites.

  9. KE Mapper • Gives a spacial representation to the collection. • Plots items on a map. • Most easily applied to Natural History collection as locality information (lat / long etc.) comprises part of the collection information.

  10. KE Mapper

  11. Object Locator • Like the mapper, but displayes the current location of objects on a map of the museum. • Requires location records to be supplemented with spacial information, but uses existing location database.

  12. Object Locator

  13. KE Portal • Draws data from several separate databases. • Interface with many different databases (Texpress or otherwise) • GBIF, OAI, DiGiR, Darwin Core schemas supported. • In use at OZCAM, and of course, Manchester Museums Unwrapped.

  14. KE Portal – www.ozcam.gov.au

  15. KE Portal – Unwrapped

  16. Future

  17. PHP 5 • Opportunity to re-write “Standard” and “Custom” interfaces (and rename them)? • Break apart from the one-size-fits-all Standard Interface model? • Is ease of use balanced by extensibility in a shared code base? • What should happen to existing PHP 4 interface? • Backwards compatibility?

  18. JDBC • Working driver in development, in use with KE Vitalware • Better interface with database • Easier to use than PHP? • More transferable than PHP?

  19. Web 2.0?(what is it?)

  20. Community contributed information or narratives

  21. Narratives, descriptive keywords, opinions & comments(still narratives?)

  22. Issues • What gets contributed? • Does it require museum approval? • If so, how should this be presented to the museum? • If not, what's the worst that could happen? • Should it be stored in EMu?

  23. EMu on the WebPast, Present and Future

More Related