Main -> Documentation -> Open SiteSearch Record Builder -> Record Builder and Constant Data

Record Builder and Constant Data

 

Contents

Document Conventions
Introduction
What Is Constant Data?
Where Does Constant Data Reside?
Defining Constant Data Values for DC or MARC Databases
Defining Multiple Constant Data Files per Database
Adding Constant Data to a Record


Introduction

Beginning with SiteSearch 4.1.2, you can make constant data available to metadata specialists who create and edit records in local databases using OCLC Database Builder's Record Builder application. You can define constant data for any database based on a Dublin Core (DC) or MARC Catalog database framework. You can create constant data values for any of the elements on a DC workform or the fields on a MARC workform, as displayed on Record Builder's Edit Record screen.


Document Conventions

  • <WebZ_root> refers to the location of the SiteSearch environment that includes Record Builder.
  • db_name is a database's top-level directory, typically <WebZ_root>/dbbuilder/dbs/dB_name.
  • "You" refers to a person responsible for Record Builder system and/or database administration.

What Is Constant Data?

In Record Builder, constant data refers to predefined values for some elements (fields) on a data entry workform. You generally define constant data for elements that have the same value for many records in a database. For example, if many of the items being cataloged in a local DC database have the the same source, you may wish to provide a constant data value for the Source element so metadata specialists do not have to enter this value manually for every record.

Return to Contents


Where Does Constant Data Reside?

You define constant data in an .xml file. The database frameworks shipped with Record Builder all include the word "constant" in the name of their constant data files and store these files in the database's top-level directory, <WebZ_root>/dbbuilder/dbs/dB_name. This is the recommended location, but is not required. See constant.xml File for DC Databases for more information about the structure and contents of a constant data file.

Return to Contents


Defining Constant Data for DC or MARC Databases

Refer to the following procedures for adding or removing constant data values for DC (DC(2) or DCQ) or MARC Catalog databases:

Return to Contents


Defining Multiple Constant Data Files per Database

You can define multiple sets of constant values for a local database by placing each set of constant data values in a different file and associating each constant data file with a different workform.

For a database based on the DC(2) or DCQ database frameworks, define separate workforms in the database's configuration file for each set of constant data values, but use the same template (template.xml) for each workform. Each workform has its own constant data file. The database configuration files shipped with SiteSearch 4.1.2 for these database frameworks demonstrate the use of multiple workforms, each with its own unique set of constant data values.

For a MARC Catalog database, which already uses multiple workforms, use a separate constant data file for each workform.

Return to Contents


Adding Constant Data to a Record

There are two ways to add constant data to a record: automatically or manually.

With automatic application, the constant data values appear on the data entry workform (Edit Record screen) as soon as a metadata specialist creates a new blank record.

With manual application, the constant data values appear on the Edit Record screen only after the metadata specialist selects Apply constant data from the Available actions list.

In both cases, the metadata specialist can edit or remove the constant data values displayed on the Edit Record screen.

The database frameworks shipped with SiteSearch 4.1.2 demonstrate each of these uses of constant data.

Return to Contents


See Also

constant.xml File for DC Databases
Performing Online Updates to Local Databases with Record Builder
Edit Record Screen
Customizing DC Templates
Planning a New DC Database


[Main][Documentation][Support][Technical Reference][Community][Glossary][Search]

Last Modified: