Greenstone Wiki

User Tools

Site Tools

You are here: index » en » user » browsing
en:user:browsing

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
en:user:browsing [2014/11/02 21:35] – external edit 127.0.0.1en: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 //List//, +A simpler classifier, called //List//, 
 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 //DateList//, which generates a  subsections. Another general-purpose list classifier is //DateList//, which generates a 
 selection list of date ranges. (The //DateList// classifier is used in the [[http://www.nzdl.org/gsdlmod?a=p&p=about&c=gsarch|Greenstone Archives collection]].) selection list of date ranges. (The //DateList// classifier is used in the [[http://www.nzdl.org/gsdlmod?a=p&p=about&c=gsarch|Greenstone Archives collection]].)
  
-<!-- 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 organisational hierarchies. and subclassifications, and organisational hierarchies.
  
-<!-- 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 //Datelist//. but in some classifiers they are sections. The internal nodes of the hierarchy are either //Vlist//, //Hlist//, or //Datelist//.
Line 46: Line 49:
  
  
-<!-- id:607 -->All classifiers accept the argument //buttonname//, +All classifiers accept the argument //buttonname//, 
 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 -->//SectionList//—like //List// but the leaves are sections rather than documents. All document sections are included except the top level. This is used to create lists of sections (articles, chapters or whatever) such as in the Computists' Weekly collection (available through // nzdl.org //), where each issue is a single document and comprises several independent news items, each in its own section. +  * //SectionList//—like //List// but the leaves are sections rather than documents. All document sections are included except the top level. This is used to create lists of sections (articles, chapters or whatever) such as in the Computists' Weekly collection (available through // nzdl.org //), where each issue is a single document and comprises several independent news items, each in its own section. 
-  * <!-- id:613 -->//AZList//—generates a two-level hierarchy comprising an //HList// whose children are //VLists//, whose children are documents. The //HList// is an A-Z selector that divides the documents into alphabetic ranges. Documents are sorted alphabetically by metadata, and the resulting list is split into ranges. +  * //AZList//—generates a two-level hierarchy comprising an //HList// whose children are //VLists//, whose children are documents. The //HList// is an A-Z selector that divides the documents into alphabetic ranges. Documents are sorted alphabetically by metadata, and the resulting list is split into ranges. 
-  * <!-- id:614 -->//AZSectionList//—like //AZList// but the leaves are sections rather than documents. +  * //AZSectionList//—like //AZList// but the leaves are sections rather than documents. 
-  * <!-- id:615 -->//DateList//—like //AZList// except that the top-level //HList// allows selection by year and its children are //DateLists// rather than //VLists//. The metadata argument defaults to //Date//.+  * //DateList//—like //AZList// except that the top-level //HList// allows selection by year and its children are //DateLists// rather than //VLists//. The metadata argument defaults to //Date//.
  
-===== <!-- 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.
  
-<imgcaption figure_part_of_the_file_sub|%!-- id:618 --%Part of the file //sub.txt// ></imgcaption>+The hierarchy is predefined in a file such as this sub.txt:
 <code> <code>
 1           1       "General reference" 1           1       "General reference"
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>, which defines the metadata hierarchy. Each line describes one classification, and the descriptions have three parts:+The //hfile// argument gives the name of a file, like sub.txt, which defines the metadata hierarchy. Each line describes one classification, and the descriptions have three parts:
  
-  * <!-- id:620 -->Identifier, which matches the value of the metadata (given by the //metadata// argument) to the classification. +  * Identifier, which matches the value of the metadata (given by the //metadata// argument) to the classification. 
-  * <!-- 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 -->Figure <imgref figure_part_of_the_file_sub> is 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 //Hierarchy// is represented in documents with values in hierarchical numeric form, which accounts for the first occurrence. It is the second occurrence that is used to determine the hierarchy that the hierarchy browser implements.+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 //Hierarchy// is represented in documents with values in hierarchical numeric form, which accounts for the first occurrence. It is the second occurrence that is used to determine the hierarchy that the hierarchy browser implements.
  
-<!-- id:624 -->The //hierarchy// classifier has an optional argument, //sort//, which determines how the documents at the leaves are ordered. Any metadata can be specified as the sort key. The default is to produce the list in the order in which the building process encounters the documents. Ordering at internal nodes is determined by the order in which things are specified in the //hfile// argument.+The //hierarchy// classifier has an optional argument, //sort//, which determines how the documents at the leaves are ordered. Any metadata can be specified as the sort key. The default is to produce the list in the order in which the building process encounters the documents. Ordering at internal nodes is determined by the order in which things are specified in the //hfile// argument.
  
  
Line 113: Line 116:
 ===== Additional resources ===== ===== Additional resources =====
   * View the full [[en:classifier:index|list of browsing classifiers]]   * View the full [[en:classifier:index|list of browsing classifiers]]
-  * [[en:developer:classifiers|The developer's page on browsing classifiers]] provides more information on how they work+  * [[en:user_advanced:classifiers| Advanced User Guide classifiers page]] provides more information on how they work
   * You can also view some [[en:user_advanced:classifiers|information related to browsing classifiers]]:   * You can also view some [[en:user_advanced:classifiers|information related to browsing classifiers]]:
-    * [[en:user_advanced:classifiers#Translating navigation bar labels for new classifiers]] +    * [[en:user_advanced:more_about_classifiers_gs2#Translating navigation bar labels for new classifiers]] 
-    * [[en:user_advanced:classifiers#dynamic_classifiers]] +    * [[en:user_advanced:more_about_classifiers_gs2#dynamic_classifiers]] 
-    * [[en:user_advanced:classifiers#Preserving the original directory structure of your collection for browsing]] +    * [[en:user_advanced:more_about_classifiers_gs2#Preserving the original directory structure of your collection for browsing]] 
-    * [[en:user_advanced:classifiers#Doing Unicode collation for a classifier]]+    * [[en:user_advanced:more_about_classifiers_gs2#Doing Unicode collation for a classifier]]
en/user/browsing.1414964120.txt.gz · Last modified: 2018/07/31 01:55 (external edit)