Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

 

Released: 03.03 2013.

 

Highlights

Support for multiple collections in the same bitrepository installation

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.

New web gui for the reference services

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:

  • The old GUI is stilla available but has been deprecated. All new functionality will only be added to the new GUI, this includes support for multiple collections.
  • Access to the different protokol operations should now be done through the command line client.
  • The new GUI is based on twitter bootstrap.
  • Detailed information access has been added to many of the information elements on the GUI. This means it is possible to click on GUI elements to show the next level of details for this information.
  • The new GUI has support for multiple collection.
  • The different services are now access through individual url's. This makes it easy to link directly to a service GUI.

Updating from 0.23

See RepositorySettings 10  for CollectionSettings 0.9 -> RepositorySettings 10 upgrade.

ReferenceSettings

type key priority summary

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

type key priority summary fixversion

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels