Presentation is loading. Please wait.

Presentation is loading. Please wait.

Experiences with implementing EMu at the Australian Museum. - Lance Wilkie (EMu Unit Manager).

Similar presentations


Presentation on theme: "Experiences with implementing EMu at the Australian Museum. - Lance Wilkie (EMu Unit Manager)."— Presentation transcript:

1 Experiences with implementing EMu at the Australian Museum. - Lance Wilkie (EMu Unit Manager).

2 The Australian Museum

3

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

5 Collection databasing –1970s to 2004 5) 2004 - SUN SunFire 280R server, 1.4 TB SAN, and tape robot purchased ~$400,000 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.

6 Australian Museum Texpress Databases 1987 - data into KE Titan 2.0 1987 - data into KE Titan 2.0 1995 - data into KE Texpress 5.0.39 1995 - data into KE Texpress 5.0.39 Became the major repositories of Collections data. 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 1995 - data into KE Texpress 5.0.39

7 2002 - ?: Australian Museum Texpress Databases to EMu DisciplineOriginal DatabaseEMu DatabaseCurrent StatusApprox. # Catalogue records ArachnologyTexpress SpidersAMliveMerged and live93, 000 EntomologyTexpress EntomologyAMliveMerged and live122, 000 HerpetologyTexpress HerpetologyAMliveMerged and live164, 000 Marine InvertsTexpress Marine InvertsAMliveMerged and live167, 000 MammalsTexpress MammalogyAMliveMerged and live43, 000 MineralogyTexpress MineralogyAMliveMerged and live2, 000 OrnithologyTexpress OrnithologyAMliveMerged and live86, 500 PaleontologyTexpress PaleontologyPALliveLive, yet to be merged with AMlive25, 000 IcthyologyTexpress IcthyologyFISHliveLive, yet to be merged with AMlive175, 000 MalacologyTexpress MalacologyMALtestTest phase.452, 000 Anthropology?AMANTHliveLive, not merged with Natural History databases 74, 000 Still To Do: Total:1, 403, 500 MineralogyNon-texpress: Dbase, Excel Yet to be mapped and loaded?? Evolutionary Biology UnitTexpress EBU Yet to be mapped and loaded?? Collections Integrity UnitAREV Yet to be mapped and loaded?? Various disciplinesNon-texpress data formats eg. Access databases, Excel spreadsheets. Yet to be mapped and loaded??

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

9

10 Cetacea tab Mammals tab Ornithology 1 tab Measurements tab

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

12 Past Present

13 The Implications of Object-Based Databases Parties Catalogue

14 Parties Catalogue Collection Events Sites Taxonomy Field 1Field 2Field 3Field 4Field 5

15 Record Security Feature

16 Discipline Tagging and Insert/Query Defaults

17 Registry Category QueryDisplayInsertEditDeleteGlobal EditsRun ReportsDesign Reports Notes Admin No restrictions to access or permissions. Every registry group other than Admin is further subdivided by Disclipline (eg. BIRDCollectionManagement, MAMDataEntry etc). Temporary Editor Now includes permission to delete, edit and global edit for certain modules (excluding Catalogue). Access may or may not be restricted by Discipline (in first instance). NB. Temporary setting only - permissions removed when job complete!!! Collection Management Now includes permission to delete and edit for certain modules (excluding Catalogue). Access may or may not be restricted by Discipline (in first instance). Edit and Delete permissions for Collection Management restricted in a similar way to Data Entry groups. Data Entry Now includes permission to edit for certain modules only. Access restricted by Discipline. Editing permission for Data Entry groups confined to Catalogue, Bibliography, Loans, Locations and Parties modules. Previous group "Others" has been modified and merged into "Data Entry" groups. Read Only Access restricted by Discipline. (eg. Research scientists, etc.) Previous group "Research" has been combined with "Read Only" Read Only Vis For Visitors - they can view data, but can't take it with them without Coll Manager's permission. Admin Read Only Access not restricted by Discipline (eg. Spatial Systems Unit). Special Highly restricted access to approved users only (eg. secret and sacred artifacts). Registry Renovation

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

19 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


Download ppt "Experiences with implementing EMu at the Australian Museum. - Lance Wilkie (EMu Unit Manager)."

Similar presentations


Ads by Google