Use of UNInn libraries as test libraries for reindexing

• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
We are thinking about setting up the UNI01/50/60 bases under the a18 tree as a mini-test environment for modifications to files that require re-indexing (tab_filling, tab20, tab22, etc).

We'd copy the /tab and pc_tab/catalog directories from ABC01/50/60 to the respective UNI directories as well as 2000 bib records from ABC01. That way when we modify a table that requires re-indexing it would take minutes instead of hours, and wouldn't lock our test bases for extended periods.

Is this a good idea? By modifying the UNI bases and directories under a18 could we damage our test environment in u18? Are there any unforeseen consequences to this sort of thing, or any other considerations that we should be aware of?

Resolution:
The UNInn libraries are intended as demo libraries for sites using Unimarc (see KB 8192-2408). They are not used at all in the support of sites using MARC21.

You can do what you want with them, but you should note that the UNInn tables and data, being in the a-tree, are subject to replacement by rep_changes and version upgrades.

The alternative is to open additional ABCnn libraries. You can do it either way.

• Article last edited: 10/8/2013