Skip to end of metadata
Go to start of metadata

CollectionSpace v4.4 Development Dates

Design and development: 8 February - 30 June 2016 (Sprint Dates)

Code freeze: 1 July 2016

QA: 4 July - 21 July 2016

Release: 25 July 2016

Installing and Configuring CollectionSpace

For instructions on installing and configuring CollectionSpace, following this link: CollectionSpace Release Documentation

Overview

Areas of work included with CollectionSpace Release 4.4 are listed below.

  • Continued work on the community of practice profiles, including:
    • Final implementation and release of the  Herbarium  profile and related extensions.
    • Final implementation and release of the Local History and Material Culture profile and related extensions.
    • Implementation and release of the Bonsai profile and related extensions
    • Implementation and release of the Materials profile and related extensions
  • Design and development of a shared authority service CSPACE-6905 - Work related to shared authorities Open
  • Additional refactoring and acceptance of a Django-based community-contributed framework for web applications, that uses CollectionSpace data and APIs.  CSPACE-6758 - Django Webapp Contributions In Progress
  • Expanding the number of automated tests for quality assurance.  CSPACE-6754 - Automating QA test plans Open
  • Updates to the reporting software and documentation. 
    • Continued improvement of end-user documentation pertaining to reporting.
    • A number of new "canned" reports available for use in all CSpace deployments: Currently Available Reports
  • Other bug fixes as prioritized by the CollectionSpace community.

For the current list of issues - bug fixes, feature enhancements, and more, please see the 4.4 issues filter in the project's issue tracker.

Release Notes

  • Added support for "property-value-variables" for the Application layer's tenant settings.xml configuration files.  A property-value-variable is of the form ${foo} where foo is the name of an environment variable.  A property-value-variable will get substituted with the value of the corresponding environment variable value.  For example, if an environment variable named foo exists with a value of "bar" then the property-value-variable ${foo} would be replaced with "bar".  Use property-value-variables for things like passwords which you don't want in the tenant settings.xml files.
  • Added Application layer configuration for enabling/disabling tenants/profiles. In the <persistence> element of each tenant's settings.xml file, you'll find a Boolean-valued element <create-disabled>. A value of true marks the tenant as disabled and false as enabled. Most of the profile tenants' use a property-value-variable of ${CSPACE_TENANT_CREATE_DISABLED_OPT} for the <create-disabled> element. If the environment variable CSPACE_TENANT_CREATE_DISABLED_OPT is set, CollectionSpace will use its value to fill out the <create-disabled> value; otherwise, a default value of true will be used.
    If you change a tenant's <create-disabled> value, you'll need to rebuild the Application layer (mvn clean install -DskipTests) and redeploy the Services layer (ant deploy import).
  • Now testing and evaluating limited functionality for a Shared Authority Server. When configured correctly, a CollectionSpace instance's authorities and vocabularies can be synchronized (server to client synchronization only) with another CollectionSpace instance. This allows the sharing of authorities and vocabularies between CollectionSpace instances. See "Configuring to synchronize with another CollectionSpace instance" for details.
  • No labels