Understanding Hyperion Maintenance and Administration

You are here: Hyperion > FAQs for the Hyperion Module > Understanding Hyperion Maintenance and Administration

Understanding Hyperion Maintenance and Administration

The following maintenance and administration tasks are required for the Hyperion DMA.

System Backups

Once all documents are captured, it is vitally important that an off-line backup regimen be established. An image backup should be made regularly, capturing both the digital documents and the bibliographic records that refer to those documents. All of this data should be stored in an off-site location for disaster recovery purposes. Between each image backup, incremental backups should be done on a daily basis, thus preventing the loss of vital information. The frequency of backing up is determined by firm guidelines, standard procedures, and user requirements.

The administrator is responsible for other system-level tasks that develop as the system is used. These may include custom script writing, report generation, and other tasks identified through continued use.

System Management

File System Management

Hyperion is a digital media management tool that is used to preserve and provide access to digital resources in your library or other information management system. How these resources are preserved and accessed is determined by the system policies, which are accessed using the wizards from the menu bar on the opening page of Hyperion. Each of these policies has provisions that allow for the creation of new policies. Changes to the following policies may be required as your metadata continues to expand and evolve.

•

The File Type policy identifies which file types are optical character recognition enabled ASCII files that can be full text indexed. Full text searching is only available for sites that purchase the Hyperion Media Text Index Manager, available only in the e-Library.

•

The Access Level policy controls who can perform what functions in the Hyperion staff client.

•

The Resource Attributes policy manages the structural units and rules used to build the hierarchy. The Resource Types are logical records that identify and describe a type of node in the directory tree.

•

The Image Directory policy identifies the directories containing the images by Name, Description, Path, Maximum Files, and Maximum Bytes. As documents and images are added to Hyperion, system policies may need to be updated to reflect the growing disk requirements. The Image Directory policy should be used to manage the continuing expansion of your metadata as new storage resources are brought online. The Image Directory policy does not create the actual directory on the server.

•

The Format policy defines the metadata formats and extended attribute fields that are associated with the Resource Attributes.

RAID Array

A RAID array is redundant, high-performance, and relatively inexpensive array of disk drives. A RAID array can be used as the primary storage are for all captured documents. They are designed to minimize downtime by employing hot-swappable disk drives and redundant power supplies. Since files are striped across all the disks, and because they are written with a significant amount of error correction, if a disk drive fails, the other disks can be used to dynamically recreate the data on the failed drive while the other drive is being serviced. The subsystem is designed so that no downtime is required if a disk drive fails.

Upgrades to Existing Modules

As long as you maintain an active software service contract with Sirsi, you receive as part of that agreement all system upgrades incorporated into the Hyperion software. Upgrades to modules are provided at no charge. Maintenance covers installation of upgrades during normal working hours. You only receive upgrades to the modules currently licensed on your system. New modules developed by SirsiDynix are not part of a system upgrade; these modules are available to all users at specified fees. Once you have purchased a module, upgrades are provided under the software service contract.

Hyperion Maintenance

Although the bulk of maintenance is accomplished by running the Hyperion reports, there are additional ongoing and maintenance tasks and user group management functions that need to be performed by system administrators or other staff members. Ongoing maintenance includes managing staff users and the general user community. As new staff members are hired or existing staff members leave, the administrator is responsible for updating the system’s user profiles to reflect these changes.

User/group management functions include adding, deleting, or renaming users, maintaining security passwords, managing user groups, controlling user document access rights, and managing document categories and types.

Additionally, a variety of maintenance functions can be performed on the Resource Types and images in Hyperion using the Hyperion helpers (Hyperion Toolkit). The helpers are accessed by either right clicking on a resource in the directory tree, or selecting one of the helper icons. These functions include the following types of activities.

•

Adding Resource Types and images to Hyperion

•

Deleting Resource Types instances and images from Hyperion

•

Modifying metadata records of existing Resource Types and images in Hyperion

•

Using the Cut and Paste helpers to reposition resources in Hyperion

Trash Sites and Trash Bins

Hyperion organizes deleted image files into a hierarchy. The trash site is an upper level resource unit used to organize the trash bins. Trash bins are the repositories of deleted images, and they are stored in Hyperion as resources with the date of deletion as the resource name. All resources deleted on a particular day are stored in a resource with that day’s date as its filename.

For example, the file 20030825 contains all resources deleted on August 25, 2003.

Deleted resources are completely removed from the metadata, including the resource name, description, resource id, access level, and attribute type. Only the images are stored in the trash bin with the day’s date, and they are still residing on the server.

If the images of several resources are stored in the trash bin, they will be in a disorganized state. To find a specific image, it is necessary to browse through the contents of the trash bin, displaying each image until the specific image to be recovered is located.

Warranty and Maintenance Agreement

Equipment purchased from SirsiDynix includes a renewable maintenance agreement. Refer to Contacting SirsiDynix Customer Support for more information.

When identified, changes to the configuration of the software may be required that affect system maintenance. These changes may be caused by changes in the hardware configuration, disk space constraints, user requirements, security, and other causes. If the system needs to be shutdown for a period of time to perform these tasks, notices should be made to the user community through the client software, email, a Web page, or some other method. Users need to understand that the downtime has been scheduled and that any interruption is not the result of some system malfunction or other unknown problem.

Sirsi software maintenance (renewable annually) includes the following services.

•

Telephone support to answer general questions on system usage, and troubleshooting of software-specific problems

•

Software corrections to the Hyperion DMA software