en:user:browsing
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:user:browsing [2018/07/31 01:55] – [Additional resources] kjdon | en:user:browsing [2023/03/13 01:46] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
+ | |||
+ | |||
====== Browsing classifiers ====== | ====== Browsing classifiers ====== | ||
Greenstone allows you to create multiple browsing indexes for users to interact with | Greenstone allows you to create multiple browsing indexes for users to interact with | ||
Line 29: | Line 32: | ||
- | <!-- id:569 -->A simpler classifier, called // | + | A simpler classifier, called // |
creates a sorted list of a given metadata element and displays it without any alphabetic | creates a sorted list of a given metadata element and displays it without any alphabetic | ||
subsections. Another general-purpose list classifier is // | subsections. Another general-purpose list classifier is // | ||
selection list of date ranges. (The // | selection list of date ranges. (The // | ||
- | <!-- id:571 -->Other classifiers generate browsing structures that are explicitly | + | Other classifiers generate browsing structures that are explicitly |
hierarchical. Hierarchical classifications are useful for subject classifications | hierarchical. Hierarchical classifications are useful for subject classifications | ||
and subclassifications, | and subclassifications, | ||
- | <!-- id:573 -->All classifiers generate a hierarchical structure that is used to display | + | All classifiers generate a hierarchical structure that is used to display |
a browsing index. The lowest levels (i.e. leaves) of the hierarchy are usually documents, | a browsing index. The lowest levels (i.e. leaves) of the hierarchy are usually documents, | ||
but in some classifiers they are sections. The internal nodes of the hierarchy are either //Vlist//, //Hlist//, or // | but in some classifiers they are sections. The internal nodes of the hierarchy are either //Vlist//, //Hlist//, or // | ||
Line 46: | Line 49: | ||
- | <!-- id:607 -->All classifiers accept the argument // | + | All classifiers accept the argument // |
which defines what is written on the Greenstone navigation button that | which defines what is written on the Greenstone navigation button that | ||
invokes the classifier (it defaults to the name of the metadata argument). | invokes the classifier (it defaults to the name of the metadata argument). | ||
Buttons are provided for each Dublin Core metadata type, and for some other types of metadata. | Buttons are provided for each Dublin Core metadata type, and for some other types of metadata. | ||
- | <!-- id:608 -->Each classifier receives an implicit name from its position | + | Each classifier receives an implicit name from its position |
in the configuration file. For example, the third classifier specified in | in the configuration file. For example, the third classifier specified in | ||
the file is called CL3. This is used to name the collection information | the file is called CL3. This is used to name the collection information | ||
Line 57: | Line 60: | ||
- | ===== <!-- id:610 -->List classifiers ===== | + | ===== List classifiers ===== |
- | <!-- id:611 -->The various flavours of list classifier are shown below. | + | The various flavours of list classifier are shown below. |
- | * <!-- id:612 -->// | + | * // |
- | * <!-- id:613 -->// | + | * // |
- | * <!-- id:614 -->// | + | * // |
- | * <!-- id:615 -->// | + | * // |
- | ===== <!-- id:616 -->The hierarchy classifier ===== | + | ===== The hierarchy classifier ===== |
- | <!-- id:617 -->All classifiers are hierarchical. | + | All classifiers are hierarchical. |
However, the list classifiers described above have a fixed number of levels, | However, the list classifiers described above have a fixed number of levels, | ||
whereas the “hierarchy” classifiers described in this section have an arbitrary number of levels. | whereas the “hierarchy” classifiers described in this section have an arbitrary number of levels. | ||
Hierarchy classifiers are more complex to specify than list classifiers. | Hierarchy classifiers are more complex to specify than list classifiers. | ||
- | < | + | The hierarchy is predefined in a file such as this sub.txt: |
< | < | ||
1 | 1 | ||
Line 95: | Line 98: | ||
- | <!-- id:619 -->The //hfile// argument gives the name of a file, like that in Figure <imgref figure_part_of_the_file_sub> | + | The //hfile// argument gives the name of a file, like sub.txt, which defines the metadata hierarchy. Each line describes one classification, |
- | * <!-- id:620 -->Identifier, which matches the value of the metadata (given by the // | + | * Identifier, which matches the value of the metadata (given by the // |
- | * <!-- id:621 -->Position-in-hierarchy marker, in multi-part numeric form, e.g. 2, 2.12, 2.12.6. | + | * Position-in-hierarchy marker, in multi-part numeric form, e.g. 2, 2.12, 2.12.6. |
- | * <!-- id:622 -->The name of the classification. (If this contains spaces, it should be placed in quotation marks.) | + | * The name of the classification. (If this contains spaces, it should be placed in quotation marks.) |
- | <!-- id:623 --> | + | The file contents above are part of the //sub.txt// file used to create the subject hierarchy in the Development Library (and the Demo collection). This example is a slightly confusing one because the number representing the hierarchy appears twice on each line. The metadata type // |
- | <!-- id:624 -->The // | + | The // |
en/user/browsing.1533002136.txt.gz · Last modified: 2018/07/31 01:55 by kjdon