1 / 18

Major repositories using the Arctos database:

Arctos A multi-institution, multi-collection museum database http://arctos.database.museum http://code.google.com/p/arctos/. Major repositories using the Arctos database: (34 collections of specimens or observations, 1.3M records). in partnership with.

cedric
Download Presentation

Major repositories using the Arctos database:

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. ArctosA multi-institution, multi-collection museum databasehttp://arctos.database.museumhttp://code.google.com/p/arctos/

  2. Major repositories using the Arctos database: (34 collections of specimens or observations, 1.3M records)

  3. in partnership with TeraGrid – A nationwide network of 11 supercomputing facilities which is a member of which is sponsored by U. S. National Science Foundation’s Office of Cyberinfrastructure

  4. Arctos: A 15 year history • MVZ: 1995 - Hired Stan Blum to develop relational data model (following modeling by Assoc. Systematic Collections). • MVZ: 1997 - Hired John Wieczorek to implement model (desktop application) using Sybase and Versata. Partial implementation (e.g., no loans). • UAM: 1998-2000 - John W. migrated mammal data to Oracle, set up Versata. • UAM: 2002 - Dusty McDonald replaced Versata with ColdFusion, implemented full model (first web-based instance,aka Arctos). • MSB: 2003 – Joined Arctos at UAM (first multi-hosting instance). • MVZ and MCZ: 2005-2007 - Implemented separate instances of Arctos at Berkeley and Harvard (MVZ: first Postgres, then Oracle). • MVZ: 2009 - Moved hosting of data to Alaska (Virtual Private Database version).

  5. Arctos Specimen Catalog label data (and more) Arctos is an ongoing effort to integrate access to museum data, collection management tools, and external resources on the Web. Accessions Loans, usage Projects contribute and/or use specimens Citations Publications cite specimens The rest of Cyberspace GenBank Federated portals BerkeleyMapper “Media” in TeraGrid

  6. Arctos Philosphy • Maximize access to high quality information about collections on the web. • Integrate different kinds of information (specimen data, DNA sequences, media, etc.) into easily and visually retrievable records. • Facilitate management of data by curators and collection managers. Collaboration (development, curatorial) is key to success. • Show value of specimens for scientific research to the public through web resources.

  7. Breadth of Data in Arctos • Fish, amphibians, reptiles, mammals, birds and bird eggs/nests, plants, arthropods, fossils, molluscs • Specimens and observations • Media (images, audio) • Publications, fieldnotes Arctos constantly evolving to incorporate new kinds of data, e.g.,: • Better representation of non-publication documents (fieldnotes, correspondence) • Cultural collections (art, anthropology...) Nearly all that is known about an object (or observation) can be included in Arctos.

  8. Linking specimen records to archival documentation…

  9. Access and Security • Virtual Private Database (Row-Level Security) allows collections to maintain control over data while sharing certain nodes (taxonomy, agents, geography). • Access to data is controlled by user privileges (collections, tables). • Public can query without user account. More options if logged in. • Business rules enforced at database (not application) level.

  10. Arctos is… A versatile online collections management system • Cataloged Items (ID, attributes, parts, etc.; batch uploading, downloading, editing; encumbrances) • Localities & Collecting Events (mapping, media, history) • Transactions (loans, accessions, borrows, permits; email reminders) • Usage (publications, projects, sponsors, GenBank) • Curatorial (object tracking, parts, condition, relations, etc.) • Determination history (identification, georef, attributes)

  11. Arctos is… Modular and Pluggable • Projects and Publications • Media (local, external URI) • External Services (GenBank, TACC, MorphBank, CalPhotos, Ubio, etc.; ) – Collaborative • DiGIR (ORNIS, HerpNET, MaNIS, VertNET, etc.)

  12. Arctos is… Customizable • Specific features, e.g., Attributes (A cataloged item can have any number of attributes, customized to collections. A generic solution.) • Users (search, results, identifiers, download; save and email searches) • Managers (users, headers, CSS, reports)

  13. Arctos is… Open • Open source code • Built upon community needs • Compartmentalized (choose what you want to share) • Community input valued (user group, code issue list) • Responsive development model (bugs generally fixed within hours, requests within days to weeks unless major new feature) – community discussion drives development

  14. Arctos is… Economical • $15,300/year hosting (currently split by 3 institutions): • secure environment • dedicated web server and database server • server and database administrators • Oracle 11G • offsite backups in Alaska, TACC, San Diego • 1 full-time developer • 1 part-time DBA • Lots of input from users

  15. Arctos Multihosting • Shared Code • Shared Cost • Shared Expertise • Curatorial • Technical ? MCZ Location not important (electrons are fast!)

  16. Goal Run Arctos as a single system from one or more mirrored locations, from which each participating institution can be represented to its users and operators as an exclusive instance through row-level security, but in which vocabulary, programming, and physical resources are shared.  (No technical issues to adding collections. Social issues in multihosting.)

  17. Governance and Operating Support • Steering Committee and Advisory Group with representatives of each institution contributing to operational budget. • Steering Committee (institutional Directors or designees): budget, proposals for funding, proposals to connect to external resources, addition of collections, etc. • Advisory Group (curators): priorities for development - Chair of Advisory Group oversees activity of developer(s), reports to Steering Committee • Operating costs shared among institutions, funded by outside grants - identify developments that require outside funding vs. in-house support

  18. Summary • Cost-effective access to a deeply relational, highly expandable database capable of recording all aspects of specimen curation, running on Enterprise-caliber hardware and software, managed by professional IT staff. • Community of experienced users provide input into data structure and new development. Burden of development and operation shared among institutions. • All Arctos data are online. The public can query it, privileged users manage it through web browsers. • Demonstrates and documents the scientific context of specimens (projects, documents, media, etc.)…more than just label data.

More Related