Go to file
2013-04-30 18:07:57 +12:00
_config Further updates for 3.1 compatibility. 2013-04-15 14:03:58 +12:00
code NEW adding content method for compatibility with TextExtraction module 2013-04-30 18:07:57 +12:00
css BUGFIX: IE8 Document type selected stylings 2012-09-12 11:57:30 +12:00
images ENHANCEMENT: Add styling to Embargo and expiry fields. Change date format to dd-mm-yyyy 2012-08-16 16:18:41 +12:00
javascript BUG DMSUploadField JS template usage 2013-01-07 10:11:55 +13:00
lang added nl.yml language 2013-01-29 03:11:47 -08:00
resources ENHANCEMENT: protecting the "dms-assets" folder from web access 2012-08-07 11:16:10 +12:00
scss BUGFIX: IE8 Document type selected stylings 2012-09-12 11:57:30 +12:00
templates Change to use loop in templates instead of control 2013-04-16 10:00:42 +12:00
tests Simplified travis support (using external scripts) 2013-03-29 10:07:05 +01:00
_config.php Further updates for 3.1 compatibility. 2013-04-15 14:03:58 +12:00
.gitignore ENHANCEMENT: adding scss stlying 2012-08-01 16:12:11 +12:00
.travis.yml Simplified travis support (using external scripts) 2013-03-29 10:07:05 +01:00
composer.json Fixed composer vendor namespace 2012-11-22 15:14:30 +01:00
config.rb ENHANCEMENT: adding scss stlying 2012-08-01 16:12:11 +12:00
README.md Travis support 2013-03-11 01:44:45 +01:00

Document Management Module (DMS)

Build Status

Overview

The module adds a new DMSDocument model which allows management of large amounts of files, and their relations to pages. In contrast to the File model built into SilverStripe core, it aims to wrap storage and access concerns in a generic API, which allows more fine-grained control over how the documents are managed and exposed through the website.

Additionally, documents are stored and managed as part of a page instead of away in a separate assets store.

Read more about the DMS module in this blog post on silverstripe.org

Features:

  • Relation of documents to pages
  • Management and upload of documents within a page context in the CMS
  • Metadata management through the powerful GridField and UploadField core APIs
  • Configurable tags for documents
  • Download via SilverStripe controller (rather than filesystem URLs)
  • Access control based on PHP logic, and page relations
  • Replacement of existing files

Documents on the Filesystem

While the DMS architecture allows for remote storage of files, the default implementation (the DMS class) stores them locally. Relations to pages and tags are persisted as many-many relationships through the SilverStripe ORM.

File locations in this implementation are structured into subfolders, in order to avoid exceeding filesystem limits. The file name is a composite based on its database ID and the original file name. The exact location shouldn't be relied on by custom logic, but rather retrieved through the API (DMSDocument->getLink()).

Example:

dms-assets/
	0/
		1234~myfile.pdf
	1/
		2345~myotherfile.pdf

Requirements

Configuration

The file location is set via the DMS::$dmsFolder static, and points to a location in the webroot.

Usage

Add a simple include to any of your .ss templates to display the DMSDocuments associated with the current page on the front-end.

<% include Documents %>

Create Documents

Create by relative path:

$dms = DMS::getDMSInstance();
$doc = $dms->storeDocument('assets/myfile.pdf');

Create from an existing File record:

$dms = DMS::getDMSInstance();
$file = File::get()->byID(99);
$doc = $dms->storeDocument($file);

Note: Both operations copy the existing file.

Download Documents

$dms = DMS::getDMSInstance();
$docs = $dms->getByTag('priority', 'important')->First();
$link = $doc->getLink();

Manage Page Relations

// Find documents by page
$dms = DMS::getDMSInstance();
$page = SiteTree::get()->filter('URLSegment', 'home')->First();
$docs = $dms->getByPage($page);

// Add documents to page

Manage Tags

// Find documents by tag
$dms = DMS::getDMSInstance();
$docs = $dms->getByTag('priority', 'important');

// Add tag to existing document
$doc = Document::get()->byID(99);
$doc->addTag('priority', 'low');

// Supports multiple values for tags
$doc->addTag('category', 'keyboard');
$doc->addTag('category', 'input device');

// Removing tags is abstracted as well
$doc->removeTag('category', 'keyboard'); 
$doc->removeTag('category', 'input device'); 
$doc->removeAllTags();