Is there a standard way to do this with CCK/views (etc) - a tutorial would be fantastic...
I'm looking to establish a website in which a community researches a topic and builds a 'knowledge-base' dynamically. I envision the community being similar to that of a wiki - but I want the data to be more structured than that. At the outset, I envision each 'record' to conform to a simple format - including a free-text notes field. As time goes by, I envision new (possibly optional) fields to suggest themselves (at the end-user domain-focused logical level, at least) and I want the site to be able to evolve (without downtime, and with minimum 'programming') to embrace ever more structured records. A major stumbling block is that, while the community is expected to have a common goal, some of the data might easily be contentious - hence it is essential that the changes are version-controlled and that an audit trail can be reviewed. Are there standard Drupal modules that would allow me to set up something like this, or would I need to write them from scratch? Thanks, in advance, for any hints..
Quoting Steve <sjh_drupal@shic.co.uk>:
I'm looking to establish a website in which a community researches a topic and builds a 'knowledge-base' dynamically. I envision the community being similar to that of a wiki - but I want the data to be more structured than that. At the outset, I envision each 'record' to conform to a simple format - including a free-text notes field. As time goes by, I envision new (possibly optional) fields to suggest themselves (at the end-user domain-focused logical level, at least) and I want the site to be able to evolve (without downtime, and with minimum 'programming') to embrace ever more structured records.
A major stumbling block is that, while the community is expected to have a common goal, some of the data might easily be contentious - hence it is essential that the changes are version-controlled and that an audit trail can be reviewed.
Are there standard Drupal modules that would allow me to set up something like this, or would I need to write them from scratch?
Administer the Content Type with admin/content/types and add "Create new revision" under the "Workflow settings" fieldset. Then allow the users to review and/or revert the revisions in admin/user/permissions for the Node module. -- Earnie http://r-feed.com Make a Drupal difference and review core patches. -- http://for-my-kids.com/ -- http://www.4offer.biz/
You would for sure want to use Revisions (part of core, just need to set up on each content type. Check out each content type's edit page). There's a Diff module which will show the differences in each node, and there is a permission for reverting revisions, too. You could also look at using revision_moderation if you are wanting to approve each revision. On Mon, Mar 16, 2009 at 8:43 AM, Steve <sjh_drupal@shic.co.uk> wrote:
I'm looking to establish a website in which a community researches a topic and builds a 'knowledge-base' dynamically. I envision the community being similar to that of a wiki - but I want the data to be more structured than that. At the outset, I envision each 'record' to conform to a simple format - including a free-text notes field. As time goes by, I envision new (possibly optional) fields to suggest themselves (at the end-user domain-focused logical level, at least) and I want the site to be able to evolve (without downtime, and with minimum 'programming') to embrace ever more structured records.
A major stumbling block is that, while the community is expected to have a common goal, some of the data might easily be contentious - hence it is essential that the changes are version-controlled and that an audit trail can be reviewed.
Are there standard Drupal modules that would allow me to set up something like this, or would I need to write them from scratch?
Thanks, in advance, for any hints..
-- [ Drupal support list | http://lists.drupal.org/ ]
-- Brett Evanson brettev@gmail.com
Earnie Boyd wrote:
Administer the Content Type with admin/content/types and add "Create new revision" under the "Workflow settings" fieldset. Then allow the users to review and/or revert the revisions in admin/user/permissions for the Node module. Thanks, I'll have to play around with that some more...
Brett Evanson wrote:
You would for sure want to use Revisions (part of core, just need to set up on each content type. Check out each content type's edit page). There's a Diff module which will show the differences in each node, and there is a permission for reverting revisions, too. You could also look at using revision_moderation if you are wanting to approve each revision.
Thanks, also for the extra detail... again, I suspect, I will need to spend longer playing around with this stuff - it is, however, very helpful to know that I'm not trying to do something entirely new. In the absence of a tutorial, by any chance, can anyone point me a a web site that uses drupal and revisions - so that I can get a feel for what can be done with the existing framework? Steve
On Mar 17, 2009, at 9:11 AM, Steve wrote:
In the absence of a tutorial, by any chance, can anyone point me a a web site that uses drupal and revisions - so that I can get a feel for what can be done with the existing framework?
Yes, http://drupal.org. For example, see http://drupal.org/node/344141/revisions (click on the view tab at the top of the page to view the current version). -Mike __________________ Michael Prasuhn 503.488.5433 office 714.356.0168 cell 503.661.7574 home mike@mikeyp.net http://mikeyp.net
Steve, you may also want to look at the Using Drupal book (O'Reilly press). It has a chapter on creating a Wiki which uses a few modules (but no any of the Wiki modules interestingly) to create this sort of content. Wikis definitely make use of revisions and the diff module and might give you some ideas for collaborative content. Regards, - Peter On Tue, 2009-03-17 at 16:11 +0000, Steve wrote:
Earnie Boyd wrote:
Administer the Content Type with admin/content/types and add "Create new revision" under the "Workflow settings" fieldset. Then allow the users to review and/or revert the revisions in admin/user/permissions for the Node module. Thanks, I'll have to play around with that some more...
Brett Evanson wrote:
You would for sure want to use Revisions (part of core, just need to set up on each content type. Check out each content type's edit page). There's a Diff module which will show the differences in each node, and there is a permission for reverting revisions, too. You could also look at using revision_moderation if you are wanting to approve each revision.
Thanks, also for the extra detail... again, I suspect, I will need to spend longer playing around with this stuff - it is, however, very helpful to know that I'm not trying to do something entirely new.
In the absence of a tutorial, by any chance, can anyone point me a a web site that uses drupal and revisions - so that I can get a feel for what can be done with the existing framework?
Steve -- [ Drupal support list | http://lists.drupal.org/ ]
and replay and replay and replay.....
*Thank For your Message I will replay to you as soon as I can* ...
*
*شكراً لك، لقد وصلت رسالتك سوف اقوم بالرد بأقرب فرصة ممكنة .. *
*
*سپاسگذارم ، در نزدیکترین فرصت پاسخ نامه ات خواهم داد *
*
------------------------------------------------------
*
Eng. Abdulla Awadh Bamelhas
م. عبدالله عوض باملهس
------------------------------------------------------------------------
-- [ Drupal support list | http://lists.drupal.org/ ]
Peter Dowling wrote:
Steve, you may also want to look at the Using Drupal book (O'Reilly press). It has a chapter on creating a Wiki which uses a few modules (but no any of the Wiki modules interestingly) to create this sort of content. Wikis definitely make use of revisions and the diff module and might give you some ideas for collaborative content. If that book is recommended, I guess I'll need to order a copy... I've kept an eye out at my local bookshop (as I'd prefer to have a glance through before parting with cash...) but haven't taken the plunge.
The big challenge that I see is with respect to the structure I want to impose on the content. While I don't want to chose an implementation strategy prematurely, it feels as if I want to manage pages conforming to an extensible (and backwardly compatible) verified XML schema... and to, somehow, keep track of ownership and edit history. It seems such an obvious thing to want to do... Steve
You'll have to experiment with some different options. I don't know about the XML part. But CCK does support fields so you can control the structure. If you need some sort of parent to children (one to many) then look at some of the ways that people use nodereference fields. And diff modules will allow users to see differences between revisions to the field level (and taxonomy as well I think). The pieces are all there for you I think. - Peter On Thu, 2009-03-19 at 19:06 +0000, Steve wrote:
Peter Dowling wrote:
Steve, you may also want to look at the Using Drupal book (O'Reilly press). It has a chapter on creating a Wiki which uses a few modules (but no any of the Wiki modules interestingly) to create this sort of content. Wikis definitely make use of revisions and the diff module and might give you some ideas for collaborative content. If that book is recommended, I guess I'll need to order a copy... I've kept an eye out at my local bookshop (as I'd prefer to have a glance through before parting with cash...) but haven't taken the plunge.
The big challenge that I see is with respect to the structure I want to impose on the content. While I don't want to chose an implementation strategy prematurely, it feels as if I want to manage pages conforming to an extensible (and backwardly compatible) verified XML schema... and to, somehow, keep track of ownership and edit history. It seems such an obvious thing to want to do...
Steve
-- [ Drupal support list | http://lists.drupal.org/ ]
participants (7)
-
bamlhs＠hotmail.com -
Brett Evanson -
Dan Robinson -
Earnie Boyd -
Michael Prasuhn -
Peter Dowling -
Steve