Tag: data

Data cleanup in Orbis and Morris for discovery and migration

Jenn Nolte

As the Quicksearch beta project moves towards becoming a production-level service, there’s been a good deal of activity in Orbis and Morris related to data cleanup.

As found with the Yufind project, the exposure of metadata in discovery systems is a double-edged sword: more metadata can be made visible, accessible and usable- but this also means that typos, outdated cataloging standards, and changing policies will surface.

Much of the cleanup work in Orbis has been done in the Catalog Management team, and led by Arcadia Falcone, Discovery Metadata Librarian.

Here’s a post on format mapping in Quicksearch by Arcadia, and most of this presentation to Tech Services discusses the additional cleanup work done by CMT.

This work is doubly important, since it not only optimizes and tidies the metadata presented in Quicksearch beta but also prepares our catalog metadata in Orbis for a future migration to a new ILS.

Data Storage Virtualization and Security Upgrades Continue

Bob Rice

LibraryIT’s Information Architecture team continues to manage the SGI/StorHouse storage virtualization upgrade and Trusted Edge implementation, begun this week.

To oversimplify, storage virtualization is the introduction of a virtualization layer that sits in between network-connected data storage spaces. This allows for related files (digital objects, typically) to be stored in unrelated storage areas yet represented in one continuous resource- the end user who is looking for and retrieving files will never see that the whole system they are using lives in separate spots.

Our StorHouse storage currently houses approximately 600TB (terabytes), or about two thousand times the size of our Orbis database, of replicated data. Plans are to implement Trusted Edge, a policy-based/tiered storage component, that will allow us to move files to specific storage based on their use and type. For example archive type data will move off to our archive system, StorHouse, while use copies that should be available to the end user might be moved off to a faster storage area for faster access.