en:user:collection_grouping
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
en:user:collection_grouping [2016/11/22 01:36] – created kjdon | en:user:collection_grouping [2023/03/13 01:46] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
+ | |||
+ | |||
====== Collection Grouping ====== | ====== Collection Grouping ====== | ||
By default, the Greenstone home page will display a grid of all valid collections. This can get quite crowded if there are a number of collections. " | By default, the Greenstone home page will display a grid of all valid collections. This can get quite crowded if there are a number of collections. " | ||
- | This is accomplished by putting a group folder inside the collect folder (greenstone2/ | ||
- | Then a configuration file is needed for the group. This lives in an etc folder inside the group, and is collect.cfg for greenstone2, | + | <tabbox Greenstone3> |
+ | |||
+ | Grouping in Greenstone 3 is controlled by the groupConfig.xml file, found in a site folder alongside the siteConfig.xml file. For example, in / | ||
+ | |||
+ | By default, there are no groups. | ||
+ | |||
+ | Add hierarchy and groupDescriptions elements to add groups to your library. | ||
+ | |||
+ | Describe your structure inside a hierarchy tag as shown in the examples below. | ||
+ | |||
+ | Hierarchies can contain groups and/or collections. Groups can contain other groups and/or collections. | ||
+ | The order they are listed is the order they will appear on the home page. | ||
+ | |||
+ | Describe your groups in groupDescriptions element as shown in the example below. | ||
+ | Without a matching group element in groupDescriptions, | ||
+ | |||
+ | If a collection is not mentioned in the hierarchy or as part of a group it will be listed on the main | ||
+ | home page after the specified groups and collections. | ||
+ | |||
+ | |||
+ | Example 1: this example puts a few Greenstone demo collections into some groups. The home page | ||
+ | will display the demo group plus any unlisted collections. The demo group home page will display its two subgroups; their home pages will display their list of collections. | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | <group name=" | ||
+ | <group name=" | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | <group name=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | < | ||
+ | <group name=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | <group name=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | <group name=" | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | |||
+ | Example 2: If you want to put your collections into a specific order, you can list them in the hierarchy. Any unmentioned collections will be listed at the end. This example has no groups, but is a way of specifying which order you want the collections to appear on the home page. | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | <tabbox Greenstone2> | ||
+ | |||
+ | |||
+ | This is accomplished by putting a group folder inside the collect folder (greenstone2/ | ||
+ | |||
+ | Then a collect.cfg | ||
- | <TABAREA tabs=" | ||
- | <TAB> | ||
- | Actually I think greenstone 3 version is completely different??? | ||
- | </ | ||
- | <TAB> | ||
< | < | ||
creator | creator | ||
Line 24: | Line 99: | ||
</ | </ | ||
- | </TAB> | + | </tabbox> |
- | </ | + |
en/user/collection_grouping.1479778607.txt.gz · Last modified: 2016/11/22 01:36 by kjdon