| | 10 | |
| | 11 | Major features: |
| | 12 | * Domain Model: Data and content "packages" with a standard set of core metadata and support for adding unlimited ''arbitrary'' additional metadata |
| | 13 | * All package data is automatically versioned in a wiki-like manner |
| | 14 | * Tagging of packages |
| | 15 | * Groups for controlled categorization of packages |
| | 16 | * Ratings |
| | 17 | * Unlimited associated package resources ('download urls') with additional metadata (format, description etc) |
| | 18 | * Complete web user interface (WUI) |
| | 19 | * Package adding, editing, listing etc |
| | 20 | * Wiki features such as "Recent Changes", edit histories, purging of changes etc |
| | 21 | * User management and user home pages |
| | 22 | * API: full JSON-based API (with python client) |
| | 23 | * RDF version also available |
| | 24 | * CKAN is easy to use as your "catalogue" backend |
| | 25 | * Search: Full searchability (including full-text support) via API and WUI |
| | 26 | * Access control: fine-grained access control for packages and groups |
| | 27 | * Open-source and python implemented |
| | 28 | * Associated command line client (datapkg) |
| | 29 | |
| | 30 | Coming soon: |
| | 31 | * Package relationships (depends on, derived from ...) |
| | 32 | * Detailed statistics (+ tag clouds etc) |
| | 33 | * See the tickets for more ... |