Page History
...
Configuring Lucene Search Indexes
Info |
---|
DSpace also provide provides a more advanced search module named Discovery that is (based on Apache SOLR and provide ) with additional features, such as filtering/faceting, hit highlighting, search snippets, etc. See Discovery This paragraph is related to the "traditional" DSpace lucene based search engine (based on Apache Lucene) and does not apply to Discovery. |
Search indexes can be configured and customized easily in the dspace.cfg file. This allows institutions to choose which DSpace metadata fields are indexed by Lucene.
...
Delegation Administration : Authorization System Configuration
(Authorization System Configuration)
It is possible to delegate the administration of Communities and Collections. This functionality eliminates the need for an Administrator Superuser account for these purposes. An EPerson that will be attributed Delegate Admin rights for a certain community or collection will also "inherit" the rights for underlying collections and items. As a result, a community admin will also be collection admin for all underlying collections. Likewise, a collection admin will also gain admin rights for all the items owned by the collection.
...
Community Administration: Subcommunities and Collections | |||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to create subcommunities or collections. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to delete subcommunities or collections. | ||
Community Administration: Policies and The group of administrators | |||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to administrate the community policies. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to edit the group of community admins. | ||
Community Administration: Collections in the above Community |
| ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to administrate the policies for underlying collections. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to administrate the item template for underlying collections. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to administrate the group of submitters for underlying collections. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to administrate the workflows for underlying collections. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to administrate the group of administrators for underlying collections. | ||
Community Administration: Items Owned by Collections in the Above Community | |||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to delete items in underlying collections. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to withdraw items in underlying collections. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to reinstate items in underlying collections. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to administrate item policies in underlying collections. | ||
Community Administration: Bundles of Bitstreams, related to items owned by collections in the above Community | |||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to create additional bitstreams in items in underlying collections. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to delete bitstreams from items in underlying collections. | ||
Property: |
| ||
Example Value: |
| ||
Informational Note: | Authorization for a delegated community administrator to administer licenses from items in underlying collections. | ||
Community Administration: |
| ||
Collection Administration: |
| ||
Collection Administration: |
| ||
Item Administration. |
| ||
Item Administration: |
|
Oracle users should consult Chapter 4 Updating a DSpace Installation regarding the necessary database changes that need to take place.
Restricted Item Visibility Settings
...
General Web User Interface Configurations
In this section of Configuration, we address the agnostic WEB User Interface that is used for JSP UI JSPUI and XML UIXMLUI. Some of the configurations will give information towards customization or refer you to the appropriate documentation.
...
Property: |
|
Example Value: | {{webui.browse.index.1 = dateissued:metadata:dc.date.issued:date:full }} |
Informational Note: | This is an example of how one "Defines the Indexes". See Defining the Indexes in the next sub-section. |
Property: |
|
Example Value: |
|
Informational Note: | This is an example of how one "Defines the Sort Options". See Defining Sort Options in the following sub-section. |
Defining the storage of the Browse Data
...
Info |
---|
Starting from DSpace 3.0 you can configure which implementation use for the Browse DAOs both for create/update operations than for read operations.and for read operations. This allows you to customize which browse engine is utilized in your DSpace. Options include:
|
Property: |
|
Example Value: | browseDAO.class = org.dspace.browse.SolrBrowseDAO |
Informational Note: | This property configures the java class that is used for READ operations by the Browse System. You need to have Discovery enabled to use the SOLR Browse DAOs |
Property: |
|
Example Value: |
|
Informational Note: | This property configures the java class that is used for WRITE operations by the Browse System. You need to have Discovery enabled to use the SOLR Browse DAOs |
Note |
---|
If a DAOs configuration is not provided the system will use the out-of-box implementation available for your DMBS Database of choice (PostgreSQL or Oracle). |
Configure the browse
...
engine to use SOLR
...
Warning |
---|
Use of SOLR DAOs for the Browse System Engine requires that you have Discovery enabled. Please check the Discovery configuration section. |
This option enables the browse engine to store its indexes in Apache Solr. This essentially allows Discovery to be used for both search & browse within DSpace. The configuration is as followfollows
Code Block |
---|
browseDAO.class = org.dspace.browse.SolrBrowseDAO browseCreateDAO.class = org.dspace.browse.SolrBrowseCreateDAO |
Configure the browse
...
engine to use PostgreSQL
...
This option enables the browse engine to store its indexes in PostgreSQL database tables. All browsing is then performed via queries to those database tables. This is the traditional browsing option for users of PostgreSQL. The the configuration is as followfollows
Code Block |
---|
browseDAO.class = org.dspace.browse.BrowseDAOPostgres browseCreateDAO.class = org.dspace.browse.BrowseCreateDAOPostgres |
Configure the browse
...
engine to use Oracle
...
This option enables the browse engine to store its indexes in Oracle database tables. All browsing is then performed via queries to those database tables. This is the traditional browsing option for users of Oracle. The configuration is as followfollows
Code Block |
---|
browseDAO.class = org.dspace.browse.BrowseDAOOracle browseCreateDAO.class = org.dspace.browse.BrowseCreateDAOOracle |
...