Home › Commons › Conversations-Forums › Archived conversations, 2005-2007 › Designing and hosting the CI Convergence site ›

feature architecture of the site

Submitted by George Por on December 11, 2006 - 10:06.

from Brandon:

Page
(Static Content)
[Admin/Super user rights for content creation]

Announcement
(Project News/Announcements)
[Admin/Super user rights for content creation]

Full Paper
Abstract
Bibliographic Link
(Archived Research/Educational Content)
[Admin/Super/Participant user rights for content creation]

Community Blog
(All participants can maintain a personal blog)
[Participant user rights for content creation]

**All of the above is outside of the group-ware framework.

Within the groups framework:
(This framework can scale to as many groups as you see fit)

Group
(These are the containers for the group-ware environment)
[Admin/Super user rights for content creation]

Discussion Topic (The name used to identify this can be changed)
(Participants post discussion topics, other users comment on specific
topic. Comments are threaded)
[Participant user rights for content creation]

Book
(Participants can work on collaborative texts)
[Not sure about this yet, it might be good to restrict]

Just to clarify, as you suggest George, we can create additional working
groups as this starts to self-organize.

I guess what I am suggesting is that we utilize a general
conference-wide working group to start things rolling.

response to questions

Submitted by Brandon Goldsmith (not verified) on December 11, 2006 - 21:14.

> how can topics organized into bigger containers, like forums, if we don't have  forums?

The group acts as the container, so these groups could be thematic or geographical or some other thing that brings the group of people together to share discussion topics.  One difference  between groups and forums (at least within drupal) is that a discussion topic could potentially (not sure that we want to set it up like this yet, because of size of community) have multiple audiences (groups).  Another useful aspect of groups is that multiple content types can flow through the group.

>Can we make [books] read-write to registered members, read-only to visitors?

Yes, but this might be tricky if these books are within the groupware framework. I'll look into this.

 >Can blog entries and topic replies associated with both vocabulary categories and folksonomy tags?

Yes 

 

container for topics / book access rights / categories and tags

Submitted by George Por on December 11, 2006 - 10:15.

Brandon, could you say more on:

how can topics organized into bigger containers, like forums, if we don't have  forums?

> Book (Participants can work on collaborative texts)
> [Not sure about this yet, it might be good to restrict]

Can we make it read-write to registered members, read-only to visitors?

Can blog entries and topic replies associated with both vocabulary categories and folksonomy tags?