内容的CMS版本控制策略 [英] CMS versioning strategies for content
问题描述
我正在寻找在我们的网络产品中构建基本的CMS功能,并研究版本控制内容的提示和设计思路。我特别寻找今天正在使用的数据库模式。
您在内容版本控制中使用了什么?如果您有不同类型的内容需要存储版本,则适用哪些模式?如何在Stack Overflow上处理问题版本控制?
感谢
文学对此使用5维模型:
- 版本(想更改)
- 查看(html,pdf,文件系统,派生性)
$ b
大多数系统只处理这些维度中的几个。
参考:
em>管理设计数据:CAD框架,配置管理和产品数据管理的五个维度。
van den Hamer,P. Lepoeter,K.
Philips Res。,Eindhoven;
本文件出现在
的会议记录出版日期:1996年1月
卷:84,问题:1
页面:42-56
ISSN:0018-9219
参考文献引用:26
CODEN:IEEPAD
INSPEC注册号:5175049
数字对象标识符:10.1109 / 5.476025
当前版本发布日期:2002-08-06
I'm looking at building basic CMS functionality into our web product and am researching tips and design ideas for versioning content. I'm specifically looking for database schemas in use today.
What are you using for content versioning? What patterns apply if you have different types of content that need versions stored? How is question versioning handled on Stack Overflow?
Thanks
Literature uses a 5 dimensional model for this:
- version (wanting to change)
- status (life cycle: creating, testing, deploy, retire)
- view (html, pdf, file system, derivability)
- hierarchy (page, section, paragraph)
- variant (largely similar, describing the differences, product families)
Most systems only handle a few of these dimensions. To handle all five, you have to describe (fix) your development process.
The reference:
Managing design data: the five dimensions of CAD frameworks, configuration management, and product data management.
van den Hamer, P. Lepoeter, K.
Philips Res., Eindhoven;
This paper appears in: Proceedings of the IEEE
Publication Date: Jan 1996
Volume: 84, Issue: 1
On page(s): 42-56
ISSN: 0018-9219
References Cited: 26
CODEN: IEEPAD
INSPEC Accession Number: 5175049
Digital Object Identifier: 10.1109/5.476025
Current Version Published: 2002-08-06
这篇关于内容的CMS版本控制策略的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!