I've blogged about Kete before - version 1.1 has been released.
From the announcement:
Kete 1.1 is now available with a giant helping of new features and improvements. This is also the first release where you can grab Kete from our code repository's new home at Github.com. See http://kete.net.nz/site/topics/show/25-downloads for details or browse the code online at http://github.com/kete/kete/.
For those who haven't seen Kete in action, Kete is open source software that enables communities, whether the community is a town or a company, to collaboratively build their own digital libraries, archives and repositories. Kete combines features from Knowledge and Content Management Systems as well as collaboration tools such as wikis, blogs, tags, and online forums to make it easy to add and relate content on a Kete site. You could create a service like Google's Knol for your community using Kete.
An in-depth list of features and issues resolved can be found at http://kete.net.nz/documentation/topics/show/182-kete-11-features-and-bug-fixes , but here are some highlights:
- Privacy Control - ability to designate any item version within a basket as only viewable to its members (guide at http://kete.net.nz/documentation/topics/show/191-use-privacy-controls-on-whole-site-or-a-specific-basket)
- Content Licensing - users can choose from Kete instance's available Licenses for a piece of content they create. Creative Commons licenses are available to be loaded as license options with one command on the server. (guide at http://kete.net.nz/documentation/topics/show/181-using-content-licenses-in-kete-11)
- OAI-PMH Repository - an Kete instance can optionally answer OAI-PMH harvester requests for its content. (guide at http://kete.net.nz/documentation/topics/show/190-turning-on-ketes-oai-pmh-repository)
- Force use of SSL Encryption on Private Items and User Account Information (optional) - Kete now can be configured to use HTTPS for all sensitive areas (login, registration, private items, certain administrator functionality). (guide at http://kete.net.nz/documentation/topics/show/172-forcing-kete-to-use-ssl-for-private-requests)