sensenet 7: this article has aon the new community site.
Sense/Net Content Repository provides services to end users for managing content. It has the following features:
- Content storage in one hierarchical tree structure with content types
- Built-in and custom meta data for content
- Create (or upload), modify, delete, copy and move content
- Trash for temporary deletion
- Ultrafast query and full text search
- Permission management with inheritance in the tree
- Versioning (version control, version history and locking) for collaboration
- WebDAV, so users can map the repository as a remote drive
- Standard OData REST API for third party applications
Structured storage of Content
Sense/Net Content Repository is basically a tree structure of the various stored content. A specific content is identified by a unique number (id) and also by its path in SNCR. The root of SNCR is at /Root path, all other content is placed somewhere under this root content - for example the login page for the default site is placed at /Root/Sites/Default_Site/login. The default structure is organized as follows (only the main folder structure is listed here):
Content Repository and the type system
Sense/Net Content Repository is built upon a metadata system with pre-defined base types and type inheritance support. Content stored in SNCR can have different types, but content can be one type at any one time. A content type defines the properties (fields) and behavior of content. Content type definitions are also stored as content in the repository. They are located in the /Root/System/Schema/ContentTypes folder. To sum it up, the SNCR relies on the type system that - from the storage perspective - defines the reusable set of fields for each content type. You can also add extra fields to a certain content (apart from the fields in its type) through aspects.
Metadata indexing for fast search and filtering
Content in the SNCR are indexed using the Lucene indexing and search library. The text of binary documents (Micosoft Word, Excel, Adobe PDF, etc) is extracted and can also be searched in SNCR. Lucene provides extremely fast query results even on big (over 10 million content) repositories.
Content access and url resolution
Every content in SNCR is identified by its unique Id and its path. You cannot change a content ID, but you can move a content to another folder and thus change its path. The tree structure of the SNCR makes it possible to use the path as a link to the content, and thus the individual content can be addressed by their root-relative or site-relative paths as URL links. For example a root-relative /Root/Sites/Default_Site/My-folder/My-file.docx content can be addressed as My-folder/My-file.docx if your browser is on the Default_Site.
Managing Sense/Net Content Repository
In an ECM system, just as in our case in Sense/Net ECM most of the operation of end users consists of searching, reading and writing content in the content repository. Document libraries in workspaces, custom forms, pictures in image libraries are all stored and managed in the one and only big tree of Sense/Net Content Repository. If you want to have an overview of the whole tree structure (similarly to Windows Explorer or OSX Finder) you can use the administrative GUI of Sense/Net ECM, the Content Explorer.
There are no examples for this article.
- How to add/modify/delete content in Content Explorer
- Content Explorer
- Content Type
- Smart Application Model
- The Skin System
There are no external references for this article.