The Proposals Wiki has been deprecated in favor of creating Feature Requests in JIRA. If you wish to propose a new idea for a feature, visit the Community Ideas Dashboard and read the Feature Requests Wiki page for more information about submitting your proposal.
« 返回到 Document Library...

Dynamic Content Modules

Ported from main wiki. Original proposal by Jonas X. Yuan.

Introduction #

The Document library portlet should support whole functions of Documents management (DM) and Record management (RM). This would make it on par with the features of other doclibs on the market. It should also connect to MS Sharepoint, and possibly offer Sharepoint features.

Overview #

Liferay's Library portlet provides document management backed by the Jackrabbit JSR-170 compliant Java content repository. Features include checkin/checkout, metadata, and versioning. Moreover, document file formats are easily converted.

This article will discuss features required for DM and RM, and it will talk about how to add dynamic content model in document library. It will also go into detail about how to implement dynamic content model in document library. The extended Document Library is also capable of connecting with Microsoft Sharepoint as well.

Detailed discussion: http://www.liferay.com/web/guest/community/forums/-/message_boards/message/2031035

Requirements #

The following table lists possible requirements on DM and RM. (C: Completely Supported; P: Partially Supported; N: not supported yet)

Required Features Expectation and Functions Document Library Notes
JSR 170 Content repository C: It uses Jackrabit
JSR 283 Content repository N: Depends on Jackrabit
Check in / check out Persistent-function P: Non-persistent – instance-based (5.2); C: 6.0 The flag should be stored in database
Custom meta-data Meta-data could be defined by users dynamically P: using Custom Fields Meta-data should be defined as any data type
Custom content type different content type will have different set of meta-data N: Only fixed meta-data are supported Users should be able to define their content types and meta data for each content type
Reference Refer to another content N: Ability to refer to any content or images
Association Associated to others contents N: Ability to associate with any content or images
Links Links to others content N: Ability to link to any content or images
Thumbnail image Icon, or logo or thumbnail images N: Each content may have one or more thumbnails
Authoring Who created content N: author
Own-able Who owned content N: owner
Auditing What’ action on content C: 6.0 Content Action history
Versioning Version history C: Versions on content
Replaceable Replace existing document N: Only content gets replaced
Attachable Attach content N: Attach any documents
Localizable meta-data localization P: Only fixed meta-data are supported For custom metadata
Transformable Open Office C: Open Office integration
Workflow-able jBPM workflow or BPEL C: 6.0 Workflow or BPEL on content
Rule-able Using rules on content C: 6.0 Using rules
Bulk import Bulk import content N: Bulk import
Content Backup Metadata and Jackrabit C: backup
Web Scripts REST N: Ability on dynamical content model
Web services SOAP P: only fixed metadata are supported WS ability on dynamical content model and meta data
CMIS Content Management Interoperability Services C: 6.0 Protocol
Indexing Search indexing P: only fixed metadata are supported Based on dynamical content types and custom meta-data

For example, there are two content types:

GAME - metadata: name, description, thumbnail, mini_game, keywords, content, tips, etc.

VIDEO - metadata: name, description, title, thumbnail, large_thumbnail, medium_thumbnail, small_thumbnail, preview_video, keywords, content, etc.

[Integration with OpenX]

0 附件
25602 查看
平均 (2 票)
满分为 5,平均得分为 4.0。
评论