| Main -> Documentation -> Open SiteSearch Record Builder -> Single Record Import |
|
Overview Beginning in version 4.2.0, Record Builder supports single record import to a local Pears or Newton database. The imported record must have the same record syntax and structure as the target database. In both cases, Record Builder converts the imported record into BER format, using the appropriate Record Handler, and adds the converted record to the target database. Records for import must be located in the import directory, as set by the Record Builder administrator in order to be imported into a local database. This directory is also used as the target location for exporting records from a local database. A cataloger can select the record to be imported by highlighting its filename from a pull down menu in the import interface. Record Builder opens the record automatically in edit mode using the template for the target database. The imported record has a record id of "null" and the cataloger can make edits and changes to the record, such as adding constant data, before submitting it to the target database. The cataloger may also save the record to the save database, export the record or cancel all changes. NOTE: records cannot be imported into the save database. After import, Record Builder displays the record in view mode with the newly assigned record id number. The record id assigned is taken from the value in the recordid.txt file for the target database. NOTE: The Record Builder administrator should ensure that the recordid.txt file is current prior to importing a record. If this file is not current, Record Builder could assign an id that is already used in the database to the imported record and consequently overwrite an existing record. Configuration A local database must have an [Import] section in its rb configuration file in order to support the import function. One parameter required for this section is recordsyntax. Acceptable values for this parameter, out-of-the-box, include MARC, SGML, DELIMITED or BER. The value entered for this parameter determines the Record Handler that will be used to convert the imported record. This is a required field. For Pears databases only, the [Import] section also should have a second parameter, dbdesc. Enter the location of the Pears desc file. This parameter can be left blank for Newton databases, as shown in the configuration files for the sample databases included in SS420. Additionally, a separate Record Handler section is required in the rb configuration for Newton databases in SGML or delimited text format only. The Record Handler section will be either [HandleSGML] or [HandleDelimited], respectively, and will have a single parameter: tags. Enter the location of the dtd file for the database. This section is not required for Newton databases in MARC or BER format. Finally, the Record Builder administrator must set a default import directory for import files. This directory is a global property for all local databases and is not configurable at the database level. The location is set in the JaSSIServer_rb.ini file under the [ExpImportLocation] section. The default setting for this parameter is <WebZ_root>/dbbuilder. This directory also serves to store records automatically exported from a local database. Following a successful import, the filename of the original record is appended with "_imported" and stored in the import directory. The Record Builder administrator can then determine which files have been processed and which have not been imported yet. Authorization Importing a record into a local database exposes the database to possible irregularities. Record Builder has a built-in checking mechanism to ensure that an imported record has the same record syntax as that of the target database. If a cataloger attempts to import a record that does not have the same record syntax as the target database, Record Builder returns an error message. However, Record Builder cannot ensure that the record structure of an imported record is consistent with the record structure of the target database. For example, it is possible to import any SGML record with one type of record structure into an SGML database with a different type of record structure and thus compromise the integrity of the database. If a record is imported improperly, it may be difficult to locate the record and remove it from the database. We recommend that the Record Builder administrator consider this exposure when assigning privileges to catalogers and trainees.Out-of-the-box, import privileges are given to RBCataloger and higher. Follow these steps to import a record into a local database.
See Also Single
Record Export |
|
[Home]
[Documentation]
[Support]
[Search]
|