pergamonmystic:linkedhelp:lookup_using
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
pergamonmystic:linkedhelp:lookup_using [2021/10/06 09:42] admin |
pergamonmystic:linkedhelp:lookup_using [2021/10/06 12:32] (current) admin |
||
|---|---|---|---|
| Line 52: | Line 52: | ||
| The exception to this use of the **[Text]** field is when the item in question is a configuration parameter - in this case the **[Text]** field is used as a description of the parameter and the important value is stored in one of the other fields. These items are largely system level items however, and rarely need editing by local staff. | The exception to this use of the **[Text]** field is when the item in question is a configuration parameter - in this case the **[Text]** field is used as a description of the parameter and the important value is stored in one of the other fields. These items are largely system level items however, and rarely need editing by local staff. | ||
| - | Here is an overview of the other fields, and what they are used for: | + | Here is an overview of the other fields, and what they are used for. Note that some of these fields are automatically removed from the screen if not required and therefore may not appear at all times. This is normal. |
| === System Key === | === System Key === | ||
| Line 58: | Line 58: | ||
| Plain-text values can be changed, not least as a result of operating Mystic in non-English languages. As a result, some important values in the Lookup Manager have a unique **System Key** which Mystic itself can use to identify the lookup item, regardless of what a user has changed the text to be. | Plain-text values can be changed, not least as a result of operating Mystic in non-English languages. As a result, some important values in the Lookup Manager have a unique **System Key** which Mystic itself can use to identify the lookup item, regardless of what a user has changed the text to be. | ||
| - | No item created by an local user requires a System Key - they are useful only if Mystic knows how to use a specific key internally. | + | No item created by a local user requires a System Key - they are useful only if Mystic knows how to use a specific key internally. |
| === Alias === | === Alias === | ||
| + | |||
| + | The **Alias** field allows the entry of one or more aliases for the item. This mechanism is most commonly used for Categories such as **Keywords** where alternate search terms can be entered without the need to create a new entry in the category, or manually attach it to a Catalogue Item (a search of either the keyword or any aliases listed has the same effect). | ||
| === HUB Sync === | === HUB Sync === | ||
| + | |||
| + | The **HUB Sync** check box is for information only. | ||
| + | |||
| + | This checkbox indicates whether the textual content of the item has been synchronised with the main HUB Bibliographic database. When synchronised, the local lookup value stores a universally unique UUID linking it to the master record in the HUB (not displayed to human users). | ||
| === 'Single Use' === | === 'Single Use' === | ||
| + | |||
| + | The check box initially labelled **Single Use** can be misleading as its use actually changes according to the nature of the category being displayed. In most uses, it represents a boolean True/False, Yes/No or On/Off setting which is related to the nature of the **Text** of the item. The label of the **Single Use** field changes accordingly to reflect what the on/off setting means in practice. | ||
| === Extra Info (1) and (2) === | === Extra Info (1) and (2) === | ||
| + | The **Extra Info** fields provide open, plain text storage for any additional information which is required by the lookup value. By far the most common use of the Extra Info fields is by the application configuration items such as in the **System Information** category. They are rarely used by normal Item or Reader categories. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Specialised Data Entry Modules ==== | ||
| + | |||
| + | Some categories require a larger amount of specialised information to be entered - such as the **Reader Audience** category, which needs to record which **Item Audiences** are permitted to be viewed / borrowed; or the **Circulation Profile** which needs to store the number of items permitted, and how long they can be borrowed for. | ||
| + | |||
| + | When required, the module is displayed beneath the normal fields (described above) and simply become part of the normal editing dialog. | ||
| + | |||
| + | The following links describe the specialised modules that may be displayed in the Lookup Manager: | ||
| + | |||
| + | * [[:pergamonmystic:linkedhelp:lookup_module_closures|Closure Days]]\\ | ||
| + | * [[:pergamonmystic:linkedhelp:lookup_module_hid|HID Formats]]\\ | ||
| + | * [[:pergamonmystic:linkedhelp:lookup_module_category|Item Category]]\\ | ||
| + | * [[:pergamonmystic:linkedhelp:lookup_module_media|Media]]\\ | ||
| + | * [[:pergamonmystic:linkedhelp:lookup_module_audience|Reader Audience]]\\ | ||
| + | * [[:pergamonmystic:linkedhelp:lookuo_module_profile|Reader Circulation Profile]]\\ | ||
| + | * [[:pergamonmystic:linkedhelp:lookup_module_groups|Reader Groups]]\\ | ||
| + | |||
| + | ---- | ||
| + | |||
| + | ==== Additional functions unique to the Lookup Manager ==== | ||
| + | |||
| + | The following additional functions are available to the Lookup Manager which are not normally found in other Manager Dialogs: | ||
| + | |||
| + | * [[:pergamonmystic:linkedhelp:lookup_merge|Merging lookup items]]\\ | ||
| + | * [[:pergamonmystic:linkedhelp:lookup_split|Splitting lookup items]]\\ | ||
| + | * [[:pergamonmystic:linkedhelp:lookup_duplicates|Finding duplicates in a category]]\\ | ||
| ---- | ---- | ||
pergamonmystic/linkedhelp/lookup_using.1633513335.txt.gz · Last modified: 2021/10/06 09:42 by admin
Page Tools
