Released: 15.05 2013.
This is a major release which changes the previous paradigm of one collection pr. bitrepository to allow many collections in the same bitrepository. This means that where the CollectionID was previously always the same throughout a installation, and were therefore mostly implied, a CollectionID is now necessary to access most of the functionality in the system.
The set of collections are defined in the RepositorySettings (formerly CollectionSettings), where each collection has a list of pillars defined.
The previous web GUI was evolved from the initial test GUI, and as for some while needed a redesign. As the focus on the web GUI has been increasing during the last periode, the GUI for the services have been reimplemented. This means:
A untested version of the client was available in the 0.23 release. The 0.24 command line client has been improved with
A list of know bugs has also been created for the cmd client, see the 'Uncovered bugs' listing below to view the complete list.
See RepositorySettings 10 for CollectionSettings 0.9 -> RepositorySettings 10 upgrade.
FileDir settings in the
PillarSettings have been replaced by a
CollectionDirs defining the directories to map the files stored for the collections. Each CollectionDirs maps a list of collectionID which should be mapped to a set of dirs. If no collectionIDs are defined in a
CollectionDirs element, the dir file be used as the default dir.
Example (where one collection has explicitly defined file-dirs and all other collections use the default file-archive dir):
<CollectionDirs> <CollectionID>collection1</CollectionID> <FileDirs>/data1/filedir</FileDirs> <FileDirs>/data2/filedir</FileDirs> </CollectionDirs> <CollectionDirs> <FileDirs>./file-archive</FileDirs> </CollectionDirs>
The data for each collection is separated beneath each filedir in folders matching the name of the given collection.
AuditTrailPreservationCollectionelement has been added to the
AuditTrailServiceSettingssettings, defining the collection the AuditTrails should be backed up to.
All Derby databases will automatically be updated when the system first starts after the update. This is due to the introduction of the collectionID on many tables.
The directories in the previous FileDir has to be moved into a folder with the name of the collection, which the files belong to. E.g.: