Areas of work for CollectionSpace Release 4.3 are listed below.
For the list of resolved issues - bug fixes, feature enhancements, and more, please see the 4.3 issues filter in the project's issue tracker.
We've update the automated installer for performing an unattended installation of a CollectionSpace 4.3 server on selected Linux systems.
An additional environment variable named JEE_PORT is required to build and deploy CollectionSpace v4.3.
Beginning with version v4.3, you can configure CollectionSpace to work with an Elasticsearch cluster. To learn more about Elasticsearch follow this link: https://www.elastic.co/guide/en/elasticsearch/reference/1.7/getting-started.html
To use CollectionSpace with Elasticsearch, you'll first need to download and install Elasticsearch 1.7.x. As of v4.3, CollectionSpace works with Elasticsearch v1.7.x (does not work yet with v2.x of Elasticsearch). You can download it here: https://www.elastic.co/downloads/past-releases/elasticsearch-1-7-4 You can learn how to setup an Elasticsearch cluster by following this link:https://www.elastic.co/guide/en/elasticsearch/reference/1.7/setup.html. The default configuration will create a cluster named "elasticsearch" which is the cluster CollectionSpace will attempt to work with by default.
By default, CollectionSpace will attempt to connect to an Elasticsearch cluster named "elasticsearch" running on the same server. You can point CollectionSpace to a different cluster by changing the configuration file at '$CSPACE_JEESERVER_HOME/cspace/config/services/proto-elasticsearch-config.xml' and restarting the CollectionSpace server.
Be sure your Elasticsearch cluster is running before you start the CollectionSpace server. This will ensure that all your CollectionSpace collection data will be indexed by Elasticsearch.