All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
For ease of use, the Configuration documentation is broken into several parts:
dspace.cfg
file settings...
Wiki Markup |
---|
The "source" file that is found in {{\[DSDOCDEV:dspace-source\]/dspace/config/dspace.cfg}} |
Wiki Markup |
---|
The "runtime" file that is found in {{\[DSDOCDEV:dspace\]/config/dspace.cfg}}
The runtime file is supposed to be the *copy* of the source file, which is considered the master version. However, the DSpace server and command programs only look at the _runtime_ configuration file, so when you are revising your configuration values, it is tempting to _only edit the runtime file_. *DO NOT* do this. Always make the same changes to the source version of {{dspace.cfg}} in addition to the runtime file. The two files should always be identical, since the source {{dspace.cfg}} will be the basis of your next upgrade. |
Wiki Markup |
---|
To keep the two files in synchronization, you can edit your files in {{\[DSDOCDEV:dspace-source\]/dspace/config/}} and then you would run the following commands: |
...
Wiki Markup |
---|
This will copy the source {{dspace.cfg}} (along with other configuration files) into the runtime ({{\[DSDOCDEV:dspace\]/config}}) directory. |
...
Wiki Markup |
---|
Run {{ant \-Dconfig=\[DSDOCDEV:dspace\]/config/dspace.cfg update}} if you are updating your {{dspace.cfg}} file and wish to see the changes appear. Follow the usual sequence with copying your webapps. |
Wiki Markup |
---|
If you edit _dspace.cfg_ in _\[DSDOCDEV:dspace-source\]/dspace/config/_, you should then run '_ant init_configs_' in the directory _\[DSDOCDEV:dspace-source\]/dspace/target/dspace-1.5.2-build.dir_ so that any changes you may have made are reflected in the configuration files of other applications, for example Apache. You may then need to restart those applications, depending on what you changed. |
...
Property: | |
Example Value: | |
Informational Note: | Root directory of DSpace installation. Omit the trailing '/'. Note that if you change this, there are several other parameters you will probably want to change to match, e.g. |
Property: | |
Example Value: | |
Informational Note: | Fully qualified hostname; do not include port number. |
Property: | |
Example Value: | http://dspacetest.myu.edu:8080 |
Informational Note: | Main URL at which DSpace Web UI webapp is deployed. Include any port number, but do not include the trailing ' |
Property: | |
Example Value: | |
Informational note | DSpace base URL. URL that determines whether JSPUI or XMLUI will be loaded by default. Include port number etc., but NOT trailing slash. Change to |
Property: | |
Example Value: | |
Informational note: | The base URL of the OAI webapp (do not include /request). |
Property: | |
Example Value: | |
Informational Note: | Short and sweet site name, used throughout Web UI, e-mails and elsewhere (such as OAI protocol) |
...
Wiki Markup |
---|
Sometimes DSpace automatically sends e-mail messages to users, for example, to inform them of a new work flow task, or as a subscription e-mail alert. The wording of emails can be changed by editing the relevant file in {{\[DSDOCDEV:dspace\]/config/emails}} . Each file is commented. Be careful to keep the right number 'placeholders' (e.g._\{2\}_). |
...
DSpace supports two distinct options for storing your repository bitstreams (uploaded files). The files are not stored in the database in which Metadata, user information, ... are stored. An assetstore is a directory on your server, on which the bitstreams are stored and consulted afterwards. The usage of different assetstore directories is the default "technique" in DSpace. The parameters below define which assetstores are present, and which one should be used for newly incoming items. As an alternative, DSpace can also use SRB (Storage Resource Brokerage) as an alternative. See DSDOCDEV:SRB File Storage for details regarding SRB.
Property: | | ||
Example Value: | | ||
Informational Note: | This is Asset (bitstream) store number 0 (Zero). You need not place your assetstore under the /dspace directory, but may want to place it on a different logical volume on the server that DSpace resides. So, you might have something like this: | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | This property specifies extra asset stores like the one above, counting from one (1) upwards. This property is commented out (#) until it is needed. | ||
Property: | | ||
Example Value: | | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="118a5f7bc5d6a496-0d154515-43144e40-8f088376-aabfc06a43d7e0ed052719a1"><ac:plain-text-body><![CDATA[ | Informational Note: | Informational Note: Specify the number of the store to use for new bitstreams with this property. The default is 0 [DSDOCDEV:zero] which corresponds to the 'assestore.dir' above. As the asset store number is stored in the item metadata (in the database), always keep the assetstore numbering consistent and don't change the asset store number in the item metadata. | ]]></ac:plain-text-body></ac:structured-macro> |
...
Wiki Markup |
---|
After changing the configuration run {{/\[DSDOCDEV:dspace\]/bin/dspace index-init}} to regenerate the indexes. |
...
Property: | |
Example Value | handle.canonical.prefix = http://hdl.handle.net/
|
Informational Note: | Canonical Handle URL prefix. By default, DSpace is configured to use http://hdl.handle.net/ as the canonical URL prefix when generating |
Property: | |
Example Value | |
Informational Note: | The default installed by DSpace is |
Property: | |
Example Value: | |
Informational Note: | The default files, as shown in the Example Value is where DSpace will install the files used for the Handle Server. |
...
Properties: | | ||
Example Values: | | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="d32bde5e0e8c88dd-06f059df-4f684ac0-b1c8a360-ade90b481323d3a81063b98f"><ac:plain-text-body><![CDATA[ | Informational Note: | This defines a crosswalk named MODS whose configuration comes from the file | ]]></ac:plain-text-body></ac:structured-macro> |
...
Wiki Markup |
---|
{{crosswalk}} first part of the property key. {{submission}} second part of the property key. {{PluginName}} is the name of the plugin. The _path_ value is the path to the file containing the crosswalk stylesheet (relative to {{/\[DSDOCDEV:dspace\]/config}}). Here is an example that configures a crosswalk named "LOM" using a stylesheet in {{\[DSDOCDEV:dspace\]/config/crosswalks/d-lom.xsl}}: {{crosswalk.submission.LOM.stylesheet = crosswalks/d-lom.xsl}} A dissemination crosswalk can be configured by starting with the property key _crosswalk.dissemination_. Example: {{crosswalk.dissemination.PluginName.stylesheet = path}} The _PluginName_ is the name of the plugin (\!) . The _path_ value is the path to the file containing the crosswalk stylesheet (relative to {{/\[DSDOCDEV:dspace\]/config}}). |
You can make two different plugin names point to the same crosswalk, by adding two configuration entries with the same path:
...
Wiki Markup |
---|
In the property key "{{crosswalk.qdc.properties.QDC}}" the value of this property is a path to a separate properties file containing the configuration for this crosswalk. The pathname is relative to the DSpace configuration directory {{/\[DSDOCDEV:dspace\]/config}} . Referring back to the "Example Value" for this property key, one has {{crosswalks/qdc.properties}} which defines a crosswalk named {{QDC}} whose configuration comes from the file {{\[DSDOCDEV:dspace\]/config/crosswalks/qdc.properties}} . |
...
Wiki Markup |
---|
Expose the metadata field. Edit _\[DSDOCDEV:dspace\]/config/input-forms.xml_ . If you have only one form‚ usually 'traditional', add it there. If you have multiple forms, add it only to the forms linked to collections for which embargo applies: |
Code Block |
---|
<form name="traditional"> <page number="1"> ... <field> <dc-schema>dc</dc-schema> <dc-element>description</dc-element> <dc-qualifier>embargo</dc-qualifier> <repeatable>false</repeatable> <label>Embargo Date</label> <input-type>onebox</input-type> <hint>If required, enter date 'yyyy-mm-dd' when embargo expires or 'forever'.</hint> <required></required> </field> |
Wiki Markup |
---|
Configure Embargo. Edit _\[DSDOCDEV:dspace\]/config/dspace.cfg_. Find the Embargo properties and set these two: |
Code Block |
---|
# DC metadata field to hold the user-supplied embargo terms embargo.field.terms = dc.description.embargo # DC metadata field to hold computed "lift date" of embargo embargo.field.lift = dc.description.embargo |
Wiki Markup |
---|
Periodically run the lifter. Run the task:_\[DSDOCDEV:dspace\]/bin/dspace embargo-lifter_You will want to run this task in a cron-scheduled or other repeating way. Item embargoes will be lifted as their dates pass. |
Wiki Markup |
---|
Expose the 'term' metadata field. The lift field will be assigned by the embargo system, so it should not be exposed directly. Edit _\[DSDOCDEV:dspace\]/config/input-forms.xml_ . If you have only one form (usually 'traditional') add it there. If you have multiple forms, add it only to the form(s) linked to collection(s) for which embargo applies. First, add the new field to the 'form definition': |
Code Block |
---|
<form name="traditional"> <page number="1"> ... <field> <dc-schema>dc</dc-schema> <dc-element>embargo</dc-element> <dc-qualifier>terms</dc-qualifier> <repeatable>false</repeatable> <label>Embargo Terms</label> <input-type value-pairs-name="embargo_terms">dropdown</input-type> <hint>If required, select embargo terms.</hint> <required></required> </field> |
Code Block |
---|
<form-value-pairs> ... <value-pairs value-pairs-name="embargo_terms" dc-term="embargo.terms"> <pair> <displayed-value>90 days</displayed-value> <stored-value>90 days</stored-value> </pair> <pair> <displayed-value>6 months</displayed-value> <stored-value>6 months</stored-value> </pair> <pair> <displayed-value>1 year</displayed-value> <stored-value>1 year</stored-value> </pair> </value-pairs> |
Code Block |
---|
# DC metadata field to hold the user-supplied embargo terms embargo.field.terms = dc.embargo.terms # DC metadata field to hold computed "lift date" of embargo embargo.field.lift = dc.embargo.lift # implementation of embargo setter plugin - replace with local implementation if applicable plugin.single.org.dspace.embargo.EmbargoSetter = org.dspace.embargo.DayTableEmbargoSetter |
...
Wiki Markup |
---|
Periodically run the lifter. Run the task:
{{\[DSDOCDEV:dspace\]/bin/dspace embargo-lifter}} .
You will want to run this task in a cron-scheduled or other repeating way. Item embargoes will be lifted as their dates pass. |
...
Wiki Markup |
---|
DSpace now comes with a Checksum Checker script ({{\[DSDOCDEV:dspace\]/bin/dspace checker}}) which can be scheduled to verify the checksum of every item within DSpace. Since DSpace calculates and records the checksum of every file submitted to it, this script is able to determine whether or not a file has been changed (either manually or by some sort of corruption or virus). The idea being that the earlier you can identify a file has changed, the more likely you'd be able to recover it (assuming it was not a wanted change). |
...
Wiki Markup |
---|
This enables 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|http://creativecommons.org|http://creativecommons.org] . Creative Commons licensing is enabled as one step of the configurable submission process, and therefore 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 to the Creative Commons site 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 {{\[DSDOCDEV:dspace\]/config/dspace.cfg}} may be customized for use: |
...
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 thumbnails using XMLUI, you need to create a theme which displays them). | ||
Property: | | ||
Example Value: | | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="8fe158bbf33457f0-2759a03e-451844cd-9a758b33-9867e533615f5e491546dedf"><ac:plain-text-body><![CDATA[ | 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: | ]]></ac:plain-text-body></ac:structured-macro> |
...
Property: | | ||
Example Value: | | ||
Informational Note: | By default, RSS feeds are set to true (on) . Change key to "false" to disable. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | Defines the number of DSpace items per feed (the most recent submissions) | ||
Property: | | ||
Example Value: | | ||
Informational Note: | Defines the maximum number of feeds in memory cache. Value of " | ||
Property: | | ||
Example Value: | | ||
Informational Note: | Defines the number of hours to keep cached feeds before checking currency. The value of "0" will force a check with each request. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | Defines which syndication formats to offer. You can use more than one; use a comma-separated list. The following list are the available values: rss_0.90, rss_0.91, rss_0.92, rss_0.93, rss_0.94, rss_1.0, rss_2.0, atom_1.0. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | By default, (set to false), URLs returned by the feed will point at the global handle resolver (e.g. http://hdl.handle.net/123456789/1). If set to true the local server URLs are used (e.g. http://myserver.myorg/handle/123456789/1). | ||
Property: | | ||
Example Value: | | ||
Informational Note: | This property customizes each single-value field displayed in the feed information for each item. Each of the fields takes a single metadata field. The form of the key is <scheme prefix>.<element>.<qualifier> In place of the qualifier, one may leave it blank to exclude any qualifiers or use the wildcard "*" to include all qualifiers for a particular element. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | This property customizes each single-value field displayed in the feed information for each item. Each of the fields takes a single metadata field. The form of the key is <scheme prefix>.<element>.<qualifier> In place of the qualifier, one may leave it blank to exclude any qualifiers or use the wildcard "*" to include all qualifiers for a particular element. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | One can customize the metadata fields to show in the feed for each item's description. Elements are displayed in the order they are specified in dspace.cfg.Like other property keys, the format of this property key is: webui.feed.item.description = <scheme prefix>.<element>.<qualifier>. In place of the qualifier, one may leave it blank to exclude any qualifiers or use the wildcard "*" to include all qualifiers for a particular element. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | The name of field to use for authors (Atom only); repeatable. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | Customize the image icon included with the site-wide feeds. This must be an absolute URL. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | This optional property adds structured DC elements as XML elements to the feed description. They are not the same thing as, for example, webui.feed.item.description. Useful when a program or stylesheet will be transforming a feed and wants separate author, description, date, etc. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | This optional property adds structured DC elements as XML elements to the feed description. They are not the same thing as, for example, webui.feed.item.description. Useful when a program or stylesheet will be transforming a feed and wants separate author, description, date, etc. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | This optional property adds structured DC elements as XML elements to the feed description. They are not the same thing as, for example, webui.feed.item.description. Useful when a program or stylesheet will be transforming a feed and wants separate author, description, date, etc. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | This optional property enables Podcast Support on the RSS feed for the specified collection handles. The podcast is iTunes compatible and will expose the bitstreams in the items for viewing and download by the podcast reader. Multiple values are separated by commas. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | This optional property enables Podcast Support on the RSS feed for the specified community handles. The podcast is iTunes compatible and will expose the bitstreams in the items for viewing and download by the podcast reader. Multiple values are separated by commas. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | This optional property for Podcast Support, allows you to choose which MIME types of bitstreams are to be enclosed in the podcast feed. Multiple values are separated by commas. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | This optional property for the Podcast Support will allow you to use a value for a metadata field as a replacement for actual bitstreams to be enclosed in the RSS feed. A use case for specifying the external sourceuri would be if you have a non-DSpace media streaming server that has a copy of your media file that you would prefer to have the media streamed from. |
...
Property: | | ||
Example Value: |
| ||
Informational Note: | This is used to customize the DC metadata fields that display in the item display (the brief display) when pulling up a record. The format is: | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | When using "resolver" in webui.itemdisplay to render identifiers as resolvable links, the base URL is take from <code>webui.resolver.<n>.baseurl<code> where <code>webui.resolver.<n>.baseurl<code> matches the urn specified in the metadata value. The value is appended to the "baseurl" as is, so the baseurl needs to end with the forward slash almost in any case. If no urn is specified in the value it will be displayed as simple text. For the doi and hdl urn defaults values are provided, respectively http://dc.doi.org and http://hdl.handle.net are used. If a metadata value with style "doi", "handle" or "resolver" matches a URL already, it is simply rendered as a link with no other manipulation. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | Specify which strategy to use for select the style for an item. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | Specify which collections use which views by Handle. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Specify which metadata to use as name of the style | ||
Property: | | ||
Example Value: |
| ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="8d4ea6826eccdeaa-23372dfb-400e4a81-b768b73e-d2803a50bb78afdbadc3305f"><ac:plain-text-body><![CDATA[ | Informational Note: | Customize the DC fields to use in the item listing page. Elements will be displayed left to right in the order they are specified here. The form is <schema prefix>.<element>[.<qualifier> | DSDOCDEV:.*][DSDOCDEV:(date)], ... | |
Property: | | ||
Example Value: | | ||
Informational Note: | You can customize the width of each column with the following line--you can have numbers (pixels) or percentages. For the 'thumbnail' column, a setting of '*' will use the max width specified for browse thumbnails (cf. | ||
Property: |
| ||
Example Value: | _}} | ||
Informational Note: | You can override the DC fields used on the listing page for a given browse index and/or sort option. As a sort option or index may be defined on a field that isn't normally included in the list, this allows you to display the fields that have been indexed/sorted on. There are a number of forms the configuration can take, and the order in which they are listed below is the priority in which they will be used (so a combination of an index name and sort name will take precedence over just the browse name).In the last case, a sort option name will always take precedence over a browse index name. Note also, that for any additional columns you list, you will need to ensure there is an itemlist.<field name> entry in the messages file. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | This would display the date of the accession in place of the issue date whenever the dateaccessioned browsed index or sort option is selected. Just like webui.itemlist.columns, you will need to include a 'thumbnail' entry to display the thumbnails in the item list. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | As in the aforementioned property key, you can customize the width of the columns for each configured column list, substituting '.widths' for '.columns' in the property name. See the setting for webui.itemlist.widths for more information. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | You can also set the overall size of the item list table with the following setting. It can lead to faster table rendering when used with the column widths above, but not generally recommended. | ||
Property: | | ||
Example Value: | | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f06e006961865f76-cef97197-4e2f402f-9624a47d-d20272e49a28dfc491406f39"><ac:plain-text-body><![CDATA[ | Informational Note: | Enable or disable session invalidation upon login or logout. This feature is enabled by default to help prevent session hijacking but may cause problems for shibboleth, etc. If omitted, the default value is 'true'. [DSDOCDEV:Only used for JSPUI authentication]. | ]]></ac:plain-text-body></ac:structured-macro> |
Wiki Markup |
---|
\[DSDOCDEV:i18n -- Locales\] |
...
If you set webui.supported.locales make sure that all the related additional files for each language are available. LOCALE should correspond to the locale set in webui.supported.locales, e. g.: for webui.supported.locales = en, de, fr, there should be:
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/modules/jspui/src/main/resources/Messages.properties}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/modules/jspui/src/main/resources/Messages_en.properties}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/modules/jspui/src/main/resources/Messages_de.properties}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/modules/jspui/src/main/resources/Messages_fr.properties}}
\\
Files to be localized: |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/modules/jspui/src/main/resources/Messages_LOCALE.properties}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/input-forms_LOCALE.xml}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/default_LOCALE.license - should be pure ASCII}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/news-top_LOCALE.html}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/news-side_LOCALE.html}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/emails/change_password_LOCALE}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/emails/feedback_LOCALE}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/emails/internal_error_LOCALE}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/emails/register_LOCALE}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/emails/submit_archive_LOCALE}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/emails/submit_reject_LOCALE}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/emails/submit_task_LOCALE}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/emails/subscription_LOCALE}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace-source\]/dspace/config/emails/suggest_LOCALE}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace\]/webapps/jspui/help/collection-admin_LOCALE.html - in html keep the jump link as original; must be copied to \[DSDOCDEV:dspace-source\]/dspace/modules/jspui/src/main/webapp/help}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace\]/webapps/jspui/help/index_LOCALE.html - must be copied to \[DSDOCDEV:dspace-source\]/dspace/modules/jspui/src/main/webapp/help}} |
Wiki Markup |
---|
{{\[DSDOCDEV:dspace\]/webapps/jspui/help/site-admin_LOCALE.html - must be copied to \[DSDOCDEV:dspace-source\]/dspace/modules/jspui/src/main/webapp/help}} |
...
Wiki Markup |
---|
All the parameters mapping are defined in {{\[DSDOCDEV:dspace\]/config/sfx.xml}} file. The program will check the parameters in {{sfx.xml}} and retrieve the correct metadata of the item. It will then parse the string to your resolver. |
...
Wiki Markup |
---|
If there is no DOI for that item, it will search next query-pair based on the {{\[DSDOCDEV:dspace\]/config/sfx.xml}} and then so on. |
...
Wiki Markup |
---|
New vocabularies should be placed in {{\[DSDOCDEV:dspace\]/config/controlled-vocabularies/}} and must be according to the structure described. A validation XML Schema (named {{controlledvocabulary.xsd}}) is also available in that directory. |
Wiki Markup |
---|
Vocabularies need to be associated with the correspondent DC metadata fields. Edit the file {{\[DSDOCDEV:dspace\]/config/input-forms.xml}} and place a _"vocabulary"_ tag under the _"field"_ element that you want to control. Set value of the _"vocabulary"_ element to the name of the file that contains the vocabulary, leaving out the extension (the add-on will only load files with extension "*.xml"). For example: |
...
Property: | | ||
Example Value: | | ||
Informational Note: | Is used by the SolrLogger Client class to connect to the SOLR server over http and perform updates and queries. | ||
Property: | | ||
Example Value: | | ||
Informational Note: | Spiders file is utilized by the SolrLogger, this will be populated by running the following command: | ||
Property: | | ||
Example Value: | | ||
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="389698bea481edad-1a541d12-4572413a-9acbb5f6-5c7235ef05dafacdd6db087c"><ac:plain-text-body><![CDATA[ | Informational Note: | The following refers to the GeoLiteCity database file utilized by the LocationUtils to calculate the location of client requests based on IP address. During the Ant build process (both fresh_install and update) this file will be downloaded from [http://www.maxmind.com/app/geolitecity] if a new version has been published or it is absent from your | ]]></ac:plain-text-body></ac:structured-macro> |
Property: | | ||
Example Value: | | ||
Informational Note: | Timeout for the resolver in the DNS lookup time in milliseconds, defaults to 200 for backward compatibility; your system's default is usually set in | ||
Property: | | ||
Example Value: | | ||
Informational Note: | Enables access control restriction on DSpace Statistics pages, Restrictions are based on access rights to Community, Collection and Item Pages. This will require the user to sign on to see that statistics. Setting the statistics to "false" will make them publicly available. | ||
Property: | | ||
Example Value: | {{solr.statistics.logBots = true }} | ||
Informational Note: | Enable/disable logging of spiders in solr statistics. If false, and IP matches an address in solr.spiderips.urls, event is not logged. If true, event will be logged with the 'isBot' field set to true (see | ||
Property: | | ||
Example Value: | | ||
Informational Note: | Controls solr statistics querying to filter out spider IPs. False by default. | ||
Property: | {{solr.statistics.query.filter.isBot }} | ||
Example Value: | | ||
Informational Note: | Controls solr statistics querying to look at "isBot" field to determine if record is a bot. True by default. | ||
Property: | | ||
Example Value: |
| ||
Informational Note: | URLs to download IP addresses of search engine spiders from |
...
Wiki Markup |
---|
The _\[DSDOCDEV:dspace\]/config/registries_ directory contains three XML files. These are used to load the _initial_ contents of the Dublin Core Metadata registry and Bitstream Format registry and SWORD metadata registry. After the initial loading (performed by _ant fresh_install_ above), the registries reside in the database; the XML files are not updated. |
...
Wiki Markup |
---|
The bitstream formats recognized by the system and levels of support are similarly stored in the bitstream format registry. This can also be edited at install-time via _\[DSDOCDEV:dspace\]/config/registries/bitstream-formats.xml_ or by the administration Web UI. The contents of the bitstream format registry are entirely up to you, though the system requires that the following two formats are present: |
...