Warning: This page has not been updated in over over a year and may be outdated or deprecated.
configuration:record_versions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
configuration:record_versions [2020/11/12 21:11] – [Underlying Technology] demiankatz | configuration:record_versions [2023/03/20 16:27] (current) – [Introduction] demiankatz | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Record Versions (FRBR) ====== | ====== Record Versions (FRBR) ====== | ||
- | :!: This feature was added in VuFind | + | :!: This feature was added in VuFind® |
+ | |||
+ | ===== Introduction ===== | ||
+ | |||
+ | VuFind®' | ||
===== Configuration ===== | ===== Configuration ===== | ||
- | Versions support can be toggled using the display_versions settings in search configuration (e.g. searches.ini). If RecordTabs.ini is customized, make sure that the Versions tab and TabScripts section is present. For versions to display, the Solr index must be updated or recreated with VuFind | + | Versions support can be toggled using the display_versions settings in search configuration (e.g. searches.ini). If RecordTabs.ini is customized, make sure that the Versions tab and TabScripts section is present. For versions to display, the Solr index must be updated or recreated with VuFind® |
+ | |||
+ | If you want to always display versions as a search result, you can disable the Versions tab in RecordTabs.ini. The links in search results and record screen are automatically adjusted to support both scenarios. | ||
===== User Interface ===== | ===== User Interface ===== | ||
- | Record versions support brings two elements to VuFind: Search results include a link for displaying other versions (including count) and a record tab that displays a set of versions for the record. All versions can also be displayed as a search result list. | + | Record versions support brings two elements to VuFind®: Search results include a link for displaying other versions (including count) and a record tab that displays a set of versions for the record. All versions can also be displayed as a search result list. |
It is an intentional choice to not introduce FRBR specific language in the user interface. The primary reason for this is that it can be a complicated model for a non-librarian to understand and even more complex to actually handle in the UI and between diverse data sources. This means that in practice, and depending on what the index actually contains, versions can include both FRBR expressions and manifestations. | It is an intentional choice to not introduce FRBR specific language in the user interface. The primary reason for this is that it can be a complicated model for a non-librarian to understand and even more complex to actually handle in the UI and between diverse data sources. This means that in practice, and depending on what the index actually contains, versions can include both FRBR expressions and manifestations. | ||
Line 17: | Line 23: | ||
Identifying versions of a record is based on so-called work identification keys. Any records that share keys are considered versions of each other. Keys are created from author + title combinations and uniform titles. It is possible that a version of a record has also other different versions since it may have additional keys not present in the initial record. Keys have been designed to be general enough that they can be created from MARC records as well as other formats. There are several rules for how the keys are created by default, notably: | Identifying versions of a record is based on so-called work identification keys. Any records that share keys are considered versions of each other. Keys are created from author + title combinations and uniform titles. It is possible that a version of a record has also other different versions since it may have additional keys not present in the initial record. Keys have been designed to be general enough that they can be created from MARC records as well as other formats. There are several rules for how the keys are created by default, notably: | ||
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
For default MARC fields used, please see work_keys_str_mv in import/ | For default MARC fields used, please see work_keys_str_mv in import/ | ||
Line 29: | Line 35: | ||
---- struct data ---- | ---- struct data ---- | ||
+ | properties.Page Owner : emaijala | ||
---- | ---- | ||
configuration/record_versions.1605215461.txt.gz · Last modified: 2020/11/12 21:11 by demiankatz