Resource Metadata Fields

SirsiDynix delivers Access Level values that are cannot be modified. The access level is also used in the OPAC Manager Gateway elements and in the User Access policy. Access levels include SYSTEMADMIN, SUPERVISOR, STAFF, PUBLIC, and EXTENDED PUBLIC. Refer to the Access Level Wizard for more information.

Classification Field (Requires Hyperion Access Control Manager with Accountability turned On to display.)

The title or document classification determines if an accountability operator can charge the accountable resource to a user. When resources are displayed, the documentation classification determines if the operator is able to display the resource.

Note: This field is required to create an accountability record.

Description Field

This is an optional field in the Hyperion Resource Metadata record where a text description of the resource can be entered. This can be helpful in limiting a search. Description is one of the Fields to Search available with the Search helpers.

Name Field

This field contains the name of the resource as it displays in the Resource Metadata window when it is selected from the directory tree. The name must be unique and can be up to 100 characters in length.

Need to Know Field (Requires Hyperion Access Control Manager with Accountability turned On to display.)

This verify field allows you to select the type of information the user is allowed to access. A user must have at least one Need to Know policy in common with a title to circulate the resource. This field is the third level of security the user must meet before checking out accountable materials in the assigned subject area, or displaying accountable media resources.

Resource Extended Metadata Fields

Extended Metadata fields allow the user to input fields such as Author or Copyright into the Metadata record. Defined Extended Attributes can be accessed from the list to the right of the first box displayed when adding extended attributes. The values that display are based on the format (such as DUBLIN or HYPERX) associated with the displayed Resource Type Attribute. If they are assigned, extended metadata records display below the Resource Metadata pane. These fields do not display in the general resource metadata unless they have been added using one of the extended metadata helpers: Create First Row Helper, Insert Row After, Insert Row Before.

Note: Before extended attributes can be used, the Entry ID and Extended Attribute Format policies have to be created. Contact SirsiDynix Customer Support if you need to make any additional fields searchable.

Resource ID Field

The Resource Id field is an optional and searchable field in the Resource Metadata record that contains a unique identifier. This field is case-sensitive and limited to 120 characters. It can contain the 856 tag information that links the image back to the library catalog. For more information, refer to FAQs: Linking Hyperion Data to the Library Catalog.

Resource Type Field

Resource Types are defined in the Resource Attribute policies. Defined Resource Types are selected via drop-down lists that display when resources are added or modified. The Resource Type Attribute policies also control whether a particular type can be a child or parent of another.

The Resource Type identifies and describes an element in the directory tree. Each element may represent an actual digital resource, or the organizational element that is used to categorize a group of related works. Resource Types may be subdivided, using parent and child concepts, to create a hierarchy in the directory tree.

For example, in the following example, COLLECTION, ABSTRACT, SUBJECT, PRESS, and DOCUMENT are Resource Types.

COLLECTION: U.S. Space & Rocket Center
ABSTRACT: Welcome to the Press Room
SUBJECT: U.S. Space & Rocket Center Press Releases
ABSTRACT: Welcome to the Press Room
PRESS: U.S. Space & Rocket Center Background Story
PRESS: U.S. Space & Rocket Center Exhibits and Attractions
PRESS: U.S. Space & Rocket Center Offers Complete Space Experience
SUBJECT: U.S. Space & Rocket Center Brochures
DOCUMENT: U.S. Space & Rocket Center, Huntsville, AL, Brochure

In this example, COLLECTION, SUBJECT, PRESS, and DOCUMENT are content Resource Types. SUBJECT is a child of COLLECTION, and PRESS AND DOCUMENT are both children of SUBJECT. However, PRESS and DOCUMENT do not have children, because they are actual objects in the directory tree. Child level Resource Types are defined as valid in the Resource Type Attribute policy.

ABSTRACT is defined as a Parent Characteristics type, which, ironically, cannot have any children. Instead, the ABSTRACT Resource Type is used to define the characteristics of the group to which it is a child. It defines the entire group.

TRASHSITE and TRASHBIN are used to retain elements that have been removed from the active metadata. These Resource Types cannot be displayed in the-e-Library.

ARCHIVE, TRASHSITE, and TRASHBIN cannot be removed.

Refer to the Resource Attribute Policy and Understanding the Structure of Hyperion for more information.

Restrictions Field (Requires Hyperion Access Control Manager with Accountability turned On to display.)

The Restrictions information categories are based on library-specified policies. Any term can be assigned to the access restriction verify list (which is usually a government-defined list or a specific group of users or documents). The patron’s access restriction must contain all the access restrictions in a resource before that resource can be accessed by the patron. The higher the number of Access Restrictions a resource has, the less likely a user will be to access a resource. The Restriction policy contains information about access restriction levels.