All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
Note | ||
---|---|---|
| ||
It is worth noting that the Once DSpace is installed, it the system only uses the settings in your |
Warning | ||
---|---|---|
| ||
When you edit the "build.properties" file (or a custom *.properties file), take care not to remove or comment out any settings. Doing so, may cause your final "dspace.cfg" file to be misconfigured with regards to that particular setting. Instead, if you wish to remove/disable a particular setting, just clear out its value. For example, if you don't want to be notified of new user registrations, ensure the "mail.registration.notify" setting has no value, e.g.
|
...
If you are unfamiliar with the Event System in DSpace, and require additional information with terms like "Consumer" and "Dispatcher" please refer to :http://wiki.dspace.org/index.php/EventSystemPrototype EventSystemPrototype.
Property: |
|
Example Value: |
|
Informational Note: | This is the default synchronous dispatcher (Same behavior as traditional DSpace). |
Property: |
|
Example Value: |
|
Informational Note: | This is the default synchronous dispatcher (Same behavior as traditional DSpace). |
Property: |
|
Example Value: |
|
Informational Note: | The noindex dispatcher will not create search or browse indexes (useful for batch item imports). |
Property: |
|
Example Value: |
|
Informational Note: | The noindex dispatcher will not create search or browse indexes (useful for batch item imports). |
Property: |
|
Example Value: |
|
Informational Note: | Consumer to maintain the search index. |
Property: |
|
Example Value: | {{event.consumer.search.filters = }} |
Informational Note: | Consumer to maintain the search index. |
Property: |
|
Example Value: |
|
Informational Note: | Consumer to maintain the browse index. |
Property: |
|
Example Value: |
|
Informational Note: | Consumer to maintain the browse index. |
Property: |
|
Example Value: |
|
Informational Note: | Consumer related to EPerson changes |
Property: |
|
Example Value: |
|
Informational Note: | Consumer related to EPerson changes |
Property: |
|
Example Value: |
|
Informational Note: | Test consumer for debugging and monitoring. Commented out by default. |
Property: |
|
Example Value: |
|
Informational Note: | Test consumer for debugging and monitoring. Commented out by default. |
Property: |
|
Example Value: |
|
Informational Note: | Set this to true to enable testConsumer messages to standard output. Commented out by default. |
...
This enables The following configurations are for the Creative Commons license step in the submission process of either the JSP or XML User Interface (JSP UI or XML UI). Submitters are given an opportunity to select a Creative Common license to accompany the item. Creative Commons licenses govern the use of the content. For further details, refer to the Creative Commons website at http://creativecommons.org .
Creative Commons licensing is enabled as one step of the configurable submission process, and therefore optionally available and may be configured for any given collection that has a defined submission sequence, or be part of the "default" submission process. This process is described in the "Customizing and Configuring Submission User Interface" section of this manual. There is a Creative Commons step already defined (step 5), but it is commented out, so enabling Creative Commons licensing is typically just a matter of uncommenting the CC License step.
For the JSP UI, Creative Commons licensing is effected by opening an Iframe captured slightly differently in each UI:
The following configurations (in dspace.cfg) relate to the XMLUI Creative Commons license process ONLY and capturing the selection result in several bitstreams, but the XML UI utilizes a more flexible web service. By default, when a license is selected in the interface, the URI for the license is stored in the 'dc.rights.uri' metadata field for the Item, and a representation of the license text is stored in a license bundle. In addition, the following properties in [dspace]/config/dspace.cfg
may be customized for use:
Property: |
|
Example Value: |
|
Informational Note: |
|
Property: |
|
Example Value: |
|
Informational Note: |
|
Property: |
|
Example Value: |
|
Informational Note: |
|
Property: |
|
Example Value: |
|
Informational Note: |
|
Property: |
|
Example Value: |
|
Informational Note: |
|
Property: |
|
Example Value: |
|
Informational Note: |
|
Property: |
|
Example Value: |
|
Informational Note: | Should a jurisdiction be used? If so, which one? See http://creativecommons.org/international/ for a list of possible codes (e.g. nz = New Zealand, uk = England and Wales, jp = Japan) |
...
Property: | webui.licence_bundle.show | ||
Example Value: | webui.licence_bundle.show = false | ||
Informational Note: | Sets whether to display the contents of the license bundle (often just the deposit license in the standard DSpace installation). | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Controls whether to display thumbnails on browse and search result pages. If you have customized the Browse columnlist, then you must also include a "thumbnail" column in your configuration. _(This configuration property key is not used by XMLUI. To show thumbnails using XMLUI, you need to create a theme which displays them)._ | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This property determines the maximum height of the browse/search thumbnails in pixels (px). This only needs to be set if the thumbnails are required to be smaller than the dimensions of thumbnails generated by MediaFilter. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This determines the maximum width of the browse/search thumbnails in pixels (px). This only needs to be set if the thumbnails are required to be smaller than the dimensions of thumbnails generated by MediaFilter. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This determines whether or not to display the thumbnail against each bitstream. (This configuration property key is not used by XMLUI. To show thumbnails using XMLUI, you need to create a theme which displays them). | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This determines where clicks on the thumbnail in browse and search screens should lead. The only values currently supported are "item" or "bitstream", which will either take the user to the item page, or directly download the bitstream. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This property sets the maximum width of generated thumbnails that are being displayed on item pages. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This property sets the maximum height of generated thumbnails that are being displayed on item pages. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Whether or not the user can "preview" the image. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This property sets the maximum width for the preview image. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This property sets the maximum height for the preview image. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This is the brand text that will appear with the image. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | An abbreviated form of the full Branded Name. This will be used when the preview image cannot fit the normal text. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | The height (in px) of the brand. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This property sets the font for your Brand text that appears with the image. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This property sets the font point (size) for your Brand text that appears with the image. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | The Dublin Core field that will display along with the preview. This field is optional. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Determines if communities and collections should display item counts when listed. The default behavior if omitted, is true. (This configuration property key is not used by XMLUI. To show strengths using XMLUI, you need to create a theme which displays them).false. | ||
Property: |
| Property: |
|
Example Value: |
| ||
Informational Note: | When showing the strengths, should they be counted in real time, or fetched from the cache. Counts fetched in real time will perform an actual count of the database contents every time a page with this feature is requested, which will not scale. If you set the property key is set to cache ("true") you must run the following command periodically to update the count: |
...
Property: |
|
Example Value: |
|
Informational Note: |
|
Apart from the single (type=metadata) and full (type=item) browse pages, tag cloud is a new way to display the unique values of a metadata field.
To enable “tag cloud” browsing for a specific index you need to declare it in the dspace.cfg configuration file using the following option:
Property: | webui.browse.index.tagcloud.<n> |
Example Value: | webui.browse.index.tagcloud.1 = true |
Class | Note |
---|---|
tagcloud | General class for the whole tagcloud |
tagcloud_1 | Specific tag class for tag of type 1 (baed on score) |
tagcloud_2 | Specific tag class for tag of type 2 (baed on score) |
tagcloud_3 | Specific tag class for tag of type 3 (baed on score)Informational Note: Enable/Disable tag cloud in browsing for a specific index. ‘n’ is the index number of the specific index which needs to be of type ‘metadata’.Possible values: true, false Default value is false. If no option exists for a specific index, it is assumed to be false. You do not have to re-index discovery when you change this configuration |
Tag cloud configuration
The appearance configuration for the tag cloud is located in the Discovery xml configuration file (dspace/config/spring/api/discovery.xml). Without configuring the appearance, the default one will be applied to the tag cloud
In this file, there must be a bean named “browseTagCloudConfiguration” of class “org.dspace.discovery.configuration.TagCloudConfiguration”. This bean can have any of the following properties. If some is missing, the default value will be applied.
displayScore | Should display the score of each tag next to it? Default: false |
shouldCenter | Should display the tag as center aligned in the page or left aligned? Possible values: true | false. Default: true |
totalTags | How many tags will be shown. Value -1 means all of them. Default: -1 |
cloudCase | The letter case of the tags. Possible values: Case.LOWER | Case.UPPER | Case.CAPITALIZATION | Case.PRESERVE_CASE | Case.CASE_SENSITIVE Default: Case.PRESERVE_CASE |
randomColors | If the 3 css classes of the tag cloud should be independent of score (random=yes) or based on the score. Possible values: true | false . Default: true |
fontFrom | The font size (in em) for the tag with the lowest score. Possible values: any decimal. Default: 1.1 |
fontTo | The font size (in em) for the tag with the lowest score. Possible values: any decimal. Default: 3.2 |
cuttingLevel | The score that tags with lower than that will not appear in the rag cloud. Possible values: any integer from 1 to infinity. Default: 0 |
ordering | The ordering of the tags (based either on the name or the score of the tag) Possible values: Tag.NameComparatorAsc | Tag.NameComparatorDesc | Tag.ScoreComparatorAsc | Tag.ScoreComparatorDesc Default: Tag.GreekNameComparatorAsc |
When tagCloud is rendered there are some CSS classes that you can change in order to change the tagcloud appearance.
|
...