Version 4.0 of CollectionSpace has been released:
http://wiki.collectionspace.org/display/collectionspace/Release+4.0
This version reflects a major effort towards simplifying the task of
configuring CollectionSpace to meet the specific needs of your museum,
making this task both faster and easier.
On its surface, version 4.0 looks very much like its predecessor,
version 3.3, with the addition of a Work authority for citing cultural
works. However, due to changes under version 4.0's surface, you can
now typically add a new field (or change the behavior of an existing
field) in an object, procedural, or authority term record, just by
adding or editing several lines in one or two configuration files; (if
necessary) editing the HTML template file for that record; and running
an automated task that builds everything else needed.
If you're evaluating a future implementation or upgrading an
existing system, we encourage you to seriously consider this release
as your baseline.
You can install and explore version 4.0 today; see the installation
documentation at:
http://wiki.collectionspace.org/display/DOC/Installing+CollectionSpace
Please also note that documentation on configuring version 4.0, to
adapt it for your museum, is slated to start appearing on the
Documentation wiki during Fall 2013 and beyond. (Due to the major
changes in this release, existing documentation will change
significantly in turn.)
On behalf of the CollectionSpace project team, and everyone who
contributed to this release,
Aron Roberts
UC Berkeley
P.S. If you'd like to experiment right away with configuring a v4.0
system, by adding or changing fields or other behaviors, you can
explore examples of custom configuration in the demonstration Lifesci
tenant:
https://github.com/collectionspace/application/tree/v4.0/tomcat-main/src/main/resources/tenants/lifesci
As well, you can find notes from a successful (test) migration from
v3.3 to v4.0 of a museum with extensive existing configuration
changes, in the first and third comments on this issue:
http://issues.collectionspace.org/browse/PAHMA-933
Version 4.0 of CollectionSpace has been released:
http://wiki.collectionspace.org/display/collectionspace/Release+4.0
This version reflects a major effort towards simplifying the task of
configuring CollectionSpace to meet the specific needs of your museum,
making this task both faster and easier.
On its surface, version 4.0 looks very much like its predecessor,
version 3.3, with the addition of a Work authority for citing cultural
works. However, due to changes under version 4.0's surface, you can
now typically add a new field (or change the behavior of an existing
field) in an object, procedural, or authority term record, just by
adding or editing several lines in one or two configuration files; (if
necessary) editing the HTML template file for that record; and running
an automated task that builds everything else needed.
If you're evaluating a future implementation or upgrading an
existing system, we encourage you to seriously consider this release
as your baseline.
You can install and explore version 4.0 today; see the installation
documentation at:
http://wiki.collectionspace.org/display/DOC/Installing+CollectionSpace
Please also note that documentation on configuring version 4.0, to
adapt it for your museum, is slated to start appearing on the
Documentation wiki during Fall 2013 and beyond. (Due to the major
changes in this release, existing documentation will change
significantly in turn.)
On behalf of the CollectionSpace project team, and everyone who
contributed to this release,
Aron Roberts
UC Berkeley
P.S. If you'd like to experiment right away with configuring a v4.0
system, by adding or changing fields or other behaviors, you can
explore examples of custom configuration in the demonstration Lifesci
tenant:
https://github.com/collectionspace/application/tree/v4.0/tomcat-main/src/main/resources/tenants/lifesci
As well, you can find notes from a successful (test) migration from
v3.3 to v4.0 of a museum with extensive existing configuration
changes, in the first and third comments on this issue:
http://issues.collectionspace.org/browse/PAHMA-933
