1 / 19

Experiences with implementing EMu at the Australian Museum.

Experiences with implementing EMu at the Australian Museum. - Lance Wilkie (EMu Unit Manager). The Australian Museum. Databasing at the AM falls into two ‘eras’ – hard copy and digital. Collection databasing –1877 to mid 1990s. Hardcopy ‘Era’: Earliest Museum register in 1877.

etan
Download Presentation

Experiences with implementing EMu at the Australian Museum.

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. Experiences with implementing EMu at the Australian Museum. - Lance Wilkie (EMu Unit Manager).

  2. The Australian Museum

  3. Databasing at the AM falls into two ‘eras’ – hard copy and digital. Collection databasing –1877 to mid 1990s • Hardcopy ‘Era’: • Earliest Museum register in 1877. • Traditional registers – used till 2000 (or later) in some collections • Data sheets still used in some collections • Card files in use for over 20 years (still referred to infrequently)

  4. Digital ‘Era’: 1) Mid 1970s – batch loading of data into CSIRO Cyber 76 computer started 2) 1987 to 2001 – several ‘old’ servers used 3) 2001 – first EMu server purchased for an integrated collection management system. 4) 2002 – Collections database integration project commenced. Collection databasing –1970s to 2004 5) 2004 - SUN SunFire 280R server, 1.4 TB SAN, and tape robot purchased ~$400,000

  5. Australian Museum Texpress Databases • 1987 - data into KE Titan 2.0 • 1995 - data into KE Texpress 5.0.39 • Became the major repositories of Collections data. • 1987 - data into KE Titan 2.0 • 1987 - data into KE Titan 2.0 • 1995 - data into KE Texpress 5.0.39

  6. 2002 - ?: Australian Museum Texpress Databases to EMu

  7. Problem #1 - Customisation Who is going to change, and how much?

  8. Cetacea tab Measurements tab Ornithology 1 tab Mammals tab

  9. Problem #2 – User Level Permissions Who can do what?

  10. Past Present

  11. The Implications of Object-Based Databases Catalogue Parties

  12. Catalogue Parties Taxonomy Collection Events Sites

  13. Record Security Feature

  14. Discipline Tagging and Insert/Query Defaults

  15. Registry Renovation

  16. Problem #3 – Impacts on Collection Management Work Practices. Who will do it if I can’t?

  17. Finally….Some things we’d like to see: • The capability to copy values from one field to another using the global edit facility. • More connectivity between Sites, Collection Events and Catalogue modules – particularly an “Objects” field in Query mode for the former two? • A review of the Cerberus issue management facility – improved issue tracking

More Related